yashsingh1/xdaforums huggingface dataset:
[Fire Q&A, Help & Troubleshooting] gseverin:
root Amazon Fire 5.3.2 in 2 steps

I successfuly rooted the Amazon Fire 5.3.2 by sideloading version 5.3.1 to it......then running KingRoot 4.9.6-151.

Same result as the above posters. :) Thank you XDA and RootJunky for your support.
[Fire Q&A, Help & Troubleshooting] Robin Son:
successfuly rooted the Amazon Fire 5.3.2

Hey gseverin

I didn't know this stupid amazon fire would just download and installed the update on its own.

Can you post some step by step instructions on how you rooted your amazon fire 5.3.2.

I hate this system need root and custom rom bad

thanks

Had to downgrade from 5.3.2 back to 5.3.1 by ADB sideload and then use Rootjunky tool.

Had to use RJ-tool 2 or 3 times to get Root

Installed Flashfire after Playstore.

Download Rom/gapps and su on pc and placed in AFire download folder.

Flashed with Flashfire

nice work and thanks
[Fire Q&A, Help & Troubleshooting] gseverin:
bricked Kindle Fire after trying to root

Hello all,

My Kindle Fire came with 5.3.2. I sucessfully flashed it down to 5.3.1 with the appropriate *.bin downgrade using adb sideload from the recovery mode and then installed root with root junky's supertool. .....so I had luck with that. I've gathered that TWRP isn't available for 5.3.1 so I ventured into Flashfire. I don't know if there's a youtube for it, but I ended up wiping my device by mistake....factory reset.....after all that work :(. After the install I looked in device options and I apparently still had 5.3.1 on my device because no new update yet

So now I have to start over. Here's where the trouble starts. I rooted the device with KingRoot 4.9.6. That works fine, but to get SuperSU, I ran RootJunky's root sequence and while combining that KingRoot with mine and installing SuperSU at the same time...bad news..it rebooted into a constant glimmering Fire page. My fault RJ...you're doing a great job. I can still reboot into recovery without the use of a "factory cable" and when in fastboot mode, the device is detected by my terminal (Ubuntu 14.04)with the command "fastboot devices", however it's not showing up in the adb server. I tried the flashall command in fastboot mode and it starts but fails. Somehow the hardware ID got changed on the device because when I plug it in (Windows 7)the device driver software can't install it ....... I have a Fire icon (sometimes shows up as MTP USB device) with exclamation point in my device manager. Right click on it...go to properties...then to details...move property device description to hardware id.. I

I get the following reading:

USB\VID_1949&PID_0221&REV_????

USB\VID_1949&PID_0221

I don't like those 4 question marks. I never looked at this when the device was operational. What's it normally say?

Can anyone shed some light on this? Thank you

:
[Fire Q&A, Help & Troubleshooting] DB126:
The ONLY way to recover the device is via stock recovery (sideloading FireOS) if still available. So called 'factory cables' are useless on this device as are common fastboot query/recovery techniques. Bootloader remains locked and Amazon crippled the few remaining fastboot commands of merit.

Contact Amazon for a courtesy exchange if still within warranty.
[Fire Q&A, Help & Troubleshooting] gseverin:
Thanks Davey...I figured that was the case.
[Fire Q&A, Help & Troubleshooting] Robin Son:
stuck with 5.1 will not boot to stock recovery

was going to try using fastboot with 5.3.1 stock img.file but can't find one

TGT123 super tool will reboot my A-fire but will not install stock recovery

O yeah and i lost root and no playstore

Anyone had this problem and fixed???
[Fire Q&A, Help & Troubleshooting] DB126:
- can't perform any recovery/reloads from Amazon's crippled fastboot

- factory/fastboot cables and/or custom recoveries (eg: twrp) non-starters

- only path to joy is via stock recovery on a non-rooted device

- if FireOS still boots use 5th gen SuperTool to root and install SuperSU

- if sucessful FlashFire can be used to install custom rom (CM, Nexus, etc)

- at present no path back to FireOS with disfunctional stock recovery

Suggest reading up on working mods/techniques for this non-standard device. Not your typical Android gizmo.
[Fire Q&A, Help & Troubleshooting] Robin Son:
Ok I got this thing running resurrection remix right with root and playstore

after playing with TGT123 super tool.

Things are a little different flashing with flashfire.

Could have had something to do with me being on 5.3.1 because I did not even see the options

in the videos tom made.

Anyway this is what I did to fix my problem.

I use TGT123 super tool like I was still on 5.3.1 and not on 5.1.1 R-Remix

because all I was needing was root again. It would install kingroot but would not root or even

start to root it. Sometimes it would just say FAIL. But it jump to 70% and fail one time and I knew then

it was going to work. It worked after about 10 more and I hit the button fast to install supersu.

then I install flashfire with the super tool and opened it.....

Post#79 is correct way

!!!!!

1) Placed Rom and gapps on ext sd card

2) Wipe system data/3rd party apps/Dalvik cache/cache partition

3) Changed internal storage to external sd then click Resurrection Remix ROM Next Mount system read write

4) Changed internal storage to external sd then click Slim-Zero GAPPS Next Mount system read write

5) Hit EverRoot disabled now Inject SuperSU and Preserve recovery

6) Now hold Wipe and place it first under Instructions

7) Flash

If this helps hit thanks
[Fire Q&A, Help & Troubleshooting] DB126:
A few non-standard steps but obviously worked for you! In general recommend leaving FF mount options at default values; no need to twiddle.

Curious if you still have access to stock recovery? If no be cautious with FF as a borked future run may leave you with limited/no recovery options.
[Fire Q&A, Help & Troubleshooting] Robin Son:
lost stock recovery on the first flash when other problems happened didn't have a opportunity to keep it.
[Fire Q&A, Help & Troubleshooting] Robin Son:
PERFECTION: Round 2 with a Amazon Fire 5.3.1

Run TGT123 Super tool with wifi off to install Adb and FB drivers

Option 6 to Root and update supersu ( turn wifi on after king root is in stalled ) both new and old versions auto updated me

Option 3 to block update

Option 5 to install FF only

1) Placed Rom and gapps on ext sd card

2) Made backup

3) Wipe system data/3rd party apps/Dalvik cache/cache partition

4) In Flash Zip or OTA, Changed internal storage to external sd then click Resurrection Remix ROM Next Mount system read write

5) Again go to Flash Zip or OTA, Changed internal storage to external sd then click Slim-Zero GAPPS Next Mount system read write

6) Hit EverRoot disable now Inject SuperSU and Preserve recovery ( If you don't use it you may lose it, I did on the first AF )

7) Now hold Wipe and place it first under Instructions

8) Flash

I also used this to jump to other 5.1.1 roms

Davey126 you were right

Pulling down old mistakes

If this helps hit thanks
[Fire Q&A, Help & Troubleshooting] Deafstarr:
Probably a really dumb question... and since my forum searching and google-fu is failing me; what is TGT123 Super Tool? The only thing I can find with reference to 'super tool' regarding Fire 7 is Root Junky's tool set. Is this the same thing? TIA!
[Fire Q&A, Help & Troubleshooting] DB126:
+1. I also did a quick search (fruitless) but since [MENTION=6144197]Robin Son[/MENTION] seemed pleased with the outcome on his device(s) didn't probe further. Regardless of where that tool came from the 5th gen SuperTool available here is the time proven way to go. Not perfect but gets the job done.
[Fire Q&A, Help & Troubleshooting] Robin Son:
[/COLOR]

Sorry, for the misunderstanding Deafstarr TGT123 and Rootjunky is the same guy.

Really cool dude, I just know him from the Droid x2 days when I first started flash roms.

Before he changed his name to Rootjunky. Davey126 gave you right tools but its up to you

how you use them.

The only dumb questions is after someone has jacked up a device that there's no way to restore at the time.
[Fire Q&A, Help & Troubleshooting] sharonbw:
Did you tell them why? I'd love to do the same thing. My Fire is essentially worthless as is but I'd need to be able to be sure to get the right version. Thanks!
[Fire Q&A, Help & Troubleshooting] DB126:
If the device was recent purchase you can likely return it during the holiday grace period. The purchase another and hope for the best (forget about exchanges; an unnecessary complication). Better yet snag a refurb from Amazon Warehouse which typically arrive with older firmware. Pricing is generally 40% or more off list. Aside from the packaging refurbs are typically indistinguishable from new.
[Fire Q&A, Help & Troubleshooting] m.w.hurley:
I just tried Kingroot v5.0.2 and it rooted my FireOS 5.3.1 Fire 7. Kind of annoying since this version doesn't seem able to auto start itself after in-progress reboots. Just start Kingroot again and usually it just continues. One time I did have to start rooting again manually. Based on the filename, looks like it was released on Jan 12.
[Fire Q&A, Help & Troubleshooting] DB126:
Kingroot v5.x (client version) also resists uninstallation by declaring itself a device administrator. Future readers should stick with the 4.9.x series. Rooting instructions come from the cloud; the client version is largely irrelevant from that perspective.
[Fire Q&A, Help & Troubleshooting] Robin Son:
Confirming that this tool works with OS 5.1.4. no need to downgrade to 5.1.1 or upgrade to 5.3.1

I used Super tool on it like it was on OS 5.3.1 and it worked.

Had to run kingroot tool about 10 - 15 times, it was saying the OS was 5.1.1 but it worked.

Also Had to uninstall su and install again with super tool

because it would not update binary.

It also worked on second round.
[Fire Q&A, Help & Troubleshooting] DB126:
KingRoot continues to evolve and apparently is now able to root all versions of FireOS 5.0.1-5.3.1 for this device. Hopefully those talents will soon extended to FireOS 5.3.2+.

The OS level reported by KingRoot refers to the underlying version of Android upon which FireOS is based; it will always show 5.1.1 (aka Lollipop 5.1) for all FireOS v5 builds.
[Fire Q&A, Help & Troubleshooting] steve8x8:
Congratulations mate! (Good that you didn't try to downgrade to fireOS 5.1.1, you'd have bricked your Fire.)

Now since I'm collecting bootloader hints (as there's the Golden Rule to always restore the OS you'd run last, before switching to a custom ROM) I'd like to ask you to parse your bootloader partition for a build date stamp. My "whichpl" script does that, and the 5.1.4 (and 5.1.3) stamps are still unknown. There's almost no magic involved, it's a simple shell script that needs root privileges but doesn't abuse them. - Thanks in advance!
[Fire Q&A, Help & Troubleshooting] ccpizz:
There is a chance it can be fixed by going to Settings > Security > Device Administrators > unticking the corresponding checkbox, and then uninstalling as usual, at least this worked for me in a couple of cases. Yet, I have also see the case when uninstall is denied because kingroot made itself a device admin but the app name does not appear under Settings > Security, and I had to use https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/.

Updating the su binary via the latest supersu from www.supersu.com/download didn't work on 5.3.1.0 but the older version bundled with the Amazone5thGenSuperTool worked fine. Once su was updated I updated the supersu app via google play, and it asked to upgrade su once again and that was successful.

During rooting Kinngroot might switch to other activities with offers to do 'useful' extras - pressing the back button works for discarding them and returning to the main rooting screen.

Also the latest Kingroot installs Purify which must be removed manually afterwards. Touching any of the extra options in Kingroot might install adware/spyware, but otherwise it worked for me on 5.3.1.0.
[Fire Q&A, Help & Troubleshooting] DB126:
- KingRoot can be uninstalled as described but those actions also remove root (su access) which prevents the installation of SuperSU which is a prerequisite for running FlashFire on FireOS

- not confident KingRoot doesn't leave other detritus after uninstallation; really isn't consistent with the app's other behaviors to perform a clean uninstall
[Fire Q&A, Help & Troubleshooting] Robin Son:
Fire 7 5th gen (ford): there are many way to break or brick it

- fireOS 5.3.2.1 cannot be rooted nor downgraded

- fireOS 5.3.2.0 can be downgraded to 5.3.1.0

- fireOS 5.3.1.0 can be rooted

- preloader check: https://drive.google.com/drive/folde...U0?usp=sharing

Steve8x8 can you let me know it worked before i flash a rom

404. That’s an error.

The requested URL was not found on this server. That’s all we know.
[Fire Q&A, Help & Troubleshooting] Robin Son:
Steve8x8 the link you posted is not working.

- preloader check: https://drive.google.com/drive/folde...U0?usp=sharing

404. That’s an error.

The requested URL was not found on this server. That’s all we know.

Can you fix and repost.

If this is something your no longer need or working on i would like to know soon.
[Fire Q&A, Help & Troubleshooting] ccpizz:
Removing the Kingroot apk does not remove the `su` binary from /system/xbin. If you use the Amazon5thGenSuperTool (http://www.rootjunky.com/amazon-fire-5th-gen-supertool/) then it will do the replacement of Kingroot with SuperSu for you. The option is called "Root Device". All I did was to replace the older verion of Kingroot.apk included with the supertools bundle with the latest version from https://kingroot.net which did work with FireOS 5.3.1.0.

If for some reason it does not work for you, then you can use instead https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
[Fire Q&A, Help & Troubleshooting] DB126:
Of course not; expunging the Kingroot apk is irrelevant. Nor was there mention of removing the su binary from xbin. Fully aware of the SuperTool's capabilities and underlying command structure. Glad it worked well for you; using the SuperTool to facilitate the transition from KingRoot/KingUser to SuperSU is the best path for most. Unfortunately, unless there has been an uncommunicative update to the SuperTool is does not always handle the removal of Kingroot 5.x due to additional actions taken by that shady tool to block uninstallation.
[Fire Q&A, Help & Troubleshooting] ccpizz:
In my experience the latest Kinroot tries to trick you into tapping additional buttons on the UI which might have unexpected consequences like the app installing itself as a device administrator, installing other apps like Purify in the background and God knows what else. My strategy was to avoid tapping anything else except the Try Root button and whenever another activity pops up just use the Back button or kill the process from recent apps and restart. And yes, it might take half an hour or more until it is finally rooted.
[Fire Q&A, Help & Troubleshooting] steve8x8:
Unable to reproduce - Just clicked the link in my sig, and it still works - what you apparently used was a copy (the ellipsis is created by the forum software).
[Fire Q&A, Help & Troubleshooting] DB126:
Like many I suppress XDA signatures in the web view as do many XDA apps (in particular XDA Labs). To access a link in a member's signature click on their name/avatar from any post which will display the member's full profile.
[Fire Q&A, Help & Troubleshooting] Robin Son:
I'm hoping the problem is me not knowing how to use this because i just can't get this to work.

I can google it and get options but don't know where to go from there.

Even tried xda labs and still got 404 error.

Can someone else check this and see if its working PLEASE
[Fire Q&A, Help & Troubleshooting] DB126:
I tested the link in [MENTION=5936853]steve8x8[/MENTION]'s signature before posting. Whatever is blocking your access is a local issue.
[Fire Q&A, Help & Troubleshooting] Robin Son:
Davey126 this is crazy, it's a little don't know how to use and network blocks on my end. It would not let me use steve8x8 signature with out that post, it was grayed out on the fire. I see I'll have to use more than one device to finish this. I had to register the device then setup email again and now it's saying network error can't upload file.

Will play with it some more this afternoon.
[Fire Q&A, Help & Troubleshooting] Robin Son:
let me know if this is working View attachment 4031931
[Fire Q&A, Help & Troubleshooting] DB126:
I can access/open attachment if that's what you are asking.
[Fire Q&A, Help & Troubleshooting] Robin Son:
Yes thanks, hope that's all steve8x8 need because I'm flashing it tomorrow.
[Fire Q&A, Help & Troubleshooting] steve8x8:
I Only found the text of the script itself, not its output. But nothing is lost yet, it will also run (as in "bash whichpl") with any custom ROM installed as that won't touch the bootloader files. (Which ROM did you flash?)
[Fire Q&A, Help & Troubleshooting] Robin Son:
I installed the the NEXUS ROM by ggpw here: https://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714

It installed alot slower than the REMIX ROM by cbolumar here: https://xdaforums.com/amazon-fire/orig-development/rom-resurrection-remix-lp-v5-5-9-amazn-t3272599

I was interested in picking up a fire but was 100% not interested in

the software and never would have picked up the fire without these custom roms. So thanks for xda and all the devs and flasher/testers for making this uninteresting device interesting to me:highfive:with some unknowns:fingers-crossed::D

The slow install is the difference between AOSP and TW right?

Question:

Have you or Davey126 tried running split screen or multi window on here?

If so how does it work and how did u install it?
[Fire Q&A, Help & Troubleshooting] DB126:
Nexus ROM includes GAaps and SuperSU extending both install and first run times. After that the two ROMs should be roughly equivalent in terms of boot speed.

I have not tried split screen on this device as it is not natively supported in Android 5 (Lollipop). I do use split screen on a different Amazon 7" tablet running LinOS 14.1 (Nougat based). Works great!
[Fire Q&A, Help & Troubleshooting] BeeWall:
I use XHFW3, which is an Xposed module. It works well. It's an app allowing multiple windows, not just split screen.
[Fire Q&A, Help & Troubleshooting] Robin Son:
OK don't like the nexus rom. The android on this AFire is 5.1.4.

Question:

How do i change roms with FFIRE?
[Fire Q&A, Help & Troubleshooting] DB126:
At present there are only two non-discontinued custom ROMs for this device (excluding FireOS) and only one, Nexus, is receiving regular updates. Read the ROM OP if you want to switch. Typically need to wipe system and data partitions then flash a new ROM in the same FlashFire operation. Pay close attention to positioning of the wipe operation. If you mess that up a reloading FireOS via stock is typically the only recourse.
[Fire Q&A, Help & Troubleshooting] Robin Son:
Bricked it, it's crazy because everything seem to be just fine and then no boot:what:. But i fix it and updated to 5.3.1 with the adb side load in the super tool. Flashed Remix rom. I think the problem was the 5.1.4 because now its alot smoother when flashing. Anyway I'm up and running again:)
[Fire Q&A, Help & Troubleshooting] Robin Son:
Thanks porygonzrock I like it after using it a little.

What rom are you using it with?
[Fire Q&A, Help & Troubleshooting] BeeWall:
I use Fire Nexus, as it is receiving updates more often then the others. If you don't care about updates, I'd recommend Ressurection Remix. I have tried this two and RR, so if you want an opinion on all the ROMs, someone else will need to answer.
[Fire Q&A, Help & Troubleshooting] domingo777i:
Hi i bought a Kindle Fire 5th Gen 7" tablet with FireOS 5.3.1.0 and was able to root and install google play store. However I want to flash Nexus ROM on it but will that brick it??? Will I be able to flash via FlashFire ver????
[Fire Q&A, Help & Troubleshooting] DB126:
Should be fine. Install the latest version of FlashFire from the Play Store and then flash Nexus ROM by following instructions in the Nexus thread OP.

https://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
[Fire Q&A, Help & Troubleshooting] next_milenium:
Kingroot not working for me

I just got a Fire with 5.3.1.0.

Read through this thread and downloaded the rootjunky tool in order to root it.

I followed the instructions to the T but the kingroot kept on failing. So I downloaded couple of different versions of kingroot (including 5.0.2 apk) and yet it keeps failing around 70%.

What am I doing wrong?

Can anyone help me here?

Thanks.
[Fire Q&A, Help & Troubleshooting] DB126:
KingRoot often takes multiple iterations to secure root. Tips:

- boot into recovery and perform a factory reset (erases personal content)

- do not register device on restart

- keep WiFi off (otherwise you may receive an unwanted FireOS update)

- launch SuperTool and prepare to root

- enable WiFi just before launching KingRoot

- if device reboots keep WiFi off as KingRoot now has what it needs

- repeat previous two steps until successful

Using a newer build of KingRoot (especially 5.x series) will not increase odds of rooting but may complicate installation of SuperSU which is a prerequisite for FlashFire and using custom ROMs.
[Fire Q&A, Help & Troubleshooting] next_milenium:
Thanks for your reply.

I actually got it to work and interestingly it worked with the older version of kingroot that was included with the SuperTool.

What I did differently was to hold down the power button several seconds until the tablet shut down. I think that clears the cache. Then the kingroot worked. Of course, I have no proof what I did was the reason why it worked. I'm just glad it worked. :)
[Fire Q&A, Help & Troubleshooting] Crashoverride1993:
Rooting fire os 5th gen tablet with version 5.3.1.0

Hello I have been trying to root a amazon 5th gen tablet with 5.3.1.0 with king root and its been doing nothing but failing and its been driving me nuts so please help someone because many people have apperantly rooted 5.3.1.0 5th gen apperantly so why cant I please help

Seriously what knowledge am I lacking kingroot should work right.
[Fire Q&A, Help & Troubleshooting] DB126:
Look back 2-3 posts; several suggestions offered.
[Fire Q&A, Help & Troubleshooting] gosa:
Me, I spent a considerable time yesterday trying to root 5.3.1.0 with the Kingroot included in the Supertool. This is my second unit that I bought just last week (to my surprise they still sell them with 5.3.1.0).

- Always the same pattern - reboot at 31%, reboot at 34%, fail at just over 60%.

Then I took an advice I read somewhere in this forum and installed the Windows version of Kingroot and I had it done in less than 10 minutes.

(after that I ran the root script from the supertool to first push and then replace Kingroot with SuperSU just in case)
[Fire Q&A, Help & Troubleshooting] jimbobmcginty:
On 5.3.1 it took about 9 attempts to work, trying the windows kingroot program, and both kingroot versions included in the supertool.

The one that finally worked was the one installed by the supertool when choosing for version 5.3.1 .

The main issue I had was stopping Fire OS from downloading the update - I had to factory reset a couple of times to avoid the update on reboot. In the end I blocked https:// access in my router to these sites:

https://firs-ta-g7g.amazon.com

https://amzdigitaldownloads.edgesuite.net

https://amzdigital-a.akamaihd.net

https://softwareupdates.amazon.com

https://updates.amazon.com

So just keep trying, it will work.
[Fire Q&A, Help & Troubleshooting] DB126:
Yep - that can happen with a speedy network connection. Nicely done with the router blocks. There are other strategies for those who don't have this option, eg: going to a coffee house or public library/location where net speeds are often slower. Also turning off WiFi after KingRoot downloads its payload which usually takes place in the first 30 sec.
[Fire Q&A, Help & Troubleshooting] ctodd111:
Can I root 5.3.1.0 without wifi? I don't want it to update to 5.3.3.0 while I'm trying to root!