'bad key' message when booting phone - Moto Z Play Questions & Answers
Hi, first time newbie posting here
I've tried looking up my problem but I have a slightly different issue to what I've seen others have.
When I turn on the phone it says 'bad key' in an odd spot. It delays the boot up time a little but eventually loads up fine.
I was aware of this before I purchased it from the person. I think the person must of got an early release of Nougat for developers because the 'About phone' details seem different to my 2nd (store purchased) Moto Z Play even after checking for system updates.
Bad Key Photo (apologies for the bad quality)
imgur.com/a/YCwht
Settings>About Phone Screenshot
imgur.com/a/6eDtd
I would assume the bootloader is unlocked, but the message looks a little different than what it usually says. Normally there's a triangle and says the device is unlocked and cannot be trusted as well. As for the About Phone, it looks the same for me.
IncendiaryPyro said:
I would assume the bootloader is unlocked, but the message looks a little different than what it usually says. Normally there's a triangle and says the device is unlocked and cannot be trusted as well. As for the About Phone, it looks the same for me.
Click to expand...
Click to collapse
Here are the details on my other Moto Z Play (the stock one) - note the different build number and security patch (both updated).
imgur.com/a/EBs1x
Could locking the bootloader remove the 'bad key' thing? How would I go about doing that?
iivii14 said:
Here are the details on my other Moto Z Play (the stock one) - note the different build number and security patch (both updated).
imgur.com/a/EBs1x
Could locking the bootloader remove the 'bad key' thing? How would I go about doing that?
Click to expand...
Click to collapse
Sorry but once the bootloader is unlocked, there is no method to relock.
iivii14 said:
Hi, first time newbie posting here
I've tried looking up my problem but I have a slightly different issue to what I've seen others have.
When I turn on the phone it says 'bad key' in an odd spot. It delays the boot up time a little but eventually loads up fine.
I was aware of this before I purchased it from the person. I think the person must of got an early release of Nougat for developers because the 'About phone' details seem different to my 2nd (store purchased) Moto Z Play even after checking for system updates.
Bad Key Photo (apologies for the bad quality)
imgur.com/a/YCwht
Settings>About Phone Screenshot
imgur.com/a/6eDtd
Click to expand...
Click to collapse
This is just someone trying to cover up the unlocked bootloader message with an altered boot logo. Whoever you bought it from tried to hide the fact that they terminated the warranty even though you could send it to Moto for them to relock it with a new key.
DroneDoom said:
This is just someone trying to cover up the unlocked bootloader message with an altered boot logo. Whoever you bought it from tried to hide the fact that they terminated the warranty even though you could send it to Moto for them to relock it with a new key.
Click to expand...
Click to collapse
Thanks, I'll give that a shot. Hopefully it wont cost too much.
Just wondering if I changed the rom to lets say Lineage would that 'bad key' message still exist?
What is so bad about that message?
It says
"You can do backups of partitions using TWRP"
It says
"You can root, meaning you can do backups of apps using Titanium backup"
It says
"You can root, meaning you can copy files keeping timestamps like on any other OS"
It also says
"You most probably won't get repairs from Lenovo because warranty is void"
Last point is the disadvantage, but changing the image or text won't help. Lenovo has your device ID in the database of unlocked devices.
tag68 said:
What is so bad about that message?
It says
"You can do backups of partitions using TWRP"
It says
"You can root, meaning you can do backups of apps using titanium backup"
It says
"You can root, meaning you can copy files keeping timestamps like on any other OS"
It also says
"You most probably won't get repairs from Lenovo because warranty is void"
Last point is the disadvantage, but changing the image or text won't help. Lenovo has your device ID in the database of unlocked devices.
Click to expand...
Click to collapse
I got in touch with Motorola's/Lenovo's authorised repairer here in Australia. I was told the motherboard would have to be changed- around $400 so not worth it.
I was actually planning to use the phone as a gps tracker so the extended boot time bothers me a little and also the fact the system updates aren't the same as my other (stock) Moto Z Play.
iivii14 said:
I was actually planning to use the phone as a gps tracker so the extended boot time bothers me a little
Click to expand...
Click to collapse
That 5 seconds display bad key? Never had problems with it, because I usually keep my device running. Would it be difficult for you to not turn it off?
I'm more bothered by annoying boot animation, unfortunately with sound. But there locked or unlocked bootloader makes no difference.
iivii14 said:
and also the fact the system updates aren't the same as my other (stock) Moto Z Play.
Click to expand...
Click to collapse
If you don't root it and don't install another OS, there is no reason for updates to be different just because the bootloader is unlocked. What is the difference in your case?
tag68 said:
That 5 seconds display bad key? Never had problems with it, because I usually keep my device running. Would it be difficult for you to not turn it off?
I'm more bothered by annoying boot animation, unfortunately with sound. But there locked or unlocked bootloader makes no difference.
If you don't root it and don't install another OS, there is no reason for updates to be different just because the bootloader is unlocked. What is the difference in your case?
Click to expand...
Click to collapse
It's about 20 seconds- I know it's not thaaaat bad but still I'd like it to fire up asap.
Its going to live in a car and only charging while the car is running (so the car battery doesn't go flat). I still need to set it up but once the car is started it'll turn back on.
I'm uncertain if its actually a different OS- it looks like the original one but its almost like the previous owner unlocked it to get Nougat on it before it was officially released- thought someone might know from the screenshot.
iivii14 said:
Its going to live in a car and only charging while the car is running (so the car battery doesn't go flat). I still need to set it up but once the car is started it'll turn back on.
Click to expand...
Click to collapse
You may consider adding a power block to your setup. I'm usually not charging my mobile from the car, but from a power block which has the advantage that I don't need long cables (cigarette lighter is on the other side of steering wheel). They are cheap and add flexibility.
If you charge the power block at home or from the car, maybe charging power block and mobile sometimes in parallel using dual adapter in the car, and which size of power block you use, may be worth consideration.
iivii14 said:
...- thought someone might know from the screenshot.
Click to expand...
Click to collapse
Sorry, I can't tell.
If it turns out to be some wrong version or if you just don't trust the current installation, you are free to flash an original one. Unfortunately Lenovo does not release signed official versions, at least not until now. There are some links on xda. Some of them should be the right one
iivii14 said:
Thanks, I'll give that a shot. Hopefully it wont cost too much.
Just wondering if I changed the rom to lets say Lineage would that 'bad key' message still exist?
Click to expand...
Click to collapse
You would get 'N/A' in place of the 'bad key' message. This because custom rom devs don't encrypt/sign their roms like Moto does so there is no key to compare (thus N/A).
iivii14 said:
Hi, first time newbie posting here
I've tried looking up my problem but I have a slightly different issue to what I've seen others have.
When I turn on the phone it says 'bad key' in an odd spot. It delays the boot up time a little but eventually loads up fine.
I was aware of this before I purchased it from the person. I think the person must of got an early release of Nougat for developers because the 'About phone' details seem different to my 2nd (store purchased) Moto Z Play even after checking for system updates.
Bad Key Photo (apologies for the bad quality)
imgur.com/a/YCwht
Settings>About Phone Screenshot
imgur.com/a/6eDtd
Click to expand...
Click to collapse
I know this is old, but I'll place my own answer as an exercise on the subject, if you don't mind: "Bad Key" sign means that someone flashed an unsigned, stock but non-original OS version on your phone; if just unlocked bootloader and even flashed custom recovery on an otherwise original OS (as shipped) it must read "N/A" instead. In both cases, phone should be equally usable; however, if OTA updates can be downloaded, they won't be installed as usual. Assuming that forcefully needed, updates can be ADB or recovery sideload installed. Relocking bootloader won't be possible under given conditions. The black screen with "Bad Key" in there simply means that there is actually no bootlogo installed, probably because previous owner failed in flashing an unwarned one and just refused to keep trying. You can't get rid of the "Bad Key" sign, but you can cover it by flashing any bootlogo of your likes, either with a full white background or a custom made image with a white section that covers exactly on the sign coordinates. Creativity should be used here. No way someone try to charge you big fat megabucks for a new motherboard, since there is no motherboard failure and there's no actual need for such a radical "solution". According to humble my point of view, you just can go rooting Z Play and enjoy the hell out of it...
Sent from my Moto Z2 Play using XDA Labs
Related
[Q] NFC while screen is off?
So is this possible? according to the Xperia commericals showing their NFC-badges you just swipe the phone over it. With the GNex you have to turn the screen on unfortunatly, is there a way to fix that? EDIT: Mod can move this to Q & A, it's getting late over here.
From what I've read, this is a security feature in ICS, as NFC can be used for payments, etc. I can understand why they have changed it, though IMO it should be an editable setting.
eddie_gordo said: From what I've read, this is a security feature in ICS, as NFC can be used for payments, etc. I can understand why they have changed it, though IMO it should be an editable setting. Click to expand... Click to collapse Ah, ofcourse now i see why but yeah it should be editable, though NFC is not that widely used yet i'd like to turn that security feature of until i connect a creditcard to my phone.
Pliind said: So is this possible? according to the Xperia commericals showing their NFC-badges you just swipe the phone over it. With the GNex you have to turn the screen on unfortunatly, is there a way to fix that? EDIT: Mod can move this to Q & A, it's getting late over here. Click to expand... Click to collapse Every demo in the xperia video shows the screen on as far as I can tell, and unlocked. The short answer though is no. ICS requires the device to be on and unlocked before the NFC service is started and the polling loop starts. If someone wants to try to modify the underlying NFC service in a custom rom it's possible. I wouldn't recommend having it on all the time, but a behavior similar to Gingerbread (unlock was not necessary) would probably be desirable for most users.
krohnjw said: Every demo in the xperia video shows the screen on as far as I can tell, and unlocked. The short answer though is no. ICS requires the device to be on and unlocked before the NFC service is started and the polling loop starts. If someone wants to try to modify the underlying NFC service in a custom rom it's possible. I wouldn't recommend having it on all the time, but a behavior similar to Gingerbread (unlock was not necessary) would probably be desirable for most users. Click to expand... Click to collapse Well now that you said it and i checked the video again..your right. Think I got the idea from when he stepped out of the car and just flashed the badge.
Pliind said: Well now that you said it and i checked the video again..your right. Think I got the idea from when he stepped out of the car and just flashed the badge. Click to expand... Click to collapse To be fair they do make it seem like that's how it would work. Who would turn their phone on, unlock it and then turn it upside down BEFORE they get out of their car just to scan an NFC tag once they got out. I don't see that being a reality though as the rest of the demos clearly show the device on and what appears to be unlocked. Given this is how the NFC service works within ICS, I'd suspect this will be the behavior as well.
[Q] accepting eual????
hi, i just unlocked the nexus and upgraded to official rom 4.2.1. by Nexus Root Toolkit then i relocked my phone. but there is a small box shown above the menu key once powering on the sentence showing sth like: please enter application, and accept EULA before using... i dont know how to express but the meaning is like that. and the box disappear after a few seconds. MAY I KNOW WHAT IS EULA? WHERE CAN I ACCEPT IT? this box is not sth big matter to my phone but when i see this sentence once i powering on, i feel mad!!!!!!!!!!!!!!!!!!!
EULA means End User License Agreement.. but i have never gotten this popup and have never heard of others so not sure why you are getting it
k786 said: EULA means End User License Agreement.. but i have never gotten this popup and have never heard of others so not sure why you are getting it Click to expand... Click to collapse :crying::crying::crying: YES!! it seems no one get this problem as i ve searched for a long time OH NO, i need to face this box once i power on?? SOSAD:crying:
[Q] Random app opens
Hi. Occasionally, and with no reason, apps will open on the screen. Often different ones. I close them and then another one will open. This has happened a few times and I can't trace a reason. Anyone have any ideas on what may be causing it and any solutions please? I spoke to HTC UK but no reason could be given. This is my second M8 and both have displayed this strange behaviour. I love it, don't get me wrong, but it's a strange and random phenomena.
openmindedguy said: Hi. Occasionally, and with no reason, apps will open on the screen. Often different ones. I close them and then another one will open. This has happened a few times and I can't trace a reason. Anyone have any ideas on what may be causing it and any solutions please? I spoke to HTC UK but no reason could be given. This is my second M8 and both have displayed this strange behaviour. I love it, don't get me wrong, but it's a strange and random phenomena. Click to expand... Click to collapse Need a little more info. As this is your second phone with the same behaviour it possibly suggests something you have done (unless you have two random phones) Is the phone completely stock? Is it: S-Off Unlocked Rooted Custom Recovery Apps installed Please give as much info as possible if you want people to help
I bet you don't have a case on, am I right? Sent from my HTC6525LVW
case 1ManWolfePack said: I bet you don't have a case on, am I right? Sent from my HTC6525LVW Click to expand... Click to collapse Yes, I have a flip case. An original I bought extra from HTC store. It also happened on the case that came with the phone. The issues occur with or with out the case.
Random app opening grentuu said: Need a little more info. As this is your second phone with the same behaviour it possibly suggests something you have done (unless you have two random phones) Is the phone completely stock? Is it: S-Off Unlocked Rooted Custom Recovery Apps installed Please give as much info as possible if you want people to help Click to expand... Click to collapse Hi. Thanks for the reply and advice. It's Vodafone UK and has apps loaded (around 100). I set both phones up as new, i.e. not used the ransfer tool. I've done a factory reset on both phones. The rom is as it was out of the box (stock?). It's my second identical phone. I'm wondering if its an app causing the behaviour.
I would do a factory reset and leave the apps off for a period and watch the phone. If it fails to happen install one at a time and leave a period between them Laborious I know but at least you will find the offender. If it happens straight after the factory reset then its your phone
Crazy Touch Screen Not Responding Bugs with my G3
So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up... Edit: This is a confirmed fix for me. If you face the same issue, try: open dialer press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400# Hardware Device Test > Touch update touch firmware touch firmware version wait 10 sec reboot
I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag). Sent from my Nexus 5 using Tapatalk
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
deedscreen said: @Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point. Click to expand... Click to collapse That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said: That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen Sent from my SM-N900P using Xparent BlueTapatalk 2 Click to expand... Click to collapse Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh). Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc. If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).
^^^^ - Will take that into consideration. This may be a possible fix for now, can't yet confirm open dialer press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400# Hardware Device Test > Touch update touch firmware touch firmware version wait 10 sec reboot It may or may not help EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.
Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.
@deedscreen I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot. ic_fw_version info SYnaptics 5.5 PanelType 1 version: v1.22 IC_product_id[PLG313] Touch IC : s3528(family_id = 1, fw_rev = 1) What version is your firmware? Also, did you find out about the fix from somewhere?
I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue. I have (RAW) touch screen firmware version: 30 05 51 96
Same problem, but not only on lock screen Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now. But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version. After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again! I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.
This is happening when the screen is on right? Or is the screen turning off and then not turning I again?
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Daum Ex said: You need to keep Knock feature on, someone already said this. That's why your screen is freezing. Click to expand... Click to collapse Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment. So bad: such a good phone and such an annoying bug
icon71 said: Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment. So bad: such a good phone and such an annoying bug Click to expand... Click to collapse I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that... That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Daum Ex said: I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that... That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me... Click to expand... Click to collapse Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like: - this is a normal behaviour and can happen (!!) - don't put your phone in the front pocket - use the quick circle case to prevent... - disable knock on (which is at least not possible over a standard setting, but only via the hidden menu). I wrote back: - that for me, this is not a normal behaviour - that 90% of male users are wearing the phone in the front pocket - that I don't like to buy a case only to prevent a bug of a premium telephone and - finally, that they please could tell me, where and how to disable knock on I am curious about their answer...
Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least. Next time i purchase an Android phone i'm going with Nexus line...
icon71 said: Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem... Click to expand... Click to collapse So what happened? How is it doing now?
Hey everyone, I just wanted to report my results of this touchscreen bug. Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it. I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER! The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen. I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL. I hope this helps someone here.
Knock If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away. I think LG really has to deal with this issue.
Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855. First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck. I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard? I really don't know what to do! Appreciate any comments or suggestions!!! Thanks in advance!
LockScreen Issues
Is anybody else having problems with their lock screen? It stopped working on my phone out of the blue. I tried wiping credentials restarting the phone several times setting up other types of security (pin, password, pattern, etc) but nothing works the phone just won't lock itself anymore it stays unlocked. Can someone please help me? Thanks in advance Update: I forgot I had stay unlocked at location (home) idiot me I know •_•
Wait a minute... I just started having the very same issue 24 hours now, but I don't get what exactly your workaround was. Could you explain a bit? What is that "unlocked on location" thing you're referring to? Is it about "smart lock"? Sent from my Moto G4 Plus using XDA Labs
The Analog Kid said: Wait a minute... I just started having the very same issue 24 hours now, but I don't get what exactly your workaround was. Could you explain a bit? What is that "unlocked on location" thing you're referring to? Is it about "smart lock"? Sent from my Moto G4 Plus using XDA Labs Click to expand... Click to collapse Yes, I think that's what he means. He had set the phone to remain unlocked while at home.
errikosd said: Yes, I think that's what he means. He had set the phone to remain unlocked while at home. Click to expand... Click to collapse Alright, I didn't. I've tried to be a little sarcastic, indeed... Yet, I'm facing this flaw of lock screen not showing nor locking nor doing its thing. Smart lock has never been set on this device, BTW; However, often it briefly reappers after shutting down the phone and restarting it, but not by means of rebooting. So far, NONE of the usual, widespread workarounds (clear caches, credentials or device administrator) is working over here, so I've been looking for a different hint on the subject, to no avail. Sadly, it probably could take years to have the right one, as I can see... But, I'm working on my own; if I don't get bored in the process, end up doing a full OS restore or simply get rid of the phone, then I will let the community know... Sent from my Moto G4 Plus using XDA Labs