Database Users

[Answered] Unroot with Iconia Root

So I rooted a couple of days after I got the Tab, left the Stock Rooted Rom and then loaded the Honey Villian Kernel for O/C purposes. Since O/C is the only thing I do with Root, I am thinking of going back to Unrooted.
My question is, in Iconia Root, if I hit the Unroot with the Custom Kernel still installed what happens? or since I do not have a copy of the original Kernel, how can I reinstall it before Unrooting?
Build is Acer_A500_4.010.13_com_gen2
Current Kernel is 2.6.36.4 Honeyvillain- 1.0+
Thanks in advance

Alteros said:
So I rooted a couple of days after I got the Tab, left the Stock Rooted Rom and then loaded the Honey Villian Kernel for O/C purposes. Since O/C is the only thing I do with Root, I am thinking of going back to Unrooted.
My question is, in Iconia Root, if I hit the Unroot with the Custom Kernel still installed what happens? or since I do not have a copy of the original Kernel, how can I reinstall it before Unrooting?
Build is Acer_A500_4.010.13_com_gen2
Current Kernel is 2.6.36.4 Honeyvillain- 1.0+
Thanks in advance
Click to expand...
Click to collapse
Did you not backup using CWM before flashing your custom kernel?
If you made that mistake, all you need to do is get the stock kernel from the build you're currently on, create a CWM flashable file and flash your stock kernel back.

I did make a backup, then screwed up and wiped the External Card it was stored on. I know, such a newbish mistake. Since then, I have other Backups, just not one with the Original Kernel.
thanks a bunch.. will see if I can search out the kernel I need.

Just grab one of the stock 3.2.1 roms in the development section and install it through cwm. That will replace the kernel, then run acer recovery installer from the market to return to stock recovery. After that you can try running iconiaroot to remove superuser or you can just uninstall it from settings/applications. Now you should be good to go.
Here is a link to a non rooted latest version. It installs through cwm. http://forum.xda-developers.com/showthread.php?t=1429199
The problem is, cwm will still be on your tablet so you will have to flash the stock recovery. I don't know where you can get a flashable version of the stock recovery without using Acer recovery installer which of course requires you to be rooted to use. Although the advantage to keeping cwm will be you can still flash a custom rom in the future the disadvantage would be you won't be able to take OTAs because they will fail when the don't find the stock recovery.

So even if I successfully Unroot, I will not be able to take OTA's?
I have the kernel and was just going to flash it back, and Unroot. If I cant take the OTA's then it's not worth the effort.
Thanks for the information.. My tablet is fine the way it is, just figured if I wasn't really using root, I would go back to stock. Not really interested in flashing a Rom as I don't want to reload all the apps and set it back up.
Thanks again, as usual you guys are quick and helpful.

Alteros said:
........ Not really interested in flashing a Rom as I don't want to reload all the apps and set it back up.
Click to expand...
Click to collapse
@Alteros - What I am about to say is NOT recommended by 90% of all posters so I expect there to be replies urging you not to do this - HOWEVER - if you install a custom Rom then just wipe the following (1)Cache (2)Dalvic Cache (3)Battery Stats DON'T wipe DATA. When you format just format the following (1)System (2)Cache (3)Flexrom DON'T format DATA.
By doing this you should get back all your Apps. There is a possibility, as other posters will tell you, that you will screw up the new Rom and then have to jump through hoops to get back to Stock. But if you want to take the chance and it works then you will have your new Rom and retain your Apps.

kjy2010 said:
Did you not backup using CWM before flashing your custom kernel?
If you made that mistake, all you need to do is get the stock kernel from the build you're currently on, create a CWM flashable file and flash your stock kernel back.
Click to expand...
Click to collapse
couldnt he just flash a rooted stock rom( a couple pages back in the dev section) then proceed with the unroot
---------- Post added at 11:59 PM ---------- Previous post was at 11:56 PM ----------
metpolds said:
@Alteros - What I am about to say is NOT recommended by 90% of all posters so I expect there to be replies urging you not to do this - HOWEVER - if you install a custom Rom then just wipe the following (1)Cache (2)Dalvic Cache (3)Battery Stats DON'T wipe DATA. When you format just format the following (1)System (2)Cache (3)Flexrom DON'T format DATA.
By doing this you should get back all your Apps. There is a possibility, as other posters will tell you, that you will screw up the new Rom and then have to jump through hoops to get back to Stock. But if you want to take the chance and it works then you will have your new Rom and retain your Apps.
Click to expand...
Click to collapse
yeah that might work, but he may just to get titianium backup and backup all his apps, if he is going to revert to stock, by flashing a stock rom over a custom rom things might act funny and since he is not rooted only thing he can do is wipe the device and start new
his less headache way of doing things is to leave root and recovery, and use a stock rom. Theres alot of tegra devices out there and who knows how long this community will be kicking out updates long after acer closes support for A500

Thanks to everyone that helped. I ended up loading Thor's 14.2 over the weekend, was not nearly as painful as I thought it would be. So I may try more in the future.
You guys are always quick to respond and helpful.
What I think I learned is that, once you root, you can never go completely stock again. Since there is not a way to get rid of CWM, at least not easily.

[Q] Custom kernel and reverting to stock kernel

Hi,
Long time reader, first time poster. I just unlocked the bootloader and flashed the latest franco nightly with fastboot and have two questions:
1. From what I've understood, in order to perform OTA updates, I have to be on the stock kernel. Do I just flash the stock boot.img extracted from the factory image? I think I may have read something about additional changes being done to the system partition after flashing a custom kernel, but I can't seem to find the thread.
2. If I want to flash a different kernel or update the existing one, do I just flash the fastboot image? Does it just overwrite the existing one or do I have to perform any additional steps, like a wipe?
I have not flashed a custom recovery or rooted the device and would like to keep it that way.

Yes. Some kernels do modify system files. If you wanted to get back to stock for an ota you'd flash both the boot.img and the system.img
Sent from my Nexus 4 using xda premium

El Daddy said:
Yes. Some kernels do modify system files. If you wanted to get back to stock for an ota you'd flash both the boot.img and the system.img
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply.
Do I keep my current settings and SMS messages when I flash system.img?
I'm guessing this is only necessary before performing an OTA update. If I'm only updating the kernel I just flash boot?

Eregoth said:
Thanks for the quick reply.
Do I keep my current settings and SMS messages when I flash system.img?
I'm guessing this is only necessary before performing an OTA update. If I'm only updating the kernel I just flash boot?
Click to expand...
Click to collapse
Yep your data will stay intact.
Yep just flash boot. Some say you should clear dalvik cache as well.
Sent from my Nexus 4 using Tapatalk 4 Beta

And what am i doing wrong, when the bootloader is not ending? i have root, unlocked bootloader, fancy kernel, cwmr and louder mod. i reverted the mod. flashed boot, system and recovery back to stock. i also want to perform an ota update.

Flashable Factory Image zips - Android 5.0 LRX21P

This is essentially the Nexus 7 2013 WiFi's factory stock image in flashable zip format, so you can flash the device back to factory stock using CWM or TWRP, without having to rely on fastboot. It is useful for people who broke their USB port, but still have custom recovery. Or messing with roms on the go and wanting to return to stock without having access to a computer.
Included are separate zip files that will flash specific partitions of the device. To have a complete stock form of the device and preventing any issues, make sure you flash all zip files. More advance users can choose to only flash specific partitions to suit their needs.
>>> DOWNLOAD: razor_lrx21p_stock_flashable_zips <<<​
Flash instruction (Important):
0. (optional) Create a full nandroid backup before flashing is recommended.
1. To have a working and stable OS, make sure you flash all the zip files, unless you know what you're doing.
2. To prevent serious incompatibilities, do a factory reset if you are coming from KitKat or from a custom rom. I would only skip doing a factory reset if the device is already running stock Lollipop.
Note: If you do not want to erase your custom recovery, do not flash the "recovery.zip", this will return your custom recovery back to stock.
I have tested flashing these multiple times with my Nexus 7 WiFi 32gb with no issues. Before proceeding with flashing, each zip files will check to make sure if the device is a Nexus 7 2013 WiFi (flo), so it won't allow you to accidentally flash on a wrong device.
If you have any issues after flashing these, even after factory resetting, follow this guide to use fastboot instead to return the device to stock.
MD5 Checksum:
File: razor_lrx21p_boot.zip
MD5: 9c12f5f7a83facf80cf596a6de1187ab
File: razor_lrx21p_bootloader_4.04.zip
MD5: 818864adb28b3559fd9d7107115de57c
File: razor_lrx21p_ddr.zip
MD5: d4ee8ae2ec00a37dc9af589cee87f9e0
File: razor_lrx21p_recovery.zip
MD5: 86d2f2d8b784ee108153b0606220040f
File: razor_lrx21p_system.zip
MD5: a0d5c8ce8fbaadc2c304f1f78e9bd6cc

Thanks a lot.
I am currently using Cleanrom. I have download the stock rooted Lolipop, and wish to flash that. It was said in that thread, that I need the latest bootloader. So from the zip file above, should I only flash the bootloader and then flash L? Or would it not make a difference if I flashed all the zips (besides the recovery)?
No, I do not want to get rid of my custom recovery. I am using the latest version of TWRP

Flashed with TWRP, works well. Thanks a lot!
eksasol said:
This is essentially the Nexus 7 2013 WiFi's factory stock image in flashable zip format, so you can flash the device back to factory stock using CWM or TWRP, without having to rely on fastboot. It is useful for people who broke their USB port, but still have custom recovery. Or messing with roms on the go and wanting to return to stock without having access to a computer.
Included are separate zip files that will flash specific partitions of the device. To have a complete stock form of the device and preventing any issues, make sure you flash all zip files. More advance users can choose to only flash specific partitions to suit their needs.
>>> DOWNLOAD: razor_lrx21p_stock_flashable_zips <<<​
Flash instruction (Important):
0. (optional) Create a full nandroid backup before flashing is recommended.
1. To have a working and stable OS, make sure you flash all the zip files, unless you know what you're doing.
2. To prevent serious incompatibilities, do a factory reset if you are coming from KitKat or from a custom rom. I would only skip doing a factory reset if the device is already running stock Lollipop.
Note: If you do not want to erase your custom recovery, do not flash the "recovery.zip", this will return your custom recovery back to stock.
I have tested flashing these multiple times with my Nexus 7 WiFi 32gb with no issues. Before proceeding with flashing, each zip files will check to make sure if the device is a Nexus 7 2013 WiFi (flo), so it won't allow you to accidentally flash on a wrong device.
If you have any issues after flashing these, even after factory resetting, follow this guide to use fastboot instead to return the device to stock.
MD5 Checksum:
File: razor_lrx21p_boot.zip
MD5: 9c12f5f7a83facf80cf596a6de1187ab
File: razor_lrx21p_bootloader_4.04.zip
MD5: 818864adb28b3559fd9d7107115de57c
File: razor_lrx21p_ddr.zip
MD5: d4ee8ae2ec00a37dc9af589cee87f9e0
File: razor_lrx21p_recovery.zip
MD5: 86d2f2d8b784ee108153b0606220040f
File: razor_lrx21p_system.zip
MD5: a0d5c8ce8fbaadc2c304f1f78e9bd6cc
Click to expand...
Click to collapse

Flawless as usual, thanks Eksasol

Great, will do this tomorrow! Thanks
Envoyé de ma Nexus 7.2 depuis tapatalk

particular order?
Thank you very much eksasol!
Is there a particular order in which these files should be flashed?
Cheers,
Sandor

schermvlieger said:
Thank you very much eksasol!
Is there a particular order in which these files should be flashed?
Cheers,
Sandor
Click to expand...
Click to collapse
No they should all work. The phone will boot correctly as long as you have all the proper kernel (boot), system (OS) and bootloader installed.

timrock said:
Thanks a lot.
I am currently using Cleanrom. I have download the stock rooted Lolipop, and wish to flash that. It was said in that thread, that I need the latest bootloader. So from the zip file above, should I only flash the bootloader and then flash L? Or would it not make a difference if I flashed all the zips (besides the recovery)?
No, I do not want to get rid of my custom recovery. I am using the latest version of TWRP
Click to expand...
Click to collapse
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.

Marvellous!

eksasol said:
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Click to expand...
Click to collapse
Would a factory reset delete the files I have on my device? If so, the ROM is in a folder on my device.
Sent from my Nexus 7 using Tapatalk

Which one of these zips controls user data? I want to try and dirty flash, as I dont want to lose any data if I dont have to. Any suggestions?

I have not done a factory reset yet; and add away tells me the device is not rooted.
Did the update remove root, or is this one of those issues related to not doing a factory reset?
All else seems to be working at the moment.

eksasol said:
You should flash both the bootloader and DDR zip. Then flash the the rom, it should work. Also if you are coming from KitKat, you will need to factory reset or you will get lots of errors.
Click to expand...
Click to collapse
So the bootloader and DDR zips can be flashed through TWRP to update the bootloader only, and then a separate rooted ROM (ie scrosler's) can be flashed through TWRP with the help of the updated bootloader?
I did try to flash the bootloader only, but it failed. The need for the DDR would explain why.
Cheers.

Thanks this is what ive been looking for.
Bought my nexus 7 2013 3weeks ago it came with 4.4.2 and i towelrooted it n flashed twrp now on a custom rom but wish i didnt coz i wanted the updates 5.0 but i dont have a pc so this is what i needed.
So if i flash all zips does that mean il be stock 5.0 and ready for future updates?
Aslo my bootloader is already 4.04 so should i stil flash the one above?
Is it possable to flash jus system+boot zips as a second rom (multirom)?

I am not going to install 5.0 yet because some of the apps I use are not yet compatible. If I just flashed the boot loader but stayed with my current ROM , cleanrom, would that be a problem?
Sent from my Nexus 7 using Tapatalk

Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?

James_Feltham said:
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
Click to expand...
Click to collapse
Hi James,
You'll need to re-root your device after you flashed these images.
CF-Autoroot will help you here; click.
You'll need to reinstall your custom bootloader as well if the stock bootloader does not meet your requirements.

timrock said:
Would a factory reset delete the files I have on my device? If so, the ROM is in a folder on my device.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It depends, for normal Android devices, if you factory reset using stock recovery it will wipe everything in the device. For TWRP and CWM, if you factory reset it will leave your internal storage alone.
MWFD said:
Which one of these zips controls user data? I want to try and dirty flash, as I dont want to lose any data if I dont have to. Any suggestions?
Click to expand...
Click to collapse
None of them control userdata, I excluded that partition image. If you want to dirty flash, just don't do a factory reset or wipe your /data folder.
toonarmy4life said:
Thanks this is what ive been looking for.
Bought my nexus 7 2013 3weeks ago it came with 4.4.2 and i towelrooted it n flashed twrp now on a custom rom but wish i didnt coz i wanted the updates 5.0 but i dont have a pc so this is what i needed.
So if i flash all zips does that mean il be stock 5.0 and ready for future updates?
Aslo my bootloader is already 4.04 so should i stil flash the one above?
Is it possable to flash jus system+boot zips as a second rom (multirom)?
Click to expand...
Click to collapse
Do not flash these zip as a secondary rom for multirom, this is meant to flash for the entire device only. This is factory images, not roms. You could download some type of stock based roms and use it with multirom instead. If you have the latest bootloader you don't need to flash it again, but it won't hurt if you do. Yes, flashing all the zips and factory resetting will return the device to stock.
timrock said:
I am not going to install 5.0 yet because some of the apps I use are not yet compatible. If I just flashed the boot loader but stayed with my current ROM , cleanrom, would that be a problem?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That should not be any problem.
James_Feltham said:
Thanks man this was really helpful for me <3 Can't seem to get root access though. Any idea why?
Click to expand...
Click to collapse
Because this is Android 5, it have extra security to prevent rooting like in the past. I believe to get root you need try Chainfire's CF-AutoRoot method, or use a custom kernel and flash SuperSu.
schermvlieger said:
I have not done a factory reset yet; and add away tells me the device is not rooted.
Did the update remove root, or is this one of those issues related to not doing a factory reset?
All else seems to be working at the moment.
Click to expand...
Click to collapse
This isn't an update. It is a factory image that return the device to stock form. You will lose root and every changes to the system partition in the process.

Can this file be flashed on any device??

#divy said:
Can this file be flashed on any device??
Click to expand...
Click to collapse
No only on Nexus 7 2013 WiFi 32gb

Rooting Query - Is Elemental X really needed?

Hi All,
I just recovered from a hard brick on my G4 plus due to various complications from flashing the Elemental X ROM as suggested before flashing the root file.
Though the root was successful on the stock Nougat OS (NPJ25..93-14), the main issue which I immediately noticed after rooting was that there was no notification sound. I fiddled through all the settings to get this working, but didn't get through. Not sure if anybody has faced this issue.
So, my queries are as below:
----- Why is a custom kernel needed to root? Just flashing a root zip file wouldn't be enough?
----- What's the issue with the sound getting disabled after flashing the Elemental X kernel? Is there a fix to re-enable the notification sounds?
----- Is there any other custom kernel which I could flash when rooting on the Stock N OS if indeed a custom kernel is required to root? (this shouldn't screw up the notification sound)
Regards,
Shonilchi

Shonilchi said:
Why is a custom kernel needed to root? Just flashing a root zip file wouldn't be enough?
Click to expand...
Click to collapse
The stock kernel from Motorola can only have temporary root access. Check the thread by Shreps if you're interested in that. There's no other way, at the moment to get permanent root access. Why? That's some way Motorola has worked out the kernel.
What's the issue with the sound getting disabled after flashing the Elemental X kernel? Is there a fix to re-enable the notification sounds?
Click to expand...
Click to collapse
Hadn't happened for me when I rooted my device. Specific to you, for some reason. Try flashing again. Backup your existing kernel (Google how to) and restore the backup if anything goes wrong.
Is there any other custom kernel which I could flash when rooting on the Stock N OS if indeed a custom kernel is required to root? (this shouldn't screw up the notification sound)
Click to expand...
Click to collapse
You can, of course try Dreamstar's Vegito or rahulsnair's Quark kernel's stock versions and then flash a superuser ZIP file (the same phhSU or Chainfire's SuperSU.
You should not have had a hard brick. Perhaps you had a soft brick. A hard brick would require a blank flash using special software to fix. What did you mean when you said your phone got hard bricked?

Great thanks for the answers. Yes, it was probably a soft brick which happened. I was able to downgrade to MM and then do a N upgrade.
BTW, I see many supersu.zip files floating around to be flashed. Do you recommend a most suitable one to flash for the G4+. I know that I need to install the pHH supersu app after I boot up.
And for the stock kernel revert I found this statement: "Do a nandroid backup and do advanced restore instead of complete restore. boot.img is the kernel." - can you please confirm if this is a good way to revert back to the stock kernel?

deleted.

Shonilchi said:
BTW, I see many supersu.zip files floating around to be flashed. Do you recommend a most suitable one to flash for the G4+. I know that I need to install the pHH supersu app after I boot up.
Click to expand...
Click to collapse
Install the phhSU zip as mentioned in the link in the post above, or, install the latest SuperSU Beta from the SuperSU XDA thread.
And for the stock kernel revert I found this statement: "Do a nandroid backup and do advanced restore instead of complete restore. boot.img is the kernel." - can you please confirm if this is a good way to revert back to the stock kernel?
Click to expand...
Click to collapse
All you need to do is backup boot.IMG from TWRP and restore it upon a botched flash.

Shonilchi said:
Great thanks for the answers. Yes, it was probably a soft brick which happened. I was able to downgrade to MM and then do a N upgrade.
BTW, I see many supersu.zip files floating around to be flashed. Do you recommend a most suitable one to flash for the G4+. I know that I need to install the pHH supersu app after I boot up.
And for the stock kernel revert I found this statement: "Do a nandroid backup and do advanced restore instead of complete restore. boot.img is the kernel." - can you please confirm if this is a good way to revert back to the stock kernel?
Click to expand...
Click to collapse
Was walking around here and couldn't help the itchy need to leave my own straight answers to your questions, mostly as an exercise, since G4/Plus is no longer that news nor the thing of excitement it still was (arguably) back in March 2017.
Whatever, as for superuser means, @topjohnwu "Magisk" has gained a lot of popularity over former Chainfire's "SuperSu" since he's no longer supporting it and development seems pretty much at iddle nowadays. Say I'm a purist (which I'm not), that's why I'm still relying on latest, all @Chainfire built SuperSu (v2.82 SR5) probably for the last time though...
On the other hand, ABSOLUTELY YES, it's a good way and you can restore just boot.img right from your nandroid backup to revert back to stock kernel. Actually, we all know it's the best practice to always do a nandroid backup right before messing around with our devices and TWRP comes with the benefit to choose which partitions you can either backup or restore...
As for @flar2 ElementalX, it wasn't really a must because I refused upgrade to "N" due to the lack of Xposed support (both came a bit late) but I flashed it anyways in order to "fix" the so called "burn screen" issue primarily... and just because it's cool. No unwanted side effects by the way and my personal experience with Moto G4 Plus aside from the "burn screen" issue (which turned out no big deal for me) is of pure joy until early days of 2018 and counting. There you (all) have it.
Sent from my Moto G4 Plus using XDA Labs

u need to reboot the device once or wait for sometime..the tones comes back automatically..its not a kernel issue. Since, no one else is facing it...
Custom kernels are better than stock as they give u an option to tweak for performance or battery.. if you don't need it keep it stock.. if u want it, the method u know is correct. Always make backups, incase u mess up.
Good luck!

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