yashsingh1/xdaforums huggingface dataset:
[Fire General] Mr. Odor:
My very first thanks! Wow, I'm a regular professional now.

But it's 4 steps forward, 1 step back. CM12.1 installed great, but the GoogleApps package apparently didn't work. I used the OpenGApps micro package, that appears to have been a mistake.

So do I need to re-flash the ROM with a different GApps package? Can I install Google Play store separately? What's my best path forward?

There's no ROM manager included in this CM build, FWIW.
[Fire General] DB126:
This happens on occasion with FlashFire. To date no definitive explanation of why it occurs and how to avoid. The Micro package is certainly acceptable (larger packages can be problematic) although I generally go with Nano as it is the smallest package that includes all of the 'core' components that can not be easily obtained elsewhere.

Best course of action is to reflash CM 12.1 and a suitable GAaps package as the two operations must be performed consecutively for greatest success (as recommended by Cyanogen):

- reinstall the latest version of FlashFire from here

- validate you have a current CM 12.1 zip and GAaps package (arm/5.1/nano) on the SD card or internal storage

- from Flashfire queue up a wipe of system/apps/dalvik/cache partitions; make sure wipe remains at the top of the operations sequence

- add in CM and GAaps zips; recheck and move (long press) wipe operation to top of sequence if needed

- recheck everything and then whack the FLASH button

Hopefully GAaps will take the second time around.
[Fire General] Mr. Odor:
Yep, that did it! Thanks!

For anyone else who might come along: I had to:

- enable root mode in CM12 (go to tablet options, tap the build number 7 times to unlock developer options, go back to settings, find "Developer settings" at the bottom, and turn on root access for apps.

- reboot and install Flashfire from the SD card.

- reinstall CM12 and re-download GApps. The problem was that I'd previously downloaded the arm/6.0/micro bundle. Switching to arm/5.1/nano did the trick.

On reboot, everything came up perfectly! People are right: the tablet is crazy fast compared to the stock FireOS. Really happy with it (considering I bought it for $35 last year) and very thankful for the great work by people in this thread to get it accessible to the general public like me.
[Fire General] andMego:
So I rooted my friends fire successfully with kingroot (the link given earlier in the thread didn't work but searching Bing got me a working one), installed Nova as a system app, and disabled lots of the Amazon garbage. Now the power button brings up the shutdown dialog BUT pressing to confirm that I want to shut down does nothing and the only way to shut it down is by holding the button for ten seconds. He doesn't like that. How can I fix it and where can I find a up to date list of safe to disable bloat? This forum is WAY messier than it was when I rooted another fire a few months ago.
[Fire General] Nhj27:
Does this work for 2015 Fire HD 8? It is under general Fire thread so unsure if this is only for the 7" version
[Fire General] andMego:
This thread is just letting everyone know that kingroot works for 5.3.1
[Fire General] DB126:
This forum is only for the 5th gen 7" Fire released 3Q15. See below for HD8 forum.

http://xdaforums.com/hd8-hd10

---------- Post added at 02:15 AM ---------- Previous post was at 02:07 AM ----------

Best bet is to reload FireOS (presumably 5.3.1) and try again. Likely a hunk of "Amazon garbage" was doing more than you thought. Will be hard to identify. To my knowledge there is no unified/current/tested list of "bloat" that can be safely disabled. Best course is to leave it alone or go for a custom ROM if your friend desires a 'clean' experience. No problem with alternate launchers, disabling lock screen ads and uninstalling preloaded apps. Beyond that you are playing with...er...Fire. ;)
[Fire General] Nhj27:
Thanks. I've tried both the crown version and the lightning bolt versions multiple times on my 2015 kindle HD 8. Neither seem to work as of now :(
[Fire General] andMego:
Use the one mentioned on page 3(I think)
[Fire General] Nhj27:
That is the one I used. I tried about 10 times, and it does not seem to work for the 2015 HD 8. So I switched to the most current version. It does not work but according to the app, about 11000 ppl have requested a root for it and thus a priority for them.
[Fire General] andMego:
Supersume says on the play store page that it doesn't work with kingroot over 4.90 so how does that work?

---------- Post added at 03:26 AM ---------- Previous post was at 03:14 AM ----------

This worked for me on the third time https://uplod.ws/puz50ty89j3r
[Fire General] Nhj27:
Thank you. I will give that one a try.
[Fire General] DB126:
The app always shows an inflated/suspect number when it can't find a root exploit. It's all spin to keep you coming back ...
[Fire General] DoctorDark_:
Thus adding to the shaddyness of kingroot
[Fire General] glock24:
I bought one of these tablets on a sale, and it looks decent enough for the price I paid. Unfortunately it autoupdated to 5.3.1, so I was stuck with Amazon's system. The stock launcher is ugly and RAM management is bad, could not have more than one app open without reloading on switch.

I read this thread and was thrilled! I tried kingroot and it failed several times, but finally succeeded. Then ran supersume, it took a long time so I left it do it's thing. I came back after a while and the tablet was stuck on the fire logo. Did factory reset but still the same. I side loaded stock system and tried again. This time everything worked, rooted with kingroot, then changed to SuperSU with supersume. I then proceeded to install CM12 using flashfire and I'm happy now.

I got a bug though, as play store didn't failed every time I tried to install an app with a network error, but that was solved by clearing app data for play store and play services.
[Fire General] Creeperr:
It worked ! Thanks a lot :)

I've just flashed SlimRom and Nano Gapps.

I used SuperSU Me 6.7 and FlashFire 0.53.
[Fire General] liu siaulong:
adroid 2.3
[Fire General] VTCruzer:
Worked Great

Followed all the steps and it works fine.

Took me much more than 2 or 3 times to root. I had to uninstall Kingroot twice to get it to work. I downloaded the 6.7 apk from online because the newest version didn't work for me. Seems like you

have

to use Supersume

6.7

, because any other version (I tried) won't detect you're rooted. After that everything flashed with FlashFire just fine (Except the Gapps, which were the wrong version [It's been a while since I've been on here don't blame me]. I'll get to that). Booted fine, and surprisingly quick too. Since I got the wrong Gapps, they didn't flash but didn't mess up the rom. Luckily I was able to reroot with Kingroot and get SuperSu with Supersume again. I then flashed the correct Gapps with Flashfire and everything is now working great with no problems. Runs 5.1 way better than my 1st gen Kindle Fire, and will probably replace the old thing now. I'll be sad to see it go, but couldn't be happier too:good:
[Fire General] ngtom:
My kindle is fire HD6. I want to root it but still stay on fire os 5.3.1. So far I know that kingroot will root fire os 5.3.1 fine and if you want to stay on fire os you have to keep the kingroot. So I want to know if any chance that if i rooted by kingroot and replaced it with superSU. Thanks.
[Fire General] chamba:
long time lurker (like way too long).. rarely post but i wanted to say thanks for this, i failed a few times along the way mostly due to me being lazy and not wiping to factory before starting , bricked my device a couple of times but i learned how to use adb if only the minimum , ran in to the issue with gaps but i realized by default the website chooses android version 6 just changed to 5.1 always choose micro or lower learned this the hard way too , and re flashed cm12 plus gaps. i used to think the fire was great with fire os before , was i ever wrong CM12 just leaves it in the dust.
[Fire General] DB126:
Wrong forum. Post here: http://xdaforums.com/fire-hd
[Fire General] ldeveraux:
SuperSUMe? Who knows? check your device forum
[Fire General] opera_1978:
Hi! Help! A wall up the device after the update SU Binary?

I did everything according to instructions, but after the update SU Binary pushed to restart! The device is now stuck on the logo of "Fire". . .

Kindle Fire 7 5.3.1
[Fire General] DB126:
Reload FireOS via stock recovery menu.
[Fire General] opera_1978:
thanks for the tip! :good: Could you send me a link to a step by step guide how to do it! Excuse me in advance, I'm new on this forum!!! :o
[Fire General] gtallmadge:
SuperTool root is now working on Fire OS 5.3.1. Runs great and the removal of KingRoot and replacement with supersu is seamless.
[Fire General] DB126:
Here ya go: http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294/page26
[Fire General] opera_1978:
I can not do anything, because the DAS mode, the device is defined as "other devices/KFFOWI" triangle. Manual drivers are not installed, writes that the most appropriate software is already installed or not needed. Reinstalling Drivers nothing. If you go in "fastboot mode", the device is defined as it should!

What can be done?
[Fire General] DB126:
Reinstall drivers: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing

https://www.andromods.com/download-files/kindle-fire-hd-7-8-10-5th-gen-2015-usb-drivers-adb.html
[Fire General] glock24:
This happened to me, you have to sideload the stock ROM and try again. After sideloading stock ROM, do not link the tablet to Amazon account, just skip it and proceed with kingroot and then supersume. When you finally have SuperSU, update the su binary but don't reboot. You can now launch flashfire and install CM12 if you want.
[Fire General] ttcontributor:
Seem like it no longer works with HD 10 5.3.1.0. Amazon might have pushed a patch!
[Fire General] DB126:
Wrong forum for HDxx discussion. Post here: http://xdaforums.com/hd8-hd10
[Fire General] iodpilot:
Working No Longer

I followed the instructions earlier and kept trying , all of a sudden it now states Root Strategy Unavailable.
[Fire General] JD33:
Coming from Fire OS 5.3.1 I was able to successfully root, replace Kingroot with SuperSu, then install CM-12.1. So far everything is running fine without issues.

Only problem I had during this process was having to run KingRoot about 4-5 times (rebooting after every fail) until it finally rooted.

Prerequisites:

Download latest Fire USB Drivers - Installing the USB Driver (Windows Users)

Download latest version of SuperTool - Amazon Fire 5th Gen [SuperTool]

Download FlashFire 0.53 - [root] FlashFire 0.53

Download CM-12.1 - [ROM][UNOFFICIAL] CM-12.1 [22 Sep 2016]

Download 5.1 GApps - Open GApps 5.1 Micro, Pico or Nano

Make sure USB Debugging is enabled before starting.

Copy CM-12.1 and 5.1 GApps to tablet.

Steps to install:

** At this point you should have Fire OS 5.3.1 rooted with SuperSu. Now to install CM-12 -- follow the directions from their thread listed below. **

After CM-12.1 boots up go to Developer Options and change Root access from "Disabled" to "Apps and ADB". Then install SuperSu from the Play Store and update binaries as usual.

Hope this helps.
[Fire General] nivednk14:
Bricked !

how to unbrick the device that bricked by restarting afer the supersu binary update step..
[Fire General] ALcAtRas500:
Runs the tab on 5.3.1 stable with only root or we have to install cm 12.1 for right work. My question behind is i want only root rights for 5.3.1 and no cm12.1.
[Fire General] DB126:
Reload FireOS: http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294/page26

---------- Post added at 12:31 PM ---------- Previous post was at 12:26 PM ----------

Yes, you can root and remain on FireOS. Simply run KingRoot and block OTA updates using RootJunky's SuperTool. No need for SuperSume, SuperSU, etc.

http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
[Fire General] Svalfio:
I have a Fire 5.3.1.0 and I just get to root it with RootJunky's SuperTool.

Can I install any other Custom ROM or the only safe one is CM 12.1?

Thank you very much!
[Fire General] DB126:
At present CM 12.1 seems to have the largest user based followed by Fire Nexus. AFAIK none of the others are 'unsafe', just don't have the same user support base as the previous two.
[Fire General] Svalfio:
I mean, is there any danger of a brick or similar damage trying to install, for example, SilmLP, or, as long as I managed to root my fire (5.3.1) and install FlashFire, I'm good to go?

And can I install a custom recovery?

Thank you for your help!
[Fire General] DB126:
- you can not install (or boot) a custom recovery w/5.3.1 bootloader

- bootloader is locked and can not be be rolled back w/o bricking

- FlashFire is generally reliable and getting better with every update

- installing (flashing) any custom ROM carries the risk of a 'soft brick'

- soft bricks can usually be recovered by reloading FireOS (ie: stock)
[Fire General] Svalfio:
Ok, got it, so I can install any Custom ROM designed for the Fire (with the risk of a soft brick, yeah, but I was aware of that).

Thank you very very much for your help and time!
[Fire General] ALcAtRas500:
I have install the latest kingroot and take 3 times now it says no way for root.
[Fire General] DB126:
Keep trying; Kingroot often takes multiple attempts.
[Fire General] williamvito:
Novice question: Been running cm12.1 coming from a base FireOS of 5.1.1, is there ANY benefit to me sideloading FireOS 5.3.1 and then re-rooting and re-installing cm12.1? Is there a kernel benefit?
[Fire General] DB126:
Good question IMO. At present there does not appear to be any notable bootloader/kernel improvements in 5.3.1 that would impact your experience on a custom ROM. The 5.1.1 bootloader does hold a slight advantage over later releases: the ability to gain temporary root via Fastboot. Also, if an unlock exploit does become available it is more likely apply to early generation bootloaders.

Moving to FireOS 5.3.1 is advised those who wish to stay on that rom and install Google Play Services, Store and associated apps. Even then it is best to remain on the lowest compatible underpinnings (as described here) if one cares about potential future exploits.
[Fire General] DPclue91:
So I can obtain root by following route junkies video regarding 5.1.2?
[Fire General] ALcAtRas500:
I have runs over and over and no root always it says fail. :rolleyes:
[Fire General] DB126:
- Use the the SuperTool to prepare your device for a custom ROM (root, block OTA, switch to SuperSU, install FlashFire, etc)

- follow guidance in the CM 12.1 thread to install ROM + GAaps

- best read up on details in advance for better outcomes

---------- Post added at 01:00 PM ---------- Previous post was at 12:44 PM ----------

Seems to be an issue unique to your device. At the risk of sounding condescending please make sure your device is a 5th gen 7" Fire first released 3Q15. Easy to confuse similar looking units.

Beyond that perhaps the best option is to reload FireOS 5.3.1 via the stock recovery menu to start fresh. Do NOT register device with Amazon when prompted (device registration sometimes interferes with KingRoot). Once FireOS is up and running tether and attempt to root using the SuperTool.

If still no joy might consider contacting Amazon for an exchange.
[Fire General] DPclue91:
So this root doesn't work for the 2015 HD 8 ?
[Fire General] DB126:
This is NOT a HDxx forum (ask here). Just because both devices carry the Amazon logo and kinda look the same doesn't mean the same procedures apply. Also doesn't work on a commodore 64 or your garage door opener.
[Fire General] ogpog:
Hi, my proven process to root 5.1.2 uses this script (mrw) to move from Kingroot to SuperSU. Has anyone used this method on 5.3.1 ?
[Fire General] DB126:
What advantage(s) does your script hold over the largely transparent method used by Root Junky's 'SuperTool'?
[Fire General] dynamitebeta:
Problem in installing CM.When i try to use flashfire,the screen freezes.how can i install cm.I rooted using Kingroot.Installation of CM and using TWRP N CM Boot is problem.How to unlock boot loader
[Fire General] DB126:
- can't unlock bootloader or install custom recovery on this device

- must replace Kinguser with SuperSU for FlashFire to work

- recommend using the SuperTool for all prepatory tasks prior to flashing a custom rom
[Fire General] ogpog:
I believe that Root Junky's 'SuperTool' requires use of a Microsoft operating system. I use Linux :D
[Fire General] dynamitebeta:
Thanks Davey126 and Rootjunky and Xda guys.I installed cm12 and also tried nexus ROM.:laugh::laugh:
[Fire General] gtallmadge:
It does not require you use Microsoft Windows, read the OP. I use only Linux and have used Root Junky's 'SuperTool' without any problems. Please don't spread FUD like this.

He has even posted a video of how to do it with Mac and Linux!
[Fire General] Jubri:
Hi all!

I have a problem, with flashfire instructions. I follow all steps, fire reboots, but flashfire don't start... only show red title (FlashFire) and stay with no messages on middle screen. Try several times with no luck... :crying:

Files are stored in a subdirectory of sdcard.

Any suggestion?

Regards.
[Fire General] DB126:
Use the SuperTool to verify root, block OTA updates, convert KingUser to SuperSU and install the latest version of FlashFire. With those preliminaries out of the way you can proceed with flashing CM 12.1+GAaps using FlashFire (follow instructions in CM 12.1 OP).
[Fire General] ogpog:
I am sure when I looked at this a couple of months ago I am pretty sure that it was only windows, and there was no mac/linux video but I might be mistaken. I have just checked the site and can see there is a shell script now, so I will take a look at that. Making a mistake is hardly spreading FUD :(
[Fire General] gtallmadge:
I have been using it since April and it always had the provision to use Linux. No, making a mistake is not spreading FUD....but failing to read pertinent information before posting inaccurate information is close to it.
[Fire General] B2Pi:
Naw, it runs on linux

Grrr... refresh before responding.
[Fire General] tbirdguy:
Worked a treat on 5.3.1

I just used super tool. used the king root that is included with it, took several tries before it achieved root, but when it did finally get root, the script worked to uninstall kingroot and super su updated fine; I installed flash fire and all seems great
[Fire General] Jubri:
Ok, finally it works!

Thanks Davey126

Difference flashfire instructions, method on Post #53 ( Ensure Auto-mount and Mount /system read/write are UNCHECKED) don't work. method on Post #146 (Accept defaults) Its works!

And now, another problem. I go into developer options and enable root access (App and ADB), but apps that require root fail... not rooted?. I install SuperSU but fail to update su binaries...

Thanks in advanced
[Fire General] ogpog:
I have successfully rooted FireOS5.3.1 using supertool on Linux and then flashfired CM12.1 and stock gapps.
[Fire General] DB126:
Can't overemphasize the importance of consulting the ROM OP (first post in rom thread) for flashing guidance. This information comes directly from the developer who, surprisingly, knows something about the product and how to install it. Not some random post for me or another member of the community. Like taking medicine without reading the doctors instructions. Who knew?

As for fixing 'no root access' reflash CM along with a suitable GAaps package (but no SuperSU) after a full system wipe. All flashable zips should be located in internal storage. They are not large and can be relocated or deleted after successful flashing.

- move all zips to internal storage under \SDCARD

- reinstall FlashFire (latest build, >0.50, preferably 0.53+)

- queue up full wipe (system, apps/data/user, dalvik, cache) in FlashFire

- add rom and GAaps zips

- confirm full wipe action remains above flash action; move if needed

- execute (Flash button)

If still no joy (happens) you will need to reload FireOS and start over.
[Mogul, XV6800 General] bimerguy:
What a great forum/website...

I am using the Alltel HTC/PPC6800 Mobile 6 Pro with ROM 2.14.671.3 dated 8/20/07 and Hdw version 0003. Model TITA100(which unit is this..is it same as anything else?)

I am new to the SmartPhone with a new Alltel HTC PPC 6800 and heard that the voice command was a winner to use on this model and I have it and no-go! I bought a version that could upgrade from v1.01 to the 1.5 SW and then :Sync-ed" it to my device and installed with a strange install directory.

It installs with the message about "installing to "" but device memory recommended and I've thought I did the recommended location as I had no choice except cancel. What is the "" means and it that my problem or can I get around it?

Anyway, it simply won't work for some reason. I have not gotten the SW to even give me the "microphone" to speak to the SW and it continues to come back withthe error about having a problem, restart and try again.

Any help out there would really be appreciated as I had to go to this "SmartPhone" after my faithful PDA and Cell broke and died on me in the same month.

Thanks in advance,

bimerguy

:eek:
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] Flashnewb:
-Deleted-
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] bilgerryan:
Safe, yes. But you most likely won't have data or wifi. In most cases your modem needs to match the software you are using.
[Blu Pure XL] jelo1:
hi guys this is my problem

i have a pure xl with a damage usb port it only charge but i cant change data from pc

i had it rooted and the problem is i did an update and it get stucked at the recovery screen

it trys to load but it say android screen 2 times and then it goes to recovery and again and again

i already tried wipe cache and wipe fata factory reset but it dosnt happen nothing

ii checked the restore user data and it dosnt delet anything all my files still there

and i download the rom and i tryed to apply update from sd card but it only show me the internal sd card

not the external :( plase guys i really need help:crying:
[Blu Pure XL] jelo1:
help

novody has an answer? :(
[Blu Pure XL] Matheusbpvh:
;-;

With a damaged usb port, it's hard say... Sorry bro!
[Blu Pure XL] Short Circuit:
Try to using another USB cable or another USB port on your computer? It could be worth a shot.

Could you also try to follow this guide and see how far you get? Thanks
[Blu Pure XL] jelo1:
finally got the usb port

finally i got a good usb port but how can i load the rom :( i cant use a sd card only usb port
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Antoonio:
Changed phone screen , so after that screen coes black when i call and cant do ****, i think sensor is kinda buggued. When i take screen off and move finger, 5cm far from sensor it works, but when i move my finger in 2 cm far from sensor it wont work. I have no clue , hard ware of software problem.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Chamelleon:
Find proximity windows on new touch screen and paint it with black marker from inside. If it doesn't help scrape all painting from this small window to make it completely transparent and then again paint it without leaving any spot transparent. Permanent marker You can clean with some alcohol, don't use any solvent cause it can damage rest of digitizer paint.

Some year ago I had whole part like this, 15 or more screens where I had to scrape this window from painting and again paint it with black marker because factory paint was to dark and light couldn't come in. But in Your case before You scrape it first paint it cause Your can be too bright and if it doesn't help then scrape and paint.