Database Info

Update to August Security Update (NJH47F) and Retain Root?

I own a non-Verizon unlocked pixel and I am currently on the June security update with TWRP and Root. I found out how to update to the June update from this thread: https://forum.xda-developers.com/pixel/how-to/guide-how-to-install-june-security-t3617536. Is is safe to repeat the same process as the above thread for the August update or is there a different way to install the update? Has anyone tried to install the August update and retained root?

Yes that method works, but instead of doing this manually, download the factory image august, open the flash-all script and remove the "-w" from last line (so it will update everything automatically without wipe).
After may, the verified boot signer is useless, so you don't need it.
-flash factory
-boot to twrp
-install twrp
-flash root and/or kernel
-reboot
Everything works fine here.

Awesome, thanks!

Can't OTA update Nokia 3

I was unlocked bootloader, flash a custom room, but it bootloop. After flash stock room via OST LA and check system update, I don't have any Security patch. My system is in December 1st, 2017.
I have try flash OTA *.zip file by Stock recovery, the January patch can, but February not. It said install Abort. After that, I can't reboot system. It's always boot into recovery again.
In the past, I was joined beta labs, and I have rolled back my devices.
What can I do?

PLEASE HELP: Problem with AOSP ROM in Mi A1

Hey, I'm having a problem with updating my MiA1 using TWRP since january patch. Here's is, more or less, what's happening. AOSP Pie with december security patch is working flawless. I can reinstall this .zip with TWRP whenever I want.
But since january ROM, I'm having the same problem: if I install january/february patch, everytime I boot the phone, with or without gapps installed, the phone continues with a black screen after the Mi logo and nothing happens. Actually, if I double press the power button, the phone vibrates (as if the camera was opening) and if I single press it, the nav bar acts like im locking;unlocking the phone.
What I did:
-Checked with MD5. No error found
-Downloaded boot.img from the latest stock ROM from Xiaomi oficial site (same patch as AOSP).
-Installed boot.img without gapps: the screen works
-Installed boot.img before AND after installing gapps: bootloop in both cases.
-February update done with a clean install and over december patch: black screen as well
Can someone please help me? I don't know what I'm missing and don't want to get stuck with an older update.
I'm sorry if I missed something, kinda of a noob here

June 2020 Magisk patched/stock boot image

I've also installed and tested / verified that Kirisakura 4.5.6 is working great with this month's patch so far.
Magisk v20.4 Patched Boot Image: https://drive.google.com/file/d/1YdnoUxgJpzy-BVM6rXSM9Oorz2r9n_eK/view?usp=sharing
Factory Untouched Boot Image: https://drive.google.com/file/d/13RGYHr37HyCChBybu80SD9VrQA05G8vc/view?usp=sharing
THESE FILES ARE FOR 10.0.0(QQ3A.200605.001, Jun 2020 All carriers except TELSTRA) ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
If these files are helpful, please drop a thanks and let me know. =)

Question bootloop after installing magisk, help required

Hello guys!
Something wrong happened with my blujay, I need ur help...
So here's the complete story:
1) since december I didn't have OTA update, I don't know why, and the system was telling me it was outdated everyday but up to date in the update menu. so I decided to download the latest OTA bluejay-ota-tq1a.230205.002-1ec64b58.zip and apply it.
2) that worked nice, it booted up updated to this version. But proposed me another security update to get me to march 2023 security update.
3) Allright, security update done, but without root. So I donwloaded the full image corresponding to the OTA i made, bluejay-tq1a.230205.002-factory-1b04ccc9.zip, extracted the boot.img, patched it with magisk 26.1, then flashed it through fastboot.
4) this is where things get naughty, I had bootloop. I imagine this boot.img was correponding to my OTA update, but then another update was done, and the boot.img was wrong for this one.
5) I tried to reflash the patched and original boot.img, same. I tried to reapply the OTA, same, still bootloop.
6) I just tried to patch the full image, removing the -w from the flash-all.bat to not wipe my data (the whole point is that I can't loose all that), and still the same, I have a screen from android recovery saying it cannot load the system and proposing me to wipe, which I don't want.
What should I do ? Save me please!!

You updated from the Feb 2023 patch to the March 2023 patch in step 2. You then downloaded and patched the Feb 2023 boot.img file and applied it, with the system being at the March 2023 update. This is where the issue is. You need to download the March 2023 image and flash the boot.img from this. It is possible though, that you are at the April 2023 patch if you did this very recently.