yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] riverstyxxx:
Twrp fails to fastboot on this one, cant install:

fastboot boot twrp.img

downloading 'boot.img'...

booting...

FAILED (remote: unknown command)

finished. total time: 0.281s

c:\adb>fastboot reboot

rebooting...

finished.
[Fire Original Android Development] sd_shadow:
twrp only works with 5.0.X bootloader
[Fire Original Android Development] riverstyxxx:
My mistake, I overlooked it. Since im on a custom rom, can I downgrade to 5.0.X with adb sideload, or is there another way to install, or am I hosed? Thanks for all the development work you've done.
[Fire Original Android Development] DB126:
Can't downgrade; guaranteed brick. Use FlashFire to install.
[Fire Original Android Development] riverstyxxx:
Thanks for the quick reply, I was hesistant to even attempt. Is there a guide? I know there are specific options to have enabled/disabled. I tried installing cyanogen and it didnt work via flashfire, i followed the options exactly as written.

Edit: Speaking of downgrades. I have a custom 5.1.1 rom, does this mean I can revert to stock 5.1.1 (should it come to that), even though at one point I had 5.1.2?
[Fire Original Android Development] DB126:
Use the CM guide. There is a known issue between CM and FlashFire that sometimes leads to failures. Make sure 'wipe' precedes the flash operation. Should not have to twiddle any other options.

Any rollback is a risk. 5.1.1 -> 5.0.1 yielded bricks. Don't have a lot of data points on 5.1.2 -> 5.1.1 attempts. I would be hesitant.
[Fire Original Android Development] sd_shadow:
no, it's the bootloader that matters, custom rom doesn't change that
[Fire Original Android Development] riverstyxxx:
Alright, thanks. Somebody mentioned using flashfire to install, but there's no guide with specific settings.
[Fire Original Android Development] sd_shadow:
there is a Thread

How to Use FlashFire App to install a Rom
[Fire Original Android Development] pfoneguy1:
So these updates have been incorporated into .15 ? Can you just flash over the current ROM using flashify?

I think I am just going back to stock, too much to concern yourself with when you don't have a custom recovery. :(

I picked up a $50 FP refurbed LG G Pad and feel it is much nicer than this Fire, the $10 difference was not worth it..... certainly not at the current $50.
[Fire Original Android Development] andream8891:
I don't have understand, is possible do something with FireOS 5.1.2? in same place i have read is possible install a CustomRom and in other in not possible, what is the truth?
[Fire Original Android Development] sd_shadow:
yes you can install custom roms, yes it may be bricked
[Fire Original Android Development] andream8891:
With FlashFire right? if i want wait for install a custom rom just for now is always possible remove the ads and change the launcher in FireOS 5.1.2? or also this is not possible? :/ Sorry if is off Topic :):)
[Fire Original Android Development] sd_shadow:
yes

yes, you can see super tool thread or

one of the other ones listed in the index

[Index]Amazon Fire 7" - 5th Gen-2015

yes it is, a little bit
[Fire Original Android Development] TonyFFH:
Great Job! A couple of minor issues

Great job on such an efficient, fast, rom for the Fire 2015 (Ford). Installed without any problem per your instructions. Everything works as expected except for two minor issues:

1. Launcher issues: It will not allow Google Now to be implemented. It "installs" but doesn't get into the Home settings list of launchers, so it can't be used. The Slim Launcher doesn't show any Apps that have been moved to the SD Card. You can place the shortcuts from the All Apps list, but they disappear on reboot. I fixed this by installing the Hola Launcher app which installed and works fine.

2. When first installed, I kept getting the "Unfortunately, Exchange Services has stopped" message, so I used my All-In-One Toolbox's System App Uninstall tool and found that there were 2 Exchange Services apps installed. One was a 5.1.1 version and one was a 6 version. I uninstalled the 6 version and have not seen the error message since then.

Thanks again for an awesome rom!

----------------------------------
[Fire Original Android Development] Chewieez:
Is there a way to move the navigation buttons from the bottom to the side when in landscape mode? I see there is a setting to move it to the bottom but it doesn't have a setting to move to the side. I'm on firmware 5.0.1 and Slim .15 (20160321).

Also I noticed that the setting for having the volume keys layout change with the tablet orientation is backwards. With it set to change the volume keys, the do not change, and when the setting is off, they to change with an orientation change.
[Fire Original Android Development] GambitK:
Hello, I've just installed your Rom and is very good and fast. I do have an issue with a game "Subway surfers", the sound doesn't start for about 15 seconds and then goes crazy, I've rebooted a couple of times and the issue persists.
[Fire Original Android Development] csolanol:
Yup that's an issue with some games. No fix for now. I have tested it several times and with the same game, sometimes sound is ok and sometimes ugly...
[Fire Original Android Development] DB126:
Happens with all custom ROMs for this device; no joy switching. Mostly with games; music/video streams fine. Seems FireOS does some custom handling of game audio that the ROM devs have yet to unravel.
[Fire Original Android Development] Chyron8472:
Was going to flash this and FlashFire complained about partition changes (my removing system files) that could bring a block level flash to cause a brick. Can I / How do I fix this issue without having to reroot?
[Fire Original Android Development] DB126:
The OTA warning is irrelevant flashing a custom ROM. Nothing to fix, proceed with flash. Choose a custom ROM carefully as switching to another occasionally involves reloading FireOS as an intermediary step.
[Fire Original Android Development] Tricksodave:
Can anyone help, I'm stuck on bootscreen with the latest build. Unable to get into recovery, totally at a loss here.
[Fire Original Android Development] sd_shadow:
stock system version that was on it?

steps you took to flash?
[Fire Original Android Development] Tricksodave:
I was on a nexus 5.1.1 build from when it first came out. The wee man had the tablet full and wasn't working right. So I download the latest version of this factory reset, then I installed this version via flashfire. Didn't boot up after it was finished. I will not boot to recovery
[Fire Original Android Development] sd_shadow:
yes, but it was stock at one point

what bootloader version then?
[Fire Original Android Development] Chyron8472:
[snip] Okay, I see.
[Fire Original Android Development] Gintoki01:
All good, but the rom is in boot animation about a 1 hour ago, this is normal? what can i do?
[Fire Original Android Development] sd_shadow:
if it doesn't boot in 10 mins, it likely did not install correctly
[Fire Original Android Development] BlockOfDynamite:
So I successfully installed this ROM and everything on my 2015 Kindle Fire 5th gen, but it gets stuck at "Checking connection..."

Got any ideas? I've tried wiping the cache partition in the stock recovery.

Edit: I installed Nexus Rom and it worked just fine.
[Fire Original Android Development] lumpylouis:
Need Help Please

I attempted to install SlimLP onto my 5.1.2 device unwittingly. The install froze almost immediately after hitting "flash". I left it for about 10 minutes and then rebooted. It then stuck at the boot animation for 20 mins or so. I am able to boot to the stock recovery. Performing a factory reset didn't get me past the boot animation either, derp
[Fire Original Android Development] DB126:
You will need to reload FireOS 5.1.2 (no other) via ADB sideload from the stock recovery menu. Procedure is detailed in the help thread.
[Fire Original Android Development] csolanol:
Op and changelog updated with new build 2.1.

Enjoy.
[Fire Original Android Development] parkerlreed:
Heh it updated and the crash went away. Woo.
[Fire Original Android Development] parkerlreed:
I don't see any mentions of this. A soft reboot seems to mess up the SD card mounting. It'll be working fine, I soft reboot (for example in Layers Manager), and when it comes back up I won't has access to anythong on the card. Going into Settings > Storage shows it as unmounted. Reinserting the card/a full reboot seems to be the only way to get it to come back.
[Fire Original Android Development] csolanol:
Soft reboot never has been working well with the ROM and external storage. That's why it isn't included in reboot menu. More when we can't control the boot process with locked bootloader. Sorry for the inconvenient.
[Fire Original Android Development] Joshmccullough:
Flashed the update a few minutes ago, Bluetooth works like a charm! Can't believe this cheap little tablet has been turned into such a great sidekick to my N5 :)
[Fire Original Android Development] parkerlreed:
Same here. Been using it slightly more than the 5X for Reddit and videos. Also runs Dead Trigger really well.
[Fire Original Android Development] Confused_Cheese:
Thanks for your work on this :) Was like a breath of fresh air seeing the normal android setup wizard after boot!
[Fire Original Android Development] t3chwizard:
Update is awesome. Like being able to use a USB drive on the tablet.
[Fire Original Android Development] Joshmccullough:
I bought one for me, one for my wife to see if she could use it as a viable alternative to the Chromebook for recipes/kitchen stuff. Even if it doesn't work out for that, I'm sure she'll ask me to put SlimROM on it to make it more user-friendly than the stock Amazon UI, which is kinda hot garbage, IMO. I think if it's more like her Nexus 5 than the Fire OS interface, she'll be more apt to pick it up (for being a web designer, she hates tech, go figure.)

Heck, for the $35 I bought it for, I told her she could use it as a Frisbee for all I care.
[Fire Original Android Development] t3chwizard:
[MENTION=2511007]csolanol[/MENTION] My friend recently clean flashed this ROM on his Amazon Fire, and while he attempted to play Subway Surfer on it, he experienced a weird sound stuttering issue, that eventually went away after a few reboots and some trial and error, but I managed to get a logcat for this, and it is available at the following link. https://paste.ee/p/1nzTd

(pastebin would not allow me to paste it because it was over the file size limit, so I posted it somewhere else.)

EDIT: I experienced this error once on my tablet a few minutes ago as well. It went away after closing the app and opening it again, and the sound was back to normal after that.
[Fire Original Android Development] sageDieu:
I cannot get the recovery working on my new Fire tablet (got it from the black friday sale) as fastboot keeps giving an "unknown command" error:

https://i.imgur.com/GnYPHpm.png

Has anyone else seen this problem? Everything on google searches is for other people randomly having the issue due to various reasons, none of which are relevant here.
[Fire Original Android Development] csolanol:
Oh oh looks like amazon patched the bootloader. Please look at fire os version.

I assume you can download factory 5.0.1 bin and downgrade it but didn't try it.
[Fire Original Android Development] 87racer:
Yep, its at 5.1.1 now. have two of these that i just picked up so I will try the downgrade real quick.
[Fire Original Android Development] csolanol:
Looks like downgrade isn't allowed: http://xdaforums.com/amazon-fire/general/fireos-5-1-1-attempted-downgrade-t3263960
[Fire Original Android Development] BigMosley:
My tablet is from the black Friday deal and have no problems, running version 2.1 perfectly.
[Fire Original Android Development] csolanol:
Well problem appears when the tablet connects to a WiFi network when boots for the first time. It will download the ota and upgrade...
[Fire Original Android Development] BigMosley:
Is it possible to not accept the Ota when first booting? Then turn off future updates when the system starts up?
[Fire Original Android Development] cbolumar:
My tablet has only one week ( 2 days before black friday) . It's 5.01 and installed your 2.1 ROM without problems. I used the device with original software only 1 day , maybe because that never ask me to upgrade to 5.1.1.
[Fire Original Android Development] csolanol:
I don't know, if i remember ok when i got the tablet and powered it on for the first time and connected to a wifi ap it started to download the ota in background. On next restart it applied the ota and didn't see nothing asking for it. It updates in the boot proccess.
[Fire Original Android Development] mbholm:
Is installing slim rom on firmware 5.1.2 not a supported action? Was planning to install slim on new devices just received.
[Fire Original Android Development] lumpylouis:
Correct. SlimLP can only be installed with rooted 5.1.1 firmware. It bricked my device but I was able to recover thanks to Davey's advice. I just read that some people have confirmed that Nexus ROM installs on 5.1.2 via flashfire without issue. Ill be trying that this week.
[Fire Original Android Development] DB126:
Nexus and CM work great on this device, receive regular updates and install without issue using the latest versions of both ROM and FlashFire (0.32+). Nexus is an easy install as GAaps (nano) and SuperSU are baked in. CM has a more robust out-of-the-box feature set while Nexus serves as an excellent platform for customization. Can't go wrong with either.
[Fire Original Android Development] mbholm:
I was hoping to look into a specific difference I had seen between SlimROM and CM...to see if it could be possible on CM. I rolled my boys out on CM so far. They are setup in restricted profiles (I don't want them being able to add new users). In SlimROM, I was able to customize which widgets appear in the top drop down settings drawer, even when in a restricted profile. With CM, I can only customize that area from a normal user profile.

So, thus the reason I wanted to put SlimROM on my extra rooted 5.1.2 fire7. Sounds like this is a problem. . .I thought, as long as you are rooted, the custom rom shouldn't be a problem.
[Fire Original Android Development] DB126:
I'm not familiar with all the intracies of restricted profiles but sense widget vagaries are more closely aligned with the active launcher than the underlying rom.
[Fire Original Android Development] mbholm:
Hm. . .k. How do I identify which launcher is active across each ROM by default?
[Fire Original Android Development] Dr.TheMaster:
Try different g apps and I think it should work just fine :)
[Fire Original Android Development] trulyparis1:
I had 5.1.3 on replacement device sent to me last week and after downgrading to 5.1.2 could only flash nexus ROM and CM12 successfully...all others failed. Took hours to work it out tho
[Fire Original Android Development] DB126:
CM has its own a custom launcher (Trebuchet). Not sure what SlimLP uses. You'll need to do some homework or install a well regarded 3rd party launcher like Nova that offers rich widget support.
[Fire Original Android Development] monkish34:
I got CM 12 flashed on my 5.1.1, but when I go to flash slim flashfire gives me a warning window with either a Cancel or Ignore option. Anyone know why that would be?

I brought the wipes up top before trying to flash.

The error is:

"it's been detected you're trying to flash a block level ota but your system/vender/or own partition has been modified. The flash will likely fail. "

And there's a Cancel or Ignore option.

What do you guys think? I got CM 12 on my 5th gen ok, and CM seems great, but I've read slimrom is all around slimmer and faster so I'd really like to give it a try.

Oh, when I first tried this it was with the version of flashfire in rootjunky's slimrom YouTube video. Version .24 I believe. I didn't get that error with that version of flashfire but when I flashed I got sent into a bootloop.

So flashfire .32 is what's giving me that error. I saw version .4 is out now.

Anyways, in flashfire which options should I choose when I select the rom and gaaps? Should I select automount on both? And unlike version .24, version .32 has more options than automount. So it might be this part that's giving me problems.

Any help would be greatly appreciated. Thanks
[Fire Original Android Development] sd_shadow:
ignore the warning
[Fire Original Android Development] monkish34:
Ok I'll give it a try. Thanks for the response.

I don't have to do anything with CM 12 right? I can just install right over it? Or actually the wipes should do that for me...
[Fire Original Android Development] cigero:
5.1.2 installation fails

hi to all,

i'm trying to install this rom on my fire (with fireOs 5.1.2) but everytime i try (every combination, e.g. flashfire 0.24 or 0.32, first wipe and then rom + gapps, etc) it fails; sometimes it remains black and sometimes it stuck on flashfire "terminal" during flashing, but everytime when i restart, it freezes on boot (and became hot).

Can someone help me? I don't know very well how to use flashfire, maybe wrong use.
[Fire Original Android Development] DB126:
Thoughts:

- FlashFire 0.32 is good

- Reboot before launching FlashFire (needs copious memory)

- Wipe as first action; tick system, user apps, dalvik (cache optional)

- Only flash SlimLP rom on first pass; GAaps can be installed later

- accept default options; no need to fiddle with auto-mounts, etc

If still no joy try flashing Nexus as it is a one file affair that goes in easy. Will test ability of FlashFire to work with a different rom.
[Fire Original Android Development] cigero:
Thanks man, it worked :good:

Now for installing gapps i must use again flashfire in slimLP ?
[Fire Original Android Development] DB126:
Correct. No wipes; just flash GAaps package using default FlashFire options. Strongly suggest Nano or smaller package to insure adequate space in System partition for future updates. Individual Google properties (apps) can then be added from the Play store.

You may hear some voices suggesting further optimization of GAapp components installed to the system partition. You can certainly do that to regain some space in the user partition (perhaps 500 MB). Approach suggested above is simpler if you are not into tinkering.
[Fire Original Android Development] hinciarte:
I realize this is probably a dumb question, but I'm trying to figure out how to set up a restricted user account correctly. Whenever I set one up, I just get a black screen when I switch to that user. I can access the "settings" from the top pull down screen, but I can't see anything. It's literally a black screen! Any help would be greatly appreciated...

Never mind: I had forgotten to enable the launcher!
[Fire Original Android Development] relaxable:
What stays after wiping?

New Fire Tablet 7, had few days and it got OTA update to 5.1.2.1.

Sideloaded 5.1.2, got root with Kingroot

Flashed Nexus rom - everything look ok and used for a bit (includes Playstore)

Then Flashed Slim (no gapps) - everything looked ok - i believe it let me set device for Google account, but no play store.

This may be where I went wrong, because before attempting flash of a slim-gapps package, I thought I would just install PlayStore by manually doing adb of the files that Supertool does, except for app 2/ the googlelogin service since I already had google account....

Play Store did install, but Play Services kept crashing, and PlayStore opened and errored with no communication...

Tried various installs of zero and mini Slim Gapps, but attempt to add a Google account resulted in inability to communicate/couldn't add, and then later, flashing the gapps didn't do a thing.

Re-flashed Nexus rom and everything pretty normal - google account fine. Play store fine.

Wiped system/data, apps, caches, AND completely wipe internal option, and flashed back Slim. No Google Account. Flash Slim Gapps. No google account or any of the gapps.

Same problem. Until finally, decided to do the gapps WITH the mount system read/write option checked. And that seemed to do the trick.

(Now, would like to get Slim set to SELinux Enforcing..)

But, I am left wondering: with a wipe it seems that there is system-related stuff that doesn't get wiped, and I'm wondering if Kingroot has been able to leave some trace of something in the system that I really don't want on my system. Since we know it uses a security exploit over an internet connection to do its magic, and since it appears to be ever-changing (Supertool had errors after root obtained in the steps it took to remove Kingroot), I wonder if the tablet has been [semi]-permanently compromised....

1 more thing: I notice some seemingly irrelevant things run on the tablet (developer options/process stats with system checked):

Mobile Network Configuration (com.android.phone) - there is no 'phone'?!

com.android.smspush - no phone/no sms?

Phone (com.android.server.telecom) -

And the DisableService app by WangQi showing a number of services running that seem irrelevant relating to phone functions - including SIP & stuff

I was able to enable SIP and make calls (while still on FireOS) using CSipSimple or Sipdroid (forget which one - one worked, the other didn't) - but maybe would be possible to get native SIP to work if somehow got a dialer app running with all this other stuff?

I guess I'm going to keep trying things and hope I don't brick this tablet...!<:cool:)
[Fire Original Android Development] radekmazur:
I like this ROM. Please continue development. Thanks.
[Fire Original Android Development] laofan:
The rom is pretty much well cooked for this device. For me I am very satisfied with what it offer on such limited hardware.

We should hope that one day we could get something similar to safetrap for the 5th gen fire so we have the chance to install Android M or even Android N.
[Fire Original Android Development] DB126:
Kernel compatibility is still required with Safestrap; only Lollipop based roms unless a bootloader vulnerability is identified/exploited or Amazon releases an Android 6+ build of FireOS for this device.
[Fire Original Android Development] guardianknox:
How to use the screen recorder

There is an option under settings - interface - screen recorder, but how do I actually use it? I've searched and can't find anything on the slimrom homepage or faqs.
[Fire Original Android Development] Chillmann:
It should be possible to ad a shortcut to power menu or quick settings
[Fire Original Android Development] guardianknox:
That's what I expected, and for days I've been searching for something dumb right under my nose.

I tried by holding the screen and trying the "slim actions" and "slim shortcuts" widgets, quite a long and repetative list, but only screenshot seems to fit, but of course only give me a screenshot.

I am misunderstanding this? Is there a built-in screen recorder, ala CM11 up+power?

Or does this refer to some other 3rd party app, api, chrome/mirror/screen/cast etc?

p.s. Trying with two Amazon Fire 2015's, one 5.0.1 with SlimLP .14 via TWRP, one 5.1, with SlimLP via FlashFire
[Fire Original Android Development] csolanol:
Screen Record needs to be added to the global menu, where reboot and power off options are. You need to show the global menu and select screen record to use it.
[Fire Original Android Development] guardianknox:
Thanks!
[Fire Original Android Development] K5LK:
Agreed. Love it!
[Fire Original Android Development] Dunard:
Some of the apps can't be move onto the sdcard. I think it a bug.

https://apkpure.com/final-fantasy-brave-exvius/com.square_enix.android_googleplay.FFBEWW and https://apkpure.com/final-fantasy-record-keeper/com.dena.west.FFRK for example.
[Fire Original Android Development] DB126:
Try Link2SD or a similar app that utilizes symbolic links. Works a treat.
[Fire Original Android Development] Dunard:
I know. I use the Apps2SD Pro. :)