Database Info

[Q&A] [GT-P31xx] CF-Auto-Root

Q&A for [GT-P31xx] CF-Auto-Root
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GT-P31xx] CF-Auto-Root. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Hi,
I 've tried root my GT-P3100 with auto-root but with no success.
I've stock 4.2.2, first wiped all data and did factory reset, then start rooting. After reboot an icon of supersu appears but after run it says "there is no SU binary installed" . I notice that this version is 2.13 with date 2014/10/10. I download it from link in the third post which is described as containing 1.30 version of superSu inside.
I try to reflashing auto-root many times but binary is still missing.
Maybe superSu misversion is a problem? How can i resolve an issue with missing binary?
Thanks for help, &Y

First post : Need personalized root info for GT-P3113
My first post and not sure what I'm doing or if its the right place, please have patience?
I have a 2012 Galaxy Tab 2 P3113 wifi only model. It auto updated from the stock Andy 4.0 to Andy 4.2.2. Im unhappy with this and Samsung tells me its irreversible. That makes me even more unhappy as, better or worse, its not the same 'user experience' for which I chose the device. Therefore I'm interested in 'rooting' it. My objective is to tweak the interface, disable some of the auto updating and some of the autostarting Samsung software and services (also some phone apps and services) which I will never use and manage autostarting of user installed apps. I would also like the ability to make complete 'single click' backups which include screen/'desktop' arrangements and app settings (such as one would make with a Windows system). I am NOT interested in loading custom ROMs or other modified system ware.
1 Is 'rooting' my solution?
2 Is it reversible?
3 Will it do anything more than unlock the existing system - what modifications will the rooting process make?
4 Will 'unrooting' reverse my settings alterations or can I disable the Samsung ware, and relock the system for safety/security? Will changes such as power or mem settings made by 'root only' apps remain in place after unrooting?
5 Is a 'temporary root' a better solution for me?
6 Has the aforementioned Samsung update made the root process any more difficult or hazardous?
7 Will just rooting leave a permanent detectable trace?
8 Can someone give me the simplest step by step procedure and reversal procedure? I realize this is covered in many places throughout these forums, but this will be my first attempt at raiding a Android device and I would be more confident with a personalized procedure that I can ask questions about and get direct device specific answers to.
I've been having trouble finding straight info about performing a ROOT ONLY. To reiterate I only want enhanced control over the EXISTING system, primarily to prevent autostarts, to positively terminate running apps and to make full image backups - I do NOT want to install modded systems or irreversibly or significantly alter the existing system.
I appreciate any clear info or advice I can get. Thank you.

Rooting Help
Hi I have a Samsung Galaxy Tab 2 7.0 GT-P3113 Jellybean 4.2.2. I have tried the CF Auto Root Method 6 times and it doesn't work. Odin says that it passes and that it worked but when the tab reboots, I try to open SuperSU but it says "There is no SU binary installed! and SuperSU cannot install it. This is a Problem!" Help me please! I know I am doing it right aren't I?

Help. Samsung Galaxy tab
i don't have much experience on rooting, i have only rooted 2 phones and worked. plus this tablet.
so i have a Samsung galaxy tab 2 7.0 GT-P3113 (IR blaster/wifi) at 4.2.2 JB
i tried rooting it with the ChainFire auto root tar.md5 file which is for GT-P3113 on Odin3.07 and odin detected my tablet, but showed it as blue
but seeing it different from Odin1.87 it worked and PASSED! by odin so i flashed it in download mode, on PDA, everything was looking normal,
after the loading on the download mode it went to where the Red pirate guy was shown and after that it rebooted.
i had the SuperSu application when i opened my tab which i didn't have before rooting so i downloaded a couple of root checkers from play store,
here comes the problem,
when i click SuperSU it says "There is no SU binary installed and SUperSU cannot install it. This is a problem!"
and when i check it with a root checker it says no Root Access so i think somehow i failed rooting.
but when i check the Build info via root checkers:
Device: espressowifi
Hardware: espresso
Product: expressowifiue
and it says on SU (info i saw on root checkers):
su found
[/system/xbin/]
i want to try to flash the tar.md5 auto-root file again with odin can i do it again? will it somehow stack the root or i don't know, be a risk for my tablet? or is there a fix to this?
Thank you.

[Q] Samsung Galaxy Trend 3 (SM-G3502) Rooting Help

So.. After a whole week trying to find a succesful way to root this f***ng phone, no success has been found.
I couldn't find this phone's section on XDA so I'm posting this on the general section...
If anyone could give me the link to the section, it would be very appreciated.
This is the phone:
Samsung Galaxy Trend 3 - SM-G3502C
Android Version: 4.3
Build Number: JLS36C.G3502CZCUAOD1
I have tried a number of on android apps, windows software, and even tried rooting manually by adb and linux. But couldn't have a single successful attempt or any signs of progress made...
Can anyone help me out with this phone, the reason I need root is because this is a chinese phone and doesnt have Play Store installed, and I need root access to install Play Store on /system/apps/ and give R+W permission...
Apps tried:
Saferoot
Kingo App Root
iRoot (vRoot/Root Master)
OneClickRoot
TowelRoot
A bunch of .bat rooting scripts
Baidu in-app Rooter
Rooting through ADB (everything was going fine until I had to access Ubuntu's Nautilus, to move the files to /system/ but the device wouldn't mount by MTP on download mode, and I couldn't access the files) link to the guide followed: http://forum.xda-developers.com/show....php?t=2684210
Any help would be truly appreciated, and If there is a way to install play store without the need of root access, or even a good replacement for play store would be really good.
Also, I have 0 experience on custom recovery, so, If any developer out there could create a custom recovery for this phone, I could give them the recovery.img from this phone and modify it to work on this phone. If that's the way it works, idk XD.
P.D. I already opened a thread on XDA-Assist but sorry, I had to move it, I saw that every post on that section had little views and replies and I was worried that this would happened to me on that section to me too. I'm ok if I need to erase it from there but I would like to leave it there for some time if there is any replies.
Link to the thread: http://forum.xda-developers.com/general/xda-assist/samsung-galaxy-trend-3-sm-g3502-rooting-t3106250

Hi, still you right~ looks like your are really can't to wait to root your device. Just try KingRoot, we just release new version which can root device from Android 2.x to 5.0. I can't give you promise, but just have a try~ good luck

[How To] Verizon s5 Kit Kat root and update to PB1 for plain vanilla user

--- edited to update from a "Should I do this?" post to "This is what I did" -------
There are some nice How To guides here, but it's tough at times to roll in years late to a model and decipher what has been updated, what is now moot, and what newer break-throughs or pitfalls have and haven't percolated back into the threads. That makes sense with the phone no longer being a big focus of effort. I, like the S5, am past my peak. It took me a lot of reading and trying to connect the dots to figure out where to go and how to get there. I've laid it out below FYI.
This worked for me in Aug 2016, on one phone and one only. Probably my first and last s5, I'll move up to the s7 when the 9 or 10 comes out and try to burn through 3 or 4 year old threads to find that ground truth. So no promises, certainly no support from me, no plans for me to maintain this thread. I'm just a knucklehead who nugged his way through, and figured I'd post my cheat sheet rather than just throw it away. I did update it a bit as I went along.
What I had --
Newly refurb'd Verizon S5 phone with 4.4.2 NCG
eMMC is 15
Target -- (I think appropriate for my modest needs)
Root & update to 5.0 PB1 with OD5 bootloader
Method overview --
root 4.4.2 using Towelroot
install SuperSUme from Play store and update binaries
use Flashfire to make backups of original system
use Flashfire to update ROM, kernel, most other software (except bootloader) to PB1
use Odin to update bootloader to OD5 (5.0 but last downgradeable)
use Titanium Backup to debloat & freeze, and to restore my user apps & data from old phone
Wondering whether I have the target right -- PB1 w/ OD5 bootloader?
Marshmallow is initially referred to as unrootable, but there's a recent way to get there . However, it seems a bit more involved - requires unlocking the bootloader and can only be done with eMMC 15, don't try with an 11. I don't know if the juice is worth the squeeze for a lower end user like me. I didn't try.
There are lots of custom ROMs, none that I know of that leap out as something I should focus on rather than just a little update and debloat, given my modest skills and enthusiasm.
I probably don't need to be able to downgrade my bootloader in the future, so I could go full PB1. But the directions I found had the OD5 bootloader baked in already, so I'll run with that.
My "For Me & Other Dummies" guide follows
(not complete yet, I'll round it out before I dummy my way through, and revise here for other dummies after I test drive it)
Good references
Paniac's guide, great overview. NOOB READ THIS!!!
Franzie's How To
muniz_ri's How To Update to G900V_xxx and Keep Root -- this one has a bit of complexity in its life cycle. It is linked to from Paniac's guide as a how to update to PB1, but the thread's original post has since been updated to run all the way up to PF4. PF4 seems to be a bit more hit & miss. However, post #777 (et al?) quotes the original post so the details are preserved there for getting to PB1.
How to migrate stuff from old phone, see the last method with TB
Steps
Charge up the new phone.
Install latest Samsung USB drivers on computer.
Start running Titanium Backup on old phone to update user apps and data, it will take a while.
Turn on the new phone. Don't bother with SIM yet. Connect to your WiFi.
Sign in to Google account and get the Play store working.
Install from Play store: eMMC brick bug checker and Astro File Manager
Run eMMC brick bug checker. If it checks out (15) then good. If it doesn't (11) then don't follow these steps, the bootloader update part will cause you pain.
Prep phone
1. Enable developer options (settings > about phone > click on build 7 times)
2. Enable usb debugging (settings > developer options)
3. Go to settings >security and allow apps from unknown sources​
Root with towelroot. See Franzie's How To post #2. Do the SuperSUme steps, too. Some highlights, but read the original post and the screens as they go by.
1. Go to towelroot.com, Click on the lambda to download the file
2. Use Astro to navigate to the download
3. Click on the .apk and use package installer
4. Run towelroot and Make it Rain
5. Install SuperSU from play store
6. Update binaries with Normal
7. Choose to disable Knox
8. Allow reboot
9. Install Root Checker from Play store and run to verify root​
Install Flashfire (see here) from Play store.
Install the PB1 ROM. Use Flashfire.....see post #777, be sure to check all downloads using MD5 checksum, see Paniac's Guide post #3
Install the OD5 bootloader. Use Odin.....again, see post #777, and info in Paniac's guide post #3 on Odin
Now you’ll be on Lollipop, 5.0, PB1 but with a bootloader that is downgradeable in the future. It will be a clean install so you’ll have to reinstall things you just put in, e.g. Flashfire and Astro, but SuperSU is in there.
Use Flashfire to create a backup of your new configuration. See here. Put the files somewhere sage to be able to do a fresh install at this point in the future. See also Odin back to stock
Now customize and move in.
1. This is a handy way to start with debloating
2. See also here for things to Freeze (OTA and security notification) and apps to debloat (though some were ​16. Install Titanium Backup Pro from Play Store (buy it). It will probably warn about “mount namespace separation” setting. Consider going to SuperSU settings and disabling. Reboot.
Use TB to get your user apps and data in from old phone.
Activate the phone on Verizon -- move their SIM over. See FAQ here (item 1) and begin here
Once all is settled, go to settings >security and unallow apps from unknown sources

If your on ngc with eMMC 15 you can unlock your bootloader and flash custom roms also if you don't go past BOD5 and don't want to unlock your bootloader you can downgrade back to kit kat
Sent from my SM-G900V using Tapatalk

That worked. Almost smoothly.
I've udpated the first post with what I learned along the way, and am outta here. No more clogging up the bandwidth of the folks that know what they're doing.
No original work on my part, just a decent bit of effort pulling together the bits and pieces from across a number of super helpful postings to figure out what was still on target for me. I'll just leave my notes for whoever might benefit, rather than flush them and leave the next person to have to chase it all down for themself..

samsung galaxy s9 root android 10 exynos

Hello, is there a way to root the phone where everything works now (Bluetooth, Face ID, etc.)?

I would very much like to see this answered. I've seen some application-specific instructions such as this reddit thread for enabling Samsung Health, and I've read about hiding the fact that the phone is rooted from apps by using MagiskHide, but it's not clear whether this works for all apps and features or just some. There's also this recently updated guide to rooting that claims:
Magisk is a highly advanced way of rooting android systemless-ly. This means that Magisk root android without changing or modifying the system partition. Hence you can receive OTA updates, run apps that require to pass Google’s SafetyNet tests.
Click to expand...
Click to collapse
However, many hacks that sound good when you read about them in advance run into snags and gotchas once you actually get into implementing them, and I'm hesitant to just give it a try and see how it works out when tripping Knox is irreversible and if things stop working you can't get them back by flashing the stock ROM.
I'd be grateful if anyone who has actual experience on this subject could vouch for being able to re-enable all lost functionality after rooting or to not lose it in the first place, or whether even some lost functionality can be enabled (and if so, what have you been able to get working and what haven't you? I don't know about OP, but to me the most important ones are Secure Folder and Samsung Health).
Also, does anyone have experience with retaining Knox-sensitive functionality on rooted S9 Exynos with Android 11 (either rooting after upgrading to 11, or rooting first and retaining root when upgrading)?

@bis225
IMO noone needs Magisk to root a device's Android. Rooting Android means having the SU-binary present on Android - a ~100KB file - nothing else. Copying SU-binary onto Android allows you to temporariy give you root access when needed.

jwoegerbauer said:
@bis225
IMO noone needs Magisk to root a device's Android. Rooting Android means having the SU-binary present on Android - a ~100KB file - nothing else. Copying SU-binary onto Android allows you to temporariy give you root access when needed.
Click to expand...
Click to collapse
I'm not sure I understand what you're saying. Are you telling me that you can simply copy the file onto an unrooted phone, and voila, you can gain root access?? Can you point to information about what to do and how this works? It runs contrary to everything I've ever read on the subject.
To the best of my understanding, in order to install su binary unto an unrooted phone you need to install a custom recovery, and use that to flash the su binary onto the phone. I thought the idea of Magisk was to provide root access without modifying system files so that SafetyNet can't detect that the system has been modified. Unless I'm missing something there's no disadvantage to rooting with Magisk, only advantages, but regardless, I don't see how it makes a difference with respect to this topic. Installing a custom recovery is what trips Knox and prevents some features and apps from working, so it doesn't really matter what root method you use if you have to use a custom recovery to install it.
If you know of a way to root a Galaxy S9 without using a custom recovery or tripping Knox and that can't be detected by SafetyNet, please elaborate.

Rooting Android simply means to add a ( hidden ) user called root ( AKA super-user ) who has ALL rights to Android's file system.
For example from within ADB you activate this user and let run him any command what requires to have ALL rights - assumed the SU-binary is located in /sdcard
Code:
adb shell "/sdcard/su -c '<command-here>'"
AFAIK Magisk installs the SU-binary in /data/adb/magisk/busybox, but I may err.

@jwoegerbauer
But I didn't ask what rooting means. Unfortunately, this doesn't answer any of my questions.

I think I clearly expressed that neither a Custom Revovery nor Magisk itself is needed to have root, that simply copying SU-binary to Android's user-space is enough.
If you want to root via Magisk then do it.
Personally never would do it this way.

jwoegerbauer said:
I think I clearly expressed that neither a Custom Revovery nor Magisk itself is needed to have root, that simply copying SU-binary to Android's user-space is enough.
If you want to root via Magisk then do it.
Personally never would do it this way.
Click to expand...
Click to collapse
This really seems contrary to everything I've read, and this Stack Exchange thread specifically explains why that wouldn't work, but if you say you have experience with this and it works for you, I'm certainly willing to give it a try and see how far it gets me. Do you know where a copy of the su binary can be obtained? All my searches for su binary lead to the supersu APK and instructions for installing it by flashing, or something along those lines. I can't find an su executable that can just be copied to internal storage as-is anywhere.

Samsung Galaxy M21 2021 Edition (SM-M215G/DS)

I own some old samsung Galaxy models like J7 Prime and had tried good Custom ROMs on them but up recent I purchased this Samsung Galaxy M21 2021 Edition (SM-M215G/DS) a few days ago thinking that it's going to be same as Galaxy M21 2019 (SM-M215F) model, to my horor its bootloader & recovery seems to work differently from J7 prime (with bar codes in download mode) . So it's a differrent model. The bootloader unlock process on this Galaxy M21 2021 Edition is same as mentioned in Galaxy M21 2019 thread ( https://forum.xda-developers.com/t/rom-full-oneui-10-totsukaos-q-for-galaxy-m21.4219975/ ) but none of the unofficial TWRP recoveries work nor does Magisk boot.img patch method work for rooting this model. Samsung does not support Fastboot as I understand & everything ends with Error : Signature verification failed. The only option left to me is sell off this phone but its so new.
If any developer can help me with some Custom Recovery that could install itself for rooting and perhaps custom ROM (I know I'm asking for too much ) for this device (SM-M215/DS), I will gladly donate $20.00/month for a year (Pls consider the bad times of pandemic we all are in). As right now I've put up this device (SM-M215G/DS) for sale. I've attached a few screenshots of the device maybe it could help any Dev who's interested (Hopefully ).

To root Android a Custom Recovery isn't required at all.

jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
jwoegerbauer said:
Firstly, I THANK YOU for replying to my desperate post. I'm delighted that Dev (jwoegerbauer) wanted to help.
Coming to the topic, Yes I was aware that rooting didnt require Custom Recovery.
1> I had tried to install Magisk_V23.zip via command [adb sideload magisk.zip] but the
response I had got was [Error: Signature verification failed, Error: Aborted.] on this device
(SM-M215G/DS).
2> When I flashed couple of TWRPs (one official for Galaxy M20 from www.twrp.me & few
unofficial TWRP builds from the net) via latest ODINv14.3 , ODIN displayed PASS! and
rebooted as I had kept Auto Reboot & F.Reset Time ON. But Native Android revovery came
on with Custom Binary Error. Again, I did the same with F.Reset Time & Auto Reboot OFF this
time and when I manually rebooted to recovery (Vol UP + Power) it was back to native
android recovery. I had to factrory reset to get the samsung logo then booted into welcome
screen.
3> I have checked the link ( https://forum.xda-developers.com/t/...al-adb-fastboot-
drivers.4185535/post-83851013 ) you provided. Awesome work! My questions are will it
enable FASTBOOT on SAMSUNG? Because when I select Reboot to Bootloader option in Anroid Recovery the phone does go into Fastboot Mode but apparently Fastboot seems
disabled by Samsung because from the PC it does not recognise the Fastboot Devices. So,
as a noob if I've understood whats mentioned in the link you provided is that Samsung didnt
provide the Native Samsung Fastboot Drivers for the Galaxy M21 2021 DELIBERATELY? So,
the link you provided will help me install the required Fastboot Drivers? & then I can flash
TWRP.img or Magisk.img?
Thanks in advance
Click to expand...
Click to collapse

jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
Followup 1:
Hi, I tried your ADB-FASTBOOT-Installer but it doesnt seem to go beyond "Waiting for devices" screen.
1> I tried installing magisk v.19.3.zip (renamed to just "OTA") using command (adb sideload OTA)
first error i got was (adb: failed to read command: No error)
2> second time i tried installing from another folder belonging to 15-seconds-adb and it showed [ (0.01x) success ] something like that
3> I installed magisk manager 2021.4.9 Magisk v22.1 by Package Installer method not sideload method. When i rebooted & checked magisk manager it wasnt rooted so I tried boot.img patch method and got error: unable to unpack boot.img
I have attched some screenshots of the errors but what I understand from this is that the new Samsung devices might have img files written in some new format i guess because why else would magisk manager fail to unpack and patch a boot.img file, ususally it does fine.
I have also attached a copy of the device stock boot image file (hope i'm not breaking some xda rules here about posting img files , i just joined yesterday so )
Maybe its of some help to some Dev who might need these to find a workable solution.
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/

Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .

jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.

LR7875 said:
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.
Click to expand...
Click to collapse
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.

jwoegerbauer said:
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.
Click to expand...
Click to collapse
Oh learned something more.
Well what is the definition of root then?

LR7875 said:
Oh learned something more.
Well what is the definition of root then?
Click to expand...
Click to collapse
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.

jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Hi there jwoegerbauer, thanks for responding. If im not being bothersome , I'll need to stalk you on XDA for some help on this issue of rooting this device, if it s okay with you . Pray tell me what else other than magisk could root this stubborn Samsung model ? Im getting some good offers for this device on the local online market but i really didnt want to sell it off just wanted to root & install roms like before.. Other than magisk I just know of SuperSU by chainfire which I think stopped working well post android 8 oreo but will it work for Android 11? No way any changes to /system/Priv-app and the phones factory reset themselves. One-Click Root only takes calls & they charge $50 for rooting, but whats the guarantee if we pay up that theyll root it properly & taht too it would be just root not Recovery or ROMs. I'm lost.

Installing Magisk DOESN'T ROOT Android. Installing SuperSU DOESN'T ROOT Android. POV.
To have said it:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
SuperSU simply is a per-app root-access management tool, nothing else: it requires Android got rooted.

OldNoobOne said:
...
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/
Click to expand...
Click to collapse
How are you "flashing"?
Why do you say it "is flashing well"?
As far as I know, you need to use Odin (on a PC) to "flash" a Samsung device. Samsung does not support fastboot -- no amount of updating drivers on your PC will make a Samsung device start supporting fastboot.
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
If you have installed the Magisk Manager app and tried to patch the AP.tar of the stock firmware, and you are getting an error, you should look through the main Magisk thread, and maybe ask there.

J.Michael said:
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
Click to expand...
Click to collapse
IMO you're WRONG: Magisk DOESN'T ROOT Android, but you additionally can install MagiskSU app what grants elevated rights ( AKA SU ) to Magisk.

jwoegerbauer said:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
Click to expand...
Click to collapse
I need to hop on and correct a few details here...
Magisk is not a successor to Xposed. That's like comparing apples and oranges. If you want to know how Magisk came to be John has written about that in a couple of places, here for example:
Spoiler
https://www.reddit.com/r/Android/comments/7oem7o
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device. Details about that here:
https://topjohnwu.github.io/Magisk/boot.html

OldNoobOne said:
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.
Click to expand...
Click to collapse
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.

Didgeridoohan said:
I need to hop on and correct a few details here...
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device.
Click to expand...
Click to collapse
Correct: it should also have been called boot.img instead of bootloader. Sorry for this.

LR7875 said:
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.
Click to expand...
Click to collapse
True . Don't quote me, (In a nut shell ) up from Andoid 9 (Pie) modification to /system /app etc. is difficult per my knowledge, thats why probably magisk sits in the boot partition, no one dare touches the system partition anymore while the gadget is ON. Only Gugle stays in the system partition im sure. The Custom Recoveries do wipe the device but are unable to erase the core andoid OS inside . Even 'Fastboot Erase' command cant get andoid out completely (exception Linux-phones i think). So practically Andoid devices are just gadgets that are 'leased' to the so-called 'owner' of the device (without explicitly mentioning the term 'leased' by gugle). The cost of the smart-gadget is practically the 'Down Payment' we pay to Gugle & OEMs then the rest of the revenue they make from Ads etc. which goes as 'Rent/lease payment' to them ultimaately & we never get to own the devices we purchase EVER! .
My sixth-sense says The chinese OEMs allowing Fastboot Mode only for now but only to make inroads into the smart-gadget market, once they have made everyones profile Gugle & pentgon might just make the softwares on these smart-gadgets wholly tamper-proof & focus more on 'managing' or keeping an eye on their 'subjects' [given that the whole gugle business,- 'search-engine', 'smart-device' etc. started officially in 2004 which was POST the 9.11 ATTACK].
So they're probably maintaining the Big-Data on everyone who uses their devices & 2014 is when data-warehousing became the need if i remember correctly; so, it was all about compressing the Big-data gathered & then Analytecs took the spotlight by 2016-17 coz they needed to analyize all the data collected & remove the junk from it then home in on pentgons targets. It's Obvious . No wonder they're pushing PX-Xperience ROMs through the ROM channels to cover the gap created by chinese OEMs eating into their market share. Why else do they charge other OEMs $2 for OTG-support while Shamshung (and now MYUI) already had native OTG-support on their devices shipped? so that's what Sekure-folder all about, YOUR DATA LOADED & LOCKED real-time then SHIPPED back to Gugle-Analytecs. Obvious.

Well so root is basically... Removing those ads and trackware up to the bare bones of the phone, to ensure all your data isn't used to make the spammy advertisements?

Android is nothing else then a derivated Linux. In the world of Linux the Root User is the user that has all rights esp. accessing / modifying system files, it's comparable to the Administrator in the world of Windows.
In the world of Linux this Root User typically is called superuser ( commonly abbreviated: SU ). In the world of Android such a superuser isn't in general implemented by default: it must get added to Android by modding it, means adding a SU ( read: Switch User ) binary - in whatever form - to Android what is systemwide accessible. In the world of Android an user root exists what is the user with user ID 0.

[ deleted ]