I got the OTA for 10.0.43 yesterday, April 1 (no April fool's lol). Change log only said security updates for March 1, 2021. At least OnePlus and Tmobile have been keeping it relatively up to date...not mentioning OOS 11, but 1+ just finally released OOS 11 Final for 7/P/7T/P, so hopefully it won't be more than a couple months before we get it on our phones.
PSA: You can no longer do the "Install to Inactive Slot" shortcut in Magisk after accepting/installing the OTA but before rebooting. It won't boot the new version and will fall back to the previous one (update failed). I'm not sure when this started, but by looking at the upgrade logs, it now checks the checksums on all partitions not only before rebooting but also while first booting after an update. So if Magisk has already been installed by using "Install to Inactive Slot", the update will fail.
Related
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
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.
I'm looking at getting one of these but wondering what version it is up to now? Sites where they sell it only ever show the version that it was initially released on. Is it still getting updates? What about security patch level? Just asking because I am having a hard time finding a local store that has it on the shelf to give it a few minutes of hands on.
Thanks.
The Z380M is upgradeable to Android 7.0. The latest security patch level is January, 2018. You can check the Asus support site downloads for info on the latest FW. They've been pretty timely with security updates. But they don't fix bugs with the OS itself, like battery calibration and log spamming And I doubt there will be any more major updates to this tablet.
Now FOTA (system update) offers update 308MB size, I tried to flash but when android reboots it reboots in TWRP (my P00A rooted and have TWRP) and nothing happening, tried rename update file to zip and flash via TWRP but not flashing, TWRP error 12
@PxYra, the incremental update needs a clean, unmodified firmware. It won't install to rooted devices or any other FW configuration where TWRP is forced to stay in place. Please download the full FW package from Asus' support site, install then reroot, etc.
My PH-1 was stock OS (Pie, Sep 2018) rooted (Magisk 17.1, Manager 7.5.1, TWRP 3.2.3). Over a year ago I accidentally clicked on the "System Update" popup which of course took away my root.
At the time I just decided I would take the final OTA updates to the last released security patch and Android 10. Been there for all this time, but I want root back now.
Is it as simple as just adb sideloading Magisk again? (Can I just use the old 17.1.zip file I still l have on the phone itself?)
I don't want to lose any data btw..
Also, TWRP doesn't load up when I try to boot into "Recovery Mode" using the power buttons from being powered off. I just get "No command " printed on the screen under the "Android robot on his side" image. I have to hit the Pow + VolUp keys to get the regular Android Recovery menu.
I assume it's still sitting on the inactive slot? Or could it have been totally erased by the subsequent updates I took going from Pie to 10.
Do I need to downgrade FIRST to the Jan 2020 patch level (I'm on the last release, Feb 2020) in order to be successful? And/or have working TWRP?
Thanks
Well, have look at Magisk's official Installation Instructions.