Database Info

How to install January 5th patch while using custom recovery and root on Google Pixel

Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!

All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.

zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself

exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.

jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?

I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.

32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.

This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.

Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk

Do you need to reflash stock kernel before removing root/TWRP before flashing?

32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.

TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.

I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?

km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.

If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away

jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them

FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.

SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3

[HOW-TO] Root Nokia 8 with Systemless Magisk

Reason for edit: Change title so more users can find this method since for now TWRP is working but not to root
Click to expand...
Click to collapse
Hello fellow XDA users,
On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
I've been following all threads here on XDA and for the last few days its like a boom of new information, yesterday a Senior Member provided me with the Unlock Key generated with my IMEI1 and the phone's bootloader is now unlocked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now the next logical part I would be installing TWRP to flash the magisk flashable zip to the phone, but there is no TWRP built to our phones (old information, there is now an official TWRP build)..
To my surprise there is this thread that offers boot images already patched with root ( @nummerok are they patched under magisk?), I tried flashing first with:
Code:
fastboot boot NB1-0-484A-00WW-boot.img
But it did not worked, no matter what the installed Magisk Manager would not find the Magisk Module on the system.
Then I found out that some users were getting root but with the problem of losing wifi connectivity, that was found to be the fault of the phone having the March Security Patch (00WW_4_84A_SP01) while flashing the boot image of the phone with the February Security Patch (00WW_4_84A).
As of this new A-B partition scheme on Android, when your boot image does not pass dm-verity it restores the older version automatically (Am I right on this point?? can please someone confirm?!)
Since my phone WAS on the march patch I saw no other option but to wait someone to grab the march boot image to patch it Magisk Manager and get root.
Buut since my generation doesn't like to sit and wait I found that there was a way to roll back to the previous firmware!
What I did was, run this code below on adb to know which slot my phone was:
Code:
adb shell getprop ro.boot.slot_suffix
Then take note of the slot and run:
Code:
adb reboot bootloader
After the device starts up in Download Mode you need to switch to the other boot slot. Just run:
Code:
If you are currently on slot A, type this: [B][I]fastboot --set-active=_b[/I][/B]
Or on slot B type this: [B][I]fastboot --set-active=_a[/I][/B]
You should see something like this:
Code:
Setting current slot to 'a'... OKAY [ 0.046s] finished. total time: 0.046s
Now run the code below and cross your fingers!
Code:
fastboot reboot
Once the phone has booted, check in Settings/System/About Phone if your Android security patch level has downgraded to the February one and proceed to the next step.
I've downloaded the full NB1-484A-0-00WW-B03.nb0 firmware from @blackpanther0582 thread under the google drive link and extracted the boot image using the tool made by @heineken78 available over here (be sure to have lots of ram available for the unpack process :fingers-crossed.
With the file NB1-0-484A-00WW-boot.img at hand I've copied it to the Nokia 8 internal storage and ran Magisk Manager to patch it, follow instructions here under Via Magisk Manager (Only support v14.0+) part.
Now grab the patched_boot.img file provided by Magisk from the phone and save it (adb pull or whatever) to your pc and run these commands:
Code:
adb reboot bootloader
After the phone boots up in Download Mode run:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
With that done, after the boot you can open Magisk Manager to see it fully installed and later on install some root checker app just to be sure of the sucess of your rooting:
Split-screen to the rescue lol
This Nokia 8 is officially rooted but with the previous February patch and I'm itching to install the March OTA provided by @2WildFirE here, any thoughts on that? What about the official system update that still lists the 2018-03 security patch? Would any of which work?
And that is all for now folks!
I would like to thank @the_laser @heineken78 @topjohnwu @blackpanther0582 @nummerok and many others in this invaluable path to learning more about this phone and the Android system in general!
Good Luck!!

Reserved

Nice, this will help some people to understand.
Powered by Nokia 8 with open bootloader

2WildFirE said:
Nice, this will help some people to understand.
Click to expand...
Click to collapse
That's the idea @2WildFirE !
btw just to make things clear, the official system update is running for like 10 hours and it seems it's not going anywhere.. would I get success by doing the march update thru the zip you've found?

Yep was working fine here, to bring my wifi back, but lost root [emoji6] what we Really need is twrp and or a method to extract the boot.img from the *. Bin file included in the update zip.
Powered by Nokia 8 with open bootloader

I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?

contrahelix said:
I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?
Click to expand...
Click to collapse
It should work only if you have your bootloader unlocked @contrahelix
You might get it unlocked officially by Nokia or wait for an alternative method.
Also you should update your adb/fastboot tools, then you would get the right error message telling you about the still locked bootloader!

On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
Click to expand...
Click to collapse
I have a TA-1012 i assume it won't work for me?

For everyone with unlocked bootloader, this is the method to root without TWRP !

Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...

Raithlin said:
Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...
Click to expand...
Click to collapse
Still have to rollback to official image.. you cannot upgrade with patched img unfortunately

As u have unlocked bootloader and installed magisk i have a question .
Is it worth to unlock bootloader and install magisk.......?
And one more any custom rom available for nokia8 ta1004.......?

شرا

[TOOL][BERYLLIUM] TOOL ALL IN ONE (Drivers|TWRP|Factory Image|Stock Recovery)

This is the Xiaomi PocoPhone F1's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

I want to specify that this tool can't bypass Xiaomi Bootloader Unlock procedure but all others function are working

Whoa... It's here already... Gonna make life easier for a lot of people like me ^_^
Thanks for the efforts ? Much Love.

Nice thing

mauronofrio said:
this is the xiaomi pocophone f1's tool all in one discussion thread more info and download go to the original thread
tool all in one
advanced options
functions
install drivers
unlock bootloader
lock bootloader (use carefully)
flash twrp recovery
flash stock recovery
flash stock factory image
install apks
uninstall apks
take a screenshot
flash partitions
erase all data (this function can decrypt the phone)
reboot phone
update the tool to latest version
update adb and fastboot to latest version
set adb and fastboot priviliges in system wide
install zip directly from pc (required twrp on phone)(these functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect twrp on my phone)
flash fastboot rom
delete downloaded files
adb file manager
device list
if you want you can send a request to add a new device here:
new device request form
device list
download
original thread
donate link
if you want to support the project please consider making a donation, thanks.
​
Click to expand...
Click to collapse
thank you very much it was much awaited tool .

bravo2526 said:
thank you very much it was much awaited tool .
Click to expand...
Click to collapse
Please don't quote the OP.
Sent from my POCO F1 using XDA Labs

Good tool. Please do make provision to select multiple apps at a time under 'install apk' option. Otherwise it is difficult to select a single app, then waiting it to install and then selecting the next app then waiting and so on...

mauronofrio said:
I want to specify that this tool can't bypass Xiaomi Bootloader Unlock procedure but all others function are working
Click to expand...
Click to collapse
EDL too?

itsmuhammedmuneer said:
Good tool. Please do make provision to select multiple apps at a time under 'install apk' option. Otherwise it is difficult to select a single app, then waiting it to install and then selecting the next app then waiting and so on...
Click to expand...
Click to collapse
Good idea, i will do it

mauronofrio said:
Good idea, i will do it
Click to expand...
Click to collapse
Happy to hear that

Boot to edl working?

Puneeth 676797 said:
Boot to edl working?
Click to expand...
Click to collapse
I have not tested it

How to root using this tool? I select root after flashing the recovery but it just flashes the recovery and boots into it. What's the next step?

jperkovic said:
How to root using this tool? I select root after flashing the recovery but it just flashes the recovery and boots into it. What's the next step?
Click to expand...
Click to collapse
Have you choose the magisk version? Can you see when you are in TWRP the device is recognized in adb mode?

itsmuhammedmuneer said:
Happy to hear that
Click to expand...
Click to collapse
Updated the tool with a new Apk Installer that support multiple apk install at the same time

mauronofrio said:
Updated the tool with a new Apk Installer that support multiple apk install at the same time
Click to expand...
Click to collapse
Wow...!!! Thanks for hearing. I wil test and report.:good:

mauronofrio said:
Updated the tool with a new Apk Installer that support multiple apk install at the same time
Click to expand...
Click to collapse
I was busy for a while and I tested it.
Cannot install apks as bulk (30+ apks) by selecting all. I tried to install 68 apks at time, failed, again tried half of it, failed.
No issues with 20-25 apks.
Please do have a note of it and try to fix it.

itsmuhammedmuneer said:
I was busy for a while and I tested it.
Cannot install apks as bulk (30+ apks) by selecting all. I tried for install 68 apks at time, failed, tried half of it, failed.
No issues with 20-25 apks.
Please do have a note of it and try to fix it.
Click to expand...
Click to collapse
Oh god, i tried with 10-15 apks, i will try with more of them, can you tell me which problem gived you?

mauronofrio said:
Oh god, i tried with 10-15 apks, i will try with more of them, can you tell me which problem gived you?
Click to expand...
Click to collapse
No response after selecting the apks. Usually a command window should open, but not in this case. Installing is shown only for a fraction of second and then it disappears and back to "Install selected Apks".

mauronofrio said:
Oh god, i tried with 10-15 apks, i will try with more of them, can you tell me which problem gived you?
Click to expand...
Click to collapse
No issues with 25+ apks. Try with 50+apks.

Moto G Play 2023

Hi all new here glad to be a member
anyway i just unlocked the bootloader and rooted with magisk through BOOT.img patching.... my Question is, are there any custom roms or anything out yet for this phone? Android 12 .thank you so much

Thats amazing. From my own research i understand this phone is so new that people have yet the get their hands on it to work on it also the fact that it uses a mediatek instead of a snapdragon is a sticking point for a lot of developers even though its basically the same phone as the g power 22 and g play 21

Hi sam9566
Yeah I broke my other phone cheap . So I looked for an unlocked carrier phone close to me and Walmart had like 7 maybe. But they were in lockup couldn't find it. So I asked the guy in the back he looked around and took his key out and went into this metal cage that you couldn't see into and pulled one out and sold it to me really quickly . Then I had to wait 9 days for the OEM UNLOCK to be UN-greyed in dev options. But in those 9 days I waited for an email from moto for my unlock code but never showed. So I got on live site chat and within 2 minutes the person gave me the 20 digit code . And after 9 days I unlocked the bootloader, then I used the Lenovo software to get the factory Rom extracted the boot.img used magisk to patch then flashed.. lol been debloating the crap out this phone.. it uses 51% storage after setup is completed

nice lets try to actually keep this thread alive so maybe we can get a lineage rom for this phone eventually???

well got rid of all the preinstalled apps and moto junk lol got down to 39% storage used. now what lol im bored

Yeah im still completely lost on how you did this could you possibly post a step by step guide???

lol ill try
1: download https://www.motorola.com/us/rescue-and-smart-assistant/p MOTOROLA SITE please be patient the program is slow just a warning if anyone thinks its hung..
2: Download magisk from GITHUB on your phone and install it.
3: download ADB_Fastboot
4: open rescue and smart assistant program and do the steps it says to do, then once it finds the ROM it MIGHT say already have latest... Say download anyway..
5: now once its done downloading dont do anything else. go to the download location and open the file and copy the BOOT.IMG to desktop or where ever you want it..
6: Now copy the BOOT.IMG to your phone's internal storage Download folder.
7:Run magisk and click top install then select and patch a file. locate the boot.img on your phone and patch it.
8: once done copy the patched file back to the PC i put it in ADB FASTBOOT folder. rename it too BOOT.IMG open CMD with admin rights or it wont work.
9: type (adb reboot-bootloader), should reboot into bootloader. now do this command (fastboot devices) make sure it see's the device.. then type ( fastboot flash boot boot.img ) -BOOT.IMG is what ever name you make it but for simple measures i did boot.img. let it finish reboot device with ( fastboot reboot ).. now open magisk and let it finish what its got to do...
10: ENJOY hope this helps someone out.. i never wrote a guide before as you can tell hahaha.. let me know if there is any QUESTIONS

Gonna have to dig out my windows pc ugh

lol what device do you have?
sam9566 said:
Gonna have to dig out my windows pc ugh
Click to expand...
Click to collapse

My main rig is a mac running os 10.15 so idk if ill be able to run your tutorial step my step i do have adb tools installed but the paths etc are different because of the operating system

sam9566 said:
My main rig is a mac running os 10.15 so idk if ill be able to run your tutorial step my step i do have adb tools installed but the paths etc are different because of the operating system
Click to expand...
Click to collapse
my bad i meant your phone.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

samtron6 said:
my bad i meant your phone.
Click to expand...
Click to collapse
So what do i do next on my pc in still lost

sam9566 said:
So what do i do next on my pc in still lost
Click to expand...
Click to collapse
do you have bootloader in dev option enabled?

Yes

samtron6 said:
well got rid of all the preinstalled apps and moto junk lol got down to 39% storage used. now what lol im bored
Click to expand...
Click to collapse
Same here. Unloaded all the "Junk",and this little pistol is much faster-- however, still looking for a custom ROM.

dcluvsme said:
Same here. Unloaded all the "Junk",and this little pistol is much faster-- however, still looking for a custom ROM.
Click to expand...
Click to collapse
same.

I was struggling to get my boot partition to flash (not found error). Ultimately I had to flash boot_a and boot_b as described here.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

hmm i didnt have to flash the boot a or boot b.. i just did the flashboot boot.img command. maybe i didnt do something right lol now im going to try this when i get time today.. thanks

Yes, you must flash boot_a and boot_b

Question How can I root the Motorola Edge 30?

All i can find are tutorials for the Neo and Pro versions of this device. Can this version be rooted? How?

recovery sideload+magisk

alekksander said:
recovery sideload+magisk
Click to expand...
Click to collapse
Hey, thanks for the reply. I'm still new, can you elaborate? Maybe possibly link a tut? Appreciate it regardless.

alekksander said:
recovery sideload+magisk
Click to expand...
Click to collapse
What is recovery sideload?

useroso987 said:
What is recovery sideload?
Click to expand...
Click to collapse
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt

Kurt Krummbein said:
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Click to expand...
Click to collapse
Well, i've been reading past days...
I've installed Delta Magisk through adb on Lineage OS 20. It was quite a fast and interesting process!
Thank you.

Kurt Krummbein said:
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Click to expand...
Click to collapse
Instead of being helpful you give some strange lessons it seems to me that you are useless here. If someone asks you politely for help, explain it to them. Every phone unlocks differently.

Kasjopea73 said:
Instead of being helpful you give some strange lessons it seems to me that you are useless here. If someone asks you politely for help, explain it to them.
Click to expand...
Click to collapse
Well, i tried to figure out, that not knowing the basics of running the phones recovery and using sideload is a bad starting point to open root access on the device.
Kasjopea73 said:
Every phone unlocks differently.
Click to expand...
Click to collapse
Well, that's not the core of my answer and i do not disagree ... just wanted to prevent a newbee from bricking his device and not beeing able to recover ;-) or walking around with a spy-phone recording and sharing his whole live-data with someone who should not know anything of it at all.
@Kasjopea73 : if you volonteer to answer request like "i tryied to root and bricked my device" in personal chat, then it's ok ... i've seen too many chats on other devices beeing flooded by those kind of requests, rendering these chats useless for developers who tried to exchange information on fixing problems.
Ciao
Kurt

Kurt Krummbein said:
Well, i tried to figure out, that not knowing the basics of running the phones recovery and using sideload is a bad starting point to open root access on the device.
Well, that's not the core of my answer and i do not disagree ... just wanted to prevent a newbee from bricking his device and not beeing able to recover ;-) or walking around with a spy-phone recording and sharing his whole live-data with someone who should not know anything of it at all.
@Kasjopea73 : if you volonteer to answer request like "i tryied to root and bricked my device" in personal chat, then it's ok ... i've seen too many chats on other devices beeing flooded by those kind of requests, rendering these chats useless for developers who tried to exchange information on fixing problems.
Ciao
Kurt
Click to expand...
Click to collapse
The best thing to do is not to write anything anymore, you are no help here and it is better to disappear. This is a forum for development, not for throwing obstacles under someone's feet. Rooting this phone is trivial, just extract the boot.img from the rom you are using, not from any other, and in magisk make a patch, instructions you will find below the post. If you don't know what is going on don't write nonsense to anyone.

Instructions Steps: Unlock Bootloader and Root​Platform Tools:
For Windows:​
Download File: Download
For macOS​
Download File: Download
For Linux​
Download File: Download
At first, you need to connect your device to PC via USB cable.
Next, head over to the platform-tools folder, then you have to type in CMD in the address bar and click enter. Command Prompt window will popup.
Now type the below command to boot your device into fast boot mode:
adb reboot bootloader
Next, you will need to get your device-specific unlock token. For that, execute the below command:
fastboot oem get_unlock_data
You will now get an alphanumeric character, that you have to copy all of the codes without the bootloader prefix. To follow this step, you may copy all the commands, paste it in a Notepad, and then delete the bootloader prefix. Further, make sure that there isn’t any space between any line of codes.
Now go to Motorola Unlock page and sign-in with your account. After this, copy that code and paste that into provided space. Then tap on the “Can my device be unlocked button”
Then, you will receive a Unique Key on your email. In normal scenerio, the code usually takes a few minutes to reach your email. But if not wait for few more minutes and you will get the code.
Go back the command prompt window and execute the below command. In the following command replace the UNIQUE_KEY with the key that you have received from Motorola.
fastboot oem unlock UNIQUE_KEY
Your bootloader is unlocked, after the whole process is done which will take few minutes. Now if your device doesn’t reboot to the system then you can use the below command to do it manually.
fastboot reboot
CONGRATULATIONS! YOU HAVE UNLOCKED THE BOOTLOADER OF YOUR DEVICE. NOW LET’S PROCEED TO ROOT THE DEVICE
2. ROOT MOTOROLA EDGE 30, PLUS ecc......​Thera are two ways root motorola edge plus: one is flashing SuperSu Zip with TWRP Recover and another one patching the boot.img file. Currerntly, there is no TWRP Recovery for motorola edge plus, so we will be choosing the latter (patching) option.
Instructions Steps:​
First download the stock firmware and extract the firmware file. Now search the stock boot file which would be named as boot.img. Copy this file to your Motorola edge plus.
Install Magisk Manager which you have downloaded earlier.
After installation, open magisk manager and tap on Install > Install > Select and Patch file (Here you have to select the boot.img file)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Magisk will start the patching process which will take just a few seconds.
After the patching process is done, you should see the magisk_patched.img in your internal storage’s Downloads folder.
Now you have to transfer magisk_patched.img to your platform-tools folder. Open CMD in this folder by searching “CMD” in the address bar and hit Enter.
Connect Motorola edge plus with PC via USB Cable and type the following command:
adb reboot bootloader
Now you have to flash magisk_patched.img and for that type the following command:
fastboot flash boot magisk_patched.img
The process will take only a few seconds. Once its complete, you may reboot your device via the following command:
fastboot reboot
Now you can open magisk manger and very the root as well.
CONGRATULATIONS! YOU HAVE SUCCESSFULLY ROOTED YOUR MOTOROLA EDGE PLUS.

There is another solution for making Root on Telegram groups. Unlock the bootloader and install TWRP then Magisk.

I did this as described, it works fine. I tried a couple of days with root and stock ROM but revert back to the original because of google wallet that didn't work suddenly.

hans3103 said:
I did this as described, it works fine. I tried a couple of days with root and stock ROM but revert back to the original because of google wallet that didn't work suddenly.
Click to expand...
Click to collapse
SafetyNet fix install