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!
See attachment. What's my next step? Am I doing anything wrong?
My 8.1 upgrade process (after I rooted on 8.0 using Magisk)
- fastboot flash boot Nov update 8.0 boot.img
- adb sideload the OTA 8.1 upgrade
- redo the Magisk root process with v14.5
What should I do?
samxsxiao said:
See attachment. What's my next step? Am I doing anything wrong?
My 8.1 upgrade process (after I rooted on 8.0 using Magisk)
- fastboot flash boot Nov update 8.0 boot.img
- adb sideload the OTA 8.1 upgrade
- redo the Magisk root process with v14.5
What should I do?
Click to expand...
Click to collapse
It's a problem with magisk 14.5, everyone has it on 8.1, just cosmetic, there is a unofficial 14.5 without the dbto img that will not show that message.
But magisk just needs updating. There is a unofficial magisk there with steps in there to correct it.
Some info here: https://forum.xda-developers.com/pixel-2-xl/how-to/tut-fix-dtbo-message-theres-internal-t3715620
and NO-dtbo Unofficial Build here: https://forum.xda-developers.com/pixel-2-xl/development/unofficial-build-thread-magisk-twrp-t3708555
depii said:
Some info here: https://forum.xda-developers.com/pixel-2-xl/how-to/tut-fix-dtbo-message-theres-internal-t3715620
and NO-dtbo Unofficial Build here: https://forum.xda-developers.com/pixel-2-xl/development/unofficial-build-thread-magisk-twrp-t3708555
Click to expand...
Click to collapse
I literally just fixed this on my device after trying for hours. I checked the "Preserve AVB 2.0/dm-verity" checkbox in the Magisk app. I then reinstalled MagiskManager 14.6 through the app (beta channel in app at time of writing). I then rebooted. This now allows you to flash you dtbo.img without having Magisk patch it. to do that. You do that just like you flashed the boot.img. commands would be add flash boot flash dtbo.img and then add flashboot reboot. Get the dtbo.img from the same factory image you got the boot.img.
Steps:
1. Check Preserve AVB 2.0/dm-verity
2. Install 14.6 MagiskManager beta
3. Reboot
4. Flash dtbo.img
5. Enjoy no annoying alert
I'm all good now, I've just got an issue where my locksceen clock font is Bold... not sure if this is because I was flashing font modules or something else but it is super annoying to the UX designer in me.
So as the official bootloader unlock broadened the audience of this from tinkerers/developers to basically everyone I thought this guide might me helpful for some...
PREREQUISITES:
- Unlocked bootloader (official or unofficial)
- latest magisk manager installed on phone (https://github.com/topjohnwu/Magisk/releases)
- latest fastboot and adb binaries from google(https://developer.android.com/studio/releases/platform-tools)
- latest twrp.img to boot (NOT FLASH), zip not needed (https://eu.dl.twrp.me/NB1/)
- Fully stock partitions (if you do not have this reflash latest stock via ostla), as OTA updates will do a integrity check.
- PC with WIN/OSX/LINUX with USB port^^ (on windows you might have to add .exe to the commands)
- disable automatic system updates in developer options, as you will still have to manually root the updated partition, so this makes sure you don't miss it. You still get notifications on available updates and can apply them easily(as you will see)
SETUP_STEPS:
1. Go into Magisk manager and "just download" the latest zip
2.1 Run
Code:
adb reboot bootloader
or reboot into download/fastboot mode via other means
2.2 Run
Code:
fastboot boot twrp-3.2.3-1-NB1.img
(change this when your version of twrp differs)
2.3 Flash the .zip magisk downloaded in 1.)
2.4 Reboot.
Congratulations you now have root!
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
Congratulations you can now reboot and will have an updated Android while keeping full root.
ALTERNATIVE GUIDE (without twrp, using prerooted boot.img)
(works for newest patch level, where twrp isn't working yet)
this guide works on newest patches as long as someone provides a prerooted boot.img.
So basically you either need a boot.img available or twrp...
Hopefully this helps until TWRP is compatible with September Security Patch
LINKS:
stock boot.img: (may to october patches)
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
prerooted boot.img: (may to october patches)
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
PREREQUISITES:
- same as above minus twrp
- patched/prerooted boot image (either create it yourself or use link provided here)
STEPS_TO_ROOT:
0.
Code:
adb reboot bootloader
or get into download mode otherwise
1.
Code:
fastboot boot NB1_prerooted_boot.img
1.1. The phone will boot into an temporarily rooted state,
2. Use magisk manager-> Install -> "Direct Install" to persist the root.
3. Reboot
Congrats you now have root even on versions where twrp isn't working yet....
Edit1:
Added link to all stock boot images from may to october security
Edit2:
Did the same for magisk prerooted
Edit3:
Added November images thanks to @czupyt
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Trissi said:
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Click to expand...
Click to collapse
That would be much appreciated. Alot of people who just unlocked bootloader cant root and the maintainer of our TWRP will take a couple of days
indeed
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
LoaderFabi said:
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
Click to expand...
Click to collapse
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
ironman38102 said:
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
Click to expand...
Click to collapse
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
LoaderFabi said:
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
Click to expand...
Click to collapse
No I get that but its just that I forget cuz this is my first phone with a/b partition. Anyway I got the phone to latest patch rooted so I'll see if I can get the untouched img
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
eric194 said:
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
Click to expand...
Click to collapse
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Trissi said:
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Click to expand...
Click to collapse
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
So did the prerooted Image Boot?
If so it basically has to be your boot/system partition(I had mine compromised too and couldn't fix it with just flashing boot.img had to reflash everything via ostla)
If even the prerooted Image didnt boot im sorry i don't really know how to help, as I have working root with Magisk on September patch and the Image boots just fine for me....
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Trissi said:
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Click to expand...
Click to collapse
Ok I will try that hope it'll work
Edit : thanks dude it worked
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Xayar said:
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Click to expand...
Click to collapse
Flash the full Stock build (i think its even may patch), via ostla (https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487), then follow this guide then reapply all updates by following the update steps...
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Xayar said:
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Click to expand...
Click to collapse
Are you trying to use OST LA 6.1.2? Cuz that doesnt work
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.
Hello,
I have a rooted (Magisk) A53 with TWRP. For a week, I get a notification asking me to update to security patch level of May 1st, 2023. I thought that with unlocked bootloaders, OTA wasn't possible, but whatever. My question is if it's possible to perform the update without losing TWRP and Magisk, and also if it's possible to keep all user data and installed apps. I have little time to spare after work and really don't want to go again through the process of resetting my phone.
Thanks.
No, it is not possible to update via FOTA in your rooted device. However, you can flash the latest stock firmware via Odin without any data loss. Download the latest firmware available for your device/CSC, patch the AP tar via the Magisk app and flash via Odin the BL, CP, AP, HOME_CSC and the Magisk patched tar in Download Mode.
Jahus said:
Hello,
I have a rooted (Magisk) A53 with TWRP. For a week, I get a notification asking me to update to security patch level of May 1st, 2023. I thought that with unlocked bootloaders, OTA wasn't possible, but whatever. My question is if it's possible to perform the update without losing TWRP and Magisk, and also if it's possible to keep all user data and installed apps. I have little time to spare after work and really don't want to go again through the process of resetting my phone.
Thanks.
Click to expand...
Click to collapse
you can install 7-zip zstd, then download your stock firmware, unpack AP with 7zip, then unpack super.img.lz then super.img until you have the system.img, you transfer system.img to your phone ( for example /sdcard) and select install and twrp and click images, and select your system.img and set it to system image, flash. Wipe cache and dalvik.
The easiest way is to update via smart switch and than reflash twrp and magisk. This has worked for me, the only thing is that I use orangefox instead of twrp because its much better.