Database Info

New to Linux, wanting to root and or flash, Xperia Z5 Android 6.0.1

Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.

spynathan said:
Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed

Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed
Click to expand...
Click to collapse
Awesome thanks! I'll try it first thing tomorrow after work.

Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.

spynathan said:
Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.
Click to expand...
Click to collapse
atleast on windows 10 i found that i had to disable driver signature verifacation and sometimes i had to run command prompt in admin

How to Update to 7.1.1 on a Rooted, Unlocked Bootloader, Google Play Pixel?

I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.

spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.

quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.

lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.

quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.

Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?

spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?

bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.

spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.

@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156

Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.

Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.

Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.

bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.

bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.

kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.

bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.

bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).

kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app

kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.

Android Oreo root Question

I only picked up my NP last week and after a couple of days it updated to 8.0 / Oreo, So all my research and prep for a root & flash has been thrown up in the air.
Are there any major changes anyone knows of that might make rooting, custom bootloader & rom flash problematic?
i did really like the old leanback launcher UI and the update is way too fussy for my liking, and i'm not even going to comment on the lack of catch-up content for UK users. If ever a device needed hacking, this is the one.
cheers in advance

Honestly im pretty sure you could just flash magisk through twrp with the 8.0 zip. Im pretty sure it would work

thanks for the reply, i'm dithering as i'd hate to lose the chromecast feature and have yet to find a rom which has it mastered and working.

gascomm said:
thanks for the reply, i'm dithering as i'd hate to lose the chromecast feature and have yet to find a rom which has it mastered and working.
Click to expand...
Click to collapse
Magisk root and TWRP work just fine. You won't lose any functionality, but that's with the stock images.

Is there a way to get back without a computer? I lost root after the forced update. Think I'm still unlocked boot loader got the icon at boot up but have no twrp recovery anymore or root sadly I miss 7.1.2 after the update it crapped the nexus player
Sent from my Nexus 7 using Tapatalk

I don't believe so. You'll need a computer to run adb to downgrade.
An easier method is to use the Nexus Root Toolkit which will input all the commands for you. You just point and click.

Current method of choice for achieving root

Long time rooter who has more or less given up in recent years.
Rooted:
HTC hero
HTC desire
Samsung Galaxy s1
Nexus 4
Nexus 5
Nexus 5x
Not rooted:
Pixel 2
Pixel 4xl
Just got a pixel 4 but would be tempted to root the pixel 2 while it's still got some life in it.
Got a few quick questions as to what has changed recently. Would be using magisk to achieve root after installing twrp. (Unless this is old hat and something else is the method of choice). Probably will have to unlock bootloader can't remember if I ever did it on the pixel 2
What's the procedure for monthly updates can they be done via ota or do I need to bring adb into it?
Best guides floating about at the moment? Any other pertinent advice? Muchthx

first of all, nobody cares how many devices you have rooted in the past, especially if you come needing help anyways which i find amusing.
secondly, to root this, boot twrp and flash magisk. if you are on android 10 you will need to patch the boot image from the factory image of the version you are on with magisk and flash it to your current boot slot.
thirdly, if you are on android 10 and rooted, you will get otas. anything lower and you will need to adb sideload otas.

IMO the rooting party is pretty much over. I also returned to xda after many flashes years ago. For the Nexus, the great Beanstown dev provided monthly flashes for your custom recovery, but it looks so much more complicated today, to the point it's not worth the effort anymore. I'm sticking with stock till the '2 dies. The risk of unlocking the bootloader and getting root is simply not worth the headache as evident in the Q&A posts. So for now, for my much wanted rootness, I resort to debian linux on the desktop, a command line, and the luxury of typing sudo!!

sudoxd said:
first of all, nobody cares how many devices you have rooted in the past, especially if you come needing help anyways which i find amusing.
secondly, to root this, boot twrp and flash magisk. if you are on android 10 you will need to patch the boot image from the factory image of the version you are on with magisk and flash it to your current boot slot.
thirdly, if you are on android 10 and rooted, you will get otas. anything lower and you will need to adb sideload otas.
Click to expand...
Click to collapse
Very impressive signature of the number of many devices you have. Maybe a new wall plaque perhaps?

Htc u12 plus phone Rooting

Hia all
Can a Htc u12plus phone, be rooted if it has the latest updates and security patch?
Would I need to turn S off on the phone too,?
I have two Htc u12 plus phones, both with unlocked bootloaders, but I am a bit nervous about bricking them, without some clear, not vage instructions, most advice so far on the net is very contradicting.
I am running a linux O.S, atm and will try to root them both with a linux terminal.
Any help would be great thanks you all in advance.

in general - yes, you can. Please be aware that custom magisk roms are based on older boot.img and you cant flash them on it.

lulonen said:
in general - yes, you can. Please be aware that custom magisk roms are based on older boot.img and you cant flash them on it.
Click to expand...
Click to collapse
I had thought of madisk, along with twrp, but most of what I have read so far is that they are both outdated, with the latest updates,and security patches.
Lulonen
I swear even as a total noob, it's been way easier to clear windows off a laptop, and put a linux O.S on it, than find a way to de google a phone.

you have tutorials here, it's rather easy and similar on every android phone.
Just start twrp via usb to backup your boot.img (in case of failure and to root), then instal magisk app and patch. Then replace orginal boot.img with patched one using usb fastboot commands.