FORUMS

How to Relock the bootloader on moto z xt-1650-03

28 posts
Thanks Meter: 4
 
By saifprvz, Junior Member on 27th July 2018, 01:26 PM
Post Reply Email Thread
Hi All,

NOTE: I am not responsible for anything that might happen to your device while doing this. (it most likely is not).
I have made this tutorial just to help other people I noticed there was no step by step tutorial on how to Relock the bootloader on moto z xt-1650-03 so I have decided to make a guide explaining How to Relock the bootloader on moto z xt-1650-03. Submit a Thanks to lesbianu, he helped me out figuring this...

1 - Download GRIFFIN_OPLS27.76-51-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Rom ( I used https://androidfilehost.com/?fid=5862345805528054929 )
2 - Download the Android SDK Platform-Tools ( I used the latest from Google: https://developer.android.com/studio...platform-tools )
3 - Extract the Android SDK Platform-Tools and within that same folder also extract the ROM
4 – On the address bar. Type CMD and Hit Enter.
5 – To Check device connectivity. Type “adb devices”
6 – Boot into bootloader mode. type “adb reboot bootloader”
7 – Ones you are into bootloader mode. Check the Device connectivity Again. Type “fastboot devices”
As soon as you press enter key, you’ll see a message saying ‘List of devices attached’ along with some random numbers. This will confirm that your Moto Z has properly connected to your computer.
8 - Run the first set of commands i.e.
Code:
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 system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
9 – Once the Flashing is Done. Directly press the power button to boot the device. let the device boots up completely.
10 – complete the first time phone configuration process. (Make sure Internet is working on your device)
11 - after completing the setup go to the setting - system - about phone - tap on the built no several time to unlock the developer options.
12 – Go to the developer option and click on "OEM unlocking" and “Allow USB debugging”
13 – Don’t reboot your Device. And Connect your Phone to PC.
14 - Again open the same folder, where you extracted your ROM and SDK tools and within that same folder again open a command prompet and type “ adb reboot bootloader “
ones again you will come back to the bootloader mode.
15 - after the phone is back to bootloader mode, run the second set of commands I.e.
Code:
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 system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash boot boot.img
fastboot oem lock
14 – After the last set of commands if everything goes well then Congrats you just relocked your Bootloader... Successfully....
30th July 2018, 11:51 PM |#2  
Senior Member
Flag Santiago
Thanks Meter: 51
 
More
as a question, what version of bootloader do you have? or doesn't care to the process?
31st July 2018, 08:26 AM |#3  
YamazakiRobert's Avatar
Senior Member
Thanks Meter: 50
 
More
Quote:
Originally Posted by eLaDiio

as a question, what version of bootloader do you have? or doesn't care to the process?

the first script updates the bootloader
The Following User Says Thank You to YamazakiRobert For This Useful Post: [ View ] Gift YamazakiRobert Ad-Free
31st July 2018, 10:54 AM |#4  
Junior Member
Thanks Meter: 0
 
More
Hello,
I need some help.
After following your guide it starts the ROM fine.
After a restart of the phone i get stuck in "no command" screen. (wipe don´t help in this case)

Starting thru the fastboot "start" will boot the phone correctly!

After that I tried to get back to LinageOS, now same problem, always boots to TRWP after installing ROM, starting correctly und restart phone.

May be this is ab Problem with the bootloader?

(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB TOSHIBA THGBF7G8K4LBATRB FV=0300
(bootloader) ram: 4GB SKHYNIX LP4 DIE=8Gb M5=06 M6=03 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: EAE795CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-24-2017
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:8.0.0/OPL
(bootloader) ro.build.fingerprint[1]: S27.76-51-5/6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.6.griffin.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.29.01R SRD
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gbf602b0 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue May 29 07:26:28 CDT 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.03-0-g722a114
(bootloader) tz.git: git=d9d553d-dirty
(bootloader) hyp.git: git=d9d553d-dirty
(bootloader) devcfg.git: git=d9d553d-dirty
(bootloader) keymaster.git: git=d9d553d-dirty
(bootloader) cmnlib.git: git=d9d553d-dirty
(bootloader) cmnlib64.git: git=d9d553d-dirty
(bootloader) prov.git: git=d9d553d-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu


I think here is the Problem: Reboot mode set to fastboot

fastboot oem fb_mode_clear doesn´t change it.

Any suggestions?
31st July 2018, 01:33 PM |#5  
Junior Member
Thanks Meter: 1
 
More
Its methods working after update ota to may security patch?
1st August 2018, 03:03 PM |#6  
OP Junior Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by Ceptoz

Its methods working after update ota to may security patch?

as YamazakiRobert told, the first script updates the bootloader. so it desent matter which version of bootloader you have. The rom is having the latest version of the Bootloader, so if you are on the old version of bootloader, this will update your bootloader version and then you can relock your bootloader with the second sets of commands.
1st August 2018, 03:08 PM |#7  
OP Junior Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by dorscht

Hello,
I need some help.
After following your guide it starts the ROM fine.
After a restart of the phone i get stuck in "no command" screen. (wipe don´t help in this case)

Starting thru the fastboot "start" will boot the phone correctly!

After that I tried to get back to LinageOS, now same problem, always boots to TRWP after installing ROM, starting correctly und restart phone.

May be this is ab Problem with the bootloader?

(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB TOSHIBA THGBF7G8K4LBATRB FV=0300
(bootloader) ram: 4GB SKHYNIX LP4 DIE=8Gb M5=06 M6=03 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: EAE795CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-24-2017
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:8.0.0/OPL
(bootloader) ro.build.fingerprint[1]: S27.76-51-5/6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.211.6.griffin.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.29.01R SRD
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gbf602b0 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue May 29 07:26:28 CDT 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.03-0-g722a114
(bootloader) tz.git: git=d9d553d-dirty
(bootloader) hyp.git: git=d9d553d-dirty
(bootloader) devcfg.git: git=d9d553d-dirty
(bootloader) keymaster.git: git=d9d553d-dirty
(bootloader) cmnlib.git: git=d9d553d-dirty
(bootloader) cmnlib64.git: git=d9d553d-dirty
(bootloader) prov.git: git=d9d553d-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 1/1
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu


I think here is the Problem: Reboot mode set to fastboot

fastboot oem fb_mode_clear doesn´t change it.

Any suggestions?

what does it shows you on -

fastboot oem fb_mode_clear
and
fastboot oem fb_mode_set
2nd August 2018, 07:35 AM |#8  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by saifprvz

what does it shows you on -

fastboot oem fb_mode_clear
and
fastboot oem fb_mode_set

C:\ADB\tools>fastboot oem fb_mode_set
OKAY [ 0.005s]
Finished. Total time: 0.007s

C:\ADB\tools>fastboot oem fb_mode_clear
OKAY [ 0.004s]
Finished. Total time: 0.006s

and after reboot and check with "fastboot getvar all" still:
(bootloader) reason: Reboot mode set to fastboot
22nd August 2018, 11:42 AM |#9  
Senior Member
Thanks Meter: 9
 
More
Guys for me everything worked but when i try OTA update it doesnt install it says error when trying to install it any help pls
22nd August 2018, 05:55 PM |#10  
lesbianu's Avatar
Member
Flag Bucharest
Thanks Meter: 65
 
More
I relocked the bootloader before the OP opened this thread: https://forum.xda-developers.com/sho...&postcount=110

The July OTA installed just fine on mine!
Try to sideload the OTA zip using a PC... If you are still receiving an error, the only way I can see it: is to unlock the bootloader again and then re-locking it back. If all goes well, you can re-test the July OTA. Good luck!
Attached Thumbnails
Click image for larger version

Name:	IMG-20180815-WA0022.jpg
Views:	342
Size:	76.6 KB
ID:	4578239   Click image for larger version

Name:	IMG-20180815-WA0021.jpg
Views:	338
Size:	58.0 KB
ID:	4578240   Click image for larger version

Name:	IMG-20180815-WA0020.jpg
Views:	330
Size:	82.1 KB
ID:	4578241   Click image for larger version

Name:	IMG-20180815-WA0019.jpg
Views:	298
Size:	57.2 KB
ID:	4578242  
The Following User Says Thank You to lesbianu For This Useful Post: [ View ] Gift lesbianu Ad-Free
22nd August 2018, 07:28 PM |#11  
Senior Member
Thanks Meter: 9
 
More
Quote:
Originally Posted by lesbianu

I relocked the bootloader before the OP opened this thread: https://forum.xda-developers.com/sho...&postcount=110

The July OTA installed just fine on mine!
Try to sideload the OTA zip using a PC... If you are still receiving an error, the only way I can see it: is to unlock the bootloader again and then re-locking it back. If all goes well, you can re-test the July OTA. Good luck!

I dont really know what sideload means and how it works can u give me detailed instructions please
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes