Related
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
How I Did it...
From a site with this in the title:
can_i_manually_flash_601_also_does_ota_work_with
Systemless root doesn't break ota, non-stock recovery breaks OTA.
Unlock bootloader, flash 6.0.1, flash TWRP, flash systemless root...
I did this:
Went back to stock recovery, by flashing via ADB, rebooted downloaded and attempted to install OTA on phone. Process started, rebooted, proceeded and then failed with error . Rebooted, got Factory image.
Extracted and ran flash-all.bat ONLY AFTER Removing the -w from this line:
fastboot -w update image-bullhead-mmb29k.zip
Got latest SuperSU v2.61 zip with auto boot patcher:
See androiding.how/android-6-0-1-root
Copied this to Memory on phone.
Flashed/Installed TWRP Recovery using ADB.
Booted into TWRP Recovery and installed SuperSU.
So now I'm running systemless rooted 6.01 on a Nexus 5X with mmb29k and every thing is working.
I think even though I rooted systemless 6.0, the modified Boot Image was still not letting OTA work.
We shall have to wait and see on the next OTA. Maybe just going back to stock recovery will be all that's needed.
There are some ADB commands that allow you to temporarily select a recovery image, but I'm not sure how that works.
Good Luck!
teapea said:
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
Click to expand...
Click to collapse
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Rooting will also mess up Ota too, but if u install a custom recovery, now that we have stock recovery it will be very easy to revert back for OTAs, there should be a way to root without a custom recovery but I am not sure how though, but with how oneplus makes it so easy to unlock bootloader and flash customers stuff there is really no need to stay stock
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
pileot said:
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Click to expand...
Click to collapse
As far as I know, you'd have to have TWRP to get root.
I don't think getting it rooted will mess up the OTA updates, other users sprovide flashable zips for the OTA anyway.. so you can still flash the zips manually with TWRP to keep you updated.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
To get root yes, you would need TWRP to flash to certain partitions but to keep root no. Your phone will operate just fine with root and stock recovery. Check what the user a few posts above mine said about temporary flashing TWRP to achieve your short term goals
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
TheSvensson said:
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
Click to expand...
Click to collapse
Yes, I have the stock recovery and it is rooted.
The recovery partition has nothing to do with all the other partitions except that it can read and write them.
This is the zip I flashed to get systemless root:
https://www.androidfilehost.com/?fid=24591000424939898
Some users reported that some Root-apps are not supported this way.
I am using Titanium Backup, Adaway, Trimmer and Root Explorer without issues.
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
All I did was manually flash OxygenOS 3.1.3 in TWRP (not flashed but booted) and reflash the root package afterwards.
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
I have an unlocked bootloader and tried this on my PC:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.709s]
booting...
OKAY [ 0.373s]
finished. total time: 1.092s
Nothing happens, bootloader start screen stays frozen. Until I hold down the power button. Might you know why?
AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
i tried to boot into twrp recovery with above command, but the phone seems to be stuck in the bootloader and not responding. Any ideas?
edit: comment above describes exact same behaviour, sorry for double post
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
AcmE85 said:
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
Click to expand...
Click to collapse
Thanks, that twrp img worked for me. The one I was using didnt allow me to boot to it.
AcmE85 said:
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
Click to expand...
Click to collapse
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
hahamuntz said:
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
Click to expand...
Click to collapse
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
AcmE85 said:
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
Click to expand...
Click to collapse
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
hahamuntz said:
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
Click to expand...
Click to collapse
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
AcmE85 said:
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
Click to expand...
Click to collapse
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
hahamuntz said:
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
Click to expand...
Click to collapse
Yes, OTAs will come and because of Root you will get the full OTA regardless, which does not cause any issues with TWRP.
I tried my previous method and the regular OTA would fail because of root which changes the kernel or the system partition.
OnePlus reacted to this and introduced the full rom OTAs at some point.
So with root on my device this is how I do OTAs now:
- get the OTA notification for the full rom
- download but don't install
- move the downloaded zip from android/data/com.oneplus.ota/files/.OnePlusOta to my download folder
- manually boot into twrp and flash full rom zip + SuperSU
AcmE85 said:
Yes, OTAs will come and because of Root you will get the full OTA regardless which does not cause any issues with TWRP.
Click to expand...
Click to collapse
Okay, thanks so much for your help
Hello,
My tmobile HTC One M8 was rooted (Supersu), unlocked bootloader, with TWRP. For the purposes of upgrading to Marshmallow, I restored stock recovery, re-locked bootloader, but was not successful in uninstalling SuperSu using Full unroot. The process hangs on 'Uninstalling'. I tried factory resetting from stock recovery, but after restarting the device SuperSU is still installed and rooted. Trying Full unroot again failed. Root checker confirmed that the phone was still rooted.
I tried loading the nandroid backup here , and installing from TWRP, but it fails to load.
EDIT - user error in loading the nandroid backup. After copying the unzipped folder and contents to TWRP folder, wiping the device then restoring, root was successfully uninstalled. Note that supersu did not uninstall with any other method. Marshmallow is now up and running.
murdoch07 said:
For the purposes of upgrading to Marshmallow, I restored stock recovery, re-locked bootloader, but was not successful in uninstalling SuperSu using Full unroot.
Note that supersu did not uninstall with any other method.
Click to expand...
Click to collapse
FYI, what you ended up doing, is mandatory (in order to OTA). You can't unroot and OTA, you need a stock (never rooted) ROM.
redpoint73 said:
FYI, what you ended up doing, is mandatory (in order to OTA). You can't unroot and OTA, you need a stock (never rooted) ROM.
Click to expand...
Click to collapse
That Is False, I Had A Rooted ROM (Slim6 HTC One M8 Android 6.0 STABLE Build) It's SuperUser/SuperSu Control Was In Dev. Options And I Still Managed To Run The OTA/RUU
---------- Post added at 10:06 PM ---------- Previous post was at 10:04 PM ----------
murdoch07 said:
Hello,
My tmobile HTC One M8 was rooted (Supersu), unlocked bootloader, with TWRP. For the purposes of upgrading to Marshmallow, I restored stock recovery, re-locked bootloader, but was not successful in uninstalling SuperSu using Full unroot. The process hangs on 'Uninstalling'. I tried factory resetting from stock recovery, but after restarting the device SuperSU is still installed and rooted. Trying Full unroot again failed. Root checker confirmed that the phone was still rooted.
I tried loading the nandroid backup here , and installing from TWRP, but it fails to load.
EDIT - user error in loading the nandroid backup. After copying the unzipped folder and contents to TWRP folder, wiping the device then restoring, root was successfully uninstalled. Note that supersu did not uninstall with any other method. Marshmallow is now up and running.
Click to expand...
Click to collapse
Follow This Link, I Made A Thread That Will Show You How To Get Back To Stock, Doesn't Matter If You're Rooted Or Not
http://forum.xda-developers.com/tmobile-htc-one-m8/general/htc-m8-t-mobile-recovery-to-stock-t3493877
PM Me On Instagram @kailehkookie
Or Email Me [email protected]
If U Need Further Help
TheKookieGuy said:
That Is False, I Had A Rooted ROM (Slim6 HTC One M8 Android 6.0 STABLE Build) It's SuperUser/SuperSu Control Was In Dev. Options And I Still Managed To Run The OTA/RUU
Click to expand...
Click to collapse
OTA or RUU? They aren't remotely the same thing. They are very different, and have very different requirements. The fact you lumped them together, to me suggest you don't know the difference.
RUU doesn't care what mods are on the phone (root, custom ROM, etc.) as long as the bootloader is locked (not needed if s-off) and you are running the proper version RUU.
OTA is a completely different animal.
Or if you ran an RUU, before OTA, the RUU would already have returned you to a full stock (never rooted) image. Which is why the OTA would then work.
redpoint73 said:
OTA or RUU? They aren't remotely the same thing. They are very different, and have very different requirements. The fact you lumped them together, to me suggest you don't know the difference.
RUU doesn't care what mods are on the phone (root, custom ROM, etc.) as long as the bootloader is locked (not needed if s-off) and you are running the proper version RUU.
OTA is a completely different animal.
Or if you ran an RUU, before OTA, the RUU would already have returned you to a full stock (never rooted) image. Which is why the OTA would then work.
Click to expand...
Click to collapse
I'm sorry I misread what u said I understand where I was wrong. Thx for telling me
I have Xperia z1 compact running stock non-rooted 14.6.A.1.236 rom. My bootloader is locked. I want to be able to install custom roms. What's the best way to root, unlock bl and install custom recovery? I've been searching forum for past few days but most of the download links redirect to d-h.st. and that breaks the chain of needed files.
Also i never used flashtool and i don't know should i use Sony flashtool or "original" one
bolcna said:
I have Xperia z1 compact running stock non-rooted 14.6.A.1.236 rom. My bootloader is locked. I want to be able to install custom roms. What's the best way to root, unlock bl and install custom recovery? I've been searching forum for past few days but most of the download links redirect to d-h.st. and that breaks the chain of needed files.
Also i never used flashtool and i don't know should i use Sony flashtool or "original" one
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6
levone1 said:
https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6
Click to expand...
Click to collapse
Do i have to be rooted to backup TA partition
bolcna said:
Do i have to be rooted to backup TA partition
Click to expand...
Click to collapse
I don't think so. Just need adb...
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
You don't have to downgrade to flash NUT. It's been a while since I did it, but I'm pretty sure that flashing supersu won't totally remove Kingroot. Best thing to do once you're rooted, if you don't want to unlock bl, is probably to install recovery, then in recovery flash a prf, which will wipe your system and install new system with supersu instead of Kingroot.
Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
I don't trust any universal rooting apps. Only way to legit root your phone is to downgrade to kitkat and then root using exploit, then flash prerooted lollipop (that is if you wan't to stay on stock rooted rom). If you don't plan on staying on stock room and only want quick root you have to use kingroot since that's only universal root that can root z1c. When it comes to recovery there you have two choices. To use xzdualrecovery or to unlock bootloader (you will loose drm keys which means you will lose stuff like x-reality) and flash normal recovery. I would go for dual recovery because if you ever wan't to get back to stock you can since stock recovery isn't getting overwritten with xzdr. But if you choose to unlock bootloader first backup TA (you have to be rooted) and then unlock.
Hope this helps
Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
bolcna said:
I don't trust any universal rooting apps. Only way to legit root your phone is to downgrade to kitkat and then root using exploit, then flash prerooted lollipop (that is if you wan't to stay on stock rooted rom). If you don't plan on staying on stock room and only want quick root you have to use kingroot since that's only universal root that can root z1c. When it comes to recovery there you have two choices. To use xzdualrecovery or to unlock bootloader (you will loose drm keys which means you will lose stuff like x-reality) and flash normal recovery. I would go for dual recovery because if you ever wan't to get back to stock you can since stock recovery isn't getting overwritten with xzdr. But if you choose to unlock bootloader first backup TA (you have to be rooted) and then unlock.
Hope this helps
Click to expand...
Click to collapse
I would go with unlock bl method. You can restore TA after rooting so you done lose drm, and it's easy to root with unlocked bl - https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6
I bought the phone (HTC One M9) yesterday and I realized I couldn't install the OTA updates I received because TWRP custom recovery was installed. I've looked through all the threads here but I never found the file I need. Any help would be highly appreciated. By the way,the bootloader is locked and the phone is unrooted, but S-OFF
S-off makes no difference. Unlocked bootloader makes no difference. If you flash a stock recovery over twrp you'll instantly kill the phone.
You need the full proper stock firmware of the exact same version you have on it now in .zip format and flash it from the external sd in download mode. You can use the ruu (.exe) too if it'll flash. Then you can take the ota's.
If the phone has been touched and not flashed back to stock you will need to flash to stock to get ota's. You cannot just "undo" what you've done to it. It must be properly reflashed to get the stock hash and keys.
shivadow said:
If you flash a stock recovery over twrp you'll instantly kill the phone.
Click to expand...
Click to collapse
Why should flashing the stock recovery via twrp kill the phone? If that was the case you wouldn't be able to get back to stock via twrp backups.
Edit @OP: If you have a RUU for the mentioned firmware version then you can use the RUU decryption tool that is linked in the ReadMe thread. The tool will extract the stock recovery from the RUU.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Why should flashing the stock recovery via twrp kill the phone? If that was the case you wouldn't be able to get back to stock via twrp backups.
Edit @OP: If you have a RUU for the mentioned firmware version then you can use the RUU decryption tool that is linked in the ReadMe thread. The tool will extract the stock recovery from the RUU.
Click to expand...
Click to collapse
Unrooted. Twrp will require root. If I remember correctly you flash twrp which roots the phone and then you flash supersu?.
If it is unrooted with twrp on it then it is in an "unknown state" (to me) and not worth risking going any further unless it is a full stock firmware flash. If he flashes a stock recovery over twrp he still wont have system "untouched" which I believe stock recovery requires?.. At least to get the ota's he will need an untouched partition.
Or would he be better off rerooting via twrp and go from there?.
No, twrp doesn't require root nor does flashing twrp root the phone. Twrp is a custom recovery that supports (unlike the stock recovery) flashing files that aren't signed by HTC. SuperSU and magisk are the ones that enable root. For using a metaphora (that might not fit exactly but that should suffice for making things clear): You don't consider your phone to be rooted, either, just because you installed Odin on your PC.
Root can (more or less) be compared with admin permissions on a Windows PC. It has nothing to do with twrp being "installed" or not. There are even methods for rooting phones without the use of twrp (e.g. kingroot - which is adware, btw).
If you flash twrp but don't root your phone then it's simply not-rooted. Keeping the phone in such a state doesn't make much sense since it isn't completely stock, either. However, it's not risky at all.
As long as the system image didn't get modified (e.g. by mounting it via twrp) and you didn't tinker with your phone aside from flashing twrp, re-flashing the stock recovery is absolutely sufficent for getting back to a completely stock state.
The thing is that most people that flash twrp to modify their system partition in one way or another. As you wrote (and due to Android updates being block-based since Android 5), ota's will fail as soon as they notice that the system got modified.
The stock recovery on the other hand doesn't "care" whether your phone is modified or not.
The only problem that might arise is that people tend to re-lock their bootloader since they learned (while using older htc devices) that it would be necessary for flashing certain stock files (e.g. RUUs) or installing OTA's. The m9 won't boot if you re-lock the bootloader and the phone isn't completely stock. There are security checks which don't differentiate between wanted user customizations and critical software failures. Therefore, they will try to save the hardware from damages caused by the "failed" software (by preventing the phone from booting).
In addition, google's frp makes it impossible to re-un-lock the bootloader in such situations if "OEM unlock" isn't activated in the developer settings of the used rom.
That's why the readme thread discourages the average Joe and the average Jane from re-locking this phone.
Sent from my Moto X Style using XDA Labs
Thanks, but I went ahead and flashed a zip RUU for that firmware version, then flashed the nougat one afterwards