I know its bootloader is locked, but what happens if I try to flash trough fastboot? I mean, in the black kinda console screen after you press Power button + Vol Down button.
ADB interface recognize this, but I'm pretty afraid to make my Moto Z a hard dead block. So, have anyone did this?
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
rusa-raus said:
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
Click to expand...
Click to collapse
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
echo92 said:
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
Click to expand...
Click to collapse
Understood, seems like Verizon is not gonna update Moto Z Play...
Hi, recently I bought my Moto Z2 Play (XT1710-09).
I really wanted to root my phone, but because of some weird bug, it soft-bricked it. Fortunately I had Absolute backup of whole internal storage so I have Original files.
Also I have not flashed TWRP, I have only fastbooted TWRP (Which is propably why I soft-bricked my phone)
So my question is very easy. Is it possible to lock bootloader if I have recovered back whole system and all it's files by stock files with which it (Moto Z2 Play XT1710-09) arrived?
Also the phone is fully functioning at the moment, with original files mantionet above, but it can't make working OTA updating process. And it's pain in ass, because the update manager is still apearing with new update...
So I have decided to lock bootloader even if it means to wipe all personal data and factory reset. Just for sake of getting rid of that stupid OTA updatete fullscreen pop up, that I have a new update waiting to be downloaded and installed.
You may ask as well "Why do you want to lock bootloadert insted of buying Titanium backup pro and freezing that update manager". The reason is simple. I'm afraid of rooting my phone again, because last time, it soft-bricked it and next time, it may full-brick it.
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Surely there is a fastboot command somewhere (which I think I saw in another thread) without having to flash some firmware?
https://forum.xda-developers.com/showpost.php?p=77270030&postcount=9
So that does mean. As long as I have 100% of stock files with which it come to me, it will lock?
julesism said:
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Click to expand...
Click to collapse
Every firmware I try fails to lock my bootloader, validation fails because non of them are above the security level of my device before I unlocked. Is there any newer firmwares ?
Just received a xt1710-01 from ebay and it is in excellent condition. Still on 7.1.1
I currently have a Droid Turbo thats rooted, now I want to do this z2.
Question is where do I start? Links?
Thank you.
Unlock the bootloader (I guess you know how to do so), Flash or boot TWRP and from it flash Magisk. That should be all.
But see if you can get the latest Oreo update to run first. For a while Moto uses a kernel with a buggy implementation of F2FS so you need to flash a module with Magisk in order to get it to work.
Whew, well I managed to unlock the bootloader. This was my first time (virgin).
Is upgrading to Oreo worth it? It's nagging me to do a update now, but I wasn't sure. I love Kitkat on my Turbo so the latest isn't really important to me, but if you feel I should, I will.
Well I have spent about 2 hours reading and d/ling updates and finally Oreo. Still not comfortable doing the rooting till I understand the procedure more.
This looks doable. https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Dammit! I read instructions to do a full wipe. Blank phone now. Looking on how to reinstall stock rom.
Finally after 2 days I have a rooted Oreo Z2. To may damn different ways to restore a OS and to root out on the net.
... You only have to boot a TWRP image from fastboot and flash Magisk there. That works for any device with unlocked bootloader, you just have to find the fitting TWRP image.
It have tried endless times trying to get root access via magisk by patching my retail Canada boot.img file. My phone has an unlocked bootloader and I definitely have the right boot image as I tried another boot image from another firmware and got a startup failure which I fixed by flashing the retail Canada boot.img. It patches okay and flashes okay (except for message "image signed with key bad key") but no root access and no installed Magisk. If anyone has a solution, has gained root access some other way or knows for a fact that magisk does not work with this model phone I would be very interested to know. This is the firmware I used the boot file from : XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-57
Thanks
Bad Key is normal after you unlock the boot loader. Have you tried side loading the Magisk apk along with a copy of the boot.img and have the app mod the boot.img? Then move the modded boot image back to your pc and fastboot it on to the phone. That's what I did with my G7Power.
Side loading
Not sure what side loading is but I did patch the boot file with Magisk manager, put it on my PC and fastbooted it to my phone with no results. The ROM for the G7 Play is different than older androids. I tried to create a makeshift recovery for it but my ROM does not have a recovery.img or other older android ROM files for that matter. I will have to wait for some kind of workaround for magisk or someone takes on the challenge to create a recovery for the different file system. I installed a recovery for my Moto G4 plus and rooted no problem. I should have researched more before I purchased the G7 Play and unlocked the bootloader so now I am at the mercy of development.
Thanks for your reply.
Nothing
I tried rooting the phone with the Magisk... Nothing.
I tried to relock the bootloader... Nothing.
What works on the other Moto G7s does not work on our G7 Play.
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
realsine said:
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
Click to expand...
Click to collapse
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Marcondes BR said:
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Click to expand...
Click to collapse
Yes, I have a Motorola Moto g7 play.
When I open the bootloader, I can't close it immediately. I get a "bad key" (or something like that). I have to flash the matching original boot.img first.
So in the bootloader:
* fastboot flash boot boot.img
And if that was successful, then afterwards (without restart)
* fastboot oem lock
Possibly the last command must be entered a second time, but this will be output when
If the command works, then the smartphone boots automatically at this point and the bootloader is closed again.
I assume that you have the correct boot.img and must flash.
I have performed this procedure several times successfully.
Information: at every LOCK and at every UNLOCK the data is reset (Factory reset?).
relock bootloader confirm
I can confirm this does work. I just relocked and unlocked my bootloader with those instructions. Again if anybody has successfully rooted this phone I would love to know.
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
thetesterman said:
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
Click to expand...
Click to collapse
This device is definitely rootable -- there is no doubt as to proof of concept. It's just a matter of a viable root method being ironed out. The developer of Magisk (topjohnwu) has stated that the current difficulty with installing systemless root on the Moto G7 Play (via patched boot image) is due to the particular A/B partition index of the device. He is actually working on a universal resolution now. It also appears that TWRP custom recovery is being compiled by the guys over at TeamWin, not to mention unofficial builds being compiled by other dedicated devs (which will likely come first). I went ahead and bought a G7 Play and am just patiently waiting for the imminent resolution for root, TWRP, and hopefully, full-on ROM development. In other words, it's not a matter of if; it's just a matter of when.
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
avf90m said:
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
Click to expand...
Click to collapse
Amen to that.
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
LexusBrian400 said:
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
Click to expand...
Click to collapse
Couldn't agree more, fantastic phone ( wish it had wireless charging though ) and all I need is root.
ninjakira said:
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
Click to expand...
Click to collapse
The G6 Play root method will not work on the G7 Play. The G7 Play uses the A/B partition index. There are currently a few developers ironing out a viable root method and also working on a stable TWRP build. Many Moto G7 Play owners have hard bricked their devices by trying root strategies intended for devices with standard GPT partition tables.
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Viva La Android said:
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Click to expand...
Click to collapse
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
GatoDeNieve said:
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
Click to expand...
Click to collapse
Ok thanks for the info. I would guess an OTA update for my variant is imminent within the next couple of weeks at least.
Motorola is not in the practice of patching root exploits via OTA updates. The company actually supports both OEM Unlocking and Android development. I don't think you would have any future issues with root by installing your pending OTA. But at the same time I don't blame you for holding off. When in doubt, don't update. Again, I do thank you for the info.
The xt1952-4 (Sprint, Boost, Virgin) variant is rolling out with PCY29.105-134 with June 1 security patches. I just got notification about ten minutes ago.
I finally got a pixel phone, the 2 XL. got a question about the romming process
if i install a custom rom, then decide to go back to stock using the images that google provides, and relock the bootloader and all that, will i still be able to get OTA updates?
i have a moto z3 play that if you go back to stock and lock it, it says the phones using a different OS and requires Motorola to reprogram the phone in order to get OTA updates again.
xSpartacusx said:
I finally got a pixel phone, the 2 XL. got a question about the romming process
if i install a custom rom, then decide to go back to stock using the images that google provides, and relock the bootloader and all that, will i still be able to get OTA updates?
i have a moto z3 play that if you go back to stock and lock it, it says the phones using a different OS and requires Motorola to reprogram the phone in order to get OTA updates again.
Click to expand...
Click to collapse
You should be fine. While I haven't done it personally, I've seen several that have ??