Is there any way to get root access on Q10 pro running 7.0 Nougat? (solved)

[Pebert]

I originally posted this on the "HiMedia Q5/Q10 4K3D (2014 Generation)" board. But there's more activity on this one, so I thought I should repost it here instead.

Hi,

This is kind of a dumb question. How do I root my Himedia Q10 pro? It's running Android 7.0 nougat.
I have done a few Google searches leading me to forum posts. Most of wich are from 2016.
So far, none of them has worked for me.

Is your Himedia box rooted? If so, how did you do it?

[Phil181]

Not sure why you have a need to root the Q10 Pro but there is a link and information on the full Backup thread here:
http://www.futeko.com/newforum/index.php?topic=1616.msg13230#msg13230

[pcristi]

This part of output not help.
Did you input correct IP without 0, something like: 192.168.10.11?
If still not work post connect output until "Installieren ROOT..."

[Pepetops]

Hi:
This->
cannot stat 'su': No such file or directory
cannot stat 'su': No such file or directory
cannot stat 'su': No such file or directory
cannot stat 'su': No such file or directory
cannot stat 'sugote-mksh': No such file or directory

seems the files su and sugote-mksh isn't in your path.
When you open ROOT_SuperSU_v2.78_via_LAN.rar must create a dir and copy all files inside.
You can see:
99SuperSUDaemon
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
busybox
.installed_su_daemon
install-recovery.sh
ROOT_via_LAN_5.1.1.bat
su
sugote-mksh
Superuser.apk
SuperuserPro.apk

Like you see, su and sugote-mksh is in the same dir than adb.exe.
I not use win but this I guess it should work

[pcristi]

@Pepetops, @Pebert script not need run as administrator and connection output is like that

Code: [Select]

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++                         Starte ADB...                            +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.10.11:5555
error: device not found
SUCCESS: The process "adb.exe" with PID 13512 has been terminated.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.10.11:5555
adbd is already running as root
already connected to 192.168.10.11:5555
remount succeeded
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++                         Starte ROOT...                            +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++                            Klarlack                               +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++                      Installieren ROOT...                         +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
3425 KB/s (133472 bytes in 0.038s)
4171 KB/s (133472 bytes in 0.031s)
3590 KB/s (133472 bytes in 0.036s)
2833 KB/s (133472 bytes in 0.046s)
3198 KB/s (157488 bytes in 0.048s)
3971 KB/s (6488979 bytes in 1.595s)
3889 KB/s (51777 bytes in 0.012s)
0 KB/s (2 bytes in 0.003s)
205 KB/s (629 bytes in 0.002s)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++                 ROOT erfolgreich abgeschlossen.                   +++
+++             Dein Androide wird jetzt neu gestartet.               +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++             Du kannst dieses Fenster nun mit der                  +++
+++             Tastenkombination Strg-C schliessen.                  +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Can see batch run too fast error: device not found and didn't get connection after adb root, important is to see remount succeeded before " Starte ROOT".

LE:
Bad output when script run as administrator and box is not get rooted.

Code: [Select]

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++                      Installieren ROOT...                         +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
cannot stat 'su': No such file or directory
cannot stat 'su': No such file or directory
cannot stat 'su': No such file or directory
cannot stat 'su': No such file or directory
cannot stat 'sugote-mksh': No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
chmod: /system/xbin/su: No such file or directory
chmod: /system/xbin/daemonsu: No such file or directory
chmod: /system/xbin/sugote: No such file or directory
chmod: /system/xbin/sugote-mksh: No such file or directory
cannot stat 'Superuser.apk': No such file or directory
cannot stat 'SuperuserPro.apk': No such file or directory
chmod: /system/app/Superuser/Superuser.apk: No such file or directory
cannot stat '.installed_su_daemon': No such file or directory
chmod: /system/etc/.installed_su_daemon: No such file or directory
cannot stat 'install-recovery.sh': No such file or directory
ln: cannot create hard link from '/system/etc/install-recovery.sh' to '/system/bin/install-recovery.sh': No such file or directory
chmod: /system/etc/install-recovery.sh: No such file or directory
/system/bin/sh: /system/xbin/su: not found
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++                 ROOT erfolgreich abgeschlossen.                   +++
+++             Dein Androide wird jetzt neu gestartet.               +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++             Du kannst dieses Fenster nun mit der                  +++
+++             Tastenkombination Strg-C schliessen.                  +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This happens because when is run as administrator file are search on %SYSTEMROOT%\System32

[Pebert]

@pcristi
Jesus Christ, it worked! Thank you. I really appreciate your help.
I feel a little stupid for not trying to root without administrator.