Database Develop

Unable to downgrade bootloader to get LMY47M OTA

I am ever impatient. So when I saw new factory images up on the Google page, I just had to try them out. I upgraded to LMY47E, then naturally the next day I saw the news about LMY47M. Being that I'm a T-Mobile customer, I want the M version (reported the T-Mobile version) of the new 5.1. Unfortunately, as part of the LMY47E upgrade, the bootloader was moved from 71.05 to 71.08.
Now, trying to flash factory images from LRX22C results in a bootloader mismatch error. I got around this by manually flashing radio, system, boot, etc. images on the phone, and I do in fact now have the 5.01 build showing. However, when I try to sideload the LMY47M build, I'm receiving an error from this line in the updater script:
Code:
#getprop("ro.build.fingerprint") == "google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys" ||
abort("Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
It's stating that I have 5.0.2 LRX22G signed with test keys. I don't know how I would have got an engineering build installed from flashing factory firmware from the Google page, but apparently something is confused somewhere along the way. The best I can guess is that perhaps that's some leftover remnants from when I had installed a CM12 nightly build (which I believe is based on 5.0.2).
I don't know what I need to flash with what to get that cleared so I can sideload the LMY47M OTA, and I'm concerned that I may be unable to properly upgrade to additional OTA upgrades if there's a missmatch along the way. There was a confirmed update coming to move from LMY47E to LMY47M per T-Mo support , also confirmed by @askdes) but again, if I have some funky mismatched stuff, unsure if I can upgrade to LMY47E again and still expect to receive the OTA.
I'd love to have someone with more knowledge of these wonderful things weigh in on this. Educated opinions are always welcome, but someone with actual first-hand knowledge would be incredibly helpful to my sanity as well.
Thanks!

Theres nothing you can do to receive the OTA now.
Maybe the M factory image will become available. If so, you'll be able to flash that. Well at least the system and boot image. If the bootloader is newer, that too.
I suppose the other options are that if someone could install TWRP with an unmodified, unrooted M on, they could take a backup of system and boot and give you them to do a Nandroid restore via TWRP... Or maybe someone can take a system dump for you. But you cannot downgrade the bootloader.

mikecole79 said:
I am ever impatient. So when I saw new factory images up on the Google page, I just had to try them out. I upgraded to LMY47E, then naturally the next day I saw the news about LMY47M. Being that I'm a T-Mobile customer, I want the M version (reported the T-Mobile version) of the new 5.1. Unfortunately, as part of the LMY47E upgrade, the bootloader was moved from 71.05 to 71.08.
Now, trying to flash factory images from LRX22C results in a bootloader mismatch error. I got around this by manually flashing radio, system, boot, etc. images on the phone, and I do in fact now have the 5.01 build showing. However, when I try to sideload the LMY47M build, I'm receiving an error from this line in the updater script:
Code:
#getprop("ro.build.fingerprint") == "google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys" ||
abort("Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
It's stating that I have 5.0.2 LRX22G signed with test keys. I don't know how I would have got an engineering build installed from flashing factory firmware from the Google page, but apparently something is confused somewhere along the way. The best I can guess is that perhaps that's some leftover remnants from when I had installed a CM12 nightly build (which I believe is based on 5.0.2).
I don't know what I need to flash with what to get that cleared so I can sideload the LMY47M OTA, and I'm concerned that I may be unable to properly upgrade to additional OTA upgrades if there's a missmatch along the way. There was a confirmed update coming to move from LMY47E to LMY47M per T-Mo support , also confirmed by @askdes) but again, if I have some funky mismatched stuff, unsure if I can upgrade to LMY47E again and still expect to receive the OTA.
I'd love to have someone with more knowledge of these wonderful things weigh in on this. Educated opinions are always welcome, but someone with actual first-hand knowledge would be incredibly helpful to my sanity as well.
Thanks!
Click to expand...
Click to collapse
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.

clairez said:
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
Click to expand...
Click to collapse
Thank you both for the replies. My course at this point seems to be "wait until M is up on the factory images page", which is what I suspected.
I have done a full factory flash of the LRX22C image, manually (since the script fails because of the newer bootloader) and it has still left me with the engineering build stamp showing. Any idea where that information is coming from? The image I used to flash back was the LRX22C for Shamu from developers <dot> google <dot> com/android/nexus/images. I would think that would have wiped the world (exception of the bootloader that doesn't know how to travel back in time; should really introduce that thing to Doc....). I'm not sure if it's because of the bootloader itself, or because of some other thing that just didn't get wiped properly. I flashed the radio, boot, cache, recovery, userdata, and system images initially, then re-flashed recovery to TWRP 2.8 after. Where does ro.build.fingerprint get it's information from? Is that all from the bootloader?

clairez said:
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
Click to expand...
Click to collapse
But you can not flash an older bootloader So far for the developer phone At least HTC has S-Off.

gee2012 said:
But you can not flash an older bootloader So far for the developer phone At least HTC has S-Off.
Click to expand...
Click to collapse
I could be wrong (often am), but I thought several folks tried and succeeded with a factory image flash, by using the following methodology:
1. If your phone is showing OEM Unlock in the developer options and you can boot into recovery, then
2. Boot into android and remove all security
3. Set OEM Unlock and USB debugging
4. Perform several reboots to ensure OEM Unlock is persistent (if not, do not proceed)
5. Perform a factory reset/data wipe in recovery
6. Reflash the 5.01 factory image (or wait for 5.1 M version) using the manual method located here:
[TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader
http://forum.xda-developers.com/nexu...shamu-t2954008
* Use Method 2 from this tutorial, Method 1 does not work
7. You can relock the bootloader as outlined in the tutorial.
8. At this point if all went as expected, the N6 is factory fresh and eligible for the OTA.
But before you proceed check out some of the other posts to ensure that others have succeeded. So many reports of bricked phones it is hard to tell what caused the problem.
I have used the above method several times, but only reflashing to a newer version.
Hope this helps ....
PS: I missed the mention of CM12! There are so many variables in your situation, I am unsure now that there is a way back. So many of the hard bricked cases involved CM12. Good luck, I hope you come out of this right side up!

mikecole79 said:
Thank you both for the replies. My course at this point seems to be "wait until M is up on the factory images page", which is what I suspected.
I have done a full factory flash of the LRX22C image, manually (since the script fails because of the newer bootloader) and it has still left me with the engineering build stamp showing. Any idea where that information is coming from? The image I used to flash back was the LRX22C for Shamu from developers <dot> google <dot> com/android/nexus/images. I would think that would have wiped the world (exception of the bootloader that doesn't know how to travel back in time; should really introduce that thing to Doc....). I'm not sure if it's because of the bootloader itself, or because of some other thing that just didn't get wiped properly. I flashed the radio, boot, cache, recovery, userdata, and system images initially, then re-flashed recovery to TWRP 2.8 after. Where does ro.build.fingerprint get it's information from? Is that all from the bootloader?
Click to expand...
Click to collapse
I am in the same situation as you are, mine shows my build fingerprint as "google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy020120939:eng/test-keys" I have gone through the same steps as you have and tried to reflash LRX22C. I guess we wait until the factory image!

wadsface said:
I am in the same situation as you are, mine shows my build fingerprint as "google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy020120939:eng/test-keys" I have gone through the same steps as you have and tried to reflash LRX22C. I guess we wait until the factory image!
Click to expand...
Click to collapse
Have you flashed a custom kernel? Sounds like a non-google boot.IMG or something is on the device.

clairez said:
4. Perform several reboots to ensure OEM Unlock is persistent (if not, do not proceed)
Click to expand...
Click to collapse
That is absurd.
Unlocked is unlocked is unlocked.
The only thing that may not be persistent is the flag in the dev settings menu, ENABLE oem unlock.
Once you enable the unlock, you may *immediately* try to unlock it. If the enable setting isn't persistent, then it just won't unlock.
ONCE IT IS UNLOCKED, IT IS UNLOCKED. DON'T EVER LOCK IT AGAIN.

I also received that error when trying to sideload the OTA. The only modification I made was using a custom kernel, but I flashed the stock boot.img before attempting to sideload. So I'm not sure what could have caused the error?
I just read somewhere that we can get the sideload to work if a line in the updater script is deleted or modified. Has anyone else read this?

To sideload an OTA you need a stock recovery. I have been unable to sideload an OTA with a custom recovery installed since 5.0. The Dees Troy (guessing TWRP recovery) in the path is a dead giveaway that it is from the recovery. I don't think it is checking bootloader version when sideloading OTA.

android_mp99 said:
TI don't think it is checking bootloader version when sideloading OTA.
Click to expand...
Click to collapse
It is. OTA doesn't replace the bootloader. It patches the existing BL with the deltas - I.e. the code that have changed. Obviously the bootloader must be the exact expected version for a patch to work, so it is definitely being checked when you install an OTA, no matter what method you use..
If you patched the BL with an incorrect patch, you could very easily be facing a brick.

Then I'm guessing the people that were able to sideload the OTA with the new bootloader got lucky or are talking a bunch of BS (totally possible). I haven't tried it myself but I know for sure that the stock recovery is needed to sideload the OTA since 5.0 and the error reported earlier by some could be because of the recovery installed.

You definitely need stock recovery, yes

Since I have never updated my bootloader, I'm inclined to think it must be recovery. I was trying to sideload via TWRP.

doitright said:
[snip]
ONCE IT IS UNLOCKED, IT IS UNLOCKED. DON'T EVER LOCK IT AGAIN.
Click to expand...
Click to collapse
There are many reasons that people want to have a locked bootloader, such as, among many other reasons, your employer requires it, for example.
rootSU said:
It is. OTA doesn't replace the bootloader. It patches the existing BL with the deltas - I.e. the code that have changed. Obviously the bootloader must be the exact expected version for a patch to work, so it is definitely being checked when you install an OTA, no matter what method you use..
If you patched the BL with an incorrect patch, you could very easily be facing a brick.
Click to expand...
Click to collapse
No, OTA updates do not verify which bootloader your device is running, and they do NOT patch the bootloader -- they fully replace it.

android_mp99 said:
Then I'm guessing the people that were able to sideload the OTA with the new bootloader got lucky or are talking a bunch of BS (totally possible). I haven't tried it myself but I know for sure that the stock recovery is needed to sideload the OTA since 5.0 and the error reported earlier by some could be because of the recovery installed.
Click to expand...
Click to collapse
rootSU said:
You definitely need stock recovery, yes
Click to expand...
Click to collapse
You can use TWRP as well. It just requires an edit to one line in the updater-script file.

efrant said:
There are many reasons that people want to have a locked bootloader, such as, among many other reasons, your employer requires it, for example.
No, OTA updates do not verify which bootloader your device is running, and they do NOT patch the bootloader -- they fully replace it.
Click to expand...
Click to collapse
Yes you're right, my mistake.
efrant said:
You can use TWRP as well. It just requires an edit to one line in the updater-script file.
Click to expand...
Click to collapse
You need to have stock recovery to apply a stock ota. You could edit the updater-script for any amount of purposes, but that isn't really the point. The people who simply want to "check for updates" and use the standard mechanism to apply it, it will not work with twrp.

rootSU said:
You need to have stock recovery to apply a stock ota. You could edit the updater-script for any amount of purposes, but that isn't really the point. The people who simply want to "check for updates" and use the standard mechanism to apply it, it will not work with twrp.
Click to expand...
Click to collapse
Yeah, ok, but we were talking about sideloading the OTA, no? You can sideload an OTA update file (or even flash it directly from your device) using TWRP just by editing one line. But yes, as far as clicking on "check for updates" and having it install that way requires the stock recovery.

efrant said:
Yeah, ok, but we were talking about sideloading the OTA, no? You can sideload an OTA update file (or even flash it directly from your device) using TWRP just by editing one line. But yes, as far as clicking on "check for updates" and having it install that way requires the stock recovery.
Click to expand...
Click to collapse
You technically can. But then you edit the line, side load the ota via twrp, and immediately flash SuperSU to stop the updated system image from replacing the recovery.. It all seems a little pointless to me. If you're going to modify an ota (or download a modified ota) to side load from custom recovery rather than use a pre-rooted ROM.zip, it seems to add unnecessary steps.

[Q] [XT1053] How to get 5.1 back. Already updated once to 5.1

Hello,
Please help me get any OS back to my XT1053 for now. Here's what happened:
1) I unlocked the bootloader, rooted my XT1053, stock recovery. Then last week I tried updating it to 5.1 official version via OTA. It failed due to files mismatch (maybe due to using apps that need root like Adaway). So I downloaded 4.4.4 STOCK version from Moto website, flashed boot.img, system.img and followed all the steps given here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Once the phone booted properly into 4.4.4, I tried 5.1 OTA and it worked fine. Then I flashed TWRP and SU to get root (I lost root when I flashed STOCK 4.4.4).
2) Everything was fine except that whenever I rebooted, my phone would Optimize ALL the apps. I Googled a lot and apparently this happened to many folks and there was no solution.
3) Today, I thought I will try and fix it by sideloading the 5.1 OTA zip (I thought the regular OTA style installation that I did of 5.1 over mfastboot style installation of 4.4.4 had something to do with it. I know, this was stupid of me!)
4) So, today I went to TWRP and tried to flash 'Blur_Version.213.44.1.ghost_row.Retail.en.US.zip'. I am 100% certain that this was the file that I copied from /cache after OTA had downloaded the file last week and I had saved it locally on PC and in SD on phone. However, this flashing gave me an error saying that it expected either 4.4.4 KXA or 5.1 but that my system was 4.4?? So the flashing failed and my OS is gone. How can I get ANY OS back? Here are the things that I tried so far:
1) Installed RSD Lite and I am downloading XT1053_TMO_RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip file from http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 as I type this out now. HOWEVER, I think I shouldn't use it as I read KidJoe saying not to downgrade. (KidJoe's comments are here http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347)
2) THEREFORE, I was wondering if I could simply flash a higher or equivalent version of ROM. Since we don't have an official 5.1 flashable zip right now, can I use 5.1.1 by CM? It's present here: http://primehowto.com/install-andro...le-moto-x-xt1053-2013-via-cm12-1-nightly-rom/
3) If yes to point# 2 above, I have a small problem. My phone is not detected by 'adb devices; in TWRP recovery mode. My battery is 11%. Could that be the issue?
I KNOW THIS WAS A LONG POST. I JUST WANTED TO GIVE ALL THE INFO. PLEASE HELP ME GET ANY OS ONTO THE PHONE AND THEN I WILL WAIT FOR THE 5.1 SBF TO BE AVAILABLE. THANKS A LOT IN ADVANCE....

here [Official] XT1058_GHOST_RETBR_5.1 FXZ/SBF (Full Rom)uploaded by our fellow user GARUXA
https://doc-10-ak-docs.googleuserco...359/*/0BwcadIv25aK8Tng3SUk2b1k5aVE?e=download
http://forum.xda-developers.com/mot...t1058ghostretbr5-1-fxz-sbf-rom-t3144161/page2

hbenz2008 said:
here [Official] XT1058_GHOST_RETBR_5.1 FXZ/SBF (Full Rom)uploaded by our fellow user GARUXA
https://doc-10-ak-docs.googleuserco...359/*/0BwcadIv25aK8Tng3SUk2b1k5aVE?e=download
http://forum.xda-developers.com/mot...t1058ghostretbr5-1-fxz-sbf-rom-t3144161/page2
Click to expand...
Click to collapse
Thanks for quick response. But I have XT1053.. Can I still use the one that you gave?

Not recommended, hold on a bit. try to flash only gpt and mboot from your 5.1 update?

hbenz2008 said:
Not recommended, hold on a bit. Did try to flash only gpt and mboot from your 5.1 update?
Click to expand...
Click to collapse
No, I didn't try mfastboot of 'gpt' from 5.1 update file 'Blur_Version.213.44.1.ghost_row.Retail.en.US.zip'. I don't see an 'mboot' or 'boot' file in it though. I do see 'gpt'. Also, in fastboot mode it says "Charger connected" instead of "USB connected". I think that's due to the low battery too?

hbenz2008 said:
Not recommended, hold on a bit. try to flash only gpt and mboot from your 5.1 update?
Click to expand...
Click to collapse
Would you know if 'Blur_Version.213.44.1.ghost_row.Retail.en.US.zip' file is the OTA 5.1 file? I think that's how the naming convention goes i.e. the name is set to the system version on which it is going to be updated NOT the system version that it will be updated to. I don't know why this flash failed though. I can give you the exact error that I get when I try flashing this if that helps? Thanks!

Shoot the error. If it's security downgrade, again flash gpt and mboot from Ota 5.1.
I will have to verify the name of Ota as its critical info.

hbenz2008 said:
Not recommended, hold on a bit. try to flash only gpt and mboot from your 5.1 update?
Click to expand...
Click to collapse
When I tried flashing "Blur_Version.213.44.1.ghost_row.Retail.en.US.zip" file (which I still think is the OTA 5.1 zip), I get this error:
Package expects build fingerprint of mototola/ghost_retail/ghost:4.4.4/KXA21.12-L1.29.1/2:user/release-keys or motorola/ghost_retail/ghost:5.1/LPA23.12-15/15:user/release-keys; this device has motorola/ghost_retail/ghost:4.4/13.11.1Q2.X-69-3/51:user/release-keys
This is where I got burned today. The above error wiped out my OS. I was on 5.1, I don't know why it says I have 4.4....

Prolly system mismatch, try only gpt and mboot. What error do u get?
---------- Post added at 09:27 PM ---------- Previous post was at 09:17 PM ----------
BTW your post provided good info. So Ota think u on 4.4.
You flashed only syst and boot to get on 4.4 ,could be where the prob is.
Need to know where img/rom info reside.
Double check the 4.4 files you flashed.
Just thinking out loud..

hbenz2008 said:
Prolly system mismatch, try only gpt and mboot. What error do u get?
---------- Post added at 09:27 PM ---------- Previous post was at 09:17 PM ----------
BTW your post provided good info. So Ota think u on 4.4.
You flashed only syst and boot to get on 4.4 ,could be where the prob is.
Need to know where img/rom info reside.
Double check the 4.4 files you flashed.
Just thinking out loud..
Click to expand...
Click to collapse
What's 'mboot'. There's no such file in the extracted folder of 'blur.....' file that I mentioned earlier. there is 'gpt'. My phone is detected via fastboot now so I can flash but don't know where the 'mboot' is

Hitdroid said:
What's 'mboot'. There's no such file in the extracted folder of 'blur.....' file that I mentioned earlier. there is 'gpt'. My phone is detected via fastboot now so I can flash but don't know where the 'mboot' is
Click to expand...
Click to collapse
Okay, so I fixed it. At least got an OS for now .. This is what I did.. I took a chance and went ahead with these steps:
1) Extracted files from Stock TMO 4.4.4 file 'TMO_RETAIL_XT1053_4.4.4_213.44.1.ghost_row.Retail.en.US_MR4_CFC.tgz' got from Moto website.
2) Modified 'flash.bat' file to have below commands:
SET mfastboot=mfastboot.exe
%mfastboot% getvar max-download-size
%mfastboot% oem fb_mode_set
%mfastboot% flash partition gpt.bin
%mfastboot% flash motoboot motoboot.img
%mfastboot% reboot-bootloader
%mfastboot% flash logo logo.bin
%mfastboot% flash boot boot.img
%mfastboot% flash recovery recovery.img
%mfastboot% flash system system.img
%mfastboot% flash modem NON-HLOS.bin
%mfastboot% erase modemst1
%mfastboot% erase modemst2
%mfastboot% flash fsg fsg.mbn
%mfastboot% erase cache
%mfastboot% reboot
3) It failed with 'partition', 'motoboot', 'logo'. Everything else was successful.
4) My phone booted into 4.4.4 now.
It's funny but I think I have successfully downgraded from 5.1 to 4.4.4... That means, my main system file was never upgraded to 5.1?? It's late and I want a phone for tomorrow so I won't try 5.1 tonight. But it would be great if experts could pitch in. How did I downgrade from 5.1 to 4.4.4?
Anyway, thanks for your help. Your comment about 'gpt' made me think "maybe my phone won't hard brick if I install 4.4.4 again".. and it didn't!
CHEERS!

You can downgrade Fri 5.1 to 4.4 without flashing gpt and mboot. Wait for full 5.1.
Excellent man. Check your bootloader version, it's probably lollipop. So don't take update yet.

I thought we couldn't downgrade without bricking? Anyway, I am getting notification to update to 5.1 via OTA. I'm ignoring until I understand what's happening. So, pls tell me what are the things that I need to check the versions of? Attached is a screenshot from 'About Phone'. How do I check bootloader version? Thanks man..
Sent from my XT1053 using XDA Free mobile app

to check bootloader BL, restart phone in fastboot read menu.
KidJoe got this better covered here
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Hitdroid said:
I thought we couldn't downgrade without bricking? Anyway, I am getting notification to update to 5.1 via OTA. I'm ignoring until I understand what's happening. So, pls tell me what are the things that I need to check the versions of? Attached is a screenshot from 'About Phone'. How do I check bootloader version? Thanks man..
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse

Hitdroid said:
I thought we couldn't downgrade without bricking? Anyway, I am getting notification to update to 5.1 via OTA. I'm ignoring until I understand what's happening. So, pls tell me what are the things that I need to check the versions of? Attached is a screenshot from 'About Phone'. How do I check bootloader version? Thanks man..
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Many try to skip GPT.BIN and MOTOBOOT.IMG... but when you have a version missmatch (gpt/motoboot from one rom, and rest from another), you increase your chance of bricking should you apply an OTA update zip in the future. And you'll likely end up with features not working or extra "bugs" that wouldn't otherwise appear.
For those who say "its safe to downgrade"... I'll point you to -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 and ask you to view the 7 links near the end of the first post as just a few examples.

Hey KidJoe, I could really use your help. I didn't want to downgrade but I had no choice as I couldn't re-install 5.1 (hence created this thread). It's good that I didn't brick when I reverted to 4.4.4 from 5.1 but I am skeptical of taking the 5.1 OTA now.
Pls look at the screen shot that I attached in my previous post. Also, my BL version is 30.BE (sha-34b7ccb, 2015-04-22 12:57:17). I have Stock Recovery KXA21.12-L1.29.1
How can I get a perfect installation of 5.1.. By perfect I mean none of the files left behind in the old version.
Appreciate your help!
Sent from my XT1053 using XDA Free mobile app

Hitdroid said:
Hey KidJoe, I could really use your help. I didn't want to downgrade but I had no choice as I couldn't re-install 5.1 (hence created this thread). It's good that I didn't brick when I reverted to 4.4.4 from 5.1 but I am skeptical of taking the 5.1 OTA now.
Pls look at the screen shot that I attached in my previous post. Also, my BL version is 30.BE (sha-34b7ccb, 2015-04-22 12:57:17). I have Stock Recovery KXA21.12-L1.29.1
How can I get a perfect installation of 5.1.. By perfect I mean none of the files left behind in the old version.
Appreciate your help!
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Hitdroid, do you mind sharing your 5.1 OTA file for xt1053.
I'm in the same situation as you. Got 5.1 OTA a few weeks ago, rooted it and installed TWRP. Then I accidentally installed my 4.4.4 backup which erased my 5.1 install.
I just installed CM 5.1 as a stopgap but i'd like to return to near stock so i'm following this thread.

as I thought, you have a 5.1 BL.
Gotta flash manually when sbf/ROM is available

Hitdroid said:
Hey KidJoe, I could really use your help. I didn't want to downgrade but I had no choice as I couldn't re-install 5.1 (hence created this thread). It's good that I didn't brick when I reverted to 4.4.4 from 5.1 but I am skeptical of taking the 5.1 OTA now.
Pls look at the screen shot that I attached in my previous post. Also, my BL version is 30.BE (sha-34b7ccb, 2015-04-22 12:57:17). I have Stock Recovery KXA21.12-L1.29.1
How can I get a perfect installation of 5.1.. By perfect I mean none of the files left behind in the old version.
Appreciate your help!
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Because of your bootloader, the safest way is wait for the 5.1 SBF to be posted (since you have an XT1053, it will be posted on Moto's web site, and you don't have to rely on leaks)... But I have no idea how long that will take.
Now, you could try to take the OTA, but I've seen enough bricks to say.. If it was my phone... I'd wait.

I'm at work so will share the file once I go home. But I think we should wait for 5.1 SBF as @KidJoe and @hbenz2008 have stated.
Sent from my XT1053 using XDA Free mobile app

Stock Recovery To Replace Twrp!!!!!Extracted from Official Rom:)

This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me

Brick
abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.

abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?

CasinovaRoyale said:
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.
Click to expand...
Click to collapse
i don't think so abt hard brick
as when i was updating i simply came with error while updating that can't update
and i also tried updating after flashing custom rom [which is available online] and i was successfully updated

smokinjoe2122 said:
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?
Click to expand...
Click to collapse
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.

thippu46 said:
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.
Click to expand...
Click to collapse
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty

yograjfire18 said:
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty
Click to expand...
Click to collapse
:angel:lol

Does someone has tried this successfully?

mabvmet said:
Does someone has tried this successfully?
Click to expand...
Click to collapse
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.

Could always just do "fastboot boot" instead of "fastboot flash". It will allow you to then boot twrp, install what you want, and not touch the stock recovery.

pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
What are the steps I need to follow to install this file? (SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
---------
Edit: Solved
---------
I followed the code section steps on this post:
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018

pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
Hey! I Finally did this, I removed the twrp and the root, I Just installed this stock (?) rom through the "adb fastboot". Now when I look for OTA updates it appears a message that indicates that the latest security update is installed, it's the one of December 2017...
Why doesn't it appear the last one (april's or so)?
What I have to do in order to have or reactivate the OTA updates?
Thanks in advance!

Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.

pratham.kamath said:
Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.
Click to expand...
Click to collapse
How can I know what is the correct stock rom?

SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.

pratham.kamath said:
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.
Click to expand...
Click to collapse
My current file >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml_1
This rom left me with the December security patch and no OTA updates available
This time I will download the same one, but the most recent (February, according with the web)
Next download >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip 03/02/2018 06:35
I followed this steps in code section to flash it... any suggest?
Steps >> https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018

Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.

pratham.kamath said:
Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.
Click to expand...
Click to collapse
Sorry, how do I run the bat file? The last time I entered the commands one by one.
My software chanel is "openmx" the sameone that I had when the phone was rooted (and with the updates available).

I need help
I need the recovery.img for the device moto g5s plus xt1806:llorando:

[StockOreo] Non-Rooted Users Upgrade to Official Stock Oreo 8.1.0

This thread is for those who haven't modified there Stock Rom in any way and are on NPSS26.116-61-8 version. Those who :-
1. Haven't Unlocked their Bootloader.
2. Haven't Rooted their Moto G5s Plus
3. Haven't Installed any Custom Rom
4. In short, were using the phone in the simple way without any modification.
can now upgrade to Stock Oreo 8.1.0 (Soak Test 1) easily.
To do that, just follow the following steps :-
1. Download the Oreo Stock Rom
https://drive.google.com/file/d/14nWazUMHTyk-od6SF3KJOXVTOWZoC_Do/view?usp=drivesdk (Thanks to the @sshbhm)
Or try this link
https://drive.google.com/file/d/1DW5zsW5uLZVRcpBPCqcumBifFzN98nbt/view?usp=drivesdk (Thanks to @Akhilesh287)
Mod Edit: If link is not working hit REPLY or send PM to the OP to notify them. Please do not REPORT a non-working link until you have contacted the OP first.
2. Cut Paste the downloaded Zip file in the root directory i.e internal storage.
(Make sure it is named as Blur_Version.26.336.15.sanders.retail.en.US.zip)
3. Give Storage permission to "Motorola Update Services" App
4. Check for any System Updates.
5. Restart your Phone.
6. Wait for some time (All I did was wait and Update notification appeared)
7. If Update Notification does not appear then check again for any updates.
8. Now, if update notification appears on your Moto and you press the update now button, let it restart and wait for approx 20-25 minutes.
9. Voila !!! You are on Official Oreo 8.1.0 Now...
Thanks to the Xda Community and its amazing members !!! :angel:
Edit - Before anyone asks whether Fingerprint is working or not, I confirm here that it is One Hundred Percent Working !!!
Hit Thanks if this helped.

Screenshots

I'm using pixel experience now ..I want stock oreo
I'm ready to lock bootloader

harikrishna.hks said:
I'm using pixel experience now ..I want stock oreo
I'm ready to lock bootloader
Click to expand...
Click to collapse
If you have already unlocked bootloader and have rooted your Moto then also you can follow this method.
Just make sure you are using stock rom when you do that. Bootloader locked or unlocked is irrelevant.

You may wish to advise users that this Oreo OTA may mean you do not receive OTA updates in the future. The reason is that this OTA is currently a soak test beta OTA. By flashing this, users move their device onto the soak test OTA path. If you're not part of the soak test program, you won't receive OTA updates.
If Motorola eventually releases OPS28.49-2 as the official OTA, then users that flashed this may be okay as they're back on the official OTA path. If not and Motorola issues another soak test OTA, then users will be stuck unless they take the responsibility to flash all the soak test OTA updates themselves or find the Oreo stock ROM.

Hi, If i have branded rom with Play, Can I upgrade to Oreo with this rom or not ?

osccarr said:
Hi, If i have branded rom with Play, Can I upgrade to Oreo with this rom or not ?
Click to expand...
Click to collapse
If your device does not have NPSS26.116-61-8 firmware on it, you won't be able to apply this OTA.
However, bear in mind that this leaked file is a soak test (beta) OTA, so you may wish to wait for the official OTA to come out via Play. If you flash this OTA, as I mentioned above, you may not receive future OTA updates unless this soak test and the official OTA are the same.

mightyjai said:
1. Download the Oreo Stock Rom
2. Cut Paste the downloaded Zip file in the root directory i.e internal storage.
(Make sure it is named as Blur_Version.26.336.15.sanders.retail.en.US.zip)
3. Give Storage permission to "Motorola Update Services" App
4. Check for any System Updates.
5. Restart your Phone.
6. Wait for some time (All I did was wait and Update notification appeared)
7. If Update Notification does not appear then check again for any updates.
8. Now, if update notification appears on your Moto and you press the update now button, let it restart and wait for approx 20-25 minutes.
9. Voila !!! You are on Official Oreo 8.1.0 Now...
Click to expand...
Click to collapse
This works even with unlocked Bootloader (xt1806), but first you have to flash official firmware (NPSS26.116-61-8). Then, just follow the steps in the guide.
After that you can install twrp and magisk if you want.

osccarr said:
Hi, If i have branded rom with Play, Can I upgrade to Oreo with this rom or not ?
Click to expand...
Click to collapse
You should be on Stock Rom to upgrade to Oreo using this method.

​
DannyRmz24 said:
This works even with unlocked Bootloader (xt1806), but first you have to flash official firmware (NPSS26.116-61-8). Then, just follow the steps in the guide.
After that you can install twrp and magisk if you want.
Click to expand...
Click to collapse
Yes you are right.
Actually this method is for those users who are using their Moto without any modifications.
Those who have modified their Moto like unlocked bootloader, installed custom recovery, rooted, installed custom Rom, etc. can do everything. But Normal Users depend upon Official Updates. So this method is useful for such users.

Are there any glitches? If not I might use this as my permanent OS, as my phone is modified and I wont receive OTAs anyway. If its too glitchy I'll wait for the official oreo though.

William1020000 said:
Are there any glitches? If not I might use this as my permanent OS, as my phone is modified and I wont receive OTAs anyway. If its too glitchy I'll wait for the official oreo though.
Click to expand...
Click to collapse
There maybe some glitches in this as it is still in Soaktest.
But I haven't found any glitches so far which is a good thing.
I recommend you to use it as Daily Driver.

Will I get future update over this one if i install it?

jyoti.id said:
Will I get future update over this one if i install it?
Click to expand...
Click to collapse
It depends upon Motorola Company.
It may be Yes or may be No.
However, if you can update to SoakTest Stock Rom then update to final Stable Rom is also possible.

mightyjai said:
It depends upon Motorola Company.
It may be Yes or may be No.
However, if you can update to SoakTest Stock Rom then update to final Stable Rom is also possible.
Click to expand...
Click to collapse
if your bootloader is unlocked, what will happen if I flash nougat stock rom over this build?

Please note that, this is not the official Oreo. It's just soak test. Once you flash this, you may not receive the official update when rolls out. So go with this with caution.

noobAKO said:
if your bootloader is unlocked, what will happen if I flash nougat stock rom over this build?
Click to expand...
Click to collapse
You have a possible risk of hard bricking your device if you flash the stock Nougat ROM over this Oreo soak test.
The flash of the Nougat stock ROM won't be the problem - however, you may still have an Oreo bootloader on your device. Thus, taking any Nougat OTA updates may hard brick your device (and I think there's a Nougat June 2018 security patch?).
Be very careful if you choose to downgrade to Nougat. There appears to be one report that someone was able to downgrade and re-lock their bootloader from the soak test after downgrading https://plus.google.com/+LaercioCarlosPereira/posts/XoVM56UDpd1 but as they've flashed the Indian stock ROM over their Brazil stock ROM they likely won't get Nougat OTA updates anyway.

echo92 said:
You have a possible risk of hard bricking your device if you flash the stock Nougat ROM over this Oreo soak test.
The flash of the Nougat stock ROM won't be the problem - however, you may still have an Oreo bootloader on your device. Thus, taking any Nougat OTA updates may hard brick your device (and I think there's a Nougat June 2018 security patch?).
Be very careful if you choose to downgrade to Nougat. There appears to be one report that someone was able to downgrade and re-lock their bootloader from the soak test after downgrading https://plus.google.com/+LaercioCarlosPereira/posts/XoVM56UDpd1 but as they've flashed the Indian stock ROM over their Brazil stock ROM they likely won't get Nougat OTA updates anyway.
Click to expand...
Click to collapse
Nice Brow, an XML already solves.This link is I hehe

Laercio_lalau said:
Nice Brow, an XML already solves.This link is I hehe
Click to expand...
Click to collapse
Are you able to provide this XML please? Also, what is your bootloader version at the moment?

When I mention an XML JA RESOLVE, I REFER TO THE XML OF 8.1 WHEN THE RELEASE IS RELEASED, AND IN RELATION TO THE BOOTLOADER, I'M NOT HOME, LATER VERIFY

how to upgrade to the regular oreo version from soak test

i had flashed oreo version OPS28.49-2 over latest nougat and now when the official oreo ota came i never got the ota as i moved to the soak update path,, is there any way to update back to latest oreo versio OPS28.65-36 without unlocking bootloader or any modifications

You could look into this tutorial - this should guide you in flashing the latest Oreo fastboot firmware to your device: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
Please verify it's the stock firmware you require and also be aware that your data may be erased. If you want to try to save your data, do not use the 'fastboot erase userdata' command, but ensure you have your important files backed up in case you have to factory reset.

echo92 said:
You could look into this tutorial - this should guide you in flashing the latest Oreo fastboot firmware to your device: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
Please verify it's the stock firmware you require and also be aware that your data may be erased. If you want to try to save your data, do not use the 'fastboot erase userdata' command, but ensure you have your important files backed up in case you have to factory reset.
Click to expand...
Click to collapse
the post says:-
Requirements:
1-Having the bootloader unlocked (I tried without unlocking and it did not work for me)
i have stock bootloader so cant use this method

kunalmisra said:
the post says:-
Requirements:
1-Having the bootloader unlocked (I tried without unlocking and it did not work for me)
i have stock bootloader so cant use this method
Click to expand...
Click to collapse
Hmm, thanks for pointing that out. However, flashing stock firmware on a locked bootloader should work if you're updating or reflashing the same firmware onto your device. What a locked bootloader prevents is downgrading the firmware, so I'm not sure what the guide author meant.
As you're updating your device from the soak test, this is the only method to get you updated without unlocking your bootloader. There are no soak test updates captured and you'd have to unlock your bootloader (wiping your device and voiding your warranty) to downgrade back to Nougat. That's unfortunately the problem with soak tests being leaked.
To the best of my knowledge, OPS28.65-36 is the firmware released to Indian devices. Again, you could try to save your data by omitting the fastboot erase userdata command, but I would strongly recommend backing up your device. There appears to be reports that users upgrading have bugs or stability issues that a factory reset seem to solve. Your experience may vary.