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

Stock and custom kernel flasher script (pre-made or send in kernel)

Hi, this is my 3rd post on the great XDA Forums.
Use this kernel flasher script at you own risk !
I am not responsible for any damage or problems such as you getting late for work because the alarm didn't go off, or the phone causing a nuclear explosion
Click to expand...
Click to collapse
.
PLEASE DO NOT SHARE MY WORK OR NIABOC79's WORK WITHOUT PERMISSION.
I present to you my custom flashing script for recovery.
WHY DID I MAKE THIS SCRIPT:
I made this from my own experience because sometimes I needed to flash a stock kernel back and I didn't want to download a whole ftf or rom to get my phone working again (especially because I will have needed to wait for the 'Android is starting' 'Optimizing Apps' rubbish, so I made this, which flashes the kernel file within the zip in recovery (which you can hot boot) ( I prefer the @DooMLoRD V11 kernel : http://forum.xda-developers.com/showthread.php?t=2735137) .
If you want me to make a kernel flasher for your ROM kernel and any other standalone kernels for the Sony Xperia Z2, please send me the name of the ROM (link) and 'boot.img' file (upload it to Drive, MEGA, Mediafire etc) (I would prefer that you send the file renamed to 'boot.elf'). I will then archive it with credits to the creator of the ROM and/or kernel in the script if needed or existent. :highfive:
I have also attached these zips to the thread in case the original gets removed. :laugh:
List of Kernel Flasher Scripts:
CUSTOM:
23.5.A.0.570/575 KERNELS
Click to expand...
Click to collapse
Abricot 8.1 .570/575: https://drive.google.com/open?id=0B6aEcBP7FwsWNVN1eFBLb1ktd00
STOCK:
STOCK 23.5.A.0.486 KERNELS
Click to expand...
Click to collapse
These are from the beta firmware so don't expect awesome performance
Stock 23.5.A.0.486 Kernel : https://drive.google.com/file/d/0B6aEcBP7FwsWTUJlWkJjNWFDVFE/view?usp=sharing
STOCK 23.5.A.0.575 KERNELS
Click to expand...
Click to collapse
Yes, I know they are the same but people beg to differ...
eXistenZ 2.0.0 Stock 575 Kernel : https://drive.google.com/open?id=0B6aEcBP7FwsWYVlLMWNuOS1sU28
Stock 23.5.A.0.575 Kernel : https://drive.google.com/file/d/0B6aEcBP7FwsWbHFQUjUzY2JBMTA/view?usp=sharing
STEPS ON HOW TO FLASH THE KERNEL ZIP:
DOWNLOAD DOOMKERNEL V11, EXTRACT IT, FLASH THE BOOT.IMG VIA FASTBOOT WITH CMD,
COMMAND FOR CMD: fastboot flash boot boot.img
THEN GO IN RECOVERY (volume down when booting) AND FLASH THE ZIP YOU NEED.
Credits:
DooMLoRD V11 Kernel for making the whole process easy: @DooMLoRD Thanks for all your amazing kernels that we all deeply miss.
eXistenZ 2.0.0 Stock 575 Kernel : @niaboc79 Thanks for the great roms you make, and for your 'updater-script' script which I have modified.
Thanks for your time
Regards,
Mohamed

Can a moderator please move this thread to android development, thanks.

Can you give me the boot.img for Marshmallow stock rom for xperia z2?? Thanks

Mostafa Sherif said:
Can you give me the boot.img for Marshmallow stock rom for xperia z2?? Thanks
Click to expand...
Click to collapse
Sure, which build number?

moman2000 said:
Sure, which build number?
Click to expand...
Click to collapse
The latest one for xperia z2 stock marshmallow .575

Mostafa Sherif said:
The latest one for xperia z2 marshmallow .575
Click to expand...
Click to collapse
Ok, Making it right now... Thanks for the quick reply
Do you also want a flashable version too?
EDIT: IT SEEMS LIKE THE OLD METHOD OF EXTRACTING THE BOOT IMAGE WONT WORK.
I NEED YOU TO DOWNLOAD DOOMKERNEL V11 (link in OP), EXTRACT IT, FLASH THE BOOT.IMG VIA FASTBOOT WITH CMD,
COMMAND FOR CMD: fastboot flash boot boot.img
THEN GO IN RECOVERY (volume down when booting) AND FLASH MY ZIP I AM MAKING.

@Mostafa Sherif Here is the zip for .575 stock kernel.
https://drive.google.com/file/d/0B6aEcBP7FwsWbHFQUjUzY2JBMTA/view?usp=sharing
I have updated my previous post with instructions on how to flash it. Good luck

moman2000 said:
Ok, Making it right now... Thanks for the quick reply
Do you also want a flashable version too?
EDIT: IT SEEMS LIKE THE OLD METHOD OF EXTRACTING THE BOOT IMAGE WONT WORK.
I NEED YOU TO DOWNLOAD DOOMKERNEL V11, EXTRACT IT, FLASH THE BOOT.IMG VIA FASTBOOT WITH CMD,
COMMAND FOR CMD: fastboot flash boot boot.img
THEN GO IN RECOVERY (volume down when booting) AND FLASH MY ZIP I AM MAKING.
Click to expand...
Click to collapse
Doomkernel v11??? Seriously? Doomkernel didn't get any update since 2014. That's almost 2 years. It was good for a while, when Z2 first released. Now noone is using it. It is dead. Also, @DooMLoRD probably not coming on XDA anymore.

V4LKyR said:
Doomkernel v11??? Seriously? Doomkernel didn't get any update since 2014. That's almost 2 years. It was good for a while, when Z2 first released. Now noone is using it. It is dead. Also, @DooMLoRD probably not coming on XDA anymore.
Click to expand...
Click to collapse
I am using that kernel for the process of flashing it because it has built in recovery that we can all use, also, i provided the links so people do not have to go searching for it.... or for any other kernel.
Regards,
Mohamed

moman2000 said:
Ok, Making it right now... Thanks for the quick reply
Do you also want a flashable version too?
EDIT: IT SEEMS LIKE THE OLD METHOD OF EXTRACTING THE BOOT IMAGE WONT WORK.
I NEED YOU TO DOWNLOAD DOOMKERNEL V11 (link in OP), EXTRACT IT, FLASH THE BOOT.IMG VIA FASTBOOT WITH CMD,
COMMAND FOR CMD: fastboot flash boot boot.img
THEN GO IN RECOVERY (volume down when booting) AND FLASH MY ZIP I AM MAKING.
Click to expand...
Click to collapse
moman2000 said:
@Mostafa Sherif Here is the zip for .575 stock kernel.
https://drive.google.com/file/d/0B6aEcBP7FwsWbHFQUjUzY2JBMTA/view?usp=sharing
I have updated my previous post with instructions on how to flash it. Good luck
Click to expand...
Click to collapse
Thank you, i'm really appreciate your work.
Actually i want it to port boot.img from Xperia Z3 to Xperia Z2 so it will help me. You have a guide or something like that which can help me in porting boot.img from one device to another!!
Another thing, how can i unpack and repack the boot.elf?? Which tool i have to use or what i have to do??
Thanks bro

moman2000 said:
I am using that kernel for the process of flashing it because it has built in recovery that we can all use, also, i provided the links so people do not have to go searching for it.... or for any other kernel.
Regards,
Mohamed
Click to expand...
Click to collapse
All the custom kernels for Z2 have built in recovery.

V4LKyR said:
All the custom kernels for Z2 have built in recovery.
Click to expand...
Click to collapse
I am aware of this but I think doomkernel is the easiest to use in my opinion, I know there are more awesome custom kernels
Such as abricot 8.1

moman2000 said:
I am aware of this but I think doomkernel is the easiest to use in my opinion, I know there are more awesome custom kernels
Such as abricot 8.1
Click to expand...
Click to collapse
Doomkernel is from 2014
ANY kernel is better than it :fingers-crossed: But yeah, Abricot is awesome indeed! :good:

V4LKyR said:
Doomkernel is from 2014
ANY kernel is better than it :fingers-crossed: But yeah, Abricot is awesome indeed! :good:
Click to expand...
Click to collapse
I approve!:highfive:

Hi, I'd just like to thank you for this. I can't access recovery anymore since I flashed the DRM fix. By the way, I'm on the Xperia Z2 (eXistenZ 2.5.0)
Anyways, I flashed the advanced stock kernel to get recovery, then flashed the 2.5.0 update, then flashed this to get my kernel back to 575. I can't seem to fastboot a recovery though. Any ideas?
EDIT: Fixed my own problem. Thanks again, though!

iArvee said:
Hi, I'd just like to thank you for this. I can't access recovery anymore since I flashed the DRM fix. By the way, I'm on the Xperia Z2 (eXistenZ 2.5.0)
Anyways, I flashed the advanced stock kernel to get recovery, then flashed the 2.5.0 update, then flashed this to get my kernel back to 575. I can't seem to fastboot a recovery though. Any ideas?
EDIT: Fixed my own problem. Thanks again, though!
Click to expand...
Click to collapse
Glad you fixed it, what exactly was the problem to begin with so i can help you prevent it in the future?
And by the way if you can flash the zip you do not need to fastboot a advanced stock kernel. I just added it for those running into bootloops from flashing the wrong things or anything else preventing them from booting their phones.

moman2000 said:
Glad you fixed it, what exactly was the problem to begin with so i can help you prevent it in the future?
And by the way if you can flash the zip you do not need to fastboot a advanced stock kernel. I just added it for those running into bootloops from flashing the wrong things or anything else preventing them from booting their phones.
Click to expand...
Click to collapse
The problem was, if you flash the DRM fix, you can't access recovery. Some fixed it by fastbooting a recovery, but it didn't work for me. Apparently the /cache/recovery wasn't being mounted properly. I just repaired the folder using recovery (had to flash the advanced stock kernel to actually GET into recovery) then it's working again.

I cannot get into recovery mode in 575. Only way I found was to follow your suggestion and flash boot.img from DoomKernel.
Flashing your zip at this point blocks again the possibility to enter in recovery mode.
Any app (ROM Manager, ROM Toolbox, ecc.) is able to reboot in recovery mode with 575.
Have you any suggestion?
Thx

mercinellim said:
I cannot get into recovery mode in 575. Only way I found was to follow your suggestion and flash boot.img from DoomKernel.
Flashing your zip at this point blocks again the possibility to enter in recovery mode.
Any app (ROM Manager, ROM Toolbox, ecc.) is able to reboot in recovery mode with 575.
Have you any suggestion?
Thx
Click to expand...
Click to collapse
Are you pressing the volume down to get in recovery?
Are you sure you have flashed the right zip? If not I could also provide you a custom kernel called Abricot 8.1 in the zip you can flash

moman2000 said:
Are you pressing the volume down to get in recovery?
Are you sure you have flashed the right zip? If not I could also provide you a custom kernel called Abricot 8.1 in the zip you can flash
Click to expand...
Click to collapse
Yes, with the DoomKernel boot.img I can get into the recovery pressing Vol Down button and then Vol Up (if not fail with an error saying there is no SW to download). Then I flashed the zip. After that if I reboot with vol Down nothing happens until I release the butto and then normal boot goes on.
I tried also with the Advanced MM Kernel boot, but nope.
TWRP and CWM are there since I can get into them if the Doom Kernel boot is installed, but as soon as I chenge the boot.img with stock they cannot be reached. No app is able to reboot into recovery (even with the DoomKernel boot).

TWRP

When are we getting TWRP? or will this phone not be supported?

popeye2468 said:
When are we getting TWRP? or will this phone not be supported?
Click to expand...
Click to collapse
Arter97 kernel has TWRP baked in and it works great.

Does that kernel work on PIE

mattwheat said:
Does that kernel work on PIE
Click to expand...
Click to collapse
Yes. I'm on Razer Phone 2 Pie MR1 running the r7 variant of the kernel

Download the image file and fastboot it to both boot_a and boot_b

blackknightavalon said:
Download the image file and fastboot it to both boot_a and boot_b
Click to expand...
Click to collapse
Does flashing arter97 kernel erase my data

Crosbuble said:
Does flashing arter97 kernel erase my data
Click to expand...
Click to collapse
If the bootloader is already unlocked then no, but if you have to unlock your bootloader it will wipe the phone.

process to flash the arter97 kernel in Razer Phone 2
DarkestSpawn said:
Yes. I'm on Razer Phone 2 Pie MR1 running the r7 variant of the kernel
Click to expand...
Click to collapse
Hi guys,
I'm wondering how can I flash this kernel, cause once I download it from GitHub it's a folder not a.img.
Is there somebody who can help me?
I would really like to install a stock ROM cause mine sadly is branded.

js 996 said:
Hi guys,
I'm wondering how can I flash this kernel, cause once I download it from GitHub it's a folder not a.img.
Is there somebody who can help me?
I would really like to install a stock ROM cause mine sadly is branded.
Click to expand...
Click to collapse
Go to Arter97's post in the "ROMs, Kernels, Recoveries, Other..." section, where you can click the "Arter97" link that will take you to the right place.
From that link you should be at the "aura" folder. From there, go to kernels, then to latest([r9] as of this reply) folder and download the img file, not the zip.
For every update after that, grab the zip and flash it in TWRP. You should also make sure your bootloader is unlocked as per the Razer Dev site's instructions and that you've used their official PIE MR1 firmware images to convert your phone to the global variant from whatever brand yours is.

blackknightavalon said:
Download the image file and fastboot it to both boot_a and boot_b
Click to expand...
Click to collapse
How do you fasboot?

etsai3 said:
How do you fasboot?
Click to expand...
Click to collapse
Don't take this wrong, but if you are asking "How to fastboot", i would not do anything at the moment. Search XDA or Google for that matter and learn about fastboot, and what you are doing when you perform fastboot commands. You can mess up your device rather quickly, then you will be asking why and how to fix. Take a couple days and understand what we mean when we say fastboot flash xxxxxxxx. These commands are basically flashing files like the OS, boot system, etc. I am not a dev nor do i know all the system partitions and all the proper or technical lingo. But i do know if you flash the wrong img/file from the wrong device or for another device, it will bork your device.
Again, not trying to bash, but asking this question will not get many replies, if any at all, especially how to perform a fastboot command. Do the research, then you can read on the device thread, for your device, and understand what is meant.

Deleted
Solved

MR3 Global March 2020 Security Update

It's available via OTA

JDBarlow said:
It's available via OTA
Click to expand...
Click to collapse
Are you able to use arter kernel with this update?

kountry83 said:
Are you able to use arter kernel with this update?
Click to expand...
Click to collapse
should be able to, I don't see why it wouldn't work

Arter works fine with it. I updated this morning.

Do you have to have stock recovery + locked bootloader to install?

BeardKing said:
Do you have to have stock recovery + locked bootloader to install?
Click to expand...
Click to collapse
I had Arter's kernel installed. I thought it would be enough to reflash stock kernel but that doesn't work. Don't think we should have to relock bootloader just to flash a system update....
Peace

chris5s said:
I had Arter's kernel installed. I thought it would be enough to reflash stock kernel but that doesn't work. Don't think we should have to relock bootloader just to flash a system update....
Peace
Click to expand...
Click to collapse
What do you mean by flash the system update? Sorry I'm new here, but what exact steps did you do? I am currently on a rooted MR2 with Arter 's kernel.

Received security updates notification a few hours ago.
Still no P-MR3 factory image on Razer dev site.
If need relock bootloader to update I guess I will wait a period. (I hope we can get Android 10 update

finixs said:
Received security updates notification a few hours ago.
Still no P-MR3 factory image on Razer dev site.
If need relock bootloader to update I guess I will wait a period. (I hope we can get Android 10 update
Click to expand...
Click to collapse
compared to MR2, we probably will need to wait for months until razer puts the factory images on their dev-page...
I really can't understand what takes so long for that last step. Just upload that crap and you're done, razer

Can the update be flashed in TWRP without disturbing Magisk or Arter's kernel? I've grabbed the update zip via a link I found by generating a bug report in the developer options and searching for "System_Update". I'm just wondering if it's safe to flash over everything.

Don't really need to relock bootloader and such, Just flash Stock recovery and the update will go through Smoothly, and then you can Reflash your twrp/magisk.

Monopod said:
Don't really need to relock bootloader and such, Just flash Stock recovery and the update will go through Smoothly, and then you can Reflash your twrp/magisk.
Click to expand...
Click to collapse
Didn't work for me. What system mods did you have in place? Kernel, root, etc?
Peace

chris5s said:
Didn't work for me. What system mods did you have in place? Kernel, root, etc?
Peace
Click to expand...
Click to collapse
Arter97 R12 Kernel with Twrp and magisk root.

Monopod said:
Arter97 R12 Kernel with Twrp and magisk root.
Click to expand...
Click to collapse
Did you just fastboot flash stock boot image?
Did you install f2fs.zip or any other mods?

chris5s said:
Did you just fastboot flash stock boot image?
Did you install f2fs.zip or any other mods?
Click to expand...
Click to collapse
No mods not even F2fs and Vold, for the stock boot image I simply fastboot flash it.

I flashed f2fs, wondering if that's why I can't flash update even after flashing stock kernel? ?
Peace

https://github.com/RadekBledowski/Razer_Phone_mods/blob/master/magisk_patched.img?raw=true
here's magisk patched version
to flash arter kernel you have to flash it via zip not fastboot so flash it first via fastboot and flash it again but in twrp as zip

So what I see is you can update without reloacking your bootloader by... (I'm asking if this is right)
1. Fastboot flash stock boot.img
2. Update normally
3. Reflash magisk, your custom kernel and what not.
Correct?

I've tried flashing back to stock kernel but it didn't work for me.

I usually perform the "reset to factory" task from the razer images (properly commenting the line that erases userdata)
After that you just are with original stock and you can update via OTA as usual.

Bootloader Question

Hi all! I am sorry if this has been asked before but I couldn't find a definitive answer in here.
I bought OnePlus 8 Pro from the official website in April and I feel it's time to flash a custom kernel. I've been modding my phones since 2011 using Xperia Neo back then.
1. If I unlock my bootloader will I still be able to receive official updates?
2. How exactly do you flash a custom kernel? At the moment I have no intentions on rooting the phone.
3. Is the procedure for flashing a custom ROM the same as the kernel?
4. Does unlocking my bootloader delete everything from the phone?
A lot has changed since Android 8 and 9 so I feel like a complete noob.
Thank you for the help in advance!

1. Yes as long as your boot partition is stock/aka not rooted or using custom kernel, you can take regular otas.
2. If rooted you can use ex kernel manager... If not you'd boot to bootloader and use fastboot commands to modify the boot image.. Note after this you wouldn't be able to take otas until you flash back stock boot img.
3. Yes very similar, you'd flash different partitions in bootloader using fastboot commands.
4. Yes, same as relocking.

You should be able to install OTA regardless of what kernel you're using.
I recommend Franco Kernel Manager for flashing kernels.
There should be instructions on how to install ROMs with fastboot. You use fastboot and fastbootd (new fastboot for system) depending on what partition you flash.

Lossyx said:
You should be able to install OTA regardless of what kernel you're using.
I recommend Franco Kernel Manager for flashing kernels.
There should be instructions on how to install ROMs with fastboot. You use fastboot and fastbootd (new fastboot for system) depending on what partition you flash.
Click to expand...
Click to collapse
I reckon I need to root to use Franco kernel manager and I shoul be able to flash any kernel just using fastboot?
Regarding the OTA, I read that you need to be on stock kernel to be able to install it so I guess I will wait for the December update and then go through the whole process of bootloader unlock etc.

kokope28 said:
I reckon I need to root to use Franco kernel manager and I shoul be able to flash any kernel just using fastboot?
Regarding the OTA, I read that you need to be on stock kernel to be able to install it so I guess I will wait for the December update and then go through the whole process of bootloader unlock etc.
Click to expand...
Click to collapse
Yes you need root in order to flash a kernel zip using kernel manager. Flashing a kernel through fastboot requires just the boot image, which i don't think any kernel provides standalone.
And no, you don't need to be have stock kernel to flash an OTA. I have no idea why someone would write that.

Lossyx said:
Yes you need root in order to flash a kernel zip using kernel manager. Flashing a kernel through fastboot requires just the boot image, which i don't think any kernel provides standalone.
And no, you don't need to be have stock kernel to flash an OTA. I have no idea why someone would write that.
Click to expand...
Click to collapse
I haven't tried a lot of kernels but in my experience coming from other phones like pixels.... When boot.img gets modified it will fail ota updates...I tried it with this phone with a rooted boot.img and it failed so I assumed a kernel modified boot.img would be the same. Much apologies if I'm incorrect... But that's my reasoning for writing my post.

Updating isn't an issue.
My guide for doing just that amongst other things.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
Personal I use ex kernel manager. Hasn't failed me yet.
Auth apps have worked for me, as does gpay so you should be ok.
Titanium / swift might do it but the OS won't be the same so the apps could notice that.
Just set them back up, the more you do it the easier it is.
Probably best to deactivate first so it's easier to enrol on your new OS