Database Info

[ROOT] PROPER Remake of Full Rooted Stock Image (aka Root66) + Easy CWM Install

SOLVED - How to flash the Proper (Fixed) Stock Rooted Image
Description: This is 100% stock with just Superuser/su added and overwrites every partition to stock but keeps your personal data, apps, settings the same (just like the stock factory image).
Samsung Official USB Drivers - Link
ODIN v3.07 - Link
Proper Rooted Stock Image - Download or (Torrent Link) - MD5 = be4350a56e739eaf7a4184352d653a7b
1. Install USB drivers
2. Download ODIN v3.07
3. Backup your data
4. OPTIONAL: Do a factory reset (highly recommended if you have issues with your current ROM)
***WARNING: Step #4 will erase internal storage but not microSD card***
5. Download the above Proper Rooted Stock Image file and extract the tar file from inside it
6. Boot phone into ODIN mode (See here for how-to)
7. Flash the extracted tar file using ODIN v3.07
You should now have a like new condition stock image and rooted with all issues resolved.
Credit goes completely to mrRobinson for creating this image for us. Thank you sir. (Original Post) + (Details How It Was Made)
To Install Official CWM Recovery
1. After following above process, download "Rom Manager" from the Play Store
2. Open Rom Manager
3. Select "Flash ClockworkMod Recovery"
4. Select "Samsung Galaxy S3 (Verizon)" down at the bottom and let it flash
5. Once completed you can reboot to CWM by selecting "Reboot into Recovery" from Rom Manager
ORIGINAL REQUEST
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
BungeBash said:
Just formatted back to stock until issues can be resolved. The stock image (which I'm told this root is + su) lost all Sprint instances and any strange extra options. Also the Keyboards are back to functioning. Not to be a conspiracy theorist, but I feel that the root image has more going on with it than what we are told.
Click to expand...
Click to collapse
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse

open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
If you don't like it, dont flash it.

tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Hardly helpful for those who already flashed it... I just want it fixed, or a work around. If it's something as simple as uninstalling a few things, or replacing some databases, I'm fine with that. I just don't want to redo everything, and re-restore everything with Titanium Backup.

tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.

open1your1eyes0 said:
Not to be rude but we're not. That's why I'm making this request to remake with proper image. Because we are skeptical of the original one that was made. I PMed the OP of that thread and he claims to have used that image but in user's experience something is definitely different from stock, hence we're requesting a remake to test this.
Click to expand...
Click to collapse
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.

I did have some odd issues with SwiftKey crashing after flashing the image. Not sure if that has to do with it or not.
tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
Useless post.
What would be useful is someone with the requisite knowledge being able to remake this exploit with the Verizon source in order to have maximum compatibility.

open1your1eyes0 said:
After various testing, it seems many users are experiencing various issues with the rooted System.img provided by the OP in this thread. Many report findings of "Sprint related elements" as well as various keyboard issues and things not working as they should. I wish I had the knowledge myself but on behalf of the community, I'd like to request for someone with knowledge of this guide to remake the same rooted system.img as in the original but this time confirmed with using the original stock Verizon SCH-I535 image downloadable here.
I'm sure many of us here would highly appreciate this effort and we can also carry out further testing as many users reported that soon as they flash back to that stock image, their issues have disappeared and everything starts working properly.
I will quote another user in reference to this:
Here's to hoping one of you knowledgeable developers are able to assist us with this request.
Click to expand...
Click to collapse
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI

alquimista said:
Are you talking about the system.img from invisibleks first image?
Link: http://forum.xda-developers.com/showpost.php?p=28402010&postcount=1
Or the stripped and rooted one?
Link: http://forum.xda-developers.com/showpost.php?p=28459565&postcount=1
I think the first one invisiblek made is pretty much what you are asking for. Remember, there's no SCH-I535 source code out there for people to build a system image from. These images are hacked system images from the stock image (found here: http://samsung-updates.com/device/?id=SCH-I535 ). One can't really "remake" the system image until we can fully bypass the encrypted and locked bootloader.
If you want to roll your own system image with the su binary and SuperUser you can follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=27801304&postcount=1
They seem pretty straight forward.
However, I'm pretty sure that's what invisiblek did for his/her first rooted image (the one that isn't stripped).
Hope that helps. I can't do much of anything till my SGS3 arrives tomorrow.
ALQI
Click to expand...
Click to collapse
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.

I could do it, but it'd require more time than whats it worth. Sorry.

tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
You are a WORM!!!!!!!
Sent from my Galaxy Nexus using xda app-developers app

tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.

tonu42 said:
If you don't like it, dont flash it.
Click to expand...
Click to collapse
tonu42 said:
I could do it, but it'd require more time than whats it worth. Sorry.
Click to expand...
Click to collapse
Two completely pointless comments.
open1your1eyes0 said:
No worries. Very understandable as that guide is quite time consuming and not for everyone. Thanks for your support either way.
Click to expand...
Click to collapse
You sir are a better man than me for being so humble in response to these replies.
I'm assuming invisiblek DID in fact use the VZW image if the phone still had all the VZW nonsense in it (VZ Navigator, for example) as that would not be found in the Sprint image. Equally, if "all" he did was follow the steps in the link, then someone else doing the same is likely to produce the same result.
tonu42 said:
If you'd like, you can flash the stripped version, and I have a second zip that will restore all the stripped apps.
Click to expand...
Click to collapse
If you have these, have you posted them anywhere? That might have been a useful thing to do.

Here is all the removed apk's in a CWR zip.
http://www.mediafire.com/?6jv8wn9l5n0li9y

I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.

BungeBash said:
I actually saw that guide you posted about creating our own. I can try and whip something up tonight if I get some time. If not, tomorrow is my "Friday" at work, so I'll have time tomorrow evening for sure.
Click to expand...
Click to collapse
Thank you much sir. You assistance would be greatly appreciated.
Unfortunately I do not have a linux box so the guide does not work for me.

It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.

Goose306 said:
It's already been diff'd. There is no difference between the stock image and the rooted one here except for su and binaries:
http://rootzwiki.com/topic/29256-ro...erizon-galaxy-s-iii/page__st__110#entry793038
I'm guessing VZW has done more to the stock image on the phone than the stock one that is available for download, which is causing these differences.
Click to expand...
Click to collapse
Considering I loaded the first root mod, then reverted to the image that it was created from and have 2 different setups I'd say two different files were used.

open1your1eyes0 said:
The one in bold is what this request is about actually. Basically to remake that. Because the non-stripped rooted system.img that invisiblek is the one causing most issues for people and people have noted things in there that are not in the factory image. I tried to follow that guide myself but I must be missing something because most of those commands do not work for me. Mind you this is on a Windows PC.
Click to expand...
Click to collapse
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI

alquimista said:
If its already been diff'd with the original, maybe the sammy-updates file ain't so good.
Hmm, I wonder if we dump the system.img from an untouched stock phone (like the one I get tomorrow), and inject that img with su, would that work out any better? I'll look into this tomorrow.
I'll also take a look at re-rolling the system.img from the sammy-updates files in the meantime.
I'll report back when and if I have a viable image.
~ALQI
Click to expand...
Click to collapse
According to users, flashing that sammy-update firmware got rid of all the issues and the Sprint related stuff. Just, FYI.

If anyone is up for the remake, you might want to try making it out of this one. Not sure if it's any different but it's from another well known Samsung firmware site.
Link to stock factory firmware

7.1.2 Upgrade Help

Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.

Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available

bush911 said:
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
Click to expand...
Click to collapse
I have tried to stay away from flash fire because I know a couple buddies who soft-bricked by using it.

xxbilxx said:
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Click to expand...
Click to collapse
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2

TonikJDK said:
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Click to expand...
Click to collapse
I don't have to sideload the March security patch first?

xxbilxx said:
I don't have to sideload the March security patch first?
Click to expand...
Click to collapse
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).

TonikJDK said:
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
Click to expand...
Click to collapse
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.

xxbilxx said:
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
Click to expand...
Click to collapse
Correct, you want N2G47E.

TonikJDK said:
Correct, you want N2G47E.
Click to expand...
Click to collapse
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!

xxbilxx said:
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
Click to expand...
Click to collapse
No problem at all. Second to the last post in the same thread I linked you to before. It all still works fine on 7.1.2. Did all of this myself yesterday afternoon.

Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways

Download the OTA, Flash it from TWRP, reflash twrp and reboot

mikeprius said:
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Click to expand...
Click to collapse
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.

robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
yeah saved it. There was only one section that had the w- and it was right before the update image. I can try it again at some point later on but that's what I did. I tried to sideload adb the OTA first which does not wipe data but kept getting an error saying device not found and emulator.

robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
Your instructions worked perfectly for me. I'm nor sure what setup the other guy had, but I did make sure I removed the -w like 20 times.

Juli112 said:
Download the OTA, Flash it from TWRP, reflash twrp and reboot
Click to expand...
Click to collapse
are you on the latest twrp rc2 or rc1?

Has anyone received the update ota on a stock google pixel XL for verizon. Mine keeps telling me I am current?

Help! Oneplus Newbie!

While i am no beginner when it comes to modding phones, having done so with Samsungs Sonys and my last HTC 10. But this is my first Oneplus and my first time dipping toes in the world of A/B partitions as well. My device is a 1910 GM21AA. While i have gone through the guides regarding bootloader unlocks and magisk rooting, I have failed to grasp some more basic aspects. For one thing, i seem to have the Chinese variant but mine isnt Hydrogen OS, i am currently sitting on 9.5.3 OOS. I was wondering how i could perhaps shift to the Global firmware. Am i to take the latest 9.5.11 OTA from https://forum.xda-developers.com/on...7-pro-global-repo-oxygen-os-t3930585#poststop and simply put it in the download folder and do a local update from the system update on the phone? Thanks in advance

Use the oygen os updater from the play store download full rom which is around 2gb and do local upgrade.
FYI GM21AA is Indian Version
Sent from my GM1911 using Tapatalk

zmafreak said:
Use the oygen os updater from the play store download full rom which is around 2gb and do local upgrade.
FYI GM21AA is Indian Version
Sent from my GM1911 using Tapatalk
Click to expand...
Click to collapse
the packages shown in the app seem to be the same zips in the thread i linked...so all i do is take the GM21AA from the thread and just do a local update? I read that 1910 is the Chinese variant for my device but it has this GM21AA build which just made things so confusing. Thank you.

I would now like to know of things i can do to bring my OP7Pro to life in case something ever goes wrong with Local storage updates or just Fcked up in general

linx1287 said:
the packages shown in the app seem to be the same zips in the thread i linked...so all i do is take the GM21AA from the thread and just do a local update? I read that 1910 is the Chinese variant for my device but it has this GM21AA build which just made things so confusing. Thank you.
Click to expand...
Click to collapse
That should do.. it should give you an error if the update is incompatible. Incase you mess up you can always fastboot and update using this thread https://www.google.co.in/amp/s/foru...ock-fastboot-roms-oneplus-7-pro-t3931424/amp/
Sent from my OnePlus 7 Pro using Tapatalk

zmafreak said:
That should do.. it should give you an error if the update is incompatible. Incase you mess up you can always fastboot and update using this thread https://www.google.co.in/amp/s/foru...ock-fastboot-roms-oneplus-7-pro-t3931424/amp/
Sent from my OnePlus 7 Pro using Tapatalk
Click to expand...
Click to collapse
After flashing the rom, i cant for some reason enter engineering mode. I could with my original firmware. Has this happened to you or anyone?

I never tried it tbh
Sent from my OnePlus 7 Pro using Tapatalk

linx1287 said:
After flashing the rom, i cant for some reason enter engineering mode. I could with my original firmware. Has this happened to you or anyone?
Click to expand...
Click to collapse
I could be wrong, but I think that's the norm with everyone since updating. Thinkni read it in one of the XDA forums around here somewhere.

How do i roll back to full stock if i am on custom rom? This is unfortunately also my first time dealing with A/B partitions.
Aside from these, i have been going around the forums and had a few more questions that i hope someone could help me with....
1. Whenever i come across a rom not based on OOS, i keep coming across never wiping system or vendor, why is that?
2. I come across flashing OOS a lot, how do i flash OOS when i am in a custom rom not based on OOS?
 @hallo dare @virtyx

zmafreak said:
Use the oygen os updater from the play store download full rom which is around 2gb and do local upgrade.
FYI GM21AA is Indian Version
Sent from my GM1911 using Tapatalk
Click to expand...
Click to collapse
GM21AA IS global too
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
hallo dare said:
I could be wrong, but I think that's the norm with everyone since updating. Thinkni read it in one of the XDA forums around here somewhere.
Click to expand...
Click to collapse
look in the volte thread
there is an apk to installnand enables it again with limited functionality
or use MSM tool to go back to 953 and tibu backup and restore on 9511
oneplus removed it for some reason...
maybe because they found out we're forcing VOLTE?

linx1287 said:
How do i roll back to full stock if i am on custom rom? This is unfortunately also my first time dealing with A/B partitions.
Aside from these, i have been going around the forums and had a few more questions that i hope someone could help me with....
1. Whenever i come across a rom not based on OOS, i keep coming across never wiping system or vendor, why is that?
2. I come across flashing OOS a lot, how do i flash OOS when i am in a custom rom not based on OOS?
@hallo dare @virtyx
Click to expand...
Click to collapse
full zip upgrade
or MSM tool.
you will be wiped.

virtyx said:
full zip upgrade
or MSM tool.
you will be wiped.
Click to expand...
Click to collapse
Do i use MSM tool or fastboot method whenever i need to get back to complete stock without any root or twrp? If so then i think MSM tool or fastboot roms would be a great way to go. 1 question, does using msm or fastboot return the phone to stock while keeping the bootloader unlocked? Also, is it ok to downgrade to a lower version of OOS with MSM or fastboot roms? i think 9.5.11 for me introduced some random background battery drain and this weird mobile data bug where switching to it doesnt enable the connection until much much later

I personally use fastboot. All you need to do is plug the phone in>Boot to fastboot (hold vol up and down and power all at once)>On the computer launch flashall.bat (dont run it as administrator, just launch it).

PerthBoi92 said:
I personally use fastboot. All you need to do is plug the phone in>Boot to fastboot (hold vol up and down and power all at once)>On the computer launch flashall.bat (dont run it as administrator, just launch it).
Click to expand...
Click to collapse
Do you use it to downgrade or whenever you need to go back to full stock after modding? does it keep the bootloader unlocked or does it relock it? Thanks. Sorry for the noob questions. This is my first Oneplus. I have kept my device stock until i get a good idea of how to deal with things going south.

I need a little guidance regarding this thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Are these rom packages for MSMtool or fastboot packages?
EDIT:
Never mind...msmtool stuff just went through the files

11.0.6.6.IN21AA magisk

I was going to try and extract the file I needed out of the 11.0.6.6.IN21AA but I can't seem to locate the global version of it. I've only seen the EUR and INDIAN so far. Does anyone know where I can find it or know if something else will work for root?

Not available yet. Keep watch here for the release.

BeardKing said:
Not available yet. Keep watch here for the release.
Click to expand...
Click to collapse
Cool thanks for the reply man. But now I'm really confused because of what I stumbled upon last night. Could you have a look at the link and see if we're on the same page? Thanks for your time if so
Post in thread '[GUIDE] Magisk for OxygenOS 11' https://forum.xda-developers.com/t/guide-magisk-for-oxygenos-11.4160833/post-85093481

Yeah, I guess they're getting the boot image from the OTA update. Me personally, I wait for OnePlus to post the full update, then I use Payload Dumper to extract the boot.img and patch it myself in Magisk, then flash with fastboot.

Download KB2005_11.C16 ?

Hi,
I currently have the version KB2005_11_C.11 on my 8T.
Via OTA I am offered the new version KB2005_11.C16_1160_202204222257. But this breaks again and again at 22% with Installationproblems.
The OxygenUpdater also brings me nothing because it constantly offers me the already existing version KB2005_11_C.11.
Where can I download the latest (full) version KB2005_11.C16?
Or other.....kann the evtl. someone times upload ?
Thanks

Is your phone rooted?

BillGoss said:
Is your phone rooted?
Click to expand...
Click to collapse
jop

Wasabi72 said:
jop
Click to expand...
Click to collapse
That's why your update won't work. C16 is an incremental update and expects the stock boot image to be in place.
Next question. Do you have a directory named something like /data/magisk_backup_c64948c228b8c5e1aee9c14fbed837abb5aa50de
The numbers will be different as mine are for C.16

BillGoss said:
That's why your update won't work. C16 is an incremental update and expects the stock boot image to be in place.
Next question. Do you have a directory named something like /data/magisk_backup_c64948c228b8c5e1aee9c14fbed837abb5aa50de
The numbers will be different as mine are for C.16
Click to expand...
Click to collapse
Yes, i have 3 of these Directorys

Wasabi72 said:
Yes, i have 3 of these Directorys
Click to expand...
Click to collapse
Good. Then you can restore the stock boot image using Magisk>Uninstall Magisk>Restore images before you do the update. Then the update should work.
And to keep root, use this process by @rage302 https://forum.xda-developers.com/t/guide-wip-root-and-keeping-root-options.4387977/post-86830285

You can get it here but it is incremental update https://android.googleapis.com/packages/ota-api/package/2332cb8c0db7e7db378805a0b811772b10a00559.zip

BillGoss said:
Good. Then you can restore the stock boot image using Magisk>Uninstall Magisk>Restore images before you do the update. Then the update should work.
And to keep root, use this process by @rage302 https://forum.xda-developers.com/t/guide-wip-root-and-keeping-root-options.4387977/post-86830285
Click to expand...
Click to collapse
Oha, that doesn't sound easy.
Especially since I can't find anything in Magisk to unroot or reset.
I can of course reset the phone completely, but I don't really want to do that.

Wasabi72 said:
Oha, that doesn't sound easy.
Especially since I can't find anything in Magisk to unroot or reset.
I can of course reset the phone completely, but I don't really want to do that.
Click to expand...
Click to collapse

ITMASTER said:
You can get it here but it is incremental update https://android.googleapis.com/packages/ota-api/package/2332cb8c0db7e7db378805a0b811772b10a00559.zip
Click to expand...
Click to collapse
Yes, there I was a bit blind....then found it and carried it out....and now I have arrived here: https://forum.xda-developers.com/t/guide-wip-root-and-keeping-root-options.4387977/post-86837951
Edit: Sorry ITMASTER i mean BillGoss