Database Info

Help: Good For Eterprise on a previously rooted phone

Trying to install GFE on a previously rooted but now unrooted phone. It's failing because it thinks I'm still rooted.
I have unrooted, removed Superuser (the apk and from the App list), etc.
What the hell is it finding?

Maybe su or busybox in the xbin folder?

wewoapsiak said:
Maybe su or busybox in the xbin folder?
Click to expand...
Click to collapse
Yes. They are both there. But how do I get rid of them now that I'm not rooted? ADB shell errors out with read only file system. If I re-root and delete them, then how do I make the file system read only again?
Also, do I need to get rid of /system/bin/su or is that part of stock Android?
Thanks so much for any help.

So all you did was delete the .apk? Download Super 1-click, re-root, then use it to unroot.
http://forum.xda-developers.com/showthread.php?t=803682

wewoapsiak said:
So all you did was delete the .apk? Download Super 1-click, re-root, then use it to unroot.
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
I rooted by flashing the update.zip and then unrooted by removing the Superuser app and then changing the file system to read only.
I thought SuperOneClick only worked with FroYo on the G2X and not with Gingerbread.

Success!!!!!!!! Many thanks to jboxer and others that pointed me in the right direction.
Here's what you need to do for anyone else facing this issue:
1. Boot into Clockwordmod Recovery and then connect your phone to the computer. CWM Recovery will be seen on ADB with root permissions.
2. Before issuing the following commands, after your phone is connected, use the menu in CWM Recovery to mount the system. If you don't mount the system you are seeing CWM's mini Android system and not the phone's.
3. Issue the following commands from your computer:
#adb uninstall com.noshufou.android.su
#adb shell rm /system/app/Superuser.apk
#adb shell rm /system/bin/su
#adb shell rm /system/xbin/su
#adb shell rm /data/local/tmp/psneuter
#adb shell "find /system/xbin -type l | xargs rm"
#adb shell rm /system/xbin/busybox
4. Use the CWM Recovery menu to unmount system.
5. Reboot your phone.
Before you attempt to re-run the Good setup, check one last time to make sure that su is gone from /system/bin and /system/xbin and that Superuser does not show up either in your Apps or when you go to Settings->Manage Apps. If any of this is still present you need to redo what is written above as the Good setup will fail.
I also recommend doing a Nandroid before unrooting, a second Nandroid after unrooting but before installing Good, and then a third Nandroid immediately after successfully installing Good.

[Q] Titanium Backup not working on my ROOTED One S

Hi,
Today I've unlocked, flashed Paul's CWM recovery, and then rooted my HTC One S.
I've installed SU and Busybox but Titanium Backup still says it couldn't get root privileges. What am I doing wrong?
reupugi

try to update the binarys in SU
if that fails re flash the root.zip file
happened to me yesterday

Thanx for the quick answer.
When I try to update the su binarys it fails saying it "failed to find currently installed su binery...
What does that mean?

uninstall and reinstall the SU app
or reflash the root file as this is supposed to install SU on your device

Well, last night I spent hours trying to uninstall and reinstall su. I've also flashed Paul's root twice but still no luck.. I've tried to install busybox with two different apps but still no luck... Is there any way to roll back everything and start over?

you need to flash the su through cwm. then you can update the app's. You can not just download a app and think that it will root the phone. Look at step 3.
http://forum.xda-developers.com/showpost.php?p=24478083&postcount=1

So I encountered a similar problem (https://github.com/ChainsDD/Superuser/issues/46).
Edit: Of-course it'd make more sense to confirm if this could be the problem first...
Code:
$ adb pull /system/framework/framework.odex
$ strings framework.odex | grep HtcIntentFlag
@test_code: getHtcIntentFlag:
@test_code: setHtcIntentFlag:
addHtcIntentFlag
getHtcIntentFlag
setHtcIntentFlag
I patched the su binary in accordance with the change I observed in the framework and that works for me.
Could the OP please try the following su binary:-
* http://revolutionary.io/one-s/su (md5sum: 83fdeaef210225d7361e6c8eb63bae96)
This will need to pushed from recovery, something like (after ensuring /system is mounted):-
Code:
$ adb push su /system/bin/su
$ adb shell chown root /system/bin/su
$ adb shell chgrp root /system/bin/su
$ adb shell chmod 6755 /system/bin/su
(You can obviously push to xbin/ if you have the appropriate symlink set-up in bin/, etc...etc...)

zylith said:
you need to flash the su through cwm. then you can update the app's. You can not just download a app and think that it will root the phone. Look at step 3.
http://forum.xda-developers.com/showpost.php?p=24478083&postcount=1
Click to expand...
Click to collapse
I've flashed su through Paul's cwm, following steps 1,2 and 3. I did have a problem entering bootloader through shutting sown - power+vol down. For some reason that didn't work, numerous times, so I got into the bootloader through terminal (mac) and command prompt (win 7).

[Q] Polaroid 8" Tablet PTAB8000 ICS 4.0.3

Ok, so a friend of mine bought 3 of these things from Kohls on Black Friday as Christmas presents for her kids and has asked me to help set them up as kid friendly devices. Unfortunately they don't come with any Gapps installed and I'm having difficulty installing any of them including the Play Store. I'm also running into problems installing simple games like Angry Birds. In fact very few of the APK's that I have backed up from my other Android devices seem to want to install on these tablets. I also can't find any forums on here or anywhere else evening addressing these devices yet. I'm wondering if there's some kind of generic udate.zip I can use for these things that isn't device specific? A little while back I was able to install an update.zip on a Zeki tablet that enabled me to finally install all the Gapps and maximize it's potential. But then again those things come rooted out of the box and the update was Zeki specific, so...
Anyways, please if anyone can help? This could be your chance to be the first to help unlock the potential of these devices.

Rooting PTAB8000
This is NOT my work, it is from mbellot at FreakTab, but it worked great for me.
Rooting is easy, market is nearly as easy. Here is the original thought process.
Here it is, modified the way I have done it (a couple times), broken into logical chunks.
1. C:\ADB> adb shell
2. [email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
3. [email protected]:/ $ ln -s /data /data/local/tmp
4. [email protected]:/ $ exit
5. C:\ADB> adb reboot
This gives you write access to /data for the next set of steps.
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. [email protected]:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. [email protected]:/ $ exit
10. C:\ADB> adb reboot
This puts you into a "debug" mode of sorts, the LCD will be black after the boot logo comes and goes.
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. [email protected]:/ # chown root.shell /system/bin/su
16. [email protected]:/ # chmod 06755 /system/bin/su
17. [email protected]:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|[email protected]:/ # ln -s /system/bin/su /system/xbin/su
19. [email protected]:/ # exit
The chown and chmod in steps 15 and 16 are critical to su working properly.
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
At this point you can install market files. You need to do it before you remove the local.prop file since the PTAB8000 refuses to run adb in root mode or allow remounting. You can use this as a starting point for installing market, but I would suggest you grab the latest ICS gapps and replace the files. Also, market/play is not vending.apk in ICS, its phonesky.apk.
Once you're done with su and market you need to make your tablet boot normal again.
21. C:\ADB> adb shell
22. [email protected]:/ # rm /data/local.prop
23. [email protected]:/ # rm /data/local/tmp
24. [email protected]:/ # mv /data/local/tmp.bak /data/local/tmp
25. [email protected]:/ # exit
26. C:\ADB> adb reboot
Finished.

Thanks.
HD Brian said:
This is NOT my work, it is from mbellot at FreakTab, but it worked great for me.
Rooting is easy, market is nearly as easy. Here is the original thought process.
Here it is, modified the way I have done it (a couple times), broken into logical chunks.
1. C:\ADB> adb shell
2. [email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
3. [email protected]:/ $ ln -s /data /data/local/tmp
4. [email protected]:/ $ exit
5. C:\ADB> adb reboot
This gives you write access to /data for the next set of steps.
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. [email protected]:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. [email protected]:/ $ exit
10. C:\ADB> adb reboot
This puts you into a "debug" mode of sorts, the LCD will be black after the boot logo comes and goes.
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. [email protected]:/ # chown root.shell /system/bin/su
16. [email protected]:/ # chmod 06755 /system/bin/su
17. [email protected]:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|[email protected]:/ # ln -s /system/bin/su /system/xbin/su
19. [email protected]:/ # exit
The chown and chmod in steps 15 and 16 are critical to su working properly.
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
At this point you can install market files. You need to do it before you remove the local.prop file since the PTAB8000 refuses to run adb in root mode or allow remounting. You can use this as a starting point for installing market, but I would suggest you grab the latest ICS gapps and replace the files. Also, market/play is not vending.apk in ICS, its phonesky.apk.
Once you're done with su and market you need to make your tablet boot normal again.
21. C:\ADB> adb shell
22. [email protected]:/ # rm /data/local.prop
23. [email protected]:/ # rm /data/local/tmp
24. [email protected]:/ # mv /data/local/tmp.bak /data/local/tmp
25. [email protected]:/ # exit
26. C:\ADB> adb reboot
Finished.
Click to expand...
Click to collapse
HD Brian,
I'm going to say thanks because I'm sure everything you just posted is probably going to be very clear to quite a few people that understand all of that. So thank you for helping out. Unfortunately though for me, I got lost. Though I've been tinkering with android and windows mobile devices for about 3 years now, I've actually never done any ADB editing and not sure I fully understand how to do it.
Personally I'm not too concerned about modifying these things too much because they are for someone else's kids, and I've found a way to work around rooting and using Gapps to be able to install the apps they're needing. And before I hand these things back over to be wrapped for Christmas I'm going to make a video showing what I've done to maximize the out of box potential of these things.
But on that note, I'm going to make a request of you if you don't mind. Considering you seem to know how to easily achieve the task, I was wondering if you'd be willing to make and post a Youtube video that takes people through the steps. I know it might be time consuming, but after all we are all here to help each other out. And I'm sure that the people who actually own these devices would really appreciate it. At this point I haven't been able to find any videos on how to mod this tablet yet and the only forums that I've found discussing these things are the one you mentioned and this one here.
So I hope you'll be willing to help other owners out, and I appreciate you taking the time to respond.
Thanks

I had been thinking about reloading the stock rom and doing the root all again as a refresher for myself, but I have never done a YouTube video before. I will try to find the time to do it and them I will post the link here.

For anyone still having issues with rooting and getting the play store on this device I have just made a script to automate the whole process.
filedropper [dot] com / polaroidaio
Note ADB drivers are required.

TeODH4 said:
For anyone still having issues with rooting and getting the play store on this device I have just made a script to automate the whole process.
filedropper [dot] com / polaroidaio
Note ADB drivers are required.
Click to expand...
Click to collapse
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.

smokethrower2 said:
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
Click to expand...
Click to collapse
Any luck with this script yet? Also, how were you able to flash back to factory?

Wanted to add, got the same black screen so I booted to recovery and did factory reset which got me back to square 1. I install the getjar app store and did a search for gmail. when it came up i downloaded it, and during the installation it also installed the "Google Play" store. I was getting a few errors but after turning sync on and using the store for a bit they all cleared up so far. Now I have google play and gmail apps on the tab.

BigT504 said:
Wanted to add, got the same black screen so I booted to recovery and did factory reset which got me back to square 1. I install the getjar app store and did a search for gmail. when it came up i downloaded it, and during the installation it also installed the "Google Play" store. I was getting a few errors but after turning sync on and using the store for a bit they all cleared up so far. Now I have google play and gmail apps on the tab.
Click to expand...
Click to collapse
Sorry about the black screen issue guys there was an issue with the code. I've also completely rewritten the application in c++. All features should work without issues now.
You can download the software here: mediafire [dot] com/?o2864kb92hcc0hb (sorry i can't post links yet, I'll work on getting some posts done...)
1) Download RAR file
2) Extract RAR file
3) Run PolaroidAIO.exe
4) Enable USB debugging and Stay awake
5) Drivers are included in this release if needed
6) Enjoy your fully rooted tablet with the Play Store and Google Services Framework.
If anyone is intrested in the source code let me know and I will post it as well...
Have fun guys!
---------- Post added at 09:58 AM ---------- Previous post was at 09:26 AM ----------
smokethrower2 said:
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
Click to expand...
Click to collapse
There was a bug in the old code, same thing happend to mine after i did a factory reset to try and replicate your situation. Try the updated version 1.2 and let me know if u face any simular issues.
---------- Post added at 10:14 AM ---------- Previous post was at 09:58 AM ----------
Dossey said:
HD Brian,
I'm going to say thanks because I'm sure everything you just posted is probably going to be very clear to quite a few people that understand all of that. So thank you for helping out. Unfortunately though for me, I got lost. Though I've been tinkering with android and windows mobile devices for about 3 years now, I've actually never done any ADB editing and not sure I fully understand how to do it.
Personally I'm not too concerned about modifying these things too much because they are for someone else's kids, and I've found a way to work around rooting and using Gapps to be able to install the apps they're needing. And before I hand these things back over to be wrapped for Christmas I'm going to make a video showing what I've done to maximize the out of box potential of these things.
But on that note, I'm going to make a request of you if you don't mind. Considering you seem to know how to easily achieve the task, I was wondering if you'd be willing to make and post a Youtube video that takes people through the steps. I know it might be time consuming, but after all we are all here to help each other out. And I'm sure that the people who actually own these devices would really appreciate it. At this point I haven't been able to find any videos on how to mod this tablet yet and the only forums that I've found discussing these things are the one you mentioned and this one here.
So I hope you'll be willing to help other owners out, and I appreciate you taking the time to respond.
Thanks
Click to expand...
Click to collapse
Hey I just wanted to point out that you can indeed use root and remount /system. if you have proper root. which my AIO application will test for you as well. Here's what you do to remount /system as r/w:
Code:
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/app
chmod 777 /system/app
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\dev\adb>adb push sample.apk /system
/app/sample.apk
12 KB/s (187 bytes in 0.015s)
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /system/app
chmod 755 /system/app
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ #

I was able to get the play store on with the first upload and then by following a couple of steps from aother tutorial, but I can't seem to get any apps in the Play Store to open or download. I keep getting a "device is not compatible" message. I've tried the DPI play store and also messed around with LCD Density Monitor but haven't had any luck. If someone could help tackle this problem as well as get netflix up and running, I would be extremely grateful. This seems like a pretty awesome tablet, it just needs to be let free.
I feel I should also add, for anyone considering doing this, that once you have the Play Store installed, at least in my experience; if you have it hooked up to a PC via the USB and try to install anything, it goes ape sh** and starts trying to force close and kicks a whole bunch of errors. It doesn't seen to do anything, but it's annoying as hell. I haven't tried it yet with it plugged into the charger, and it doesn't do it nearly as much when you have it unplugged, but it's just another one of those quirks that I'm sure will be fixed in due time.
TeODH4 said:
Sorry about the black screen issue guys there was an issue with the code. I've also completely rewritten the application in c++. All features should work without issues now.
You can download the software here: mediafire [dot] com/?o2864kb92hcc0hb (sorry i can't post links yet, I'll work on getting some posts done...)
1) Download RAR file
2) Extract RAR file
3) Run PolaroidAIO.exe
4) Enable USB debugging and Stay awake
5) Drivers are included in this release if needed
6) Enjoy your fully rooted tablet with the Play Store and Google Services Framework.
If anyone is intrested in the source code let me know and I will post it as well...
Have fun guys!
---------- Post added at 09:58 AM ---------- Previous post was at 09:26 AM ----------
There was a bug in the old code, same thing happend to mine after i did a factory reset to try and replicate your situation. Try the updated version 1.2 and let me know if u face any simular issues.
---------- Post added at 10:14 AM ---------- Previous post was at 09:58 AM ----------
Hey I just wanted to point out that you can indeed use root and remount /system. if you have proper root. which my AIO application will test for you as well. Here's what you do to remount /system as r/w:
Code:
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/app
chmod 777 /system/app
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\dev\adb>adb push sample.apk /system
/app/sample.apk
12 KB/s (187 bytes in 0.015s)
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /system/app
chmod 755 /system/app
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ #
Click to expand...
Click to collapse

Just to be sure you may want to run the updated script because there was alot of garbage left behind by 1.0. which 1.2 will clean up.
1) Select "Remove Google Applications and Framework"
2) When done, select "Un-Root Device"
3) Finally select "Root Device and Install Google Applications, and Framework"
This will clean up the garbage left behind by 1.0 and might help with some of your issues.
I am aware that some apps are showing up as un-supported, I'm pretty sure its an issue with build.prop. I'm looking into it right now. Are you having issues with all the apps on the play store? or just some of them like netflix, angry birds, etc? Also can you elaborate on what errors you are getting? I think i need to find an updated version of google services framework, I've noticed when the market upgrades to the play store it will crash quite a few times during the updates, and then gets better but does crash from time to time. Don't hurt functionality but it is very annoying.
If you find any info on any of this please be sure to share. I'll try and get an updated release out tonight that takes care of at least some of these issues... At least we are making progress...

I downloaded the files from location listed above but it my anti virus primped me for a Trojan virus... Is this not a secure release?

psctornado said:
I downloaded the files from location listed above but it my anti virus primped me for a Trojan virus... Is this not a secure release?
Click to expand...
Click to collapse
This is a secure release, it probably doesn't like all the files embedded into the exe... I can re-upload it un-packed if you like.

No it's ok I thought I would ask. So the big issue is the play store?

psctornado said:
No it's ok I thought I would ask. So the big issue is the play store?
Click to expand...
Click to collapse
Yes, the protected applications do not show up, or if you try to use the web site, and send an app to your device it will say unsupported, I'm going to take a look at my build.prop in a little bit and see if i cant get the full market working. From what I can tell its google blocking the apps because this is a non google supported device. which is why we needed to load the play store in the first place, if you run AIO 1.2 you will at least get all Googles app's working... Gmail, etc. I will have an update out soon to fix the play store issues, and hopefully fix the crashing gapps service...

Okay. I don't have the tablet with me right now, but when I do, I'll redo everything. Also, I was able to get Netflix to work by downloading it from Amazon's App store and everything "seemed" to work. I'll have to try more testing when I get the tablet back. As far as the Play store goes, it just says that it has stopped working and has to close, and when I hit okay, the error goes away but it stays open. I'll get the exact verbatim when it pops up again. Other than that, nice work and hopefully we can work out the kinks.
TeODH4 said:
Just to be sure you may want to run the updated script because there was alot of garbage left behind by 1.0. which 1.2 will clean up.
1) Select "Remove Google Applications and Framework"
2) When done, select "Un-Root Device"
3) Finally select "Root Device and Install Google Applications, and Framework"
This will clean up the garbage left behind by 1.0 and might help with some of your issues.
I am aware that some apps are showing up as un-supported, I'm pretty sure its an issue with build.prop. I'm looking into it right now. Are you having issues with all the apps on the play store? or just some of them like netflix, angry birds, etc? Also can you elaborate on what errors you are getting? I think i need to find an updated version of google services framework, I've noticed when the market upgrades to the play store it will crash quite a few times during the updates, and then gets better but does crash from time to time. Don't hurt functionality but it is very annoying.
If you find any info on any of this please be sure to share. I'll try and get an updated release out tonight that takes care of at least some of these issues... At least we are making progress...
Click to expand...
Click to collapse

rysimpson318 said:
Okay. I don't have the tablet with me right now, but when I do, I'll redo everything. Also, I was able to get Netflix to work by downloading it from Amazon's App store and everything "seemed" to work. I'll have to try more testing when I get the tablet back. As far as the Play store goes, it just says that it has stopped working and has to close, and when I hit okay, the error goes away but it stays open. I'll get the exact verbatim when it pops up again. Other than that, nice work and hopefully we can work out the kinks.
Click to expand...
Click to collapse
If the play store is just crashing then i would most definitely recommend using 1.2 to clean things up and reload the playstore, you may even want to go as far as to do a factory reset after you un-install and un-root... Well for some reason build.prop doesn't seem to change anything on the market, I'm downloading an updated gapp for 4.0.3 maybe that will take care of some issues under the hood.

TeODH4 said:
If the play store is just crashing then i would most definitely recommend using 1.2 to clean things up and reload the playstore, you may even want to go as far as to do a factory reset after you un-install and un-root... Well for some reason build.prop doesn't seem to change anything on the market, I'm downloading an updated gapp for 4.0.3 maybe that will take care of some issues under the hood.
Click to expand...
Click to collapse
So are you saying a clean install will remedy the issue?what is the 1.2 download link?

psctornado said:
So are you saying a clean install will remedy the issue?what is the 1.2 download link?
Click to expand...
Click to collapse
Sorry for the late response, but it should fix some of the issues. See the thread below for more info on current bugs...
I will now be posting all project updates and downloads here: http://forum.xda-developers.com/showthread.php?t=2066041

BigT504 said:
Any luck with this script yet? Also, how were you able to flash back to factory?
Click to expand...
Click to collapse
I haven't tried the new version yet since I don't have my laptop with me right now but I'll try it later. To reset back to factory after getting stuck on the black screen follow this sites direction. You will need a micro SD card. southerntelecom dot com / polaroidsupport / firmware /firmware_guide_ptab8000 dot html then download the files for your model and then put them on the SD card and insert the SD card in the tablet. Then to start the factory reset hold down volume down and power at the same time until you see the update screen come up. I believe that is what it said. It should explain it all in the link. If my link won't post since I'm new just Google ptab8000 firmware and click on the link for a southerntelecom firmware site.

[Working]Root Kindle Fire HD8 6th Gen

Ladies and Gentleman,
I was able to root the HD8 6th Gen using Kingoroot while in airplane mode. I download the executable and ran it directly from my computer. My Fire tablet is on version 5.3.1.1 and was never registered with Amazon. I can run su in adb but the SuperUser app is not working on my tablet. I am looking into replacing the KingoRoot SuperUser app with SuperSU. I suggest you block updates as soon as you achieve root.

look at this thread to see if you can remove Kingroot and replace
https://forum.xda-developers.com/am...rtool-root-t3272695/post69855730#post69855730
This applied to 7" but may be same issue you are having. Note I would suspect you at least need to install the app since you used the PC version but then that might allow replacement fully. The Rootjunky script basically installs supersu and removes the kingroot app following this approach: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
So now the questions are:
* Does the app work too or just PC version
* Does a device which has been used and registered with Amazon work? I am on 5.3.1.1, have OTA disabled, have Novalauncher sort of working, and managed to get Amazon to disable the ads lock screen but right now the device does not leave home due to Opendns constraints as I did not want to lose 5.3.1.1 while waiting.

Decided to try this on 5.3.2.1, ran Kingroot for PC few times (version 3.4.0 build 1142). Did not work. Hope it works for you 5.3.1.1 guys.

I believe 5.3.2 can be downgraded to 5.3.1.1 but I also believe 5.3.2.1 is confirmed to not be downgradable.
I was lucky and got my BF unit with 5.3.1.1 and blocked OTA right away

I register to reply this thread and tell everyone that 5.3.1.1 CAN BE ROOT using KingoRoot(not KingRoot)
blocked OTA and planning to place Kingoroot with Supersu now.
go kingoapp.c0m(replace 0 with o) and download the PC one.
Tried APK one but seems stuck at 90% or not enough patient?
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
chemie99 said:
look at this thread to see if you can remove Kingroot and replace
https://forum.xda-developers.com/am...rtool-root-t3272695/post69855730#post69855730
This applied to 7" but may be same issue you are having. Note I would suspect you at least need to install the app since you used the PC version but then that might allow replacement fully. The Rootjunky script basically installs supersu and removes the kingroot app following this approach: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
So now the questions are:
* Does the app work too or just PC version
* Does a device which has been used and registered with Amazon work? I am on 5.3.1.1, have OTA disabled, have Novalauncher sort of working, and managed to get Amazon to disable the ads lock screen but right now the device does not leave home due to Opendns constraints as I did not want to lose 5.3.1.1 while waiting.
Click to expand...
Click to collapse
my device is registered with amazon and it works
Detailed instruction on post#38

so what is difference between
kingoroot
and kingroot
??
I am familiar with Kingroot but kingoroot seems to be another animal? Is kingo safe? We have a total of 3 lifetime posts from two accounts who are speaking its benefits....

chemie99 said:
so what is difference between
kingoroot
and kingroot
??
I am familiar with Kingroot but kingoroot seems to be another animal? Is kingo safe? We have a total of 3 lifetime posts from two accounts who are speaking its benefits....
Click to expand...
Click to collapse
honestly I dunno, I'm new to android, just bought the kindle to start playing with android...
but I found it difficult to replace the kingoroot with supersu, when I type su in terminal, it show nothing, can't give root permission to terminal emulator.

I replaced kingoroot with supersu following instruction from androidforums.com/threads/script-replace-kingoroot-with-supersu.919175/
After it's done, supersu doesn't prompt for root access. So I set 'default access' to 'grant' in supersu settings, and it seems to be working.

g4ry12 said:
Decided to try this on 5.3.2.1, ran Kingroot for PC few times.
Click to expand...
Click to collapse
I was not paying attention, it's KingoRoot, not KingRoot. Downloaded KingoRoot for PC (v1.4.9), and tried on 5.3.2.1. Rooting failed, unfortunately.

I ran the PC kingo and rooted.
I then tried to remove and replace with supersu and it failed
I lost root
I tried to rerun Kingo PC but it wanted debugging enabled even though it was
tried the apk kingo (from kingoapp.com; playstore it is a adware hack)
got stuck at 90%
exited and kindle was really sluggish; maybe something to do with my novalauncher or something?
power off reboot and stuck in boot up (Fire image). Now can't boot.
Message is be careful with kingo when removing....will try restore now.
Edit: wiping data and cache did not help. Did brick recovery to 5.3.1.1 (which is what it was on when I got it), and managed to recover. Glad I don't have to send this one back to Amazon!
I will now restart kingo root effort and if it works will report back steps (including supersu replacement).

So I have root according to kingo but "root checker basic" says I do not have root.
Try to open "superuser" (which is a kingo superuser app) and it is just a blank screen then back to Home.
The removal tool that @2ig2ag linked did not work.
It failed on "mount -w -o remount /system" with "mount: operation not permitted"
I also tried to manual cp the su file over and get error "read only file system"
Edit: Despite kingo saying you have root, you don't. At least not complete root. I am unable to copy anything into system/app via ES File explorer too. I am unable to grant programs that want access, that access. For example, Titanium BackUp is unable to detect "Su and Busybox" so no go.
I am able to pm disable the firelauncher for example but that is about it

chemie99 said:
So I have root according to kingo but "root checker basic" says I do not have root.
Try to open "superuser" (which is a kingo superuser app) and it is just a blank screen then back to Home.
The removal tool that @2ig2ag linked did not work.
It failed on "mount -w -o remount /system" with "mount: operation not permitted"
I also tried to manual cp the su file over and get error "read only file system"
Edit: Despite kingo saying you have root, you don't. At least not complete root. I am unable to copy anything into system/app via ES File explorer too. I am unable to grant programs that want access, that access. I am able to pm disable the firelauncher for example but that is about it
Click to expand...
Click to collapse
I soft-bricked once, stuck at fire logo, sideload adb and resumed normal.
I didn't use the root checker to check, the superuser included will crash when I launch it,
but I can su in adb shell..
@2ig2ag's way not work for me either,
I cannot run the script, it said permission denied, then I try to run it manually,
I can remount /system, it do not show any error, but I am stopped at "cp ./su /system/xbin/daemonsu",
it said "daemonsu" text file in use.

tried ultra explorer as another way to get to /system and it just locks up when trying to detect root.
Tried manually installing supersu.apk and it locks up and requires reboot to get back to working device.
@phpbb88 I retried "mount -w -o remount /system" and it worked; maybe I wasn't in su at the time. I get the same error on file copy
So to summarize:
you can: adb su
you can: pm disable fire launcher and OTA (not sure if unrooted allows this too?)
you can not:
write to /system
install any apk that require root and grant root access
switch to supersu
adb remount (fails)
I would not call this a successful root. I am not even sure of the pm disables will last more than 24 hours.

chemie99 said:
tried ultra explorer as another way to get to /system and it just locks up when trying to detect root.
Tried manually installing supersu.apk and it locks up and requires reboot to get back to working device.
@phpbb88 I retried "mount -w -o remount /system" and it worked; maybe I wasn't in su at the time. I get the same error on file copy
So to summarize:
you can: adb su
you can: pm disable fire launcher and OTA (not sure if unrooted allows this too?)
you can not:
write to /system
install any apk that require root and grant root access
switch to supersu
adb remount (fails)
I would not call this a successful root. I am not even sure of the pm disables will last more than 24 hours.
Click to expand...
Click to collapse
I am using a file explorer called "ES File explorer", it cannot view the system file when it is not root.
After Kingoroot, I can view them, but I still cannot create file in /system by using that File explorer.
However I can successfully create a dir in /system in adb shell, shown below.
[email protected]:/system # mkdir 123
[email protected]:/system # ls
123
app
bin
build.prop
data
etc
fonts
framework
lib
lib64
lost+found
media
priv-app
recovery-from-boot.p
sbin
security
sqfs
tts
usr
vendor
xbin
[email protected]:/system #

I have made progress...with kingo install I did this:
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!''
edit:
but do I have root?
Titanium backup still fails but ultra explorer does say it has root
now adb shell su fails.....

chemie99 said:
I have made progress...with kingo install I did this:
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 root with supersu!
Titanium backup still fails but ultra explorer does say it has root
Edit: hmmm..
now adb shell su fails.....
Click to expand...
Click to collapse
I cannot run the step1.sh, still show permission denied.
I tried manually, but got another permission error...
[email protected]:/sdcard/Kingo # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo # daemonsu -d &
[1] 8434
[email protected]:/sdcard/Kingo # ./step1.sh
sh: ./step1.sh: can't execute: Permission denied
[1] + Done daemonsu -d
126|[email protected]:/sdcard/Kingo # cp ./su /system/xbin/su
[email protected]:/sdcard/Kingo # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo # ./chattr.pie -ia /system/xbin/ku.sud
sh: ./chattr.pie: can't execute: Permission denied
126|[email protected]:/sdcard/Kingo # ./chattr.pie -ia /system/xbin/supolicy
sh: ./chattr.pie: can't execute: Permission denied
126|[email protected]:/sdcard/Kingo #

after the errors, did you install supersu.apk?
I ignored the errors thinking they were from differences between kingo apk and kingo PC versions of what they put on device.
Supersu does manage to install itself but root checker still says I do not have root.

chemie99 said:
after the errors, did you install supersu.apk?
I ignored the errors thinking they were from differences between kingo apk and kingo PC versions of what they put on device
Click to expand...
Click to collapse
I didn't finish all the steps in step1.sh, cause I have installed SuperSU at the beginning of time,
I then try to run Supersu and it said blahblahblah error, need to reboot my device.
wola, i lost my connection to root adb shell, and now going to root it again

phpbb88 said:
I didn't finish all the steps in step1.sh, cause I have installed SuperSU at the beginning of time,
I then try to run Supersu and it said blahblahblah error, need to reboot my device.
wola, i lost my connection to root adb shell, and now going to root it again
Click to expand...
Click to collapse
I only install supersu as the step after running step1; it worked, and took hold (at least no errors and opening the program looks normal). The issue is that it won't grant access to anything (TB, flashfire, etc)

chemie99 said:
I only install supersu as the step after running step1; it worked, and took hold (at least no errors and opening the program looks normal). The issue is that it won't grant access to anything (TB, flashfire, etc)
Click to expand...
Click to collapse
Kingoroot PC asked me to grant root access to it by pressing OK on my device's pop up when my device is under root,
but my device wouldn't show anything.
Is there any problem on fire OS that wouldn't show this pop up?

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