Database Info

[BlueStacks Beta for Mac OS X] Getting root access - Experimental

Hi guys, i tried to root Bluestacks Apps Player Beta for Mac OS X on Windows by using a method similar to the one used to root BS for Windows.
But unfortunately i am not able to test the modded files as i do not actually own a Mac OS X device, and i am not familiar with the OS either.
So i am asking, any volunteer here willing to help me test this experimental modded files?
How to use
1) Download BlueStacks AppPlayer Beta .dmg for Mac OS X & install it.
2) Download modded files provided below, make sure the targeted version is same as your installed version.
3) Extract the downloaded zip and use the modded files to replace the following folders:
Code:
~/Library/BlueStacks App Player/Android/Root.sparsefs/
~/Library/BlueStacks App Player/Android/Prebundled.sparsefs/
~/Library/BlueStacks App Player/Android/Data.sparsefs/
~/Library/BlueStacks App Player/Android/SDCard.sparsefs/
Downloads & Changelogs:
Code:
[URL="http://goo.gl/wJYSR"][SIZE="3"]BSRoot_0.3.6.102d.zip[/SIZE][/URL] (99.88 MB, Pass: [COLOR="Red"][email protected][/COLOR], Last Update: [COLOR="Red"]03/04/2013[/COLOR])
~ Target: BlueStacks for Mac OS X v[URL="http://goo.gl/ILhtK"]0.3.6.102[/URL] Only (Released: 21/03/2013)
+ Allow /system rw
+ su (standalone/on the fly)
+ Google Play v3.10.14
+ Google Contacts/Calendar Sync
+ Flash Player v11.1
+ Holo Launcher v2.0.2 Free
+ Terminal Emulator v1.0.52 OS
- Most bloatware
Notes:
- By replacing above folders, your existing settings & data will be gone, you are advised to create a backup before trying the mod.
* Please note that all version prior to the 03/04/2013 update probably will not work, try the latest version.
* If you tried please at least COME BACK TO VOTE so that i can know how it goes. Thank you!

-Reserved-

I think this worked, still trying to find a way to test the "rooted-ness" of it. Do you know where bluestacks puts the apps it installs from the market? /data seems to be empty.
---------- Post added at 04:58 PM ---------- Previous post was at 04:41 PM ----------
typing su into terminal gets me a segmentation fault
SuperSu hangs or doesn't run.
ESFile Explorer can't use it's "root" features. (Test Fails)

efdisastet said:
I think this worked, still trying to find a way to test the "rooted-ness" of it. Do you know where bluestacks puts the apps it installs from the market? /data seems to be empty.
typing su into terminal gets me a segmentation fault
SuperSu hangs or doesn't run.
ESFile Explorer can't use it's "root" features. (Test Fails)
Click to expand...
Click to collapse
Hi, Thanks for the feedback.
Without SuperSU working properly, terminal is running as app user thus you will not be able to view contents of /data/ as the folder is owned by 'system'.
Not sure why SuperSU is not working. Anyway, I have updated the files to use Superuser 3.2 instead of SuperSU, now with the updated files,
Superuser can be uninstalled easily, and if the superuser still causing problem, try uninstall it & run su without the apk installed.
Appreciate if you can retry the new file & also provide me the output for 'mount'. Thank you.

codelover said:
Hi, Thanks for the feedback.
Without SuperSU working properly, terminal is running as app user thus you will not be able to view contents of /data/ as the folder is owned by 'system'.
Not sure why SuperSU is not working. Anyway, I have updated the files to use Superuser 3.2 instead of SuperSU, now with the updated files,
Superuser can be uninstalled easily, and if the superuser still causing problem, try uninstall it & run su without the apk installed.
Appreciate if you can retry the new file & also provide me the output for 'mount'. Thank you.
Click to expand...
Click to collapse
Superuser app opened, but then closed on its own before I could check the settings.
I cleared data and then it seemed to stay open, so that I can go through the settings.
here's the result of su (still Segmentation fault)
and then mount
(sorry that it's a picture, copy seems to be an option, but can't find a way to paste.)
why does xda resize the pictures so small?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Re: [Emulator][BlueStacks Beta for Mac] Getting root access - Testers wanted
Would love to try this, codelover, but am wondering if you are testing in your own environment first, or are you expecting us to QA it? Don't get me wrong... I really appreciate you taking the lead on this, I just need to understand what my effort and interest level need to be. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium

efdisastet said:
Superuser app opened, but then closed on its own before I could check the settings.
I cleared data and then it seemed to stay open, so that I can go through the settings.
here's the result of su (still Segmentation fault)
and then mount
Click to expand...
Click to collapse
Thanks! Now i know that /system can be mounted rw, one step forward. Next step is to find a working copy of su then we are done.
Can you confirm the Segmentation fault still appear after the apk been removed/uninstalled? One more thing, can you test run su after cd to /sdcard?
Just checked the alpha root by @bitstra, looks like they faced the same problem with superuser apk, so they have su working alone without the apk, maybe i will get you a copy of the su to test.
Btw do you have adb for Mac? Might need it to push su to BS for testing.

meatlocker said:
Would love to try this, codelover, but am wondering if you are testing in your own environment first, or are you expecting us to QA it? Don't get me wrong... I really appreciate you taking the lead on this, I just need to understand what my effort and interest level need to be. Thanks.
Click to expand...
Click to collapse
Hi meatlocker, Thank you for your interest. The answer is no, i have no chance to test it because i do not actually own a Mac.
But i have been working with BS for Windows for months that i am pretty sure Mac version can be rooted too.
I am just trying to help, it's really up to Mac users effort if they really want to see it get rooted.
The more feedback the faster it can be done. If i got a Mac that would be easier since i got several test cases that i can run on my own.
For now, everything is based on my assumption.

codelover said:
Thanks! Now i know that /system can be mounted rw, one step forward. Next step is to find a working copy of su then we are done.
Can you confirm the Segmentation fault still appear after the apk been removed/uninstalled? One more thing, can you test run su after cd to /sdcard?
Just checked the alpha root by @bitstra, looks like they faced the same problem with superuser apk, so they have su working alone without the apk, maybe i will get you a copy of the su to test.
Btw do you have adb for Mac? Might need it to push su to BS for testing.
Click to expand...
Click to collapse
yup, I've got adb installed and it see bluestacks, haven't tried to run any commands or anything
still get the Segmentation Fault and never get a typical su request popup for any app.
uninstalled superuser.
tried su in terminal, still Segmentation fault
installed SuperSu from play store
same results... app didn't run very well... tried to update itself and failed.
uninstalled
installed superuser (3.1.3?) from the Play store
took some screenshots (looked kinda hopeful?)
still same errors in terminal, no access to /data

efdisastet said:
installed SuperSu from play store
same results... app didn't run very well... tried to update itself and failed.
uninstalled
installed superuser (3.1.3?) from the Play store
took some screenshots (looked kinda hopeful?)
still same errors in terminal, no access to /data
Click to expand...
Click to collapse
You cannot install Superuser/SuperSU directly from market because it will install an arm version of the binary instead of the x86 that we need.
Now we need to identify which su binary version works with BS for Mac.
Please download the attached su-test.zip that contains various versions of su, extract to adb folder and then run the following commands:
Code:
adb push su-test /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su*
adb shell /data/local/tmp/su-3.1-x86 -v
adb shell /data/local/tmp/su-3.1.1-x86 -v
adb shell /data/local/tmp/su-3.2-x86 -v
adb shell /data/local/tmp/su-bin-3.1 -v
adb shell /data/local/tmp/su-1.25 -v
adb shell /data/local/tmp/su.x86 -v
adb shell /data/local/tmp/su.orig -v
* Also try to run above su without -v
We are expecting su to returns a version number or 'permission denied' message from a working copy, instead of segmentation fault.
Please let me know which version works. I think we can finalize this soon. Thank you again.

Re: [Emulator][BlueStacks Beta for Mac] Getting root access - Testers wanted
Also, how can we get into the contents of the Android disk image files on a Mac to extract android files, etc?
And how much space do we have in the simulated Android to install apps?

Code:
adb push su-test /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su*
adb shell /data/local/tmp/su-3.1-x86 -v
[COLOR="Red"]returned 3.1[/COLOR]
adb shell /data/local/tmp/su-3.1.1-x86 -v
[COLOR="red"]returned Segmentation fault[/COLOR]
adb shell /data/local/tmp/su-3.2-x86 -v
[COLOR="red"]returned Segmentation fault[/COLOR]
adb shell /data/local/tmp/su-bin-3.1 -v
[COLOR="red"]hung[/COLOR]
adb shell /data/local/tmp/su-1.25 -v
[COLOR="red"]hung[/COLOR]
adb shell /data/local/tmp/su.x86 -v
[COLOR="red"]returned Segmentation fault[/COLOR]
adb shell /data/local/tmp/su.orig -v
[COLOR="red"]returned su: permission denied[/COLOR]
* Also try to run above su without -v
[COLOR="red"]same results as above except that I got Segmentation fault on the ones that hung with -v[/COLOR]

efdisastet said:
Code:
adb shell /data/local/tmp/su-3.1-x86 -v
[COLOR="Red"]returned 3.1[/COLOR]
.....
adb shell /data/local/tmp/su.orig -v
[COLOR="red"]returned su: permission denied[/COLOR]
Click to expand...
Click to collapse
Definately a good news! I will try to rebuild Root.sparsefs to include both working copies of su-3.1 & su.orig.
But if i am not mistaken su.orig only works alone thus not supporting Superuser apk for confirmation.
EDIT: Files updated, download HERE.
CHANGES: Using su.orig copy without any Superuser apk.
NOTE: Might need to replace all new .sparsefs files instead of just Root.sparsefs.
Kinda weird as all su in su-test can run in BS for Windows except su.orig that returned Seg. fault.
Anyway, hope to hear some good news soon.

I replaced the files and kill Bluestacks, then I re-open Bluestacks .... NOTHING HAPPENED, my data and apps still there, and NO ROOT. Why?

nudawa said:
I replaced the files and kill Bluestacks, then I re-open Bluestacks .... NOTHING HAPPENED, my data and apps still there, and NO ROOT. Why?
Click to expand...
Click to collapse
1) Make sure you are using the required version, as these rooted files only works for v0.3.6.102.
2) Once you have replaced Data & SDCard, non of your existing apps should remain; If the apps still there you probably did it wrong.
3) Make sure you close your Bluestacks before replacing those files.
* Please note that the 'rooted files' mentioned above are 4 folders that contains 2 files in each folder.

codelover said:
Definately a good news! I will try to rebuild Root.sparsefs to include both working copies of su-3.1 & su.orig.
But if i am not mistaken su.orig only works alone thus not supporting Superuser apk for confirmation.
EDIT: Files updated, download HERE.
CHANGES: Using su.orig copy without any Superuser apk.
NOTE: Might need to replace all new .sparsefs files instead of just Root.sparsefs.
Kinda weird as all su in su-test can run in BS for Windows except su.orig that returned Seg. fault.
Anyway, hope to hear some good news soon.
Click to expand...
Click to collapse
did you want me to run some more tests?
so far all I've done is load the new files, open terminal, and try su: got permission denied

efdisastet said:
did you want me to run some more tests?
so far all I've done is load the new files, open terminal, and try su: got permission denied
Click to expand...
Click to collapse
Have you tried executing 'su' from adb instead of Terminal?
I am not sure how the included su.orig from alpha should behave as i got segfault here on Windows.
Unlike the newer SuperSU that works without apk, the su-3.1-x86 that worked for you during the test needs superuser apk,
but non of the apks i tested here work with that binary (All hung), kinda weird, until we have a working su+apk, other apps cannot gain root.
So i was thinking maybe we should try other superuser app, like the opensource ClockworkMod Superuser since it support x86 too.
Please download the attached su to test, let's see whether this one still causing segfault or not.
Code:
adb push su /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/su -v
As usual, we are expecting su to return some version info.
As i don't think it's a good idea to keep asking you to download & test a new 100M file for something unsure, i provide you an alternative:
By replacing with this modded initrd.img (~/Library/BlueStacks App Player/AppBundle/Contents/Android/initrd.img), if this work (hopefully), it will:
- Create the following public accessible folder if not exists: /data/root
- Create the following test files: /data/root/test
- Change ownership, group & permissions needed for su for all files found inside /data/root/ on every boot.
Click to expand...
Click to collapse
Once replaced initrd.img, reboot and if you see a new file /data/root/test and it's owned by root then you can proceed to the below tests, otherwise useless.
Code:
1) Install ClockworkMod [URL="https://play.google.com/store/apps/details?id=com.koushikdutta.superuser"]Superuser[/URL] or download [URL="http://download.clockworkmod.com/apks/Superuser.apk"]here[/URL].
2) adb push su /data/root/su
3) Restart Bluestacks to get the permissions needed by su.
4) Open terminal & type the following command: /data/root/su # Should get a prompt
* Note that you will be asked to update su binary but you won't be able to do so at the moment. leave that first.
If non of the above work i guess the only option is to test all su binaries and apks, which is very time-consuming.
But i guess i am to giving up instead as it's too hard for me to debug without actually owning a Mac to test it.

codelover said:
Have you tried executing 'su' from adb instead of Terminal?
Click to expand...
Click to collapse
tried running it from an adb shell, still permission denied
I am not sure how the included su.orig from alpha should behave as i got segfault here on Windows.
Unlike the newer SuperSU that works without apk, the su-3.1-x86 that worked for you during the test needs superuser apk,
but non of the apks i tested here work with that binary (All hung), kinda weird, until we have a working su+apk, other apps cannot gain root.
So i was thinking maybe we should try other superuser app, like the opensource ClockworkMod Superuser since it support x86 too.
Please download the attached su to test, let's see whether this one still causing segfault or not.
Code:
adb push su /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/su -v
As usual, we are expecting su to return some version info.
Click to expand...
Click to collapse
tried this: segmentation fault
As i don't think it's a good idea to keep asking you to download & test a new 100M file for something unsure, i provide you an alternative:
By replacing with this modded initrd.img (~/Library/BlueStacks App Player/AppBundle/Contents/Android/initrd.img), if this work (hopefully), it will:
Once replaced initrd.img, reboot and if you see a new file /data/root/test and it's owned by root then you can proceed to the below tests, otherwise useless.
Code:
1) Install ClockworkMod [URL="https://play.google.com/store/apps/details?id=com.koushikdutta.superuser"]Superuser[/URL] or download [URL="http://download.clockworkmod.com/apks/Superuser.apk"]here[/URL].
2) adb push su /data/root/su
3) Restart Bluestacks to get the permissions needed by su.
4) Open terminal & type the following command: /data/root/su # Should get a prompt
* Note that you will be asked to update su binary but you won't be able to do so at the moment. leave that first.
If non of the above work i guess the only option is to test all su binaries and apks, which is very time-consuming.
But i guess i am to giving up instead as it's too hard for me to debug without actually owning a Mac to test it.
Click to expand...
Click to collapse
did all that. /data/root exists and seems writable (though trying to do an ls in /data still gives me permission denied)
but /data/root/su still gave me segmentation fault...
which version was that? Which versions did we get to give us a version number the other day?

efdisastet said:
tried running it from an adb shell, still permission denied
/data/root exists and seems writable (though trying to do an ls in /data still gives me permission denied) but /data/root/su still gave me segmentation fault...
which version was that? Which versions did we get to give us a version number the other day?
Click to expand...
Click to collapse
It was su-3.1-x86 that i got it from here but the site is down at the moment. You can still find the binary on my previous post, inside su-test.zip.
With that version i managed to get root with adb, but without a working apk you cannot gain root from other apps since it was designed to act like that.
But what makes me wonder is that the su.orig that worked without apk (anyone confirm?) on alpha supposed to work on this beta too.
Now that /data/root/ is working as expected, it's so much easier for you to test the binaries, just push to /data/root/ and reboot to get the required permissions.

codelover said:
It was su-3.1-x86 that i got it from here but the site is down at the moment. You can still find the binary on my previous post, inside su-test.zip.
With that version i managed to get root with adb, but without a working apk you cannot gain root from other apps since it was designed to act like that.
But what makes me wonder is that the su.orig that worked without apk (anyone confirm?) on alpha supposed to work on this beta too.
Now that /data/root/ is working as expected, it's so much easier for you to test the binaries, just push to /data/root/ and reboot to get the required permissions.
Click to expand...
Click to collapse
/data/root/ may be working as expected, but there still seems to be a "su" in the path somewhere, whose permissions are denied. Will that cause problems
I put the 3.1 file from the su-test folder into /data/root, restarted bluestacks, and then went to terminal, I've attached a screenshot of those results, including calling just "su" to note the difference
Maybe if I had a better handle on what we wanted all the permissions to be and where we wanted this executable su to be, and what su an app/apk like superuser tries to use, I could help more.

[ROOT available] [18-01-2015] Acer Liquid S1 / S510 / A10 with KK ROM!

Hi all,
*Q&A Thread is here*
Automatic process:
Please use the root from scratch method (only on UNIX!) from the Acer Iconia Toolkit thread
Manual process:
I have succeeded to root Acer Liquid S1 (S510 / A10). In the Acer Iconia Toolkit thread @Optimissimus99 mentioned to use the MTK Logger when using a Kitkat ROM. Using @vache's S1 root sources I figured out how root was done with JB using the Network Utility, so I tried doing the same steps using the MTK Logger.
Requirements:
Acer Liquid S1 (S510 / A10)
Being able to follow procedure to the step
Have an Ubuntu installation (I used 14.10)
Post screenshots, clear steps and results when asking for help
Getting root can be achieved with these steps:
Copy or download a busybox file (I used the one from the Iconia Toolkit) to your /sdcard
Using MTK Logger Util
Open engineering mode (for instance with MTK Engineering Mode)
Swipe to Log and Debugging screen
Open MTKLogger
Click on Settings
Click Run Command and execute the following commands:
cp /sdcard/busybox /data/local/tmp
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234
Using Terminal
ls -la /data/local/tmp/busybox
This should show correct execute permissions on busybox
/data/local/tmp/busybox telnet 127.0.0.1 1234
This should open Telnet correctly
cat /proc/dumchar_info | grep "android"
This should show the size of your system image. In my case:
"android 0x0000000040000000 0x0000000005d00000 2 /dev/block/mmcblk0p5”
so quickly calculating (using the code from Vache’s S1 Root tool)
l_seekBlocks = systemEndAddr / 4096; var endA = addrs[2]; endAddr = Convert.ToInt64(endA, 16); 0x0000000005d00000 97517568/4096 = 23808
l_countBlocks = systemStartAddr / 4096; var startA = addrs[1]; startAddr = Convert.ToInt64(startA, 16); 0x0000000040000000 1073741824/4096 = 262144
dd if=/dev/block/mmcblk0 bs=4096 skip=23808 count=262144 | gzip >/storage/sdcard1/system.img.gz
This should create your gzipped ROM dump on the external sdcard.
Within Ubuntu
Transfer the system.img.gz file to Ubuntu
Transfer extracted SuperSU (I used UPDATE-SuperSU-v2.40.zip)
Run the following code:
Code:
gunzip system.img.gz
sudo mkdir /media/iconia
sudo mount -o loop system.img /media/iconia
sudo mv /media/iconia/etc/install-recovery.sh /media/iconia/etc/install-recovery_original.sh
sudo mkdir /media/iconia/bin/.ext
sudo chmod 0777 /media/iconia/bin/.ext
sudo cp UPDATE-SuperSU-v2.40/common/Superuser.apk /media/iconia/app/Superuser.apk
sudo cp UPDATE-SuperSU-v2.40/common/install-recovery.sh /media/iconia/etc/install-recovery.sh
sudo cp UPDATE-SuperSU-v2.40/armv7/su /media/iconia/xbin/daemonsu
sudo cp UPDATE-SuperSU-v2.40/armv7/su /media/iconia/xbin/sugote
sudo cp UPDATE-SuperSU-v2.40/armv7/su /media/iconia/xbin/su
sudo cp UPDATE-SuperSU-v2.40/armv7/su /media/iconia/bin/.ext/.su
sudo cp /media/iconia/bin/mksh /media/iconia/xbin/sugote-mksh
sudo cp UPDATE-SuperSU-v2.40/armv7/supolicy /media/iconia/xbin/supolicy
sudo cp UPDATE-SuperSU-v2.40/armv7/libsupol.so /media/iconia/lib/libsupol.so
sudo chmod 0644 /media/iconia/app/Superuser.apk
sudo chmod 0755 /media/iconia/etc/install-recovery.sh
sudo chmod 0755 /media/iconia/xbin/daemonsu
sudo chmod 0755 /media/iconia/xbin/su
sudo chmod 0755 /media/iconia/bin/.ext/.su
sudo chmod 0755 /media/iconia/xbin/sugote
sudo chmod 0755 /media/iconia/xbin/sugote-mksh
sudo chmod 0755 /media/iconia/xbin/supolicy
sudo chmod 0644 /media/iconia/lib/libsupol.so
sudo ln -s /media/iconia/etc/install-recovery.sh /media/iconia/bin/install-recovery.sh
sudo umount /media/iconia
sudo rm -rf /media/iconia
mv system.img systemrooted.img
gzip systemrooted.img
Check for errors - if there is any, fix them
Next steps is to reload the system image with the following command:
copy systemrooted.img.gz to device
start mtklogger (see above 2.3 / 2.4)
start telnetdaemon (see above 2.5.3)
start terminal (see 3)
start telnet (see 3.2)
Run the command:
/data/local/tmp/busybox zcat /storage/sdcard1/systemrooted.img.gz | dd of=/dev/block/mmcblk0 bs=4096 seek=23808 count=262144
As I do not have much time, I am not sure when I can do this... will post progress in this thread.
Next steps in the development:
Add Xposed Framework
Thanks go to @vache @paugustin @Shreps @Optimissimus99 for providing some of the above info and helping me with this device!
Regards,
Nika.

Here's some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You have done the hardest part, just need to push the su daemon service for KK ?
Envoyé de mon A1-840FHD en utilisant Tapatalk

Just in case anyone reads this thread and decides to try it on their own - the system.img wasn't mountable (yet). Looks like I used seek= instead of skip= when creating the new image... will try again later....

Yeah, rooting works!
Check first post for details...

Nice!!! Realy like your work So we now have root on Acer Liquid S1! Will there be a quick way to root it?
with a kinda batch tool for instance?

ARRRDJ said:
Nice!!! Realy like your work So we now have root on Acer Liquid S1! Will there be a quick way to root it?
with a kinda batch tool for instance?
Click to expand...
Click to collapse
Oh yeah, we sure will. I'll contact @entonjackson to know whether we can add it to his toolkit and @Chainfire to know whether we are allowed to include SuperSU in a kit this way...

nikagl said:
Oh yeah, we sure will. I'll contact @entonjackson to know whether we can add it to his toolkit and @Chainfire to know whether we are allowed to include SuperSU in a kit this way...
Click to expand...
Click to collapse
Nice!! Finally, root for S1
Will you keep us up to date with the latest developments? I cannot wait to run Xposed

ARRRDJ said:
Nice!! Finally, root for S1
Will you keep us up to date with the latest developments? I cannot wait to run Xposed
Click to expand...
Click to collapse
Sure. I will need @entonjackson for that though, otherwise I'll have to rewrite his code to suite S1, use the MTKLogger and add SuperSU. Adding Xposed is a good idea too - the problem with the /system on this device is that it's locked and we cannot unlock it. So adding stuff (or removing for that matter) always requires to use an existing /system dump and restore it to the device using dd. Recovery too, will only allow installation of signed zips and as we don't have the right keys, we won't be able to use (or change) it... In the end, doing a root from scratch will always require either Ubuntu (to do it with the ROM you have on your device) or restore a system.img from another device... It requires Ubuntu btw, because in Ubuntu you can mount a system.img and easily change it, which is not feasible from DOS/Windows...
So... for the time being, let's wait for @entonjackson and if he doesn't have the option, I'll try to write something. Just keep in mind I am not a developer, I can follow procedures and hack my way into existing stuff, but writing from scratch remains a bridge too far...

nikagl said:
Sure. I will need @entonjackson for that though, otherwise I'll have to rewrite his code to suite S1, use the MTKLogger and add SuperSU. Adding Xposed is a good idea too - the problem with the /system on this device is that it's locked and we cannot unlock it. So adding stuff (or removing for that matter) always requires to use an existing /system dump and restore it to the device using dd. Recovery too, will only allow installation of signed zips and as we don't have the right keys, we won't be able to use (or change) it... In the end, doing a root from scratch will always require either Ubuntu (to do it with the ROM you have on your device) or restore a system.img from another device... It requires Ubuntu btw, because in Ubuntu you can mount a system.img and easily change it, which is not feasible from DOS/Windows...
So... for the time being, let's wait for @entonjackson and if he doesn't have the option, I'll try to write something. Just keep in mind I am not a developer, I can follow procedures and hack my way into existing stuff, but writing from scratch remains a bridge too far...
Click to expand...
Click to collapse
Okay, let's hope @entonjackson can help! Oehw that's sad. So it's impossible to root this phone on the 'normal' way? Is it restricted in the software or in the hardware?
But once you've rooted it, can you use Xposed (or another rootapp), without having to restore a systemdump file?
Ubuntu is not a problem, since I develop in Ubuntu
No problem! I've a lot of respect that you came so far without having a lot of experience

ARRRDJ said:
Okay, let's hope @entonjackson can help! Oehw that's sad. So it's impossible to root this phone on the 'normal' way? Is it restricted in the software or in the hardware?
But once you've rooted it, can you use Xposed (or another rootapp), without having to restore a systemdump file?
Ubuntu is not a problem, since I develop in Ubuntu
No problem! I've a lot of respect that you came so far without having a lot of experience
Click to expand...
Click to collapse
It's in the software/signing of the zips. The keys are unavailable for "normal" people like us. Just Acer has them I guess.
Yes, as soon as Xposed is integrated, you can use it. With the integration I am a bit worried to do it though. I have looked at the current release of Xposed (de.robv.android.xposed.installer_v33_36570c) and it requires me to replace /system/bin/app_process with the one from Xposed. My S1 does not have USB access anymore so I am very hesitant to replace a file like that. If it gets into a bootloop, I won’t be able to recover it…
Also, the update-binary that Xposed uses to integrate itself into the framework replaces that app_process file, but also expects certain configuration (/data/data/de.robv.android.xposed.installer) of the APK to be available. I am afraid that the apk needs to be installed before actually introducing the new app_process file. As the installation of the APK is not part of /system and therefore the /data folders will not be created, I wonder how it behaves if the new file is introduced in the new /system...hopefully it won't cause bootloops....
Regards,
Nika.

I tried adding Xposed by changing the app_process file but it didn't work. I used the following commands:
Code:
sudo cp de.robv.android.xposed.installer_v33_36570c.apk /media/iconia/app/
sudo cp -a /media/iconia/bin/app_process /media/iconia/bin/app_process.orig
sudo cp de.robv.android.xposed.installer_v33_36570c/assets/arm/app_process_xposed_sdk16 /media/iconia/bin/app_process
sudo chmod 0755 /media/iconia/bin/app_process
It does see the new file version installed but Xposed is not running. Asked in some threads for extra help. Also no response yet from @entonjackson, so asked in the Iconia thread whether there's others that can help

nikagl said:
I tried adding Xposed by changing the app_process file but it didn't work. I used the following commands:
Code:
sudo cp de.robv.android.xposed.installer_v33_36570c.apk /media/iconia/app/
sudo cp -a /media/iconia/bin/app_process /media/iconia/bin/app_process.orig
sudo cp de.robv.android.xposed.installer_v33_36570c/assets/arm/app_process_xposed_sdk16 /media/iconia/bin/app_process
sudo chmod 0755 /media/iconia/bin/app_process
It does see the new file version installed but Xposed is not running. Asked in some threads for extra help. Also no response yet from @entonjackson, so asked in the Iconia thread whether there's others that can help
Click to expand...
Click to collapse
Ah okay, unfortunately!! I cant wait to run xposed! I hope you'll get some support from members with more experience, because I think we're really close to a more easier rooting way
Let me know if you make some progress

ARRRDJ said:
Ah okay, unfortunately!! I cant wait to run xposed! I hope you'll get some support from members with more experience, because I think we're really close to a more easier rooting way
Let me know if you make some progress
Click to expand...
Click to collapse
So do I and trust me - I tried it all. Also tried it on another device, it will simply not start and I don't know why
Regards,
Nika.

progress?
Any progress yet?

ARRRDJ said:
Any progress yet?
Click to expand...
Click to collapse
Nope, just root works. If you want I can add it to the rootfrom scratch method of the toolkit, but Xposed won't work. Simply do not get any help from anywhere to fix this and spent hours (if not days!) troubleshooting it, so i have given up...

thanks it's a wonderful job anyway u really deserve respect! :highfive:

Make sure to monitor the following thread for new versions:
http://forum.xda-developers.com/showthread.php?t=2240029
I am not yet sure when I get to make one, it's almost holiday week here in NL and with that and the preparations for it I don't have much time... more news soon.

I have created the first Acer Liquid S1 version of the toolkit. Let me know what you think.

First of all thank you very much for your efforts, I just downloaded your toolkit but it says "put prerooted system.img.gz... " etc. Question is where do I find prerooted system.img.gz?

[COMPLETE GUIDE]Root HD7/8/10(6th Gen 2016) and replace with SuperSU

FOR 2016(6th GEN) ON 5.3.1 AND 5.3.1.1 ONLY: Works on HD7, HD8 and HD10
You can downgrade from 5.3.2 by adb sideload the 5.3.1.1 bin file.
DO NOT downgrade from 5.3.2.1!! Hard-brick attention!!
This guide requires some ADB skills, read more from the forum, install it from here
Enable ADB and install apps from other sources in Developer Options
Download Kingoroot PC version at www.kingoapp.com or google mirror
Root your Kindle using Kingoroot, then reboot your device
Download a file explorer apk (ie. ES File Explorer) and sideload install the apk to your kindle
Download SuperSU apk at APKPure, but DON'T install it first
Download the attachment "Kingo.to.SuperSU" below then unzip and paste into your kindle, ie /sdcard/Kingo.to.SuperSU
Run ADB Shell and type
Code:
su
mount -w -o remount /system
Keep the root-accessed ADB shell open, then remove root by using Kingoroot
(If your kindle reboot at this step, you need to re-root it and try the above steps again)
In the ADB shell type
Code:
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
Still keep that root-accessed ADB shell opened, copy the SuperSU apk into your kindle and install it using the file explorer, DO NOT OPEN IT.
In the ADB shell type
Code:
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku
rm -rf /sdcard/Kingroot
(1 error with "No such file or directory" is okay I think)
Run SuperSU and update binary, choose the "normal" one, then it should ask you to reboot your kindle
Open up SuperSU and go to setting
Set the "Default Access" as [Grant]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Due to unknown reason, kindle cannot prompt the "Asking for root access", this step is to allow all access for all apps.
Install Root Checker and confirm you have root, run ADB shell to confirm you can su
Remove Kingolink and that Kingo battery app from kindle
Uninstall Kingo from PC via manual unins000.exe inside install directory in programs(x86)
ALL DONE! You may then want to install google play, do all the pm disable for OTA, firelauncher, and other amazon services you don't want.
References:
[Index] Amazon Fire HD 8 and HD 10 (5th Gen/2015)
[Working]Root Kindle Fire HD8 6th Gen
Tips, Tricks, and the Root!
[HOW-TO] Install Google Play Store (Fire OS 5.3.1.1) (No Root/ADB)
[Script] Replace KingoRoot with SuperSU
Credits:
@coltxL2717
@chemie99
@2ig2ag
@smokejumper76
@phpbb88 ME

phpbb88 said:
Code:
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku
rm -rf /sdcard/Kingroot
[*]Run SuperSU and update binary then it should ask you to reboot your kindle
[*]Open up SuperSU and go to setting
Click to expand...
Click to collapse
Getting error at Step 11:
After entering
rm /system/bin/install-recovery.sh
getting
No such file or directory
Then when updating binaries, SuperSU says "Installation successful! Reboot your device." On reboot, says that binaries are not installed and the app closes itself. Also, when initially updating SuperSU binaries, which option is to be chosen? The first "Normal" or the second "Custom/TWRP."
Here is my full log:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 5542
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
rm: /system/bin/install-recovery.sh: No such file or directory
1|[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU # reboot

imadiamond said:
Getting error at Step 11:
After entering
rm /system/bin/install-recovery.sh
getting
No such file or directory
Then when updating binaries, SuperSU says "Installation successful! Reboot your device." On reboot, says that binaries are not installed and the app closes itself. Also, when initially updating SuperSU binaries, which option is to be chosen? The first "Normal" or the second "Custom/TWRP."
Here is my full log:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 5542
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
rm: /system/bin/install-recovery.sh: No such file or directory
1|[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU # reboot
Click to expand...
Click to collapse
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary

Thanks for making this clear and concise guide! Well done.

phpbb88 said:
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary
Click to expand...
Click to collapse
Did cache wipe/format and reset to factory settings via device recovery (powering on and holding volume button.)
Went through the process again, and THOUGHT it worked, even though I got the same "No such file or directory" error. I didn't reboot on Step 12 and went into SuperSU setings to "Grant." Got Root Checker. Had root. Rebooted and opened Root Checker and had no root. So--
1) still getting same "No such file" error: how can I reset the device "clean" without that new .bin? Isn't there a way to "clean" the OS already on the device? On 5.3.1.1 On device did "wipe data/factory reset" then "wipe cache partition" and have also done them in the opposite order to make sure.
2) On step 12 do you reboot the device like SuperSu says, or do you just go straight into the settings. I was rebooting the device at this point for 3 or 4 tries. The last two times I did not and went straight into settings. Still same error of "No such file or directory." The file IS in the Kingo.to.SuperSU folder though, even downloaded and unzipped the attachment a few times.

Could I also install a customrom after root? with one?

meikschlenther said:
Could I also install a customrom after root? with one?
Click to expand...
Click to collapse
Not at this time... There are no ROMs as of yet, and if I'm not mistaken we would need a custom recovery and our bootloader is still locked.

imadiamond said:
Did cache wipe/format and reset to factory settings via device recovery (powering on and holding volume button.)
Went through the process again, and THOUGHT it worked, even though I got the same "No such file or directory" error. I didn't reboot on Step 12 and went into SuperSU setings to "Grant." Got Root Checker. Had root. Rebooted and opened Root Checker and had no root. So--
1) still getting same "No such file" error: how can I reset the device "clean" without that new .bin? Isn't there a way to "clean" the OS already on the device? On 5.3.1.1 On device did "wipe data/factory reset" then "wipe cache partition" and have also done them in the opposite order to make sure.
2) On step 12 do you reboot the device like SuperSu says, or do you just go straight into the settings. I was rebooting the device at this point for 3 or 4 tries. The last two times I did not and went straight into settings. Still same error of "No such file or directory." The file IS in the Kingo.to.SuperSU folder though, even downloaded and unzipped the attachment a few times.
Click to expand...
Click to collapse
Please download the official 5.3.1.1 bin, wipe cache, factory reset, then sideload the bin through recovery mode and follow the guide step by step strictly.
edited: please have a look at here, I somehow worked with 1 error, which is likely the "rm /system/bin/install-recovery.sh" command.

phpbb88 said:
Please download the official 5.3.1.1 bin, wipe cache, factory reset, then sideload the bin through recovery mode and follow the guide step by step strictly.
edited: please have a look at here, I somehow worked with 1 error, which is likely the "rm /system/bin/install-recovery.sh" command.
Click to expand...
Click to collapse
First problem was even though previously all drivers loaded and I was able to root/re-root and navigate adb.... when booting the device into recovery mode? Tablet not recognized by computer. Extremely frustrating. Read and read and read.... and finally came across something from @smokejumper76 -----answer was in Device Manager, tablet was showing up as KFGIWI with the error that drivers were not installed. Did "manually install drivers" "Search online" does not work) and chose ADB Composite Device, and now tablet is recognized in recovery mode.
Issue NOW is the process gets halfway through installation and then force closes with
E: failed to verify whole-file signature
E: signature verification failed
Man, I am ticked. What now? Been reading for the past hour++. People elsewhere are saying to change the .bin extension to .zip, but I haven't seen that here on the XDA forum.
---------- Post added at 01:48 AM ---------- Previous post was at 01:11 AM ----------
Install from ADB complete: went through. After multiple tries, did 2 things at once so not sure which one it was
1) ran cmd prompt as Administrator
2) deleted all 5.3.1.1 bin files from computer, just in case what was gotten previously was corrupt, and redownloaded fresh file onto the ADB computer, instead of the copy and paste version from another computer

Thanks for making this guide! Worked perfect 1st time on my hd8 2016. Used rootjunky supertool to disable ota, install nova, disable ads Lockscreen, install Google play.
Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.
Thanks again
From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.

I hope all you guys are also donating some bux to Kingoroot (I did).
We want to keep those geniuses happy and cranking out rooting updates for the v5.3.2.x builds!

Thanks so much for the guide. It was pretty easy to get through!
I have Nova Launcher running now and it is way better.
However, Auto Rotate screen isn't working quite right. If it is in Portrait, it will flip to landscape if I turn the tablet, but then it gets stuck in landscape which is the wrong landscape that I need for my Fire cover/stand.
Anyone else experiencing this?

Dumbest question:
the root is supposed to stay after turning the tablet off and on again, right?
I say this because went through the whole process successfully. New .bin. No errors on any commands. SuperSU installed binaries and then downloaded Root Checker and verified. Then verified su in adb shell. Then did pm disable of amazon apps and services,
and then turned tablet off and back on and Root Checker says NO ROOT. Root is supposed to stay, correct??? Or is it to just get all of the Amazon items off and customize tablet. Have rooted at least 8 or 9 devices, LG, Samsung, HTC etc, and this one has been the absolute _____ .

el7145 said:
Thanks for making this guide! Worked perfect 1st time on my hd8 2016. Used rootjunky supertool to disable ota, install nova, disable ads Lockscreen, install Google play.
Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.
Thanks again
From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.
Click to expand...
Click to collapse
Thanks for pointing out the mistake, cause I had disable ota update by OpenDNS method before, so I was not aware of this.

imadiamond said:
Dumbest question:
the root is supposed to stay after turning the tablet off and on again, right?
I say this because went through the whole process successfully. New .bin. No errors on any commands. SuperSU installed binaries and then downloaded Root Checker and verified. Then verified su in adb shell. Then did pm disable of amazon apps and services,
and then turned tablet off and back on and Root Checker says NO ROOT. Root is supposed to stay, correct??? Or is it to just get all of the Amazon items off and customize tablet. Have rooted at least 8 or 9 devices, LG, Samsung, HTC etc, and this one has been the absolute _____ .
Click to expand...
Click to collapse
did you change the default access in SuperSU from prompt to grant? or have you disabled the OTA service?
in normal case, root will not lose till the OS updated.

Need to type exit, exit in shell to save settings?
phpbb88 said:
did you change the default access in SuperSU from prompt to grant? or have you disabled the OTA service?
in normal case, root will not lose till the OS updated.
Click to expand...
Click to collapse
Good question. Thanks for asking phpbb88! Definitely changed the default access. Rebooting here was one of the problems earlier since SuperSU says to reboot, then you must hit "Ok"-- and then logically, you would reboot. But instructions don't say to *ignore* and stay in SuperSU. Previously was rebooting, since Step 13 says "Open up SuperSU"... but SuperSU is already open in Step 12, so no need to open it up.
Only connected to the internet with it once, in December. Saw that everything needed an Amazon account, so have had wireless off/airplane mode ever since. Bought it with sole purpose to root.
The only thing I can think of would be not typing "exit" twice to get out of the shell. First read that instruction at the end of the pm disabling tutorial. If that's important than it needs to be added to the instructions also. Otherwise, when finished people will just power down the device or pull the USB plug. It's got to be written so that someone not knowing anything- first-time Kindle buyer like me , can do it. Here is the log.
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 7590
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU #
C:\Users\COMPUTER\AppData\Local\Android\Sdk\platform-tools>

smokejumper76 said:
I used eu.chainfire.supersu_2.79-SR3-279_minAPI7(nodpi)_apkmirror.com.apk for superSU...that would be another thing to check
Click to expand...
Click to collapse
ROOOOOOOOOOOOOOOOOTEEEDDDDDDDDDDDDDDD.
Final piece of puzzle I think it was the SuperSU I had. Didn't do any other changes. Got it from appsapk.com . FOLKS, do not use any SuperSU you get from there (or anywhere else) at least for this process. You'll end up chasing squirrels. It *might* have gone through even with the other errors etc (like phpbb88 mentioned it did for him), but the wrong SuperSU probably killed everything in the end. Go to https://apkdot.com/apk/chainfire/sup...ersu-2-79-sr3/ and get your SuperSU there: thank you for the suggestion smokejumper76. For one, immediately noticed the app logo was different. Also took longer to load the binaries. Whatever the other SuperSU apk is I'm deleting it now: don't even want to know the version.
phpbb88, I see you added the answer to my question about which option to pick in SuperSU (Normal) to the instructions. Thanks! Would also suggest 1) to add a note NOT to reboot even though SuperSU asks to, since in the next line you say "Open SuperSU" but it's already open and 2) the link for the proper SuperSU in the credits at the end, or the file even.
This was Christmas gift for my gf... now she can use it. Was planning on getting a HD10 for myself, but it's been so long that unfortunately now it might ship with newer software. Might buy one from a retail store as they will have older stock, and the return will be a quick walk-in if it's got 5.3.+.+ .

imadiamond said:
ROOOOOOOOOOOOOOOOOTEEEDDDDDDDDDDDDDDD.
Final piece of puzzle I think it was the SuperSU I had. Didn't do any other changes. Got it from appsapk.com . FOLKS, do not use any SuperSU you get from there (or anywhere else) at least for this process. You'll end up chasing squirrels. It *might* have gone through even with the other errors etc (like phpbb88 mentioned it did for him), but the wrong SuperSU probably killed everything in the end. Go to https://apkdot.com/apk/chainfire/sup...ersu-2-79-sr3/ and get your SuperSU there: thank you for the suggestion smokejumper76. For one, immediately noticed the app logo was different. Also took longer to load the binaries. Whatever the other SuperSU apk is I'm deleting it now: don't even want to know the version.
phpbb88, I see you added the answer to my question about which option to pick in SuperSU (Normal) to the instructions. Thanks! Would also suggest 1) to add a note NOT to reboot even though SuperSU asks to, since in the next line you say "Open SuperSU" but it's already open and 2) the link for the proper SuperSU in the credits at the end, or the file even.
This was Christmas gift for my gf... now she can use it. Was planning on getting a HD10 for myself, but it's been so long that unfortunately now it might ship with newer software. Might buy one from a retail store as they will have older stock, and the return will be a quick walk-in if it's got 5.3.+.+ .
Click to expand...
Click to collapse
Glad to hear that you can finally root your fire.
In fact, I never typed exit twice in adb shell, I just close it...lol
1) After SuperSU updates its binary, I followed the reboot, still success to root my device.
2) I am using the SuperSU apk download from apkpure linked above, why don't you download it in the first try...?
I went to appsapk.com and have a look of the SuperSU, it is totally a different app.

Thanks for the Guide finally got root!

phpbb88 said:
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary
Click to expand...
Click to collapse
I had the exact same problem over and over finally tried this:
change this: rm /system/bin/install-recovery.sh
To this: rm install-recovery.sh

[Megathread]Root Fire HD 10 (7th Gen 2017)

FOR FIRE HD 10 (7th GEN, 2017) ON 5.6.0.0 ONLY
Seems like this is a tradition so I will put this on here.
Update 4: 2018/1/14, Offline rooting method by retyre (If no new method comes out, this will be the final update)
Update 3: 2018/1/1, Minor text fix
Update 2: 2017/12/31, New rooting method by bibikalka.
Update 1: 2017/12/28, Added more content
Code:
###Disclaimer###
I am not responsible for the potential damage that will be done to your tablet, such as boot looping and bricking.
Your warranty might be void by doing the following steps.
YOU are choosing to make these modification.
Looks like these methods doesn't work for Fire HD 8 (7th GEN, 2017)
Reason to start this thread
The topic was started by ztrund in this thread and we ended up with a pretty messy thread, which makes people really hard to locate the exact tutorial post. So I think it should be a good idea to start a new thread.
Note: This thread doesn't work for HD 10 (7th Gen) anymore because root access is temporary and it can't survive after a reboot. As a result, don't follow the exact steps on that thread.
Special thanks to strund, DragonFire1024, Blaiser47, mistermojorizin, UROMEGAX, retyre, bibikalka and countless people who helped, discussed and contributed in the original thread.
By the way, please correct me if there is any problem or mistake.
Some useful posts
1. The first detailed tutorial is located in #221 in the original thread. mistermojorizin provided the method and adb shell history.
2. #233 in the original thread. UROMEGAX provided a detailed guide of the method.
3. #304 in the original thread. I provided a more coherent step by step guide.
4. #248 in the original thread. retyre provided a different way to root the tablet. (Blaiser47 wrote that it's easier for him)
5. Easier Way to Root Fire HD 10 used a different approach by bibikalka. (Looks like new method is easier to do) (For legacy method go to post #2)
6. Offline Rooting Method by retyre
After getting root access
1. Xposed & FlashFire posted by retyre
2. tweaks/apps/modules/hacks/optimizations started by razers7t8

New method
Easier Way to Root Fire HD 10 by bibikalka.
Offline Rooting Method by retyre
Legacy way
You need the following things in order to proceed:
1) adb (Available Here)
2) Kingoroot PC version (Available Here)
3) Kingo.to.SuperSU.zip (can be found here in the attachment of the post)
Preparation work:
1. Turn on USB debug mode and "allow third party app to install" on fire HD 10
2. Update Kingoroot to the latest version
Note: There will be a small grey box on the update pop up page. It is up to you whether to uncheck that box or not. I don't think that will affect the following process.
3. Connect your fire HD 10 with your PC.
4. Unzip "Kingo.to.SuperSU.zip". Copy the folder to your internal storage on tablet.
Note: In root explorer the directory is /storage/emulated/0
Let's start:
1.- Install supersu (ver 2.82) on the fire and root file explorer.
2.- Use Kingoroot to root
3.- Open the adb shell and start to type "su" while Kingoroot is rooting (You can also wait until it's done, then type su to proceed)
Code:
[email protected]:/ $ su
Note: Do not type "adb shell su" because you won't be able to type any command once the # appear. The correct way is to type "adb shell" first then start typing "su"
4.- once the # appear i did # mount -w -o remount /system
5.-Uninstall the Kingo super user app normally (Do not choose to unroot in Kingo super user app)
6.- # cd /data/media/0/Kingo.to.SuperSU
7.- # cp ./su /system/xbin/daemonsu (no error was given in my situation)
8.-# chmod 0755 /system/xbin/daemonsu
9.-# daemonsu -d &
10.-# cp ./su /system/xbin/su
11.-# chmod 0755 /system/xbin/su
12.-# rm /system/xbin/supolicy
13.-# rm /system/bin/install-recovery.sh
14.-# rm -rf /system/usr/iku
15.-# rm -rf /sdcard/Kingroot
16.-Open Supersu (and get the Su occupied error)
17.-setting > reinstall (It is not rebooted)
18.-Install Supersu (ver 2.79) and open it
19.-Supersu ask the user to update binary (I tried to update the binary but failed, nothing happened, didn't reboot)
20.-setting > set supersu as a system app (Mine rebooted immediately after doing this step)
21.-Go to google play to launch Supersu (Don't know why the Supersu icon is not shown in the Fire Launcher so this is an alternative way to open Supersu)
22.-setting > set grant as default access
23.-Then (not sure if a reboot is required here) I received a notification from Supersu and it ask me to update binary
24.-Click the notification to update binary and it should work.
Not sure whether it will work or not if SuperSU (ver 2.79) is used in the beginning of the guide.

Personally the method posted here seems simpler and makes more sense to me.
https://forum.xda-developers.com/hd...re-hd-10-7th-generation-t3718629/post74940137
No need to mess with two versions of supersu. After you have root you can just update supersu and binaries to the latest.
I also do not think there is any need to start adb while kingoroot is rooting. It is fine, and maybe better to prevent errors, to just wait until it is done.
I would recommend one always go back to a clean system by sideloading the official Amazon 5.6.0.0 .bin and do not fully set up or connect to the internet until you have rooted. To skip Amazon set up, just select a wifi and enter the wrong password. Then hit back and it will let you skip. May need to do it a few times.
Make sure to say in the op to copy the kingo folder with the files to your SD card storage and clarify that this is the emulated SD. Implied but for newbies just saying you need to have it and not saying where could be confusing.
After you root, if you want the latest updates, at least as of a day or so ago you can still update officially via device options, system updates. But be careful as at some point doing this may remove root if Amazon pushes more updates. To this point I strongly encourage everyone who roots to keep a copy of the current 5.6.0.0 .bin in case you need to recover. If Amazon updates their website with a new updated os, this version may be gone.
Another note, if you are using the fire launcher (default) and new apps are not showing up, just go to manage apps and find the system app called Home Pages. Force stop it and see if that fixes it. If not, go back and force stop and clear data. That should make it work.
I'll add more as I think of things and as this thread evolves.

why do I have problems with the :
... cd /data/media/0/Kingo.to.SuperSU command
and the ... cd /sdcard/Kingo.to.SuperSU command
Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?

Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?
Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.
Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
C:\ADB>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy
1|[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bakshi said:
Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?
Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.
Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
Click to expand...
Click to collapse
I'll try to answer as much as possible.
First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.
Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.
For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?
---------- Post added at 09:53 PM ---------- Previous post was at 09:50 PM ----------
davidinfoman said:
why do I have problems with the :
... cd /data/media/0/Kingo.to.SuperSU command
and the ... cd /sdcard/Kingo.to.SuperSU command
Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?
Click to expand...
Click to collapse
Use adb and explore your devices directories. CD to get to a directory, ls to list things in the directory. It shouldn't matter how you get it onto your fire, but it needs to be unzipped. It also doesn't matter where you put it as long as you adjust the commands accordingly. Maybe try the downloads folder?

Thanks for your quick reply, I'll do this now!
UPDATE: Your advice worked! Thanks for clarifying that we should do this with a factory reset and should use Kingoroot on the PC.
Blaiser47 said:
I'll try to answer as much as possible.
First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.
Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.
For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?
Click to expand...
Click to collapse

Part of my problem was seeing written many times ... put files on SD card, and I thought we had to have an external SD card put in the tablet. ( I have been running with that "false IDEA" for a couple of days until an hour ago.
No! SD card just refers to location that is on Fire Tablet itself. The ls command helped me a lot. Others should be aware of this.
I thank Blaiser47 for pointing that out. I am getting much further so far, following the advice in this thread.
Thank you oscarcx for starting this thread. Hopefully you can watch over it, and help correct our errors and giving helpful pointers.
Thanks everybody. I feel better now because the roadblock I hit, has been overcome, now for the other steps in the process.

Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.
Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.
5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.
6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.
7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.

manaox2 said:
Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.
Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.
5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.
6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.
7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Click to expand...
Click to collapse
manaox2
Thank You! Thank You! Thank You!
You are the man!
Only those of us that have been frustrated with this process can appreciate your KEEP IT SIMPLE approach to this!
Not sure why the other BIG thread on this couldn't do a step by step like you just did!
You listed the steps that were screwing around with me the last couple of days.
Finally it is ROOTED! Yeah!

Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?

Has anyone tried this method with HD 8 2017 ?

dusty23007 said:
Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?
Click to expand...
Click to collapse
1. You can get it from Google Play or get it from any liable third party app store.
2. If you get it from any liable third party app store, place it directly in the internal storage so you can install it in es file manager.
3. I remember seeing a post about how to save the bricked device in this forum. You can try to follow that post if your tablet got bricked.

YEAH!!!
rooted baby!!!! now can i get rid of the home tabs?
never mind... i disabled fire launcher

Silly question perhaps, Do I need to reset the device before attempting this?

Guys, how about HD8 2017 ?

wikke said:
Silly question perhaps, Do I need to reset the device before attempting this?
Click to expand...
Click to collapse
It is recommended but may not be required

hacker-on said:
Guys, how about HD8 2017 ?
Click to expand...
Click to collapse
As reported in the original long thread, it doesn't work on Fire 7 or Fire HD8.

my .02, i like these instruction by @retyre. Easy peasy when I had to re-root. mostly just posting here for my own reference, hope it's ok.
retyre said:
I have done this with success multiple times over the last day, so try this and report:
1. Start with a pristine /system (adb sideload update .bin if you can).
2. Root using KingoRoot as usual; confirm su usage in adb shell.
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps (incl. SuperUser) from the Apps page on your Fire's Settings.
5. Confirm su and daemonsu are in /system/xbin/:
Code:
cd /system/xbin
ls -al
If not, copy them to /system/xbin/ as in step 3.
6. Copy SuperSU 2.79 .apk (other versions might work, but this is the one I have tried) to your tablet and install.
7. Open SuperSU and update binary as Normal. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Click to expand...
Click to collapse

oscarcx said:
3. #304 in the original thread. I provided a more coherent step by step guide.[/SIZE]
Click to expand...
Click to collapse
When I use KingoRoot it gets stuck at 90%, nevertheless su binary exists and is working.
The folder /data/media/0/Kingo.to.SuperSU however does not exists.
So I skip steps 7-11.
The folders /system/usr/iku and /sdcard/Kingroot do not exists, so I skip 14 & 15 as well
SuperSU does not show "ocupied", but the update binary pop-up (as in step 19) which seems to be successfull (non-recovery install).
I move SuperSU to /system (SuperSU config) and reboot manually.
afterwards the boot is stuck at the "fire" Logo, a soft brick. I tried this two times using adb sideload to reset the system.

I need help rooting my zte quest 5

Ok so i got a zte quest 5 (z3351s) though qlink. Not the phone i wanted but it was one i could afford. And it works very well just can't run amazon music and other apps at the same time.
But the bloatware is unreal. Used to in my galaxy s3&s4 days i could root and delete all apps i didn't need. I know i can disable them but i want them gone completely.
Majisk didnt work
Kingoroot same even used pc.
I am hoping someone knows of a way i can root this phone or at least delete all the un needed apps for example i have Google maps go (came stock) i put the org google maps which is better plus offers sat view.
Edit i did some math and converting and the useless apps 11 out of 58 come out to 349.72mb which is a lot if your phone only has 16gb of space. Also note i don't have hardly anything.
Worst case i can Hotspot to my note10+ for multitasking but not sure of data limit.

@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.

I heard about adb methods but i haven't messed with it in forever since apk/ios apps came out

jwoegerbauer said:
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
Click to expand...
Click to collapse
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.

vp1117 said:
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
Click to expand...
Click to collapse
I spoke of SU-binary and NOT of SuperSU installer package
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.

TexasPride, sorry I stepped in your thread.​
jwoegerbauer said:
I spoke of SU-binary and NOT of SuperSU installer package
Click to expand...
Click to collapse
I see. It is often mixed in numerous materials one can find in the net. Subject is SU-binary update, but the ultimate goal is to install supersu.
jwoegerbauer said:
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Click to expand...
Click to collapse
What should be result of running this code? SU-binary located in Downloads with 777 permission? What is the practical sense/use of it?
What software/application would use SU in that location?
Sorry for my questions. I'm not arguing. I try to understand the idea.
jwoegerbauer said:
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
Click to expand...
Click to collapse
Somehow, with my almost zero knowledge of edify and linux command line I got the same conclusion: SuperSU zip has to be modified in order to install it via adb on devices that do not have TWRP for sideload. I failed to find any examples of SuperSU modding...

@vp1117
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"

jwoegerbauer said:
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
Click to expand...
Click to collapse
OK. I guess, I can repack zip to tar.
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
jwoegerbauer said:
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
Click to expand...
Click to collapse
Interestingly, I can execute all commands I need without having su-binary (~100 KB) uploaded to my phone. It is strange but I see #-prompt after I ran <adb shell>. This happens on my UNrooted phone, running stock ROM. I guess, it's a specifics of my phone, no need to try explain it.

I done failed trying to read i dont really understand linux all that well. But if anyone has any links so i can download it and try it

vp1117 said:
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
Click to expand...
Click to collapse
Of course it's your decision how you transfer the SuperSU package onto phone: many ways lead to Rome.
My decision was to push SuperSU package repacked as TAR-file onto phone, extract it there, and finally run the modified update-binary.sh when phone is booted into recovery mode:
Code:
adb shell "$(cat < %supersu_dir%/update-binary.sh); echo $?"

So I rebooted to stock recovery and then uploaded following from UPDATE-SuperSU-v2.82-20170528234214.zip package to my phone's folder /tmp:
/arm64
/common
/META-INF
update-binary.sh
Here is what I got:
Z:\android\adb>adb shell "$(cat < /tmp/update-binary.sh); echo $?"
127
/system/bin/sh: #!/sbin/sh: not found
And here's what I got running same command from # command line:
# $(cat < /tmp/update-binary.sh); echo $?
/system/bin/sh: #!/sbin/sh: not found
127
In response to # ls -al /sbin I get lots of lines one of them is as follows:
lrwxrwxrwx 1 root root 7 1970-01-01 00:00 sh -> busybox
I feel that I'm doing something wrong, but what exactly?
In attached txt-file I put some more details I got in command line.

jwoegerbauer said:
... and finally run the modified update-binary.sh when phone is booted into recovery mode:
Click to expand...
Click to collapse
Am I right the only modification needed is to rename update-binary to update-binary.sh ?

@vp1117
NO.
When I said modified then I didn't mean simply rename it: The contents of original update-binary file must be rewritten / deleted in some parts. Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above. Take also note that, if device's Android isn't rooted yet, the location for unpacked SuperSU mandatory must be /data/local/tmp.
BTW:
I can see BusyBox is installed on your device's Android. Take note that BusyBox by default comes with the SU-binary. Hence your device's Android is rooted! Wondering why you waste your time with trying to completely install SuperSU from scratch?

jwoegerbauer said:
Wondering why you waste your time with trying to completely install SuperSU from scratch?
Click to expand...
Click to collapse
Good question.
Probably, because I see this when phone restarts from recovery to normal android:

jwoegerbauer said:
Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above.
Click to expand...
Click to collapse
OK, no problem, I can re-pack zip into tar.
However, what you demonstrated above was a screenshot showing update-binary.sh being inside the tar. At the same time you don't tell how update-binary.sh must be amended. Is it OK?

TexasPride​
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.

vp1117 said:
TexasPride​
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
Click to expand...
Click to collapse
Its ok, i dont mind at all.

@TexasPride
FYI: I no longer participate this hijacked thread.