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

Search This thread
By:
Advanced…
S

saifprvz

Member
Nov 14, 2012
29
4
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....
 
Last edited:
D

dorscht

New member
Jul 31, 2018
2
0
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]: soncm@ilclbld53) (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?
 
Last edited:
S

saifprvz

Member
Nov 14, 2012
29
4
Ceptoz said:
Its methods working after update ota to may security patch?
Click to expand...
Click to collapse

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.
 
S

saifprvz

Member
Nov 14, 2012
29
4
dorscht said:
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]: soncm@ilclbld53) (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?
Click to expand...
Click to collapse

what does it shows you on -

fastboot oem fb_mode_clear
and
fastboot oem fb_mode_set
 
D

dorscht

New member
Jul 31, 2018
2
0
saifprvz said:
what does it shows you on -

fastboot oem fb_mode_clear
and
fastboot oem fb_mode_set
Click to expand...
Click to collapse

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
 
P

Pathera

Senior Member
Dec 31, 2012
151
9
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
 
lesbianu

lesbianu

Senior Member
Jul 16, 2013
94
65
Bucharest
I relocked the bootloader before the OP opened this thread: https://xdaforums.com/showpost.php?p=77177509&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! :good:
 

Attachments

  • IMG-20180815-WA0022.jpg
    IMG-20180815-WA0022.jpg
    76.6 KB · Views: 391
  • IMG-20180815-WA0021.jpg
    IMG-20180815-WA0021.jpg
    58 KB · Views: 386
  • IMG-20180815-WA0020.jpg
    IMG-20180815-WA0020.jpg
    82.1 KB · Views: 371
  • IMG-20180815-WA0019.jpg
    IMG-20180815-WA0019.jpg
    57.2 KB · Views: 338
  • Like
Reactions: Techvir
P

Pathera

Senior Member
Dec 31, 2012
151
9
lesbianu said:
I relocked the bootloader before the OP opened this thread: https://xdaforums.com/showpost.php?p=77177509&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! :good:
Click to expand...
Click to collapse

I dont really know what sideload means and how it works can u give me detailed instructions please :)
 
lesbianu

lesbianu

Senior Member
Jul 16, 2013
94
65
Bucharest
Hard to explain it step-by-step, check this tutorial: https://www.getdroidtips.com/moto-z-android-oreo-opl27-76-57/
Use all the information from there, but when you reach Step-8 Now to flash the firmware give the following command, use this command:
Code: 
ADB sideload Blur_Version.27.231.8.griffin.retail.en.US (OPLS27.76-51-7).zip

The OTA file to update to 1 June 2018 it's HERE (I downloaded it using @erfanoabdi's tool).

Hope you can mange it! :)

---------- Post added at 10:01 PM ---------- Previous post was at 09:59 PM ----------

You can change the OTA filename from Blur_Version.27.231.8.griffin.retail.en.US (OPLS27.76-51-7).zip to OTA.zip, so the command will become:
Code: 
ADB sideload OTA.zip
 
Last edited:
E

Elmariano132

New member
Mar 26, 2014
2
0
I have OPLS27.77-51-7 (July update) - Can I safety do this as pots #1 with GRIFFIN_OPLS27.76-51-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Rom Software?
 
lesbianu

lesbianu

Senior Member
Jul 16, 2013
94
65
Bucharest
If you updated via OTA to the latest firmware you'll have to wait for the corresponding firmware zip file to emerge on internet. It should contain your latest build in the name of the zip, something like: GRIFFIN_OPLS27.77-51-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
The firmware file from the 1st post it's older than your current installed ROM. You will receive errors...
 
  • Like
Reactions: Elmariano132
E

eLaDiio

Senior Member
Nov 27, 2011
150
49
Santiago
Works all the guide, i will put my info about if works the update via OTA, thanks for the guide


i can't update my phone, while was installing send error on the screen, i will force it by sideload anyway
 
Last edited:
P

Pathera

Senior Member
Dec 31, 2012
151
9
lesbianu said:
Here is another guy with the same problem. I wrote there what I would do...
Click to expand...
Click to collapse

Hi, so i tried everything (sideload, reflash) and it didnt work.

I unlocked my bootloader again and installen the OTA then through phone, and it worked. But I'd like to lock my bootloader, can u tell me how to do that now without flashing the older versions? So just locking it now.
 
lesbianu

lesbianu

Senior Member
Jul 16, 2013
94
65
Bucharest
If you updated to the latest version: OPLS27.76.-51-7 (1 July security patch) you cannot re-lock the bootloader until a OPLS27.76.-51-7 full firmware .zip file will be available for download. Sorry!
You had to re-flash OPLS27.76-51-5, re-lock the bootloader and after that to test the latest OTA (I wrote the steps on the post for the other guy). That way your phone would be locked and updated to the latest ROM. Now you have to wait...

---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------

@Pathera
 
You must log in or register to reply here.

Similar threads

Manish54
[GUIDE] Unbrick hard bricked Moto Z
Replies
337
Views
123K
ItsAsfar
ItsAsfar
erfanoabdi
[GUIDE][ROOT][TWRP-MOTOMODS] How To Root Moto Z with SuperSU
Replies
201
Views
92K
C
CostasV23
abhishekiswithyou
Moto Z Android Oreo Update Available -Channels- (screenshots)
Replies
368
Views
93K
S
szybki_ben
Y
  • Locked
[Official]Moto Z Receiving 7.1.1 Update!!
Replies
263
Views
47K
ph03n!x
ph03n!x
X
[GUIDE] to enable DualSim on SingleSim Moto Z by xequtor
Replies
103
Views
39K
M
moemos

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 1
    YamazakiRobert
    YamazakiRobert
    eLaDiio said:
    as a question, what version of bootloader do you have? or doesn't care to the process?
    Click to expand...
    Click to collapse

    the first script updates the bootloader
    View
    1
    lesbianu
    lesbianu
    I relocked the bootloader before the OP opened this thread: https://xdaforums.com/showpost.php?p=77177509&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! :good:
    View
    1
    lesbianu
    lesbianu
    If you updated via OTA to the latest firmware you'll have to wait for the corresponding firmware zip file to emerge on internet. It should contain your latest build in the name of the zip, something like: GRIFFIN_OPLS27.77-51-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
    The firmware file from the 1st post it's older than your current installed ROM. You will receive errors...
    View
    1
    C
    crnkoj
    I don't and my moto z is relocked so I can't really. It's easy. You just do what is written
    View

New posts