Database Develop

[Q] all software on my moto x is gone. please help.

so i tried to update to the new sprint update that fixes the 4.4 battery issues. i was on twrp recovery and i flashed back to stock recovery and tried to dirty flash the update on top. i had xposed framework installed so was pretty sure that wasn't going to work. and it didn't. now i decided to use the moto x toolkit to flash back to stock. it booted up just fine then i downloaded the update from 4.2.2 to 4.4 and the update failed. now i'm stuck with basically nothing on my phone at all. i can get to fastboot mode but thats it. cant power up cant enter recovery can't do anything.. also i had a unlocked bootloader and now its reading locked again. here is the error i'm getting.
failed to hab check for gpt_nain: 0x35
failed to hab check for gpt_gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. contact Dealer: 0xdead
No SP partition found
Fastboot Reason: Invalid CID
I've been working on this for about 7 hours and have looked up everything i could think of to try and get this fixed. i may just be missing something.. does anyone know how i could fix this?

What version is your bootloader, you can see it in the fastboot screen.

30.71(*) (sha-913941e, 2013-07-31 10:46:37)
is that was your looking for?

OK, that is the 4.2.2 bootloader. Your bootloader is locked in that screen shot - so how did you install twrp recovery?
Also your avatar shows AT&T but you mention you tried using the Sprint update, can you confirm the phone you have is a Sprint model?

Steve-x said:
OK, that is the 4.2.2 bootloader, so you should be fine to try flashing the phone again. I'd download the Sprint 4.4 package and try a full flash using rsdlite if possible. Everything on the phone will be wiped/erased of course. Then take the update to 4.4.2. Once that is done you can reinstall the latest version of twrp and root the phone again.
Click to expand...
Click to collapse
thanks for the reply! well i already tried that and i can't get rsd to flash. are there some special drivers i'm supposed to install? i got the motorola drivers from their web-sight. and it won't flash. it sees that there is a phone but all catagories read n/a and it just comes up with flash fails..

i'm not sure how the bootloader got locked again.. it wasn't locked before i'm pretty sure the moto x toolkit i used to flash back to stock relocked it?.. or maybe not. but i do know it was unlocked and now its locked. and when i try to get the unlock code like last time it doesn't work.

yes this is a sprint phone.
Edit: thank you for pointing that out, never changed it from years ago

If you were able to relock the bootloader and have the phone report status code 0 then you'd be the first to have done it. You can relock the bootloader but it requires a specific procedure to be followed and the phone will never indicate status code 0 again.
Review this guide - the first flashing option you should work for you, remember to remove the getvar line
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515

i'm a idiot. i must have looked at that guide 15 times today and never read through all of it. just needed to deleate that one file and it all worked. thanks everyone for you help!

the status code 0 must have been incorrect. its back to status code 3 and unlocked. thank you all for your help!

[Q][Solved] Relocking the bootloader

Hey guys,
I am currently trying to get my Moto X back to stock and relock the bootloader. Not because I need to, but just because I want to. I have a retDe XT1092 which I have converted to a XT1095. Is there any way to get the phone back to software status official and relock the bootloader? It doesn't matter to me that Motorola does know that I was unlocked before, I just want to relock it. I hope you guys can help me.

May I ask why you want to relock it? There really is no benefit to relocking it. :/
Anyway the command is:
fastboot oem lock
Sent from my XT1095

I know, but want to keep myself from flashing on this phone. I am trying to get away from rooting on non-nexus phones.
Yeah I've tried that multiple times, but as long as your software status isn't official the oem lock will fail. I'd guess this happens because most images you can download are not signed images.

Is your phone still converted to 1095? If so that is why lock wont work.
You would have to flash back the 1092 de image to be unmodified.
Sent from my XT1095

Okay good to know. I thought this wouldnt matter. But are there even any existing official images for the 1092?

Moto x firmwares:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25
Sent from my XT1095

These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.

Bl4ckX said:
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Click to expand...
Click to collapse
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.

juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095

juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.

AGISCI said:
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
Click to expand...
Click to collapse
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
strafer69 said:
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
Click to expand...
Click to collapse
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?

Bl4ckX said:
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Click to expand...
Click to collapse
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095

AGISCI said:
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
Click to expand...
Click to collapse
I am currently downloading the XT1092 retDe image. I will report back in 6hours when I am back from work and this damn free download is finished. It takes forever..

The bootloader unlocked message would be a signed Motorola image since it is shipped with the phone. The bootloader essentially has a toggle that would switch between the normal and the unlocked message. I assume the toggle just doesn't get switched back when you OEM lock. It's not like he flashed a different custom logo or anything.
Sent from my Moto X 2014 Pure Edition using Tapatalk

Correct. You will notice the status message when you enter the bootloader there is a status code. 1=LOCKED 2=RELOCKED and 3=UNLOCKED. Once you unlock the bootloader, you can never go back to status 1 again and you will always get the bootloader unlocked message. If you read the message it states that the bootloader HAS been unlocked. There is a counter trigger in the phone telling it how many times it has been unlocked. When I had my old Galaxy S2 Skyrocket I remembered a program that would "RESET" this counter, but I do not believe one exists for Motorola. Once you unlock your bootloader there is no going back.
http://i5.androidxda.com/main/Motorola_Bootloader_Warning.png

Yeah I know about this relocked state, but it doesn't matter as I don't want to RMA the phone. I just want it locked but I wasn't able to accomplish a successful oem lock and I am now searching for a way to do so.
Edit: So this morning after the download had finished I brought my X to fastboot mode. And for whichever reason the software status was set to official even on the XT1095 image. I would have sworn that this wasn't the case when I flashed it and I have no idea why it changed. And a big thanks to you @AGISCI after typing "fastboot oem lock begin" I could flash the Image you linked here and software status stayed official and I was even able to relock the bootloader. So I simply must have had wrong images in the past, because I did entirely the same process I did now, 3 times already and it didn't work out at all.
So thanks again guys. The only annoyance is that I can't get rid of the bootloader unlocked message. This one seems to stay.

Relock Droid Turbo Bootloader

What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.

mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.

According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.

Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk

SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.

TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?

You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571

Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse

droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.

How to get out off a full brick?( i have tried it all so far)

I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?

Still stucked?
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse

Salik Iqbal said:
Still stucked?
Click to expand...
Click to collapse
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.

Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse
Cesarisg said:
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.
Click to expand...
Click to collapse

Salik Iqbal said:
Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Click to expand...
Click to collapse
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.

I am ARSH and Iive in india if some one is having brazzers membership p lzz give me for one day p lzz share with me my e-mail [email protected] plzzzzzz

No problem..
Cesarisg said:
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.
Click to expand...
Click to collapse

I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.

mwaterbu said:
I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.
Click to expand...
Click to collapse
There was 2 main reasons why I had to go back to stock, the main one was that the OS would not let me uninstall any app, I tried everything I read online to try to fix it, even flashing the rom again, nothing work and the other reason was the phone app would not let me hear from the earpiece, it got fixed after getting back to 5.1 and many other bugs and sudden restarts, some of them might be cause by my phone or not, but since 5.1 everything is a lot more stable.

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