I have been watching Kingo Root for awhile and I just noticed they added Amazon devices to their list of compatible devices. Its a PC root so you would need to attach the fire TV to your PC. I do not have a cord to do so, but its worth a try.
Also, I know windows notices the Fire TV, but not sure what driver is needed. If anyone has any details on an Amazon device driver for windows, please let us know.
If anyone tries Kingo Root, please report back.
Please do not talk about how to get Kingo Root to work if does not work, cause if it doesn't work it just doesn't work. Please no getting mad about anyone else's comments, cause everyone has a voice.
There is also Root Genius that roots a lot of devices, but I do not know if it has worked on any Amazon devices.
OK here's a quote from Amazon.com about installing the USB drivers for the Fire TV
"The USB driver for the Fire tablets also works with Fire TV."
So I guess all you have to do is install the Fire tablet driver.
porkenhimer said:
OK here's a quote from Amazon.com about installing the USB drivers for the Fire TV
"The USB driver for the Fire tablets also works with Fire TV."
So I guess all you have to do is install the Fire tablet driver.
Click to expand...
Click to collapse
Not sure I'm much help here. I have rooted aftvs and don't really want to mess with them. However, I did try it once with my aftv stick with no usb drivers installed.
At first it said to enable usb debugging (which pretty sure isn't an option on stick)
Then it recognized the device as aftm
It started checking root status and downloading scripts but it just repeated that loop for about 10 minutes.
I'm willing to try again later. In the mean time if anyone has a link for drivers please post. It'll save time hunting them down. I actually have them on my Mac.
But this does seem more likely to work on the box since you can enable usb debug there.
KLit75 said:
Not sure I'm much help here. I have rooted aftvs and don't really want to mess with them. However, I did try it once with my aftv stick with no usb drivers installed.
At first it said to enable usb debugging (which pretty sure isn't an option on stick)
Then it recognized the device as aftm
It started checking root status and downloading scripts but it just repeated that loop for about 10 minutes.
I'm willing to try again later. In the mean time if anyone has a link for drivers please post. It'll save time hunting them down. I actually have them on my Mac.
But this does seem more likely to work on the box since you can enable usb debug there.
Click to expand...
Click to collapse
Just google "Fire HD USB Driver". Download and install it. If your computer notices your device then USB debugging should be working or it wouldn't notice your devices.
Tried again same result except this time I put the stick back in the tv. It actually installed kingo root on it. So I launched it. There's nothing to click and it says usb not connected. So I plugged the usb into my computer. In the kingo app on tv it says "rooting..." but on the pc it just repeats the same loop as last time.
There's no fastboot on stick. The box would at least have a chance of working. I think that's why it can't reboot which it needs to do during the process.
KLit75 said:
Tried again same result except this time I put the stick back in the tv. It actually installed kingo root on it. So I launched it. There's nothing to click and it says usb not connected. So I plugged the usb into my computer. In the kingo app on tv it says "rooting..." but on the pc it just repeats the same loop as last time.
There's no fastboot on stick. The box would at least have a chance of working. I think that's why it can't reboot which it needs to do during the process.
Click to expand...
Click to collapse
Well we now know it doesn't work on the stick. Hopefully someone tries it on the Fire TV. I noticed with Kingroot, it would say that your device may need to reboot during rooting, but I also noticed a couple times, not every time though, Kingroot would say it couldn't reboot the device. So I am guessing maybe we stumbled upon something. Maybe part of the process for some devices Is a need to be rebooted during the root process. I have seen videos where some devices would actually reboot during Kingroot and be rooted after the reboot. Maybe a dev with more knowledge on why a device would need to reboot during the root process can give us some info. Maybe the problem with the Fire TV is that Kingroot and other apps like Kingo Root cannot reboot the Fire TV, but that just an idea. It does not sound likely, but anything is possible.
I have another idea that I am not sure anyone would be willing to try. Maybe someone can run Kingroot or Kingo Root on a rooted device and see what happens. It would have to be someone that has more than one Fire TV incase they messed their device up, but I am sure it could be easily fixed by flashing a pre rooted ROM. Maybe it could give us a better idea of what Kingroot is doing and what it might take to root, if it actually worked on a rooted device.
Maybe this will help with drivers etc
https://developer.amazon.com/public/solutions/devices/fire-tv/docs/connecting-adb-over-usb
It says the stick can connect to adb via USB. Perhaps installing the correct drivers will help.
KLit75 said:
Tried again same result except this time I put the stick back in the tv. It actually installed kingo root on it. So I launched it. There's nothing to click and it says usb not connected. So I plugged the usb into my computer. In the kingo app on tv it says "rooting..." but on the pc it just repeats the same loop as last time.
There's no fastboot on stick. The box would at least have a chance of working. I think that's why it can't reboot which it needs to do during the process.
Click to expand...
Click to collapse
Back up the Kingo Root app and uplod the apk and I'll try installing it on the Fire TV box. If you don't know how to backup apps, you can do it with ES File Explorer. It says "app" under the library tab, click it and it will let you backup apps.
porkenhimer said:
Back up the Kingo Root app and uplod the apk and I'll try installing it on the Fire TV box. If you don't know how to backup apps, you can do it with ES File Explorer. It says "app" under the library tab, click it and it will let you backup apps.
Click to expand...
Click to collapse
Just got your post. This is really just the UI for your phone/tablet so you can see the progress and if it works it'll probably warn you not to disconnect the device. But here you go.
I just tried Kingo Root with an unrooted Fire TV running 51.1.5.0 over USB and it did not root the device.
Kingo Root connected fine to the Fire TV over USB and installed v1.2 of its APK onto the Fire TV. I then clicked the ROOT button on the windows app and it began to do its thing. After several minutes of letting it run, it began to just bounce back and forth between "Download dependency files" and "Checking root status". I then tried the whole process again with the v1.3 APK that @KLit75 posted with the same result.
AFTVnews.com said:
I just tried Kingo Root with an unrooted Fire TV running 51.1.5.0 over USB and it did not root the device.
Kingo Root connected fine to the Fire TV over USB and installed v1.2 of its APK onto the Fire TV. I then clicked the ROOT button on the windows app and it began to do its thing. After several minutes of letting it run, it began to just bounce back and forth between "Download dependency files" and "Checking root status". I then tried the whole process again with the v1.3 APK that @KLit75 posted with the same result.
Click to expand...
Click to collapse
I guess its case closed for unrooted Fire TVs and Fire TV Sticks. I am still wondering what kingroot or Kingo Root would do on an already rooted device. I know it sounds kinda risky, but it may actually be able to commplete its process if the device is already rooted.
KLit75 said:
Just got your post. This is really just the UI for your phone/tablet so you can see the progress and if it works it'll probably warn you not to disconnect the device. But here you go.
Click to expand...
Click to collapse
Thanks. Didn't work for me either, but it was worth a try.
AFTVnews.com said:
I just tried Kingo Root with an unrooted Fire TV running 51.1.5.0 over USB and it did not root the device.
Kingo Root connected fine to the Fire TV over USB and installed v1.2 of its APK onto the Fire TV. I then clicked the ROOT button on the windows app and it began to do its thing. After several minutes of letting it run, it began to just bounce back and forth between "Download dependency files" and "Checking root status". I then tried the whole process again with the v1.3 APK that @KLit75 posted with the same result.
Click to expand...
Click to collapse
I had basically the same results except I let mine continue to run. It eventually said "root failed". Connected fine. One note: it did install the correct usb drivers for the Fire TV. I used version 1.3
porkenhimer said:
I guess its case closed for unrooted Fire TVs and Fire TV Sticks. I am still wondering what kingroot or Kingo Root would do on an already rooted device. I know it sounds kinda risky, but it may actually be able to commplete its process if the device is already rooted.
Click to expand...
Click to collapse
I'm not gonna have time for a little while. Both my aftvs get used a lot so I'm not willing to risk (even if its slight) losing one of them for an undetermined amount of time. If that changes and no one steps up I might reconsider. However, surely there are better eyes than mine when it comes to diagnosing what might be needed.
Here's a thought. You could email AFTVNews. He's got many aftvs, some of which he probably just uses for testing purposes. He'd also be a good resource since he has tons of experience with this device. Actually its possible he already tried this root method.
dk1keith said:
I had basically the same results except I let mine continue to run. It eventually said "root failed". Connected fine. One note: it did install the correct usb drivers for the Fire TV. I used version 1.3
Click to expand...
Click to collapse
KLit75 said:
Here's a thought. You could email AFTVNews. He's got many aftvs, some of which he probably just uses for testing purposes. He'd also be a good resource since he has tons of experience with this device. Actually its possible he already tried this root method.
Click to expand...
Click to collapse
AFTVNews is responding to this thread.
Verified it doesn't work. /thread
jpeg42 said:
AFTVNews is responding to this thread.
Verified it doesn't work. /thread
Click to expand...
Click to collapse
He may not have been paying attention to who was posting on the thread, but he was actually talking about asking him to run Kingroot or Kingo Root on an already rooted device, to see what haapens so that maybe we can figure out what they do during the root process. My thinking is that you can write to the system if you are already rooted so maybe Kingroot or Kingo Root can complete the process if the device you run it on is already rooted. Who knows, it may be hugely helpful towards achieving root if someone runs these apps on rooted devices and reports their findings, that is if it completes the process on the rooted device.
LOL! Yes it looks like he has indeed. And I'm looking pretty stupid. Am I imagining this or wasn't there a thread started by @porkenhimer last night? I must've somehow responded to a different thread thinking it was the one from last night. Anyway if he tried it on a rooted device and it doesn't bring about any new info then I guess this topic is dead.
Edit--oh I see. Aftvnews chimed in a few posts back. I was just responding to those who quoted me & didn't keep up with the thread.
AFTVnews.com said:
I just tried Kingo Root with an unrooted Fire TV running 51.1.5.0 over USB and it did not root the device.
Kingo Root connected fine to the Fire TV over USB and installed v1.2 of its APK onto the Fire TV. I then clicked the ROOT button on the windows app and it began to do its thing. After several minutes of letting it run, it began to just bounce back and forth between "Download dependency files" and "Checking root status". I then tried the whole process again with the v1.3 APK that @KLit75 posted with the same result.
Click to expand...
Click to collapse
I know doing a factory reset was tried on the Fire Stick but I didn't see where it was tried on the Fire TV (i may have just missed it) so I tried it. Did factory reset and tried Kingroot 4.0 and 4.1 with no success. Also tried the PC version of Kingroot and Kingoroot with no success. Just wanted to make sure I tried everything I could to get it to work before giving up on it. Only have one rooted Fire TV so I can't mess with that one.
Just wanted to pass on my results.
Related
when I rooted my first kindle hd, I started as if I were gonna do the manual root, making sure that I was able to read the device using windows command prompts, had some problems with the usb error and also the device manager error (which has already been covered here)
Once I got that straightened out I used the auto quemo root, and was able to root and do all the other cool stuff I wanted
Picked up a 2nd kindle hd for my mom, trying to root it and failing
I'm able to detect the device using command prompts and I can get it to show up in device manager as "android composite adb interface"
but when I do auto root, I get stuck on step 2 "cannot create/data/local.prop: permission denied"
I've tried rollingback and uninstalling then re-installing adb drivers, can't get it to work
any suggestions?
Is it because I'm trying to root a 2nd kindle on the same laptop? Do I need to delete any directory regarding adb or kindle and start from scratch?
I'm either gonna try deleting everything and starting from scratch or try the manual root, any help?
ksound said:
when I rooted my first kindle hd, I started as if I were gonna do the manual root, making sure that I was able to read the device using windows command prompts, had some problems with the usb error and also the device manager error (which has already been covered here)
Once I got that straightened out I used the auto quemo root, and was able to root and do all the other cool stuff I wanted
Picked up a 2nd kindle hd for my mom, trying to root it and failing
I'm able to detect the device using command prompts and I can get it to show up in device manager as "android composite adb interface"
but when I do auto root, I get stuck on step 2 "cannot create/data/local.prop: permission denied"
I've tried rollingback and uninstalling then re-installing adb drivers, can't get it to work
any suggestions?
Is it because I'm trying to root a 2nd kindle on the same laptop? Do I need to delete any directory regarding adb or kindle and start from scratch?
I'm either gonna try deleting everything and starting from scratch or try the manual root, any help?
Click to expand...
Click to collapse
i noticed today I recieved a system upgrade to 7.2.2 on my formerly rooted Kindle Fire HD, which removed root access. Running autoroot gives me exactly the same error as yourself. Looks like amazon has shut off that route?
wrexhamafc said:
i noticed today I recieved a system upgrade to 7.2.2 on my formerly rooted Kindle Fire HD, which removed root access. Running autoroot gives me exactly the same error as yourself. Looks like amazon has shut off that route?
Click to expand...
Click to collapse
yeah I had meant to mention that, my other one is running 7.2.1
gonna try resetting to factory defaults on the new one and see if I can root it that way
eta- nope restes to 7.2.2 and still no root
never mind I figured it out
I just recently did a manual update of my Note 3 with Odin and am now on MJE. Every time I plug the Note in and run Kingo Root it never recognizes the phone but the computer does!
I have tried using a different USB port, re-installed Kingo, I'm sure my drivers are correct because again, I can connect to the PC with no problem.
Anyone have any idea how to get Kingo going? I am familiar with it since I used it to root my Note 3 when on MJ7 previously.
PLEASE HELP! I have a lot of apps that depend on root access that now I can't run any more.
Thanks.
P.S. - Sorry if this has already been covered somewhere here on the forum. I did several searches but came up with nothing.
What worked for me was turning on automatic updates in windows. I always have it disabled so I can control the windows update process.
Sent from my SM-N900V using XDA Premium 4 mobile app
Reilly1812 said:
What worked for me was turning on automatic updates in windows. I always have it disabled so I can control the windows update process.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info. I'm currently at work, and it appears that Windows automatic updates are already on and set to update once every week. However, all of these settings are actually greyed out so I assume that only my administrator can make any changes to these settings.
When I used Kingo before I was at home, so maybe I'll have more luck when I get there but surely welcome yours and anyone else's ideas on this.
See if vroot will do the job for you.
I'm having a Similar issue, I have the MJE update, however no matter what I do, I'm getting a "Not Support" error when trying to root, and I've tried multiple cables, ports, and two PCs now, getting the exact same error. I googled around but wasn't able to see ANYONE with this error, and all Kingo says to do is keep trying when the root fails.
Edit: i've even tried wiping my phone and resetting to defaults, but still, i get this error, my PC at home was windows 8 enterprise, and the PC i tried at work was XP, i'm going to try a win7 PC next, but this is really frustrating.
In the same boat, for the most part.
Got the phone three days ago. Shipped with MI9. Odined to MJE.
Tried every combination of Kingo 1.1.6, 1.1.7 and 1.1.8, along with several cords, all available USB2 and USB3 ports, along with setting the phone up as MTP, PTP and Media device USB3 mode. USB debugging is ON, every PC given authority on the phone popups. Unknown sources CHECKED. Antivirus off on PC. Display on phone set to 10 minutes. Rebooted phone and PC between installations of Kingo, between attempts at rooting, between driver installations and uninstallations. Let Kingo install drivers, pre-installed through XDA links to drivers on Sam's site. You name it, I've tried it. In all, I've spent about 4 hours trying over 100 permutations of variables I could think of. Goose eggs.
ZachPA said:
In the same boat, for the most part.
Got the phone three days ago. Shipped with MI9. Odined to MJE.
Tried every combination of Kingo 1.1.6, 1.1.7 and 1.1.8, along with several cords, all available USB2 and USB3 ports, along with setting the phone up as MTP, PTP and Media device USB3 mode. USB debugging is ON, every PC given authority on the phone popups. Unknown sources CHECKED. Antivirus off on PC. Display on phone set to 10 minutes. Rebooted phone and PC between installations of Kingo, between attempts at rooting, between driver installations and uninstallations. Let Kingo install drivers, pre-installed through XDA links to drivers on Sam's site. You name it, I've tried it. In all, I've spent about 4 hours trying over 100 permutations of variables I could think of. Goose eggs.
Click to expand...
Click to collapse
I'm wondering if where it pulls files it needs is having issues or something and isn't pulling the dependencies we need to properly root?
So it's not just me. Bummer
int3gr4l said:
I'm wondering if where it pulls files it needs is having issues or something and isn't pulling the dependencies we need to properly root?
Click to expand...
Click to collapse
And yet, there are plenty of reports here and elsewhere of folks with Verizon Note 3's on MJE having no troubles at all rooting using Kingo. FMITGA.
ZachPA said:
And yet, there are plenty of reports here and elsewhere of folks with Verizon Note 3's on MJE having no troubles at all rooting using Kingo. FMITGA.
Click to expand...
Click to collapse
That's why I'm curious if their site is having issues with us downloading the files using the root. It fails for me with the not support error immediately after saying downloading the dependencies.
Just some added confusion... I did the same method... Odin to MJE... Root with kingo... Get same fail message... Try again but this time noticed that it actually rebooted the phone... Same fail message again... Check with root checker and I'm rooted... Install safestrap and update superSU... Good to go... Kingo says fail but I'm rooted and all root access apps working and rom slots flashed.
Lucky SOB.
Sent from my SM-N900V using xda app-developers app
having the same issue here. just got my note yesterday and been trying but no luck. getting NotSupport right after the 2nd "downloading requisite dependency files". would love some insight on this.
privy said:
having the same issue here. just got my note yesterday and been trying but no luck. getting NotSupport right after the 2nd "downloading requisite dependency files". would love some insight on this.
Click to expand...
Click to collapse
I really am wondering if it's the Kingo site. Whenever I try to navigate to the site it's taking quite a long time to load, as if they're having some issues with hosting, and when it goes to download the second set of files, it's unable to get through to the site to pull them.
Same here Privy
Sent from my SM-N900V using xda app-developers app
I had this issue when using a USB 3.0 port. Once I switched to USB 2.0, my device was recognized by the software.
Sent from my SM-N900V using Tapatalk
Same issue here, was having some issues with play store so back to stock with odin. Tried everything just like everyone else here. It has to be an issue with the kingo site. Redownloaded kingo and it tool an hour. Thats way too long and i bet root is timing out. Has to be it, at least i hope so.
Just an FYI I was on the stock OTA MJE with my note 3 and I rooted with Kingo and it literally worked the very first time I did it. Click, click boom rooted. Couldn't of been easier.
Point being it's doable on the rom, and easily. So keep it up
Sent from my SM-N900V using Tapatalk
The first time I rooted with no problem but after I went back to stock with odin I can no longer root with Kingo.
Just got my Note 3 yesterday, and have spent easily an hour installing and reinstalling drivers trying to get Kingo to work, but no luck.
As privy said: "having the same issue here. just got my note yesterday and been trying but no luck. getting NotSupport right after the 2nd "downloading requisite dependency files". would love some insight on this."
That's exactly the issue I'm having too.
Hey all OUYAins!
So recently I updated my OUYA to Chickcharney and lost root access *cue crying*
I tried installing RootMyOuya1.1 by WonderEkin but it didn't install. So I snooped around for different rooting methods such as ReRoot script by Eldon McGuiness (You can take a look at his script here).
The method that worked perfectly fine for me was to download a piece of software called Kingo (here). Simply download and install it and connect your OUYA to your computer via USB and click Start Root. Wait for the software to root your OUYA and it will eventually reboot. You should now have SuperSU installed with root access!
I hope this thread helps anyone having difficulty with getting root access on Chickcharney!
I'm assuming the device needs to already have been rooted prior to trying Kingo ROOT? I just got my system on Thursday and since I'm new it forced me to download the Chickcharney update and I can't figure out what the best way is to root my OUYA.
i just got one on friday and the same thing it updated automatically
i use this to root my system it still works
http://forum.xda-developers.com/showthread.php?t=2350900
my ouya was rooted before the update. yesterday I tried Kingo and it said "already rooted", but I had no root permission. So I clicked "root again" and after a minute or so my ouya was rooted again properly.
Thanks Sn0wdune
joserod1980 said:
i just got one on friday and the same thing it updated automatically
i use this to root my system it still works
http://forum.xda-developers.com/showthread.php?t=2350900
Click to expand...
Click to collapse
I tried that to root it but it said it couldn't find the Ouya. I'm running the latest update Chickcharney on mine. Do I need to wipe it to run the root?
circledrag said:
I'm assuming the device needs to already have been rooted prior to trying Kingo ROOT? I just got my system on Thursday and since I'm new it forced me to download the Chickcharney update and I can't figure out what the best way is to root my OUYA.
Click to expand...
Click to collapse
Well not neccessarily. It should still work in any case!
circledrag said:
I tried that to root it but it said it couldn't find the Ouya. I'm running the latest update Chickcharney on mine. Do I need to wipe it to run the root?
Click to expand...
Click to collapse
That's odd. Are you sure you have your OUYA connected via USB properly and the drivers are correctly installed?
Sn0wdune said:
Well not neccessarily. It should still work in any case!
That's odd. Are you sure you have your OUYA connected via USB properly and the drivers are correctly installed?
Click to expand...
Click to collapse
The driver's wouldn't install because I had to turn off driver signing. I got it working after that with Ouya Toolbox root... even though it was crashing part way through. I had to run the TEST version of Ouya Toolbox and just forced the root and I guess it was fine because it appears to be rooted.
I tried the OS 4.5.2 rooting from the forum and that did not work. I tried KingRoot and its works. Can someone test this on OS 4.5.3 or higher OS please
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Sent from HDX 7 OS 4.5.2 Rooted
Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.
Sometimes you have to tried several times the last time I fail too but the second works. I dont know what cause it
Sent from HDX 7 OS 4.5.2 Rooted
PsymH said:
Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.
Click to expand...
Click to collapse
From what I've heard, 4.5.4 can't be rooted. If you have a 3rd generation HDX, then you have to first downgrade to 3.2.8 and then manually update to 4.5.2.
Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.
rabaker07 said:
Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.
Click to expand...
Click to collapse
You obviously understand the risk and assume you tried alternate (Moto) drivers along with different cables and host ports to confirm diagnosis. Note cables/ports that work on one device may not on another - especially finicky HDX hardware.
You're probabky not going to get a high confidence response to your KingRoot question as most take the full step of unlocking. Plus age of device and waning interest. Good luck.
Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul. The risks come in when you attempt to flash a ROM and it fails by partially loading and overwriting/erasing critical files without completing (loss of power mid flash!) or if the ROM is incompatible in some way and you are unable to flash your previous ROM. That's where bootloader recovery software comes in (TWRP and the like). So that you can access the system before loading (or failing to load) the ROM, and flash over it or flash a backup.
Moral of the story is that YES, Kingroot works on HDX 3rd Gen on 4.5.5.3. I tried it last night and it worked. I now have access to the root directory. Oh, the places you'll go!!
Sent from my Pixel 2 XL using Tapatalk
rabaker07 said:
Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul.
Click to expand...
Click to collapse
Nope; root attempts can yield a bootloop or otherwise dysfunctional device. Glad all worked out for you.
Ouch. I didn't realize that. It always seemed very benign and I've never had it go wrong. I guess I'm used to devices that are designed to be accessible. Fortunately my HDX rooted without a hitch.
A contributor is reporting success rooting 5.3.2.1 with Kingroot. No immediate confirmation...simply reposting for visability and comment. Report your results here for community benefit.
https://forum.xda-developers.com/am...-5th-gen-supertool-root-t3272695/post70784402
Reminder: Do not attempt to rollback FireOS 5.3.2.1; you will likely be rewarded with a brick.
No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.
stonedpsycho said:
No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.
Click to expand...
Click to collapse
Not having any luck with it either.
This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.
TechDad378 said:
This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.
Click to expand...
Click to collapse
Are you sure it was 5.3.2.1 you where on ? I only ask because downgrading to 5.3.1 from 5.3.2.1 should result in a brick as the boot loader used in 5.3.1 and 5.3.2 changed from on 5.3.2.1 and the anti-roll back measure amazon have should have kicked in to give you a brick.
How did you roll back ? Through ADB or placing the update file in the internal SD ?
Correct it was 5.3.2.1. While playing around with it I hit a black screen while booting. Upon reading some posts, I thought there was no return because of the version. Since the device responded via usb on pc, adb sideload worked causing downgrade to work.
Don't get me wrong this may have been just pure random luck. But hopefully my results my lead to "Fire Lineage OS".
No luck with this method. Will keep trying.
Zero Luck yet as well. Will try again. Hopefully something more reliable will come about soon.
Sorry to hear you have had no success. Will revert everything back and document each step. Once the method has been identified as successful, the information will be provided.
You still need to provide us with one of the most important tips, what version of kingroot you are using.
Thank you
TechDad378 said:
... But hopefully my results my lead to "Fire Lineage OS".
Click to expand...
Click to collapse
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.
If someone succeeds, could they try to post the kmPlugins.zip from their downloads folder? If we can get that from a successful root, then we could probably skip all the repeated failures and just get KingRoot to use that method immediately.
What ever happened to the guy that had rooted it? I knew he was bs.
Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Hmm...
Interesting response.
With a full time job and a family, this is a hobby I do for fun in my spare time. Most mods are done with patience and diligence.
Recommending following command,
C:/yourself/ adb sideload patience.zip
---------- Post added at 03:20 AM ---------- Previous post was at 03:09 AM ----------
Davey126 said:
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.
Click to expand...
Click to collapse
Point taken. Just hoping LineageOS will be as widespread.
As for the root, I reverted back to original. Trying to recreate the environment which allowed success.
Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Nice. If you bothered to read his post history you might think differently. Well presented/documented with all the appropriate caveats.
Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
What a shame that people can't be considerate online anymore.
@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this
5.1.4 Rooted !!!!!
Mr McBoatface said:
@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this
Click to expand...
Click to collapse
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.
Mr McBoatface said:
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.
Click to expand...
Click to collapse
Nice! While you can downgrade 5.1.4, this mean it may be possible to root without using a PC to downgrade first. I'm going to try on 5.3.2.1, and see how it works.
Sent from my Amazon Fire using XDA Labs
Repeated root on 5.1.4, replace the kingroot in supertools with the "NewKingrootV5.0.1_C165_B377_xda_release_protected _2016_12_22_20161222120332_105243_signed.apk" version and ran the script.
It needed 2 attempts this time but it rooted. The supertools script removed it and replaced with supersu.
See attached video in zip to confirm