Database Users

[MMB29P] January Android 6.0.1 Security Patch Factory Images Available

Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x

westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?

Nice find thanks

Now just need the modified boot.img for this newest build.

Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!

it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!

ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.

Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?

Can you post a link to OTA

bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.

So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!

Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.

Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk

Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.

dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.

Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.

tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.

I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.

Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app

How do I install the January security update on a rooted, unlocked Nexus6p?

Hello, dumb question. Like the subject says, how do I flash the OTA update on my phone? When I try to do it via the phone (notification tray), it gives me an error after the attempted flash.
I assume I need to download the OTA somewhere and sideload it. Where can I get it? My current build number is MMB29M
Thanks in advance
EDIT: I assume I just flash the system.img from the latest factory image?

Easiest way would be to download the factory image, edit the flash-all.bat to remove the -w flag (this is what tells it to wipe userdata) and flash the factory image.
Once you've flashed and booted, install TWRP, then flash systemless root in TWRP. If you have Xposed installed currently, you don't need to change anything with Xposed or your modules, just flash the Xposed installer again once you've flash TWRP and rooted, all your modules will still be installed and working once you flash the Xposed zip from TWRP.
This is what I have done for each of the security updates each month. If you can stand to wait, the new one for February will probably come out in 2-3 weeks, so it might save you from doing the process twice in a short period of time.
If you remove that -w flag from the batch file, the whole update process takes about 30 minutes, depending on how many apps you have to wait for it to optimize after flashing.

fury683 said:
Easiest way would be to download the factory image, edit the flash-all.bat to remove the -w flag (this is what tells it to wipe userdata) and flash the factory image.
Once you've flashed and booted, install TWRP, then flash systemless root in TWRP. If you have Xposed installed currently, you don't need to change anything with Xposed or your modules, just flash the Xposed installer again once you've flash TWRP and rooted, all your modules will still be installed and working once you flash the Xposed zip from TWRP.
This is what I have done for each of the security updates each month. If you can stand to wait, the new one for February will probably come out in 2-3 weeks, so it might save you from doing the process twice in a short period of time.
If you remove that -w flag from the batch file, the whole update process takes about 30 minutes, depending on how many apps you have to wait for it to optimize after flashing.
Click to expand...
Click to collapse
That's what I am using right now. However, with each month's update this process will take a lot of time. What I want to try is to apply the OTA update (which has much less size in MBs). That will work much faster. The only problem is that by using TWRP you will get stuck in the recovery. Did you tried to write back the original recovery and then take the OTA? Are there any chances to work with a systemless root?

foomanjee said:
Hello, dumb question. Like the subject says, how do I flash the OTA update on my phone? When I try to do it via the phone (notification tray), it gives me an error after the attempted flash.
I assume I need to download the OTA somewhere and sideload it. Where can I get it? My current build number is MMB29M
Thanks in advance
EDIT: I assume I just flash the system.img from the latest factory image?
Click to expand...
Click to collapse
If only there was a guide pinned at the top of the general section...
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sent from my Nexus 6P

Heisenberg said:
If only there was a guide pinned at the top of the general section...
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sent from my Nexus 6P
Click to expand...
Click to collapse
You mean there is a guide for that, how could I have missed it?

dratsablive said:
You mean there is a guide for that, how could I have missed it?
Click to expand...
Click to collapse
Not looking at the stickies?
Or not searching...

brichardson1991 said:
Not looking at the stickies?
Or not searching...
Click to expand...
Click to collapse
I forgot my <sarcasm> tags.

Update OTA with root and TWRP

I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?

ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!

ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433

ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
You must do the following:
1. Return to complete stock - that means get rid of root and TWRP. Best way to do that is download the factory image from Google, extract the boot, recovery, and system images from the factory image, and Flash those, for example: fastboot flash recovery recovery.img Don't flash data.img so you can keep your data.
2. OTAs depend on stock recovery to load, so now that you're back to stock, you have 2 choices. You can simply boot your phone normally, wait for the notification for the update, install it, and you're done - or, you can access android's stock recovery and side load the OTA zip using ADB. Good luck
Sent from my Nexus 6P using Tapatalk

Gamer_Josh said:
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
Click to expand...
Click to collapse
I forgot to mention that I also had TWRP recovery installed. The result was like it is with a normal OTA update, as none of my data/apps/settings were affected. Worked like a charm!

DJBhardwaj said:
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.

ponzi314 said:
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
Click to expand...
Click to collapse
You are sure that you used the correct OTA file?

DJBhardwaj said:
You are sure that you used the correct OTA file?
Click to expand...
Click to collapse
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3

ponzi314 said:
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
Click to expand...
Click to collapse
That's weird. It has worked for me everytime, and most users here.

DJBhardwaj said:
That's weird. It has worked for me everytime, and most users here.
Click to expand...
Click to collapse
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.

tech_head said:
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
Click to expand...
Click to collapse
Sideloading the update, right?

DJBhardwaj said:
Sideloading the update, right?
Click to expand...
Click to collapse
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.

tech_head said:
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
Click to expand...
Click to collapse
I also avoid using any toolkits. Yes I know they are fast and easy, and of course someone's hardwork. But I like to everything manual, same as you. :highfive:

I usually like to do things like that manually, because I like to know how things work. But I was under a bit of a time crunch at that point, so decided to try the Nexus Root Toolkit. Though I do understand the procedure of sideloading OTA updates via ADB, from researching and reading on the forums here.
Anywho, I hope you are able to get it going OP.

The OTA fixed it for me, thank you so much!

6t mclaren getting back to full stock, please help

quick question,
I am the owner of a Oneplus 6t Mclaren, I installed twrp and magisk to root my device, but at the moment I would like to return to stock, i mean full stock. I thought uninstalling magisk through the itself would be enough to remove root but its not. whenever I try to update i receive a notification saying that my bootloader is unlocked.
What happens if I update my oneplus 6t mclaren, magisk is already uninstalled, I only have twrp bluespark something on my device. Please let me know

abati said:
quick question,
I am the owner of a Oneplus 6t Mclaren, I installed twrp and magisk to root my device, but at the moment I would like to return to stock, i mean full stock. I thought uninstalling magisk through the itself would be enough to remove root but its not. whenever I try to update i receive a notification saying that my bootloader is unlocked.
What happens if I update my oneplus 6t mclaren, magisk is already uninstalled, I only have twrp bluespark something on my device. Please let me know
Click to expand...
Click to collapse
To update a rooted device, you need the full OTA.
You then choose the local update option.

tech_head said:
To update a rooted device, you need the full OTA.
You then choose the local update option.
Click to expand...
Click to collapse
can you ellaborate a bit, my goal is to get rid of root fully, i want to make the phone original.

abati said:
can you ellaborate a bit, my goal is to get rid of root fully, i want to make the phone original.
Click to expand...
Click to collapse
If you are not on the current OS (9.0.11) then download the fullOTA and install it locally from the update menu.
Typically just having your BL unlocked will not prevent an OTA.
TWRP, Magisk will cause the normal OTA to fail.
If you download the full OTA (normally about 1.75GB) and install locally, it will remove TWRP and Magisk and take you back to stock.
A full OTA installed from the system menu will install the factory kernel, system and vendor.
On thing you will want to do is install the OTA, reboot then install the OTA again.
This makes sure that both A & B partitions are flashed.

tech_head said:
If you are not on the current OS (9.0.11) then download the fullOTA and install it locally from the update menu.
Typically just having your BL unlocked will not prevent an OTA.
TWRP, Magisk will cause the normal OTA to fail.
If you download the full OTA (normally about 1.75GB) and install locally, it will remove TWRP and Magisk and take you back to stock.
A full OTA installed from the system menu will install the factory kernel, system and vendor.
On thing you will want to do is install the OTA, reboot then install the OTA again.
This makes sure that both A & B partitions are flashed.
Click to expand...
Click to collapse
I am on oxygen os 9.0.9, after checking update, it says download complete, install now, but i need to skip the part were it says install now right ? if yes where can I find the ota it downloaded ?

abati said:
I am on oxygen os 9.0.9, after checking update, it says download complete, install now, but i need to skip the part were it says install now right ? if yes where can I find the ota it downloaded ?
Click to expand...
Click to collapse
I just found out something, if look on my device for the ota folder there is nothing to be found in the root directory of the device, but when I connect the mclaren to the pc, I can see a folder called .Ota , in that folder there is zip file about 1.62gb that should be the full ota I believe, but on the original oneplus filemanager the .Ota folder is not visible, also on es file manager it is not visible. Could this be the cause of uninstalling magisk ? cuz I uninstalled magisk.

abati said:
I just found out something, if look on my device for the ota folder there is nothing to be found in the root directory of the device, but when I connect the mclaren to the pc, I can see a folder called .Ota , in that folder there is zip file about 1.62gb that should be the full ota I believe, but on the original oneplus filemanager the .Ota folder is not visible, also on es file manager it is not visible. Could this be the cause of uninstalling magisk ? cuz I uninstalled magisk.
Click to expand...
Click to collapse
Download the OTA from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Post #2.
Follow the instructions in Post #3

tech_head said:
Download the OTA from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Post #2.
Follow the instructions in Post #3
Click to expand...
Click to collapse
i will try that thanks

tech_head said:
Download the OTA from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Post #2.
Follow the instructions in Post #3
Click to expand...
Click to collapse
just a simple question that ota frimware from the link you send me, it should not bring harm to the mclaren when I flash it right ? I mean If I flash it, the device will keep its original mclaren theme right?

Only one version of the 9.0.11 firmware as far as I know. Has everything.

tech_head said:
Only one version of the 9.0.11 firmware as far as I know. Has everything.
Click to expand...
Click to collapse
it worked thnx for al the info !

abati said:
it worked thnx for al the info !
Click to expand...
Click to collapse
No problem.

tech_head said:
Only one version of the 9.0.11 firmware as far as I know. Has everything.
Click to expand...
Click to collapse
It Does, just flashed it on my 1+ 6T Mc all is good

How to update to 11.0.8.8IN11AA on pre rooted device

Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.

paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.

MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?

Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.

MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.

paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.

Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.

Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...

datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?

Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches

What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.

It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.

Could someone post boot img I can't find this 11.8.8 to download.
Thanks.

Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.

If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.

h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541