My MetroPCS Moto E4 was just prompted with an OTA update, NCQ26.69-46-5-4. It says it's an update to include Android security updates through January 1, 2018.
I've got TWRP installed, and I'm rooted with Magisk, but I'm still on the stock ROM. I've been holding off to install Lineage until after the bump to 15.1, and (hopefully) "official" status.
Has anybody taken the OTA yet? If so, can you confirm that TWRP and Magisk still work?
OTA Release Notes:
https://mobilesupport.lenovo.com/us/en/solution/ms126534
wrkerr said:
My MetroPCS Moto E4 was just prompted with an OTA update, NCQ26.69-46-5-4. It says it's an update to include Android security updates through January 1, 2018.
I've got TWRP installed, and I'm rooted with Magisk, but I'm still on the stock ROM. I've been holding off to install Lineage until after the bump to 15.1, and (hopefully) "official" status.
Has anybody taken the OTA yet? If so, can you confirm that TWRP and Magisk still work?
OTA Release Notes:
https://mobilesupport.lenovo.com/us/en/solution/ms126534
Click to expand...
Click to collapse
You're going to have to jump through a few hoops to take that ota. I know there are methods for pixels and nexus' for doing it, but they likely won't work on this device.
Probably gonna have to backup your data, then flash the stock firmware, re root and restore data. But there shouldn't be any reason twrp won't work after updating.
Related
I have TWRP, but I'm still on android 6.0, security patch November 1, 2015, system version 24.11.18.clark_retus and no xposed. I have systemless root, so does full remove root in SuperSU then flashing the right recovery.img work to take all the OTA's till now? The February TWRP flashable OTA thread no longer has a live link.
HelpMeXDA said:
I have TWRP, but I'm still on android 6.0, security patch November 1, 2015, system version 24.11.18.clark_retus and no xposed. I have systemless root, so does full remove root in SuperSU then flashing the right recovery.img work to take all the OTA's till now? The February TWRP flashable OTA thread no longer has a live link.
Click to expand...
Click to collapse
This question is hard to answer... will it work? Maybe, we don't know. The problem is if you are rooted, you did it for a reason (or I would assume so) and you have made some changes to the /system partition over time. Doing a full unroot will not undo those changes. So if you do a full unroot, and fastboot the correct recovery image, then accept the OTA, the recovery is going start the OTA's installation script attempt to process it where it will start a checklist of items to verify, bootloader, boot image, system image, etc... the problem is we don't know what changes will cause the update to error out and which will allow it to apply.
To be honest, I don't think I have heard anyone say they have been able to successfully take this update without going back to pure stock, but ymmv.
The best thing to do would be to return to pure stock via the factory firmware images, we have a known good one of the May 2016 security update.
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
d.casper.b said:
I just updated to Nougat and safetynet fails. I have not even rooted or put TWRP back on.
I'm using the EU ROM.
Previously I updated from 6.0 Sept to 6.0 Dec patch by flashing the boot and recovery image (from the Sept. firmware) on the device, then taking the update. And then flashing TWRP and magisk again.
6.0 Dec. to Nougat didn't go as well. I flashed the boot and recovery but the phone didn't boot... I used the Sept firmware as I do not have the Dec. firmware (I'm very adamant about getting the latest stock ROM for flashing purposes..). Anyways, so I had to flash the entire 6.0 Sept ROM again (I did not wipe my data) and then update to the December patch and then to Nougat. Would have been so much easier if I had the December patch ROM to flash...
I actually uninstalled magisk before all of this. But actually, magisk/root would be gone after flashing the boot image anyway.
After updating to Nougat I have not done any modding, but safetynet fails... Why is this? And I can only start from scratch from the 6.0 September patch...so starting over is not sounding good.
Possibly due to the unlocked bootloader from reading other threads...
Click to expand...
Click to collapse
I have the same issue with safetynet, I could only fix it while flashing this: Universal SafetyNet Fix v2 beta 4 !
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
An unlocked bootloader will cause SafetyNet to fail in Nougat, at least in some devices (Pixel/Nexus, HTC 10/U11, OP3/3T too), could well be the reason it is failing.
I bought the phone yesterday and performed a 68 mb August update.
Got another December update (about 1080 MB, check screenshot in next post) but decided not to go ahead with.
Unlocked my bootloader, booted TWRP (didn't flash to system, stock recovery still intact), flashed magisk and the modules I needed.
My question is :
1. Is this "December update" Oreo? Didn't say anything in the description or the notification.
2. Will flashing any Nougat December update or Oreo update affect Magisk?
3. Will either of these updates even flash and not brick the phone along the way? (Magisk is systemless so they should not but just want to confirm)
Screenshot of update attached
Hey guys,
My G5+, which is running NPN25.137-83, rooted with Magisk, TWRP, Xposed just prompted me for an OTA update.
I'm guessing if i try to update i'll (best case scenario) break something, worst case brick my phone.
I'm running Aug2017 security patch.
This OTA update says it includes Security updates till Nov2017 + Stability improvements.
Any suggestions? Thanks!
seed_87 said:
Hey guys,
My G5+, which is running NPN25.137-83, rooted with Magisk, TWRP, Xposed just prompted me for an OTA update.
I'm guessing if i try to update i'll (best case scenario) break something, worst case brick my phone.
I'm running Aug2017 security patch.
This OTA update says it includes Security updates till Nov2017 + Stability improvements.
Any suggestions? Thanks!
Click to expand...
Click to collapse
Do not apply the update, it will end up failing as you have TWRP installed, but every time you restart your phone, it will boot to TWRP and then you'll have to reboot from TWRP to bootloader and then system. Anyways, I recommend waiting until the OP of the TWRP flashable stock thread updates the links with that update and then flash the update via TWRP. Make sure you go into developer options and turn off automatic updates. You can also use an app to freeze Motorola update service if you don't want to be notified about the update.
jeffsga88 said:
Do not apply the update, it will end up failing as you have TWRP installed, but every time you restart your phone, it will boot to TWRP and then you'll have to reboot from TWRP to bootloader and then system. Anyways, I recommend waiting until the OP of the TWRP flashable stock thread updates the links with that update and then flash the update via TWRP. Make sure you go into developer options and turn off automatic updates. You can also use an app to freeze Motorola update service if you don't want to be notified about the update.
Click to expand...
Click to collapse
Per the TWRP flashable stock thread guide, I downloaded the OTA and shared the zip there
Thanks @jeffsga88! I will disable automatic updates to avoid any accidents.
Firmware Finder shows there's a new update available for my BTV-W09. It's B355 dated 06/05/18. It's a small OTA, only 190mb. Has anybody installed it? Does anybody know what's in it?
Firmware Finder provides the changelog. It has the June security patches.
No netflix hd update? ****!
How install? I don't remember. [emoji28]. Thanks in advance.
Enviat des del meu ONEPLUS A6003 usant Tapatalk
Anyone have any luck applying this update with TWRP recovery? Looks like it is going to require a flash back to stock to apply?
I was only able to install it with stock. Even then, it had to be the full install, not the OTA update. That install locks the bootloader and unroots; so I then had to re-unlock, which of course wipes the entire device, and then restore from a Google and Titanium backup. Not sure updating is worth the pain. really.
My rooted tab is now threatening to install this update when I reboot. Does anybody remember how to stop a firmware update when it wants to update on reboot?
I don't think there's much to worry about as if you're rooted with TWRP, it'll just reboot into TWRP and wait for you to manually apply it, if you can find it on the file system.
I'm currently trying to apply B356 which was recently released. This minor update contains the July 2018 Google security patches. The last time I did this from B351, this is what I did:
Via TWRP, Installed the 2 full OTA zip files for B352 downloaded with firmwarefinder. This replaced TWRP with the stock recovery but did not wipe my data.
Rebooted, and applied B353 via the normal OTA through settings. This installed the B353 full package (2.52GB).
Reinstalled TWRP with fastboot (twrp_BTV-W09_5_greatslon.img)
Booted to TWRP & installed Magisk
Re-enabled the 5GHz wifi radio
However, this doesn't seem to be working with B356 thus far. Installing the Firmwarefinder zip files failed (at least update.zip did, I didn't try the other two) so I installed the FF B352 images mentioned above. However, applying the stock OTA through settings wants to install 3 patches (B353, June 18, July 18) of size 786MB. They downloaded successfully but then it fails to apply during the reboot.
Anyone else have any luck? What did you wind up doing?
Thanks!
Every time I've applied an update, I ended up locking the bootloader and then having the phone wiped when I unlock the bootloader. I'd love to find a way to update without locking the bootloader. If you find a way to that with this update, please let post how you did it!