yashsingh1/xdaforums huggingface dataset:
[Fire General] -Yami-:
now the question, I never unrooted a rooted device from the Rom itself,

how do I remove the one I have? XD uninstalling APKs? That simple? Not sure.

I googled it nor, gonna try.
[Fire General] wtfjajaja:
you can unroot the device under settings in kingroot itself
[Fire General] -Yami-:
Well I have done it right now, hope it doesn't cause any problems.

Good thing is I should still be safe from OTA anyways gonna try the one provided by you now.

Root Failed, now I am afraid the one I had also not going to work and I'll be the only guy around stuck with 5.3.1 xd

Does this root yours? because It doesnt root mine tried over and over again.

Now I gonna try the one I had, but I am afraid it gonna fail xd

also says 1 people asked for research.

hope their explolit was not using some part of OTA apks xd

fails around 30%

edit edit:

I gave the version you give me one more try, and this time it rooted,

So this is hit and miss guys try over and over again.
[Fire General] wtfjajaja:
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 :)
[Fire General] -Yami-:
Trying super sume, before it didnt recoginize kingroot, with the apk you provided it did.

pressed big blue button, seems like it froze but waiting bcz don't know how long it gonan take.

and also I dont want to shut it off in the half way incase it messes up something.

Really lazy to sideload, dont even know how to enter recovery yet let alone where to find valid 5.3.1
[Fire General] DB126:
If you end up reloading/sideloading 5.3.1 (anything lower will likely result in an unrecoverable brick) it will need to be pure unrooted stock. The thread you referenced is not relevant to a FireOS refresh with bootloader/kernel > 5.1.2.
[Fire General] -Yami-:
so basically if I screw up, I am **** up? and cant sideload because I am rooted? well.

Super sume gets stuck btw after I grant root permissions how long it takes I dont know.

but why would I need to be unrooted before I sideload?

or do you mean I need pure stock 5.3.1 to sideload?

I think amazon released it, but I am not sure where to find.
[Fire General] wtfjajaja:
dude, read again my post, follow the instruction.

you can sideload 5.3.1 back anytime, when something happens!

the magic here is.... SuperSU-ME version 6.7!
[Fire General] DB126:
- keep trying...throw in an occasional reboot for good measure

- if still no joy perform a factory reset from the stock recovery menu

- do not register device with Amazon when FireOS reinitializes

- grab the latest/recommended/suggested version of Kingroot and continue rooting effort; might take a few rounds
[Fire General] -Yami-:
oh I used the latest one I guess, okay lets go thanks I missed your post apperantly.

What did you do when you bricked (assuming you have 5.3.1) can you share the stock rom? so I can also sideload if needed.
[Fire General] wtfjajaja:
on CM12.1 already! it's sooooooooo f***ing smoooth, like a new device

don't restart after updating supersu binary! flash the rom directly! important~

well if you do.. you might end up with a bricked device, then you gotta sideload back the official 5.3.1 firmware like Davey126 said.
[Fire General] -Yami-:
Yeah I was asking where to find Official 5.3.1 because it seems you already have it, you may save me couple of minutes :p

Got everything downloaded gonna try now.
[Fire General] wtfjajaja:
http://xdaforums.com/showpost.php?p=62986665&postcount=3

it's here, by sd_shadow

/facepalm
[Fire General] -Yami-:
Pressed flash fingers crossed, I'll edit this post later hope to give you guys good news.

edit:

Passed boot, "Android is starting" promt pop-up so it is safe to guess everything done! thank you everyone. [MENTION=7588255]wtfjajaja[/MENTION]

Hope OP puts your instructions in first message or another thread so everyone can find it.

with the Kingroot version provided by you.

I have one more question.

Since we do not have Recovery, if something bad goes with our Cyanogenmod laterwards,

I go to recovery menu, sideload 5.3.1 and It is okay I guess.

That Flashfire thing is really new to me, never seen such way to install a rom before.

edit:

Finally I am on CM12.1, nothing wrong happened everyone can fallow [MENTION=7588255]wtfjajaja[/MENTION] post on page 4

and

http://xdaforums.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416

Works like a charm.
[Fire General] ahac85:
Not working on the new fire HD 8 on 5.3.1 ?
[Fire General] WaywardOne:
This is the wrong forum for that device, try http://xdaforums.com/hd8-hd10
[Fire General] td854:
wtfjajaja's method worked for me on Fire 7 5.3.1.

Just to re-iterate steps I took:

- Copied kingroot (post #36), CM 12.1, supersume 6.7, flashfire 0.53, mini g apps to SD

- Factory reset

- Wipe cache

- root with kingroot (took 4 tries, first try rebooted device on its own, the rest i just closed and reopened app after fail)

- a minute or so later device rebooted automatically

- Installed supersume and ran it

- installed flashfire 0.53

- followed instructions from flashfire thread:

- Waited a while (5-10 minutes) stuff happened, eventually CM 12.1 booted

It's unbelievably faster compared to stock...

This is my first time rooting the fire (have rooted old phones) and I'm impressed with the performance difference, thanks wtfjajaja for doing the leg work.
[Fire General] Dunard:
WaywardOne I knew it not for this Amazon Fire OS 5.3.1. :D
[Fire General] julianpaul:
So if i understand correctly, there's no way to root AND stay on FireOs? You have to flashfire and move to CM ?
[Fire General] DB126:
No - you can root and remain on FireOS. Those looking for a custom rom (eg: CM) need to take extra steps. After rooting be sure to block OTA updates or risk loosing root with the next FireOS update.
[Fire General] mathbes001:
I bricked my device after rebooting with supersu.

How do I recover ?

My kindle fire is not recognize on my pc...

When I try to run the utility file adb is offline....

need help to unbrick

wtfjajaja' I think you can help me thank you.
[Fire General] julianpaul:
Then why does he say after step 4, don't restart device bricked? There's nothing to do with a custom rom at this stage yet.
[Fire General] mathbes001:
I restarted after step 4 and my device is now bricked.

when a power on my device is stuck on the fire logo. (yellow white)

Unable to unbrick it.
[Fire General] DB126:
- power down

- restart using <power>+<vol-up>

- if stock recovery menu appears you can 'sideload' 5.3.1

- if no response/menu then device is permanently borked
[Fire General] -Yami-:
As he mentioned in his instruction posts and I asked him for stock 5.3.1 under this thread somewhere around page 5.

He already bricked his device more than once (exact way you did) and sideloaded stock 5.3.1 so you must be fine.

Go into recovery and sideload 5.3.1.

Carefull, do not, do not login and accept amazon's updates basically better if you do not connect to wifi.

then repeat this time do not reboot.

For CM12.1 it is faster,

I also get 400MB free Ram, now I just need to buy Link2SD and get rid of my 8gig problems, I already have 16gb SD installed ^^
[Fire General] ttcontributor:
This meant we must install a new rom or reboot will brick the device?!

---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------

Plz, if you don't mind to have us some mn, please help zip us those files.

Is SuperTool ppl referred too this one? http://xdaforums.com/android/general/toolwindows-android-supertool-v1-0b-t2812481
[Fire General] DoctorDark_:
If you stay on kingroot, you should be fine. I think it will brick if you use supersume. (Which it didn't for me)
[Fire General] DB126:
100% correct. Too much caffeine in this thread; lots of rapid posts and jumping to conclusions. Deep breath, reread for clarity, details matter.

---------- Post added at 04:51 PM ---------- Previous post was at 04:44 PM ----------

5th Gen Fire SuperTool: http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695

No zips! Go direct to source for latest versions. Last thing we need is a bunch of dated files burning future readers.
[Fire General] DoctorDark_:
After flashing cm, I decided to flash twrp, which of course didn't work and messed up my recovery. Can someone backup their stock recovery through flashify and upload it here? Thanks.
[Fire General] DB126:
Pretty sure that won't work (reinstalling stock recovery) as others have tried w/o success. It appears stock recovery remains intact after a twrp flash attempt; only access is cut off. To my knowledge no one has cracked that nut yet ...
[Fire General] epiclay:
I'm not having much luck with mine.

This is my first time trying to root this device, so I started with a factory reset. Kingroot actually worked after that and I did get root. Then I screwed up by rebooting after supersume and bricked it. Sideloaded "update-kindle-global-37.5.5.2_user_552153420.bin" and now Kingroot fails every time. I've done multiple factory resets, nothing seems to work. Kingroot will usually reset the device at about ~17%, then continue on restart but fail a while later. I've seen it go as high as ~55% bu always fail. After failing a few times kingroot says a root strategy is unavailable and won't do anything at all. Then I have to factory reset again.

I'm doing factory rest > join wifi > download kingroot from their site > attempt root

I'm not downloading any updates or doing anything else.
[Fire General] DB126:
Verify you are not (re)registering device w/Amazon after reloading 5.3.1. Keep trying with an occasional full power off/reboot between attempts. Kingroot can be annoyingly frustrating ...
[Fire General] Cliffsu:
Help

Hi,

My 5.3.1 rooted using kingroot successful,

And I can replace with supersume

But when I run flash fire it tell me there is no SuperSU and can't update cm 12

Any idea what's wrong with my case?

What I can do is uninstall SuperSU, uninstall kingroot, then brick. Luckly I can reset in recovery mode and get fire 7 back.

Hope anyone can give me some tips to try again.

Thanks

Cliff
[Fire General] td854:
What version of flashfire (must be 0.53), are you running SuperSU after running super sume and letting it update binaries? Have you tested root to make sure it's actually working?
[Fire General] -Yami-:
On CM12.1 sometimes my brightness get stuck, not sure if I brake it via Root Booster or It was broken from beginning.

On its thread they suggest using "Brightness Level" but when that bug occurs, brightness level also cannot change brightness it just gets stuck at lowest light.

if anyone knows how/why and how to avoid it, please inform.

Couldn't find anything else but use "Brightness Level"

in case I brake it,

am I safe to use FlashFire directly Through CM12.1 to Flash CM12.1 again? (I think so because FlashFire works with CMsu)

tell me if it works just like a Custom Recovery or not, if it does, I don't need any information else.
[Fire General] td854:
I don't know if this will help you, but I did a factory restore through CM 12.1 normal system menu when I came in contact with a free space corruption issue (there were 2.5GB of space unaccounted for) and it worked fine. So far I haven't had any brightness issue though.
[Fire General] epiclay:
So close! I rooted with Kingroot, used supersume, installed flashfire and selected "cm-12.1-20160921-UNOFFICIAL-ford.zip", along with gapps micro. The process started, but it went to a black screen and eventually restarted and was bricked. Not sure what I could have done wrong.
[Fire General] DB126:
- stuck brightness is a known bug; only workaround is to reduce number of simultaneous processes (seems to happen more frequently as 'free' memory gets depleted); likely a hunk of system code gets swapped out

- FlashFire can be installed/used in the manner you propose

---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------

Happens on occasion; reload stock 5.3.1 and try again. Likely will be successful next time around.
[Fire General] vorcers:
I also successfully installed cm12.1 on 5.3.1 with wtfjajaja instructions.

I first had also the issue that I couldn't root with Kingroot. It always aborted hat ~30%. I am a german user and used german as system language. After another system factory reset I kept the language settings at english - it worked! :victory:
[Fire General] Cliffsu:
Help

I can root now, but need to make sure if my supersume and flashfire are downlad correctly.

Anyone can share the download link. Thanks.

Cliff
[Fire General] DB126:
FlashFire / Super-Sume. Google if you are looking for Super-Sume 6.7; no cracked links allowed on XDA (rightly so).
[Fire General] Kailee71:
Hi all,

first let me say thank you to all who have contributed to rooting 5.3.1 - it's great having CM on this little tablet!

I have one little question though; now that I have rooted and installed CM 12.1 on my Kindle Fire 5th gen, do I still need to disable OTA updates, or has that been achieved by installing CM12.1 already? If so, is there a way to do this straight on the tablet itself or do I have to use SuperTool or something similar?

Many thanks in advance,

Kailee71.
[Fire General] DB126:
OTA updates are ROM specific. Unsolicited FireOS updates are not a concern when running a custom ROM on this device.
[Fire General] hooks024:
The kingroot link on here works(the build from September 22, i think. The one from the 30th isn't recognized as rooted by supersume). It always quit on me around 32%, and said that root wasn't available. I gave up a couple of days ago, when i was on my facebook app, a notification came up that said kingroot recommended extra permissions. I started supersume, and it's working. It's taking a while, but I'll let you all know how it works out. Thanks to everyone for their contributions.
[Fire General] Cliffsu:
Hi All,

Anyone know how to play POKEMON GO in Fire 7+CM12.1

After upgrade to CM12.1, I got two error message:

1) Play store show: device not compliance

2) After apk install, show "auth errow" mainly error code for root device (my Fire is CM12.1 without active root)

If someone knows how, please advise.

Thanks

Cliff
[Fire General] luk2009:
Factory reset with recover

cache wipe

and now I don't Know how to install kingroot from my sd card , because I don't have any file explorer on my tablet and amazon appstore failed to install file commander, file manager, esfile, etc.

what can I do?
[Fire General] DB126:
Several options. Perhaps easiest is to download ES File Explorer from here and the tap on notification when complete to initiate the installation. Be sure sideload option is enabled in FireOS first. Otherwise you'll need to go the 'adb install <apk>' route via tether which can be ugly for those unaccustomed to line-mode commands. Last resort is to reinstall FireOS via stock recovery which should fix the amazon appstore issue and allow direct installation of a file manager.
[Fire General] luk2009:
I went back to do the factory reset and wipe cache three times and I could install file commander.

After installing kingroot, I have noticed that the tablet was still rooted, then I followed the steps and I'm in CM12.

Thanks for all the help.

finally free
[Fire General] nickoh_lvp:
Is it safe to factory reset while being rooted with kingroot? I haven't installed supersume

And what about OTA updates being rooted? I know I can lose the root access, but updating will result in brick?
[Fire General] sd_shadow:
you will lose root, if you update

I don't recommend factory resetting stock if rooted
[Fire General] hooks024:
Help! I installed cm12 successfully, but i flashed the wrong gapps file. I'm able to use the apps on there, but a message keeps popping up saying that I need to update google services. I tried installing a supersu apk and flashfire, but the supersu binary won't update. Any suggestions, or do i have to go back to stock and start over? Thanks in advance, guys.
[Fire General] DB126:
Start over. CM 12.1+ and GAaps must be flashed together (no reboot between) for stable operation. You could try to enable the native root manager in CM 12.1 (under developer options), install FlashFire and then try a redo from CM; just be sure to perform a full system/data wipe before reflashing CM and a suitable GAaps package (arm/5.1/nano). Order of operations matters; check closely before committing.
[Fire General] hooks024:
Big thanks to Davey! It worked, bud! Just waiting for Google to install my saved apps. This calls for a little drinky poo.
[Fire General] julianpaul:
So if someone absolutely wanted to stay on 5.3.1 and be rooted, would it be possible to follow the root instructions in this thread, install flashfire and cm12 and then follow the following thread to have a rooted 5.3.1?

http://xdaforums.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
[Fire General] DB126:
Simply root 5.3.1 with KingRoot and be done with it. The extra gyrations are only needed for FlashFire which is the gateway to installing custom roms. Don't forget to block OTA updates with the SuperTool (or rename DeviceSoftwareOTA.apk manually).
[Fire General] julianpaul:
No, multiple people just said that if they rebooted without flashfire, the device bricks.
[Fire General] DB126:
Previously addressed this mis-information. Softbrick occurs after after using Super-Sume and updating SuperSU binaries if a reboot is attempted. That's where the guidance to immediately install FlashFire and flash/install CM (or another custom ROM) comes into play.

Rooting w/Kingroot alone does not present a problem. KingUser will be the default root manager. Super-Sume, SuperSU and FlashFire are not part of the equation w.r.t your specific question.
[Fire General] julianpaul:
Oh, ok it didn't register the last time, sorry. Thanks for clarifying.

Is this kingroot/kinguser stuff a possibly hacking/backdoor risk?
[Fire General] DB126:
Yup - 'they' certainly don't do it for the good of the community. Best case is the maintainers are simply nabbing some coin off looks and clicks. Could be other rubbish going on under the covers. At present there is no better tool for obtaining root on a wide variety of devices. Promptly wiping system and flashing a different rom will get rid of any undesirable detritus. I'm not convinced Super+Sume is as comprehensive from a purge perspective.
[Fire General] -Yami-:
is SlimLP or Resurrection Remix or Fire Nexus rom any better?

I guess we can now flash every rom (yay!) what are your thoughts guys?

Especially that brightness bug really bugs me (:P) on CM12.1
[Fire General] DB126:
Nexus also suffers from the 'brightness bug'. Not sure about the others. Use caution jumping between ROMs; be sure to read the OP and corresponding threads for issues others have encountered during installation and suggested remediations. Best practice is to wipe system/data/dalvik/cache partitions between flashes but that isn't always practical if you are trying to preserve settings/apps/data/etc 'as-is' (sometimes referred to as a 'dirty flash').
[Fire General] -Yami-:
No, no as you answered my previous question, Flashfire is just like a custom recovery and it is too much work if you soft-brick the Fire,

so I'll always wipe then install a custom rom to be safe.

but if they suffer from same issue, well no point I like CM12.1 anyway.
[Fire General] optimumpro:
It didn't register, because instructions and other "clarifications" look like someone half asleep was mumbling Gibberish. The main thing is this:

1. If you want to stay on FireOS 5.3.1 and have root, use KingRoot only. Maybe it could work, although from reading this thread, it is not clear at all. But under no condition use Supersu.me or Flashfire. You don't need them if you are staying with FireOS

2. If you want CM, then after rooting with KingRoot, use Supersu.me, then Flashfire to install CM. If you reboot after Supersu.me and before installing CM, you will brick your device.

That was easy, wasn't it? :)

Regards to all...

P.S. Use KingRoot at your own risk, as the app is known for nefarious data collection activity. Install Afwall and try to block internet access to Kingroot and see if it would still work...
[Fire General] Mr. Odor:
Well... I'm an idiot. Rooted, installed sudosume and got to the "press ok to restart" and tapped it before yelling "NO! WAIT!" But too late. When I reboot, I get the fire logo forever.

I tried booting into recovery mode, but get no special menu. But I've never had a "bricked" device that would give me the starting graphic.

So am I doing something wrong booting into recovery, or am I hosed? Is there any adb magic I can do?
[Fire General] DB126:
All of the above is 100% correct. Given the newness of root to 5.3.1 and rapidly evolving understanding of what works and what does not a little repetition is good. So thanks for reinforcing what was already known.

---------- Post added at 03:16 AM ---------- Previous post was at 02:59 AM ----------

At present the only path to recovery on an unbootable device is via the stock recovery menu:

- long press the power button to fully shut down device

- press <power>+<left-vol> buttons simultaneously for up 10 sec

- if no response release both buttons and try again (might take a few attempts)

- if still no joy contact Amazon for a courtesy exchange if still within the warranty period for your region

Note: The 'left' volume button is the one closest to the headphone jack.
[Fire General] Mr. Odor:
Thanks for the response. Couldn't get it to work; finally figured out the problem and I'll leave it here in case anyone else has the same issue.

I hold the Kindle with the power and volume buttons on top, so I was holding the right-hand volume button for "up." But that's actually "down." Holding the left-hand button brought up the recovery menu.

Back to square one, but at least I'm not ruined. Try try again.
[Fire General] Mr. Odor:
Ok, I'm stumped.

I used adb to sideload 5.3.1. I used Kingroot to root, then ran SuperSUME. Updated, DIDN'T ALLOW IT TO REBOOT, and ran Flashfire. Took a couple of tries but Flashfire finally started up with root privileges. Hit "+" and chose wipe, then hit "+" and chose "Flash ZIP or OTA." That's where I'm stuck. It says "Select File" but I just get a spinning circle for ~10 minutes. I know the SD card is good; it's how I installed SuperSUME and Flashfire.

Thoughts?
[Fire General] DB126:
Exit FlashFire and try moving the rom zip to internal storage. Immediate goal is to get that rom installed to avoid a soft brick should the device inadvertently reboot while still on FireOS. Also, verify you have a recent build of FlashFire (0.52+) as earlier versions had some stability issues. You can safely grab the latest version from here .
[Fire General] SwitzXXL:
Can someone list good sources/links for the needed applications?

FlashFire

SuperSUME

KingRoot

Thanks
[Fire General] Mr. Odor:
Moving the files from SD card to Downloads made no difference... it still spins forever.

The apk on my SD card is eu.chainfire.flash_0.53-53_minAP117(armeabiv7a,x86)(nodpi)_apkmirror.com.apk; that's the same one that your link suggests I download.

Any other ideas?
[Fire General] sd_shadow:
Flashfire

http://www.apkmirror.com/apk/chainfire/flashfire/

SuperSume thread

http://xdaforums.com/general/paid-software/supersu-please-t3110954

Kingroot thread KingRoot thread

rootjunky's supersume video

https://www.youtube.com/watch?v=3O3DcpeS_Ic

or manually install supersu with a terminal emulator

http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
[Fire General] Mr. Odor:
It worked! I noticed that I seemed to lose su privileges after a couple minutes, so I re-ran SuperSUME from scratch, went straight into Flashfire, and was able to find the files. Cyanogen is starting right now!

This is sweet! Thanks for your help, Davey!
[Fire General] DB126:
Appears you solved the problem on your own! Thanks for sharing the resolution; might help others caught in the same situation. :)