Related
So I cannot find an update for the Moto g4. The software update says it is fully up to date even though it is running Android 6.1.1 when 7.0 is out.
If any info is needed, ask me.
I'm guessing you mean v6.0.1 MM (NPJ24-139.64/65 I think is the latest MM for XT1625 and XT1644 devices)?
If you wanted to, you could flash the fastboot stock ROM for NPJS25.93-14.4 which is the latest update available (v7.0, March 2017 security update):https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 As always, be aware that the update may affect your data (as with any flash to system), back up accordingly.
echo92 said:
I'm guessing you mean v6.0.1 MM (NPJ24-139.64/65 I think is the latest MM for XT1625 and XT1644 devices)?
If you wanted to, you could flash the fastboot stock ROM for NPJS25.93-14.4 which is the latest update available (v7.0, March 2017 security update):https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 As always, be aware that the update may affect your data (as with any flash to system), back up accordingly.
Click to expand...
Click to collapse
Are you sure this is for XT1625? It looks like it is for XT1641 and 1645.
FIUSHerson said:
Are you sure this is for XT1625? It looks like it is for XT1641 and 1645.
Click to expand...
Click to collapse
It should work, as the NPJS25.93-14.4 build is based on the NPJ25.93-14 (Dec 2016 security patch) build, just updated with the March 2017 security update.
If you wish to be more certain, you can flash the aforementioned NPJ25.93-14 update via the fastboot ROM (from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369) which has XT1625 users reporting it flashes, and then wait for the OTA for the March 2017 security patch (which recent indications suggest it's been deployed in the US), or you could sideload the OTA (after flashing the Nougat 93-14 update) by downloading from here: https://forum.xda-developers.com/moto-g4-plus/how-to/official-moto-g4-plus-ota-update-build-t3584982
Hopefully, by flashing the Nougat update, OTA updates will arrive again via the retail USA software channel.
My wife has moto g5plus reteu device. I looked into "About Phone"
She has android 7.0 with August 2017 patch.
This is not the latest. Am i right?
I was trying to search for latest update but it says its latest.
If not, how can i manually update it.
Is it possible to download the latest patch as zip and flash it with stock recovery.
Thanks
Has your device been tampered with (unlocked, reflashed stock) before? If you're fully stock, that should be the latest version. I don't know what's the current version for your software channel though, I'm on RETUS.
Npns25.137-93-4 january is the latest for EU.
Normally it will be available in the updater in settings: "about phone".
Try connecting both with and without WiFi.
reCoded said:
Has your device been tampered with (unlocked, reflashed stock) before?
Click to expand...
Click to collapse
Yes it was.
knjigo said:
Yes it was.
Click to expand...
Click to collapse
As Knutselmaaster said that the latest is the January patch, that must mean that you either didn't flash the correct firmware for your country, or something went wrong with flashing. Reboot into your bootloader and check if your software status says "Official."
reCoded said:
As Knutselmaaster said that the latest is the January patch, that must mean that you either didn't flash the correct firmware for your country, or something went wrong with flashing. Reboot into your bootloader and check if your software status says "Official."
Click to expand...
Click to collapse
just rebooted into fastboot it says "Official"
knjigo said:
just rebooted into fastboot it says "Official"
Click to expand...
Click to collapse
Alright, that's a good sign. I can't really help you too much since I don't have a RETEU device. I'd look into finding the correct build number for RETEU, find the firmware file, then flash the firmware and test your luck.
I'll hook up into this thread, as my stock software status says modified. Does:
1. Flashing TWRP
2. Flashing Magisk
3. Solving service and 4G problem by not erasing modemsts
influence the software status? I have all above, but I'd like to get OTA somehow. Now I'm with november's security update.
reCoded said:
Alright, that's a good sign. I can't really help you too much since I don't have a RETEU device. I'd look into finding the correct build number for RETEU, find the firmware file, then flash the firmware and test your luck.
Click to expand...
Click to collapse
so i found the latest two firmwares from 3.2.2018 (in motorola firmwares)
but the one is npn and the other one is retail.
what to flash?
knjigo said:
so i found the latest two firmwares from 3.2.2018 (in motorola firmwares)
but the one is npn and the other one is retail.
what to flash?
Click to expand...
Click to collapse
I believe I flashed a NPN build that didn't have retail on it. If you want, give it a go.
As far as I recall, the firmwares released for EU were:
NPN25.137-33 (Jan 2017) > NPNS25.137-33-5 (May 2017) > NPNS25.137-33-11 (Aug 2017) > NPN25.137-93 (Nov 2017) > NPNS25.137-93-4 (Jan 2018). Brackets indicate the associated security patch, not necessarily when they were released.
Hopefully one of those firmware is on your wife's device, from what you've mentioned, the likely candidate is NPNS25.137-33-11.
echo92 said:
As far as I recall, the firmwares released for EU were:
NPN25.137-33 (Jan 2017) > NPNS25.137-33-5 (May 2017) > NPNS25.137-33-11 (Aug 2017) > NPN25.137-93 (Nov 2017) > NPNS25.137-93-4 (Jan 2018). Brackets indicate the associated security patch, not necessarily when they were released.
Hopefully one of those firmware is on your wife's device, from what you've mentioned, the likely candidate is NPNS25.137-33-11.
Click to expand...
Click to collapse
Thank you very much for information.
Now I only need the phone. My wife don't like messing around with her phone. I hope I can get it somehow
echo92 said:
As far as I recall, the firmwares released for EU were:
NPN25.137-33 (Jan 2017) > NPNS25.137-33-5 (May 2017) > NPNS25.137-33-11 (Aug 2017) > NPN25.137-93 (Nov 2017) > NPNS25.137-93-4 (Jan 2018). Brackets indicate the associated security patch, not necessarily when they were released.
Hopefully one of those firmware is on your wife's device, from what you've mentioned, the likely candidate is NPNS25.137-33-11.
Click to expand...
Click to collapse
She has NPN25.137-83 it says August 2017 security patch
Is it safe to flash NPNS25.137-33-11 over NPN25.137-83. It seems that i flashed wrong firmware last year.
knjigo said:
She has NPN25.137-83 it says August 2017 security patch
Click to expand...
Click to collapse
NPNS25.137-93-4 Stock Rom With 1 January 2018 Security Patch
https://drive.google.com/file/d/165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD/view
Kdemwa said:
NPNS25.137-93-4 Stock Rom With 1 January 2018 Security Patch
https://drive.google.com/file/d/165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD/view
Click to expand...
Click to collapse
Thank you very much:good:
Successful flashed. Thanks guys
Kdemwa said:
NPNS25.137-93-4 Stock Rom With 1 January 2018 Security Patch
https://drive.google.com/file/d/165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD/view
Click to expand...
Click to collapse
Is this an unmodified stock rom? No messing with dm-verity or anything like that?
dunderball said:
Is this an unmodified stock rom? No messing with dm-verity or anything like that?
Click to expand...
Click to collapse
Should be:
1)Flashable on locked bootloaders - if it was modified, then the bootloader would block you from flashing and/or booting. We've seen users being able to flash this okay:https://forum.xda-developers.com/showpost.php?p=75703702&postcount=22
2)The description text file mentions 'release-keys', so this firmware is likely signed with Motorola's cryptographic keys.
3)Users appear to have no issues with this build. Bear in mind this build (NPNS25.137-93-4) is mainly for EU (retEU/retGB), US (retUS) and Asia (retAPAC) devices as seen from OTA updates, you may flash this build onto devices from other retail software channels but you may not receive future OTA updates.
echo92 said:
Should be:
1)Flashable on locked bootloaders - if it was modified, then the bootloader would block you from flashing and/or booting. We've seen users being able to flash this okay:https://forum.xda-developers.com/showpost.php?p=75703702&postcount=22
2)The description text file mentions 'release-keys', so this firmware is likely signed with Motorola's cryptographic keys.
3)Users appear to have no issues with this build. Bear in mind this build (NPNS25.137-93-4) is mainly for EU (retEU/retGB), US (retUS) and Asia (retAPAC) devices as seen from OTA updates, you may flash this build onto devices from other retail software channels but you may not receive future OTA updates.
Click to expand...
Click to collapse
Thank you!
echo92 said:
Should be:
1)Flashable on locked bootloaders - if it was modified, then the bootloader would block you from flashing and/or booting. We've seen users being able to flash this okay:https://forum.xda-developers.com/showpost.php?p=75703702&postcount=22
2)The description text file mentions 'release-keys', so this firmware is likely signed with Motorola's cryptographic keys.
3)Users appear to have no issues with this build. Bear in mind this build (NPNS25.137-93-4) is mainly for EU (retEU/retGB), US (retUS) and Asia (retAPAC) devices as seen from OTA updates, you may flash this build onto devices from other retail software channels but you may not receive future OTA updates.
Click to expand...
Click to collapse
I am from India and i have just successfully installed this rom and relocked bootloader with no issue but will i get ota updates?
Hey there !
I have a Moto G5 Plus International edition (XT1681) with firmware NPNS25.137-92-4 (latest January Patch).
I want to know what firmware to download from here (https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/) for factory flash not to get bricked like an idiot.
I don't know which one is good
Thanks
The last 2 ROMs are for your device, if you have a custom recovery I recommend to install the flashable version from this link .
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Here are the same version of your device NPNS25.137-92-4 (20180101 security patch)
Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/
CobraBoyFR said:
Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/
Click to expand...
Click to collapse
i didnt try to flash over a fastboot rom, maybe you cant do that.
Thanks
But basically, what I need is flashing full stock firmware (with recovery and kernel), no matter if it's january update or not. Just the factory images I had when I bought the phone. And I don't know what version is OK for my phone (XT1681 with NPNS25.137-92-4 now) 'cause I don't want to hard brick it when OTA updating (to Oreo for example)
From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.
RokCruz said:
From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.
Click to expand...
Click to collapse
Right now I'm on stock NPNS25.137-92-4, with TWRP recovery + Magisk root + ElementalX kernel
I'm not planning to flash any custom ROM for the moment. When the official Oreo update comes out, I want to update. But I know it won't go well if I OTA update it with my current configuration. That's why I want to be able to flash stock with fastboot (rough clean install), no matter what version I get : All i want is to be able to update to Oreo when it's out. Problem is, I don't know which image I need to download from here : https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I know it's there, but don't know exactly the good version.
This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.
RokCruz said:
This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.
Click to expand...
Click to collapse
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.
echo92 said:
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.
Click to expand...
Click to collapse
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?
RokCruz said:
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?
Click to expand...
Click to collapse
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
That was roughly what I figured out but damn, those explanations, thanks buddy :highfive:
The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.
driverdis said:
The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.
Click to expand...
Click to collapse
On xt1681 right?
Thanks for your feedback
echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
yeah i cant apply normal OTA over flashable rom. I was on NPN25.137-92(flashable) i download NPNS25.137-92-4(flashable too) i dirty flashed it and it works perfect without lose my stuff
I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.
jkl555 said:
I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.
Click to expand...
Click to collapse
Just to reply to myself for (2). I found the following link
https://www.stockrom.net/2017/05/st...g5-plus-xt1683-xt1681-android-7-0-nougat.html
Few mins ago Moto pushed February security patch for RETBR.
Download it here:
https://motoota.lolinet.com/index.p....26.241.15.addison.retail.en.US&carrier=retbr
You need to be on build NPNS26.118-22-2-12 to flash this update!
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
Just the security patch. Although islt coincided with the Oreo update in China. Let's hope that's in preparation for retbr Oreo.
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
I presume they will push Oreo in few hours.
rafikowy said:
I presume they will push Oreo in few hours.
Click to expand...
Click to collapse
That will be great. Even though I'll wait for a .xml.zip, on the one hand I accidentally did a downgrade (and I have no idea of the bootloader of September and December patch are different enough to cause bricking with OTAs) and I think my phone is due for a factory reset. It reboots very randomly and even though battery life is great I'm told it should be even better. Let's see if that does the fix
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
8cpaiw said:
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
Click to expand...
Click to collapse
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Artim_96 said:
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Click to expand...
Click to collapse
Hahahah true, but I'm still hoping for the best outcome
Already available for RETIN and RETUS. I'm guessing this is the last nougat patch, hopefully Oreo is next
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
You are 100% right :good:
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
If I'm reading the info in fastboot correctly, the Feb update does include an updated bootloader:
C1.14 (sha-a62b7ae, 2018-02-21 16:09:43)
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
SherlockDk said:
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
Click to expand...
Click to collapse
If the blankflashes in the other thread don't work, then you may either:
1)Have to wait for a newer blankflash to get leaked. These are Motorola internal development tools and as such aren't generally available - as they're also signed by Motorola, we may not be able to make them ourselves. The ones we have either came with the factory stock ROM or a leak from a generous Motorola engineer. You may be lucky and a blankflash may be included if an Oreo factory stock ROM comes out (not the usual fastboot ROM, a full factory image).
2)Have to pay to have your motherboard replaced, which seems to be 60-70% of the cost of a new device as far as I understand, so you may wish to put that money towards a new device instead.
I'm sorry I don't have better news, hard bricks are very difficult to resolve without the proper tools. You may wish to research making a loader image (a partition level copy of a working device, loaded onto an SD card), but it's not a definite rescue method.
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
fernseher said:
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
Click to expand...
Click to collapse
You will stay on RETEU. The link I provided is RETAIL version.
Hey can i use these files for my guide? This save me some time
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Bad url
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
If you still have that file, please upload it to androidfilehost or somewhere.
I was on Oreo 85.13 pre-release...then I unlocked bootloader...and installed pixel experience...but meanwhile I formatted all data which ihave backed up..then I installed twrp flashable with June security patch zip..and I was on Android 7..then I flashed pixel experience..now..if I want to back on Oreo stock and to lock bootloader..what should I have To do...???I heard somewhere you need stock Oreo ROM zip where I can find one...???is that same one which we have used in manually updating to Oreo... please reply...
As far as I know the only stock Oreo zip we have is the OTA, which can't be used to flash firmware. We need the full firmware file before we're able to flash stock ROMs via fastboot.
Anyway, I'm also curious if there are any differences for the unlocking/flashing/backup process starting at the official Oreo we have now, and if going back to it later is the same as it is with Nougat.
The stock US OTA update can be found here: https://technoplanners.blogspot.com...tock-update-for-moto-g5-plus-OPS28.85-13.html
This can be side-loaded to upgrade after you've flashed Nougat with one caveat. Nougat has to be at Build number NPNS25.137-92. If your Nougat ROM has the June security patches (Build number NPNS25.137-93) you'll be SOL since the manifest specifies the pre-req for the update. So the fools at Motorola released the June update for Nougat, then released Oreo at the same security patch level and won't let you apply the update. Real geniuses.
nvrpayretail said:
The stock OTA update can be found here: https://technoplanners.blogspot.com...tock-update-for-moto-g5-plus-OPS28.85-13.html
This can be side-loaded to upgrade after you've flashed Nougat with one caveat. Nougat has to be at Build number NPNS25.137-92. If your Nougat ROM has the June security patches (Build number NPNS25.137-93) you'll be SOL since the manifest specifies the pre-req for the update. So the fools at Motorola released the June update for Nougat, then released Oreo at the same security patch level and won't let you apply the update. Real geniuses.
Click to expand...
Click to collapse
That's not quite correct; the build required for this Oreo OTA that's currently around is NPNS25.137-92-14 (June 2018 security patch for Brazil and Indian devices). The NPNS25.137-93-14 patch you mentioned is the June 2018 patch for EU, US and Asian devices, which means the Oreo patch for those devices isn't around yet.
To the opening poster, as previously mentioned, you will have to wait for the OPS28.85-13 stock fastboot ROM to be leaked. You must lock with a stock firmware as new or newer than your current bootloader. You cannot downgrade bootloaders via fastboot anyway and it's really not recommended to downgrade.
The US patch is available (Blur_Version.28.51.16.potter.retail.en.US.zip). It can be downloaded from the link I provided.
Correction: My bad. Didn't realize "92" indicated India and "93" indicated US. Evidently the referenced download is labeled wrong