about Tizen, SDK, etc...

[forhadaliBan]

Hey @adfree
you should try to change the path of ACL. Internal To External. It's Make About 600 MB Large File in System. Z2 N Z4 Has Get their Own Changing Path Future In Last Update . If this possible Maybe we can run Some Games And Apps Run Smoothly. I guess ! What you think ?

 

[adfree]

@forhadaliBan

I will try to check your idea...

Please remember I am not fastest...

So need some time...

Best Regards

 

[forhadaliBan]

@adfree Relax Sir
I am not telling you to do this work fast.
Give YourSelf Some Time to Do This

 

[Qiangong2]

Samsung has published the recent Tizen 5.5 kernel source for sc7730 devices. This will most likely work for the Z1 and Z3. I am in the process of compiling it for the Z2 and Z4.

It's not Android, but we could potentially get Tizen 5.5 and Tizen 6 on our devices!

 

[forhadaliBan]

It is really Worthy In end of 2019.

 certs.txt

ACL For Tizen 2.3.140
Or Andro-zen pro bla bla bla ?????

 

[forhadali]

Version Of Z1 Bangladesh

Edited

 

[adfree]

Please look at this post:
https://forum.xda-developers.com/showpost.php?p=71147844&postcount=393

Since around 4 yearS I have NO other solution as Computer + SDB ROOT ON


Summary...

Computer + SDB Tool = more access
NO Computer = NO way...

Sorry.

I have NO time yet... Nor in near future...

For me it is perfect working for my SM-Z130H and my SM-Z300H and my RD-PQ... if I use my Computer with SDB Tool.

I have checked my old rooted Version for Bangladesh:

BANGLADESH_ROOTed_ROOTFSonly_CPI1_SMz130_v1.zip

su Binary is inside... should work with PC.

Please don't blame me.
if you have no Computer...

Sorry I am not smart enough to bypass all s h it t y Security SH... from Samsung...

I hope you understand.

Best Regards

 

[forhadaliBan]

I Understand
Okay

 

[adfree]

D:\SDB\SDB260>sdb root on
* server not running. starting it now on port 26099 *
* server started successfully *
Switched to 'root' account mode

D:\SDB\SDB260>sdb shell
sh-3.2# cd /bin
sh-3.2# ls -a1l su
-rwsr-srwx 1 root root 31604 Feb  1  2017 su
sh-3.2#
sh-3.2# mount -vo remount,rw /
/dev/mmcblk0p24 on / type ext4 (rw)
sh-3.2# chmod -v 4755 su
mode of `su' changed to 4755 (rwsr-xr-x)
sh-3.2# ls -a1l
total 2764
drwxr-xr-x  2 root root   4096 Feb  1  2017 .
dr-xr-xr-x 21 root root   4096 Nov 11 06:40 ..
lrwxrwxrwx  1 root root      4 Sep 26  2016 awk -> gawk
-rwxr-xr-x  1 root root 528376 Jul  7  2016 bash
-rwxr-xr-x  1 root root  24080 Jul  7  2016 cat
-rwxr-xr-x  1 root root  56872 Jul  7  2016 chgrp
-rwxr-xr-x  1 root root  51440 Jul  7  2016 chmod
-rwxr-xr-x  1 root root  59752 Jul  7  2016 chown
-rwxr-xr-x  1 root root  81096 Jul  7  2016 cp
lrwxrwxrwx  1 root root     15 Sep 26  2016 cpio -> ../usr/bin/cpio
-rwxr-xr-x  1 root root  61420 Jul  7  2016 date
-rwxr-xr-x  1 root root  52564 Jul  7  2016 dd
-rwxr-xr-x  1 root root  47476 Jul  7  2016 df
-rwxr-xr-x  1 root root  15676 Mar  9  2016 dmesg
lrwxrwxrwx  1 root root      8 Sep 26  2016 dnsdomainname -> hostname
lrwxrwxrwx  1 root root      8 Sep 26  2016 domainname -> hostname
-rwxr-xr-x  1 root root  20304 Jul  7  2016 echo
lrwxrwxrwx  1 root root      4 Sep 26  2016 egrep -> grep
-rwxr-xr-x  1 root root  17160 Jul  7  2016 false
lrwxrwxrwx  1 root root      4 Sep 26  2016 fgrep -> grep
lrwxrwxrwx  1 root root     15 Sep 26  2016 find -> ../usr/bin/find
-rwxr-xr-x  1 root root  25416 Mar  9  2016 findmnt
-rwxr-xr-x  2 root root 224072 Mar  9  2016 gawk
-rwxr-xr-x  2 root root 224072 Mar  9  2016 gawk-3.1.5
-rwxr-xr-x  1 root root  59672 Mar  9  2016 grep
-rwxr-xr-x  1 root root     61 Mar  9  2016 gunzip
-rwxr-xr-x  1 root root  47688 Mar  9  2016 gzip
-rwxr-xr-x  1 root root   9148 Mar  9  2016 hostname
-rwxr-xr-x  1 root root   3089 Mar  9  2016 igawk
-rwxr-xr-x  1 root root  32476 Jul  7  2016 ln
-rwxr-xr-x  1 root root  39812 Jul  7  2016 login
-rwxr-xr-x  1 root root 118384 Jul  7  2016 ls
-rwxr-xr-x  1 root root  31900 Mar  9  2016 lsblk
-rwxr-xr-x  1 root root  28196 Jul  7  2016 mkdir
-rwxr-xr-x  1 root root  26712 Jul  7  2016 mknod
-rwxr-xr-x  1 root root   8184 Jul  7  2016 mktemp
-rwsr-xr-x  1 root root  54264 Mar  9  2016 mount
-rwxr-xr-x  1 root root  89352 Jul  7  2016 mv
-rwxr-xr-x  1 root root  83972 Mar  9  2016 netstat
-rwxr-xr-x  1 root root  72988 Mar  9  2016 ps
-rwxr-xr-x  1 root root  21404 Jul  7  2016 pwd
-rwxr-xr-x  1 root root  53040 Jul  7  2016 rm
-rwxr-xr-x  1 root root  19516 Jul  7  2016 rmdir
-rwxr-xr-x  1 root root  11128 Mar  9  2016 rpm
-rwxr-xr-x  1 root root  32064 Mar  9  2016 sed
lrwxrwxrwx  1 root root      4 Sep 26  2016 sh -> bash
-rwxr-xr-x  1 root root  22568 Jul  7  2016 sleep
-rwsr-xr-x  1 root root  31604 Feb  1  2017 su
-rwxr-xr-x  1 root root  17516 Jul  7  2016 sync
-rwxr-xr-x  1 root root 174628 Mar  9  2016 tar
-rwxr-xr-x  1 root root  49004 Jul  7  2016 touch
-rwxr-xr-x  1 root root  49612 Jul  7  2016 toybox
-rwxr-xr-x  1 root root  17160 Jul  7  2016 true
-rwsr-xr-x  1 root root  39544 Mar  9  2016 umount
-rwxr-xr-x  1 root root  19400 Jul  7  2016 uname
-rwxr-xr-x  1 root root     62 Mar  9  2016 zcat
sh-3.2# ls -a1l su
-rwsr-xr-x 1 root root 31604 Feb  1  2017 su
sh-3.2# exit
exit

D:\SDB\SDB260>sdb root off
Switched to 'developer' account mode

D:\SDB\SDB260>sdb shell
sh-3.2$ su
sh-3.2$ whoami
developer
sh-3.2$ su root
sh-3.2$ exit
exit

D:\SDB\SDB260>sdb shell
sh-3.2$ su
setgid: Operation not permitted
sh-3.2$ exit
exit

D:\SDB\SDB260>sdb root on
Switched to 'root' account mode

D:\SDB\SDB260>sdb shell
sh-3.2# mount -vo remount,rw /
/dev/mmcblk0p25 on / type ext4 (rw)
sh-3.2# cd /bin
sh-3.2# ls -a1l su
-rwxr-xrwx 1 root root 31604 Apr 22  2018 su
sh-3.2# chmod -v +sx su
mode of `su' changed to 6757 (rwsr-srwx)
sh-3.2# ls -a1l su
-rwsr-srwx 1 root root 31604 Apr 22  2018 su
sh-3.2# exit
exit

D:\SDB\SDB260>sdb root off
Switched to 'developer' account mode

D:\SDB\SDB260>sdb shell
sh-3.2$ su
sh-3.2$ whoami
developer
sh-3.2$ exit
exit

D:\SDB\SDB260>sdb root on
Switched to 'root' account mode

D:\SDB\SDB260>sdb shell
sh-3.2# cd /bin
sh-3.2# mount -vo remount,rw /
/dev/mmcblk0p25 on / type ext4 (rw)
sh-3.2# chmod -v 4755 su
mode of `su' changed to 4755 (rwsr-xr-x)
sh-3.2# exit
exit

D:\SDB\SDB260>sdb root off
Switched to 'developer' account mode

D:\SDB\SDB260>sdb shell
sh-3.2$ su
sh-3.2$ whoami
developer
sh-3.2$ su --root
su: unrecognized option '--root'
Usage: su [options] [LOGIN]

Options:
  -c, --command COMMAND         pass COMMAND to the invoked shell
  -h, --help                    display this help message and exit
  -, -l, --login                make the shell a login shell
  -m, -p,
  --preserve-environment        do not reset environment variables, and
                                keep the same shell
  -s, --shell SHELL             use SHELL instead of the default in passwd

sh-3.2$ su root
sh-3.2$ su app
Password:
crypt: Invalid argument
sh-3.2$ su system
Password:
crypt: Invalid argument
sh-3.2$ exit
exit

D:\SDB\SDB260>sdb root on
Switched to 'root' account mode

D:\SDB\SDB260>sdb shell
sh-3.2# su system
sh-3.2# whoami
root
sh-3.2# su -system
Cannot execute ystem: No such file or directory
sh-3.2# su --system
su: unrecognized option '--system'
Usage: su [options] [LOGIN]

Options:
  -c, --command COMMAND         pass COMMAND to the invoked shell
  -h, --help                    display this help message and exit
  -, -l, --login                make the shell a login shell
  -m, -p,
  --preserve-environment        do not reset environment variables, and
                                keep the same shell
  -s, --shell SHELL             use SHELL instead of the default in passwd

sh-3.2# exit
exit

https://gist.github.com/rossja/d65f6b31c8f47010700161bd90e24a6c

su Binary Download expired from this Link...

So I can not compare to see if I am toooooo dumb...

But for me this is NOT possible on my SM-Z130H nor on my SM-Z300H...

Maybe somebody could enlight my tiny stupid brain in 2020... why I can not su...

Still Computer + SDB:

sdb root on

This works fine. :good:

Type su in shell not work... :cyclops:

Best Regards

 

[Qiangong2]

https://gist.github.com/rossja/d65f6b31c8f47010700161bd90e24a6c

su Binary Download expired from this Link...

So I can not compare to see if I am toooooo dumb...

But for me this is NOT possible on my SM-Z130H nor on my SM-Z300H...

Maybe somebody could enlight my tiny stupid brain in 2020... why I can not su...

Still Computer + SDB:


This works fine. :good:

Type su in shell not work... :cyclops:

Best Regards

The way Tizen works, is that every command is checked against sdb which has a sort of "catalog" of permissable commands in regular, non root mode. No matter what you do, without recompiling sdb yourself, you can't use su from shell like Android can.

That's the only reason "sdb root on" is a command. It essentially "unlocks" the shell to use any command.

When you type "sdb root on", sdb searches for a valid su binary. When it finds it, it enables root access. However, this can only be done outside of the shell. When you enter the shell, it's akin to locking out what commands can be added and used.

You should be able to run su from shell if you rebuild a Tizen image for your device.

 

[adfree]

No matter what you do, without recompiling sdb yourself, you can't use su from shell like Android can.

Are you 100 % sure?

I mean I can do this with my Z1 since yearS on older Firmware as 2.4...

With Tizen 3 and 4 I can do this on my SM-R732 and my SM-R760...

1 User confirmed this on SM-R815U...

With modified rootfs.img...

I mean commercial rootfs.img...

Since few days/weeks I found solution to nuke stupid SMACK... to have access like on Combination Firmware.

For SM-Z130H no Tizen 2.4 Combination Firmware exists...
And for my SM-Z300H I am to lazy to flash and to compare...

But SDB Tool is the last thing... in this Security chain massaker...
ADB IMHO sent same ...

I was too lazy in all these years to check, what SDB/ADB sends to device... after:

adb root on
sdb root on

Best Regards

 

[Qiangong2]

Are you 100 % sure?

I mean I can do this with my Z1 since yearS on older Firmware as 2.4...

With Tizen 3 and 4 I can do this on my SM-R732 and my SM-R760...

1 User confirmed this on SM-R815U...

With modified rootfs.img...

I mean commercial rootfs.img...

Since few days/weeks I found solution to nuke stupid SMACK... to have access like on Combination Firmware.

For SM-Z130H no Tizen 2.4 Combination Firmware exists...
And for my SM-Z300H I am to lazy to flash and to compare...

But SDB Tool is the last thing... in this Security chain massaker...
ADB IMHO sent same ...

I was too lazy in all these years to check, what SDB/ADB sends to device... after:


Best Regards

Adb doesn't send anything. It doesn't have the root on command.

 

[forhadaliBan]

Android have two way to enable root.
1. Using 3rd party app like kingroot,kingoroot,etc
2. By flashing magskin or install

 su

You can run su from shell in android.
It no need special permission to run su in shell.

But tizen have !
Tizen is also a Linux os but either we can't use some command like linux. Like
RPM
It aslo require root for install packages.
Maybe Reason is security issues.
But a dead os still have hard Security Nice

And Anothe Reason is Tizen Community sucks

#Bad English
Sorry For That

 

[adfree]

Example from my SM-R760 with Tizen 4... modified commecial cr. Firmware...

C:\SDB>sdb root on
Switched to 'root' account mode

sh-3.2# cd /usr/bin
sh-3.2# ls -a1l su
-rw-rw-rw- 1 root root 20404 Jan 17 23:15 su
sh-3.2# chmod -v +sx su
mode of `su' changed to 6777 (rwsrwsrwx)
sh-3.2# exit
exit

C:\SDB>sdb root off
Switched to 'sdk user' account mode

C:\SDB>sdb shell
sh-3.2$ su
Password:
bash-3.2# whoami
[B]root[/B]

But this Trick not work with Tizen 2.4 and my SM-Z130H nor my SM-Z300H...

I was only able to do this with SM-Z130H on Tizen 2.3
Post from 2017... 3 years ago...
https://forum.xda-developers.com/showpost.php?p=71147844&postcount=393
Post from 2016...
https://forum.xda-developers.com/showpost.php?p=66799727&postcount=277

Sorry I am not smart enough to fullfill all dreams...

And thank you sooooooooooooooooooooooo much for all help...

Maybe somebody with Z2,Z3 or Z4 can check if Combination Firmware allow su from Shell...

I am tooo lazy to flash my SM-Z300H to check it self...

Best Regards
@forhadaliBan

I was NEVER able to su from app User...

In all my years of Tizen... from Handset alone impossible without doing more Security Hacking... SMACK crap... Sandbox kicking...

Edit 1.
Forgotten...

Tizen 3 4 5 5.5... higher as 2.4

C:\SDB>sdb shell
sh-3.2$ whoami
owner

 

[forhadaliBan]

Maybe somebody with Z2,Z3 or Z4 can check if Combination Firmware allow su from Shell...

And Maybe They Did It



First Of All Tell Me Can SDB Run Without Tizen Studio.
In case Without Android studio

 ADB

Run Smoothly.
Maybe SDB Is Different

 ls -a1l  bin/su

Doesn't Allow to Change The Permission in shell.

Best Regards @adfree
You Invented Some Amazing things for tizen and for us .
Win7 is Dead :'(
Maybe In Future you will be find some better way.

Try To Flash Z3 Firmware And Check .


Again tnx sir @adfree

 

[adfree]

Hmmm... if I look at my old post...

https://forum.xda-developers.com/showpost.php?p=72854079&postcount=460

device-sec-policy

Hmmmmmm... I would say this is again SMACK crap... IMHO...

Tooo long ago. I have forgotten if I have SM-Z300H Combination Firmware...

Somebody knows if SM-Z300H Combination firmware is leaked... somewhere... and maybe Filenames could help to search on my HDDs...

Best Regards

 

[forhadaliBan]

@adfree sir I found this
https://bit.ly/3aM6g82

 

[adfree]

Thanx, but still question:

Somebody knows if SM-Z300H Combination firmware is leaked...

I can not remember nor can find in Internet...

I mean not the Qualcomm SM-Z300F...

I have only SM-Z300H for easy testing...

Best Regards

 

[adfree]

@Qiangong2

You ever compiled the Platform stuff?


I mean /usr/apps...

Or you found rpm files?



Best Regards

 

[Qiangong2]

@Qiangong2

You ever compiled the Platform stuff?


I mean /usr/apps...

Or you found rpm files?



Best Regards

If you do the standard gbs build, it should build you the rpm files