yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
Seems unlikely:

- probably needs kernel support

- not baked into native CM 12.1

- requires high output USB port

- appears to be falling out of favor on newer devices

http://blog.clove.co.uk/2015/11/08/whatever-happened-to-mhl/
[Fire Original Android Development] platypoid:
You have that right - this CM version works great ! The battery lasts a very long time. I don't use if for anything too complicated but it does what it needs to.
[Fire Original Android Development] steve8x8:
adb shell "ls /data/tmp/file && echo OK", then check the output. (No idea how to do this with Windows :cool:)

BTW, "There be dragons updates" - better get a recent version. (I just found the build stamp of 5.0.0, and will add the 5.1.3 one once I have it.)

Someone willing to write an apk to cover the whole set of version reports?
[Fire Original Android Development] fuzzynco:
Better to always get a new copy from dropbox?

hmm are you suggesting it is better to always wget a new copy and push it?

would something like

adb shell "ls -b /data/local/tmp/file" > %TMP%/file

create a file with the output of the ls command

that I can then put into a variable to check for existing file

via set /p variable= < %TMP%/file?

I was thinking it would be better not to keep pushing

(updating on the flash memory) if the file was there.
[Fire Original Android Development] jaladhjin:
So I did the steps in the spoiler.. & also included Internal Storage in FlashFire.. because that's what makes me think really clears out all the internal storage files to fresh not just the specific last rom system data.. not sure if that's accurate or not that's why I mention it..

Coming from the Nexus Fire rom as well..

The CM image & GApps were on my external SD card & I chose them no problems when I setup the flash..

Now I'm stuck on the Amazon logo.. a bootloop I assume yeah ? :-/

Going to try a restart once after I give it a little more time but I assume I get to do some brick recovery type shenanigans since I don't have TWRP huh..

Which is fine.. I'll do it..

Why did it happen though ? :(

- Fresh Installation from FlashFire 0.50

- Click the Red + and choose 'Wipe'

- Ensure System data, 3rd party apps and Dalvik cache are CHECKED

- Click the Red + button and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Cyanogenmod Zip

- Accept defaults

- Click the Red + button again and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Open Gapps Zip.

- Accept defaults

- Move "Wipe" to the Top of the order

- Press the big FLASH button.
[Fire Original Android Development] Mr McBoatface:
Did you use flashfire 0.50 or 0.53 (0.53 is the current version on play store) ?

Something similar happened to me switching from Nexus to latest CM12.1. There was a mount failure error on flashfire screen. I remember reading up on it at the time and that in flashfire 0.53 there are 2 mount image options (the option appears when you select the CM12.1 flashable rom) . Those options should be unselected when flashing from one custom ROM to another (maybe an expert should confirm this :) ). Didn't test it myself I just done an ADB fire OS recovery to stock rom and rerooted the fire tablet using root junkies supertool and installed cm12.1

Good news is ADB recovery is easy enough to do, if you remember what fire OS you where on you can download that image and recover the tablet, reboot it to recovery and select adb install, using your PC and adb you install the Fire OS image . If you don't know for sure what Fire OS you where on it prior to flashing the custom rom you could try restoring the latest rootable fire OS, Fire OS 5.3.1. But returning to the fire os you had prior to flashing would be best.

Bad news is you're at risk of having an auto update to the latest fire OS which can't be rooted and can't be rolled back. This can happen if kingroot doesn't root quickly, the update downloads and installs without your interaction.

I believe you can block amazon update domains on your router if the router allows domain blocking..... Actually think I done this in December. Will check out later when I have a chance

EDIT On my TP Archer C7 router I've blocked the following domain's:-

edgesuite.net

softwareupdates.amazon.com

updates.amazon.com

amzdigitaldownloads.edgesuite

fireos-tablet-src.s3.amazonaws

amazonaws.com

I don't recall where I got the domain list from or if its accurate anymore, everyone's router will be different and some may not allow domain blocking. I don't have any amazon devices on stock ROM to test whether it still works. But at the time I was setting up my tablets (december 2016) the then latest updates didn't appear or download on my tablets.
[Fire Original Android Development] jaladhjin:
Whatever the latest from Play is :D

This actually happened.. lucky for me it only upgraded to 5.3.2 & I was able to downgrade to 5.3.1

Now though.. I'm stuck with Kingroot 5.0.3 & all attempts to get SuperSU on as a replacement have failed :(

Since they seem to be actively attempting to circumvent SuperSU taking over so people will use their software..

I believe supertool also pushes an old KingRoot still capable of being removed easily.. but that one kept failing.. so often that's what got me upgraded to 5.3.2 on a reboot..

So after I downgraded I used the latest KingRoot & it worked like a charm.. now to just figure how to get SuperSU to take over..

Alas http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html & similar didn't work :(
[Fire Original Android Development] jasonmerc:
[MENTION=5349270]jaladhjin[/MENTION] did you at least disable OTAs in the meantime, so you can be stuck on 5.3.1? I'll look into solving this SuperSU issue as well.
[Fire Original Android Development] jaladhjin:
Yup yup I did the block OTA with Supertool.. hopefully it holds :D

Didn't block any packages but maybe I should.. kinda figure that's what Supertool did but it'd be good to know on my own to check'm too :D
[Fire Original Android Development] jasonmerc:
Now I didn't read the article you had about putting SuperSU on, but here's a plan I just thought of that may or may not work (I apologize if I'm just repeating what the article said)

Enable debugging, connect the tablet to a computer, get in adb shell, and get root privileges on that shell session. I believe there is a command to disable apps through ADB, but I forget what it is or the syntax involved. Anyway, disable the Kingroot app through root ADB with whatever that disable command is, then try to install SuperSU and update the su binaries in it. Not sure how permanent something like this is, but if it at least gets FlashFire to work where you can flash over to CM12.1 then it's mission accomplished.

EDIT: once in ADB with root privileges, type "pm list packages -e" and look for kingroot's app name. It should be something like com.android.kingroot or whatever. Once you find its com.whatever name, type "pm disable com.whatever". This should disable Kingroot.
[Fire Original Android Development] DB126:
- don't bother with packages; simply toggle off WiFi to block OTA updates while working other issues (belt and suspenders)

- see here for info on removing KingUser
[Fire Original Android Development] Mr McBoatface:
Well done on recovering and rooting the tablet, hopefully you'll get the supersu package on soon.

In my experience if kingroot in the supertool failed repeatedly it was solved by removing any SD cards and making sure I removed the usb cable connected to the pc. When it rooted just connected the cable and picked up where I left off on the installation script.
[Fire Original Android Development] steve8x8:
Not "always" but "occasionally". If you're happy with the current version then keep it. Additions may cover 5.0.0, 5.1.[34], and future stock versions, eventually.

If you don't want to overwrite with identical content, use rsync.

Flash wear may happen due to writes to /data, but the probability is rather low that your foreground actions will cause it.
[Fire Original Android Development] jaladhjin:
Only issue i could see happening with that is if I attempt to disable or otherwise kill Kingroot.. my root acccess will go with it won't it ?

thanks to davey showing me it seems like Tomsgt has a decent post on a starting point of working around 5.0 KR but they might have updated more anti circumvention in this 5.0.3 I have or something since it isn't working either..

It does seem like SuperSU is granted root by KR in its own properties but I'm not sure that would do me any good if I disable KR..

Seems like one other problem too is KR did away with the "KingUser" app.. it's all contained in the singular Kingroot now.. or at least that's all FireOS shows anymore..

At this point & after the almost loss of root potential currently I'm not to keen on trying anything while on FireOS that's going to mess with my root..

Luckily I was able to downgrade from 5.3.2 or I'da been wrecked on root 'til KR updated.. haha

I've been askin' the SuperSU-Me fellow too if he'd allow me to test some potential fixes they roll out for 5.0x KR removals so we shall see..

It's just sitting here awaiting something atm.. lol
[Fire Original Android Development] jamoosh:
Hi everybody, I was wondering if anybody has flashed the latest version via TWRP, overwriting 12.1-20151216-UNOFFICIAL-ford, without losing their applications and data. Thanks in advance for any input, and thanks to the developers and users contributing here on XDA.
[Fire Original Android Development] yochananmarqos:
Yes, dirty flashing will not wipe user data.
[Fire Original Android Development] Mr McBoatface:
If you've blocked OTA updates no harm in uninstalling kingroot app. Then without rebooting use rootjunky's tool to retry the kingroot/supersu install script.

I just brought one of my fire 7 back to stock 5.3.1 and can confirm my router blocked amazon updates, super tools rooted after 2 attempts.
[Fire Original Android Development] jaladhjin:
I had actually been thinking I wonder if I could do that too.. don't see why not..

Wonder what packages actually in block OTAs do you know ?

I could ensure they stayed disabled too with other methods :D
[Fire Original Android Development] Jrhotrod:
Use the Super Sume app. It's a few bucks on the Play store but free with a few Google searches... I'll leave that up to you.
[Fire Original Android Development] DB126:
SuperSume app yielded soft bricks on 5.3.1. Developer may have updated it but to date the has been no indication (forum posts) that has happened.
[Fire Original Android Development] Jrhotrod:
Okay then. Sorry that didn't help
[Fire Original Android Development] jaladhjin:
I've actually already been in touch with that dev.. offered to test potential fixed releases on my device.. so on & so forth.. awaiting to hear more :-/

And saw it mentioned somewhere don't reboot after SuperSu-Me does it's thing or that's when the soft brick occurs..

Currently you're instructed to let SuperSU-Me do it's thing.. then right away Flashfire your rom without a reboot..

Anyway it isn't updated for 5.xx Kingroot sad to say :(
[Fire Original Android Development] JustIceForSake:
Hello,

I have a Fire 5th generation in the options so if I'm not mistaken I could install this rom right? I'm still using Amazon's original ROM, would you recommend switching to this (or other ROM that you can point out) over it (how is performance and stability compared to Amazon's OS)?

Anything important I should consider before making the switch?

Thanks!
[Fire Original Android Development] Mr McBoatface:
If you're fire tablet has Amazon's latest OS version 5.3.2.1 you're stuck with it as currently it can't be rooted or have have flashfire installed. Flashfire and root SuperSU are needed to install custom roms

If and when the latest amazon OS can be rooted is unknown.
[Fire Original Android Development] JustIceForSake:
Yep, I was just reading this on another thread...I'm stuck on Fire OS 5.3.2.1...lucky me.

Well, I saw that I could at least put Google Play on it...I will do that hoping that in the future someone can crack the "5.3.2.1 locked Fire". ;)

Thank you for the reply btw.:)
[Fire Original Android Development] Jrhotrod:
Actually, I'm pretty sure that you can easily sideload FireOS 5.3.1 (rootable) from recovery mode easily. Please note that I am not responsible for bricked devices. Here's how to do it:

1. Go to http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool and download the AmazonFire5thGenSupertool.zip. Extract it to somewhere where you can conveniently access it.

2. Also go to http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/Firmware and download fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin.

3. Now open the Supertool folder you downloaded and run auto.bat. Once everything loads up, select option 1 and when those options load, select option 3 to test your drivers. Depending upon your result, you can install the necessary drivers now or move along as you were. This test can also determine whether you have ADB.

4. Enable USB debugging on your Fire.

5. Plug in your tablet.

6. Now go to the folder where you downloaded the 5.3.1 firmware. Hold down Shift and right click inside the folder. Select "Open command window here".

7. Type

adb devices

in the window. If a series of numbers appears, then your Fire is recognized and you are good to go. If it says "unauthorized", you may need to turn on the tablet and allow USB debugging from this certain PC.

8. Now reboot your tablet to recovery by typing

adb reboot recovery

.

9. Once in recovery, on your Fire select "Apply update from adb". Now go to the Command Prompt window you have open and type:

adb sideload fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin

10. The downgrade will begin in earnest. DO NOT be afraid if it says "patching system image unconditionally" because that is TOTALLY NORMAL and you will be fine. You will know when the downgrade is complete when the menu reappears on the tablet.

11. Now select on your Fire "reboot device now".

12. Okay! You are now in a ROOTABLE ROM! To take advantage of this we need to go and open the Fire 5th gen Supertool once again and this time select option 6 (or whatever it is) and root device now! Follow the onscreen instructions.

BOOM! Done and rooted with SuperSU. Now you can install CM 12.1. Contact me if you have any questions regarding this or the ROM.
[Fire Original Android Development] Mr McBoatface:
DO NOT DO THE ABOVE...... IT WILL BRICK YOUR TABLET IF ON FIRE OS 5.3.2.1

It worked on fire OS 5.3.2 to Fire OS 5.3.1 because the boot loader files where the same , but they change in 5.3.2.1
[Fire Original Android Development] Jrhotrod:
Oh, the bootloader changed? Dang it... I thought that it would still work with 5.3.2.1. Is there any alternative (even temp root) that we could use...?
[Fire Original Android Development] Mr McBoatface:
Not at the moment
[Fire Original Android Development] Jrhotrod:
Then maybe this guy's best bet is to buy a replacement. When you first buy the tablet it's typically running an older version of FireOS
[Fire Original Android Development] Mr McBoatface:
Most tablets sold since January have the new firmware pre-install. You could be lucky and find a store with old stock but would have no way of knowing till you fired it up (pardon the pun). Best bet is to hold on and see if a root method come along.
[Fire Original Android Development] DB126:
*** warning *** warning *** warning ***

Do not attempt to flash/install/sideload fireos 5.3.1 if current version is 5.3.2.1 or greater. Device will hard brick with no possibility of recovery.

*** warning *** warning *** warning ***
[Fire Original Android Development] Jrhotrod:
Yes, my bad. That method works for FireOS 5.3.2, but not 5.3.2.1. thanks for the heads up Davey126
[Fire Original Android Development] jaladhjin:
You could try the latest KRs if you want to be adventurous..

Get them straight from the source not Supertool or something until they release updated files.

Just know.. if you do this you're sailing into dark waters.

You may sail back with a chest of dubloons & let us all know we're good to root 5.3.2+

Or you'll be visiting Davey Jones Locker
[Fire Original Android Development] jaladhjin:
Why oh why oh why is there no mention of Root in post 1 or 2 :(

I finally got my recovered rolled back tablet figured out.. I'm on CM but no root :(

Doesn't mention anything about Flashfire'ng SuperSU or anything.. that I saw anyway..

So I'm on this CM.. I really have to reroot with KR ?

I'm used to major custom roms like that coming prerooted :-/

Sa'right though.. I need to re-root it with KR amirite ? :(
[Fire Original Android Development] GhostRider86:
Root is build in this CM build, see developer options, reboot after enable root for apps (root for adb seems to not work in most cases)
[Fire Original Android Development] kyledowling:
If your on CM then use the built in root in developer options to grant FlashFire root access then flash SuperSU using FlashFire.
[Fire Original Android Development] jaladhjin:
Even if you enable it ?

When you turn it on you have 3 options:

Apps

ADB

Or Apps & ADB
[Fire Original Android Development] freaky2xd:
the resolution is very weird
[Fire Original Android Development] GhostRider86:
Go into Developer Options, Enable root for apps, reboot, enjoy root. If you know what you are doing, flash SuperSU.
[Fire Original Android Development] jaladhjin:
Why didn't you mention anything about root like this isn't pre-rooted so flash SuperSU after GApps in your install instructions :(

Or did you & I'm not seeing it somewhere ?

I have enabled root for Apps and ADB in Developer options..

It does not seem to work..

SuperSU itself installing from the Playstore isn't updating the binary the Normal method.. or even asking for root :(

Flashfire isn't asking for root access of any kind either so I can't do as the gentleman above suggested..

KingRoot doesn't seem to be able to root this CM 12.1 either :(

After all this which was & is totally my own fault.. of boot looping restoring downgrading having issues removing Kingroot I finally finally got CM 12.1 loaded up..

And now.. no root :(

Would you please update your Post #1 to reflect oh by the way this isn't pre-rooted so flash your Superuser package of choice in addition to this rom & GApps..

I'm sorry if I sound frustrated but I am..

and to be very clear I know it's not all your fault.. it's not your job to make sure I know what I'm doing..

But that's a very critical piece of information..

I thank you very much for your awesome roms I want to make that clear.. you're a gentleman & a scholar..

That being said do you or anyone have any advice other than going back to FireOS.. re-rooting & flashing SuperSU this time in addition to the rom & gapps ?
[Fire Original Android Development] Jrhotrod:
Depends on your ises. If you plan on just using apps, then enable that. Same with ADB if you plan on solely using root on that. I personally enable both because I use ADB a lot, but it's your call.

Also, CM has a built-in Superuser app. It's okay, but I recommend downloading SuperSU from the Play Store to replace it. SU binary should update fine (choose Normal).

Let me know if I helped.

EDIT:

I noticed you said that the SU binary won't update... That's weird because it worked for me. Is your bootloader unlocked?
[Fire Original Android Development] jaladhjin:
The built in super user enabled in Developer Options doesn't seem to be working.

And unlocked boot loader..

What ?

You know we're talking about Kindle Fire 5th gen right ?

Now that I'm saying that though some of the real old ones could be unlocked at the boot loader level couldn't they.

Nope I do not have an unlocked boot loader or I'd flash with TWRP and never have any issues [emoji1]
[Fire Original Android Development] Jrhotrod:
Well, my sister was able to unlock her bootloader back in the 5.0.2 days, so I was just checking.

So, how is exactly isn't this working? Is it just not properly granting root access or is it not prompting? It is it something else? If you can post screenshots or links to them that would help.
[Fire Original Android Development] GhostRider86:
It is working, enable it in developer options and reboot!
[Fire Original Android Development] Mr McBoatface:
Root is built into CM12.1 you just need to enable it after flashing CM12.1 to your tablet.

To enable root on your tablet after flashing CM

(1) Go to "Settings" menu/app , navagate to "About Tablet"

(2) Click on it, then find "Build Number" ,

(3) Tap "Build Number" 5 times to enable developer mode, it'll let you know when its enabled,

(4) Return to previous menu you'll see "{ } Developer options" now appears the menu

(5) Open it , Click "Root access" and enable the root type you want, personally I choose "Apps and ADB"

(6) Reboot

(7) All is well in the world :)
[Fire Original Android Development] ggow:
[MENTION=5349270]jaladhjin[/MENTION]

- It is well known that CM-12.1 includes built in root. I implemented workarounds to enable this to work with a locked bootloader.

- While it may not be in the OP or the 2nd post. It is well documented how to get the the built in root to work and using the search facility of the thread could have saved you some time.

- Kingroot cannot work for CM-12.1 because in general it is much more secure than Amazon's crappy FireOS.

- The only difference between this and other devices that are unlocked is you need to reboot for the permissions to be granted correctly.

- I'll add something to the OP on the next ROM update.
[Fire Original Android Development] sd_shadow:
There is no unlocking 5th gen bootloader

5.0.X firmware versions allow booting custom recoveries, that is not the same as unlocked
[Fire Original Android Development] kyledowling:
Enable root for apps and adb then reboot and all will be good
[Fire Original Android Development] Jrhotrod:
My bad then, thanks for the correction.
[Fire Original Android Development] zeusminos:
How long it takes to fully recharge the battery? I am using the latest ROM and it takes more than 5 hrs
[Fire Original Android Development] RedsonRising:
Plug it in and turn it off, it'll charge faster. Mine charges up fairly quickly, maybe a few hours from 30%.
[Fire Original Android Development] zeusminos:
Are you using the standard wall charger? Have you tried the new smart chargers?
[Fire Original Android Development] borisboing:
Mine charges from empty to 100% in under 3 hours, although I usually charge at around ~50% which takes roughly a little over an hour.

Using supplied USB adaptor and cable.
[Fire Original Android Development] zeusminos:
3 hrs to get full charge :-0. Mine more than 6 hrs. What a junk :-/
[Fire Original Android Development] xenokc:
Looking forward to LineageOS port. Am concerned the security path levels are now a few months old with Nov CM release.
[Fire Original Android Development] kramalot:
About 3 to 4 hours typically from 20 or 30 percent. But hell, it cost $50 or 50 ukp to me, thanks to the tech exchange rate :'( (the way things are going of course the real exchange rate and the tech exchange rate will soon match!).
[Fire Original Android Development] DB126:
Bootloader can not be unlocked (yet) on this device.

---------- Post added at 04:00 PM ---------- Previous post was at 03:52 PM ----------

Not likely. No LineageOS ports for Android 5.x (Lollipop) which is the highest version of Android that can run on this device due to kernel restrictions. Can not update kernel as bootloader remains locked. Development community is aware and considering options.

---------- Post added at 04:18 PM ---------- Previous post was at 04:00 PM ----------

- device is equipped with 2980mAh battery

- charge circuit tops out at ~850mAh

- Lithium-icon cells never fully discharge (safety feature)

- (2980*0.9)/850 = ~3 hrs to fully charge

- stock charger is rated at 1A and should be sufficient

- cables and/or loose connections are the #1 culprits in poor charging performance assuming source has sufficient capacity

- in this case ROM is irrelevant as charging is regulated at lower levels