Updating LineageOS 16 from the 29th October build to the 7th November (and later) build makes the device bootloop into TWRP.
Is there anything I can do to fix this?
I used the built-in updater for this.
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 downgraded from oreo to nougat ,than while trying to update to last december update it says failed,Any help?
fastboot flashing december update image
so today as of regular cleaning and restoring my g4 plus to stock...i restored and think i updated it to the the february security path xml zip via fastboot using (ATHENE_NPJS25.93-14-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) file...the problem was that i was scared to hell when the security patch downgraded itself to september 2017 even on using feb'18 file and the stock recovery returned "no command" error on startup and "error" on updating so...
can please anyone tell me...
1.what's the current version of the bootloader on the latest april/feb'18 build?
2.can i flash apr'18 build over the the one flashed before with all the commands safely(im too worried about hard bricking it!!!!!)?
thank you so much in advance!
1)The NPJS25.93-14-10 firmware is the September 2017 security patch firmware, so flashing that would flash the Sept 2017 security patch to your device. You'd have likely received the December 2017 NPJS25.93-14-13 update then the NPJS25.93-14-15 Feb 2018 update. I'm not entirely sure which update you tried to flash then...
2)The NPJS25.93-14-18 firmware is currently the latest April 2018 security patch firmware, available from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 I've seen it flashed on Indian, Brazilian, EU and UK devices, not sure about other territories. Current bootloader version on the April 2018 firmware is B1:07.
3)You should be able to flash the April 2018 firmware over whatever you flashed, and as it's the latest firmware, it should not hard brick your device. Please avoid flashing older firmwares or if you do, be very careful with OTA updates.
4)The 'no command' screen is the normal screen for stock recovery. If I recall, if you're on that screen, hold down power then tap the volume up key, then release both to access the stock recovery.
I installed lineage os 15.1 on note 4x.Recently the September update has been rolled out.When the updater went to twrp to install the update it started showing encrypted data.Input password what to do
i had the same problem, just download the latest TWRP and it should fix this
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.