yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
App2SD is a great app. But it still dependent on rom and/or developer support for movable apps which can yield the results you experienced. Link2SD uses a different approach that is well known in the Linux world (and other desktop OSes) on which Android is loosely based. Give the free version a whirl; it has few restrictions and will demonstrate if it can 'move' apps the others can't. Downside is the physical SD card must be formatted in a specific way for the most flexible/powerful type of migration to work. Not difficult or limiting - just different. Throws a lot of people off who then deem the app a steaming pile.

BTW - I have no personal interest in App2SD, Link2SD or any other app. I understand how it works and can appreciate the potential advantages of each - not convince one way or the other. Happy tinkering. :)
[Fire Original Android Development] Dunard:
Last time I tried the Link2SD. Just a few years ago. It had linking issues back then. Lost apps and data files.

I switch to Apps2SD ever since. Plus it have a partition tool. When ever I had a problem I contact Vicky on an issue. (Tip on the formatting the sd card. Put one point more on the 1st partition. Other wise the 2nd will take one point away from the 1st one. Probably a bug that Vicky haven't fix.)
[Fire Original Android Development] DB126:
Great to hear the App2SD developer is responsive. Regarding Link2SD I have never experienced a loss but that's just one person with a handful of devices and an app portfolio that probably looks a lot different than yours. App/data loss doesn't seem to be a problem now if public reviews are accurate.
[Fire Original Android Development] huzel:
How can i get root?

Where can i find the buld-in tool?

I have the 0.15 Version installed.

thx
[Fire Original Android Development] -RioT-:
Ok, I got fresh amazon fire 5th gen with 5.1.1 installed. I did not update.

Is this the thread to start?

Do I need another thread to unlock the bootloader or can I follow the OPs instructions?
[Fire Original Android Development] DB126:
- can't unlock bootloader

- use SuperTool for rooting, blocking OTA, obtaining other tools, etc.

- use FlashFire (0.50 or above) to install (flash) custom roms, etc.

- no rollbacks below 5.1.2; soft brick with no known recovery

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485
[Fire Original Android Development] Alaxmofo:
Sorry to bother

I Am having slight issues with the rom like getting exchange services unexpectedly stopped and can't download google play games getting error -505 when it trys to install. Any idea? Other than that its a really good ROM.
[Fire Original Android Development] Alaxmofo:
Question??

What layer did you use in the picture just wondering
[Fire Original Android Development] Chinzo502:
Play store error, now this...

So I was getting an error 505 installing play games, so I figured (after deleting all cache and data on my Google apps) maybe reinstalling Gapps would be the way to go. Used flashfire to first wipe system and Dalvik, and flashed mini Gapps again, and now I'm stuck at checking connection. Any advice?
[Fire Original Android Development] DB126:
505 errors are well known on this device (and many others with custom roms) and largely unfixable. Best workaround is to sideload troubesome apps/games. As for your current situation I would be loath to stick with your current build; integrity may have been compromised by wiping system without an immediate reflash of a compatible rom along with GAaps. Restoration comes via the stock recovery menu - reload FireOS 5.1.2, root, flash SlimLP, etc. You're likely familiar with the routine ...
[Fire Original Android Development] iNETglow:
Can anyone flash it at this point? It hasn't been working for me - keeps crashing in the middle of the flash - opened a help thread for that and no1 posted success stories either.
[Fire Original Android Development] Dunard:
https://apkpure.com/apkpure/com.apkpure.aegon Download this app. Then search for the app that Google Play Store won't install because of the error. Download it and then install it from the APKPure app.
[Fire Original Android Development] DB126:
As always use caution with sites/tools of this nature. Ask yourself:

- why are they doing this?

- how are they monetizing expenses?

- where are the apps coming from?

- are you well prepared for the occasional bum load?
[Fire Original Android Development] Dunard:
The website is clean. No paid apps allow there. All apps came from Google Play Store. All apps uploaded and backup for use. Alt website. No danger at all. :)
[Fire Original Android Development] jaladhjin:
so I've got me three questions ^_^

1. Does this rom have the "legacy" floating flag mentioned here: http://xdaforums.com/xposed/modules/mod-xhfw3-floating-windows-t3371074

2. Do you recommend any hidden trigger app bars similar to the pull out style of SlimPIE controls.. the goal being to have SlimPIE on the left.. app bar on the right..

Multiwindowsidebar is close.. but I can't hide the trigger it's a clickable expandable arrow on the side at all times :(

3. Is there an easy way.. a not "Get a mod called GravityBox" way to get the screen off / lockscreen delay fixed so when I press power off.. the screen shuts off before the lockscreen comes up..

Currently I notice it comes up then the screen turns off..

All very minimal quality of life interests of mine..

Love the rom ^_^
[Fire Original Android Development] bLiTzJoN:
Well now, I had everything working with CM and Nexus so thought I would give Slim a chance. I flashed Slim-ford-5.1.1.layers.0.15-UNOFFICIAL-20160321-0835.zip successfully. Everything seems to be working on the Rom from what I can tell, BUT it's missing SuperSU, appear to have lost root and can't get into recovery. Anyone else experience the like?
[Fire Original Android Development] DB126:
Tough situation with no recovery. Assuming you can not boot twrp and did everything w/FlashFire 0.50+. Unfortunately, there is a small risk associated with every flash especially with a tool like FF compounded by the lack of an off-device recovery should something go wrong. Cycling through roms on this device is a bit like crossing railroad tracks blindfolded with ear muffs. As some point the train will be be there too.

You might be able to use the SuperSU apk to regain root access if the binaries survived the SlimLP flash. Otherwise you are probably looking at more exotic rooting methods as I don't believe Kingroot is effective against SlimLP. If the device is under warranty consider contacting Amazon for an exchange.
[Fire Original Android Development] jaladhjin:
Any of you have any neat tricks for SlimLauncher specifically to change the color of the App Drawer background to black or some sort of cool transparent and/or just the home screen looking style ?
[Fire Original Android Development] DB126:
Try Nova. Offers a fair degree of customization of the elements you mention packaged in a rock solid, low resource tool.
[Fire Original Android Development] laofan:
I am using the exact same rom and had flashed it several times before.

The rom has SuperSu built-in and is pre-rooted. The supersu settings is in settings, right above "about tablet ".

If your rom is not rooted, you might have a bad download or something might go wrong during the installation. Try use Kingroot to root it and then flashfire it.

Recovery has nothing to do with the rom. If your fire version is higher than 5.0.1, you can't get into recovery.
[Fire Original Android Development] bLiTzJoN:
I flashed several roms since I got the tablet a week ago; Slim killed it for me. Can't use Kingroot, SuperSU wants to update binary and can't, FF can't obtain root access (nor do I get a prompt from SuperSU), and I can't perform a factory reset through the Slim settings. It hangs on the Amazon logo when I attempt to enter recovery through soft booting via menu and hard booting with buttons. I'm having Amazon replace it. Arrives today.
[Fire Original Android Development] DB126:
Not true. Amazon's stock recovery should remain accessible provided is wasn't trashed during the prior rom flash attempt. The presence of *stock* recovery is significant as it allows FireOS to be reloaded (with important caveats) which effectively restores a borked device.

[MENTION=4314948]laofan[/MENTION] is correct that a *custom* recovery can not be invoked if the bootloader is higher than 5.0.1.
[Fire Original Android Development] laofan:
Yup. We are on the same page. Your description is easier to understand and more accurate.

(Not that it is important, but when I said recovery has nothing to do with the rom, I mean flashing this slimLP rom would not remove recovery.)

The slimLP has not been updated since March. But man, I love it so much! Almost everything is working perfectly. I did try out the July Cm 12.1. The broken brightness control kill it for me.

What is your favorite rom, Davey?
[Fire Original Android Development] DB126:
Different preferences on different devices. While I try out roms regularly my daily drivers tend to be trailing edge stalwarts that have withstood the test of time. My daily driver is a KitKat Nexus variant augmented with Xposed. On this device (secondary) CM 12.1 gets the job done with minimal tweaking.
[Fire Original Android Development] jaladhjin:
I noticed an odd issue with my Gmail while using this rom

My compose section & reply section is dark themed.. making it very hard to read the words :-/

I was going to put up a screenshot & still can.. I just forgot to enable autobackup to Photos on the tablet so I haven't got it accessible at the moment since I wanted to obfuscate my email :D

Strange.. the rest of the Gmail.. using the official Gmail app is white & looks like it always has.. can read emails on my normal white background..

:(
[Fire Original Android Development] csolanol:
Remove gmail stuff from /system/vendor/overlay
[Fire Original Android Development] jaladhjin:
There doesn't seem to be anything relevant in there

Just some notifications

Nuke those?

I haven't installed anything else via layers either
[Fire Original Android Development] n3roxda333:
Hey folks,

i have just downgraded to 4.5.3. rooted and installed twrp 2.8.6

when iam trying to start twrp 2.8.7 with adb shell only the old version is booting.

now i have tried to install the zip with twrp 2.8.6 and get the following error:

E:Error executing updater binary in zip 'sdcard....'

whats wrong?

regards
[Fire Original Android Development] jaladhjin:
[ROM] SlimLP 5.1.1 for Amazon Fire 2015 (Ford)

Here's what it looks like bee tea dubs
[Fire Original Android Development] DB126:
Appears you have posted in the wrong forum; this thread is for 2015 5th gen 7" Fire.
[Fire Original Android Development] n3roxda333:
Damn.. Sorry!
[Fire Original Android Development] danielyoung200:
Can't get my Micro SD card to mount. Tried an 8GB SanDisk and a 16GB Kingston Micro SD cards and neither work, while working in my laptop perfectly.

EDIT: Inserted SD card using my finger, instead of a piece of plastic and it randomly started working. While inserting the card, I noticed some weird behaviour where the card would continuously remount and disconnect. I have formatted the card now, and everything should be fine :) This is an amazing ROM, thank you.
[Fire Original Android Development] jaladhjin:
Any suggestions on how I can get immersive mode to enable immediately ?

Or I guess technically more permanently..

With it enabled via GravityBox when I unlock the screen I see the status bar for a few seconds then it goes away..

I'd like it gone permanently unless I swipe down from the top to reveal it..

---------- Post added at 03:58 AM ---------- Previous post was at 03:57 AM ----------

Funny you mention that when I put an SD in I had problems getting it to stay in too.. thought it was just my lack of a fingernail..

So I used the back of another SD to push it in apparently the entire way.. didn't detect properly so formatted.. haven't had an issue since either :D
[Fire Original Android Development] jaladhjin:
I decided to give the Fire Nexus rom a try too to see how it feels :D

But uhh.. I was wonderin'.. this rom has the AOSP keyboard with symbols on all the keys for long press doesn't it ? I don't remember :-/

If it does.. could I get that to replace my current apk that doesn't ?

I looked in the zip for an apk but it's a whooole lot of .sh & that boot.img
[Fire Original Android Development] Chewieez:
I've just noticed that when I switch to a different user, I cannot get Bluetooth to turn on. It just stays stuck saying "turning on". When I switch back to my primary user account Bluetooth works fine. Has anyone else had this issue?
[Fire Original Android Development] niftypixelz:
Hey all,

I updated to the newest ver of Slim Ford last night (wiping cache/dalvick/3rdparty) via FlashFire. Everything went smoothly. Now when I boot up though I get to the 'welcome' screen where I select my WiFi AP, give it the password, then it stays stuck on the 'verifying connection' screen. I've tried 3 different WiFi AP's all with good connection, I've reboot it a dozen times. I'm stuck, and the 'skip' button on the bottom right is grayed out. Is there any way to bypass this screen? any way to load a diff Rom via FastBoot (seems to be the only thing I can get in to). I cannot get in to CWM/TWRP after it loads them via fastboot the device just sits saying xfer OK (I'm guessing I'm on the higher ver where custom recovery isn't supported).

ANY assistance would be appreciated. As it stands I have a non-functional tablet :-/ I don't understand why it can't get past checking connection, the connection is fine and I've verified its speed on an another Fire tablet just like it (which I've not upgraded to newest Slim yet).

Thank you!

-----------------------------------

Update: I've FINALLY GOT IT! After rebooting back in to recovery via adb and clearing cache, on maybe the 3rd try it finally let me skip the initial setup after connecting to an AP without inet connectivity. Yay!

-----------------------------------

Update: I've tried booting back in to recovery via adb and clearing cache etc, the ROM boots back up np, does the 'optimizing app' stuff then unfort I'm back to square one.

-----------------------------------

Update: I've also tried *#TESTMODE on dialer, this does not help or show the home buttons etc.

-----------------------------------

Update: I've also tried the trick mentioned in other threads to connect to a router that does NOT have internet connection. This just says 'Couldn't connect to the internet' and forces me to go back to the WiFi AP selection screen, never allowing me to hit skip or move forward :-/

[IMG="Connecting to a router that has no internet."]http://i.imgur.com/yN9XBHN.png[/IMG]
[Fire Original Android Development] atsiz77:
[ROM] SlimLP 5.1.1 for Amazon Fire 2015 (Ford)

Where i can find, the DHCP Option in this OS?
[Fire Original Android Development] Xx_xBLADEx_xX:
Bootloop after flash with [Flash Fire]

I've tried flashing this ROM twice with no luck. Bootloops at the Amazon logo every time. Downgraded from 5.1.4 to 5.1.2, rooted and flashed with Flash Fire, moved wipe to the top. Instructions are unclear, it states wipe everything but that makes no sense if I need the ROM stored internally. I've selected only defaulted option "System data, 3rd party apps and Dalvik cache", first time with GAPPS, the second time without. What am I missing?
[Fire Original Android Development] DB126:
Q) "What am I missing?"

A) Wipe system partition like the instructions state.

Wipe actions can be repositioned in FlashFire. Tee up a full system wipe (system, data, dalvik, cache) along with whatever you want to flash. Just prior to execution long press the wipe action and drag to top of operations sequence. Then hit Flash.
[Fire Original Android Development] UndyingShadow:
I double checked that the wipe action had been re-positioned to before the ROM install. I also double checked that the wipe action was set to wipe system, data, dalvik, and cache. It still causes a boot loop that can only resolved via amazon recovery. Something is wrong.
[Fire Original Android Development] DB126:
Probably something the rom developer/maintainer will have to address. Not sure how active he/she is. You might want to go with one of the more popular roms for this device - currently CM 12.1 or Fire Nexus.
[Fire Original Android Development] B2Pi:
Just to sum what others have said....

I spent much of the day trying to install this, before I came across the thread portion that discussed the soft requirement that ROM files are on internal storage, not an SD card.

Nice little tablet. SlimLP is way behind the times, thought... I'll probably try out the Nexus ROM.
[Fire Original Android Development] DB126:
At present CM and Nexus receive the most love with monthly security updates and fixes as needed. Recognize the bootloader/kernel remain locked on this pup; not going to see Android 6/7 roms anytime soon. That said, toss Nova, Xposed, Greenify and a few other key modules at Nexus and you have a sweet little device that looks/performs a lot like Marshmallow.
[Fire Original Android Development] caymera:
Hi guys i followed Rootjunky to flash this rom (my first rom) But it just wiped my data and when the zip is prepared to be flashed it just skips and boots to Fire OS with all my data wiped I think i still have Root but superSu is gone and flashfire as well

Thanks.
[Fire Original Android Development] sd_shadow:
you likely missed a step, or rom.zip was an incomplete download
[Fire Original Android Development] NightCrayon:
Rom runs great for the most part, but cant get a good working slim gapps zip. Ive tried using Dankomans Slim mini and Slim Zero gapps, they install fine but always return a code 505 error when trying to update. This is very frustrating as i really like this rom, i just really need gapps to be working correctly. Any suggestions? Does open Gapps work with slim rom? Thanks for any help :)
[Fire Original Android Development] DB126:
I believe Open GAaps works fine with this rom. Suggest starting with nano due to limited space in system partition. Individual Google properties can then be added from the Play Store as needed. Can go up to Mini (Stock won't fit) but that leaves little working space for future updates. Or you can roll your own with a config file.

For the initial load recommend reflashing Slim along with a suitable GAaps package. Layering on GAaps after the ROM has initialized can be problematic. Also leave all FlashFire settings/options at there default settings. Lots of older guidance suggest enabling/disabling this and that which was relevant at the time. Now just leads to problems. Good luck!
[Fire Original Android Development] NightCrayon:
I tried to use Open Gapps and it didnt work for SlimLP, so I installed CM12.1 with Open Gapps, I am getting the same problems with CM12.1, So i said lets try another rom, I installed Resurrection Remix, same problem, so i tried tkgapps same thing. why is it 505ing with every gapps package and rom that i Use? is there something im doing wrong? Perhaps the newer builds on open gapps have probelms? Should i try an older build? I am using flashfire 0.53

Here is what i do when flashing list order first to last:

1. Wipe: System Data, 3rd Party apps, Dalvik, Internal storage, Cache Partition

2. Install Rom.xxx.zip (default ff settings)

3. install SuperSU (default settings)(if necessary)

4. Install Gapps package (Default ff settings)

everything goes through smoothly, i get to a good running environment. Then, once I add my google account and open the store, it attempts to check for updates. Updates are usually available for google webview etc, they all fail with a 505. Tried, removing account then signing back in, changing time, clearing cache stopping processes, nothing seems to solve the issue.
[Fire Original Android Development] BobBaltzer:
Which version do you use? I have used CM 12.1 and Gapps, micro. No problems - ever.
[Fire Original Android Development] NightCrayon:
unfortunately open gapps doesn't work with slimLP. after giving up on the current slim gapps build i just force installed every apk that i needed updated through adb. For now it seems to have resolved all of my issues. I'm loving this rom, will update if anything changes.
[Fire Original Android Development] mikejs1:
Need a solution

So I flashed this using Flashfire, did it the proper way, wiped everything and moved wipe to the top of the queue. it successfully flashed the rom, but now there's no root access in the developer settings, and i can't install google play services without it crashing every second. it doesn't boot into recovery either, no matter what. if i try to go to recovery using the buttons, it sits at the Amazon boot logo, if i do it using adb, it goes into fastboot. i tried flashing the stock rom using fastboot commands but it says flashing isn't allowed, so i can't do that. i tried kingroot again, and it doesn't work. kingoroot reboots the device when it gets to 90% in the root procedure. so my device is stuck on a rom that i can do nothing on. i can't get root access to use flashfire, and it doesn't have a recovery to boot to.
[Fire Original Android Development] DB126:
Yikes - haven't encountered a post-flash borked stock recovery in some time. What version of FlashFire did you use? I assume SuperSU (zip) was not included in the flash package as that should have taken. Do you recall what version of FireOS was last on the device?
[Fire Original Android Development] mikejs1:
5.13 was the original, then i downgraded to 5.12 so i could root it using the supertool. when i flashed slimlp i used flashfire 0.53. SuperSu is in the settings, but needs the binary to be updated.
[Fire Original Android Development] DB126:
Seems you did everything right. Don't have any immediate suggestions other than an exchange if the device is still under warranty. Very concerning stock recovery got slammed. Thought we were through that with newer builds of FlashFire and ROMs. Possible (albeit unlikely) SlimLP image has the same problem as early CM builds for this device that sometimes yielded the same results. Last I looked SlimLP hadn't been updated in a while.
[Fire Original Android Development] mikejs1:
got it replaced, won't be making the same mistake twice
[Fire Original Android Development] mbholm:
Supertool used to have an old version...
[Fire Original Android Development] DB126:
Curious - what mistake? Have you identified the culprit or just taking a different path.
[Fire Original Android Development] mikejs1:
Just going to avoid flashing this specific rom or anything i'm unfamiliar with. i just don't like the layout of the stock Fire OS or the lack of google play services