Database Users

[WARNING] Do NOT Downgrade Your Bootloader or Partition Table - You Risk Bricking!!!

BEFORE YOU COMMENT ON THIS THREAD - PLEASE READ THIS POST AND UNDERSTAND WHAT THE DIFFERENCE IS BETWEEN THE BOOTLOADER, PARTITION TABLE, SYSTEM AND KERNEL/RAMDISK!!!!
This post is not about downgrading from lollipop to kit kat in general. It is SPECIFICALLY about and it is ONLY about downgrading the BOOTLOADER (motoboot.img) and the PARTITION TABLE (gpt.bin). The system (system.img) and kernel/ramdisk (boot.img) are NOT the subject of this thread. If you don't understand the difference b/t the bootloader, partition table, system and kernel/ramdisk, then please refrain from posting on this thread and simply read until you understand the difference.
Please do not comment if you do not even know the version of the bootloader you are running b/c you have nothing substantive to contribute then. If you know the version of the bootloader you are running now and know what it was before you upgraded and after you downgraded, great, please let us all know your experience. But if you don't, AGAIN, you have nothing of value to contribute to this thread.
The Moto X 2014 is not a Nexus device - you CANNOT safely downgrade your bootloader (motoboot.img) or partition table (gpt.bin). You risk bricking if you do, especially if you downgrade the bootloader!!!
You need to understand what you are flashing. If you don't understand what you are flashing, read and ask questions before you flash until you do understand what you are flashing. You also need to know what version of the bootloader you currently have before you flash.
Also, you should not attempt to have a bootloader-partition table mismatch in terms of versions. Both your bootloader and your partition table should be the same version - i.e., if your bootloader is the 5.0 bootloader, your partition table should be the 5.0 partition table.
Edited - it looks like mfastboto and maybe even regular fastboot have checks in them to prevent a bootloader or partition table downgrade. However, the OTA updater scripts may or may not have sufficient checks in them to prevent bricking if you have previously upgraded then downgraded the system/kernel/radios and then attempted to take an OTA. For instance, people have reported bricking after flashing to 5.1 then downgrading system/kernel/radios to 4.4.4 then taking the 5.0 OTA = brick.

I've seen alot of stuff about that in the threads. Are you saying that you can't downgrade back to 5.0 or 4.4? Cause I have successfully flashed back to stock KitKat from the 5.1 soak several times. Even flashing partition and motoboot. It just downgraded the tz.
Sent from my XT1095

dustin_b said:
I've seen alot of stuff about that in the threads. Are you saying that you can't downgrade back to 5.0 or 4.4?
Click to expand...
Click to collapse
I am saying exactly what I said in the OP - you can't safely downgrade your bootloader or partition table. And you can't have a bootloader/partition table version mismatch. There are rare exceptions to that like the one for the MX13 that jcase used to root 4.4.
dustin_b said:
Cause I have successfully flashed back to stock KitKat from the 5.1 soak several times. Even flashing partition and motoboot. It just downgraded the tz.
Click to expand...
Click to collapse
Did you use RSDLite to flash motoboot.img and gpt.bin? If so, like I said in the OP, it has checks built into it and it will prevent you from downgrading your bootloader and partition table. mfastboot may have the same checks built in, idk, but I don't think fastboot from the SDK does and that is where people are getting into trouble.
What did you use to flash?
Also, can you post a video showing you doing this w/o bricking? Show your BL version on 5.1, which from what has been reported is 60.14, and then flash the 5.0 BL, which is 60.1 1 and show us that you were able to downgrade your bootloader back to 60.11 w/o bricking. Then once you do that, downgrade the bootloader down to 4.4.4 (I am not sure what the version number is, but once you successfully downgrade you can tell us).
The Q&A forum is littered with people who bricked their devices when they attempted to downgrade their bootloaders.
I think people would be foolish to believe that it is safe to downgrade the bootloader of a Moto X given all the bricks unless you post some proof it is safe.

It might be awhile before I could do a video but I just used fastboot from the SDK. I don't know if it actually downgrades the bootloader. Maybe just the trust zone. I've never actually checked. I wonder if people have noticed but on the 5.1 soak you have to go into developer options and check OEM unlocking now.
Sent from my XT1095

In the past when I downgraded to KK from 5.0, if I tried to flash the old bootloader, it would simply fail to flash. It never bricked. I have also flashed the gpt from KK when downgrading in the beginning. It flashed fine and didn't brick. I don't flash gpt now that I know what it is but the first few times I downgraded, I did flash it.
Edit: I always used fastboot/mfastboot. I can't get RDSLite to detect my Moto X. MDM doesn't detect it either.

dustin_b said:
It might be awhile before I could do a video but I just used fastboot from the SDK. I don't know if it actually downgrades the bootloader. Maybe just the trust zone. I've never actually checked.
Click to expand...
Click to collapse
Honestly, I would not try this as there is no reason to do it. It is dangerous and it doesn't provide any benefit. If you don't believe me that it it dangerous, read on the Q&A forums when people ask for help after bricking their devices - almost always they were attempting a bootloader or partition table downgrade when they bricked. It is just not worth it IMO. You do what you want of course as you seem to believe it is possible but it is not something I would do.
dustin_b said:
I wonder if people have noticed but on the 5.1 soak you have to go into developer options and check OEM unlocking now.
Click to expand...
Click to collapse
That is how it is on the Nexus 6 too.

walrusmonarch said:
In the past when I downgraded to KK from 5.0, if I tried to flash the old bootloader, it would simply fail to flash. It never bricked.
Click to expand...
Click to collapse
why some people get a failed flash and others get a brick, idk, but all you have to do is read on the Q&A forums how many people brick attempting to downgrade the BL and/or PT.

JulesJam said:
why some people get a failed flash and others get a brick, idk, but all you have to do is read on the Q&A forums how many people brick attempting to downgrade the BL and/or PT.
Click to expand...
Click to collapse
Yeah, I've seen people brick it that way. I think I just got lucky the few times I have done it

walrusmonarch said:
I have also flashed the gpt from KK when downgrading in the beginning. It flashed fine and didn't brick. I don't flash gpt now that I know what it is but the first few times I downgraded, I did flash it.
Edit: I always used fastboot/mfastboot. I can't get RDSLite to detect my Moto X. MDM doesn't detect it either.
Click to expand...
Click to collapse
I just don't see why it is ever necessary to mess with the BL or PT. System, recovery, radios, kernel, sure I see why you would do that. If downgrading your BL or PT doesn't provide any benefit to you, why do it?

JulesJam said:
I just don't see why it is ever necessary to mess with the BL or PT. System, recovery, radios, kernel, sure I see why you would do that. If downgrading your BL or PT doesn't provide any benefit to you, why do it?
Click to expand...
Click to collapse
I agree with you. I did it mostly because I didn't know what the heck I was doing back then. I was just flashing away hoping everything would work

walrusmonarch said:
I agree with you. I did it mostly because I didn't know what the heck I was doing back then. I was just flashing away hoping everything would work
Click to expand...
Click to collapse
My first device was a Nexus (GNex) so I flashed with abandon w/o knowing what I was doing and never bricked. When I got my Moto X 2013, I went to the MX13 XDA forum and started to read and am damn glad I did b/c I would have never known. There were tons of people who bricked trying to downgrade. I am sure Motorola had to do a lot of warranty replacements for this reason. Really, there should have been more checks that would prevent bricking and the flash would just fail. There weren't though except with RSDLite. IMO Motorola deserved having the added cost of these warranty replacements.
Hopefully, Motorola has built more checks into the system now where the flash will fail rather than bricking the device, but clearly whatever they have done isn't enough. Again, idk why some people report being able to do this and others end up with bricks, but I don't see the need to do it at all and until it becomes universally safe to do this across the board every time, I wouldn't do it.

JulesJam said:
My first device was a Nexus (GNex) so I flashed with abandon w/o knowing what I was doing and never bricked. When I got my Moto X 2013, I went to the MX13 XDA forum and started to read and am damn glad I did b/c I would have never known. There were tons of people who bricked trying to downgrade. I am sure Motorola had to do a lot of warranty replacements for this reason. Really, there should have been more checks that would prevent bricking and the flash would just fail. There weren't though except with RSDLite. IMO Motorola deserved having the added cost of these warranty replacements.
Hopefully, Motorola has built more checks into the system now where the flash will fail rather than bricking the device, but clearly whatever they have done isn't enough. Again, idk why some people report being able to do this and others end up with bricks, but I don't see the need to do it at all and until it becomes universally safe to do this across the board every time, I wouldn't do it.
Click to expand...
Click to collapse
Yeah, my first android device was a N7 (2012). I flashed away at it like crazy. Sometimes multiple times a day... I guess I just had that same mentality when I started trying to flash the Moto X... It is a good idea to read before flashing. I've been trying out Windows phone recently and managed to flash a rom on my lumia 635 without bricking. I barely read anything, and I probably just got lucky again...
RSDLite seems convenient. I wish I could get it to work for me, along with MDM. Sigh... oh well.

walrusmonarch said:
RSDLite seems convenient. I wish I could get it to work for me, along with MDM. Sigh... oh well.
Click to expand...
Click to collapse
The only thing with RSDLite if you don't want your data overwritten, you have to edit the xml file.
As far as the driver issue, you can try downloading the drivers from root junky's site to see if you can install them that way.
http://rootjunkysdl.com/?device=Android Drivers&folder=Motorola

JulesJam said:
The only thing with RSDLite if you don't want your data overwritten, you have to edit the xml file.
As far as the driver issue, you can try downloading the drivers from root junky's site to see if you can install them that way.
http://rootjunkysdl.com/?device=Android Drivers&folder=Motorola
Click to expand...
Click to collapse
Yep, I have tried those too. No luck. I have at least got fastboot and adb working fine, so its not so bad. Thanks for trying to help!

OK, I changed the title from stating "you will brick" to "you risk bricking".

JulesJam said:
Honestly, I would not try this as there is no reason to do it. It is dangerous and it doesn't provide any benefit. If you don't believe me that it it dangerous, read on the Q&A forums when people ask for help after bricking their devices - almost always they were attempting a bootloader or partition table downgrade when they bricked. It is just not worth it IMO. You do what you want of course as you seem to believe it is possible but it is not something I would do.
Click to expand...
Click to collapse
Ok, so after attempting again I have discovered a couple of things. First, I had to use the fastboot commands from withn the mfastboot folder. I did not use mfastboot commands though. Secondly, it doesnt actually downgrade the bootloader. I think it just downgrades the tz (there is a message about this on the fastboot screen). It did not brick though and I have done this multiple times. But it obviously doesnt make a difference so I'm with you. No one should try this at the risk of bricking their device! My apologies to you @JulesJam. I wasn't trying to be offensive but just thought I would throw it out there since I thought I had done it before. I am far from an expert on these things especially fastboot cause I was on Galaxy devices before this so i never had to use it. I'm kind of like the other guy I have always went by another guide on returning to stock and just thought it should be that way. So again, DO NOT DO THIS AT THE RISK OF BRICKING YOUR PHONE:good:

dustin_b said:
Ok, so after attempting again I have discovered a couple of things. First, I had to use the fastboot commands from withn the mfastboot folder. I did not use mfastboot commands though.
Click to expand...
Click to collapse
I am not sure what you mean fastboot commands w/in the mfastboot folder. Mfastboot
is just motorola's version of fastboot that allows the system image to be flashed as a single image file instead of being broken down into chunks. Unless you manually rename it, it is called fastboot, however some people have manually renamed it and then uploaded it in a zip file and you can find links to it online. I manually renamed mine mfastboot.exe so as to avoid confusion with fastboot.exe from the SDK.

dustin_b said:
I was on Galaxy devices before this so i never had to use it. I'm kind of like the other guy I have always went by another guide on returning to stock and just thought it should be that way. So again, DO NOT DO THIS AT THE RISK OF BRICKING YOUR PHONE:good:
Click to expand...
Click to collapse
Did you use ODIN before? I think RSDLite is similar to ODIN but since I have never used ODIN I don't really know.
But yes, what Samsung does and what Motorola does wrt the bootloaders is completely different as the bootloaders are proprietary. I am just glad to see that there are more checks now than there used to be that prevent you from downgrading at least some of the time.
There are some very sad people on the Q&A forum right now searching for the signed binary files to restore their bootloaders but those have to be leaked and so far, they do not seem to be anywhere accessible by outsiders.

I've done it loads of times too. Everytime I tried to flash back the gpt or motoboot, it just failed (was trying to relock bootloader, never would let me), normal fastboot. Also with the newest version of fastboot it can flash the system files, no need to use mfastboot at all anymore.

nbell13 said:
I've done it loads of times too. Everytime I tried to flash back the gpt or motoboot, it just failed (was trying to relock bootloader, never would let me), normal fastboot.
Click to expand...
Click to collapse
Yeah, again I can't explain why some people just get a failure and others get a brick, but on the Q&A forum you will see there are those who brick attempting to downgrade.
nbell13 said:
Also with the newest version of fastboot it can flash the system files, no need to use mfastboot at all anymore.
Click to expand...
Click to collapse
Last time I tried the latest version of fastboot, it cannot flash the single file system.img. It can flash the system if it is broken down into chunks. So if you are using the fxz with the single system.img, you have to use mfastboot last I checked.

[Q] Another Rooting Question

The majority of my phones have been HTC so not really sure if unlocking the bootloader is normal procedure for a Motorola phone to obtain root. So i have a couple of questions on rooting this device, I'm happy to stay on a rooted stock so don't really see the point/need of unlocking the bootloader at this time.
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Thanks in advance.

rnscotch said:
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
Click to expand...
Click to collapse
Yes, at this time there's no way to obtain root without unlocking the bootloader.
rnscotch said:
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Click to expand...
Click to collapse
It can be relocked but then it'll be just "re-locked" not "locked", that means it'll have a different status.

Also note that you void the warranty just by obtaining the unlock code from Motorola; it doesn't matter if you've actually applied it to your device

If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?

LuizHenrique91 said:
If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?
Click to expand...
Click to collapse
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.

If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.

eskamhl said:
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.
Click to expand...
Click to collapse
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------
ooklathemok said:
If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.
Click to expand...
Click to collapse
Yes.. I'm considering to root mine X Play for be able to change the kernel and get the LED working (and maybe some optimizations). It's not prioritary, but I want. I won't install a custom ROM, because I like Moto Voice to much and I know we lost it.

LuizHenrique91 said:
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
Click to expand...
Click to collapse
Of course in that case you'll need to install the recovery and root, but as ooklathemok said you'll be able to update through a stock rooted rom simply from recovery

How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong

deaksfrost said:
How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong
Click to expand...
Click to collapse
Do not reboot to OS after flashing recovery, just reboot to recovery. If you reboot to OS after flashing twrp the stock Rom will over write recovery

Do Custom OS support Active/Moto Display and Moto voice?

yekollu said:
Do Custom OS support Active/Moto Display and Moto voice?
Click to expand...
Click to collapse
No, custom Roms do not support moto voice nor will they ever. Active display is all custom Roms provide.
This is my second moto x, I had the original moto x from 2013 and hated moto display.

Android 6.0 Marshmallow

Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.

joe1blue said:
Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.
Click to expand...
Click to collapse
You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool and take the ota them reroot
2) Wait for a flash able zip to become available.

TrenchKato said:
2) Wait for a flash able zip to become available.
Click to expand...
Click to collapse
Which will most likely be faster available than waiting for the OTA.

I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.

Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.
Click to expand...
Click to collapse
Chances are, if you unlocked your bootloader, you flashed a custom recovery. You can't take an OTA through a custom recovery -- not because it's "blocked," but because the OTA tool is not written to work with that recovery.

Could be. Easy enough to fix if so. Just tell TWRP to allow the OS to overwrite it, the reflash TWRP after the update.

Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!

jonathanbailie said:
Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!
Click to expand...
Click to collapse
A modified system will prevent the install. You would need to flash the system image as well.
Sent from my XT1575 using Tapatalk

I know some owners rooted their device for different reasons other than roms, but imo better to wait for 6.0 for OTA first. This phone comes with pure Android rom. Not like you need to remove bloat apps. Just need custom roms and kernels which is slow developing. Maybe the devs don't want to waste time with lp and their also waiting for marshmallow. I'm surprised how slow this device is moving under development. Oneplus one didn't have mass sale but their development was quick. Being so similar with nexus 6, hopefully we can get some love with MXP.
Sent from my XT1575 using XDA Free mobile app

I have been holding out on unlocking for this reason. I'm lazy and don't want to set everything up again so I will use Marsh to back everything up first then I will go to town

Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work.
Click to expand...
Click to collapse
OTA will not work for rooted MXPE's.
1) Rooting the MXPE requires you to load an alternative recovery (TWRP), which doesn't work with the OTA installation scripts.
2) Rooting the MXPE modified /system files. And OTA updates check /system integrity before it runs the update. Rooted phones will fail that integrity check, and will fail to OTA for that reason.
You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA. I'm sure that most people will do that, and then re-install TWRP and re-root after that is done. However, I'd recommend you wait a bit for other people to try this first, just in case there are any issues and to verify that root is still available in Android Marshmallow 6.0

Makes sense. Somebody has to be first. I will do a nandroid backup before attempting to update by any means.

Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.

hijax2001 said:
Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.
Click to expand...
Click to collapse
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?

PiousInquisitor said:
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?
Click to expand...
Click to collapse
Yup, you're correct ... I just used the tool earlier today and I do indeed have stock recovery.
Sent from my XT1575 using Tapatalk

Sharing my experience... good it's supposed to. Didn't for me, for some reason, until 2nd power cycle. It is stock recovery now though. Sorry for the confusion.

XT1575 Need advice - Relock bootloader, failure

Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Sent from my Portable

PassatSport15 said:
Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Click to expand...
Click to collapse
A few problems here... First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old, it's the original MM firmware from Moto's website (the one on Moto's site is very old and dated incorrectly). We don't have the 18-16 image yet, so you cannot relock or even effectively fix this.
Also, you used a tool to flash, so when pieces failed to flash, you didn't even know it... And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
When you relock a Moto device, you don't just enter "fastboot oem lock" like a Nexus device, there is a process where you start with "fastboot oem lock begin" then flash a complete, signed factory image, wipe, and end with "fastboot oem lock" in one process.
Many parts to this process went wrong... Right now you are just kind of stuck.
BTW, relocking the bootloader has no effective gains except security... You will still be able to see in a glance it was unlocked from the bootloader screen or a fastboot command and the unlocked bootloader warning screen will still be there (you have to flash a custom logo to make it go away).

Did you make a backup of your stock ROM with TWRP prior to rooting? Restoring the backup with TWRP along with stock recovery is usually going to be the simplest and easiest way to go back to full stock.
As acejavelin stated, there really is no benefit to relocking the bootloader except from a security standpoint. As long as the stock ROM and recovery are restored to preroot condition with no system mods, you can take OTAs regardless of bootloader status.

acejavelin said:
First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old
Click to expand...
Click to collapse
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
acejavelin said:
And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
Click to expand...
Click to collapse
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Sent from my Portable

PassatSport15 said:
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Click to expand...
Click to collapse
I think 18-12 is the latest we have so far, but trying to flash it would not help... Your best bet at this point is either custom ROM or wait until we can get the image for 18-16. The problem here is Moto's don't support downgrading, it can be done but it often leaves you in a mixed state.
You could try flashing the latest version we have available manually (don't use a tool) and it might be close enough to able to OTA from there. You have some though, rumor has it initial surveys for an upgrade on the Pure just went out to MFN users this week, assuming it is the Nougat upgrade trial then once it starts you have 4-6 weeks barring any problems they encounter before public release. Assuming of course that history repeats itself and Lenovo follows the same path as Moto has previously.
So basically I'm saying have patience... We don't know when (or really if) we will get the current firmware image, sometimes it's quick and sometimes it takes months.

Update on my xt1575, that I could not take an OTA, it gave me an error - unsuccessful.
My original software was MPHS24.49-18-16, December update, latest software.
Well, I went ahead unlocked the bootloader, installed TWRP, then rooted....
Days later I had decided to unroot, so I would be able to take the OTA.
While I unrooted my device, it was successful, but could not take the updates at all.
Now I reflashed again, in this order below.
Autoflash Script with MPHS24.49-18-8.
Reboot the phone, checked if it was unrooted (No root)
Now I went to software update, and the phone did it's upgrade, like last time. Did the update, device rebooted and it was SUCCESSFUL!
I am finally back to the original software MPHS24.49-18-16
Which was December 2016 update.
Sent from my Portable

G6 Play: Pie Soak Test

Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.

Could anyone verify?

Figures it's for Aljeter. Makes me wonder if Jeter will get it at all.

yes it is for aljeter and is working fine

Spaceminer said:
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
These installation steps need confirmation. I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Click to expand...
Click to collapse
Tested and working on G6 Play do Brasil!

Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.

Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)

Spaceminer said:
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Click to expand...
Click to collapse
Thanks @Spaceminer !!!! I'll give it a go. I thought at first that I might need to make some sort of patched boot image and faff about quite a bit but your instructions are clear and straightforward.
I must say I'm impressed with the G6 Play. I had a Nexus 6P and a Pixel both of which died on me from physical and customisation fatigue. I could afford a flagship so got this to see be through and I haven't had one complaint yet.
The handful of Pie features and esthetics have been implemented well by Motorola and battery life is still epic on this device.
Edit: rooted and fully set up how I usually have my daily driver handset. Pie is so tasty!

Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...

picopi said:
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
Click to expand...
Click to collapse
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.

madbat99 said:
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
Click to expand...
Click to collapse
Well yeah, I know that much. I meant the extra stuff like unlocking bootloader and downgrading the firmware etc lol. Ta for the extra info, mind.
Extra questions though because despite being having novice experience of doing phone flashing stuff, I've never touched a soak test for official firmware before...but I'm guessing I'll have to move back to Oreo temporarily to get the official Pie update...? Or will it just shift up from this soak test version?

Anyone get this working with the xt1922-7?

Donavonn said:
Anyone get this working with the xt1922-7?
Click to expand...
Click to collapse
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.

Spaceminer said:
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Click to expand...
Click to collapse
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?

Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working

Donavonn said:
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Click to expand...
Click to collapse
Yes, it should be possible on the first setup. I think if it works, LTE probably won't without an APN edit. That's what happens when I flash xt1922-5 RETUS firmware anyways.

picopi said:
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Click to expand...
Click to collapse
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.

Spaceminer said:
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Click to expand...
Click to collapse
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?

picopi said:
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
Click to expand...
Click to collapse
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.

Spaceminer said:
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Click to expand...
Click to collapse
Righto. In that case I'll report back with my findings, but yeah I'd imagine it should work fine as well. We'll see, fingers crossed.