Did u have it connected to hotspot?
No does it need to be to work?
why shouldnât i run what it says on the wifi adb app?
Yes. Make a hotspot and connect your laptop and the headunit to it (can also just make a hotspot and use termux on the same device instead of a laptop).
Open that app, and with your other device, not the headunit, run what it says.
You should then have a shell. From there:
adb shell su -c id
I still have a feeling itâs rooted.
On my unit, thereâs no way to enable Developer options.
However, in the units settings there is an option to switch from Host mode to device mode.
After switching, adb worked from a PC, even without enabling usb debugging.
Got a root shell too. Neither Termux nor any other apps were able to get root access on the device itself.
According to Gemini this is common on aftermarket units. Itâs some sort of production root, if I recall correctly.
failed but plain su worked
Now what do I do?
Whatever you wanted to do in the first place
Wanted to edit Rom but to scared to brick without mtk
What would be the command to grant root access to fx?
It doesnât let me make tripleU MDM as device owner
This is where youâll have to do some tinkering
Dd everything first
Use the terminal, no apps will look for that su binary and it probably doesnât have support for it
can you give me a list of commands for all partitions
Before this you got a figure out a way to unlock the bootloader, or at least see that thereâs no real verification of partitions.
permission manager got root
Here is a list
adb shell ls -i /dev/block/by-name
10450 backup
9717 baseparameter
2631 boot
9709 cache
10454 dtbo
10446 frp
2624 jancar
10442 jansys
65 januser
9713 logo
10298 metadata
2620 metazone
57 misc
10438 mmcblk2
2638 mmcblk2boot0
2627 mmcblk2boot1
53 recovery
10458 security
10294 super
2635 trust
9705 uboot
61 userdata
9701 vbmeta
Whatâs the error you get setting and mdm
Also, using su to set?
adb reboot fastboot worked but afterwords the pc couldnât communicate
Tried both su and not
the error was unknown admin