yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] :
sure thing...actually I'm going to try it again..but I noticed a couple of stupid things on my end.

I have an HTC m8 heavily modified. So my platform tools dir is full of htc adb, and fastboot crap.

Now, before doing all this I installed the fire drivers and..well at least it showed everything was cool..except the one time I was just messing

in recovery mode and I noticed that it did not show up as android ADB or ADB composite, but in other devices it showed "KFGIWI"..which was weird. So I was able to update the driver to android composite device and it now shows up in recovery as sideload.

Anywhere except in recovery I could issue adb commands. In recovery it would not show the device.

So, I fixed that issue and replaced my platform tools with newer versions of adb because when I tried to adb sideload the .bin file to start fresh I got error I need adb 1.0.32 or newer..so I replaced my platform tools dir and retried the .bin flash and it went through...yay..so now I will try again.
[Fire HD 8 and HD 10 General] chemie99:
I did have the problem of the "no binaries installed" once in the three times I did this. The only fix I found was to restart with fresh 5.3.1.1. and then it did work. No idea what was different. The one thing is you could try issuing all the commands in the original instructions instead of the ones where I listed the ones with no error message; maybe I missed one? I did issue them all and it worked. (The other time it worked for me, I was able to run ./step1.sh ; the time it failed I got an access file error).

I do suspect that it has to do with ADB. I think kingo uses an old or modified version so when I started adb, it said out of date and had to

adb kill-server

adb start-server to recover

Maybe this is why we sometimes could run the step0.sh step 1.sh scripts (which [MENTION=7995022]phpbb88[/MENTION] has extracted for you to manually run instead) and sometimes would would say that we did not have permission to access (even though it was on sdcard and should not be protected).

Anyway,short of reloading, not sure if you have any options. Note that I did use adb to installl supersu but I see no reason why ES file explorer would not work either.
[Fire HD 8 and HD 10 General] :
ok. will do

Just for clarification, when you say to restart with a "fresh 5.3.1.1" do you mean a factory reset or recovery via adb .bin sideload flash?
[Fire HD 8 and HD 10 General] chemie99:
adb sideload via recovery

I wipe cache, then data, then sideload
[Fire HD 8 and HD 10 General] :
oh wow..i did it the opposite, i would side-load, then wipe data then cache..but ill try it that way.

---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------

and I found your post:

copy the files of the kingo root removal to sdcard/kingo

adb shell

su

mount -w -o remount /system

cd /sdcard/kingo

cp ./su /system/xbin/daemonsu

fails because it is locked. Then I started to think that the steps were for the kingo app and not the PC so

with adb window still open, run PC program and remove root

then

cp ./su /system/xbin/daemonsu

chmod 0755 /system/xbin/daemonsu

daemonsu -d &

./step1.sh

got some errors

then sideload the supersu apk via ES file explorer

then allow supersu to do it thing and reboot.

Now I have supersu running!''

~~~~

I'll try it like that and see..nuking now...I'll keep u posted.
[Fire HD 8 and HD 10 General] chemie99:
To recap all 9 pages... The above worked for me the first time. I did not think I had root (for the reasons that [MENTION=7995022]phpbb88[/MENTION] describes later), so I ended up wiping. The second time around it failed with Supersu saying it failed to load binaries. During that attempt, I had tried to do the same thing as the first time but I got the error when running ./step1.sh saying I did not have access to the file (so in the end none of step1 commands were issued). The third time I ran using instructions from [MENTION=7995022]phpbb88[/MENTION] and it worked.

It is obviously finicky, as nearly the same steps produce different results. I thought I did the same things between two attempts and one worked and one didn't.
[Fire HD 8 and HD 10 General] gpmartinson:
I am not prepared to join in to the process that you all are describing but I speak for many when I say thank you for working through this. You are blazing a trail and we all hope to benefit from your experience.
[Fire HD 8 and HD 10 General] chemie99:
I see now that my original steps, I installed Supersu AFTER the ./step1.sh commands and it worked. [MENTION=7995022]phpbb88[/MENTION] has you doing inbetween ./step0.sh (step #7 in his instructions) and ./step1.sh steps (Step #9 in instructions) (which did work for me in my final attempt). I do not know which is better but I could see it mattering.
[Fire HD 8 and HD 10 General] phpbb88:
OMG I see that too now. In the README file, SuperSU was installed after step1.sh.

The dame statement at the bottum of step0.sh cheated me.
[Fire HD 8 and HD 10 General] chemie99:
Well, your steps as written did work (at least once) but perhaps we need to revise. I know for sure the first time I did it after ./step1.sh commands. Feel free to combine your original steps and my add-ons for the final guide but we still need someone to work from fresh flash and confirm.,...
[Fire HD 8 and HD 10 General] phpbb88:
[MENTION=6200352]smokejumper76[/MENTION]

Please see if swapping step 8 and 9 works

---------- Post added at 02:17 AM ---------- Previous post was at 02:15 AM ----------

I wrote the instruction by memory, so there may have some faults...

thats why we need tester..lol
[Fire HD 8 and HD 10 General] chemie99:
You know, while I think I followed your instructions, since I was doing it for the third time, it is POSSIBLE I followed my steps and did Supersu after ./Step1.sh commands. I know I was trying to track which of the commands were needed but it was late and 12 hours into the effort at that point (right after you went to bed if I recall)

Looking at the commands:

rm /system/xbin/supolicy

rm /system/bin/install-recovery.sh

rm -rf /system/usr/iku

I could see the "rm /system/xbin/supolicy" as being important. You want to delete the version from kingo and not new Supersu. I do not know for sure that Supersu installation adds this file to this location but.....
[Fire HD 8 and HD 10 General] phpbb88:
yes, its possible. really tired that night

---------- Post added at 02:27 AM ---------- Previous post was at 02:25 AM ----------

It is so strange that someone could have it success while step 8 and 9 were in wrong sequence....
[Fire HD 8 and HD 10 General] chemie99:
I think a few are out of sequence.

You have step 6 out of order too.

It is:

.step0.sh commands

cd /sdcard/Kingo.to.SuperSU

cp ./su /system/xbin/daemonsu

chmod 0755 /system/xbin/daemonsu

daemonsu -d &

then remove root

then /.step1.sh

rm /system/xbin/supolicy

rm /system/bin/install-recovery.sh

rm -rf /system/usr/iku

then install supersu

I might have been following the readme and not your exact steps. I know you used the actual commands from your post but maybe followed our original order
[Fire HD 8 and HD 10 General] :
sorry...for not getting back..it was like my 3rd or 4th attempt. I tried not reflashing and just rerooting the steps and command line commands..and same thing.

Then I came back on here and read to try swapping steps 6&7..lemme nuke it again and start fresh. it will take a few min. so ill be on here while it's done flashing.
[Fire HD 8 and HD 10 General] chemie99:
Note my more recent comments on order. Need to swap a few steps.
[Fire HD 8 and HD 10 General] :
10-4
[Fire HD 8 and HD 10 General] chemie99:
Step 5, then 7, then 6, then 9, then 8
[Fire HD 8 and HD 10 General] :
are we dancing? lol..thanks i was redoing the list im going off of..that helps. waiting on the flash.computer not the fastest.

BTW..thank you all for your help.
[Fire HD 8 and HD 10 General] phpbb88:
in addition if you wanna get safer, look into the README for ref.

and also this is the full code of step 7(step0.sh file):

mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &

this is the full code of step 9(step1.sh file):

cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
./chattr.pie -ia /system/xbin/ku.sud
./chattr.pie -ia /system/xbin/supolicy
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/shipclean
rm /system/bin/start-ssh
./chattr.pie -ia /system/etc/install-recovery.sh
./chattr.pie -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install_recovery.sh
rm /system/usr/icu/icusuflag.conf
./chattr.pie -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot

---------- Post added at 02:49 AM ---------- Previous post was at 02:46 AM ----------

Please help to copy my current instruction for back up, I'm afraid changing the order would make things worse, as someone above had it success using that "wrong" sequence.

I will change the above instruction 1 hr later, I'm already late for workkkkkkkkkkkkkkkkk
[Fire HD 8 and HD 10 General] chemie99:
although where they say remove kingoroot, this is where you remove root from the PC.
[Fire HD 8 and HD 10 General] :
I'm at step 5 right now:

1|root@giza:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu

cp: /system/xbin/daemonsu: Text file busy

1|root@giza:/sdcard/Kingo.to.SuperSU #

Because kingoroot hasn't been removed yet. I know that if i remove kingoroot keeping the adb # open i will be able to then issue that command...so im kinda in a loop here.

* I need to remove kingoroot via pc in order to pass that command.

although it looks like it puts me in a deeper # process via "11|root"...hmmm wait a sec...
[Fire HD 8 and HD 10 General] phpbb88:
yea... the text file busy.. You got to remove kingoroot first then

---------- Post added at 03:30 AM ---------- Previous post was at 03:26 AM ----------

i knew i have the reason to swap the sequence, just cannot remember anything now
[Fire HD 8 and HD 10 General] :
OK...i just tried it step 5, then 7, then 6, then 9, then 8, even with the locked txt error....just doing the steps as prescribed. sideloaded supersu and no su binary installed.

~~~~~~~~~~

root@giza:/sdcard/Kingo.to.SuperSU # mount -w -o remount /system

root@giza:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu

cp: /system/xbin/daemonsu: Text file busy

1|root@giza:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu

root@giza:/sdcard/Kingo.to.SuperSU # daemonsu -d &

[1] 3532

root@giza:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy

[1] + Done daemonsu -d

root@giza:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh

root@giza:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku

root@giza:/sdcard/Kingo.to.SuperSU #

~~~~
[Fire HD 8 and HD 10 General] chemie99:
That rings a bell...in fact I think we even posted on this back on page 3 or something. That is when I removed the kingo root on PC which then allowed access to remove that file.

---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------

How about 5,6,7,9,8 ?

PS. I know you don't want to hear this, but you might have to re flash. Try to get kingo to do the root again and re-start the steps but when I tried, kingo wanted me to grant access on the device which you can't do since the kingo Supsersu is broken.
[Fire HD 8 and HD 10 General] :
yup. reflashing now..my mind is numb

I'm no *nix greybeard but I do believe that daemonsu spawns a child su process or something. I could be wrong/smoking something. But if I was right, I would be smoking something.
[Fire HD 8 and HD 10 General] nbc12:
Does anyone know if kingo supersu would work if we mounted /system as rw?
[Fire HD 8 and HD 10 General] chemie99:
The only good news is that you will get there. I have a fully working root so we know it can be done. The problem was that two of us on Saturday tried so many things, it is hard to remember what worked when and how. I think the instructions are "close" but as I said before, I might have read what he put but done what I had working earlier. It took me three tries and that is without instructions (actually, I had it and then lost it and struggled to get it back so there you go).

---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------

worth a try. Honestly, the fact that it crashes was always secondary to me because I would prefer to use supersu but with their superuser crashing, that just made it all the more important. Getting it to work might eliminate all these reflashes since when you try to re-add root from kingo PC, it wants you to grant access which you can't do since it is borked.
[Fire HD 8 and HD 10 General] :
once we get this..despite all the logging, etc...you guys can update everything so a definitive guide will be posted. that will be awesome for everyone. I'm willing to do the plunge like u guys did.

closest I got was I tried just installing supersu with kingoroot installed and supersu would prompt to update the binaries..i left the tablet for like 20 minutes and it eventually succeeded, or kinda but not really according to titanium backup. That was the furthest I got.

Still..flashing.
[Fire HD 8 and HD 10 General] chemie99:
our guinea pig ...excellent.
[Fire HD 8 and HD 10 General] nbc12:
Well, if kingo superuser has a setting to remove itself and install supersu, wouldn't that be easier? idk if it has an option that does that, this is the first time I've used it. Ill try it right now
[Fire HD 8 and HD 10 General] phpbb88:
[MENTION=6200352]smokejumper76[/MENTION] sorry about that.

if you have try following my instruction accordingly but not working, try swaping 8 and 9. Not others. I can recall most when I wrote the instruction, not now. Trust the old me lol

page2 is where we find the way out, you can take ref. there too.

---------- Post added at 03:59 AM ---------- Previous post was at 03:56 AM ----------

there's nothing you can do with the built-in superuser, it crashes once opened.

that's why we need to replace it with superSU
[Fire HD 8 and HD 10 General] chemie99:
I re-read page 1 and realized that [MENTION=2825960]2ig2ag[/MENTION] actually mentioned the supersu permission issue but I think we both missed that. That could have saved me a few re-flashes.

I wonder if [MENTION=631273]Chainfire[/MENTION] could comment on why supersu is not prompting. Perhaps a missing file or permission?
[Fire HD 8 and HD 10 General] nbc12:
Thats what I'm saying. If we can fix it, and it has an option that removes itself so the user could install another superuser (ex supersu), wouldn't that be easier? It seems like the only thing stopping it is that /system isn't r/w
[Fire HD 8 and HD 10 General] phpbb88:
FYI, I re-flashed total 3 times then make it to the goal XD

you still remember that time I said I would like to keep the status as I cannot grant anything before installing SuperSU? BUT YOU RE-FLASHED lol

---------- Post added at 04:05 AM ---------- Previous post was at 04:04 AM ----------

I didn't test on it, would you?

if it does, that would save lots of pain.
[Fire HD 8 and HD 10 General] chemie99:
except I do not think it will give that option. That is why there were the instructions on how to manually tear it out and replace which was the basis for our procedure. Kingroot does not give this option so I doubt kingo does.

---------- Post added at 03:11 AM ---------- Previous post was at 03:10 AM ----------

Well, I also re-flashed 3 times but actually had a working supersu after just one time. That is even worse!

BTW, we are at 48 hours and still seem to have the OTA disabled. I will give it a few more days then go wild and open things up.
[Fire HD 8 and HD 10 General] :
ok...ill try the original steps, but swap steps 8 & 9.

*cake break..mmm cake.
[Fire HD 8 and HD 10 General] nbc12:
I couldn't get kingo superuser to work with /system remounted as r/w, so if somebody else wants to take a crack at it, go right ahead.
[Fire HD 8 and HD 10 General] coltxL2717:
I was able to root multiple times following phpbb88's steps. I always rebooted after installing KingoROOT. I also copied all the files to /data/local/tmp and did a "chmod 0755 *" on the whole directory. Hope this helps.
[Fire HD 8 and HD 10 General] phpbb88:
Thanks for testing it :) :good:

That means changing to SuperSU is a must.

---------- Post added at 08:00 AM ---------- Previous post was at 07:48 AM ----------

I somehow searched about the permission denied problem before,

some said when bash file was store in sdcard, they cannot be excuted.

So I think if the file were saved at another place, the step0.sh and step1.sh can be excuted.

---------- Post added at 08:06 AM ---------- Previous post was at 08:00 AM ----------

The script is used to replace kingroot/kingoroot apk version to SuperSU,

but we used PC version to root the device, so there should be differences.

Also, the step1.sh part is meant to delete the Kingoroot thing in the device, however we have already did that by manually remove the root on PC, so lots of "No such file or directory" errors come out.

So whats the result? Could you root your device successfully? By the swapped instruction or the original one?

Thanks.

---------- Post added at 08:31 AM ---------- Previous post was at 08:06 AM ----------

updated the instruction on page 4 for more detailed desc.

still not confirm if step 8 and 9 should be swapped, so I'm not gonna change it this time.
[Fire HD 8 and HD 10 General] phpbb88:
That's why I didn't remove the extra code in step1. As "Permission denied", the device cannot even execute one single line of code.

However, I am very confused about step 8 and 9. Since the OP of this thread(@coltxL2717) said he can successfully root his device few times using my steps. Is the swapping necessary to success root?
[Fire HD 8 and HD 10 General] :
Tell ya what....I'll nuke it from scratch again and go plan A then plan B. But in plan A, I'll make sure to run ALL the commands...ill do it in a few. need more cake.

I'm confident I'll get root again, so I'm not afraid to start over so we can get definitive answer. I'll try to make better log too. I can be lazy without not properly formatting, sorry.
[Fire HD 8 and HD 10 General] phpbb88:
Glad to hear you can perform test! :laugh:
[Fire HD 8 and HD 10 General] :
Prep:

C:\dump\adt-bundle\sdk\platform-tools>adb reboot recovery

C:\dump\adt-bundle\sdk\platform-tools>adb devices
List of devices attached
G000XXXXXXXXXXHB sideload

C:\dump\adt-bundle\sdk\platform-tools>adb sideload update-kindle-49.5.5.4_user_554206920.bin
Total xfer: 2.00x

C:\dump\adt-bundle\sdk\platform-tools>

Plan A. Steps 8&9, as written but with certain commands listed in step1.sh

step 1-2

loaded kingoroot and rooted tablet <adb enabled, unknown sources, etc etc)

step2B

reboot <adb reboot>

step 3

C:\dump\adt-bundle\sdk\platform-tools>adb install es-file-explorer-4-1-6.apk
[100%] /data/local/tmp/es-file-explorer-4-1-6.apk
pkg: /data/local/tmp/es-file-explorer-4-1-6.apk
Success

C:\dump\adt-bundle\sdk\platform-tools>

step 4

copy Kingo.to.SuperSU folder to Computer\Fire\Internal storage

step 5

adb shell
su
mount -w -o remount /system

step 6

leave adb # window open:

load up pc kingoroot and remove root

step 7

in adb window:

cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &

step 8

sideload supersu app (kept adb window open, just opened 2nd command prompt)

C:\dump\adt-bundle\sdk\platform-tools>adb install "eu.chainfire.supersu_2.79-SR3-279_minAPI7(nodpi)_apkmirror.
com.apk"

Success

step 9:

issue commands (I'm going to do 6 of them as listed in step1.sh

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

step 10

run supersu on tablet and update binary...SUCCESS :cool::cool::cool:

NO to reboot, settings->default access grant <at least for now.lol>

then, adb reboot

test for persistant root succeeded.

I was actually going to do PLAN B if Plan A didn't work, but PLAN A , also worked. So steps 8&9 can be swapped

BUT:

These commands MUST be run:

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

<that last one is important me thinks..well they all are..lol>

once that's done, superSU binaries will update.
[Fire HD 8 and HD 10 General] phpbb88:
[MENTION=6200352]smokejumper76[/MENTION]

In fact I didn't see any differences between your last try and the previous' try...

Can you tell the differences? Any missing step so that the rooting not work?

Maybe the script part?
[Fire HD 8 and HD 10 General] chemie99:
I think [MENTION=6200352]smokejumper76[/MENTION] caught a missed commands in Step 9 (which needs to be swaped with Step 8). I had actually run every command (many with errors) but went back and tried to caught only those needed. I must have not scrolled all the way up.

./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

versus

rm /system/xbin/supolicy

rm /system/bin/install-recovery.sh

rm -rf /system/usr/iku
[Fire HD 8 and HD 10 General] chemie99:
See above; a few more commands are needed. There should be a way to get the bash script to run. I know I had it running a few times. Should be able to change the r/w chmod or something. Someone mentioned they chmod 0755 the whole kingo directory which seems a good idea to try
[Fire HD 8 and HD 10 General] phpbb88:
lazy makes failure.....lol

I always try with the full script
[Fire HD 8 and HD 10 General] chemie99:
I am going to try tonight to fix supersu to prompt; I have some ideas. Most likely, I will end up breaking it and reflashing in which case I will also get the bash to work. Too many commands to type correctly.
[Fire HD 8 and HD 10 General] phpbb88:
[QUOTE="phpbb88, post: 70588604, member: 7995022"]
I somehow searched about the permission denied problem before,
some said when bash file was store in sdcard, they cannot be excuted.
So I think if the file were saved at another place, the step0.sh and step1.sh can be excuted.
[/QUOTE]

FYI, my previous reply.

Still, we cannot test it as we already in a stable state with everything installed... what a pain to start it all over and test it...
[Fire HD 8 and HD 10 General] phpbb88:
playing around with the superSU makes me loss my root,

okay then I can test the confusing parts.

1. Tested moving the Kingo.to.SuperSU to /data/local/, still cannot run the bash script step1.sh directly.(Permission denied) darn, I forgot to test the chmod 755 part.

2. Tested the script in step1.sh, SuperSU still works while only executing the 6 command below. (On the second attempt, 1 out of 6 shows No such file or directory, so I included a statement to declare 0-1 error is okay)

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

3. Tried using another Superuser app, still cannot make it prompt.

updated the instruction on page 4.
[Fire HD 8 and HD 10 General] chemie99:
Can you elaborate? One of my ideas was to try the "install in system directory" option. No point if that breaks root.

Also, for your Page 4 steps, are you sure about order for Steps 8 and 9?