Related
Hello Guys,
I have sucessfully managed to remove the UNLOCKED BOOTLOADER WARNING message from phone boot.
4.4 image is slightly different from 4.2.2 image, is has the same Green M Logo, but now it says "A Google company"
4.4.3 image says "Powered by Android" instead of "A Google company
You just need to:
Download and Unzip the attachment and run:
Code:
fastboot flash logo logo_nowarning-4.4.bin
(This will not bring your warranty back, tho)
Enjoy!
EDIT:
Updated with 4.4.3 image! Unzip and run:
fastboot flash logo logo.bin
Helvio88 said:
Hello Guys,
I have sucessfully managed to remove the UNLOCKED BOOTLOADER WARNING message from phone boot.
4.4 image is slightly different from 4.2.2 image, is has the same Green M Logo, but now it says "A Google company"
You just need to:
Download and Unzip the attachment and run:
Code:
fastboot flash logo logo_nowarning-4.4.bin
(This will not bring your warranty back, tho)
Enjoy!
Click to expand...
Click to collapse
FDP! You are the man!
Helvio88 said:
(This will not bring your warranty back, tho)
Click to expand...
Click to collapse
Nope, because Motorola already did.
http://motorola-blog.blogspot.com/2013/11/you-asked-we-listened-announcing.html?m=1
That's for the Developer Edition device, so you still have voided your warranty if you have unlocked a device which is not a developer one That's my case! But thanks for pointing it out, great news!
This doesn't work on droid maxx DE. Thought these phones were the same unless they changed something in the KK boot loader.
Sent from my XT1080 using Tapatalk
obvious question here but this doesn't work on 4.2.2 does it?
joda08 said:
obvious question here but this doesn't work on 4.2.2 does it?
Click to expand...
Click to collapse
pretty sure it does. look in the themes section. you could replace it with whatever image you want essentially.
Is it the same command for 4.2.2? If not can you give it to me, want to rid my phone of this....thanks..
Okay it works, but sort of a noob with adb, what would I use to put any image on? Now it just a garble of colours etc...so any help would be most appreciated on what to label the image to flash properly or where do I drop the new image!!
joda08 said:
obvious question here but this doesn't work on 4.2.2 does it?
Click to expand...
Click to collapse
It should work, it's just an image
Helvio88 said:
It should work, it's just an image
Click to expand...
Click to collapse
Flashed it a second time, it takes away the boot loader image, but image is a bunch of lines......where is the image stored in the root? That is most likely where I can re-place the image????
caanda45 said:
Is it the same command for 4.2.2? If not can you give it to me, want to rid my phone of this....thanks..
Okay it works, but sort of a noob with adb, what would I use to put any image on? Now it just a garble of colours etc...so any help would be most appreciated on what to label the image to flash properly or where do I drop the new image!!
Click to expand...
Click to collapse
You have probably flashed the ZIP instead of what's inside. Make sure to unzip the package before flashing (with fastboot, not adb)
Helvio88 said:
You have probably flashed the ZIP instead of what's inside. Make sure to unzip the package before flashing (with fastboot, not adb)
Click to expand...
Click to collapse
LOL well another noob question, I did unzip the file, so how do I flash with fastboot? Do I not use android-sdk tools and a command prompt and fastboot flash logo logo_nowarning-4.4.bin? I gather it is how I am attempting to flash...
It would be great if you could create one for 4.2.2.....at this point I would say it sort of works on 4.2.2.
caanda45 said:
LOL well another noob question, I did unzip the file, so how do I flash with fastboot? Do I not use android-sdk tools and a command prompt and fastboot flash logo logo_nowarning-4.4.bin? I gather it is how I am attempting to flash...
It would be great if you could create one for 4.2.2.....at this point I would say it sort of works on 4.2.2.
Click to expand...
Click to collapse
ok, then probably it's not compatible with 4.2.2, there's another thread for that. This is the direct link to the nowarning 4.2.2 logo, please try it:
http://d-h.st/3Z7
Okay thanks that worked......
Here is a thread for 4.2.2....http://forum.xda-developers.com/showthread.php?p=45439918
and the command is
fastboot flash logo (logo file name).bin
Hope this helps everyone...OP I suggest you put a link in OP, thanks for all your help.....
Work on Moto X XT1058 (Brazil version) Android 4.4 ? without problem ?
caanda45 said:
Okay thanks that worked......
Here is a thread for 4.2.2....http://forum.xda-developers.com/showthread.php?p=45439918
and the command is
fastboot flash logo (logo file name).bin
Hope this helps everyone...OP I suggest you put a link in OP, thanks for all your help.....
Click to expand...
Click to collapse
Just curious about the difference between mfastboot (motorola fastboot) and fastboot as it pertains to Motorola phones. I know I had to use mfastboot for flashing TWRP recovery and getting root with Supersu after unlocking my T-Mobile Moto x. But regular fastboot works fine with flashing the OP file? Would mfastboot work as well?
Nixal said:
Work on Moto X XT1058 (Brazil version) Android 4.4 ? without problem ?
Click to expand...
Click to collapse
Yes.
Enviado de meu XT1058 usando Tapatalk
MaKTaiL said:
Yes.
Enviado de meu XT1058 usando Tapatalk
Click to expand...
Click to collapse
Ty Man!
Groid said:
Just curious about the difference between mfastboot (motorola fastboot) and fastboot as it pertains to Motorola phones. I know I had to use mfastboot for flashing TWRP recovery and getting root with Supersu after unlocking my T-Mobile Moto x. But regular fastboot works fine with flashing the OP file? Would mfastboot work as well?
Click to expand...
Click to collapse
Fastboot is used for unlocked boot loaders and cfastboot is used for locked boot loaders. Did you mean c not m?
caanda45 said:
Fastboot is used for unlocked boot loaders and cfastboot is used for locked boot loaders. Did you mean c not m?
Click to expand...
Click to collapse
No, mfastboot is Motorola's modified fastboot utility that supposedly works better on Motorola devices. I think it has to be used for flashing .img files due to a size discrepancy in one of the partitions. I was just wondering for regular kinds of flashing zips if it matters which fastboot utility is used.
4.4.4 is now Pre-installed on Moto G, Now you can flash full stock 4.4.4. not required to first falling back to 4.4.2 and then updating the system to 4.4.4.
Code:
Model number: Moto G
Android version: 4.4.4
Baseband version: MSM8626BP_1032.355.66.00R
Kernel version: 3.4.42-gb2383d6 [email protected] #1 Fri Jun 20 00:05:34 CDT 2014
System version: 210.12.40.falcon_umtsds.AsiaRetail.en.03.zip
Build number: KXB21.14-L1.40
Instructions 4.4.4:
1. Download the Package and Extract it to a folder.
2. Download mfastboot-v2 and Extract it into the same folder. Download: http://goo.gl/i8Tsy9
3. Reboot the phone into Bootloader.
4. Run Following commands from the Command Prompt after cd-ing to the folder, one by one.
If you do not wish to lock bootloader skip 4.1 and 4.3.
4.1
Code:
mfastboot.exe oem lock begin
4.2
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
4.3
Code:
mfastboot.exe oem lock
4.4
Code:
mfastboot.exe reboot
Downloads 4.4.4:
1.http://goo.gl/gXxeM6
or
2.http://goo.gl/JGfUk0
or
3.http://goo.gl/KB0lbQ by @jri3
Lets start by Thanking a few people:
@deej_roamer [For Guidance]
@jri3 [For Mirror]
@archies20 [its me]
Anyone willing to mirror the link is welcome!
If it helped, Hit thanks
I create a mirror on dev-host
Code:
http://d-h.st/oEg
jri3 said:
I create a mirror on dev-host
Code:
http://d-h.st/oEg
Click to expand...
Click to collapse
Thanks!! Adding your mirror.
Thank you so much, you save my friend's Moto-G life!!!
omegahanggara said:
Thank you so much, you save my friend's Moto-G life!!!
Click to expand...
Click to collapse
Ohh yeah :good: Its my pleasure
This looks like a direct lift from this thread http://forum.xda-developers.com/showthread.php?t=2700502 . Atleast change the wordings or credit the source.
I guess 4.4.4 link is not available:cyclops: on that forum that's all matter....don't comment anything just for fun
these are standard procedure....
ajeetone said:
I guess 4.4.4 link is not available:cyclops: on that forum that's all matter....don't comment anything just for fun
these are standard procedure....
Click to expand...
Click to collapse
Ya its not available on that thread thats why i create this thread. :victory:
unknownemous said:
This looks like a direct lift from this thread http://forum.xda-developers.com/showthread.php?t=2700502 . Atleast change the wordings or credit the source.
Click to expand...
Click to collapse
Thanks For Your Suggestion. :good:
I tried to relock my moto g (indian dual sim) using these instructions and after relock the boot logo still shows up as bootloader unlocked warning.
any idea on how to get rid of this bootlogo?
mla123 said:
I tried to relock my moto g (indian dual sim) using these instructions and after relock the boot logo still shows up as bootloader unlocked warning.
any idea on how to get rid of this bootlogo?
Click to expand...
Click to collapse
Check in fastboot if your device is locked. If it is then flash original logo.bin file to remove warning message.
unknownemous said:
Check in fastboot if your device is locked. If it is then flash original logo.bin file to remove warning message.
Click to expand...
Click to collapse
The device status is now locked. I tried to flash the logo.bin that came inside 4.4.4 zip, but the warning remains..
is there any other logo.bin file that needs to be flashed to remove the warning. If yes then where can I find it?
also since the device is now locked won't there be any problem flashing modified .bin files?
mla123 said:
The device status is now locked. I tried to flash the logo.bin that came inside 4.4.4 zip, but the warning remains..
is there any other logo.bin file that needs to be flashed to remove the warning. If yes then where can I find it?
also since the device is now locked won't there be any problem flashing modified .bin files?
Click to expand...
Click to collapse
I'm on phone currently. Search moto g forums for "remove boot loader warning screen". There is no problem flashing the file.
mla123 said:
I tried to relock my moto g (indian dual sim) using these instructions and after relock the boot logo still shows up as bootloader unlocked warning.
any idea on how to get rid of this bootlogo?
Click to expand...
Click to collapse
You flash full stock firmware?? or only use relock command??
mla123 said:
I tried to relock my moto g (indian dual sim) using these instructions and after relock the boot logo still shows up as bootloader unlocked warning.
any idea on how to get rid of this bootlogo?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2548530
archies20 said:
http://forum.xda-developers.com/showthread.php?t=2548530
Click to expand...
Click to collapse
that worked.. :good:
Greate :good:
My baseband version is MSM8626BP_1032.390.81.01P, ROW_DSDS_CUST
Will this procedure still work?
soumitro316 said:
My baseband version is MSM8626BP_1032.390.81.01P, ROW_DSDS_CUST
Will this procedure still work?
Click to expand...
Click to collapse
yup it works
Tnks for the share, downloading Rite now...
Sent from my Moto G XT1033 using Tapatalk
This is a guide that is strictly for those who are as impatient as I am to get Lollipop on their Moto G (2014). I know there are several guides for folks in the US, and other countries as well, but currently there is no OTA for Canada yet. We are literally left out in the cold. So, I thought I would put a collaborative guide together so the Canadians can enjoy some 5.0, too!
First and foremost, if you F up your phone, that's on you. This will void your warranty, and I am in no way responsible for any stupidity you conjure up during the process.
I have only tested this on the XT1064, which is the single SIM US/Canada model.
The issue when trying to simply follow the upgrade guide for the XT1064 is that the OTA file looks for a 4.4.4 variant of Android that needs to be the same region as where the OTA came from. If you try to install it on the Canadian versions, you will get an error. So, here goes:
1. Unlock your bootloader. Follow this wonderful guide: http://forum.xda-developers.com/mot...wip-unlock-bootloader-moto-g-2nd-gen-t2875728
2. Download the US version of 4.4.4, it can be found here: http://www.filefactory.com/file/2ygnt0x45vcr/RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
3. Extract the above file to the same location you installed Minimal ADB in the first step (C:\Program Files(x86)\Minimal ADB and Fastboot)
4. Turn your phone off and disconnect it from the computer. Press and hold the volume down (-) button and power button to get into Fastboot mode. Connect your phone to the computer.
5. Run Minimal ADB and run these commands:
PHP:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot reboot
I removed the modem commands on purpose, and I will explain why later.
6. Once the phone has rebooted, plug it in to the computer and follow this guide: http://forum.xda-developers.com/moto-g-2014/development/lollipop-moto-g-2014-xt1064-t2937361
You should now have Lollipop on your Canadian XT1064!
If you have issues with the WiFi or cellular, you may have to flash the modem commands again from the old file. I had to download the original Canadian ROM (http://www.filefactory.com/file/78znv8hx0tvt/RETCA_XT1064_4.4.4_KXB21.85-16_cid14_CFC.xml.zip) and using Fastboot flash the following:
PHP:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
After that I had no issues and everything seems to be working as it should. You can relock your bootloader afterwards if you like as well.
Thanks to the other contributors above, I was simply trying to put a quick guide together for us Canadian folks who wish to get Lollipop, too!
Cheers!
This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?
This worked for me! Thanks for the awesome tutorial!
brianshayne said:
This is great - although I think I'm still "out in the cold." I have 11.24 and couldn't flash the above due to "downgrading." Unless I'm missing something... Any ideas?
Click to expand...
Click to collapse
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?
NexusChrist said:
At which part do you get an error? Are you trying to use a script to flash, or are you doing exactly step by step like mentioned above? I had the latest of the late on my Moto G 2014, so I know that these steps work on it.
Is your bootloader unlocked as mentioned above?
Click to expand...
Click to collapse
Yeah - I'm not sure what the problem was - originally it wouldn't take the US ROM due to a downgrade error. Tried it again, after a factory reset and for some reason it went through. Flashing Lollipop and the modem after was no issue at all - so good to go now. It's beautiful.
Thanks for the follow-up.
AKA: I should have just ignored downgrade error + HAB fail on phone, the first time around
I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help
ramzilla136 said:
I am getting hab check failed for boot when i use the command " fastboot flash boot boot.img "
please help
Click to expand...
Click to collapse
Disregard the error and move on to the next command. You are going to get a few errors. Don't worry.
installing update
verifying current system
/system/app/3c_main.apl has unexpected contents
installation aborted
this is after i run the commands and upload from sd card...
followed your commands and tried few fresh zips
can you please help, it won't let me install the lollipop file
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Is this procedure better? Any enhancement? Thanks.
Botsok said:
Is this procedure better? Any enhancement? Thanks.
Click to expand...
Click to collapse
This one just avoid you to flash USA KitKat and then Lollipop. This one goes directly to Lollipop.
Doesn't flash Modem/Radio from USA Lollipop because doesn't work on Canadian models, at least didn't work with WIND Mobile model.
WIND canada moto G XT1064 lollipop
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
https://mega.co.nz/#!dk430ZBZ!diHa6V-rcidHFc3niGjshk-2A9ELbqZtCnb63pFK010
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
TiGuy82 said:
Another way:
Go to this link, XT1064 > Lollipop, download the file and extract it.
And follow the same idea of OP but with few changes:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Just a super-dooper-uber Thanks To NexusChrist!
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post
UnderAppreciatedDev said:
Who ever you are, I tried to follow your system. it didn't work for me, infact I lost wifi connection, but anyways what I did was I used another script for this (http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167) And this worked, but now I lost Cellular Service....Big problem eh? Well no more, thanks to you. I downloaded the Canadian rom, and just to be more specific (cause it was kinda vague in the tutorial, (Extract the files again to the Mininal ADB fastboot file location the whole c drive thing yenno?)) And I ran that php and BAM thank you so much I was worried out of my MIND that I f'ed up my phone somehow. Foreal, bless your soul....or your XT1064?
No XT1064s were hurt in the making of this post
Click to expand...
Click to collapse
That happened because you flash the modem from Lollipop... Just flash the modem in OP and you will be ok.
spiritflare said:
Thanks very much for posting this. and thanks for posting the link for 5.02 from MEGA which is a lot faster than filefactory!
I've attached a link to the original Wind 4.4 modem files in case someone's modem doesn't work afterwards, if they followed the top post original instructions and accidentally flashed the US KitKat 4.4 modems.. instead of downloading that huge file from filefactory.com (extremely slow site), the link has just the 2 files (22MB).
Also may be worth mentioning to ignore the "hab check failed" messages when flashing lollipop. (I was using mfastboot)
Click to expand...
Click to collapse
Just a tad bit curious I also have a Wind Mobile Moto G2 and i'm just wondering how you unlocked the bootloader in the first place. If you could please share the process on how you did it that would be great.
Anyone know how we can get the LP bootloader on the Canadian version?
I'd like to be able to update my CM12.
Thanks!
Awesome
I'm on Bell &
everything is working 100% radio/wifi/bluetooth all good
Thanks
This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.
Kewjoe said:
This is a great guide. But I'm wondering if we've been given any explanation on why Canadian Moto G's aren't getting OTA updates? It's April and my Moto G is saying up to date with 4.4.4. It's from wind if that matters.
I understand we can do this work around. I'm just trying to understand why we're not getting updates.
Click to expand...
Click to collapse
Your carrier is most likely the reason since they have the final say on updates.
Tel864 said:
Your carrier is most likely the reason since they have the final say on updates.
Click to expand...
Click to collapse
But what about the people that bought their phones from Staples. It's unlocked and not associated to any carrier. They are directly under Motorola and still no update at all. Phone are getting 5.1 update already, but we're still at 4.4.4
What's so different in the Canadian market from the US one that the update can't come fast? Specially if the phone is not associated to a carrier and the update should come directly from Motorola
This method is only works, if you are in Oreo
unlocked bootloader, and use custom rom,
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
How it works.
YOU NEED TO BE ON A CUSTOM ROM TO RELOCK THE BOOTLOADER!
1 - Download Stock ROM in the first post down below
2 - install adb minimal fastboot
3 - after install adb minimal fastboot, go to the install location and paste all the files there
5 - Copy all commands how is in this site and past it on the cmd screen and wait. (you need to press enter for the last command)
Stock Oreo Signed ROM
If u are in June bootloader Kindly use June Security Patch rom, otherwise, phone should be Brick
June Security Patch
Commands
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash boot boot.img
fastboot oem lock
Now youre phone will reboot, and your phone is locked again.
I'm using this ROM here:
[ROM][Stock+] [7.1.1] Dec. Patch NPNS26.118-22-2-12 Prerooted
https://forum.xda-developers.com/moto-z-play/development/rom-nov-patch-npns26-118-22-2-8-t3717037
Do I need to perform any procedures before starting this installation?
I think fast boot erase modemmst 1 & 2 may get a result of IMEI 0 error.
talktosam said:
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
Click to expand...
Click to collapse
talktosam said:
So how does this differ from the method below that was posted here months ago by someone else on doing the same thing? Looks like you copied and pasted....
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Click to expand...
Click to collapse
Jimi Mack said:
talktosam said:
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
Click to expand...
Click to collapse
talktosam said:
So how does this differ from the method below that was posted here months ago by someone else on doing the same thing? Looks like you copied and pasted....
Yes, text is copied, but rom is different Oreo... procedure is same...
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Click to expand...
Click to collapse
Click to expand...
Click to collapse
talktosam said:
Thanks for clearing that up. So the older was to fully restore to Nougat and yours it to restore to Oreo. So being I never updated to Oreo I should restore with the old file, as I am sure yours would cause issues being I never updated to Oreo. You should clearly document that in the thread as well and not just the Title as well if this is the case. Just because most people do not thoroughly read but skim quickly and then jump without looking.
Click to expand...
Click to collapse
Jimi Mack said:
talktosam said:
Thanks for clearing that up. So the older was to fully restore to Nougat and yours it to restore to Oreo. So being I never updated to Oreo I should restore with the old file, as I am sure yours would cause issues being I never updated to Oreo. You should clearly document that in the thread as well and not just the Title as well if this is the case. Just because most people do not thoroughly read but skim quickly and then jump without looking.
Click to expand...
Click to collapse
Yes, if you are in 0xC182 Oreo bootloader, in title i mentioned its works only if u are in oreo bootloader unlocked
Click to expand...
Click to collapse
Can I use this tutorial if I have 0xC114 bootloader (february patch)???
gercdgcat said:
Can I use this tutorial if I have 0xC114 bootloader (february patch)???
Click to expand...
Click to collapse
Yes, but u are in custom rom, u can,
I was in AOSP 8.1 with Oreo bootloader (I had stock oreo before installing the ROM) and just did this procedure, everything went fine ! IMEI is safe and system works as intended, thank you !
If I have the bootloader blocked and I want to update to OREO with your tutorial which commands would I have to skip?
Dude you are a lifesaver..
---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------
Mario3DS said:
I was in AOSP 8.1 with Oreo bootloader (I had stock oreo before installing the ROM) and just did this procedure, everything went fine ! IMEI is safe and system works as intended, thank you !
Click to expand...
Click to collapse
I am in the exact same situation as you. I will give this a try and report
djdelarosa25 said:
Dude you are a lifesaver..
---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------
I am in the exact same situation as you. I will give this a try and report
Click to expand...
Click to collapse
Just do exactly what OP says and everything will be fine, I even recovered my Software Channel (attmx) somehow
oh and btw, you can "fix" the navbar bug in stock Oreo changing the theme with Custom Navigation Bar (it's an app)
I just did it and it fixed it completely
Mario3DS said:
Just do exactly what OP says and everything will be fine, I even recovered my Software Channel (attmx) somehow
oh and btw, you can "fix" the navbar bug in stock Oreo changing the theme with Custom Navigation Bar (it's an app)
I just did it and it fixed it completely
Click to expand...
Click to collapse
Your software channel isn't supposed to change anyway
Safety net failed, help
CTS profile match only failed. Is it because of unlocked bootloader?
The bootloader unlocked screen doesn't seem to want to go away
EDIT: My bootloader is still unlocked.
EDIT: Fixed. It wasn't mentioned that you need to enable OEM unlocking in Developer options, noobs like me might get confused. Lucky I got that sorted out
djdelarosa25 said:
The bootloader unlocked screen doesn't seem to want to go away
EDIT: My bootloader is still unlocked.
EDIT: Fixed. It wasn't mentioned that you need to enable OEM unlocking in Developer options, noobs like me might get confused. Lucky I got that sorted out
Click to expand...
Click to collapse
So... Now are you in Oreo stock with locked bootloader? In boot image only shows motorola logo? Nothing of bad key or any notification?
gercdgcat said:
So... Now are you in Oreo stock with locked bootloader? In boot image only shows motorola logo? Nothing of bad key or any notification?
Click to expand...
Click to collapse
Yup, 100% stock. No more bootloader warning message. The guide did not mention that within the custom ROM that you are using, you must have OEM Unlocking under Developer options turned on before you flash the commands.
djdelarosa25 said:
Yup, 100% stock. No more bootloader warning message. The guide did not mention that within the custom ROM that you are using, you must have OEM Unlocking under Developer options turned on before you flash the commands.
Click to expand...
Click to collapse
I think OEM Unlocking only exists in the stock ROM. Regardless of whether you're on a stock ROM already or are flashing the stock ROM, as you mentioned, OEM unlocking must be turned on for the OEM locking commands to work.
Of course, with re-locking your bootloader, it's up to you if you wish to keep OEM Unlocking enabled or disabled afterwards. If you disable it, your device will not be unlockable until you boot into system, which can be more secure but if you have any boot issues, then troubleshooting is a lot more difficult, plus you have no warranty. If you leave OEM unlocking on, then you could unlock your bootloader, but then so can anyone else with physical access to your device.
echo92 said:
I think OEM Unlocking only exists in the stock ROM. Regardless of whether you're on a stock ROM already or are flashing the stock ROM, as you mentioned, OEM unlocking must be turned on for the OEM locking commands to work.
Of course, with re-locking your bootloader, it's up to you if you wish to keep OEM Unlocking enabled or disabled afterwards. If you disable it, your device will not be unlockable until you boot into system, which can be more secure but if you have any boot issues, then troubleshooting is a lot more difficult, plus you have no warranty. If you leave OEM unlocking on, then you could unlock your bootloader, but then so can anyone else with physical access to your device.
Click to expand...
Click to collapse
OEM unlocking also exists in custom ROMs. The reason that relocking your bootloader is not possible with the stock ROM is that the option is greyed out if you have your bootloader unlocked, thus making the bootloader lock commands not work. With a custom ROM, I was able to toggle OEM unlocking on, even when my bootloader was already unlocked. This allowed the bootloader lock commands to work and make the warning message disappear.
someone knows how to have the factory logo.bin after unlocking the bootloader
..
sun75 said:
In /product/etc/media there is a file called "bootanimation.zip" that contains the boot animation (System part, not the Boot one).
Click to expand...
Click to collapse
but when you unlock the bootloader it changes the logo.bin and I want the stock to that I mean
..
sun75 said:
Ok, so you refer to the "bootloader" logo. From what I've read on other threads every tries to change that logo or parts of the Bootloader code to do anything else, ends up with a bricked device! So the actual situation is: you have to see that ugly BL screen remembering you that your phone is "insecure". You know! But better that screen but unlocked, that a beautiful logo but locked and a dumb device!
At least, for now!
Click to expand...
Click to collapse
You can do the logo.bin factory, as do the Motorola