GNUROOT PERMISION CELLPHONE

[metasploita]

Tanks the problem is when i try to open the /dev file with dir or ls command, I use chmod to give privileges, the user root not have permission to open this file.

[debiman]

that's kindof normal for the files in /dev.
and what does it have to do with a cellphone?
i think you need to provide a better problem description, if you want help. read the 1st link in my signature.

btw, cool username

[Funkygoby]

/dev is a directory
dir command doesn't exists

uname -a

[peter_irich]

NAME
4 dir - list directory contents
5
6 SYNOPSIS
7 dir [OPTION]... [FILE]...
8
9 DESCRIPTION
10 List information about the FILEs (the current directory by default).

[llivv]

metasploita <got-updates

devs put code in source so (insert adjective here) admins don't mess / things beyond pay grade,
until they have enough experience to know how much extra work will be made for all by changing permission,
of file/directory that are generated automatically by a daemon.

automagic can reduce work for everyone until,

until automagic compounds with interest.
/run
< 82
> 17
>> 2048

[metasploita]

Tanks llivv
Is there any way to modify the Daemons, release the source code, pay for a version with permissions, where I can see the GNUROOT source code and modify it, which part of the code should I modify ?, I must wait for a more free version, which is the solution ?

[llivv]

IF your question was answered please edit your first posts title adding (SOLVED)

ie GNROOT PERMISSION CELLPHONE (SOLVED)

[metasploita]

Is there any way to modify the Daemons, release the source code, pay for a version with permissions, where I can see the GNUROOT source code and modify it, which part of the code should I modify ?, I must wait for a more free version, which is the solution? Thanks when find the solution I will post the post as solved, I not find the daemon permission

[llivv]

systemd-udev

[debiman]

Is there any way to modify the Daemons, release the source code

yes.
linux is FOSS.

pay for a version with permissions

no.
linux is FOSS.

where I can see the GNUROOT source code and modify it, which part of the code should I modify ?, I must wait for a more free version, which is the solution? Thanks when find the solution I will post the post as solved, I not find the daemon permission

you're still not telling us anything about your problem.
what is GNUROOT?
and what cellphone? there's millions of different devices.

[metasploita]

GNUROOT is a aplication for android that enulate DEBIAN 8 SO, when i run KALILINUX in pc i have permission like root therefore i can install aplications, llivv say me a Daemon that start and give permission to the sistem im investigate configurate daemon and i talk you about this configurate Daemon, /etc/udev/udev.conf this udev provides a dynamic device directory containing only the files for actually present devices. It creates or removes device node files in the /dev directory, or it renames network interfaces. But i studyng how edit or change the permissions but i dont know how, i need edit /dev but i cant

[llivv]

GNUROOT is a aplication for android that enulate DEBIAN 8 SO, when i run KALILINUX in pc i have permission like root therefore i can install aplications, llivv say me a Daemon that start and give permission to the sistem im investigate configurate daemon and i talk you about this configurate Daemon, /etc/udev/udev.conf this udev provides a dynamic device directory containing only the files for actually present devices. It creates or removes device node files in the /dev directory, or it renames network interfaces.

gnuroot from what I gather so far is built to install linux on a phone without rooting the phone, ie it doesn't use root/super accounts.
One can get other apps to get root on the phone, but than you start messin with the fundamentals of the app.
The source is here
https://github.com/corbinlc/gnuroot
It's not a Debian program - neither is Kali
So this is not the forum to ask about either gnuroot or kali unless someone else in this forum has personal knowledge, sorry

But i studyng how edit or change the permissions but i dont know how, i need edit /dev but i cant

Not many users know how to create/modify /dev files
Learning how to make a character or block device is not trivial learning - you have to learn a lot before success.

Especially since /dev files are automatically generated - And -
the automagic that generates them gets more complex with every version release of udev in linux and whatever it is called in android,

more links to read
.https://android.stackexchange.com/quest ... ermissions
Not the answer you're looking for? Browse other questions tagged root-access or ask your own question.
https://android.stackexchange.com/quest ... oot-access

https://www.techrepublic.com/article/us ... id-device/

http://turbocontrol.com/gnuroot.htm

[debiman]

it seems op believes in the power of permissions - be root, and everything succeeds!
https://www.xkcd.com/149/
i am not so convinced.
also, they still didn't tell us what "CELLPHONE".
the previous poster linked an article that clearly says that gnuroot doesn't work beyond android 5.x.

[Pick2]

... i run KALI LINUX

That says it all right there
/end thread

[llivv]

Pick - I thought that after reading the OPost and user name.
A week after first reading the OP I finally joined in. anyways
I believe anyone that wanted to actually learn how to add a new device to a
Debian static /dev directory would have to go back at least 20 years to Sarge
to see how that process worked using MAKEDEV and using

Code: Select all

ls -la /dev

to see major, minors inline.

More can be learned by reading the kernel source doc under devices.txt
if there are any kernel monks fluent with interenals.

I also found a tutorial for udev rules that might be helpful to anyone with a
burning desire to chip away at the OS. It's a medium intensity tutorial, and no
guarantees how long it will remain useful, so be forewarned.
https://linuxconfig.org/tutorial-on-how ... s-in-linux

especially like debiman mentioned a few times above,
if anyone is using an old wheezy 2.6 kernel and/or has machine running
android with (a)new device(s) not recognised by the latest kernel.