Develop Bugs

HELP!! Potentially bricked my m9

Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!

anshuashmeet said:
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
Click to expand...
Click to collapse
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?

Flippy498 said:
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Click to expand...
Click to collapse
Thanks for your reply!
I've submitted an enquiry form to them. Didn't know that service existed. Hopefully they have the RUU file that I need.
I did download the stock backup file from that link but I thought before I give it a go, I'll try and get an OTA and get an official update. That failed so I decided to flash the firmware before going to the latest rom. Forgetting I just locked my bootloader with stock recovery, completely unaware of this 5.1 developer option issue. My fault for not doing research, but I didn't know such issue could exist as for the last few years, I haven't had an issue like this. Normally issues occur if I flash a newer ROM without firmware so was trying to avoid that.

OTA issue after unlocking bootloader, installing TWRP and then uninstalling TWRP

heyyyy, so, i can't manage to get OTAs to install...
bootloader is unlocked, and i had installed TWRP for a while, but ultimately reflashed an older version of the stock recovery.img
now, i'm still having issues with OTAs... they download and begin to execute as normal, but the progress bar on the update screen stops at about 10% and then the screen with the android figure with it's chest cavity open pops up and simply says error!
the phone reboots itself as normal after a minute or so, and once booted up properly, it just says "update failed, no changes were made"
any thoughts or suggestions on that?
i've got the -01 version, north american retail...

imho OTAs aren't working since you cannot re-lock the bootloader of the z2 play because there is no boot.img signed from motorola available.
so you will have to install OTAs manually when the become available through e.g. TWRP.
the OTAs recognize an altered boot.img and don't get installed this way.

I had originally unlocked my phone and did the whole TWRP/root thing, but with the lack of development, I went back to stock, using the images Junior Passos has posted. I still have an unlocked bootloader, but I can apply OTA updates fine (I've had the last three OTAs install without issue).

Vzw pixel xl update to newest stable release.

Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you

Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
This excellent guide by HomeBoy76 should give you all the info that you need....
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279

Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.

It's actually pretty simple, just download the latest factory image of either Oreo,. Flash the flash all script included with fast boot. Afterward boot into the system without setting up a pin or password or anything, set it up, then reboot into boot loader and boot the latest TWRP, then within TWRP flash TWRP zip file and Magisk root. Reboot system.

Homeboy76 said:
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
Click to expand...
Click to collapse
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.

Hobocoe said:
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Click to expand...
Click to collapse
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.

Homeboy76 said:
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Click to expand...
Click to collapse
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.

Hobocoe said:
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Click to expand...
Click to collapse
You're welcome

update error

in brief
I have unlocked the botloder with commands in cmd, I have uploaded magisk, I expanded internal memory by sd card (my error). Unfortunately, after the upgrade to Android 9, the phone fail at receive any new updates (installation error of 30%). Subsequently, dumped magisk, did not help, , I uninstall sd card, now I did restore the factory data and the updates still do not work. November version of Andorida is badly bugged and there are problems even with the camera. So it looks like I'll have to send a phone for guarantees, a question now how to block a botloader or you have an idea how to fix ota update.

same here, but now you can download the full 10.0.3.0 rom to install with miflash. https://en.miui.com/download-354.html

fine but how to reblock a botloader ?

karenz88 said:
fine but how to reblock a botloader ?
Click to expand...
Click to collapse
use this on fastboot:
Code:
fastboot oem lock
Warning: this will wipe your data and if you have tampered with phone's partitions phone will hard brick. Make sure to have a backup. Other people have also experienced issues with January update. Locking the bootloader and booting the phone successfully doesn't mean that you will have January update for sure.

There's no point in locking the bootloader or returning the phone just because you failed to apply OTA update. Your phone is perfectly fine. Most of us had problems and bootloop while trying to apply Magisk OTA. This has been a frequent issue since the initial Pie update and the phone has nothing to do with it. It's either Google implemented stricter security policies or current version of Magisk are having Pie compatibility issues. If OTA is to important to you, just flash an official fastboot image and don't root your phone.

Ota does not have much meaning for me, but I have a problem with the camera and it annoys me already. I reblock a botloader and still cant update phone...

karenz88 said:
Ota does not have much meaning for me, but I have a problem with the camera and it annoys me already. I reblock a botloader and still cant update phone...
Click to expand...
Click to collapse
Fastboot image of 10.0.3 is already out. You could consider flashing your phone with "flash all" option to fix the errors. And i would recommend keeping the bootloader unlocked because many mi a2 owners got their phone bricked as a result of ota update with a locked bootloader in which case the only workaround is to disassemble the phone.

Has anyone successfully rooted Moto G7 Play?

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.