How To Root Phone Without Unlocking Bootloader

You lot are using an out of date browser. It may non brandish this or other websites correctly.
You should upgrade or employ an alternative browser.

• #ane

Phone is Samsung A50 (A505F), Android 11,

one) As championship.. how do you lot do that? I will keep stock ROM.
But desire to root to debloat, and add other apps that require root.

2) Too if you use kingroot, does it unlock the bootloader?

three) If you relock a bootloader does information technology remove root?
Will relocking erase user data?

Thank you

Concluding edited: May 24, 2021

Deleted member 1890170

Invitee

• #2

Generally speaking - with regards to this thread's title:

Rooting phone's Android works without unlocking it's bootloader. Rooting Android simply is calculation an user chosen "superuser ( AKA root )" to Android.
Reason why people unlock bootloader is to be able to flash custom ROMS.

Last edited by a moderator: May 23, 2021

• #3

1) Every bit title.. how practice you lot exercise that?

2) Also if you apply kingroot, does it unlock the bootloader?

Is the kingroot app required to exist installed at all times to keep root?

3) If you relock a bootloader does information technology remove root?
Volition relocking erase user information?

Phone is Samsung A50 (A505F)

Thank you

Rooting without unlocking bootloader just works on
4.2 jellybean
4.four KitKat
5.0 lollipop
v.1.1. lollipop
All of the other version of android will not piece of work considering in android 6 marshmallow google patched root without unlocking bootloader then this means if u are on Android 6 marshmallow it will not work likewise if u are on Android vi marshmallow and higher don't brother with kingroot or all of that 1 click root because that volition non work I would recommend magisk to root your phone

Deleted member 1890170

Guest

• #iv

@rossrosh007

Hint: Add Samsung A50 (A505F) to this thread'southward title thus mainly owners of such a device get addressed.

• #five

Rooting without unlocking bootloader only works on
iv.2 jellybean
iv.4 KitKat
five.0 lollipop
v.1.1. lollipop
All of the other version of android will not work considering in android six marshmallow google patched root without unlocking bootloader so this ways if u are on Android 6 marshmallow information technology will non work likewise if u are on Android half dozen marshmallow and higher don't brother with kingroot or all of that 1 click root considering that will not work I would recommend magisk to root your phone

I'g on Android eleven.
Ok, so I have to patch boot.img with magisk or magisk manager (I don't know the departure)? On GitHub the latest version is simply magisk v22.

And then to use magisk unlocking bootloader is required... I'll be keeping stock ROM. So will I exist able to relock bootloader after patching and rooting?

• #half-dozen

By and large speaking - with regards to this thread's title:

Rooting phone's Android works without unlocking it'due south bootloader. Rooting Android simply is calculation an user chosen "superuser ( AKA root )" to Android.
Reason why people unlock bootloader is to exist able to wink custom ROMS.

I'm on Android 11, and I'll keep stock Rom.
How tin can I flash SuperSU without custom recovery or unlocking bootloader?

If I have to unlock bootloader, can I relock it later flashing SuperSU?

Deleted fellow member 1890170

Guest

• #7

I'm on Android 11, and I'll keep stock Rom.
How can I flash SuperSU without custom recovery or unlocking bootloader?

If I accept to unlock bootloader, can I relock it after flashing SuperSU?

Don't misfile SuperSU ( what is an awarding which lets you manage root permissions for apps which require root access) and SU ( AKA superuser and/or root ): Totally different things.

SuperSU app relies on presence of SU applet.

Installing SU applet doesn't require phone's bootloader gets unlocked, just information technology's required Android'southward DM-VERITY characteristic permanently gets disabled before, this because content of /system partition gets contradistinct.

Look also within here:

Last edited by a moderator: May 24, 2021

• #8

Don't confuse SuperSU ( what is an awarding which lets you manage root permissions for apps which require root access) and SU ( AKA superuser and/or root ): Totally different things.

SuperSU app relies on presence of SU applet.

Installing SU applet doesn't require phone'south bootloader gets unlocked, but it's required Android's DM-VERITY feature permanently gets disabled before, this considering content of /system partition gets altered.

Look also inside here:

Ok. SuperSU app is the permission manager.

How exercise I go about implementing superuser without unlocking bootloader on Android 11?

Unlocking BL is required when using magisk. I'll be keeping stock ROM, so will I be able to relock BL after patching boot.img with magisk? Volition root/superuser stay if I relock BL?

Some threads say the magisk patched kick.img is considered tampered and the DM-verity will cause issues when relocking BL. Unless you sign it... Is that truthful? (Different users saying true and false, then I don't know what is what)

Terminal edited: May 24, 2021

Deleted member 1890170

Guest

• #9

1. You install matching SU applet by ways of ADB. The SU applet can go fetched from here

2. Can't tell you what is right or incorrect: never fabricated apply of Magisk or TWRP.

Concluding edited past a moderator: May 24, 2021

• #10

i. You install matching SU applet by ways of ADB. The SU applet can become fetched from here

2. Can't tell you what is correct or wrong: never made use of Magisk or TWRP.

Fair enough on point 2

The SU from LineageOS not a problem to use on Samsung stock Rom? I hateful that SU applet non developed to be compatible with LineageOS only or something?

Whatever instruction on how to apply this SU applet will be useful. (I'thousand searching through the forum as well)

Deleted member 1890170

Invitee

• #11

Only to clarify things:
SU is a Linux command, Android is based on Linux kernel, hence SU applet compiled for mobile's CPU compages ever works, regardless of mobile's brand / model / Android release.

Every bit I already mentioned hither, you can install SU by means of a ADB command-sequence which typically looks like this

                                  adb disable-verity adb reboot adb beat out "mount -t car -o rw,remount /system" adb push <SU-BINARY-LOCATION-ON-PC-HERE> /organisation/bin adb vanquish "chown root:root /system/bin/su" adb shell "chmod 06755 /system/bin/su" adb shell "chcon '/system/bin/su' u:object_r:su_exec:s0"                                

Last edited by a moderator: May 24, 2021

• #12

Only to clarify things:
SU is a Linux command, Android is based on Linux kernel, hence SU applet compiled for mobile's CPU compages always works, regardless of mobile's brand / model / Android release.

Every bit I already mentioned hither, you can install SU by means of a ADB control-sequence which typically looks like this

                                  adb disable-verity adb reboot adb vanquish "mount -t auto -o rw,remount /organisation" adb push <SU-BINARY-LOCATION-ON-PC-Hither> /organisation/bin adb crush "chown root:root /system/bin/su" adb trounce "chmod 06755 /organization/bin/su" adb shell "chcon '/system/bin/su' u:object_r:su_exec:s0"                                

True, it'southward all Linux based, but thought the directories might be different manufacturer to manufacturer. With the verify functions and all... Didn't want to modify a wrong directory and get bricked.

Nice, thanks for the help and ADB commands. Besides just came across LADB (on-phone ADB beat out), will requite it a keep that.

Will update dorsum.

• #13

Rooting without unlocking bootloader only works on
4.2 jellybean
four.4 KitKat
five.0 lollipop
5.ane.1. lollipop
All of the other version of android volition not work considering in android 6 marshmallow google patched root without unlocking bootloader so this means if u are on Android half-dozen marshmallow it will not work likewise if u are on Android vi marshmallow and higher don't brother with kingroot or all of that one click root because that will not work I would recommend magisk to root your telephone

I'thousand on Android 11.
Ok, so I have to patch kick.img with magisk or magisk director (I don't know the departure)? On GitHub the latest version is but magisk v22.

Then to use magisk unlocking bootloader is required... I'll be keeping stock ROM. So will I exist able to relock bootloader afterwards patching and rooting?

Hope you lot can give me some insight on this. Would be good to learn.

• #xiv

Only to analyze things:
SU is a Linux command, Android is based on Linux kernel, hence SU applet compiled for mobile's CPU compages always works, regardless of mobile's brand / model / Android release.

As I already mentioned here, you can install SU by means of a ADB command-sequence which typically looks like this

                                    adb disable-verity adb reboot adb vanquish "mount -t auto -o rw,remount /system" adb push <SU-BINARY-LOCATION-ON-PC-Hither> /system/bin adb shell "chown root:root /arrangement/bin/su" adb shell "chmod 06755 /system/bin/su" adb shell "chcon '/system/bin/su' u:object_r:su_exec:s0"                                  

Can I install supersu.apk (root access manager) after this?

If I need to revert things back to how they were (unroot, enable dm-verity) ... How do I do that?

Last edited: May 25, 2021

Deleted member 1890170

Guest

• #15

Can I install supersu.apk (root access managing director) after this?

SuperSU APK is just like any other Android application. It only will properly work if SU is runing as Android service, means gets started at Android'south boot up

                                # su daemon service su_daemon /organisation/bin/su --daemon     seclabel u:r:sudaemon:s0     oneshot on property:persist.sys.root_access=i     start su_daemon                              

what requires Android'due south kicking file init.rc must got patched accordingly.

• #16

frequently conversing - with thoughts to this thread'south headline:

I am rooting the phone's Android products externally, unfastening its bootloader. Rooting Android but is combining a user-designated "superuser ( AKA motive )" toward Android.
Special purpose how? Somebody unlock bootloaders is to be capable of flashing system ROMS.

• #17

Merely to clarify things:
SU is a Linux control, Android is based on Linux kernel, hence SU applet compiled for mobile's CPU compages e'er works, regardless of mobile's make / model / Android release.

As I already mentioned here, yous can install SU by means of a ADB command-sequence which typically looks similar this

                                  adb disable-verity adb reboot adb shell "mount -t auto -o rw,remount /arrangement" adb push <SU-BINARY-LOCATION-ON-PC-HERE> /organisation/bin adb beat out "chown root:root /system/bin/su" adb shell "chmod 06755 /system/bin/su" adb shell "chcon '/system/bin/su' u:object_r:su_exec:s0"                                

I've only establish this thread and wanted to understand something. Does adb disable-verity piece of work without unlocking bootloader?

Do yous hateful that if you lot install su on the system via adb on the above sequence then the organization is substantially rooted no thing whether you lot unlock the bootloader or not?

Before information technology was mentioned that you need to run a service in order for the superuser apps to work and this requires the boot.img to exist modified and this needs the bootloader to exist unlocked. Will superuser apps like superuser apk work just with su on the organisation?

I mean tin can I just soft start the daemon with a terminal app without calculation it as a startup service?

Deleted member 1890170

Guest

• #18

Over again: Rooting Android is calculation an user named SUPERUSER to Android OS - not to get confused with Android's default user named root - an user who has elevated rights ( comparable to Administrator in Windows OS ).

The SuperSU app what y'all're referring to is a manager app that runs a database where apps which request superuser right are stored.

The SuperSu service ( read: sudaemond ) is a consummate other thing, it serves another purpose: information technology's needed to have SuperSU app working.

Final edited by a moderator: Nov 6, 2021

• #nineteen

Information technology's not possible to add together any binary or user or rooting app without unlocking your bootloader. All partitions except /data are not writable.

Deleted fellow member 1890170

Guest

• #20

More than nonsense is hardly possible.

Like threads

How To Root Phone Without Unlocking Bootloader,

Source: https://forum.xda-developers.com/t/questions-about-rooting-without-unlocking-bootloader.4281491/

Posted by: martineztherlon84.blogspot.com

Share this post