Related
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.
Kingroot now roots 5.3.1!
If you are having trouble installng cm 12.1, try the supertool or @wtfjajaja's instructions.
wtfjajaja said:
try it a few times, i encountered the same problems as well
here's what i did
1. factory reset through recovery
2. root with kingroot, (it worked for me after 2 to 3 tries)
3. installed supersu-me 6.7
4. update su binary
it's important here! don't restart yet, my device bricked few times here
5. install flashfire 0.53
6. follow the steps to install cm12.1 under flashfire from here
7. enjoy
Click to expand...
Click to collapse
Supertool: http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Bricked?: http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Fingers crossed! I can't wait to start flashing roms!
If you're root then maybe you can use flashfire to flash a rom just like 5.1.2
tonibm19 said:
If you're root then maybe you can use flashfire to flash a rom just like 5.1.2
Click to expand...
Click to collapse
Flashfire needs supersu
or Cmsu to work.
hooks024 said:
Flashfire needs supersu
or Cmsu to work.
Click to expand...
Click to collapse
Try rootjunky's supertool after rooting to see if it can install it.
.
tonibm19 said:
Try rootjunky's supertool after rooting to see if it can install it.
Click to expand...
Click to collapse
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1
DoctorDark_ said:
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1
Click to expand...
Click to collapse
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.
marvelous news!!!
DoctorDark_ said:
Kingroot now roots 5.3.1! Hopefully someone can quickly push out a toolkit.
Click to expand...
Click to collapse
Would you add the 5.3.1 version in the title ???
tonibm19 said:
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.
Click to expand...
Click to collapse
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.
Nice I will try it out.
Good chance the latest versions of Kingroot (always evolving) will also work for those on FireOS 5.1.2.1-5.1.4. Worth a try before attempting a rollback to 5.1.2.
I couldn't get super sume to work.
not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)
ttcontributor said:
not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)
Click to expand...
Click to collapse
Not good - earlier builds of Kingroot froze around 29% before crapping out. Make sure you have the latest Kingroot app. Also try a factory reset (warning: you will loose personal apps/data) and do not register with Amazon during subsequent device initialization. This proved effective for some in the past. Recognize the community is still learning; expect some failures along the way.
Davey126 said:
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.
Click to expand...
Click to collapse
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.
-Yami- said:
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.
Click to expand...
Click to collapse
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.
Davey126 said:
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.
Click to expand...
Click to collapse
Come check my browser, I've read every single thread on the forums man, the thing is 5.1.2 is not same as 5.3.1 and device has locked bootloader and anti-rollback.
So it is not like my Motorola with unlocked bootloader, I am not sure if I always can save the device and also I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
So I had to make it clear everything works for 5.1.2 also will work for 5.3.1
Now I have to convert kingroot to supersu somehow (can't find the option under supertool like you mentioned.)
Your approach was a little bit harsh on me m8
It doesn't say "What can be done on 5.1.2 also can be done on 5.3.1" anywhere, it says the opposite everywhere.
So someone had to clear it out. Thank you for your help, It really helped me a lot.
-Yami- said:
Come check my browser, I've read every single thread on the forums man...
Click to expand...
Click to collapse
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
-Yami- said:
I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
Click to expand...
Click to collapse
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu
Davey126 said:
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu
Click to expand...
Click to collapse
The reason that I cannot return device to amazon is, shipment will cost more than the actual device from here to amazon, and I got it as a gift.
and Thanks so I missed out the part that Supertool automates the conversion when I click install Flashfire, thank you.
Now after this post everybody jumping right onto 5.3.1 root gonna know it, and the guy on first page have used Super Sume, so he probably would use
Supertool if he knew.
I've glanced at the updates for the latest Fire HD 8 2016 model, and it has version 5.3.1.1 already available :
https://www.amazon.com/gp/help/customer/display.html?nodeId=202073860
So if history is any guide, all the other Fires will see the same update real soon now ...
Use the latest Kingroot to root FireOS 5.3.1, and disable OTA !!!
http://forum.xda-developers.com/amazon-fire/general/root-t3471289
How do I remove ota Updates?
I renamed 2 APKs now when I check for updates it reports "Failed" am I Fine?
I want to switch to CM12.1 but I am afraid to try the method for 5.1.2 someone said it is the same procedure but I am not yet srue.
and I need to pay for Super Sume I guess.
so At least can someone clear out how we disable ota updates? I don't trust PM hide method, Renamed some apk but I am not sure if it worked.
-Yami- said:
How do I remove ota Updates?
I renamed 2 APKs now when I check for updates it reports "Failed" am I Fine?
I want to switch to CM12.1 but I am afraid to try the method for 5.1.2 someone said it is the same procedure but I am not yet srue.
and I need to pay for Super Sume I guess.
so At least can someone clear out how we disable ota updates? I don't trust PM hide method, Renamed some apk but I am not sure if it worked.
Click to expand...
Click to collapse
You could use rootjunky's supertool but if it already says failed it should be fine
tonibm19 said:
You could use rootjunky's supertool but if it already says failed it should be fine
Click to expand...
Click to collapse
thanks I'll go ahead and also apply rootjunkies supertool method, I wasnt sure if it gonna work on 5.3.1 so didn't try.
Just to make sure I am not letting it connect to internet, switching to CM12.1 will be the best.
-Yami- said:
How do I remove ota Updates?
I renamed 2 APKs now when I check for updates it reports "Failed" am I Fine?
I want to switch to CM12.1 but I am afraid to try the method for 5.1.2 someone said it is the same procedure but I am not yet srue.
and I need to pay for Super Sume I guess.
so At least can someone clear out how we disable ota updates? I don't trust PM hide method, Renamed some apk but I am not sure if it worked.
Click to expand...
Click to collapse
Really need to take a step back and review the documentation that has already been posted starting with the forum index . Tons of relevant material. The SuperTool should handle everything you need in advance of flashing a new ROM if that's your objective:
- SuperTool can disable OTAs, replace KingUser with SuperSU and perform a host of other useful tasks
- "renamed some apk" is not helpful; details matter
- don't need to pay for anything beyond the device itself
- if still worried about OTA updates turn off WiFi and keep reading on another device
Davey126 said:
Really need to take a step back and review the documentation that has already been posted starting with the forum index . Tons of relevant material. The SuperTool should handle everything you need in advance of flashing a new ROM if that's your objective:
- SuperTool can disable OTAs, replace KingUser with SuperSU and perform a host of other useful tasks
- "renamed some apk" is not helpful; details matter
- don't need to pay for anything beyond the device itself
- if still worried about OTA updates turn off WiFi and keep reading on another device
Click to expand...
Click to collapse
I am aware of supertool, I was not sure if it gonna work on 5.3.1 or not and someone said he switched using super sume so it was paid.
I renamed otaverifier.apk and devicesoftwareota.apk
I'll go ahead and use supetool thank you.
edit:
I got an option:
1 block OTA updates from Amazon 5.0.1
2 block OTA updates from Amazon on 5.1.1 and 5.1.2
so this was why I avoided this tool, not sure which one to use and not sure if it gonna brake something or not because I am on 5.3.1
I'll go ahead and read .bat file.
edit2:
found these lines
files\adb.exe shell pm hide com.amazon.otaverifier
files\adb.exe shell pm hide com.amazon.device.software.ota
files\adb.exe shell pm hide com.amazon.settings.systemupdates
Renamed those APKs.
but the tool also have this:
files\adb.exe shell su -c "rm -r /system/app/otaverifier"
files\adb.exe shell su -c "rm -r /system/priv-app/DeviceSoftwareOTA"
files\adb.exe shell su -c "rm -r /system/priv-app/SystemUpdatesUI"
so these are responsible APKs, I missed out "SystemUpdatesUI" on my first try thanks to this tool now I know what do rename.
I must be safe now I guess, it is not going to download and replace those bcz I didnt use PM-Hide.
edit:
I also cannot find any option to convert from kingroot to SuperSu in supertool.
at least not in its menu.
-Yami- said:
I am aware of supertool, I was not sure if it gonna work on 5.3.1 or not and someone said he switched using super sume so it was paid.
I renamed otaverifier.apk and devicesoftwareota.apk
I'll go ahead and use supetool thank you.
edit:
I got an option:
1 block OTA updates from Amazon 5.0.1
2 block OTA updates from Amazon on 5.1.1 and 5.1.2
so this was why I avoided this tool, not sure which one to use and not sure if it gonna brake something or not because I am on 5.3.1
I'll go ahead and read .bat file.
Click to expand...
Click to collapse
- devicesoftwareota.apk is the operative file; just make sure it does not end in .apk
- as noted in numerous recent posts follow the procedures for 5.1.2 with 5.3.1
- if you can read/interpret the .bat file then none of this should be a mystery; the SuperTool simply automates a number of relatively trivial tasks that can be performed manually if desired (taking nothing away from the SuperTool; it is a fantastic resource for a huge community of individuals who have benefited from the selfless individual who authored it; props to @tomstg, a.k.a. Root Junkie!).
- if you have a question, ask; just be sure you have done your homework first given the vast pool of resource that is already out there; no interest in repackging what has already been written; props to @sd_shadow who tirelessly collects information from contributors and and assembles guides for YOUR benefit.
- if still uncertain shelve the device for a few weeks until the dust settles given the recent (<48 hours old) discovery that 5.3.1 can be rooted
Can 5.3.1.1 be downgraded to 5.3.1.0?
Danny1976 said:
Can 5.3.1.1 be downgraded to 5.3.1.0?
Click to expand...
Click to collapse
Unknown but assume not unless posted otherwise. Only way to know is someone tries it and scores success or a brick.
I got my Fire HD8 (6th gen/2016) and the update for 5.3.1.1 is available. Still hasnt updated, I turned it off now. I cannot root 6th gen HD8 and I dont know of any methods that prevent the OTA update without root. Help
Edit: ops, I fail at navigating the xda forum apparently. I didn't see im in the wrong section.
I guess a benefit of the having a low end device like the Fire 7" is that they receive updates later than other devices. So you are aware of problems related to rooting early.
Anyways I ordered a Fire at Amazon Germany that arrived today and was initially shipped with Firmware 5.0.1.
I wonder why they still ship out devices with such old firmware. But tht's good for us
sebr said:
I guess a benefit of the having a low end device like the Fire 7" is that they receive updates later than other devices. So you are aware of problems related to rooting early.
Anyways I ordered a Fire at Amazon Germany that arrived today and was initially shipped with Firmware 5.0.1.
I wonder why they still ship out devices with such old firmware. But tht's good for us
Click to expand...
Click to collapse
You know the drill - root and protect that bootloader before connecting to WiFi! Or take the express route and boot directly into fastboot via <power>+<vol-down>, fire up TWRP and have your way with a custom ROM. Bounce back if you need any help with procedures.
Yeah no worries CM12 already running on it. But what is different in Bootloader versions past 5.0.1? I thought the bootloader is locked anyways - regardless of what firmware version is used - and cannot be flashed.
sebr said:
Yeah no worries CM12 already running on it. But what is different in Bootloader versions past 5.0.1? I thought the bootloader is locked anyways - regardless of what firmware version is used - and cannot be flashed.
Click to expand...
Click to collapse
5.0.x bootloader allows a custom recovery (eg: twrp) to be booted from fastboot. Nothing like a true recovery to expedite flashes and recover from missteps.
Yeah.... I wasn't able to get KingRoot to work with 5.3.1.1 and now I'm on 5.3.2 and it still won't work. I just got this tablet about a week ago. I should have rooted it before I first connected to WiFi, but I received it as a gift, so I hadn't researched the process in advance and I wasn't certain that I wanted to mess with it. I usually root my devices, but I considered leaving this one unrooted... until it was too late. Sometimes, a little hesitation makes the decision for you.
ManWithCamera said:
Yeah.... I wasn't able to get KingRoot to work with 5.3.1.1 and now I'm on 5.3.2 and it still won't work. I just got this tablet about a week ago. I should have rooted it before I first connected to WiFi, but I received it as a gift, so I hadn't researched the process in advance and I wasn't certain that I wanted to mess with it. I usually root my devices, but I considered leaving this one unrooted... until it was too late. Sometimes, a little hesitation makes the decision for you.
Click to expand...
Click to collapse
First I have heard of 5.3.1.1 and 5.3.2 for 5th gen tablets. Sure you have a 7" model (first released Sept 2015) and not the latest HD8 (released 2016)?
Davey126 said:
First I have heard of 5.3.1.1 and 5.3.2 for 5th gen tablets. Sure you have a 7" model (first released Sept 2015) and not the latest HD8 (released 2016)?
Click to expand...
Click to collapse
That's probably because the smart people on here have already blocked their updates. Yes, I confirmed that a 7" tablet is what was ordered from Amazon. It also has 2015 stamped on the back and it claims to be a 5th generation tablet in the settings. It installed the 5.3.2.0 update last night at 11:18pm.
ManWithCamera said:
That's probably because the smart people on here have already blocked their updates. Yes, I confirmed that a 7" tablet is what was ordered from Amazon. It also has 2015 stamped on the back and it claims to be a 5th generation tablet in the settings. It installed the 5.3.2.0 update last night at 11:18pm.
Click to expand...
Click to collapse
So now we know: FireOS 5.3.2 is in the wild and (apparently) can not be rooted w/KingRoot at present. What isn't known is whether 5.3.2 can be rolled back to 5.3.1 without bricking. Typically someone has to sacrifice their device (accidentally or intentionally) to determine that.
I'll create a new thread with you findings later today if someone doesn't beat me to it. Thanks for sharing.
FYI - early indications 5.3.2.1 -> 5.3.1.0 rollbacks are problematic.
http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70052733
Here as well
http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70061090
Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files
Attached a scatter file I found online for the MTK8127 chipset, which fire has. No idea if it's right. SP tool for some reason won't keep the com port open...
kaysond said:
Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files
Attached a scatter file I found online for the MTK8127 chipset, which fire has. No idea if it's right. SP tool for some reason won't keep the com port open...
Click to expand...
Click to collapse
scatter files haven't worked, with any firmware versions
Sent from my sailfish using XDA Labs
---------- Post added at 05:50 PM ---------- Previous post was at 05:47 PM ----------
see http://forum.xda-developers.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747
Sent from my sailfish using XDA Labs
Yeah, I got the READYREADYREADYREADYREADY brick that I was expecting. Three tablets, got two of them rooted and OTA blocked, then had an emergency and the third apparently wasn't actually Off so it happily ****ed me.
There's never been a recovery from the READYREADYREADY firmware loader, I'd assume? Deciding if I should keep or toss this one. At least this ****'s cheap since we don't actually own it.
I just got an Amazon Fire and am new to this whole thing. Ultimately I'd love to root it, and install a different ROM. But in the short term, I'm just playing with installing the Play Store and turning off lock screen ads. Anyway, I just opened the package up today, and I let it update itself to 5.3.2.1 before I was aware that this might cause me trouble.
I did download the SuperTool here:
http://rootjunkysdl.com/files/?dir=SuperTool
I successfully installed the Play Store. I next tried disabling the lock screen ads, but the tool said I would need to root first. When I selected the option to do that, it asked for my FireOS version, but didn't give 5.3.2.1 as an option. So I'm afraid to go through the root process.
It sounds like downgrading to an earlier version will brick this. What about rooting it with a tool like the one I downloaded? Is that likely to cause trouble as well? Is there much I can do with this currently?
There's no known way (yet) to flash 5.3.2.1 back to something earlier, that's true (and some who got hit by a brick will confirm).
There's also no known success (yet) rooting this, but since KingRoot is evolving, there may be hope. There are multiple releases of KR around, and the cloud part (where the methods are kept) seem to be constantly changing - if you decide to keep the Fire, you may as well spend some time trying to get it rooted... KR versions 4.8.5, 4.9.2, 4.9.6 have been suggested; if you decide to use KR 5, you will have to remove it from the list of device administrators before replacing it with SuperSU - of course only if you're successful. We're all waiting for RootJunky to release a new SuperTool that will possibly automate this - ATM Nov 29 is still the latest version available...
Does the RootJunky SuperTool just use KR under the hood? I'll have to keep an eye on this. I don't mind getting my hands a bit messy on this, but I don't want to be blazing a new trail. I'm not experienced enough with it. I don't mind waiting a bit to get some hand holding.
komi_9 said:
Does the RootJunky SuperTool just use KR under the hood?
Click to expand...
Click to collapse
It does:
Code:
$ grep -ri kingroot.apk .
./1-Amazon-Fire-5th-gen.bat:files\adb.exe install -r apps\Kingroot.apk
./3-Amazon-Fire-5th-gen-linux-mac.sh: sudo $ADB install -r apps/Kingroot.apk
SuperTool is a zip file - and the "magic" is done in human-readable scripts (bat or bash). Firmware bin files are zips too. Open them in your fav archive tool, and inspect what's inside.
tl;dr: ST installs whatever you put into apps/Kingroot.apk - watch out for Spelnig when replacing the version coming with ST with another one you have dl'ed from apkmirror.
hope this works! Thanks for the good work guys
dmerillat said:
Yeah, I got the READYREADYREADYREADYREADY brick that I was expecting. Three tablets, got two of them rooted and OTA blocked, then had an emergency and the third apparently wasn't actually Off so it happily ****ed me.
There's never been a recovery from the READYREADYREADY firmware loader, I'd assume? Deciding if I should keep or toss this one. At least this ****'s cheap since we don't actually own it.
Click to expand...
Click to collapse
I'm fairly certain you can still write to the flash memory from that loader, just a matter of figuring out how. There's a python script that I think will work as long as you figure out what to write...
So..there is no way to Root or downgrade 5.3.2.1??
At this moment there isn't, sorry. But tools are not static, and there's even the chance that a future fireOS upgrade will be easier to root. You've got the choice to return your Fire while/if still on warranty or wait for better days to come.
Edit: I have read rumours that KingRoot would now be able to root 5.1.3 - this, of course, may be due to the usual number confusion (and 5.3.1 was meant).
On the other hand, the patch level of 5.3.2.1 might not include DirtyCow attacks yet:
Code:
ro.build.version.security_patch=2016-10-05
and indeed I saw RootJunky add some DC stuff to his download site... There might be something around the corner, indeed.
Confirm, even hardbrick if flash from 5.3.2.1 to 5.3.2
I just used the supertool on the same model Fire tab, on 12/27/16. Here's what I've learned:
1. Amazon will indeed remove offers/ads from the discounted Fire, without cost, if you ask.
2. Supertool uses KingRoot, as of my download date.
3. Supertool was not successful in removing ads, but did install the Play Store. It did prevent OTA updates, but the root didn't work for me, so I reloaded original firmware and of course it updated right away. Next time I would try to root after registering my Fire with Amazon.
4. It aopeared to me that the Supertool attempted a downgrade (5.1.1?) before rooting, so if downgrading will brick a device running 5.3.2.1, then I think the answer to the OP's question is "no".
related question: Knowing all the above, can I still re-try the Supertool option #1, and (re)install the Play Store and remove ads? (I bought 3 of them Amazon removed ads on 1 of them so far.))
rallison203 said:
I just used the supertool on the same model Fire tab, on 12/27/16. Here's what I've learned:
1. Amazon will indeed remove offers/ads from the discounted Fire, without cost, if you ask.
2. Supertool uses KingRoot, as of my download date.
3. Supertool was not successful in removing ads, but did install the Play Store. It did prevent OTA updates, but the root didn't work for me, so I reloaded original firmware and of course it updated right away. Next time I would try to root after registering my Fire with Amazon.
4. It aopeared to me that the Supertool attempted a downgrade (5.1.1?) before rooting, so if downgrading will brick a device running 5.3.2.1, then I think the answer to the OP's question is "no".
related question: Knowing all the above, can I still re-try the Supertool option #1, and (re)install the Play Store and remove ads? (I bought 3 of them Amazon removed ads on 1 of them so far.))
Click to expand...
Click to collapse
- SuperTool does not attempt a FireOS rollback
- 5.1.1 refers to underlying Android build
- Amazon will (reluctantly) remove ads from ONE device registered to an account
- KingRoot works best if device is NOT registered with Amazon
- at present KingRoot is not effective against FireOS 5.3.2+
Thanks for responding, sorry for any misinformation, I'm quite a noob. So - if the supertool doesnt rollback, do you think I'd have trouble retrying the ad removal tool while running 5.3.2.1. ?
rallison203 said:
Thanks for responding, sorry for any misinformation, I'm quite a noob. So - if the supertool doesnt rollback, do you think I'd have trouble retrying the ad removal tool while running 5.3.2.1. ?
Click to expand...
Click to collapse
Don't see any significant risks with rerunning but also don't think it will be fully effective on an unrooted device.
Is this probably the best thread to follow if I want to be notified when it's possible to root 5.3.2.1?
valzi said:
Is this probably the best thread to follow if I want to be notified when it's possible to root 5.3.2.1?
Click to expand...
Click to collapse
I hope so, I'm certainly subscribed
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