Hi,
tl;dr: Is there a download link available for the WW_V21.40.1220.1698 official firmware?
Details:
I have a ZE600KL and this official page says Marshmallow is released for it.
I have unlocked bootloader and currently stock recovery and ROM, that I've flashed myself by downloading from the official support page (1.16.40.1523_20160426). I've been checking for updates from Settings>About>System Update for a while, to no success. I used to have a root but flashing the 1.16 seems to have removed it. And if I flash TWRP and reboot to recovery, it asks me whether it should leave the system partition untouched. So this makes me think I should be able to receive the OTA, normally. And yet, as I said, no such luck.
I've seen some ROMs that mention they require MM firmware for ZE600KL, such as this one. Again, this makes me thing some people out there must have received the 21.40 update (or any Marshmallow update) for their ZE600KL. I've been searching the internet but I didn't find this firmware anywhere. If somebody knows a link or if by some enormous kindness somebody uploads this, I'd be really grateful.
Thank you in advance to anyone who replies
Edit: I came across this link but I haven't yet been able to verify if it works, will update after I try:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-21.40.1220.1698-user.zip
Second Edit: The zip in the link flashes and boots. I'm sorry to have created a thread and then manage to solve it on my own later, but hopefully this might be helpful to other ZE600KL owners in the future.
Hi all,
Trying to solve some terrible freezing/lag on my Verizon XT1585 Turbo 2 (sometimes upwards of 30 seconds delay between keypresses). Wiping cache and factory reset has no effect. It happened after the OTA 7.0 update so I wanted to try and flash the full 7.0 image and start fresh.
However I noticed that the firmware available here on the site may be slightly older than what I have on my phone, and I'm worried about bricking by trying to flash what is technically an older version.
The build number of the firmware here on the site lists itself as: NCK25.118-10, but my phone shows it's build number as NCK25.118-10.2. This appears to be two OTA updates behind, from February. Newest one is from August.
Am I being overly paranoid about minor OTA updates, or would I have issues if I were to try and flash?
Thanks!
EDIT: With some googling I have found the newest NCK25.118-10.2 firmware was uploaded just yesterday by Motorola-Firmware-Team on AndroidFileHost (I can't post the link because I'm still too new)
Would it make sense to update the firmware download thread with this new firmware? And would I have been boned if I flashed the older file?
you can only flash NCK25.118-10.2 , the one you mentioned in your post, this is because your device is on the latest buildNCK25.118-10.2 and currently, flashing older builds or downgrading is not possible.
also reflashing NCK25.118-10.2 build will not fix random reboots as i am experiencing it first hand.
ferolac said:
you can only flash NCK25.118-10.2, the one you mentioned in your post, this is because your device is on the latest buildNCK25.118-10.2 and currently, flashing older builds or downgrading is not possible.
Click to expand...
Click to collapse
That's what I thought, glad the most recent firmware just came out. Thanks very much! I'm worried that my problem is a hardware issue as well, it seems to freeze whenever it's accessing files (reading image thumbnails, cached data etc. Maybe memory going bad or bad solder connections). I thought it couldn't hurt to flash fresh as long as I had the correct file.
How would we go about getting the firmware thread updated with the new file?
Darkhand said:
That's what I thought, glad the new firmware just came out. Thanks very much! I'm worried that my problem is a hardware issue as well, it seems to freeze whenever it's accessing files (reading image thumbnails, cached data etc). Maybe memory going bad etc. Thought it couldn't hurt to flash fresh as long as I had the correct file.
How would we go about getting the firmware thread updated with the new file?
Click to expand...
Click to collapse
this build was already available here, long before it was uploaded to android filehost. As for how to update the firmware thread here . . . informing the mods i guess
The J727P has been certified by Wi-Fi Alliance running Oreo 8.0. If I can find the leaked firmware, I will post it here. If anyone else happens to track it down before me, please also post it here!
stock boot.img ?
Spaceminer said:
The J727P has been certified by Wi-Fi Alliance running Oreo 8.0. If I can find the leaked firmware, I will post it here. If anyone else happens to track it down before me, please also post it here!
Click to expand...
Click to collapse
Sounds good, one question thought, where is stock boot.img on j727p firmware for odin? BP,CSC,CP, or AP.
J727P
Spaceminer said:
The J727P has been certified by Wi-Fi Alliance running Oreo 8.0. If I can find the leaked firmware, I will post it here. If anyone else happens to track it down before me, please also post it here!
Click to expand...
Click to collapse
One question is this fore real ?
Yes I ask this because I was on stock firmware three days ago an I checked for the update an there wasn't one ! Maybe Verizon gets the update first I will check again in a day or two !
---------- Post added at 12:32 AM ---------- Previous post was at 12:00 AM ----------
lamike said:
Sounds good, one question thought, where is stock boot.img on j727p firmware for odin? BP,CSC,CP, or AP.
Click to expand...
Click to collapse
Boot img is in the AP file !!
peter couniaz said:
One question is this fore real ?
Yes I ask this because I was on stock firmware three days ago an I checked for the update an there wasn't one !
Click to expand...
Click to collapse
Yes. It's just not officially released yet. I've been scouring the web for a leak. This means Oreo has been built for our device already and the official release coming. If you're curious about WiFi Alliance, wikipedia has good information about them.
J737P
Spaceminer said:
Yes. It's just not officially released yet. I've been scouring the web for a leak. This means Oreo has been built for our device already and the official release coming. If you're curious about WiFi Alliance, wikipedia has good information about them.
Click to expand...
Click to collapse
Ok thank you an let me know if you find anything more about this !
peter couniaz said:
Ok thank you an let me know if you find anything more about this !
Click to expand...
Click to collapse
I managed to find the firmware, however, it's behind a pay wall on servers in Iran. The firmware name is J727PVPU4BRH5 if you want to help look for it. As soon as find it on a free server, I'll post an update.
J727P
Spaceminer said:
I managed to find the firmware, however, it's behind a pay wall on servers in Iran. The firmware name is J727PVPU4BRH5 if you want to help look for it. As soon as find it on a free server, I'll post an update.
Click to expand...
Click to collapse
Yes the 8.0 update is up for this phone I'm on stock firmware an I don't know if I will do the update until I see root for it ! I will let you what I decide !
J727P update
peter couniaz said:
Yes the 8.0 update is up for this phone I'm on stock firmware an I don't know if I will do the update until I see root for it ! I will let you what I decide !
Click to expand...
Click to collapse
I'm going to take the update to 8.0 an hope someone cames up with a Root process ! an it is the U4 bootloader so backdating the firmware should work if I don't like it !
peter couniaz said:
I'm going to take the update to 8.0 an hope someone cames up with a Root process ! an it is the U4 bootloader so backdating the firmware should work if I don't like it !
Click to expand...
Click to collapse
I'm already running Oreo. TWRP has problems with it. I can't make a backup of the OS. You can restore a back up, but you have to flash the BL file from ARG2 then wipe everything in TWRP first. SuperSU 2.82-SR5 will cause a boot loop. I'm going to try magisk 17.1. Honestly, I'm very disappointed with Samsung's Oreo... It's almost the exact same as Nougat, and the new camera sucks, very bad. They gave us Nougat, with Oreo 8.1 as the base firmware. That's my literal take on it. I'm definitely getting a Moto G6 after seeing this, and I'm going back to my stock build.
J727P update
Spaceminer said:
I'm already running Oreo. TWRP has problems with it. I can't make a backup of the OS. You can restore a back up, but you have to flash the BL file from ARG2 then wipe everything in TWRP first. SuperSU 2.82-SR5 will cause a boot loop. I'm going to try magisk 17.1. Honestly, I'm very disappointed with Samsung's Oreo... It's almost the exact same as Nougat, and the new camera sucks, very bad. They gave us Nougat, with Oreo 8.1 as the base firmware. That's my literal take on it. I'm definitely getting a Moto G6 after seeing this, and I'm going back to my stock build.
Click to expand...
Click to collapse
You haven't tried flashing back to nougat then !
peter couniaz said:
You haven't tried flashing back to nougat then !
Click to expand...
Click to collapse
I have, and flashing back to nougat works fine. You have to flash ARG2 for it to work, and you can't downgrade the Modem. I'll put together instructions and probably a debloated ROM later this evening, and I'll get the firmware uploaded ASAP. Some notes, clearing the camera data fixes the blurry image problem, and it can be rooted. You need the latest TWRP, and Magisk 17.1 stable. You must flash TWRP, swipe to allow modifications, then format data with the option that makes you type "yes", then flash magisk. Root works perfectly. No issues. I'm debloating the OS right now. I'm about to test Viper too. Its actually much faster than Nougat once the junk is out and yes, it can be fully deknoxed. This might not be so bad. I'm still disappointed with their lack of Oreo-esq cosmetics though.
J727P update
Spaceminer said:
I have, and flashing back to nougat works fine. You have to flash ARG2 for it to work, and you can't downgrade the Modem. I'll put together instructions and probably a debloated ROM later this evening, and I'll get the firmware uploaded ASAP. Some notes, clearing the camera data fixes the blurry image problem, and it can be rooted. You need the latest TWRP, and Magisk 17.1 stable. You must flash TWRP, swipe to allow modifications, then format data with the option that makes you type "yes", then flash magisk. Root works perfectly. No issues. I'm debloating the OS right now. I'm about to test Viper too. Its actually much faster than Nougat once the junk is out and yes, it can be fully deknoxed. This might not be so bad. I'm still disappointed with their lack of Oreo-esq cosmetics though.
Click to expand...
Click to collapse
Thank you for the info on downgrading back to nougat !
peter couniaz said:
Thank you for the info on downgrading back to nougat !
Click to expand...
Click to collapse
I've got 3 of 4 firmware files uploaded. The AP file is giving me trouble cause my WiFi sucks, and it keeps failing before it finishes. I did put together a full stock Oreo ROM but its got problems. You can only flash it using TWRP if you have the ARG2 bootloader, but, the ARG2 bootloader, won't allow Oreo to boot up no matter what. We'd need a custom boot.img and I can't make one. The ROM can't be flashed with the Oreo bootloader installed either, because it prevents TWRP from copying/writing to the data or system partitions. If it tries to, it'll reboot half way through. Magisk 17.1 will also lose root after awhile. We need a custom boot, or we need a modified root method and an updated TWRP to have any fun with it. SMH at Samsung right now. They gave us Oreo, with no milk, and a slap in the face. Nougat everything, running on Oreo 8.1 firmware... I'll never get over that. I'm running an ARG2 build cause everything works, and largely looks the same. I swear, they didn't even try. They just reskinned some Nougat apps and put them in an Oreo system. I will never buy another Samsung product after seeing this half hearted Oreo they gave us.
J727P update
Spaceminer said:
I've got 3 of 4 firmware files uploaded. The AP file is giving me trouble cause my WiFi sucks, and it keeps failing before it finishes. I did put together a full stock Oreo ROM but its got problems. You can only flash it using TWRP if you have the ARG2 bootloader, but, the ARG2 bootloader, won't allow Oreo to boot up no matter what. We'd need a custom boot.img and I can't make one. The ROM can't be flashed with the Oreo bootloader installed either, because it prevents TWRP from copying/writing to the data or system partitions. If it tries to, it'll reboot half way through. Magisk 17.1 will also lose root after awhile. We need a custom boot, or we need a modified root method and an updated TWRP to have any fun with it. SMH at Samsung right now. They gave us Oreo, with no milk, and a slap in the face. Nougat everything, running on Oreo 8.1 firmware... I'll never get over that. I'm running an ARG2 build cause everything works, and largely looks the same. I swear, they didn't even try. They just reskinned some Nougat apps and put them in an Oreo system. I will never buy another Samsung product after seeing this half hearted Oreo they gave us.
Click to expand...
Click to collapse
You are using the latest twrp try going back 2 builds on the twrp an see if that will stick on the full 8.1.0 firmware don't know if it will work but if you have the full 8.1.0 firmware give it a shot an let us all know if it does ! Or when you get the full firmware uploaded send me a link an I will try it ! Thank you !!
I have posted the oreo firmware here https://forum.xda-developers.com/galaxy-j7/how-to/sm-j727p-oreo-8-1-firmware-t3841778
HELP FLASH BACK J727P to nougout
i need some help, every time i try to downgrade to android 7 in this phone j727p, i get errors flashing modem, ive tried combination firmware, and full flash 4arg2 im currently 8.1.0 4brh5 and cant flash back to nougout
---------- Post added at 07:09 PM ---------- Previous post was at 07:04 PM ----------
Spaceminer said:
I have, and flashing back to nougat works fine. You have to flash ARG2 for it to work, and you can't downgrade the Modem. I'll put together instructions and probably a debloated ROM later this evening, and I'll get the firmware uploaded ASAP. Some notes, clearing the camera data fixes the blurry image problem, and it can be rooted. You need the latest TWRP, and Magisk 17.1 stable. You must flash TWRP, swipe to allow modifications, then format data with the option that makes you type "yes", then flash magisk. Root works perfectly. No issues. I'm debloating the OS right now. I'm about to test Viper too. Its actually much faster than Nougat once the junk is out and yes, it can be fully deknoxed. This might not be so bad. I'm still disappointed with their lack of Oreo-esq cosmetics though.
Click to expand...
Click to collapse
sr ive been trying to flash back the nougout firmware arg2 but still problems, the cp box in z3x uncheck, but still got errors with csc, i need to downgrade from brh5 and it wont let me, if you could be more specific how did you do the process
Galaxy J7 Perx (Boost) on J727PVPU4BRH5
Spaceminer said:
I managed to find the firmware, however, it's behind a pay wall on servers in Iran. The firmware name is J727PVPU4BRH5 if you want to help look for it. As soon as find it on a free server, I'll post an update.
Click to expand...
Click to collapse
Dear Sirs;
Having had to replace my originally bought (Nov 17, 2017) J7 Perx from Boost, then bricking it and replacing it with a Galaxy S6 refurb from Boost, which was then STOLEN by a "friend" of 6(six) years, has been replaced by a NEWER J7 Perx. This device received at lest 3, if not 4 OTA updates, one of which was a supplemental firmware/software update. About Phone (and Samsung INFO app) NOW reveal the following detail:
HARDWARE VERSION; J727P.02
Mfg date; 03/15/2018
Software Version; J727PVPU4BRH5
Android Version; 8.1.0
Samsung Experience; 9.5
Baseband Version; J7272PVPU4BRH5
Build Number; M1AJQ.J727PVPU4BRH5
Android Security Patch; August 1, 2018.
If given instruction and link to necessary utility to extract the firmware from my device to my PC, I would be more than pleased to provide the files(s) procured from that process.
I look forward to hearing more about possible deodexed firmware to ROOT my newest device.
A custom ROM would be nice, too.
---------- Post added at 15:23 ---------- Previous post was at 15:14 ----------
Guess I should have browsed a few more posts before posting.
I found the link to all the 8.x firmwares for the various models, and must say "Bravo!" for the Herculean effort expended to collect, upload and make all that available.
Thanks!
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Thanks for the response
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
psychopac said:
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Click to expand...
Click to collapse
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
kash664 said:
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
Click to expand...
Click to collapse
Make sure to follow the flashing instructions mentioned by the thread OP properly
psychopac said:
Make sure to follow the flashing instructions mentioned by the thread OP properly
Click to expand...
Click to collapse
Yes. Hope everything turns out fine
kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
I hope i can help !!
vishalrickz said:
I hope i can help !!
Click to expand...
Click to collapse
Sure sir
I'm worried that I've permanently messed up my phone. I didn't make a backup of my stock firmware when I first flashed Lineage OS, and then I was having issues with that, so now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk. That should of been sufficient to factory reset it right? It just keeps having little problems that it didn't have before, like internet loading things slowly and bugs and crashing apps. The reason I switched off the Lineage OS rom is because it had little problems like that too. I just don't know what to do anymore.
Relevant Info:
Device: Moto G5 Plus Unlocked US version
Carrier: T-Mobile
lumbo7333 said:
I'm worried that I've permanently messed up my phone. I didn't make a backup of my stock firmware when I first flashed Lineage OS, and then I was having issues with that, so now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk. That should of been sufficient to factory reset it right? It just keeps having little problems that it didn't have before, like internet loading things slowly and bugs and crashing apps. The reason I switched off the Lineage OS rom is because it had little problems like that too. I just don't know what to do anymore.
Relevant Info:
Device: Moto G5 Plus Unlocked US version
Carrier: T-Mobile
Click to expand...
Click to collapse
What exactly are your problems? Check the thread of the custom ROM you installed and look for fixes there, maybe you installed an outdated version and your problems have been fixed in the updates. Good luck.
lumbo7333 said:
...now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk.
Click to expand...
Click to collapse
What do you mean with "stock but not official"?
Where did you get it from?
There are some sources for official firmwares signed by Motorola here on XDA so what makes you think the one you use isn't official?
If so that could be for sure the reason for problems for I have to say that I haven't seen unofficial stock ROMs except TWRP flashables (you said you flashed using fastboot so it can't be this) or debloated stock ROMs.
Wolfcity said:
What do you mean with "stock but not official"?
Where did you get it from?
There are some sources for official firmwares signed by Motorola here on XDA so what makes you think the one you use isn't official?
If so that could be for sure the reason for problems for I have to say that I haven't seen unofficial stock ROMs except TWRP flashables (you said you flashed using fastboot so it can't be this) or debloated stock ROMs.
Click to expand...
Click to collapse
I mean it didn't come officially from Motorola. I got it from this:
getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated (It's not allowing me to post outside links because I'm a new user, so just add www to that)
lumbo7333 said:
I mean it didn't come officially from Motorola. I got it from this:
getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated (It's not allowing me to post outside links because I'm a new user, so just add www to that)
Click to expand...
Click to collapse
If you can flash the firmware by fastboot it's most likely an official signed firmware that was leaked. To be on the safe side use the firmware found here on XDA like this source:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Just make sure to use the same firmware you we're on or a newer one that fits to your region.
I recommend to reflash the latest stock firmware, maybe something went wrong the first time.
And remember to always make a backup before you flash anything that could cause problems.
It the latest stock firmware different from the stock rom I flashed?
You can also try the repair function in Lenovo Moto Smart Assistant app.
https://support.motorola.com/us/en/solution/MS126499
Hmm. Now my security updates are failing.
goodjuju said:
You can also try the repair function in Lenovo Moto Smart Assistant app.
https://support.motorola.com/us/en/solution/MS126499
Click to expand...
Click to collapse
Will doing that use official firmware?
lumbo7333 said:
It the latest stock firmware different from the stock rom I flashed?
Click to expand...
Click to collapse
lumbo7333 said:
Will doing that use official firmware?
Click to expand...
Click to collapse
Sure. The firmwares from Moto Smart Assistant are the same like the ones I've posted above, I compared the hash files.
Would be interesting to know what firmware you're on at the moment.
I'm on OPSS28.85-17-2
I thought my firmware was unofficial since it was leaked. Also do you why I can't update?
lumbo7333 said:
I'm on OPSS28.85-17-2
I thought my firmware was unofficial since it was leaked. Also do you why I can't update?
Click to expand...
Click to collapse
Any firmware you'll find is leaked even the official ones. Motorola doesn't release any firmwares except the ones you can download with Lenovo Motorola Smart Assistant.
The link I posted https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
contains official firmwares too. The latest one for the US (85-17-4) can be found there too.
What happens exactly when your OTA fails?
Wolfcity said:
Any firmware you'll find is leaked even the official ones. Motorola doesn't release any firmwares except the ones you can download with Lenovo Motorola Smart Assistant.
The link I posted https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
contains official firmwares too. The latest one for the US (85-17-4) can be found there too.
What happens exactly when your OTA fails?
Click to expand...
Click to collapse
- I download the update the update
- It reboots and goes into TWRP for some reason
- I have to manually reboot to system from TWRP
- My phone boots to system and says update unsuccessful
(This is a security update by the way.)
lumbo7333 said:
- I download the update the update
- It reboots and goes into TWRP for some reason
- I have to manually reboot to system from TWRP
- My phone boots to system and says update unsuccessful
(This is a security update by the way.)
Click to expand...
Click to collapse
You can't take any system updates when you have TWRP installed!
For OTA you have to be on unrooted full stock ROM incl. stock recovery. This is a very important rule.
So you have to ways to handle this:
- Flash clean stock firmware and apply to the OTA afterwards (if you flash the latest firmware 17.4 you don't need the OTA anymore). You will loose your internal storage data or skip the "erase userdata" command.
Firmware from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
- Take a TWRP flashable build but be aware that you can't take OTA updates at all in the future which is not needed as the firmwares are up to date.
TWRP flashables here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Wolfcity said:
You can't take any system updates when you have TWRP installed!
For OTA you have to be on unrooted full stock ROM incl. stock recovery.
So you have to ways to handle this:
- Flash clean stock firmware and apply to the OTA afterwards (if you flash the latest firmware 17.4 you don't need the OTA anymore). You will loose your internal storage data or skip the "erase userdata" command.
Firmware from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
- Take a TWRP flashable build but be aware that you can't take OTA updates at all in the future which is not needed as the firmwares are up to date.
TWRP flashables here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Click to expand...
Click to collapse
Will flashing a new build delete my data?