Database Info

why not removing the camera sound and then flash the rom?

well we are all looking for a way to silence the camera and i wonder why not to open the rom file and remove the camera sound or replacing with a silent one ?

Within the Gear's rom in the standard-armv7l/usr/share/feedback folder there's a file called sound.xml.
In this file there's the following entry:
Code:
<sound>
<label>FEEDBACK_PATTERN_SCREEN_CAPTURE</label>
<data>/usr/share/feedback/sound/operation/shutter.ogg</data>
</sound>
By removing this entry I guess the shutter sound is also removed.

Corstian said:
Within the Gear's rom in the standard-armv7l/usr/share/feedback folder there's a file called sound.xml.
In this file there's the following entry:
Code:
<sound>
<label>FEEDBACK_PATTERN_SCREEN_CAPTURE</label>
<data>/usr/share/feedback/sound/operation/shutter.ogg</data>
</sound>
By removing this entry I guess the shutter sound is also removed.
Click to expand...
Click to collapse
i am just afraid that it will make error instead ...
but i can try maybe when i get some free time.|
I've already flashed a rom with Odin and still i get updates

lightdelegate said:
i am just afraid that it will make error instead ...
but i can try maybe when i get some free time.|
I've already flashed a rom with Odin and still i get updates
Click to expand...
Click to collapse
In the weekend I've been trying to compile this rom in which I didn't succeed yet. Once I can compile (hopefully after an Ubuntu reinstall) I'll give it a shot!

Corstian said:
In the weekend I've been trying to compile this rom in which I didn't succeed yet. Once I can compile (hopefully after an Ubuntu reinstall) I'll give it a shot!
Click to expand...
Click to collapse
thanks

So it is possible to modifiy the files and flash?
Why are poeple messing with hardware hacks when it seems to be so easy?
What's the catch?

is the rom still in tar format?
why not removing the shutter.ogg (or replace with a dummy file), re-tar and flash with odin? without the .md5 ending odin still flashes normally...
Sent from my Nexus 7 using XDA Premium 4 mobile app

If you root the Gear 2, there is an easier way of disabling Camera sounds:
http://www.tizenexperts.com/2014/06/hack-tizen-samsung-gear-2-gear-2-neo-get-root-access/
Rooting:
Instructions
Here are some instructions on how to Load into Odin and flash your device with the downloaded firmware
Download Odin 3.09, and extract it to its own folder
Download the rootfs.img file from the above links
Put your Gear 2 device into download mode
Launch Odin
Connect Smart watch to your PC
Make sure the settings are the default ones ie Auto Reboot and F. Reset Time selected
Select the AP Button
Navigate to where you downloaded the file and select it
Click on Start
Wait for it to finish.
In order to activate root you need the sdb.exe from Tizen-SDK, or equivalent file depending on your OS.
Click to expand...
Click to collapse
Disable camera sounds
sdb root on
sdb shell mount -o remount,rw /
sdb shell mv /usr/share/sounds/mm-camcorder/ /usr/share/sounds/mm-camcorder_bak/
sdb shell mv /usr/apps/com.samsung.w-camera-app/res/sounds /usr/apps/com.samsung.w-camera-app/res/sounds_bak
sdb shell mount -o remount,ro /
Click to expand...
Click to collapse

Installing busybox

To install busybox on a rooted gear 2, turn root on (sdb root on) and then push this package (download.tizen.org/snapshots/2.3-wearable/common/tizen-2.3-wearable_20140605.1/repos/tizen/armv7l/packages/armv7l/busybox-1.17.1-2.3.armv7l.rpm) to the device. Install the package (from a sdb shell on the watch) by typing "rpm -i busybox-1.17.1-2.3.armv7l.rpm".
This gets you VI (a CLI text editor) on the device. Very useful when editing xml and config files.

kylgore said:
To install busybox on a rooted gear 2, turn root on (sdb root on) and then push this package (download.tizen.org/snapshots/2.3-wearable/common/tizen-2.3-wearable_20140605.1/repos/tizen/armv7l/packages/armv7l/busybox-1.17.1-2.3.armv7l.rpm) to the device. Install the package (from a sdb shell on the watch) by typing "rpm -i busybox-1.17.1-2.3.armv7l.rpm".
This gets you VI (a CLI text editor) on the device. Very useful when editing xml and config files.
Click to expand...
Click to collapse
Awesome. Thanks jumping straight on it

This is very good. Thanks.
But I wonder; do we have a use for Busybox on the Gear 2 yet ?
Thx.

Hi, when I try any install, I get "installing package busybox-1.17.1-2.3.armv71 needs 188KB on the / filesystem"
I've tried putting the package on the "SD card" (storage for music, pictures etc.) but still nothing
You guys know any solutions?

Make sure root is on and that you mount the filesystem r/w (then be sure to mount r/o after)
sdb root on
sdb shell mount -o remount,rw /
for read-only------>
sdb shell mount -o remount,ro /

mrmrmrmr said:
This is very good. Thanks.
But I wonder; do we have a use for Busybox on the Gear 2 yet ?
Thx.
Click to expand...
Click to collapse
I'm serious: do we have a use for Busybox on Gear 2 ?
thx.

mrmrmrmr said:
I'm serious: do we have a use for Busybox on Gear 2 ?
thx.
Click to expand...
Click to collapse
I am just tinkering and exploring at this point. Other than that... no not really.

mrmrmrmr said:
I'm serious: do we have a use for Busybox on Gear 2 ?
thx.
Click to expand...
Click to collapse
I said this in my initial post. It provides VI. Without VI (or another text editor), there's no way to edit files on the device without a push/pull. Maybe you don't need that, but it's very helpful to me, and I assume to others.

SM-R600 Full Firmware for use with ODIN, repair and study

670 MB for download... for study...
Code:
AP_R600XXU1AQI8_usr.tar
BL_R600XXU1AQI8_usr.tar
CSC_OXA_R600OXA1AQI8_usr.tar
Download Link for OXA region... contains all CSC for SM-R600:
https://www.file-upload.net/download-12796748/R600XXU1AQI8_OXA.zip.html
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Still missing, maybe somebody can share the LDU XXX Version.
Thanx in advance.
Code:
COMBINATION-FT30_R600XXU1AQI4.tar
COMBINATION-FT30_R600XXU1AQI6.tar
LDU Live Demo Unit XXX
Code:
AP_R600[B][COLOR="Red"]X[/COLOR][/B]XXU1AQI6_usr.tar
BL_R600[COLOR="Red"][B]X[/B][/COLOR]XXU1AQI6_usr.tar
CSC_OXA_R600[B][COLOR="Red"]X[/COLOR][/B]OXA1AQI6_usr.tar
Best Regrds

What is tizen version

What is tizen version
Click to expand...
Click to collapse
In theory something with Tizen 3...
At the moment I am not 100 % sure if:
Code:
3.0.0.0
Maybe more something like this:
Code:
3.0.0.1
Best Regards

SM-R600 Bootloader...
R600XXU1AQI8
Code:
sboot.bin
cm.bin
Please ask before you try something "amazing"... and your Gear is dead...
OWN RISK!
For study... and maybe repair...
Best Regards

Meanhwile I have SM-R600 Firmware for study.. Thanx. :angel:
Next problem.
Old methods not work to unpack...
7zip nor ext4 unpacker work...
So they used something "new"...
Code:
nad_fw.bin
nad_refer.bin
In BL package... this 2 for me unknown files inside...
Maybe with some Google search I can find some usefull info...
Short XDA search...
https://forum.xda-developers.com/sitesearch.php?q=nad_fw.bin
https://forum.xda-developers.com/sitesearch.php?q=nad_refer.bin
Maybe this can lead to compatible Unpacker/Extractor...
Best Regards

For extraction I will try this... as other attempts failed...
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-extract-img-to-dump-t3673863
Will report if success...
Best Regards
Edit 1.
Attempt 1 fail...
SVAImgUnpack.exe ramdisk.img
Code:
SVAImgUnpack - Unpacker img to ext4. Version 2.1 from 30.04.2013
----------------------------------------------------------------
Source file: ramdisk.img (file size = 7.340.304 bytes)
Destination file: ramdisk.ext4.img
Unpacking ...
Header error: source file has wrong format! Program terminated.
Unpacking successfully done!
Press any key ...
Edit 2.
I can mount *.img files in Tizen Studio...
Emulator with Tizen 3 Mobile... as I need SD card feature... otherwise not enough space to mount and tar 1200 MB
Then simple "copy & paste"... with SDB
First I have waste my time with Wearable Image T3... and spent hours to realize that SD card option is not possible here...

No success with any "converter" Tools at the moment...
New idea is to mount in Tizen 3 Emulator... need some time for Copy & Paste...
Later more...
Meanwhile if sombody want take an look:
https://www.file-upload.net/download-12781791/CSC_OXA_R600OXA1AQI8_usr.tar.md5.zip.html
Only CSC + PIT inside...
I am toooo lazy to upload now... and it seems nobody else want R600 Firmware.
Best Regards

Code:
R600XXU1AQJ5
Seems updated to this Version...
Somebody knows the Changelog...
I am not able to find something similar like this...
http://doc.samsungmobile.com/SM-R760/CHC/doc.html
Not for XAR nor for DBT or other Sales Code...
Maybe depend on big or small letters... like here
http://doc.samsungmobile.com/sm-g930f/dbt/doc.html
Or Samsung work like this...
Ehne mehne mu und Du kriegst halt nix...
Best Regards

Oh, magic.
After 5 years of Development from Tizen 3.0 we reach:
Tizen 3.0.0.1
http://doc.samsungmobile.com/SM-R600/CHC/doc.html
Code:
R600XXU1AQJ5
Best Regards
P.S:
I have added Link in first post for Odin package...
Only as hint...

I downloaded COMBINATION-FT30_R600XXU1AQI6.tar.rar from some kind of free site, so 100% is not sure if this is really it. I will be grateful if anyone will check - https://www.dropbox.com/s/z6nvlob4f3ixoft/COMBINATION-FT30_R600XXU1AQI6.tar.rar?dl=0

Code:
COMBINATION-FT30_R600XXU1AQI6.tar.md5
:good:
Thanx for sharing.
I can not try self... as no SM-R600... but first look looks good.
Related to my first mistake with SM-R732... where I have first flashed the Live Demo Unit Firmware...
2 XX in Filename is correct for Retail device
3 XXX means "danger", because for LDU
Also no Rollback Prevention problem at the moment visible...
Code:
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI6
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI8
Both Firmware packages in same Software Revision. :good: :good:
So in theory...
We need only 1 brave tester.
I need some time to extract all files...
To check if Codes etc. maybe same or changed...
Best Regards

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-R600
SM-R600 Source for study available. :good:
Best Regards

I have extracted Combination Firmware in this way...
Still with help of Tizen Studio... Tizen 3 Mobile Emulator...
"Beta" Batch...
Code:
sdb root on
sdb push t3.tar /opt/media/SDCardC
sdb shell cd /opt/media/SDCardC
sdb shell tar -xvf t3.tar
sdb shell mkdir csc
sdb shell mkdir user
sdb shell mkdir ramdisk
sdb shell mkdir ramdisk-recovery
sdb shell mkdir system-data
sdb shell mkdir rootfs
sdb shell mount -t ext4 -o loop,rw user.img /opt/media/SDCardC/csc
sdb shell mount -t ext4 -o loop,rw user.img /opt/media/SDCardC/user
sdb shell mount -t ext4 -o loop,rw ramdisk.img /opt/media/SDCardC/ramdisk
sdb shell mount -t ext4 -o loop,rw ramdisk-recovery.img /opt/media/SDCardC/ramdisk-recovery
sdb shell mount -t ext4 -o loop,rw system-data.img /opt/media/SDCardC/system-data
sdb shell mount -t ext4 -o loop,rw user.img /opt/media/SDCardC/rootfs
tar -cvf r600v1.tar rootfs
tar -cvf r600v2.tar csc
tar -cvf r600v3.tar user
tar -cvf r600v4.tar ramdisk
tar -cvf r600v5.tar ramdisk-recovery
tar -cvf r600v6.tar system-data
rm t3.tar
sdb pull *.tar
Maybe someone find other Tool or method to extract Tizen 3 Firmware...
Best Regards

Woooah, seems I was drunken with my "Beta" Batch file... for extracting *.img
Few really bad "mistakes"...
I made it few times now with line by line...
As my batch not work proper..
Meanhwile SM-R600 got new update:
Code:
R600XXU1AQK4/R600OXA1AQK4
At the moment I can again not find up2date Changelog...
Best Regards

Code:
COMBINATION-FT30_R600XXU1[B]AQL1[/B].tar.md5
Meanwhile new Combination Firmware floating around...
Only as info.
Best Regards

adfree said:
Code:
COMBINATION-FT30_R600XXU1AQI6.tar.md5
:good:
Thanx for sharing.
I can not try self... as no SM-R600... but first look looks good.
Related to my first mistake with SM-R732... where I have first flashed the Live Demo Unit Firmware...
2 XX in Filename is correct for Retail device
3 XXX means "danger", because for LDU
Also no Rollback Prevention problem at the moment visible...
Code:
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI6
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI8
Both Firmware packages in same Software Revision. :good: :good:
So in theory...
We need only 1 brave tester.
I need some time to extract all files...
To check if Codes etc. maybe same or changed...
Best Regards
Click to expand...
Click to collapse
I HAVE the live demo version. Can I Flash regular version of tizen onto live demo unit with any of the zip files in this forum? I'm very familiar with flashing via odin, i just can't tell if any of these will work on my unit?

Thanks for all the work @adfree! I have the Canadian SM-R600 (R600XXU1AQK4) and was wondering if you have had any success yet changing the CSC? I saw you played an active part in accomplishing that on the S3.
I'm by no means proficient in programming, but quite familiar with rooting, sdb, odin, etc. Let me know if I can help.
Cheers!

@detjoe
I have no SM-R600 for own tests...
1 user told me via PM he tried COMBINATION-FT30_R600XXU1AQI6.tar.md5 long time ago.
With no success in changing CSC...
He wrote...
Flashing no problem... Combination Firmware work... Code is same...
But after Reboot old CSC is back...
I have only idea it is maybe related to Product Code...
Maybe security increased... or maybe only no luck.. or maybe error in Combination Firmware...
Meanwhile also CQL1 as Combination Firmware "available":
Code:
[COLOR="Red"]COMBINATION-FT30_R600XXU1AQI4.tar.md5[/COLOR]
[COLOR="Green"][B]COMBINATION-FT30_R600XXU1AQI6.tar.md5[/B][/COLOR]
[COLOR="Red"]COMBINATION-FT30_R600XXU1AQL1.tar.md5[/COLOR]
Green means we have for free download... :good: and tested by 1 user
Red is only on paid sites...
Maybe with other Combination Firmware more luck...
Maybe if somebody is willing to test...
Own risk!
Best Regards
Edit 1.
SDB Tool is for instance here... with tiny Instruction how to connect via WiFi...
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330

@mmafighter077
I wrote you PM...
No idea if you allready tried?
Best Regards

Hoping this works....
adfree said:
@mmafighter077
I wrote you PM...
No idea if you allready tried?
Best Regards
Click to expand...
Click to collapse
I'm hoping you guys get this to work.....I have a German version of the watch, but need it to be set for the US. I had the same issues as reported above with it swapping back to the original CSC.
Any update on this for you guys?

How to install tpk directly on the gear sport?

I have put tpk file on the device but when I click to install it (as android) appears : Error occurred: No matched application found.
How Can I solve it?
It's important to install it directly from gear sport and not using a pc software.
Thank you
Sofia

No idea what you trying to achieve...
But...
1.
You are familiar with SDB or ADB Tool?
Code:
[B]sdb install [/B]blahblaTPKorblablaWGT.blabla
2.
Because you can enter device over WiFi from ADB Android APK...
So you could try to fire up few Commands...
Look here:
https://forum.xda-developers.com/showpost.php?p=75833894&postcount=7
I have success with this nice APK:
https://play.google.com/store/apps/details?id=com.cgutman.androidremotedebugger
So in theory... no PC... but you need ADB on Phone...
Sorry, we have no Developers... which creates something usefull for free...
In theory it is not Rocket Science to create Installer APK on Phone...
Best Regards

@sofiaxxx
You tried?
I am too lazy to check it...
As I am using PC... and "sdb install"...
https://developer.tizen.org/ko/foru...t/how-install-tpk-within-device?langswitch=ko
Something like this could work:
Code:
/usr/bin/pkgcmd -q -i -t tpk -p <tpk file name>
Best Regards

How do I temporarily root a samsung device running android 9 without twrp recovery?

I have used magisk to patch the file and android platform tools (fastboot or stuff like that) but it does not work. I dont want to install twrp as i dont really trust custom recoveries as much and i dont want to use odin for the same reason. Is this impossible or is there a way but i am just doing it incorrectly. Please reply asap!

Never installed Magisk nor TWRP, why should I have done it?
To answer your question: A temporary root can get achieved by putting a suitable su into directory /data/local/tmp and making it executable.
https://forum.xda-developers.com/attachments/su-binaries-zip.5566949/

xXx yYy said:
Never installed Magisk nor TWRP, why should I have done it?
To answer your question: A temporary root can get achieved by putting a suitable su into directory /data/local/tmp and making it executable.
https://forum.xda-developers.com/attachments/su-binaries-zip.5566949/
Click to expand...
Click to collapse
The data partition is not accessible without having root first. How are they to place su in data partition to gain temp root without first gaining root to place su in data partition? How can they root the device by using a method that requires root in the first place to achieve what you are telling them?

I think the code
Code:
adb push <PATH-TO-SU-ON-PC> /data/local/tmp
always works , because this path ( /data/local/tmp ) is always present and writable on Android dev device and Emulator.
At least it always worked for me since I'm rooting Android this way.

xXx yYy said:
I think the code
Code:
adb push <PATH-TO-SU-ON-PC> /data/local/tmp
always works , because this path ( /data/local/tmp ) is always present and writable on Android dev device and Emulator.
At least it always worked for me since I'm rooting Android this way.
Click to expand...
Click to collapse
do i unroot my device by rebooting it?
p.s. will doing this solution create a possibility of bricking my device?

Technically seen you can't root / unroot a device, but only Android OS.
As with Android OS root ( sometimes called superuser ) is the same as Administrator with Windows OS. Simply adding an user with elevated privileges never will brick an Android device.
Become familiar what root is the world of Linux OS - take note that Android OS merely is a port of it.

xXx yYy said:
Technically seen you can't root / unroot a device, but only Android OS.
As with Android OS root ( sometimes called superuser ) is the same as Administrator with Windows OS. Simply adding an user with elevated privileges never will brick an Android device.
Become familiar what root is the world of Linux OS - take note that Android OS merely is a port of it.
Click to expand...
Click to collapse
so running that command will give me legit root privileges and i can do the things an admin can do without any malware or damage?

Droidriven said:
The data partition is not accessible without having root first. How are they to place su in data partition to gain temp root without first gaining root to place su in data partition? How can they root the device by using a method that requires root in the first place to achieve what you are telling them?
Click to expand...
Click to collapse
so should i really use magisk to root my device?

moutsu said:
so should i really use magisk to root my device?
Click to expand...
Click to collapse
No, try what was suggested by placing su in the data/local/tmp. If that doesn't work, try using magisk to root your device.

xXx yYy said:
I think the code
Code:
adb push <PATH-TO-SU-ON-PC> /data/local/tmp
always works , because this path ( /data/local/tmp ) is always present and writable on Android dev device and Emulator.
At least it always worked for me since I'm rooting Android this way.
Click to expand...
Click to collapse
I've never seen a device rooted by such simple means, in my experience, it has always required root to even access data partition, especially if trying to push/pull files to/from data via adb.
I mean, if it were really that easy, why would all these rooting tools snd methods that exist on XDA have ever been needed to be created?
What devices have you rooted using this method? Can you provide information that explains and confirms what you say?

Hmmmm...
Short checked on my SM-R860 Android 11...
Code:
freshbs:/ $ cd /data/local/tmp
freshbs:/data/local/tmp $ ls
freshbs:/data/local/tmp $ ls -a1l
total 6
drwxrwx--x 2 shell shell 3452 2022-03-25 01:20 .
drwxr-x--x 4 root root 3452 2022-03-25 01:20 ..
Need more time or drinks to place something here...
Waiting for other results...
Best Regards

@Droidriven
Fellow member @adfree has proven that even with Android 11 directory /data/local/tmp worlwide exists and is writeable.
Sometimes it really makes sense to understand what OP wants to achieve: He just wants to know how Android can be temporarily rooted.

xXx yYy said:
@Droidriven
Fellow member @adfree has proven that even with Android 11 directory /data/local/tmp worlwide exists and is writeable.
Sometimes it really makes sense to understand what OP wants to achieve: He just wants to know how Android can be temporarily rooted.
Click to expand...
Click to collapse
I do need to know how an android can be temporarily rooted so I can give certain apps on my phone root access to recover some stuff I accidentally deleted. However, I do need a bit of clarification on what su file I need to put into the directory as the filed you linked was a zip file.
I would also like a method on how to unroot my device.

Dear moutsu...
IMHO instead blabla... IMHO it makes sense to start from scratch with FULL infos.
I can see only bla bla Samsung Device...
Please give full details...
A
Model Name...
Example:
SM-G920F is Android 7 for instance...
B
Is Phone alive... then give full details about Firmware Version.
Easiest way for most infos...
Type:
*#1234#
Type or make Photo or Screenshot...
Best Regards

@xXx yYy
Thank you very much. But...
I clicked through your profile and find some more puzzle parts of your idea...
Learning to root my old Galaxy S4
I have an old Samsung Galaxy S4. It's been off the network for a while and its system clock has drifted. However, adb works and I can use the old phone as a sandbox environment to learn about low level Android fundamentals. I would like to learn...
forum.xda-developers.com
After this I was drunken enough to try few things with my SM-R860...
WITHOUT success...
Later I will add my ADB output... for better understanding...
IMHO I am not total Noob in Rooting something...
Also I have "some" experiences in recover halfdead devices to backup beloved data...
I am sure you have forgotten about Samsung additional Security check... like Knox crap etc...
So my conclusion...
Your method is good to know...
But chance for success in "newer" Samsung devices is not 100 %...
Maybe you can give Samsung model name... where this work?
I could check SM-G920F with Android 7 just for fun... if I have time...
Thanx in advance.
Best Regards

regardless it is writeable to adb shell only (uid 2000), chown is forbidden anyway. even if you set SUID bit that wouldn't make much sense in /data/local/tmp
furthermore, even if you could place su binary in /system (which requires unlocked bootloader + dm-verity patch) it still requires privileged daemon in background where su want connect apps (but not exist).
so this method never worked, except for some ancient android devices where remount /system was possible from adb root.
and we haven't spoke about selinux, yet
Magisk does all this, but requires* unlocked bootloader - which triggers factory reset. So unless you have some nice exploit like dirty-cow or mtk-su, temporary root is simply impossible.
edit: TWRP is not able to decrypt samsung encryption btw. So if you want have access to userdata partition on locked bootloader the only way would be (samsung signed) so called "combination ROM" (with same bootloader level) to be flashed from Odin via HOME_CSC or heimdall.
if your device is ancient old you might lucky bootloader is unlocked, userdata partition is not encrypted at all, and ROM is just signed with test keys. in that case you can flash anything on recovery partition. philz touch recovery even provided flashable zips that signed with test keys, these zips can be flashed straight from stock recovery without PC. I remember temporary zips exist, that only boot into custom recovery without actually installing it.
edit2: *except some Mediatek devices with AVBv1 where one can flash magisk patched boot.img on locked bootloader

My last 2 cents here ( I no longer participate this thread ):
The su ( read: switchuser ) command is used to run an Android system function as a different user. It is the easiest way to switch or change to the administrative account ( read: superuser ) in the current logged in session.
Most versions of Android disable the superuser ( mostly mistakenly called root user - take note that root user in Android is the user with ID 0 who is by default present on all Android versions, is the user of session when Android gets started ) account by default making the system more secure. But, this also restricts the Android user from running specific system related commands.
Using su to temporarily act as a superuser allows you to bypass this restriction and perform system related tasks with different users.
The synthax of su command is
Code:
su [options] [username [[arguments]]
If a username isn't specified, su defaults to the superuser. Now, the logged-in user can run all system commands. This will also change the home directory and path to executable files.
If the su is used to temporarily act the logged-in user as superuser then the su binary can be located anywhere in Android's filesystem, e.g. /data/local/tmp, /storage/emulated/0, etc.pp, it must not be located in Android's system partition.

xXx yYy said:
My last 2 cents here ( I no longer participate this thread ):
Click to expand...
Click to collapse
yes, that's maybe better. teach yourself about android first. android is not linux
What special privileges "/system/xbin/su" does have w.r.t. root access?
This answer says: Because of the way directory/file permissions are configured on Android, you need to have the su binary on your /system partition in order for it to work. Putting elsewhere...
android.stackexchange.com

what is your current bootloader level? combination ROM is available (haven't checked these download links)
https://www.samsungfirmwares.info/samsung-sm-j415gn-combination-firmware-file-rom
my expectation ro.debuggable=1 is enabled
adb root will work on eng build

aIecxs said:
yes, that's maybe better. teach yourself about android first. android is not linux
What special privileges "/system/xbin/su" does have w.r.t. root access?
This answer says: Because of the way directory/file permissions are configured on Android, you need to have the su binary on your /system partition in order for it to work. Putting elsewhere...
android.stackexchange.com
Click to expand...
Click to collapse
Yeah, I get where they were coming from but.....
Nah. It just doesn't work that way for everybody. Like all things android, it really just depends on what device you have and how crappy its hardware/software and security is. Lower end/cheap and old stuff doesn't have as much time invested in making them secure to save on development and distribution costs.
Unfortunately, Samsung just isn't one of those brands that are easily rooted these days, unless you buy specific models with specific firmware/binary combinations.