yashsingh1/xdaforums huggingface dataset:
[Fire General] DB126:
Agreed. Also includes 'battery saver' apps and similar rubbish - especially on a rooted device. Why it's best to verify basic charging functionality with device fully powered down (not just sleeping). Once basic operations are confirmed then power on tests can be conducted to narrow down possibilities and identify the likely culprit.
[Fire General] Christ_Gj:
Does anybody know where can I find and download stock rom for amazone fire 5th gen?

I need files to use with SP flash tool ?
[Fire General] DB126:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200529680
[Fire General] sd_shadow:
no one has gotten SP flash tool to work with Amazon Fires
[Fire General] knicknut:
I'm at my wit's end, would appreciate some advice.

I tried to install SlimLP via FlashFire (following the instructions exactly), but it caused an eternal boot. I was able to boot into recovery and tried it again, still an eternal boot.

Now I can't get back into recovery to do the adb sideload. If I hold power down and power, I get the amazon screen, which never goes away to reveal recovery, or nothing at all. I can get into fastboot reliably every time. I tried using the tool to get into recovery via fastboot, which also puts me on the Amazon screen forever.

I can't imagine the recovery was able to corrupt itself between the first and second boots when I didn't write anything else. Any other suggestions?

Thank you.
[Fire General] DB126:
Couple thoughts:

- try to 'long press' power (20+ sec) to see if that offers a more robust device reset and possibly restores access to recovery

- there is an evolving line of thinking around ways to restore recovery access (here). Be aware this is largely untested but might offer a recovery path if all else fails and you can't return/exchange the device. Worth watching.
[Fire General] gtallmadge:
Thanks for this. I rooted my Fire yesterday and managed to brick it(my fault..too impatient) and used the information here to install Fire OS 5.1.2 without any issues. Had the tablet rooted and installed AOSP ROM very quickly after. Thank you for the amazing work on this tablet!
[Fire General] lh94:
So I take it as there is still no way to unbrick 5.1?
[Fire General] DB126:
No new breakthroughs. One or two individuals have reported being able to access stock recovery after a series of extended/random key presses but no one has been able to recount the exact sequence used. Could very well have stemmed from confusion on which combination activates recovery (more). There was a recent find on how to restore stock recovery (here) but a working/bootable rom is needed at present.
[Fire General] Y314K:
So I bought a few Amazon 5th Gen 7" tablets during the BF sale. Had already blocked Amazon updates on my router due to my FireTV's. Then I checked what FW they came with (Fire OS 5.0.1 - Build 37.5.2.2_user_522055120). I put them aside. And now I am ready to root & install a true Android Rom on them. But first I wanted to have the stock FW they came with just in case there are any problems.

But the first problem is that it seems my tablets shipped with a FW that was never posted on Amazon or no one ever backup.

I am looking for Fire OS 5.0.1 - Build 37.5.2.2_user_522055120 - Any info would be appreciated, thanks. I would want to keep my Fire OS @ 5.0.1 to keep TWRP compatibility.

Could I use the 5.0.1: update-kindle-37.5.2.2_user_522054520 FW if needed? Has anybody actually done this ? Or will I just be bricking my tablets if I ever need to get things back to stock ? Dose this mean that I would need to flash Fire OS 5.1.1 FW if it came to that ?
[Fire General] sd_shadow:
any 5.0.1 build should work

you just can't downgrade system versions like from 5.1.1 to 5.0.1
[Fire General] Y314K:
Thanks for the quick reply. Now trying to learn about Link2SD to be ready for the full mod. :good:
[Fire General] DB126:
Info on Link2SD here with additional comments here and here. Should work with any ROM except possibly FireOS due to potential conflicts with integrated functionality. Proper setup is key along with intelligent choice on what to move/link. Sorry for referencing my own posts; seems to be some misinformation on Link2SD floating around the forums (no bad intentions; individuals just reporting experiences).

As mentioned no need to mess with FireOS on your devices. Best option is to skip initialization all together and boot directly into TWRP. You can load a selection of ROMs onto an SD card (or even USB drive via OTG) in advance and sample a few. My humble suggestions are Nexus if you like a clean base with easy installation (just one file to flash) or CM 12.1 for a nice balance of feature/functionality without bloat. Both are updated regularly by the same dev. SlimLP and Remix are fine too. All are stable, feature complete and well liked by the community. Stay away from FlashFire while cycling through ROMs. Once your settled you should be able to use FF for updates.
[Fire General] radrnatn:
if i origionaly had 5.0.1 and and it updated to 5.1.2 by it self,I cant adb side load ot back to 5.0.1 it will brick correct.i regret not turning off auto update with TOMSGT tool.
[Fire General] DB126:
Correct - no rollbacks.
[Fire General] Robo-rooter:
But you can reload 5.1.2 if you need to with no problem. Before successfully loading the Nexus rom on my Fire 7/ 5.1.2, I bricked it twice trying to load the Slim rom with FlashFire. Side loading with 5.1.2 via adb brought the Fire 7 back both times.
[Fire General] nyln:
This worked wonderfully, thanks.
[Fire General] Y314K:
Great info. Great links. Had already found the first one. Very detailed. I am understanding the process I should take now. For the most part.

I usually prefer soup or multiple in one type of ROMs like REMIX but since it's outdated right now (multiple security patches). I will try both CM & Nexus for now until REMIX gets updated. Which means I will need XPosed to do some of the same mods. Although theme wise CM would have more stuff builtin then Nexus right ?

I plan to write a step by step of what I am planning to do to make sure I have not missed or misunderstood anything. Will probably post it in the SuperTool thread. But really glad I read your posts.

Thanks :good:
[Fire General] DB126:
Thanks for your comments :)

CM has a handful of integrated knobs/dials which mitigates the need for XPOSED IMO depending on your interests. One less thing to flash. I don't do anything with skinning/themes so can't comment beyond the out-of-the-box experience which is pretty clean. I would lean toward Nexus if planning extensive mods as AOSP is the ideal platform for Xposed and similar tools. Note Nexus does NOT support live wallpapers with no easy way to add the required binaries. Post a comment in the Nexus thread if interested as the dev is generally responsive to feedback (doesn't mean you'll get it as any mod to AOSP must be carefully considered). Bottom line: you can't go wrong with either ROM.
[Fire General] Y314K:
I am now leaning towards CM too. Since It's the most complete of the two ROM's. And it comes with a builtin Theme service + knobs & dials. Do you just run ASOP ? No Launcher or other mods ?

Really hopping REMIX does get an update soon too.

I am leaning on going with the PICO Gapps. Although I am planning to run Link2SD Pro. Seems the RootJunkies Video of the CM installation was running Stock Gapps. But that causes system space problems. To bad we can't install Gapps directly to an ext4 partition @ initial flash. Researching more about the best Gapps option for now.

Waiting for the "Icons disappearing when moved to SD card" bug to get resolve to start flashing away.

I got 4 tablets to flash for us. Three of them will need to be made as simple as possible. They are for less techie Family members. And mine which I can test away different options on. Just trying to line my ducks in a row before getting it done. Thanks again for your help.

:good:
[Fire General] DB126:
I run different roms/mods on a variety of Amazon devices. On this device I lean towards CM as it contains the right mix of tweaks for the intended use/audience. My favorite ROM is [MENTION=5749760]ggow[/MENTION]'s build of AOSP Nexus (available for several models) with Nova and a handful of potent Xposed modules. Simple to flash, easy to mod, rock solid. Goodness defined.
[Fire General] Coollest:
Hello guys. I have such problem. I tried to flash SlimLP, but it was not successful. After that i've tried to install adb sideload new FireOs Firmware, it was 100%, but after reboot only black screen and not known device if connecting to pc. Fastboot also not working. If i will buy an factory cable - it will help? thank you.
[Fire General] sd_shadow:
no a factory cable will not work
[Fire General] Coollest:
Thank you. No way to unbrick?
[Fire General] sd_shadow:
you haven't given enough info

Bootloader version (stock version)?

did you try booting into stock recovery?

...
[Fire General] Coollest:
I am sorry. It was on FireOs 5.1.1. Then i received root, installed FlashFire for flashing, downloaded Rom 2.1 and tried to install it. Everything was ok, but after extracting the archive - no new lines on screen with information. Was waiting for 1 hour and then made a reboot. Nothing works except recovery menu. Then i've downloaded the official FireOs Firmware as in instruction and then tried to adb sideload it. Everything ok, 100%, reboot and black screen without any signs of life. Can't fastboot it (am holding power + volume button), can't go to recovery b/c/ of unavailable fastboot. Thank you
[Fire General] DB126:
Given the symptoms I doubt your device is recoverable using any common techniques discussed in these forums. An unresponsive screen and inability to enter fastboot are telling. If within warranty consider contacting Amazon for a courtesy exchange.
[Fire General] Coollest:
I am sorry, i am newbie in flashing. May you please give the link to some techniques? Because i can't enter fastboot and don't know what to do without it and access to recovery.
[Fire General] DB126:
See below. Keep in mind you are attempting to recover a device that appears to have serious problems. Options are few if you can't access fastboot or the stock recovery menu.

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485/page10
[Fire General] Designassist:
Cyanogenmod 12.1 Unoffical Ford trying to install gapps

Hi,

I installed cyanogenmod with flashfire. When my kindle rebooted I noticed I had no google playstore which I had also flashed along with it. I went and downloaded flash fire again but it said I was either not rooted or not running supersu. Which CM came with root which I enabled in developer options. I tried root checker it said I was not rooted. So I king rooted it then tried installing supersu but updating binaries kept failing. It said there was another supersu detected and attempted to delete but failed. So I tried going into recovery to flash gapp.zip but quickly realized after flashing with flash fire I no longer could access recovery only fast boot. I wanted to know if there was a way to insatll su? I can wait until somehow someone finds a way to fix recovery but for now I want to be able to access the playstore and be able to use flash fire to maybe install another rom or flash amazon recovery if possible?

Note I have already tried disabling CM root to no avail it is still conflicting with supersu. I appreciate any suggestions. Thanks in advance. :fingers-crossed:
[Fire General] sd_shadow:
without knowing what bootloader version you have, guessing 5.1.x

no there is nothing that can be done with recovery

you could try installing playstore without rooting

http://xdaforums.com/showthread.php?t=3216122

Installing Google Framework/Playstore without Root 5th Gen Amazon Fire 7in 2015 ONLY
[Fire General] DB126:
Trashing recovery suggests an older version of FlashFire (pre 0.31) was used to install CM. At present there is no solution for restoring recovery access. If your device is still in warranty consider contacting Amazon for a one time courtesy exchange.
[Fire General] Designassist:
Os 5.1.2 fire flash v. 30

I installed cm12 via flashfire version 30. I was on amazon os 5.1.2 I downgraded from 5.1.2.1. Should I exchange it? It does work it just no longer has recovery. Do you think in the near future someone may find a solution?
[Fire General] DB126:
The lack of a functioning recovery may come back to haunt you should the installed ROM fail to boot or otherwise become unstable. At present you are depending in FlashFire (0.32 or above) to perform all updates which requires a stable ROM as it can not be launched independently. There are hints a method of restoring recovery may be in the wings but to date no one has successfully done it (or at least reported a positive result). Your call on the exchange - effectively working without a safety net.
[Fire General] Azure_:
So if I want to downgrade from 5.1.2.1 to 5.1.2.0, would I get the file for 5.1.2.1 or 5.1.2.0? Doesn't it say not to use the file from older versions?
[Fire General] DB126:
You can safely rollback 5.1.2.1 to 5.1.2 but no lower. For your purposes you want the 5.1.2 image.
[Fire General] Azure_:
Thanks for the quick reply!
[Fire General] Designassist:
I adb sidelined to downgrade from 5.1.2.1 to 5.1.2 using supertools by root junky. Just sideboard the bin. Make sure you pit it in the folder with adb in it or make sure you have adb outside the folder by editing the path in environmental variables.
[Fire General] Azure_:
Did you get the bin from Rootjunky's site or from Amazon? The one straight from Amazon is probably the 5.1.2.1 verison.
[Fire General] Designassist:
Amazon and I put it in the adb folder and inpute the commands.
[Fire General] Azure_:
Thanks, just did that. Still trying to root it with Kingroot. Still failing at about 30%. How many tries does it take?
[Fire General] Designassist:
https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin

---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485

Here the link to downgrade tutorial

---------- Post added at 09:10 PM ---------- Previous post was at 09:06 PM ----------

Did you downgrade yet? And when you root make sure you choose the right os. There is three options for rooting 5.0.1 5.1. 5.1.2 you have to select the 3rd option. And it went through the first time but it does say reboot if it doesn't go through. Then open king root again and getting rooting also check in for checker or esfile of you have one of those because you might be rooted and not realize it yet. That what I did because it rebooted at 30%.
[Fire General] Azure_:
Thanks, that .bin you linked did it.
[Fire General] Designassist:
Great if your flashing a rom with flashfire be carefully about the order in how you wipe because it can erase amazon recovery.
[Fire General] DB126:
Order of operations *is* important but getting it wrong will not "erase amazon recovery" or otherwise disable access to stock recovery using recent versions of FlashFire (post 0.30) and the rom of your choice.
[Fire General] Designassist:
I no longer have access to recovery and I flashed with flashfire 30.
[Fire General] DB126:
Reread post - FlashFire 0.31 and above recommended. v0.30 and below exhibited bad manners on this device with certain rom images.
[Fire General] Herox:
My kindle wont pass the amazon logo when I try to boot recovery. Any ideas?
[Fire General] DB126:
No resolution at present. Did you previously use FlashFire 0.30 or below to install/update a custom rom?
[Fire General] Herox:
Sure did. People in the flashfire thread said that's why it happened. I'm incredibly upset and if Amazon won't give me an exhange then I'm out 50 bucks on that and I cannot get another right now.
[Fire General] DB126:
Amazon is pretty good about exchanges if within warranty. Simply state it froze during an update. If outside warranty you're out of luck.
[Fire General] Herox:
Sure are. Got a replacement on the way. Hopefully they don't see it's been messed with and try to charge me for it. I have to send this one in once I get my replacement.
[Fire General] DB126:
They won't. Be aware the the courtesy exchange is a one-timer. Suggest posting your intentions if you plan to root or install a custom rom on the new device. Someone will help guide you to the best tools/techniques. Don't want to trash the replacement.
[Fire General] Dunard:
I stick with the Fire ROM because of a lot of reasons. I have a fear of installing CM ROM and Slim ROM. Always read up before doing something.
[Fire General] K5LK:
I'm enjoying the rooted Fire Rom with Google Launcher. Somewhat the best of both worlds for me so far. Stable and smooth from what I can tell.
[Fire General] blazinandroid1:
Can we downgrade this way... Just putting a check mark here..
[Fire General] DB126:
http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485/post62986665
[Fire General] Jordaliz09:
Oh Oh

"for KFFOWI/Ford, Fire 7in 2015 5th Gen Only

Download Firmware

System version 5.1.3 & 5.1.2.1 can be downgraded to 5.1.2

System Version 5.1.X cannot be downgraded to 5.0.X"

Not entirely true. I just hard bricked my tab trying to downgrade from 5.1.2 to 5.1.1 :'(

Better add that other line:

"System Version 5.1.2 cannot be downgraded to 5.1.1"
[Fire General] Y314K:
There is nothing on your quote that says 5.12 can be downgraded to 5.11 . But I guess adding the info will stop folks from bricking some tablets.
[Fire General] Kramar111:
Maybe "System version 5.1.3 & 5.1.2.1 can be downgraded ONLY to 5.1.2" would be better?
[Fire General] Jordaliz09:
Actually, the clarification must be not to attempt to downgrade to 5.1.1

Any downgrade to it, no matter the version, will get your fire bricked. But it's just a suggestion, put it as you want.
[Fire General] jje12435637:
i cant get the device to show up when in safe mode, i have updated adb drivers and it shows when conntected normally with adb enabled, but when in safe mode its a no show, any ideas?
[Fire General] sd_shadow:
safe mode?
[Fire General] ripteh1337:
Ok, so i think i have 5.1.2.1 installed, gets to 30 and errors out. Saw video on how to sideload a previous install but whenever using adb sideload command it states 'adb' is not recognized as an internal or external command operable program or batch file.
[Fire General] DoLooper:
You have 5.1.2.1 if build date in device settings>update is March. You need to install drivers for sideload mode. Go into sideload mode (yellow text on tablet), open device manager and install drivers just as you did for system mode.

EDIT: NVM. This was cross-posted [tsk tsk] and already answered.
[Fire General] badmojorayman:
Thank you just the same for repeating it. I've been on this issue for 3 hours now, and this is the first time I found an answer for it.
[Fire General] 03s1:
Hey my Fire tablet, can not be returned flashed. Currently is 5.1.4.

I want to 5.1.2. ADB drivers installed. ADB Devices is ok with the Serriennummer. Then I give CMD commands:

ADB devices

ADB reboot recovery

The tablet will boot

Then I want ADB sideload ........ Enter, but the connection is gone.

What am I doing wrong?

Driver is loaded, reboot also.
[Fire General] sd_shadow:
with device in adb sideload mode

select Other Devices>kffowi

Right Click>Update Driver Software

Browse my computer for Driver Software

Let me pick from a list of drivers on my computer

select Android or Android Phone (or ADB Interface or Android Device)

Select Android Composite ADB interface

you may have to reboot pc
[Fire General] guillermius:
Hi!...thanks for the info!

I do a downgrade from 5.1.4 to 5.1.2 in an unrooted kindle fire 5th and everything was happening like the tutorial.

But then when i reboot it never boot anything...my screen its just BLACK.

Im kind of freaking out.

And when i connect to the pc it seem that mt6xx preloader driver its trying to install but then disconect.

There is someway to do a hard reset or something?

Thanks!
[Fire General] sd_shadow:
that's not good

try power off then hold volume up button and power on

if it boots to recovery, select factory reset
[Fire General] guillermius:
Nothing happens.

I try volume down and power, volumen up and power and holding the power button for 60 seconds.

Nothing happens...

I think i blew it..ha
[Fire General] sd_shadow:
did you disconnect from the PC?
[Fire General] guillermius:
Yes, i try it disconnected and conected, i change usb port and reboot my pc (just in case).

I have to use a factory cable now?
[Fire General] sd_shadow:
fastboot cable doesn't work with 5th gen
[Fire General] fmc000:
Looks like there are two different 5.1.4 versions?
[Fire General] sd_shadow:
Could be
[Fire General] dunas2331:
I just got the 5.1.4 update. So just to be sure there is no downgrading of this version yet? I don't wanna brick my device
[Fire General] sd_shadow:
Tomsgt and a couple of others have successfully downgraded 5.1.4 to 5.1.2

just make sure that the 5.1.2 file it downloaded completely

I should post the md5 checksum
[Fire General] dunas2331:
I don't want what happened to the guy in post #170 to happen to me... I'm scared now
[MX Player] Consumers:
Option to show the resume position out of the video duration

An option in View -> Fields (or by default) to toggle an additional text field that shows the time the video will resume at, as well as possibly a progress bar at the bottom of the thumbnail that illustrates how much of the video has been watched. As reference, DicePlayer has this feature and for how relatively straightforward it is, it is very helpful.

Option/change to "finish watching" the current video when skipping to next

An option in Settings -> Player that either toggles between the current behavior and automatically completing the current video when skipping to next, or possibly a slider that automatically "finishes" the video if the user skips to next with the seek position at least 0-100% of the total duration. Skipping to the next video currently marks the current position in the video to resume at later, which has its uses but it poses a small, continuous inconvenience when used for entertainment in conjunction with always resuming. I typically don't even use the Next button anymore, instead manually seeking to the end of the video to mark it finished and reset if viewed again before continuing to the next video.

Option/change to more aggressively save resume positions

This may not affect others, but I have noticed that if the app is closed unexpectedly or perhaps if the device is shut down, the current resume position will remain the same and only updates when the video is paused or exited from within the app itself. While this doesn't occur often, it is still fairly inconvenient (especially for long videos, which would be annoying for things like podcasts or audiobooks). Either as a universal or optional change, update the resume position regularly (optional and/or longer intervals if it poses a performance/IO issue) as well as when the user "properly" pauses/exits the video.

I've used MX Player Pro quite a lot now, so I appreciate the work put into it. These suggestions are in response to some pet peeves I've had with resuming videos and would love to see any and all of the above implemented! Thanks!
[MX Player] EdwardSmith36:
I must thank you for this helpful post, let me try the instruction posted above!
[MX Player] Consumers:
Note that the post is suggesting the options/instructions listed. They're not implemented in MX Player as far as I'm aware. Sorry! I'd like to have them, as well.
[Fire TV Q&A, Help & Troubleshooting] thepacketslinger:
As far as I can tell, every custom recovery requires an old version and I haven't been able to successfully downgrade (on aftv2 and /cache is only 242 MB, whereas stock images are all 397 MB).

Is there anything I can to do get something like cyanogenmod working on an aftv2?
[Fire TV Q&A, Help & Troubleshooting] rbox:
a) What are you trying do downgrade to?

b) I am working on recovery.