[Moto Maxx] Remove unlocked bootloader Warning

[Jaocagomez]

If i do this command will remove unlocked logo?

Yes it will

 

[ChazzMatt]

@respider, two news articles from this week now mention this for the Moto Maxx. One gives you full credit, while the other does not even mention where they found it.

Gives you credit.
http://www.ibtimes.co.uk/how-remove-bootloader-unlocked-warning-moto-maxx-xt1225-1489724

If you wish to get rid of this irritating message at the start-up, here is a simple step-by-step guide for the purpose with due credit to XDA senior member, respider.

Does NOT mention you at all:
http://www.droidviews.com/remove-bootloader-unlocked-warning-on-moto-maxx-xt1225/

Yet uses your file.

Ironically, the site that gives you credit mentions they found out about it from the site that did not give you credit. But they must have done search and found your user name...

 

[respider]

@respider, two news articles from this week now mention this for the Moto Maxx. One gives you full credit, while the other does not even mention where they found it.

Gives you credit.
http://www.ibtimes.co.uk/how-remove-bootloader-unlocked-warning-moto-maxx-xt1225-1489724


Does NOT mention you at all:
http://www.droidviews.com/remove-bootloader-unlocked-warning-on-moto-maxx-xt1225/

Yet uses your file.

Ironically, the site that gives you credit mentions they found out about it from the site that did not give you credit. But they must have done search and found your user name...

Thanks for brining that up!

Looks like link 2 added a source? There's "source xda" with link to this topic at the very end

Enviado do meu XT1225

 

[ChazzMatt]

Thanks for brining that up!

Looks like link 2 added a source? There's "source xda" with link to this topic at the very end

Enviado do meu XT1225

Maybe I overlooked that "source" "XDA" at the end. It blurred into all the "tag" names (and smaller fonts than the article itself).

Whereas, the top link was nice enough to mention you by name IN the article.

 

[xt_gonzalo]

Bootloader logos

Flashing this should affect the bootloader logos right? seeing the huge difference in size from the stock logo.bin

For those who unlocked your bootloaders and now have that annoying "Unlocked bootloader" warning, just download attached file, unzip and flash like this:

fastboot flash logo logo_nounlocked.bin

As always, I'm not responsible for any damage this may cause to your device. Do at your own risk.

Edit: Thanks to @Helvio88 for the help

 

[matheus_sc]

thanks, installed and works fine

 

[arigatox]

Great! Thanks. My Moto maxx ex Chile now Brazil ex Movistar now Retail ex KitKat now Lollipop says thanks!!

 

[ChazzMatt]

Is there any Motorola logo in black background?

It would be great!

Enviado desde mi XT1225 mediante Tapatalk

Yes.

http://forum.xda-developers.com/showthread.php?t=3065141

 

[gumbi2647]

Worked great after I figured out how to flash using fastboot! I haven't done any flashing since my Galaxy S3.
Thanks for all that you pros do for us!!

 

[Shtiff1]

What does the logo look like?

 

[rashdi.edu]

Can I flash logo_nounlocked.bin in to Droid Turbo XT1254

Dear, plz tell me Can I flash logo_nounlocked.bin (Droid Turbo XT1254) plaz reply on my email: [email protected]

For those who unlocked your bootloaders and now have that annoying "Unlocked bootloader" warning, just download attached file, unzip and flash like this:

fastboot flash logo logo_nounlocked.bin

As always, I'm not responsible for any damage this may cause to your device. Do at your own risk.

Edit: Thanks to @Helvio88 for the help

 

[ChazzMatt]

Dear, plz tell me Can I flash logo_nounlocked.bin (Droid Turbo XT1254) plaz reply on my email: [email protected]

Not going to reply to your email. You asked here.

If your bootloader is unlocked, yes you can flash it.

But I actually prefer this one, by @Jaocagomez:

http://forum.xda-developers.com/showthread.php?t=3065141

Replaces the unlock warning with a BLACK Motorola logo!

 

[jdl512]

Remove Unlock Msg prior to trade in

Thanks very much for this. I have unrooted my phone, reinstalled the stock recovery, and returned to stock backup and want to remove the unlock msg to not draw attention while trading in to upgrade my verizon turbo. I have installed ADB and fastboot on my windows PC and updated the drivers as instructed in another thread here. I found that adb will only see my phone if its booted. It will not when i am in fastboot/stock recovery mode. Fastboot will do the opposite. it will see my phone only when in fastboot/recovery mode. USB debugging is enabled.

1- should i be working with adb with my phone booted ?

2- how does the adb command know where to find the bin file? i havent been able to find any info on that.

Thanks very much.

 

[ChazzMatt]

Thanks very much for this. I have unrooted my phone, reinstalled the stock recovery, and returned to stock backup and want to remove the unlock msg to not draw attention while trading in to upgrade my verizon turbo. I have installed ADB and fastboot on my windows PC and updated the drivers as instructed in another thread here. I found that adb will only see my phone if its booted. It will not when i am in fastboot/stock recovery mode. Fastboot will do the opposite. it will see my phone only when in fastboot/recovery mode. USB debugging is enabled.

1- should i be working with adb with my phone booted ?

2- how does the adb command know where to find the bin file? i havent been able to find any info on that.

Thanks very much.

You put the .bin file in the same Windows folder as the other stuff you flashed in the past -- recovery, radio, etc.

The first command you do is from the Windows folder, shift key + right click, open a command window and reboot into bootloader mode. then execute the other commands. In this case to replace the bin file.

See here:

How to Set Up ADB and Fastboot with Android SDK
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/

 

[jdl512]

You put the .bin file in the same Windows folder as the other stuff you flashed in the past xfinity-- recovery, radio, etc.

The first command you do is from the Windows folder, shift key + right click, open a command window and reboot into bootloader mode. then execute the other commands. In this case to replace the bin file.

See here:

How to Set Up ADB and Fastboot with Android SDK
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/

Thank you. This is my first use of adb and fastboot because I was able to unlock, install twerp, and root without connecting to a computer. I should put the new logo bin in the c drive location where the adb and fastboot executables are?

Also, having another issue now since my Windows 10 laptop received a system update today. I can no longer see adb in my device manager on the laptop. That's where I updated driver's last night after install. There's also no 'other devices' there as was originally after installing adb last night. Fastboot won't find my device now. The adb command will send me from booted to fastboot mode, but the fastboot command to install the logo results in 'waiting for device'. 'Fastboot devices' command would show my phone last night, now there is no result. I reinstalled adb again just now using the 15 second install thread, but it still doesn't show in my laptop device manager as it did last night. I am running as administrator. Any help is greatly appreciated. I see the google driver's package installed with adb last night in the programs and features screen, but nothing for adb despite reinstalling just now.

 

[ChazzMatt]

Thank you. This is my first use of adb and fastboot because I was able to unlock, install twerp, and root without connecting to a computer. I should put the new logo bin in the c drive location where the adb and fastboot executables are?

Also, having another issue now since my Windows 10 laptop received a system update today. I can no longer see adb in my device manager on the laptop. That's where I updated driver's last night after install. There's also no 'other devices' there as was originally after installing adb last night. Fastboot won't find my device now. The adb command will send me from booted to fastboot mode, but the fastboot command to install the logo results in 'waiting for device'. 'Fastboot devices' command would show my phone last night, now there is no result. I reinstalled adb again just now using the 15 second install thread, but it still doesn't show in my laptop device manager as it did last night. I am running as administrator. Any help is greatly appreciated. I see the google driver's package installed with adb last night in the programs and features screen, but nothing for adb despite reinstalling just now.

See step #23. When you install ADB it creates a folder on your C drive called Android SDK (or sometimes just Android). And in THAT folder are many sub-folder. The one you want is "platform-tools". THAT is where you drop the stuff you want to flash and where you will shift+right click to create the command window.

Your other questions I don't know. Maybe reinstall and use "install as administrator"?

 

[jdl512]

See step #23. When you install ADB it creates a folder on your C drive called Android SDK (or sometimes just Android). And in THAT folder are many sub-folder. The one you want is "platform-tools". THAT is where you drop the stuff you want to flash and where you will shift+right click to create the command window.

Your other questions I don't know. Maybe reinstall and use "install as administrator"?

Thank you very much. I have been running as admin and reinstalled. Your response is very helpful as it seems to confirm that my install isn't complete. I do not have and Android folder on my c drive so I do not have a platform tools folder. I only have an adb folder on the c drive and it contains the adb and fastboot exe's. Maybe I should try another install option instead of using the 15 second adb install thread.

 

[jdl512]

Thank you very much. I have been running as admin and reinstalled. Your response is very helpful as it seems to confirm that my install isn't complete. I do not have and Android folder on my c drive so I do not have a platform tools folder. I only have an adb folder on the c drive and it contains the adb and fastboot exe's. Maybe I should try another install option instead of using the 15 second adb install thread.

I gave up on my windows 10 laptop and tried on XP which worked nicely. installing the moto device manager for my turbo was key in order for the XP device mgr to see my phone as an android device under 'other devices' before updating the adb drivers. That did not work on windows 10 for me.
Also, it seems the 15 second install thread option does not create the sub folders with platform tools subfolder, etc. It only installs 4 files.....the adb and fastboot exe's and two dll's into a folder named 'adb' in the C root. I was able to replace the bootloader unlock msg by placing the bin file in that folder and opening the command prompt from there by placing cursor in open space and shift>rt click> open command prompt here.

Now I have decided to keep the phone after upgrading to pixel so I want to add the unlock message back and use the phone to learn with as a backup. Who knows when we will be able to unlock Pixel so I don't want to be left out of the fun in the meantime. Thanks again.

---------- Post added at 01:38 AM ---------- Previous post was at 01:19 AM ----------

on fastboot write:

fastboot erase clogo

and you will have the warning back

Hello. I tried the erase command above and it did not work on my Verizon turbo. Earlier today I removed the message and returned to the black moto image prior to boot animation using instructions in another thread (used logofixed.bin in fastboot). I am still seeing the moto image after booting despite getting a positive result in cmd prompt after running the erase command.

erasing 'clogo'...
OKAY [ 0.062s ]
finished. total time : 0.062s

I have decided to keep the phone and would like to return to the unlocked message. Not that important I know but it would be a good learning opportunity as I am new to ADB/fastboot. I appreciate any more input you may have.

 

[gps4213]

I actually like the warning message. It reminds me that "Now I am in control of the phone and not the other way around.". I left it on my last droid and probably will with my XT1254 as well.

I do want to thank the OP as the new logo does look great even though I will not be using it.

And for the S&G factor I have a question. What size does the picture need to be for a boot logo? It has probably been asked in these forums a few times but for the benefit of future guests it might be relevant in this thread as well. As well as How to make a .bin file out of a picture file.

Thanks.
Sent from my low budget 720BE running Zorin

 

[ChazzMatt]

Here's some custom boot logos from my Moto Maxx/Moto Turbo guide. Works on all Quarks -- Droid Turbo/Moto Turbo/Moto Maxx. Your choice of colors of the Motorola M logo. Very classy.

Install either via ADB (fastboot) or TWRP. Both choices are offered.

____________
BOOT LOGOS

You can just reflash your choice of boot logo to replace the unlocked warning screen. It's just a static image Motorola insists on showing you that your bootloader is unlocked.

I know, I UNLOCKED it on purpose!

Here's boot logos (not to be confused with boot animation -- the boot logo is what you see before the boot animation starts) you can flash with ADB. Various colors of the Motorola M logo.

Remove annoying bootloader unlocked warning

* ADB FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68538894&postcount=2

And here's the same boot logos you can flash with TWRP:

* TWRP FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68579272&postcount=5

Works for all Quarks (XT1254/XT1250/XT1225).


* Black and White

* Black and Teal

*White and Teal

* Black and Red

(The last three with color are custom graphics made by @fenix3nk0r3 . I am using the black and teal on my daily phone.)