futeko.com FORUM

Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: Pepetops on May 20, 2017, 11:46:06 AM

Title: script ROOT_SuperSU_v2.78_via_LAN
Post by: Pepetops on May 20, 2017, 11:46:06 AM

Hi,I do not speak / write German or Romanian so I write the question here:
I use linux and I want to modify this script written for windows, which is used to do root in my Q10pro.
There are some lines of the script that I do not understand and I would like someone to explain something to me, for example:

Code: [Select]

echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
echo +++                         Starte ADB...                            +++
echo +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
adb connect %var%:5555
adb root
adb remount
taskkill /f /im adb.exe
adb connect %var%:5555   <---WHY KILL ADB AND REPEAT COMMANDS AGAIN?
adb root
adb connect %var%:5555
adb remount

If I open a root console on my PC I suppose no need adb root command,isn't it?

If my Q10pro is not root,need this lines?:

Code: [Select]

db shell rm -f /system/bin/su
adb shell rm -f /system/xbin/su
adb shell rm -f /system/sbin/su
adb shell rm -f /vendor/sbin/su
adb shell rm -f /vendor/bin/su
adb shell rm -f /vendor/xbin/su
adb shell rm -f /system/xbin/daemonsu
adb shell rm -f /system/xbin/sugote
adb shell rm -f /system/xbin/sugote-mksh
adb shell rm -f /system/xbin/supolicy
adb shell rm -f /system/lib/libsupol.so
adb shell rm -f /system/lib64/libsupol.so
adb shell rm -f /system/bin/.ext/.su
adb shell rm -f /system/bin/install-recovery.sh
adb shell rm -f /system/etc/install-recovery.sh
adb shell rm -f /system/etc/init.d/99SuperSUDaemon
adb shell rm -f /system/etc/.installed_su_daemon
adb shell rm -f /system/app/Superuser.apk
adb shell rm -f /system/app/Superuser.odex
adb shell rm -rf /system/app/Superuser
adb shell rm -f /system/app/SuperUser.apk
adb shell rm -f /system/app/SuperUser.odex
adb shell rm -rf /system/app/SuperUser
adb shell rm -f /system/app/superuser.apk
adb shell rm -f /system/app/superuser.odex
adb shell rm -rf /system/app/superuser
adb shell rm -f /system/app/Supersu.apk
adb shell rm -f /system/app/Supersu.odex
adb shell rm -rf /system/app/Supersu
adb shell rm -f /system/app/SuperSU.apk
adb shell rm -f /system/app/SuperSU.odex
adb shell rm -rf /system/app/SuperSU
adb shell rm -f /system/app/supersu.apk
adb shell rm -f /system/app/supersu.odex
adb shell rm -rf /system/app/supersu
adb shell rm -f /system/app/VenomSuperUser.apk
adb shell rm -f /system/app/VenomSuperUser.odex
adb shell rm -rf /system/app/VenomSuperUser
adb shell rm -f /data/dalvik-cache/*com.noshufou.android.su*
adb shell rm -f /data/dalvik-cache/*/*com.noshufou.android.su*
adb shell rm -f /data/dalvik-cache/*com.koushikdutta.superuser*
adb shell rm -f /data/dalvik-cache/*/*com.koushikdutta.superuser*
adb shell rm -f /data/dalvik-cache/*com.mgyun.shua.su*
adb shell rm -f /data/dalvik-cache/*/*com.mgyun.shua.su*
adb shell rm -f /data/dalvik-cache/*com.m0narx.su*
adb shell rm -f /data/dalvik-cache/*/*com.m0narx.su*
adb shell rm -f /data/dalvik-cache/*Superuser.apk*
adb shell rm -f /data/dalvik-cache/*/*Superuser.apk*
adb shell rm -f /data/dalvik-cache/*SuperUser.apk*
adb shell rm -f /data/dalvik-cache/*/*SuperUser.apk*
adb shell rm -f /data/dalvik-cache/*superuser.apk*
adb shell rm -f /data/dalvik-cache/*/*superuser.apk*
adb shell rm -f /data/dalvik-cache/*VenomSuperUser.apk*
adb shell rm -f /data/dalvik-cache/*/*VenomSuperUser.apk*
adb shell rm -f /data/dalvik-cache/*eu.chainfire.supersu*
adb shell rm -f /data/dalvik-cache/*/*eu.chainfire.supersu*
adb shell rm -f /data/dalvik-cache/*Supersu.apk*
adb shell rm -f /data/dalvik-cache/*/*Supersu.apk*
adb shell rm -f /data/dalvik-cache/*SuperSU.apk*
adb shell rm -f /data/dalvik-cache/*/*SuperSU.apk*
adb shell rm -f /data/dalvik-cache/*supersu.apk*
adb shell rm -f /data/dalvik-cache/*/*supersu.apk*
adb shell rm -f /data/dalvik-cache/*.oat
adb shell rm -f /data/app/com.noshufou.android.su*
adb shell rm -f /data/app/com.koushikdutta.superuser*
adb shell rm -f /data/app/com.mgyun.shua.su*
adb shell rm -f /data/app/com.m0narx.su*
adb shell rm -f /data/app/eu.chainfire.supersu-*
adb shell rm -f /data/app/eu.chainfire.supersu.apk

Thanks

Title: Re: script ROOT_SuperSU_v2.78_via_LAN
Post by: pcristi on May 20, 2017, 01:12:58 PM

Script is not only on Q10/Q5 Pro with original HiMedia FW, can root many device with accept adb root command over ip.

Q10/Q5 Pro HiMedia FW are enough like that

Code: [Select]

adb connect %var%:5555
adb remount
If you try to root NFPRoot HImedia FW will need

Code: [Select]

adb connect %var%:5555
adb root
adb connect %var%:5555
adb remount
When try to root NFPRoot Egreat A10/A5 not always adb restating to root or adb see device offline

Code: [Select]

adb connect %var%:5555
adb root
adb connect %var%:5555
adb remount
taskkill /f /im adb.exe    <---WHY KILL ADB AND REPEAT COMMANDS AGAIN?
adb connect %var%:5555
adb root
adb connect %var%:5555
adb remount
Other option is to write proper routine to check adb device list...to lazy to do this.

2nd part not need you run clean FW, but is good practice didn't have to check what is status of device when scripts in run, easy to clean.

Title: Re: script ROOT_SuperSU_v2.78_via_LAN
Post by: Pepetops on May 20, 2017, 02:52:40 PM

Thank you so much for your explanation