Related
Just curious because, even though we shouldn't need them if they haven't changed, they didn't include the bootloader and radio, as every other MM monthly, has included. Anything odd or did your security update go smoothly. With all the N mystery around the factory image, just wondering.
I flashed the full MTC20L OTA from https://developers.google.com/android/nexus/ota over MTC20F. Android Security Patch level: September 6, 2016. Full OTA has bootloader, radio, and vendor files. No issues so far. The Kernel has a build date of Aug 9 2016. I will wait for Google to fix the bugs and post full OTA's and Factory Images before upgrading to N. This is my primary device, so it needs to work.
SpookyTunes said:
I flashed the full MTC20L OTA from https://developers.google.com/android/nexus/ota over MTC20F. Android Security Patch level: September 6, 2016. The Kernel has a build date of Aug 9 2016. I will wait for Google to fix the bugs and post full OTA's and Factory Images before upgrading. This is my primary device, so it needs to work.
Click to expand...
Click to collapse
I manually do so via fastboot so it's entirely different, but good to know the OTA was fine.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
I manually do so via fastboot so it's entirely different, but good to know the OTA was fine.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I just went back from Nougat to MTC20L via fastboot. The bootloader and radio images from the August update are the same ones necessary for this release. No issues whatsoever rolling back.
blitzkriegger said:
I just went back from Nougat to MTC20L via fastboot. The bootloader and radio images from the August update are the same ones necessary for this release. No issues whatsoever rolling back.
Click to expand...
Click to collapse
I did that a few days ago to MTC20F. More referring to the monthly update from that to L. I suspect it is fine but this whole N thing has been weird.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
I did that a few days ago to MTC20F. More referring to the monthly update from that to L. I suspect it is fine but this whole N thing has been weird.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The android-info.txt located within the images zip mentioned that the same bootloader and radio version as the August zip were required so I thought it was safe to flash away. I guess the non-inclusion of the bootloader/radio on the latest image was accidental.
Indeed N has been weird for a lot of people. I'm just lucky I haven't experienced the issues others were having with N. I just think of the delay in releasing N images as an opportunity to spend a little more time with M stuff. I'm going with the speculation that the full release of N for the 6p has been delayed due to VR. Or another possibility is that official images will debut with the MR1 release.
blitzkriegger said:
I just went back from Nougat to MTC20L via fastboot. The bootloader and radio images from the August update are the same ones necessary for this release. No issues whatsoever rolling back.
Click to expand...
Click to collapse
Can you explain step by step to revert back to MM from N ?
ariefabuzaky said:
Can you explain step by step to revert back to MM from N ?
Click to expand...
Click to collapse
Just flash the factory image. Instructions are here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
EDIT: Or, if you're going to restore a previous Nandroid, make sure that you use TWRP 3.0.2-0 or 3.0.2-2.
ariefabuzaky said:
Can you explain step by step to revert back to MM from N ?
Click to expand...
Click to collapse
Okay Buddy. Here are some assumptions prior to doing the steps:
*You have the required adb/fastboot/adb environment configured on your computer as mentioned on the intro of Heisenberg's How-to Guide
*You either have the August factory images or at least a copy of the August bootloader and radio image
*You have the latest September factory image
*You are on TWP 3.0.2-2
Steps:
1.) Copy/paste all important files you have on your phone to your PC.
2.) Next, make sure that the September image files are extracted within the "SDK Tools">"platform-tools" folder on your computer.
3.) Next extract or copy/paste the August bootloader (bootloader-angler-angler-03.54.img) and radio (radio-angler-angler-03.61.img) images within the "SDK Tools">"platform-tools" folder on your computer.
4.) Once you are all set reboot your phone to TWRP recovery first. Once within recovery go to "Wipe">
Advanced Wipe", place a check mark on all items then proceed with the wipe.
5.) If you want a decrypted system like I did, or make everything as clean as can be go to back to "Wipe">"Format Data" and proceed to format data.
6.) After formatting data, my practice is to reboot back to TWRP first. Once back to TWRP I then reboot to fastboot.
7.) Once on fastboot flash the images as specified on item#9 of Hesienberg's guide. Make sure that you execute the reboot-bootloader command after flashing the August bootloader. Also execute the same reboot-bootloader command after flashing August radio. Then flash away the remaining images (except recovery.img if you wish to keep TWRP).
8.) When done flashing all files my practice is to reboot-bootloader again. Then afterwards reboot to system. Then patiently wait for the phone to boot.
Disclaimer:Some of the steps are not fully required. It's just my practice as I flash totally clean.
blitzkriegger said:
Okay Buddy. Here are some assumptions prior to doing the steps:
*You have the required adb/fastboot/adb environment configured on your computer as mentioned on the intro of Heisenberg's How-to Guide
*You either have the August factory images or at least a copy of the August bootloader and radio image
*You have the latest September factory image
*You are on TWP 3.0.2-2
Steps:
1.) Copy/paste all important files you have on your phone to your PC.
2.) Next, make sure that the September image files are extracted within the "SDK Tools">"platform-tools" folder on your computer.
3.) Next extract or copy/paste the August bootloader (bootloader-angler-angler-03.54.img) and radio (radio-angler-angler-03.61.img) images within the "SDK Tools">"platform-tools" folder on your computer.
4.) Once you are all set reboot your phone to TWRP recovery first. Once within recovery go to "Wipe">
Advanced Wipe", place a check mark on all items then proceed with the wipe.
5.) If you want a decrypted system like I did, or make everything as clean as can be go to back to "Wipe">"Format Data" and proceed to format data.
6.) After formatting data, my practice is to reboot back to TWRP first. Once back to TWRP I then reboot to fastboot.
7.) Once on fastboot flash the images as specified on item#9 of Hesienberg's guide. Make sure that you execute the reboot-bootloader command after flashing the August bootloader. Also execute the same reboot-bootloader command after flashing August radio. Then flash away the remaining images (except recovery.img if you wish to keep TWRP).
8.) When done flashing all files my practice is to reboot-bootloader again. Then afterwards reboot to system. Then patiently wait for the phone to boot.
Disclaimer:Some of the steps are not fully required. It's just my practice as I flash totally clean.
Click to expand...
Click to collapse
Thanks you very much mate.
blitzkriegger said:
The android-info.txt located within the images zip mentioned that the same bootloader and radio version as the August zip were required so I thought it was safe to flash away. I guess the non-inclusion of the bootloader/radio on the latest image was accidental.
Indeed N has been weird for a lot of people. I'm just lucky I haven't experienced the issues others were having with N. I just think of the delay in releasing N images as an opportunity to spend a little more time with M stuff. I'm going with the speculation that the full release of N for the 6p has been delayed due to VR. Or another possibility is that official images will debut with the MR1 release.
Click to expand...
Click to collapse
Well, at least updating to the September release via normal flashing process worked fine, too. Really hoping we're not flashing any more MM monthlies ...
Sent from my Nexus 6P using Tapatalk
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0. The new emoji aren't supported either. Back in Lollipop I also got an update that says Android 5.0.2 but the version stayed at 5.0 after the update. Anyways, this update is 15MB and takes around 20 minutes to install, contrary to what Motorola says.
Also, really Motorola? MAY?! I'd be expecting you to roll out the QuadRooter (August/September) patch by now.
Hi,
thnx for the info.
Any suggestions if anyone is making update zip for twrp installation?
Regards
LK82
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
YassGo said:
Hi, it downloaded the 15Mb update when I came back home. Do I lose root if I update ?
Click to expand...
Click to collapse
I think these official updates fail if you are rooted.... but if it succeeds i don't know if you retain root.
Again the RetGB variant being overlooked apparently. Spanish version got it and British version nothing...
Do anyone have some changelog for this security update? Does it fix Bluetooth issues (sometimes not routing audio via BT when connected to Nokia car kit)?
AB__CD said:
Strangely in the initial update prompt (which I don't have a screenshot of unfortunately, so if someone has an XT1092 and can corroborate it would be much appreciated) it says Android 6.0.1 and not security update, but the Android version remains at 6.0 and by all accounts remains 6.0.
Click to expand...
Click to collapse
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Hello
This weekend I got a prompt on my phone (model XT1092) to upgrade to android 6.0.1.
I was happy about this upgrade because it solves a bug that prevented me from using bluetooth tracking devices [1].
However, after the upgrade the android version mentioned in the phone settings is still 6.0 and not "6.0.1" as expected. The only change I notice is that the "security patch" level is now May 1 2016.
Please confirm which version is actually is and/or if the specific bluetooth low-energy fix mentioned in link [1] is included.
Thanks
Click to expand...
Click to collapse
[1] URL can't link to in this forum, but search for "tileapp 6.0.1" in google
No OTA when rooted.
My MOTOX is rooted and has TWRP, so no OTA possible.
Any chance of this upgrade being downloadable somewhere alreadY?
bart.cerneels said:
I was surprised and exited that there was an update to 6.0.1 for my XT1092, which would fix the bluetooth BLE issue. No screenshot unfortunately, but I clearly remember it stating "6.0.1", not just a security upgrade.
I've contacted Motorola UK support though their email (sic) contact form with below message:
Click to expand...
Click to collapse
I can confirm that notification says "New version: 24.201.3.en.EU" and "Android 6.0.1, Marshmallow".
OK, in OP there is a screenshot with 6.0 still. So no go for BT patch I think...
Screenshot Android 6.0.1 promt
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
sgpieter said:
They instead labeled this as the 6.0.1 update.
I tried to inform Motorola (lenovo) about it but it seems that it didn't came through, it was pretty hilarious:
Initial mail:
Subject: Software update labeled wrong
Dear Motorola,
This morning I received an software update saying that it would update my phone to Android 6.0.1 . This was not the case, it was merely the may security update (those are important to, don't get me wrong).
Response:
Dear Customer,
Thank you for contacting Motorola.
It is an official update form the Motorola end.So please update your device.
Me:
I did perform the update on my device, that was not my question/problem.
I meant to say that the update said it was 6.0.1 but it isn't. It updates the device to a new security patch, not form 6.0 to 6.0.1. This was probably not the intention (to say that it would update to 6.0.1) and I tried to attend you on this mistake.
Second response:
Dear Customer,
Thank you for contacting Motorola.
After updating the security patch update you will receive the official update of 6.0.1
And then I gave up on the matter, it would have been pointless to go on.
Click to expand...
Click to collapse
Yeah, Motorola might just as well be Chinese now.
maybe this helps someone
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
Click to expand...
Click to collapse
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
4. Reboot into the bootloader, and then reflash stock recovery (download mentioned in step 1) with the command
"fastboot flash recovery 6.0_recovery.img"
5. Then reboot into recovery. From here, it will say "no command". Hold the power button and press the volume up key, then select apply patch from SD and choose the OTA you put on your internal memory. If all your system files are stock then this should run smoothly, if not, you might get a status error 7 and it will tell you which files are not stock. If you can, try to change them, but otherwise, you would need to download the stock files for 6.0 (you can also get them on the same link I suggested to get the stock recovery in step 1) and reflash everything to stock
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
Hi, could you possibly upload the OTA file you downloaded? Could come in handy
Thnx in advance.
Cheers
Sent from my MOTO X using XDA Labs
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
JonesMuc said:
As I'm new to this forum I cannot post links directly:
amazon.
de/clouddrive/share/dGQUmD6a5DvQrxlmSocfHr0Pm2XgIS9gBZ9b6lZAlla
(if the link is not working, you have to add https and www)
The file is called Blur_Version.24.11.18.victara_retde.retdeall.en.DE.zip so I think It's made for an update from 24.11.18 to 24.201.3
Click to expand...
Click to collapse
Thnx m8, really appreciated:good:
Cheers
Sent from my MOTO X using XDA Labs
JonesMuc said:
I got this OTA update although I had root and TWRP. But to do a successful update I had to fully unroot in SuperSU and flash the stock recovery.img and the stock boot.img.
But before unrooting I copied the automatically downloaded update file from the /cache directory to my normal download directory, so I could reach it from the stock recovery menu. Therefore you need a root file explorer.
I than flashed the OTA update manually from the stock recovery using this instructions from reddit (but had to also flash boot.img as mentioned before):
After updating and checking that everything is fine I rooted again with TRWP, SuperSU-beta and this "echo SYSTEMLESS=true>>/data/.supersu" command.
As I cannot post links, you find the original instruction I used when you click on the first link after you googled "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1"
The normal SuperSu without this SYSTEMLESS command did not work in my case.
Hope I could help somebody
Click to expand...
Click to collapse
May you tell the name of the post after searching "How To Root Moto G4 on Android 6.0.1 Marshmallow androidcustomrom1" ?
or some clues,
smthg plz ?
I suppose this is for rooting again
I'm looking for the stock recovery.img and the stock boot.img.
May you tell what to search to obtain them plz ?
Thx
You can find the recovery.img and boot.img in any stock firmware.
I used one from this site because it had the same version as mine:
androidsage.com/2016/02/09/install-official-marshmallow-ota-for-moto-x-android-6-0-ota-capture/
When you google for "blur_version.24.11.18" (or the version you need) you will find a lot of firmwares to download.
You are right, the other post is just for rooting again, after you updated
OK, thx :good:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
theoblackhawk said:
Don't know why it took so long for you guys in Europe, but here in Brazil we've been using the may security patch since, errr... may! Hahahaha
Click to expand...
Click to collapse
One word: Lenovo
Actually four words: Lenovo being an ass
Hi, everybody!
I have a couple questions and couldn't find clean answers.
I have an unlocked and rooted Moto G5 Plus (XT1683, build number NPNS25 . 137-15-5 - POTTER_BRAZILDSDS_CUST).
As you all may know, after a root process, you're not fully stock anymore.
1 - I have received the OTA August update (NPNS25.137-15-11) and i'm planning on installing it after restoring my device to stock. Since the update may not show up immediately after restoring the device, i'd like to download it and make it a flashable zip or something like that instead of waiting for a update notification that could take sometime to come back again.
Also, I couldn't find this OTA on the internet. How can i do that?
2 - I know I can find stock images/firmware at https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ but I still have some doubts.
As said, my device's build number is NPNS25.137-15. At the link above, the firmware is named as NPN25-137-15. Also, I've found some people talking about NPN25 instead NPNS25. Are they all mistyping or is it really a different Moto G5 Plus version?
About the last NPN25.137-15 (Last updated 10-09-2017) file in the link: Is it the August update?
3 - What's up with all these variants for just one device? NPNS25-137-15, NPNS25-137-13, NPNS25-137-35, NPNS25-137-69. XT1681, XT1683, XT1685 in just one country. What a mess!
I know this questions may sound lame but I couldn't find solid answers and I don't intend to mess anything up. Better safe than sorry, right?
So you are currently rooted, correct?
Install a root file manager and make sure you can access /.
Download the OTA update.
Once it is finished downloading, you will find it in the /cache directory; copy it to your device storage, then to PC.
Since you don't want to take the update right away, reboot into recovery and wipe /cache; this will remove the ota file from /cache so that you don't accidentally auto update.
If you would be so kind, please upload the OTA and share the link.
I can make a TWRP flashable zip with it, as I have with other recent OTA files:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
*edit*
You said your current build is NPNS25.137-15-5?
The closest available fastboot file available currently is NPN25.137-15, which means that I would also need the OTA file from NPN25.137-15 to NPNS25.137-15-5 for the current file to be of any use.
You could use the fastboot file to flash back to NPN25.137-15 and pull that OTA, or maybe even a larger OTA that goes from NPN25.137-15 directly to NPNS25.137-15-11.
Hi, thanks for your help!
Yes, i'm rooted and on NPNS25.137-15-5 right now. I'll upload the OTA file tonight when i'll be in no rush!
The closest available fastboot file available currently is NPN25.137-15, which means that I would also need the OTA file from NPN25.137-15 to NPNS25.137-15-5 for the current file to be of any use.
You could use the fastboot file to flash back to NPN25.137-15 and pull that OTA, or maybe even a larger OTA that goes from NPN25.137-15 directly to NPNS25.137-15-11.
Click to expand...
Click to collapse
-That means that NPNS25.137-15 is an updated version from NPN25.137-15?
Anyway, i'll upload the OTA file tonight!
Q9Nap said:
So you are currently rooted, correct?
Install a root file manager and make sure you can access /.
Download the OTA update.
Once it is finished downloading, you will find it in the /cache directory; copy it to your device storage, then to PC.
Since you don't want to take the update right away, reboot into recovery and wipe /cache; this will remove the ota file from /cache so that you don't accidentally auto update.
If you would be so kind, please upload the OTA and share the link.
I can make a TWRP flashable zip with it, as I have with other recent OTA files:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
*edit*
You said your current build is NPNS25.137-15-5?
The closest available fastboot file available currently is NPN25.137-15, which means that I would also need the OTA file from NPN25.137-15 to NPNS25.137-15-5 for the current file to be of any use.
You could use the fastboot file to flash back to NPN25.137-15 and pull that OTA, or maybe even a larger OTA that goes from NPN25.137-15 directly to NPNS25.137-15-11.
Click to expand...
Click to collapse
I have uploaded the 93-8 OTA (March 2018 security patch)..if you could please convert it into a flashable ZIP we'd greatly appreciate it!
https://drive.google.com/file/d/1EihHeSrnj03usOKrLkZkWqdEjeMeIZQb/view?usp=sharing
I see over a dozen different versions here but I'm not sure which one to download:
https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I've already tried two different ones but I receive no cell signal when it boots.
Any ideas?
Thanks!
I actually found the answer on my own: none of them. Wrestling with the G5 this morning made me lose my mind. I ended up with the Pixel ROM.
Does anyone have a copy of the XT1687 stock rom (carrier unlocked ... I bought mine at Costco)? I could really use it.
My phone is totally messed up. My /system is empty except for 'bin'....
Thank you for any help!
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
did going back to stock and accepting the OTA work for you??!
roydhritiman said:
did going back to stock and accepting the OTA work for you??!
Click to expand...
Click to collapse
I ended up with some kind of error with the OEM partition, but in the end all of the details on my settings screen show that I'm on the latest security patch, kernel, etc.
dunderball said:
I have used this one: POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
dunderball said:
I was on this version for a while, rooted, and I had to use this firmware to reflash back to stock in order to take the OTA successfully (the OTA is NPNS25.137-93-4, which is the latest as of this writing).
I basically flashed everything from the flashfile.xml
Click to expand...
Click to collapse
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
dlong said:
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
Patches, a full ROM is rarely sent as an OTA. You'll know it's a full ROM if the size of the OTA is greater than 1GB. Anything less than say 300-400MB is patches to the system
dlong said:
What does this version of the firmware say for (in the About settings) Software Channel? Android Version? Or rather, I guess what does it say now that you think it took the OTA successfully?
The OTA that are downloaded into /cache are named something like Blur_* right? Do you know if those OTA contains the full image or is it just patches to various parts of the system?
Click to expand...
Click to collapse
I went from version 83 to successful OTA 92 (November patch), then to 93 January patch (but ended up with a failure message after booting up for whatever reason). I'm on retus, baseband M8953_37.46.07.47R POTTER_NA_CUST, build number NPNS25.137-93-4.
As far as I see, I don't see any full stock firmware out for NPNS25.137-93-4 which is unfortunate. I have a feeling my update to Oreo will fail if it ever comes out. I'm not even sure why my OTA fails, as I do my best to avoid modifying any partitions and mostly use systemless modules through Magisk. Whatever though.
No joy. So apparently, since I'm on NPN25.137-92 (POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), I wasn't able to downgrade to (POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip).
I did re-flash everything and the results seems to be the same (unable to 'see' new updates). I am on November 2017 patch but when I check for upgrades, it states the system is up to date.
I hope that because my phone is 'unlocked from store (Costco - USA)' that RETAIL is the correct firmware. Anyone know for sure?
Also... I guess I wiped recovery when I installed TWRP. Is there an OEM recovery.img available for Moto 5G Plus?
Edit: So the whole reason, I originally rooted my phone was so that I can enable Hot Spot by adding net.tethering.noprovisioning=true to /system/build.prop (now I wonder if root is even required to do that?)
Hi! I'm on NPJS25.93-14.7-3 (December 2017 security update). My phone is Moto G4 Plus XT1644 and I'm rooted with Magisk.
I want to install the new OTA update (NPJS25.93-14.7-5), but since I'm rooted I need a stock NPJS25.93-14.7-3 so I can restore the recovery. I have been searching for weeks but I can't seem to find this version.
Anyone know where I can find it?
Thanks.
As far as I know, there is currently no NPJ25.93-14.7-3 or NPJ25.93-14.7-5 firmware uploaded to either firmware.center or the Motorola Firmware Team Android FileHost page.
There is a way to revert back to the stock ROM (credit to Danny1976 and pastorbob62 https://forum.xda-developers.com/showpost.php?p=76081679&postcount=110 ), though you will have to flash the NPJ25.93-14.7 stock ROM (Sept 2017 security patch). Though normally downgrading isn't a good idea, in this case you're only downgrading to the directly preceding firmware and then the OTA should bring you back up to NPJ25.93-14.7-3, after which you could flash the OTA update to the Feb 2018 security patch.
So the general procedure is:
1)Back up your device (make a TWRP backup and keep it safe).
2)Download the NPJ25.93-14.7 stock ROM (retail US: https://androidfilehost.com/?fid=817906626617945295 or Amazon software channel: https://androidfilehost.com/?fid=817906626617956922 )
3)Flash as per the above linked XDA post. You may wish to ignore security downgrade errors with GPT/bootloader as the next OTA update should flash the same bootloader as you currently have. These set of flashing commands should not affect your data but nonetheless, at least you have a backup.
4)Reboot and update to NPJ25.93-14.7-3
5)Reboot and update to NPJ25.93-14.7-5
Then you should be up to date. I do not know if this procedure will work for the next OTA update , so perhaps best to boot TWRP, do not swipe to allow modification in TWRP and take a backup of your NPJ25.93-14.7-5 installation. This should be okay to revert back to if there is no firmware still available.
You may wish to read the posts from this page and the subsequent pages for more information: https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page12
echo92 said:
As far as I know, there is currently no NPJ25.93-14.7-3 or NPJ25.93-14.7-5 firmware uploaded to either firmware.center or the Motorola Firmware Team Android FileHost page.
There is a way to revert back to the stock ROM (credit to Danny1976 and pastorbob62 https://forum.xda-developers.com/showpost.php?p=76081679&postcount=110 ), though you will have to flash the NPJ25.93-14.7 stock ROM (Sept 2017 security patch). Though normally downgrading isn't a good idea, in this case you're only downgrading to the directly preceding firmware and then the OTA should bring you back up to NPJ25.93-14.7-3, after which you could flash the OTA update to the Feb 2018 security patch.
So the general procedure is:
1)Back up your device (make a TWRP backup and keep it safe).
2)Download the NPJ25.93-14.7 stock ROM (retail US: https://androidfilehost.com/?fid=817906626617945295 or Amazon software channel: https://androidfilehost.com/?fid=817906626617956922 )
3)Flash as per the above linked XDA post. You may wish to ignore security downgrade errors with GPT/bootloader as the next OTA update should flash the same bootloader as you currently have. These set of flashing commands should not affect your data but nonetheless, at least you have a backup.
4)Reboot and update to NPJ25.93-14.7-3
5)Reboot and update to NPJ25.93-14.7-5
Then you should be up to date. I do not know if this procedure will work for the next OTA update , so perhaps best to boot TWRP, do not swipe to allow modification in TWRP and take a backup of your NPJ25.93-14.7-5 installation. This should be okay to revert back to if there is no firmware still available.
You may wish to read the posts from this page and the subsequent pages for more information: https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page12
Click to expand...
Click to collapse
I will look in to this in more detail. Thank you very much!
This worked like a charm! I followed the steps and now I'm on NPJS25.93-14.7-5.
I read somewhere that this version fixes the screen ghosting effect, but sadly not for me, so I had to root again and correct the RGB values.
Thanks!
juanml said:
This worked like a charm! I followed the steps and now I'm on NPJS25.93-14.7-5.
I read somewhere that this version fixes the screen ghosting effect, but sadly not for me, so I had to root again and correct the RGB values.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems that if you are one of the unfortunate who has the ghost touch issue it isn't fixed by this version. I am on 14.7-5 and I don't have that problem at all, which leads me to believe it is a hardware issue. Doesn't explain why some versions don't have it though.
Hi! Anyone know if this method still works for updating to NPJS25.93-14.7-8?