If some of the more experienced people here could check my steps for returning to stock, I'd really appreciate it. I have some questions and also want to confirm that I correctly understand how to do some of the others. Thanks.
My XT-1575 is running 6.0 build number MPHS24-49-18-16. I would like to change ROMs (probably to Lineage OS 14.1) but be able to return to the same build at a later time. I do not want to update the Moto firmware to 7.0.
Steps:
1) Use the instructions in the thread: [GUIDE] [XT1575] Return to stock and relock bootloader by @acejavelin
2) Download the latest 6.0 factory image available (MPHS24.49-18-8) with the link in the thread and place it in the adb platform-tools directory
3) Open a command prompt in the platform-tools directory and issue the commands listed in the thread to flash the firmware. This will not lock the bootloader because this is an earlier build.
4) As shown in the thread, go to @annoyingduck's post (post #366) to get the OTA .zip to go from 18-8 to 18-16
5) This needs to be sideloaded.Is TWRP used for this? Will TWRP still be in recovery after running the commands in step 3? Do I need to flash TWRP to recovery? When I flash the OTA, will this replace TWRP with the stock recovery?
6) Is there an additional step(s) to lock the bootloader? The instructions say flashing an older build will fail at locking the bootloader. Instead, the OTA is flashed manually, but how does the bootloader get relocked?
7) Are there any additional steps to return to official status to pass safetynet and get OTAs?
xdafan15 said:
If some of the more experienced people here could check my steps for returning to stock, I'd really appreciate it. I have some questions and also want to confirm that I correctly understand how to do some of the others. Thanks.
My XT-1575 is running 6.0 build number MPHS24-49-18-16. I would like to change ROMs (probably to Lineage OS 14.1) but be able to return to the same build at a later time. I do not want to update the Moto firmware to 7.0.
Steps:
1) Use the instructions in the thread: [GUIDE] [XT1575] Return to stock and relock bootloader by @acejavelin
2) Download the latest 6.0 factory image available (MPHS24.49-18-8) with the link in the thread and place it in the adb platform-tools directory
3) Open a command prompt in the platform-tools directory and issue the commands listed in the thread to flash the firmware. This will not lock the bootloader because this is an earlier build.
4) As shown in the thread, go to @annoyingduck's post (post #366) to get the OTA .zip to go from 18-8 to 18-16
5) This needs to be sideloaded.Is TWRP used for this? Will TWRP still be in recovery after running the commands in step 3? Do I need to flash TWRP to recovery? When I flash the OTA, will this replace TWRP with the stock recovery?
6) Is there an additional step(s) to lock the bootloader? The instructions say flashing an older build will fail at locking the bootloader. Instead, the OTA is flashed manually, but how does the bootloader get relocked?
7) Are there any additional steps to return to official status to pass safetynet and get OTAs?
Click to expand...
Click to collapse
All of these questions are answered in the threads you referenced...
1) Yup, that's fine.
2) Same, remember to extract it... Although I would recommend extracting it to a unique directory and add platform-tools to your path
3) Correct, sort of... You cannot use an older firmware to lock, but there are specific commands to attempt a lock and to just flash. When downgrading be aware gpt.bin (partition table) and bootloader.img may fail and that is normal.
4) Yup, good there
5) Sideload in this regard is accomplished through stock recovery, start stock recovery and select "Apply update from ADB" then execute "adb sideload update.zip"
6) Your only option at this time to lock the bootloader is to flash a Nougat firmware image... We do not have a Marshmallow 18-16 image and without one you cannot lock the bootloader, no matter how much you downgrade.
7) "Official" status is not required to pass SafetyNet API check on Marshmallow or Nougat, but you must have a purely stock /boot, /recovery, and /system partition. On Nougat you must also have a locked bootloader. The only way to get back to "Official" status is to flash an official firmware image and then take an official OTA successfully.
Thanks for your help, @acejavelin! Some further clarifying questions-
acejavelin said:
3) Correct, sort of... You cannot use an older firmware to lock, but there are specific commands to attempt a lock and to just flash. When downgrading be aware gpt.bin (partition table) and bootloader.img may fail and that is normal.
Click to expand...
Click to collapse
I assumed I would just copy and paste the commands you provided exactly as listed. Is that OK? Or do I need to substitute the commands you showed at the bottom:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
Or it doesn't matter?
acejavelin said:
6) Your only option at this time to lock the bootloader is to flash a Nougat firmware image... We do not have a Marshmallow 18-16 image and without one you cannot lock the bootloader, no matter how much you downgrade.
Click to expand...
Click to collapse
And the way to do this is to flash NPH25.200-22 from adb fastboot as shown in your other thread, correct? Can I also take the Moto OTA from 18-16 (the one I am currently being offered)?
acejavelin said:
7) "Official" status is not required to pass SafetyNet API check on Marshmallow or Nougat, but you must have a purely stock /boot, /recovery, and /system partition. On Nougat you must also have a locked bootloader. The only way to get back to "Official" status is to flash an official firmware image and then take an official OTA successfully.
Click to expand...
Click to collapse
So you are saying that if I follow the instructions to return to 18-16 I will be able to recieve OTAs and will pass safetynet. Only downside is that my bootloader will remain unlocked?
By flashing the Nougat image, my bootloader can be locked (part of the sequence of commands)
but only by doing this plus accepting a future OTA will the status return to "official"?
[/QUOTE]
xdafan15 said:
Thanks for your help, @acejavelin! Some further clarifying questions-
I assumed I would just copy and paste the commands you provided exactly as listed. Is that OK? Or do I need to substitute the commands you showed at the bottom:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
Or it doesn't matter?
Click to expand...
Click to collapse
Using the 'oem lock' commands will fail, and it will get stuck in fb_mode that you have to clear. Better to just use the fb_mode commands up front.
xdafan15 said:
And the way to do this is to flash NPH25.200-22 from adb fastboot as shown in your other thread, correct? Can I also take the Moto OTA from 18-16 (the one I am currently being offered)?
Click to expand...
Click to collapse
Guess I am confused... if you flash NPH25.200-22 you won't be offered 18-16 OTA, but will likely be offered the NPHS25-201.1 update. If you are on 18-8 and are pure stock you can accept the 18-16 update, and within 24 hours after that is successfully applied you should be offered the Nougat update(s).
xdafan15 said:
So you are saying that if I follow the instructions to return to 18-16 I will be able to recieve OTAs and will pass safetynet. Only downside is that my bootloader will remain unlocked?
By flashing the Nougat image, my bootloader can be locked (part of the sequence of commands)
but only by doing this plus accepting a future OTA will the status return to "official"?
Click to expand...
Click to collapse
You can chose whether to lock the bootloader or not by flashing the Nougat image, the question is which do you want? Just flashing an image won't make your software status "official" in most cases. We have seen some cases where it does, but we don't know why and in most cases it will stay unofficial until you accept an OTA update, then somehow it miraculously becomes official. The key to remember here is once you accept an OTA that is a higher version than the stock images we have, you have no way to lock the bootloader, so if you want to lock your bootloader in your current state the only possible way is to flash the NPH25.200-22 image using the locking commands, because if you don't lock at this point and accept an OTA update you cannot relock the bootloader until (or if) we get a newer factory image.
One more thing to keep in mind, if you accept an OTA to Nougat or manually upgrade, and decide to downgrade to Marshmallow, it is possible, but once this is done do NOT accept any OTA updates back to Nougat, it will hard brick... and I mean perma-brick such that a mainboard replacement is necessary to fix it, which Moto won't do because you unlocked the bootloader, so basically the phone is trash.
@acejavelin, thanks again and sorry for asking so many questions. For those of us who only play around at this stuff, it is hard to keep this all in our heads. Especially since a wrong move can hard brick the phone as you mentioned.
acejavelin said:
Guess I am confused... if you flash NPH25.200-22 you won't be offered 18-16 OTA, but will likely be offered the NPHS25-201.1 update. If you are on 18-8 and are pure stock you can accept the 18-16 update, and within 24 hours after that is successfully applied you should be offered the Nougat update(s).
Click to expand...
Click to collapse
Interesting- You say if I return to stock 18-8, Moto will offer me the 18-16 OTA first, I won't be offered Nougat directly?
Since I would want to relock the bootloader, is there any reason not to just go directly from Lineage OS to NPH25.200-22?
The string of commands to issue (shown in the "return to stock" thread) is the same whether it is a MM or Nougat image that is being flashed, correct?
acejavelin said:
One more thing to keep in mind, if you accept an OTA to Nougat or manually upgrade, and decide to downgrade to Marshmallow, it is possible, but once this is done do NOT accept any OTA updates back to Nougat, it will hard brick... and I mean perma-brick....
Click to expand...
Click to collapse
If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?
Does it matter if the Nougat version I was originally on before downgrading was 200-22 vs 201.1?
Thanks again!
xdafan15 said:
@acejavelin, thanks again and sorry for asking so many questions. For those of us who only play around at this stuff, it is hard to keep this all in our heads. Especially since a wrong move can hard brick the phone as you mentioned.
Interesting- You say if I return to stock 18-8, Moto will offer me the 18-16 OTA first, I won't be offered Nougat directly?
Since I would want to relock the bootloader, is there any reason not to just go directly from Lineage OS to NPH25.200-22?
The string of commands to issue (shown in the "return to stock" thread) is the same whether it is a MM or Nougat image that is being flashed, correct?
If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?
Does it matter if the Nougat version I was originally on before downgrading was 200-22 vs 201.1?
Thanks again!
Click to expand...
Click to collapse
Yes
No
Yes, except watch the number of sparse chunks
Yes, as long as you flash the full image and not as an OTA.
No
I guess this conversation is going all over the place... are you wanting to return to stock and lock the bootloader or run a custom ROM? You can't really do both. If you want to return to stock, that depends on your current version, if you want to run custom there are less constraints. This is a 2 year old device, just pick one and go with it.
Thanks for your patience with me, @acejavelin.
My intent is to switch to Lineage OS now, but make sure I understand the correct steps to return to stock in the future if I want to. I wanted to confirm that info before everyone is gone from the Moto X Pure forum. I tend to keep my phones for a long time.
I think I've got it now, but I do want to ask 1 more clarifying question:
I asked "If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?"
and you answered
"Yes, as long as you flash the full image and not as an OTA."
Do you mean
(A) as long as I flash the full 25.200-22 image and then take the OTA (which motorola will offer to me at that point to get to 25-201.1),
OR
(B) did you mean after flashing the image to get to 25.200-22, I cannot take the OTA to 25-201.1, but must wait until (if) someone posts the image file for 25-201.1 and flash that?
Sorry for asking so many questions. I really appreciate it
xdafan15 said:
Thanks for your patience with me, @acejavelin.
My intent is to switch to Lineage OS now, but make sure I understand the correct steps to return to stock in the future if I want to. I wanted to confirm that info before everyone is gone from the Moto X Pure forum. I tend to keep my phones for a long time.
I think I've got it now, but I do want to ask 1 more clarifying question:
I asked "If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?"
and you answered
"Yes, as long as you flash the full image and not as an OTA."
Do you mean
(A) as long as I flash the full 25.200-22 image and then take the OTA (which motorola will offer to me at that point to get to 25-201.1),
OR
(B) did you mean after flashing the image to get to 25.200-22, I cannot take the OTA to 25-201.1, but must wait until (if) someone posts the image file for 25-201.1 and flash that?
Sorry for asking so many questions. I really appreciate it
Click to expand...
Click to collapse
Honestly, the smart bet would be to flash the NPH25.200-22 image, then do NOT take any OTA. Then go ahead and flash TWRP and LineageOS. You can always go back to the full image without issues of "downgrading".
At this time the 25.200-22 image is the newest we have and downgrading can never be perfect. If there is no reason to take the OTA (like you are going to just flash Lineage anyway), then don't take it... At least you have an easy out.
The main reason for this is we don't have an image for 25-201.2 and we don't know when, or even if, we ever will. For example, we never did get an image of Marshmallow 18-16 and at this point I doubt we ever will.
Thanks for the excellent support, @acejavelin! That's why I love XDA.
@acejavelin I was on official (stock) 7.0, build NPH25.200-23. I installed unofficial LOS 14.1 (by Hashbang) because I have the N modem, and official LOS 14.1 only supports the M modem. I later decided to go back to stock. As we all know the NPH25.200-23 factory images have not yet been (or ever will be) released, so I followed your guide on how to revert to stock, except I flashed the available NPH25.200-22 partitions (the ones that flashed, anyway, minus the ones that gave Preflash Validation Error) without relocking the bootloader, and now I am back to NPH25.200-22. I also immediately received the notification for the -23 OTA but I did not install it. My question is this: Can I accept the -23 OTA or will I risk bricking? I never downgraded to M, I only had unofficial LOS 14.1 builds, and now the stock -22 build.
My battery is acting all weird, shutting down at about 70%, plugging it again and showing 50%. When I boot, if I unplug it will immediately shut down. Basically it's plugged in the whole time. I have no idea what's causing this, the fact that I flashed unofficial LOS, or because of a faulty battery since I had changed it before flashing LOS), or because of partitions mismatch. So I'm trying to narrow it down and pinpoint the cause. But it seems that every time I try something, it makes the battery worse.
The battery is probably reaching the end of it's life...
You can accept the -23 OTA, the risks are minimal if everything you told me is correct.
acejavelin said:
The battery is probably reaching the end of it's life...
You can accept the -23 OTA, the risks are minimal if everything you told me is correct.
Click to expand...
Click to collapse
Thanks for the reply. Are you sure that taking the OTA on mismatched partitions (bootloader and gpt from -22 and everything else from -23) would not brick? There have been cases like that in the past (https://forum.xda-developers.com/moto-x-2014/general/warning-hard-bricking-downgrading-t3116379) on the Moto X 2nd Gen because the updater script did not have the correct checks to prevent a brick. Maybe it was the case when downgrading to a previous full version i.e. from 5.1 to 4.4.4, or just on older phones/older versions. Do we know if the updater script from -22 to -23 has to correct checks to prevent a brick?
discovery94 said:
Thanks for the reply. Are you sure that taking the OTA on mismatched partitions (bootloader and gpt from -22 and everything else from -23) would not brick? There have been cases like that in the past (https://forum.xda-developers.com/moto-x-2014/general/warning-hard-bricking-downgrading-t3116379) on the Moto X 2nd Gen because the updater script did not have the correct checks to prevent a brick. Maybe it was the case when downgrading to a previous full version i.e. from 5.1 to 4.4.4, or just on older phones/older versions. Do we know if the updater script from -22 to -23 has to correct checks to prevent a brick?
Click to expand...
Click to collapse
Your not downgrading... Either it will work or the checks will fail. The chances of bricking are minimal.
The issue of the MM vs. N modems is part of the reason I started this thread. My understanding was that official Lineage OS 14.1 would only work properly if the phone was still running MM firmware because LOS 14.1 was not configured to handle the N modem as written above by @discovery94. It seems like the unofficial LOS 14 by @Hashbang173 has some problems, so it seemed safer to stay on MM. But @acejavelin's advice to me was to upgrade to N before switching ROMS which would seem to severely limit choices of ROMs
I guess the options are stay on MM and have a large selection of ROMS (including official LOS 14.1)
or upgrade to N and only select form Hashbang's LOS, RR by LuisG, and AOSP EX by Obsolete1,
or maybe upgrade to N, then extract the modem from MM stock firmware and flash it to avoid the modem mismatch problem.
Have I summed this up properly?
acejavelin said:
Your not downgrading... Either it will work or the checks will fail. The chances of bricking are minimal.
Click to expand...
Click to collapse
So the OTA was unsuccessful. The recovery first showed installing update, then displayed "Error", and then the phone rebooted and displayed an update not successful screen (Images attached). I guess the only way is to use the factory images, but I won't even get my hopes up for that.
Related
My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.
I am able to flash stock firmware with fastboot, however recovery.img and boot.img always fail with "(bootloader) image signed with key bad key"... doesnt matter if its 139.48-49-64 or the nougat soak test. I have xt1625 US retail, i made sure im using the correct non-amazon US firmware...
It boots up and runs properly, and i can install twrp... however, im unable to install the OTA updates without stock recovery, so im stuck on NPJ25.93-11 instead of 14
anybody have any similar issue?
That error with the boot.img and recovery.img, if I recall, usually shows up - provided after the warning the log says they were flashed okay, then you shouldn't have any problems, as you've experienced.
Yup, you cannot install any OTA updates from Motorola once you've modified your system - you need to be on stock recovery and system. Unlocking your bootloader is okay, but modifying your recovery, kernel, or any other part of your system may stop the OTA from installing. Your possible options are to re-flash the 93-11 update and download the 93-14 OTA if it's available in your region, or fastboot one of the 93-14 ROMs in the Guides section (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
ourangashane said:
I am able to flash stock firmware with fastboot, however recovery.img and boot.img always fail with "(bootloader) image signed with key bad key"... doesnt matter if its 139.48-49-64 or the nougat soak test. I have xt1625 US retail, i made sure im using the correct non-amazon US firmware...
It boots up and runs properly, and i can install twrp... however, im unable to install the OTA updates without stock recovery, so im stuck on NPJ25.93-11 instead of 14
anybody have any similar issue?
Click to expand...
Click to collapse
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
pastorbob62 said:
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
Click to expand...
Click to collapse
Likely fastboot'ed one of the Nougat images in the Guides section; I've not seen any mentions of OTA updates in the US either - Canada and Brazil appear to have received it thus far, hopefully the US isn't far behind!
echo92 said:
Likely fastboot'ed one of the Nougat images in the Guides section; I've not seen any mentions of OTA updates in the US either - Canada and Brazil appear to have received it thus far, hopefully the US isn't far behind!
Click to expand...
Click to collapse
That would be my guess as well. I don't get why some are so impatient to get Nougat that they risk flashing firmware not intended for their devices. Then they wonder why they are having issues. Oh well!
pastorbob62 said:
When and how did you get the Nougat update for the XT1625? I am on stock and have not received it, nor have I seen any update from Motorola available for it.
Click to expand...
Click to collapse
No, no update yet.... i just flashed the indian version from the forum..
echo92 said:
That error with the boot.img and recovery.img, if I recall, usually shows up - provided after the warning the log says they were flashed okay, then you shouldn't have any problems, as you've experienced.
Yup, you cannot install any OTA updates from Motorola once you've modified your system - you need to be on stock recovery and system. Unlocking your bootloader is okay, but modifying your recovery, kernel, or any other part of your system may stop the OTA from installing. Your possible options are to re-flash the 93-11 update and download the 93-14 OTA if it's available in your region, or fastboot one of the 93-14 ROMs in the Guides section (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
Click to expand...
Click to collapse
Had i just used my eyes lol... Id been looking for a fastboot 93-14, i must have been way too tired lol.. thank you
Hi!
I have got two G4, one with Marshmallow and one with Nougat.
The one on N (offical N, updated by OTA and did a full wipe) has lots of problems with BT, and I want to downgrade it to MM.
I have read lots of posts, here and everywhere else, and saw some vids about the procedure. But I still have some doubts about the proccess:
* Most of the procedures I have read relate to downgrade from N leak to MM in order to upgrade to official N. I have seen someone ask if the same procedure could be used to downgrade from offical N, but no answer. Can I use the same procedure to downgrade from official N?
* Some say you have to unlock the bootloader, others make no mention of it. Some say you should not write gpt.bin and bootloader from the MM ROM as N udated them and it is not possible to downgrade them. Do I have to unlock the bootloader before using fastboot to write the MM ROM? Should I avoid writing gpt.bin and bootloader?
I don't mind voiding the phone warranty, and I don't mind not being able to OTA update future versions.
Thank you very much.
Regards.
If you have bootloader locked, you can't overwritte nothing including system, boot, bootloader and gpt. I tried with my Moto G4 and i can't go back from official N to official MM through fastboot
Thank you.
So I understand I have to unlock the bootloader.
Now I just need to make sure if I should overwrite gpt and bootloader with MM versions (coming from stock N) or not.
Regards.
CalvinH said:
Thank you.
So I understand I have to unlock the bootloader.
Now I just need to make sure if I should overwrite gpt and bootloader with MM versions (coming from stock N) or not.
Regards.
Click to expand...
Click to collapse
A couple of weeks ago, I read something about it. I think you should not overwrite the bootloader and recovery but I do not remember very well.
But if you have your bootloader unlocked just flash (or boot into) a custom recovery and make a backup of everything and after play along a while
lerg96 said:
A couple of weeks ago, I read something about it. I think you should not overwrite the bootloader and recovery but I do not remember very well.
But if you have your bootloader unlocked just flash (or boot into) a custom recovery and make a backup of everything and after play along a while
Click to expand...
Click to collapse
Thank you.
Based on the overwhelming popularity of this thread (thanks lerg96!) I have decided to come back and tell how it went.
I had a Moto G4 with official Nougat. I wanted to downgrade it to MM.
The first problem is that I didn't find the .63 ROM (last MM one) for my device (XT1622). I found the 23.5 version (previous one), and the .63 version for the XT1624. Since 22 and 24 differ on LTE bands and so, I decided to use the older but right ROM.
First attempt: downgrade without unlocking bootloader... NO WAY.
Second attempt: unlock bootloader + downgrade without overwriting bootloader and gpt.bin. :good::good:
I got the boot warning message, but everything went ok and my BT problems are gone. I got the .63 OTA notification, but didn't installed it as I read scary histories about doing it.
Regards!
now that your bootloader is unlocked, install TWRP and make a backup of your system. I used TWRP to restore my OS. I went from Nougat back to MM, I am sure you can go the other way around too.
also, the fastboot method for reload the os seems to work well on phones with unlocked bootloaders.
Does anyone know about this ?
The last version of the firmware that got OTA'ed to my phone is POTTER_RETAIL_7.0_NPNS25.137-93-8.
The only twrp backup of the firmware I have is while it was on POTTER_RETAIL_7.0_NPNS25.137-93-4.
When I tried to flash the phone with v 93-4 using fastboot, I got denied because of the version being older than that of the bootloader. But the problem is that I was able to erase prior to attempting writing ...
I need to re-install a stock rom in the phone, but POTTER_RETAIL_7.0_NPNS25.137-93-8 cannbot be found anywhere yet.
I though about twrp-flashing the phone with my 93-4 backup, but I am hesitant, I fear bricking the phone.
Is there any alternative to patience while waiting for POTTER_RETAIL_7.0_NPNS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip eventually appearing somewhere ?
Or, in other words, knowing that the last OTA to my phone installed v 93-8, is there any way to flash POTTER_RETAIL_7.0_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip for instance ?
CanadianGixxerman said:
I though about twrp-flashing the phone with my 93-4 backup, but I am hesitant, I fear bricking the phone.
Click to expand...
Click to collapse
An older version (your twrp backup) will work with a newer bootloader, however you can't do any OTAs. An OTA will try to apply the same changes to the bootloader that were already made, resulting in a hard brick - though the OTA would fail anyway since you don't have an intact /oem partition. You will have a functional phone, and you can get back on track after 93-8 images or Oreo are released.
I know because I'm in a similar situation. I wanted to update from 93-4 to 93-8, and I had an intact /system image backup, but /oem was mounted before so I had to flash it via fastboot. Little did I know it was from the wrong channel (retus instead of reteu), resulting in the OTA updating everything except for oem and messing stuff up, so I just flashed a 93-4 twrp backup. Everything works, patiently waiting for Oreo.
bazinga137 said:
I just flashed a 93-4 twrp backup.
Click to expand...
Click to collapse
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
craigl14 said:
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
Click to expand...
Click to collapse
Honestly, I am not sure. I did a twrp back up with the default selected partitions. But it turned out that this backup is not reliable. The phone does boot up on it, but suffers from applications crashes all over. Last I discovered is that the phone itself was not working for a phone, meaning making receiving calls is not possible.
craigl14 said:
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
Click to expand...
Click to collapse
It needs to be an image backup for OTAs. Unlike a regular backup, image backups are block-by block pristine copies, and restoring them preserves dm-verity and all /system checks. On the other hand the /oem partition cannot be backed up as an image (I asked GtrCraft, the official maintainer of twrp for some moto devices), and since OTAs also check if /oem has been tampered with, the update fails.
Updates will only pass if /oem has never been mounted, and you have a system image backup.
bazinga137 said:
It needs to be an image backup for OTAs. Unlike a regular backup, image backups are block-by block pristine copies, and restoring them preserves dm-verity and all /system checks. On the other hand the /oem partition cannot be backed up as an image (I asked GtrCraft, the official maintainer of twrp for some moto devices), and since OTAs also check if /oem has been tampered with, the update fails.
Updates will only pass if /oem has never been mounted, and you have a system image backup.
Click to expand...
Click to collapse
Dumb question...How do I know if the oem partition is tampered with or has never been mounted? I am rooted with elementalx kernel and supersu. TWRP partition stock backup made immediately after taking 93-8 update and before flashing twrp, rooting, etc. I know I am hosed without the system IMAGE as far as ota's go, but I'm just trying to learn.
I'm in the same boat. Pretty much stuck on 93-8 forever until a new full image is released somewhere. I might just move onto a custom Oreo rom.
dunderball said:
I'm in the same boat. Pretty much stuck on 93-8 forever until a new full image is released somewhere. I might just move onto a custom Oreo rom.
Click to expand...
Click to collapse
Well, I did that. I have tried a few cutom roms : Pixel Exprerience, Resurection Remix, AOSP extended, AOSiP and Dirty Unicorns. The latter and AOSiP are those I find the most reliable. Avoid PE and RR, too buggy, AOSP-E has issues with SIM/SDcard here.
But I will want to go back to stock moto rom when I can (ie : full 93-8 load fastboot flashable is released).
If moto had been quicker to release Oreo AND fix the wifi bug, I would not have given up on retus.
I guess I have an even more fundamental dumb question than my twrp restore issue and maybe it belongs in another thread. Aside from advanced excel formulas, I have no programming experience of any kind, let alone android. However, it seems to me that if I have a full firmware package for 93-4 (which I do) and a "blur" ota update file that takes it to 93-8 (which I do), I should be able to create a full 93-8 firmware package file myself from those two files without waiting on the file hosting sites. Maybe this is way too advanced a process but it seems to me this is 1+2=3 variety.
craigl14 said:
I guess I have an even more fundamental dumb question than my twrp restore issue and maybe it belongs in another thread. Aside from advanced excel formulas, I have no programming experience of any kind, let alone android. However, it seems to me that if I have a full firmware package for 93-4 (which I do) and a "blur" ota update file that takes it to 93-8 (which I do), I should be able to create a full 93-8 firmware package file myself from those two files without waiting on the file hosting sites. Maybe this is way too advanced a process but it seems to me this is 1+2=3 variety.
Click to expand...
Click to collapse
Your device now being at 93-8 is what's in the way. It seems like you can restore your twrp 93-4 on it, but you won't be able to relock the BL, hence OTA will not work.
CanadianGixxerman said:
Your device now being at 93-8 is what's in the way. It seems like you can restore your twrp 93-4 on it, but you won't be able to relock the BL, hence OTA will not work.
Click to expand...
Click to collapse
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
I'm on a slightly same boat as OP, but I don't have my backup since I thought it was on my SD and wiped my phone, with the backup only there. I was on 93-8 when I wiped. Would getting a 93-4 backup work?
This question might of been answered but I did not see it when I read through this thread.
craigl14 said:
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
I took a full backup of my system image through twrp, and I was on 93-8. I'll upload it when I have time and you can give it a try.
CanadianGixxerman said:
[...] but you won't be able to relock the BL, hence OTA will not work.
Click to expand...
Click to collapse
Why would you need to relock the BL to take an OTA?
craigl14 said:
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
Sadly you can't apply an OTA to the firmware images, if that's what you're thinking. They need to be signed by moto to be flashable through fastboot. And if you'd want to provide someone with a twrp backup of a firmware higher than theirs, their bootloader would need to be updated too, via an OTA.
bazinga137 said:
if that's what you're thinking.
Click to expand...
Click to collapse
Thanks. That's exactly my question. So the answer is that Motorola controls the process. Makes sense. Any thoughts on my oem mounting question?
craigl14 said:
Thanks. That's exactly my question. So the answer is that Motorola controls the process. Makes sense. Any thoughts on my oem mounting question?
Click to expand...
Click to collapse
I really can't think of a way of checking the mount count of Android partitions, and I haven't found anything online.
I discovered the mount counter thingy when sweeping through logs of a failed OTA. I'm really not sure where the OTA script reads it from.
craigl14 said:
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
I made a full backup of 93-8, but still i can't lock bootloader. We need complete firmware, until then, Lineage OS is the answer.
---------- Post added at 11:55 PM ---------- Previous post was at 11:52 PM ----------
bazinga137 said:
Why would you need to relock the BL to take an OTA?
Click to expand...
Click to collapse
No idea, i saw this first time now on Motorola. On any other manufacturers i could lock bootloader, and even get OTA updates just by flashing stock recovery and having unlocked bootloader was not a problem.
If your device was formally updated to NPNS25.137-93-8 (March 2018 security patch), then you could try to flash the NPNS25.137-93-4 (Jan 2018 security patch) update again as you previously tried (link to the Jan 2018 stock firmware for EU/US and Asia devices: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ ). You may wish to ignore the security downgrade errors (you cannot downgrade bootloaders anyway, presumably to prevent you opening security vulnerabilities) when you flash, which should just be for GPT and bootloader. You may also see 'image signed with bad key' for recovery and boot as well, but verify those partitions, and the other partitions report [OKAY] after flashing. That way, you should have a NPNS25.137-93-4 system, with a NPNS25.137-93-8 bootloader, and when you boot you should have a device reporting with fully stock NPNS25.137-93-4. The next OTA you should receive is the NPNS25.137-93-8 OTA and then the NPNS25.137-93-10 April 2018 security patch OTA, which should bring you up to the latest stock firmware.
By reflashing the NPNS25.137-93-4 firmware, this should also restore your OEM partition to being untampered (read only status?), as should your system partition (which should be read only, I recall that swiping to allow modifications in TWRP sets your system partition to read-write, which causes the OTA to fail).
Normally, I would advise against downgrading and using OTA updates, as this is a prime way of hard bricking. However, in this case you are downgrading your device firmware to the firmware directly preceding the newest firmware you had (i.e. downgrading to NPNS25.137-93-4 from NPNS25.137-93-8), with the next OTA being NPNS25.137-93-8, which brings you back up to the build you had, this may be safe. To your device, you are flashing the same bootloader from the NPNS25.137-93-8 OTA as currently on your device, which should not hard brick.
If you previously had stock NPNS25.137-93-10, then I cannot recommend this procedure as you'll be downgrading two firmware versions (and you'll have to wait for newer stock firmware to be leaked), else if you try flashing NPNS25.137-93-4 onto the April 2018 firmware and try using OTA updates, you may hard brick and have a pricey paperweight. I also do not know if this will work by cross-flashing from the NPN25.137-92 series of updates either.
Of course, as the NPNS25.137-93-4 firmware is older than your bootloader, you will not be able to re-lock your bootloader (you'll need a newer firmware, probably the April 2018 or newer security patch stock firmware), but being back on full stock, you should be eligible for OTAs provided you only downgraded from NPNS25.137-93-8 (and that March 2018 security patch was the latest stock firmware on your device).
If you are truly concerned about hard bricking, then I would follow other member's suggestions in this thread and stay with TWRP flashables of the stock ROM, as they do not usually affect the bootloader.
Any questions or comments before you perform this procedure, please ask.
bazinga137 said:
I really can't think of a way of checking the mount count of Android partitions, and I haven't found anything online.
I discovered the mount counter thingy when sweeping through logs of a failed OTA. I'm really not sure where the OTA script reads it from.
Click to expand...
Click to collapse
Thanks. Weird. Sorry for hijacking this thread. But if my process were to take OTA after which it reboots, then IMMEDIATELY reboot into bootloader, fastboot BOOT into twrp (not flash it) and take a backup of boot, logo, oem, recovery and system (FULL IMAGE), how would that change oem?
CanadianGixxerman said:
Well, I did that. I have tried a few cutom roms : Pixel Exprerience, Resurection Remix, AOSP extended, AOSiP and Dirty Unicorns. The latter and AOSiP are those I find the most reliable. Avoid PE and RR, too buggy, AOSP-E has issues with SIM/SDcard here.
But I will want to go back to stock moto rom when I can (ie : full 93-8 load fastboot flashable is released).
If moto had been quicker to release Oreo AND fix the wifi bug, I would not have given up on retus.
Click to expand...
Click to collapse
What's buggy about PE? I was just about to try it...
I am not responsible for your bricked phone or pigeon poo on your toupe. Do at your own risk.
Many thanks to @SupahCookie for idea and motivation!
INTENTIONALLY DOES --NOT-- LOCK BOOTLOADER!!!
Get factory images here:
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
THIS GUIDE IS FOR FACTORY/STOCK ROMs - NOT YOUR AVERAGE CUSTOM ROM which may not have bootloaders!!! (thanks!!!!! @echo92 )
FIX:
IF YOU ARE ABLE TO GET TO FASTBOOT THIS SHOULD WORK.
IF YOU HAVE 8.x bootloaders AND ARE DOWNGRADING TO 7, use "Alternative to RSDlite" below.
1 boot to win - 7 or 10 works fine.
2 boot phone to fastboot, and connect phone to computer.
3 start RSDlite
pick a ROM. I believe I used a 7.1.1 rom
3Nov9-ADDISON_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RSDlite installed it and fixed the problem.
- -
I was then able to use RSDlite to install @rafikowy 's signed 8.0 . - going up from 7 to 8.
- -
- -
If you are on 8.x bootloaders and want to go to 7.x bootloaders, use this (RSDlite throws an error and stops):
ALTERNATIVE TO RSDlite:
1 I used 7zip to extract that 7.1.1 zip (or any ROM zip) into a folder x,
2 add all the adb and fastboot junk to folder x,
3 add the attached file (rename it to flash.bat) to folder x.
4 boot phone to fastboot and connect to computer.
5 click on flash.bat - it throws a lot of "slot" errors but works just fine.
6 reboot your phone if it hasn't already and go through the 7.x install stuffs.
7 you will not show an IMEI if you are coming from an 8.x bootloader. However, it IS there.
NOTE: you may need to add a line to the flash.bat if there are more/less sparsechunk's in your FACTORY/STOCK ROM...
THIS IS NOT FOR CUSTOM ROMs!!!!!!!
EDIT: 3-8-19: I just did this myself to go back very briefly to 7.1 - be sure you don't flash TWRP to it if your going to take OTAs - it will brick it. boot to TWRP if you need TWRP briefly: fastboot boot twrpimg.img
----------
If you can boot to fastboot screen, you can do anything.
Never OTA a ROM if you have modified recovery (TWRP, etc) or if magisk is present.
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
I changed the attached file to add pause and reboot and exit to make it slightly more automated.
I have successfully used this many times going back and forth. If you can boot to fastboot screen, you can save your phone and flash anything you want.
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
echo92 said:
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
Click to expand...
Click to collapse
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
KrisM22 said:
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
Click to expand...
Click to collapse
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
YES - that's why I wrote these 3 guides - before, it was quite possible to wind up with a bootloader mix - esp depending on the zip you use! - factory/stock only!!!
I added a line to the guide saying that it is only intended to be used for the factory/stock zips as these have (I believe) the bootloaders appropriate to the ROM.
Many thanks for pursuing this! - I wonder if we'll have to exclude certain ROMs that are in the factory lists?????
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device
Click to expand...
Click to collapse
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
KrisM22 said:
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
Click to expand...
Click to collapse
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
echo92 said:
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
Click to expand...
Click to collapse
Downgrading is a piece of cake if you don't use RSDlite - it throws an error and stops. Using the bat file it can happily throw all the errors it wants and all I care is at the end I have what I want.
It does indeed change the entire environment when you bat file the zip contents. You can bat file to get from 8 to 7 and then use RSDlite to flash a different 7 OR 8 zip file. There is no resulting difference in whether you RSDlite it or bat file it - the bat file simply comes from the .xml file that is within the zip. There is very little or no difference between that among addison factory/stock zips. Other zips are different (custom ROMs.)
Grab any factory/stock zip for addison and expand it and you will see modems, bootloaders, indeed absolutely everything you would find on that phone if you went to a store and bought it. SupahCookie simply added a couple lock command lines because it was intended for folks who somehow thought that if phone was locked they could take it back to the store and get their money back. Or some such. I found that ATT folk didn't care if you were on CM or whatever if you just needed to swap SIMs or whatever.
I DON'T want to lock the phone as it prevents me from modifying forever. Oh yeah that reminds me I was going to post the obligatory guide (again) about how to flash a white boot logo so you don't get that message - it's still there LOL but since the font is in white, you can't see it.
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Necrowr said:
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Click to expand...
Click to collapse
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
KrisM22 said:
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
Click to expand...
Click to collapse
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Necrowr said:
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Click to expand...
Click to collapse
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
or
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
might have some stock ROMs of interest...
KrisM22 said:
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
might have some stock ROMs of interest...
Click to expand...
Click to collapse
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
Custom ROMs won't usually update the bootloader (even if they are newer) as stock ROMs typically only have the bootloader firmware.
You could look into flashing the stock Oreo albus 8.0 ROM https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 or the 8.0 June 2018 firmware https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 but please check that firmware has been released for your device variant.
I don't know if updating your baseband to stock Oreo formally may fix your IMEI issue.
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
KrisM22 said:
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
Click to expand...
Click to collapse
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Necrowr said:
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Click to expand...
Click to collapse
If you flashed a stock O that would have changed bl to O, but doing the above with the stock 7.1.1 would have changed them back to N. No matter (other than academic) that you don't remember the path - flashing a stock anything reverts it to that point in time. However, IMEI may have been moved - don't know. It will likely show on EITHER 7.x or 8.x stock - just don't know which.
If you flash a stock 8.x from those links I gave you above, it should offer you ota, ASSUMING there are any at this point in time(Z has 2). Adding Magisk at any point seems to hose you for receiving any more ota's - don't understand why, even with magisk uninstall, so that would mean going back to the latest stock and losing what you have (which is why I try to take a TBPro and copy that backup to PC (because re-flashing 8.x stock will likely reset internal storage.).
yes, if you enter stock recovery, you are likely at stock, though you could reflash the latest 7 or 8 stock to be sure, depending on which you want to use as base. Since 8 is having security fixes released, I choose 8 and will likely have no more interest (no time!) in 7.
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Necrowr said:
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Click to expand...
Click to collapse
did it offer to let you d/l it again? you could try that.
However, there exist O stock zips in those links I gave you so you could just flash the latest...