yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] GJCarpenter:
Stuck after Unofficial SlimLP flash - Amazon Fire 5th Gen

Hello XDA Dev. Team –

Any help with the below issue would be extremely appreciated. That being said, I will no matter what be reading every post related so I can to fully educate myself for the future, which is what I should have done in the first place. I’m angry at myself for doing these things without fully understanding how it all works.

•	I recently purchased an Amazon Fire 7” 5th generation Tablet (16GB). HERE

•	I used RootJunky’s supertool to downgrade to version 5.1.2 from 5.1.4

•	I then used RootJunky’s supertool to root the device, install Google apps, remove ads -

•	I then used RootJunky’s supertool to replace the fire launcher with nova launcher. - HERE

•	Everything worked great, but I noticed I couldn’t use widgets, so I decided to try a ROM.

•	So I then followed the instructions in flashing the Nexus Rom here - > HERE

•	Everything was great at this point except for two issues - I would get Netflix errors when trying to play videos, and I kept getting the annoying the unfortunately Google play services is not responding messages.

•	So I thought I would try flashing a new ROM. This is where it all went bad…

•	I downloaded the Unofficial SlimLP 0.15 (20160321) by clicking on the link in this thread. HERE

•	I flashed the ROM with flashfire.

•	Installed fine, however somehow I lost root access, and SupeSu and flashfire disappeared. So now I’m stuck.…

•	I can’t download anything as I can’t get Google Play. I also can’t get into recovery as when I try it just freezes at the Amazon screen.

•	I can get into fastboot, and I can get into SlimLP, but that’s it.

•	Note I tried installing Gapps through rootjunky’s supertool, and they installed, but apparently aren’t compatible as google play won’t open. I just get an error.​

Any help would be extremely appreciated….Thanks for your time.

Current SlimLP About Tablet screenshot attached.
[Fire Original Android Development] GJCarpenter:
Same issue here. Will Amazon replace even though it's loading a Rom? I just bought the thing.
[Fire Original Android Development] DB126:
- system partition should have been wiped (didn't see reference to that step)

- SuperSU must be flashed with this ROM retain root access

- need access to stock recovery to reload FireOS; crippled fastboot is useless

- Amazon will typically accept returns/exchanges of rooted/hacked devices if within applicable windows (obviously use discretion on volunteering info)

Even if all steps were performed correctly loss of access to stock recovery is both unacceptable and irresponsible if ROM build is at fault. This problem (borked recovery) plagued early builds of CM 12.1 but was subsequently fixed by developer. Disappointing to learn it remains a 'feature' of this otherwise great rom.
[Fire Original Android Development] NightCrayon:
SuperSU is included with the ROM, no need to flash it.
[Fire Original Android Development] DB126:
That may be true but it obviously didn't take for the individual reporting issues and several others in the past. Not a big deal with a bootable custom recovery (simply reflash SuperSU to score root) but forces a compete redo on this device - assuming stock recovery remains accessible. As the poster also lost access to stock recovery there is no path to root, recovery or updating the rom at this time.

Until the ROM dev/maintainer investigates further I would be hesitant flashing/updating SlimLP on devices with FireOS (bootloader) >5.0.x. Using TWRP should reduce/eliminate the chance if loosing access to stock recovery.

Those wishing to proceed with the current build of SlimLP on newer devices should consider including SuperSU in FlashFire operations sequence.
[Fire Original Android Development] NightCrayon:
The problem is that this version of slimlp comes with an older version of SuperSU. Once the ROM is installed with Google play services it tries to update SuperSU, a binary update warning comes up, just continue without binary update anyway, it should update just fine. It did for me anyway... I guess flashing SuperSU with the ROM would prevent the issue in the first place but it does not solve the problem because they are still stuck with no root on their current build.

Just ignore the binary update and continue installing SuperSU, it should work.

If Google play services are failing you will need to manually install/update through adb

Use "adb install -r filename.apk" (obviously replace filename.apk with the actual name of the apk) to reinstall your Google play services. Use apk mirror to find the Google apks you need. Use the no dpi or 160dpi apk versions.

Sorry i can't get into more detail at the moment as I'm rushing off to work right now, but let me know if you need more help, I'll check back later.
[Fire Original Android Development] DB126:
This would be a nice outcome if it works. I have my doubts given the symptoms reported; hope I am wrong!

[MENTION=7907731]GJCarpenter[/MENTION] - you can grab SuperSU from here if the Play Store is not working. Any version will work; suggest 2.76 for reasons that are beyond the scope of this discussion.
[Fire Original Android Development] CptKlink:
I can not install this rom for the life of me. I did everything with the super tool and wiped and installed useing flash fire and when it completes and restarts i'm right back to completely stock fire os 5.1.2 no root no nova launcher no nothing. I don't get what i'm doing wrong. Anybody have any ideas?
[Fire Original Android Development] DB126:
Most likely not including the recommended wipe actions (which must include the system partition if coming from FireOS) or failing to moving it to the top of FlashFire's operational queue just before flashing.
[Fire Original Android Development] CptKlink:
Ya I figured that out last night but now i just get a boot loop right after the amazon logo it restarts and does the same thing over again.
[Fire Original Android Development] DB126:
SlimLP has not received much love of late. Suggest sticking with one of the mainstream options (for this device) - CM 12.1 or Fire Nexus. The latter is having issues with Google Play Services at present making CM the best choice IMO.
[Fire Original Android Development] danielyoung200:
I can not mount any external Micro SD card. I have tried a new 128GB SanDisk Micro SD card which is working perfectly in my laptop, and is not getting detected by my tablet. Mount SD card and Erase SD card options are not working, and do not grey out when the card is removed. I have tried rebooting my tablet multiple times and is still not working correctly. I have also tried other cards including an 8 GB SanDisk Class 4. I have had this problem before and really want to get my new Micro SD card working, especially considering the fact that there is only 8GB of internal storage on this tablet.
[Fire Original Android Development] DB126:
See previous post regarding state of SlimLP. Other thoughts:

- reboot device; amazing how often this fixes SD card issues

- see if card is detectable in a 3rd party app such as Apps2SD, Link2SD or a file explorer/manager

- test format a small (≤32GB) FAT32 partition on another device

- try a different ROM to validate card reader is working; you can backup and restore SlimLP image using FlashFire
[Fire Original Android Development] Drivepnut:
Did you ever find the solution to this problem cause same exact thing happened to me
[Fire Original Android Development] Drivepnut:
I lost root root when I installed slim lp. I know I did everything right as I followed rootjunky instructions word by word. Everything was fine until I booted up. I went to supersu and I couldn't update binary. Downloaded rootchecker and it says I am not rooted. So I get ready to restore Amazon firmware so I can root tablet again. I power device off and then hold down power and volume down, it gets stuck on Amazon screen and I can't get into recovery. I have to hold the power button for 15 seconds so it will go away so I can turn device back on. Is there a fix for this. Any help in advance is appreciated.
[Fire Original Android Development] DB126:
Well, that's not good. Button combination to access stock recovery is <power> + <vol-up>, where <vol-up> is the button nearest the headphone jack.

There is no known recovery if the device will not progress beyond the Amazon logo. Contact Amazon for a courtesy exchange if still under warranty.

Tip: skip SlimLP and go for CM 12.1 next time around. To many bad outcomes with this build.
[Fire Original Android Development] Drivepnut:
I thought that button near the headset jack was the down button. It's strange because I can just press power and it will turn on and I am stuck with using it with no root but when I try to go in recovery it gets stuck at the Amazon logo. I wonder what cause all that to happen

---------- Post added at 12:18 AM ---------- Previous post was at 12:14 AM ----------

One question. Could I use rootjunky super tool to root it even though it is on the slim lp rom or is that no no
[Fire Original Android Development] sd_shadow:
likely will not root, could cause issues
[Fire Original Android Development] DB126:
An apparent interaction between FlashFire and SlimLP permanently borks access to the stock recovery partition. Happened with other 5th gen Fire ROMs (especially CM 12.1) in early releases but developer identified and addressed the issue nearly a year ago. There is no known fix short of sending device back to Amazon for a courtesy exchange if still in warranty.

You can try rooting with KingRoot 4.x (no need to use SuperTool); others have tried without success. However, KingRoot is continuously evolving so maybe you will have better luck. Be aware KingRoot is borderline malware that often spawns other issues that are difficult to resolve.
[Fire Original Android Development] danielyoung200:
Already tried rebooting device and has still not been detected. Tried using third party app to check, not recognized, formatted a 16 GB Kingston Micro SD on my computer and plugged it into tablet, still not detected, now just completely formatted the device and reinstalled FireOS 5.1.1 and still no Micro SD cards are detected. Is there any way that I can fix this?
[Fire Original Android Development] DB126:
Possible hardware problem given symptoms are identical after restoring FireOS. Contact Amazon for an exchange (if still in warranty).
[Fire Original Android Development] NightCrayon:
Make sure the partition is formatted as a primary partition and not a logical one. I had this same issue with a different ROM on a different device. Use minitool or other partitioning software to verify partition type. Ensure partition is formatted as a primary partition. This may not fix your problem, but its worth trying.
[Fire Original Android Development] wuhoatu:
do not flash version 0.15

otherwise you will stuck with the rom without root nor recovery​
[Fire Original Android Development] DB126:
Will take it a step further and say do not flash this ROM period. There has been limited (essentially no) developer support since initial release and many less than favorable outcomes. The perceived merits of SlimLP over other stable ROMs for this device do not offset this risks IMHO. At minimum review thread for detail and know what you are buying into.
[Fire Original Android Development] csolanol:
Hi al, sorry for the silence, but no time for this device for now. Gonna update the op to discontinued.

Enviado desde mi Mi 4c mediante Tapatalk
[Fire Original Android Development] NightCrayon:
Very sad to hear that, but thank you for everything :)
[Fire Original Android Development] connervt:
Agree. Thanks for being one of the first to develop for Ford. It was the first ROM I put on my Fire.
[Fire Original Android Development] wuhoatu:
I myself would like to say many thanks to developers. v 0.14 is the first room I flash to my fire. Just warning about the risk of 0.15
[Fire Original Android Development] TheJaHa5:
Quick Question...

Will this also work with the HD8 version? (5th Gen, 2015)
[Fire Original Android Development] DB126:
Nope - no root or custom ROMs for any HD 8 device regardless of generation. Enjoy FireOS as that's the only option. Add the Google Play Store and custom launcher for a (potentially) better experience.
[Fire Original Android Development] TheJaHa5:
Well, that sucks!!! SMH

Thanks a million, anyhow...
[Fire Original Android Development] BigMosley:
This is probably a no brainer question but since we're on a custom ROM, this latest Fire OS will have no affect on us, correct?
[Fire Original Android Development] csolanol:
Yup, no amazon ota system in the rom.
[Fire Original Android Development] BigMosley:
(shakes fist in the air) Screw you Amazon! lol
[Fire Original Android Development] BigMosley:
I usually turn off the tablet first to charge it and I noticed that after plugging it in the tablet turns back on. Is this a normal function for a tablet? Only way around this I've noticed is to plug it in first then turn it off.
[Fire Original Android Development] inscythe:
I was thinking that the FireOS 5.1.1 update might bring better compatibility with CM12.1, but then from the looks of it, the new bootloader will also block the booting of custom recoveries through fastboot...
[Fire Original Android Development] switchy85:
Cancel the setup after selecting a language and never connect to wifi. Then enable adb in developer options and go nuts. Either use that debloat script or boot recovery to load a new rom. Then no ota. :)
[Fire Original Android Development] sageDieu:
Yeah mine did the OTA on boot as well. Damn, guess we will have to find a new way around it - I'm not sure if it's related but I also can't get the ads to go away. I did the pm hide com.amazon.kindle.kso command and they went away last night but they were back when I woke up this morning.

---------- Post added at 12:17 PM ---------- Previous post was at 11:58 AM ----------

This is normal behavior.
[Fire Original Android Development] BigMosley:
This ROM works great with games like GTA : San Andreas, best $35 ever spent!
[Fire Original Android Development] azcom:
The first two of these tablets I played with I allowed to download and install the OTA update after connecting to WiFi during setup and had no problems with either of them booting to TWRP recovery via fastboot after the update. The 3rd one I sent into fastboot on first power up without ever booting into FireOS and they all worked exactly the same when flashing to CM12.1.

Regarding the Gapps thing fwiw I've been using 'open_gapps-arm-5.1-pico-20151120.zip' which I'm pretty sure I got from the rootjunkie site when I was looking into rooting this device before finding this thread and ggow's fine work on this ROM. I've not found and issues here so far using this file on any of the 3 tablets I've done.
[Fire Original Android Development] blueberry.sky:
The new FireOS 5.1.1 update (which is blocking root & fastboot) seems to have just come out yesterday. The previously update did not block TWRP.
[Fire Original Android Development] Vlasp:
Can someone test Clash of Clans on this ROM and reply with feedback? The time that I was on CM12.1, my device would shut down randomly while I was playing. Thanks!
[Fire Original Android Development] BigMosley:
Never played this game before but seems to be working.
[Fire Original Android Development] Vlasp:
Can you try keeping the screen on for around 3 minutes? It worked well when I was on it for quick peeks, but after around 3 minutes, it just crashed. Thanks for the quick reply! I will try this ROM out and update this post when I get to play (I am a hardcore player lol).
[Fire Original Android Development] BigMosley:
Sure no problem. I just left it alone on that same screen for over 5 minutes and its still responsive with that goofy background music playing lol
[Fire Original Android Development] Vlasp:
lol I guess I will install this ROM, since Camera is working, and I don't use video. Thanks!
[Fire Original Android Development] csolanol:
It works, another fan of that game here lol. Tablet reboots occasionally when it gets too hot. We have no control over thermal engine in the kernel. Btw don't play too much while charging, temperature will raise fast.
[Fire Original Android Development] BigMosley:
Out of curiosity, what would you use the camera for? Being that it's only 2MP and all.
[Fire Original Android Development] Vlasp:
Mainly just pictures of worksheets for my school, since my phone is very slow.
[Fire Original Android Development] azcom:
Aaah, I didn't realise there was another official update just released when I posted. That's what happens when you dont fully catch up on the thread after sleeping. Glad I'm aware now though.

Apologies to csolanol and diegocr too, I've been following both the slimlp and cm12.1 threads for this device and as many posts are similar on both threads I didn't realise I actually posted to this one when I referenced ggow's work. I know the guys have been putting in a lot of work to their respective ROM's and all deserve credit. It's nice to see them sharing fixes too, I love the spirit of the xda community.
[Fire Original Android Development] blueberry.sky:
What kind of temps are you hitting before it crashes or reboots?

I managed to hit 73 °C running stabilitytest before the freq throttled down a step. I might try adding heatsinking. Though the parts will take weeks to arrive from china.
[Fire Original Android Development] t3chwizard:
I had the reboot issue when playing a game as well.
[Fire Original Android Development] theophile2:
Could additional CPU governors and thermal controllers be built as modules for the stock kernel?
[Fire Original Android Development] blueberry.sky:
If it's an cpu/gpu intensive game try keeping an eye on the temp. Apps like cputemp will overlay a temp reading even within games.

---------- Post added at 10:56 PM ---------- Previous post was at 10:38 PM ----------

Hmm, I just got 2 reboots playing plants vs zombies2. Temps were just in the 60s °C.
[Fire Original Android Development] 4t701:
I've literally been playing "Gangstar 4" pretty much all day and haven't had a single reboot or lag at ALL(Dead Trigger also runs fine). This Fire seems to run cpu/gpu intensive games just fine for me.
[Fire Original Android Development] csolanol:
Guys talking about xposed and xprivacy module, why don't you use integrated app security on Settings->Security->First option?
[Fire Original Android Development] case-sensitive:
The security option you pointed out is a positive first step, but xprivacy provides much more fine-grained and usable control.

The built-in option simply turns on/off certain features, and some apps simply crash if they are denied access to those features (e.g. contact, location). On the other hand, if you turn off a feature (e.g. contact, location) in xprivacy for a given app, when this app tries to access this feature xprivacy will return a "fake value" (e.g. an empty contact list, a fake GPS coord) so the app will continue to work while preserving the users' privacy. Also, xprivacy provides control over many more features then the ones available through Setting->Security.
[Fire Original Android Development] blueberry.sky:
Xprivacy allows you to deny access to all identifiable information, including serial number or any device identifiers. I use that just as standard with any non-open source apps.

Do the ART optimizations mainly come from the ezio mods? Aka would SlimLP without ezio be able to run xposed?

I really like SlimLP & greatly appreciate the work csolanol & diegocr. Updates & fixes seem to come faster. I presume ggow may not have as much time at the moment to work on his CM12.1.
[Fire Original Android Development] Joshmccullough:
Anyone but me not getting the Chromecast option in Netflix? I'm getting it everywhere else (Google Play Music, YouTube, etc.), but it's not showing up in 'Flix....

Sent from my Slim ROM'd Amazon Fire
[Fire Original Android Development] t3chwizard:
To the dev, please leave the ezio mods in the ROM and do not remove them. If you want to use Xposed you can try to use Wanam's xposed. I don't think devs even support using Xposed much tbh. I for one hate Xposed. It is a security risk. Also have you even tried using Wanam's xposed yet?
[Fire Original Android Development] case-sensitive:
I tried wanam's xposed and no dice; see my post #7 in http://xdaforums.com/amazon-fire/help/differences-cm-12-1-slimlp-t3263452
[Fire Original Android Development] blueberry.sky:
Yep. Same bootloop with Wanam's xposed. Why is there a need to hate xposed? Don't like it, don't use it. :laugh:

What do the ezio mods bring to the table?
[Fire Original Android Development] t3chwizard:
Because Xposed is a blatant security risk. You are trusting the developers of Xposed mods with full access to your device, even more powerful than root.
[Fire Original Android Development] blueberry.sky:
You should have a serious conversation with whoever is forcing you to use xposed.

Root can be a security risk as well. Too much of a risk. We should all be good little children and only do what the manufacturers tell us to. We are just talking about xposed + xprivacy, not any random modules. Has anyone shown that xprivacy is using it's privileges for evil?
[Fire Original Android Development] mistical:
I chose to install SlimLP over CM12.1 and now wish I had read about Xposed absolutely not working ahead of time.

I honestly didn't think this was something I had to check on and make sure worked prior to installing. It's very disappointing. I've always enjoyed Slim rom's in the past (especially for the old Samsung Vibrant) and that's why I figured I'd want to configure my Fire with such too. Oh well, not anymore I guess.

I just never thought that there would be a dev here at XDA that would be making the decision for me rather or not I can install Xposed. Might as well remove root?
[Fire Original Android Development] sd_shadow:
it's certainly not that simple

---------- Post added at 10:26 PM ---------- Previous post was at 10:25 PM ----------

and root is not included with cm12

---------- Post added at 10:31 PM ---------- Previous post was at 10:26 PM ----------

if you don't like it, you can build it your self.
[Fire Original Android Development] mistical:
I don't think it's been explained here as to why it's not that simple? The only thing I've read through this entire thread that it's likely ezio's ART modifications is what breaks it (probably?). Honestly, since I/we don't know what these modifications or advantages are, I'd rather not have them if I can have Xposed and setup my device how I want.

You can still have root though, I'm about to flash it with it in a moment here (SuperSU 2.52 beta), which I'm sure you are aware of. It's not like it's being prevented from it.

I don't necessary have to build my own when I can just choose another rom over this. There are a bunch of other users wishing Xposed worked on this rom too. I even expressed myself I've enjoyed Slim roms since the Samsung Vibrant, which is a very old device at this point (2010). I just felt it was worth expressing my disappoint for something that a LOT of users do use here around the forums, Reddit and so forth (Xposed). It would have probably been better to have stated stated in the first post that they are choosing not to support Xposed and it'll never work, etc, whatever they want to add.
[Fire Original Android Development] sd_shadow:
Differences between CM 12.1 and SlimLP by oliman99