yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DragonFire1024:
My Android Tools is very awesome. It's good for a good many things. Also a very powerful app that can also brick you if you tap the wrong switch. With this tool I've been able to see there are more than a few packages running OTA.
[Fire Original Android Development] Jrhotrod:
This for sure. Privacy Guard is a great tool that I use in every one of my devices running LOS (which are many). I recommend checking it out, especially for privacy-minded users.
[Fire Original Android Development] gompka:
Got bit by Flashfire again :( stuck on Amazon screen.
[Fire Original Android Development] t3chwizard:
DS battery saver seems to be running fine so I don't mind.
[Fire Original Android Development] deepsunzhine:
Guys i need help. My tablet is useless. I flash from nexus rom with gapps and lineageos works but no gapps and privacy browser dont let me install any apks. I dont have google services nor playstore. File manager dont see the apks on the download folder. When i go to downloads on homescreen i see the apks but says cant opne file. Im trying everything i can nothing works
[Fire Original Android Development] ipdev:
You should be able to use adb to install apps still. Enable Developer Options and make sure Android debugging is toggled on.

Depending on how broken the install was, you may have to revert back to fireOS and start over.

As for gapps not installing: my experience with this device

- Wrong version or not enough room detected to install

- Removing CMSetupWizard with a gapps_config file

- Installation failed don't remember the exact error but, the ff lastlog may show an abrupt reboot

Note - You got one up on me. :)

I get stuck at the Amazon splash screen if I flash lineage from Nexus.

I can flash Nexus from lineage though.
[Fire Original Android Development] DV8_MKD:
Hi guys. I had trouble with lineage-12.1-20180315. I installed it fine with FlashFire but had an issue with the unlock screen. I needed to press the power button 2-3 times and swipe the screen for it to unlock.

Before it unlocks, the privacy guard dialog would show and no way to press on it. So, after reading that there is an issue with this build of LineageOS I went and downloaded the latest one.

I tried using FlashFire to install it but it crashed as soon as it showed the "looking for Pro" line. I tried 15 versions of FlashFire and nothing worked. Then, I read somewhere that I should change the system date to any time before today. I was desperate. I tried it and it worked. FlashFire loaded fine and I installed the latest build just fine.

However, the primary issue persists. When I try to unlock the screen, at first it does not respond to swiping at all. I need to press the Power button 2-3 times before swiping to unlock has any reaction.

And the privacy guard dialog is still there, like it prevents the unlocking gesture.
[Fire Original Android Development] DB126:
Unlikely the latest build installed 'clean' or at all. Best redo the install making sure to wipe the system partition before replacing Lineage. Don't forget to include a suitable GApps package (recommend Open GApps arm/5.1/nano).
[Fire Original Android Development] DV8_MKD:
Wiping the system worked. Everything is working now. Thanks!
[Fire Original Android Development] ScouseReaper:
HI, does anyone have superuser issues? Flash fire closes after checking pro and supersu says "su binary occupied" thanks in advance.
[Fire Original Android Development] DB126:
This was a known issue on numerous devices (not just Amazon gizmos) with SuperSU builds prior to 2.82 SR3 (current is SR5). The only reliable solution is to reinstall FireOS and start over.
[Fire Original Android Development] ScouseReaper:
I have superuser working again but flashfire is still crashing, do I still have to start over?
[Fire Original Android Development] DB126:
You can experiment by uninstalling/reinstalling FlashFire. It's picky about the root solution. If using something non-standard, intentionally or otherwise, it'll probably kick out. Question then becomes how important FlashFire is to your immediate interests.
[Fire Original Android Development] ipdev:
Quick Reminder.

I only mention this here because the majority of users have to use FlashFire with this device.

FlashFire has a built in "TimeBomb" date for Non-Pro version users.

FlashFire v0.73 - 1st. April 2018. (That was five days ago ;) )

FlashFire ReleaseNotes

FlashFire checks for Pro when you start it. If Pro is not detected, and it is past the "TimeBomb" date, it will abruptly close. Appears like the app crashes.

Easiest work around.. Change the system date to something earlier than 2018.04.01.

Pro users.. Need to be logged into your google account when you run FlashFire for the first time so it can find the pro purchase.

Note: I set my date back to 2017 when I have to make a pitstop on fireOS before flashing a custom ROM. Once I am safely running a custom ROM, I log into google so FlashFire can detect pro.
[Fire Original Android Development] ScouseReaper:
You sir are a legend.
[Fire Original Android Development] kgirlx:
A quick check of changing system date and reopening FlashFire works. I just changed it to March 31st, FF worked instead of closing as stated above. Thanks for the heads up in case I need to update Nexus ROM. Currently running latest Nexus.
[Fire Original Android Development] gostmn26:
Ok, so here are my test result with the 25MAR2018 lineage update.

I started with both of my kids fire's, they were both on the latest version of Nexus (17DEC2017).

On my sons, I used the latest version of flashfire, the settings i used was.

-Wipe was at the top

-zip install for 25Mar2108, I clicked on "system read/write"

-zip install pico gapps.

This led to the Amazon screen for an hour. I ended up side-loading fire OS 5.1.3 back onto it and and then redo'ing lineage, without read/write checked. Also, GAPPS didn't install initially and had to use flashfire after initial install for it.

On my daughters fire, I reset to factory and installed the latest flashfire. Afterwards flashfire kept shutting down when clicking to open. I then turned the date back to Apr 1, 2018 and it still closed out. When I set the date back to Mar 31, 2018 flashfire ran fine.

The settings I used for hers are:

-Wipe/ default settings

-Lineage/ default settings

-Gapps-pico/ default settings.

My guess is trying to update from a previous version isn't going to play too friendly for people. Best bet is to make sure to backup your things and do a system wipe. Then you can install the updated lineage/ with security updates.
[Fire Original Android Development] Blob Blobbed:
Dude you did an incredible job here. This is literally the best my fire has worked since I got it. I bet Jeff Bezos never thought Id still be using this $50 abomination 3 years laters. screw you jeff
[Fire Original Android Development] DB126:
Even a full system wipe is no guarantee of a successful outcome. Tried that on a previous release only to observe the telltale FlashFire error stating the system partition could not be mounted. That leads to a borked install and subsequent freeze on the bootloader graphic (Amazon logo). Fortunately, all of my 5th gen devices have the ability to boot TWRP so recovery was easy. For most rolling back to FireOS and starting over is the only recourse.
[Fire Original Android Development] nirogu325:
Man, you reminded me that I need to repair my other Fire tab motherboard. It only needs the micro USB connector soldered. That one came with the first firmware.
[Fire Original Android Development] riverstyxxx:
Don't update or you will live to regret it. This is three times I've been through it, rooting fireos is getting more difficult with each reinstall. This rom needs to be retired while it's still ahead.
[Fire Original Android Development] DB126:
I concur with the general guidance not to update via FlashFire unless you are willing to do the FireOS rollback tango. Especially given no significant improvement in the latest builds beyond routine security patches whose 'benefits' can easily be duplicated via good app hygiene and responsible online behavior. That said, there is no need to retire something simply because it is difficult for some to install.
[Fire Original Android Development] riverstyxxx:
I'd rather be dragged through the sahara desert with my tongue nailed to the bumper than go through it again, last time it took nearly all day to root.
[Fire Original Android Development] DB126:
Understandable. After three sour experiences sounds like you are a good candidate to install and freeze. Best part - you control all the knobs!! No one is ramming an update down your throat. Best way to avoid pain is to avoid the thing that causes the pain. :)
[Fire Original Android Development] riverstyxxx:
Yeah that's nice. You're that penguin who goes around blaming everybody else instead of doing something about it...As if you could if you wanted to, are you even a developer?
[Fire Original Android Development] DB126:
Seriously dude. Reflect upon your experiences, choices, actions and outcomes. The mirror seldom lies unless we ask it to. Be happy for what you have and for the considerable time and effort of others that liberate and enrich a simple gizmo that was designed strictly as an Amazon shopping portal. Even when those processes and products are less than perfect. Don't like it? Go back to FireOS.

Qualification challenge?? Oh boy.
[Fire Original Android Development] nirogu325:
Davey126, I think it's just best to report his behavior to a mod. It's the 2nd strike.
[Fire Original Android Development] DB126:
Thanks for the support - but naa. There are no XDA violations here. Got a couple high spirited individuals exchanging perspectives on an uncomfortable event. No one enjoys hours of rework from what should be a routine 15 min task. Been there, done that, yuk! We have all smashed a finger driving a nail. How one responds to that experience (both in the heat of the moment and after some reflection) usually determines how one will approach a similar situation should it arise. Doing the same thing without modification will generally yield a predictable outcome. Hey, we've all done that too! Does not mean the opportunity itself should be eradicated. I now use a spike holder and refrain from blaming the damn hammer. In the absence of a suitable solution or off-setting benefit I won't engage in a discretionary task that leads to discomfort. Simple stuff.
[Fire Original Android Development] nirogu325:
No, you know what I'm pointing out. Last time you pointed it out for him and talked about the "this group" remark. Now he's calling for a ROM retirement. I don't think that's the right way to voice disappointment. Let us remember ggow is the only developer we have.
[Fire Original Android Development] DB126:
...and the 'problem' (which can be avoided by leaving well enough alone) likely crosses several boundaries which are outside [MENTION=5749760]ggow[/MENTION]'s control.
[Fire Original Android Development] nirogu325:
Fair. I'm just grateful for what ggow has been voluntarily doing for so long.
[Fire Original Android Development] Neffy27:
Indeed! This is my first and only tablet.
[Fire Original Android Development] prisoner1969:
I'm grateful too. I was lucky enough to get one of the early tablets without major issues. I was able to do the twrp method. Tablet is a little weak on ram and is sometimes slow but for $35 it's been a good offline Wikipedia reader using kiwix app. The entire Wikipedia in a 60 gig download for the first time but it's been good when I needed info and didn't have internet access.
[Fire Original Android Development] melvinaury:
I agree for the ones with TWRP thete is no issue. Is only for the ones that need to use Flash Fire..
[Fire Original Android Development] chaosp:
Is this note valid also for the later updates?!
[Fire Original Android Development] DB126:
A clean wipe is NOT required if updating from a build dated Jan 28th '18 or later.

That said, strongly advise NOT attempting to update your existing Lineage build using FlashFire. There is a very good chance the update will fail necessitating reinstallation of FireOS to recover your device.

Stick with what you have; be happy your device is working.
[Fire Original Android Development] chaosp:
[MENTION=5488402]Davey126[/MENTION]

Thank you for your answer! My tablet has the version from 20171202 now. I've asked because it's getting slower and slower and I thought about a fresh flashing and install of the apps.
[Fire Original Android Development] Ma4x:
I'm at the moment on CyanogenMod 12.1-20160203.

SuperSU is installed.

I tried now to install TWRP to flash LineageOS.

But the install of TWRP failed:

root@manjaro# adb reboot-bootloader
root@manjaro# fastboot boot TWRP_Fire_2.8.7.0_adb.img
downloading 'boot.img'...
OKAY [ 0.604s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.607s

fastboot devices give me the device in fastboot mode back.

What i am doing wrong?

Or is there any other way to flash LineageOS on this CM Fire Tablet?
[Fire Original Android Development] DB126:
The Bootloader on your device does not support booting a custom recovery and/or modifying the recovery partition. Your can try using FlashFire (see OP) but there's a good chance the installation will fail necessitating reinstallation of FireOS to recover the device. Recommend leaving well enough along. If you do go the FlashFire route you must set the date to 20180331 or earlier due to embedded time bomb.
[Fire Original Android Development] scooter1979:
I can't find a Pro key to purchase in the Play store, so I was going to set back the date for the time being... How the heck do you set back the date?? I keep getting the "automatically set" message every time I tap the date in settings. I'll be happy to pay for Pro if I can get the dang thing running.

Edit: currently on FireOS 5.3.1, rooted and all.
[Fire Original Android Development] DB126:
FireOS is such a restrictive PiTA. You will probably need to use an adb shell command to accomplish the deed on your rooted device. I will leave it as an exercise to research the required command structure. There is probably a tricky app to pull this off; couldn't immediately find one in the Play Store given the lousy search options. Probably because root is required.

Once you get FF fired up immediately purchase the 'pro' version to avoid the hassle of rolling back the date whenever you need to use it.
[Fire Original Android Development] scooter1979:
Ok, thanks. I wasn't sure if I was missing some less obvious yet easier way. I'll do some searching, I'll be sure to post back if/when I find results.
[Fire Original Android Development] frankslade:
Hi Guys !

I've an issue with ford of my son running the CM-12.1 [22 Nov 2016] with root apps and adb activated from CM developer settings...

when I start Flashfire (whenever version tried from 0.57 to 0.73), after few seconds it crashes... Can I install Lineage 12.1 using RASHR flash tool ?

or I have only to use Flasfire ?

It is possible install this Lineage directly from CM ?

Thanks!
[Fire Original Android Development] DB126:
Obviously didn't search (this thread in particular) before posting. No, you can't use RASHR or any of the other flashing toys. You'll need to push the date back to get FlashFire v0.73 running. In fact that was the topic of conversation in the post just prior to yours. Imagine that.

Also suggest searching this thread for "CM" or "12.1" as the likelihood of going from CM to LOS without a lengthy detour to painsville is rather high. Might be better to stick with CM unless you're up for some tinkering.
[Fire Original Android Development] frankslade:
Searched, thanks ! But all the cases are different from mine... later I'll try with date change, thanks.

I have to change coz CM12.1 are too old and slow to do everything...

Bye!
[Fire Original Android Development] DB126:
Updating to Lineage 12.1 will do little to address the issues you mention as it is nearly identical under the covers to CM 12.1. Sure, it will feel faster at first being a fresh install. But the sluggishness will soon return due to hardware characteristics and common code of both ROMs which are based on Android 5.1. Just trying to set expectations and save you some potential pain. Good luck.
[Fire Original Android Development] frankslade:
Ok! Thanks !
[Fire Original Android Development] ipdev:
[MENTION=3037872]scooter1979[/MENTION]

Most of the time FlashFire installs as Pro for me even after a factory reset and sideload of fireOS. I remember reading something about this quirk a long time ago.

If you haven't found it yet, the command line code has to be run as root.

date -s YYYYMMDD

Examples.

adb shell

bash-3.2# adb shell su -c "date -s 20170520"
Sat May 20 00:00:00 GMT 2017
bash-3.2#

or

bash-3.2# adb shell
shell@ford:/ $ su
root@ford:/ # date -s 20170420
Thu Apr 20 00:00:00 GMT 2017
root@ford:/ #

Install and run from a terminal app.

u0_a15@ford:/ $ su
root@ford:/ # date -s 20170101
Sun Jan 1 00:00:00 GMT 2017
root@ford:/ #

Note: From what others have mentioned. You need to predate to start ff, and then correct the date when you go to purchase "pro". PlayStore gives an error if the date is wrong.

;)
[Fire Original Android Development] scooter1979:
Let me ask this... Does anyone know, if I purchase FF Pro on a more date-mod friendly device, will the Pro license show up on my Fire when I try to run FF there?
[Fire Original Android Development] TripOG:
It does, I used that same method last night.
[Fire Original Android Development] Samwest1:
Fire7 lineage os xposed

I have got my fire rooted from 5.1.2 fire os . After that i put xposed on it and everything was fine. I was then able to flash with flashfire .73, lineage rom.That worked fine, but now im trying to put xposed onto it, and i cannot get flashfire to install the xposed framework. Is there something im missing. Am i trying to install the wrong xposed framework , as far as lineage rom is concerned. I used the fire supertool to root and install flashfire, and that program had xposed framework within , once i got flashfire installed the framework was ready to be flashed when i opened flashfire. On fire os it worked, but now on lineage i cannot get it to install xposed. I dont know,maybe i missed a part of thread that explained it, or that it wont work with lineage, idk. Ive been reading and reading and reading threads , trying to find an answer before asking on here,but im kinda stumped. Can anyone maybe throw me some ideas of possibile ways to get xposed installed on lineage 5.1.1 os on fire 7. Please. And im sorry, if this has been gone over, i tryed to find the answer by searching for last day and a half already.
[Fire Original Android Development] DB126:
Xposed framework and most modules work fine with the Lineage 12.1 build for this device. Unfortunately, you haven't detailed what is failing when and how which is essential for providing meaningful assistance. You'll want to use the SDK 22 arm framework (v89) which can be secured from here. After flashing the zip you'll need to (re)install the Xposed management app which can be obtained from the same link.
[Fire Original Android Development] Samwest1:
Flashfire wasnt installing xposed on the tablet, re installed flashfire and xposed, from within the supertool and got it working.
[Fire Original Android Development] frankslade:
Hello!

Changing date on Flashfire 0.58 (0.58 cause was already installed on tablet) I installed Lineage 12 and Gapps Pico 5.1 without issues !

After the reinstallation of all the apps, I had no issues or lags... for now more stable and fluid than CM 2016...

THX!
[Fire Original Android Development] Samwest1:
Anyone have any info on different commands to change the date on kindle fire 7 on 5.1.2 .0n 1 of my tablets, it started at 5.1.4 and downgrade to 5.1.2, i ran code to change auto time set to 0, so that feature of setting date and time when connected to network. , is disabled. It worked , and when i go to date and time in settings , i click change date and it comes up with a calander now and ican change the date to whatever i want.

Now the other tablet started at 5.1.3, and i downgraded to 5.1.2 with the same files and process, i got it rooted, but i cannot change the date and time , it worked to change it when i first rooted the tablet, but then flashfire still wouldnt open , even with the date changed back to february 5th, so i tried re installing flashfire again and again after uninstalling it and it didnt work. Nothing i do at all changes the date. Ive factory reset and ran the adb codes again. But date wont change. After the factory restore and re root. The calander doesnt even come up, it just says date and time set by network or somthing to that extent.

The codes i ran were

Adb shell, (i have root so didnt put su to get into rootford instead of shellford but did it both ways)

settings put global auto_time 0

And

date 010219302018.00 set

And

am broadcast -a android.intent.action.TIME_SET

That worked on one fire, but other doesnt change the setting to make it able to manually set date and time , and im kinda stumped. Im new to running adb commands. I thought maybe when i put the commands in for the second time it did somthing i wasnt aware of and messed it up. Idk. After i run adb shell , do i need to run a code to disable shell after im done using adb shell. Just wondering, i thought on one of these threads, someone mentioned exiting shell when done, or disableing it i thought, i wasnt sure so wanted to ask.
[Fire Original Android Development] ipdev:
I got a chance to do some testing.

fireOS 5.1.1 WiFi enabled and connected.

settings put global auto_time 0 - Auto was disabled

date 010219302018.00 set - Did not work

date 010219302018.00 - Gave me August 19, 2021 10:03 AM

date -s 20180102.193000 - Gave me Jan. 2 2018 07:30 PM

These devices are based on Android 5.1 (or so I thought :confused: )

Android 5.1

date [-s 20070325.123456] [-u] [date]

Android 6.0 -> 8.1 The date format changes along with command syntax

date [-u] [-r FILE] [-d DATE] [+DISPLAY_FORMAT] [-s SET_FORMAT] [SET]

am broadcast -a android.intent.action.TIME_SET is not normally needed in Android 5.1

Used in Android 6 and up to trigger the time change right away, instead of having to wait a minute.
[Fire Original Android Development] starmagoo:
Is there another way to flash the ROM besides FlasFire?

FlashFire does not work for me: https://xdaforums.com/showpost.php?p=76338843&postcount=6582
[Fire Original Android Development] DB126:
FlashFire is the only viable solution for most devices (specifically bootloader builds v5.1.1-5.3.1) Device date must be rolled back to March 31, 2018 (or earlier) to use FlashFire v0.73. Discussion of commands/techniques for rolling back the date on FireOS can be found in recent posts within this thread.