yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] bankara:
I have been unable to get FlashFire to flash CM12.1 (1-20151222-UNOFFICIAL) or RR(v5.5.9-20151217) or even to update the version of GappsS that I installed when I put SlimLP on it. I am running 5.1.1, never had a chance to install recovery on 5.0.1. I used RootJunky's tool and guide to root and install SlimLP 2.3 and his recommended version of Gapps. Gapps failed to install, I keep getting a "Unfortunately, Google Play Services has stopped running" error message.

I have tried updating to Resurrection Remix, CM12.1, or just updating Gapps and FlashFire always quits on me and reverts back to the previously installed version of SlimLP. I have tried wiping all options, tried with everroot enabled to inject Super SU and tried it disabled, tried installing micro, nano, and pico Gapps, but every single time FlashFire gets to the same point (wiping... and then it reboots without running any installs) and then just boots SlimLP. All of the zips are on an ext SD card.

I have read thru a ton of material over the last couple of days and I just want to get CM12.1 flashed on this tab and a lightweight version of Gapps but I cannot get it to work. I am not a dev but I have been flashing ROMS on my daily driver phones for years and for that one friend who always asks too :p. You can see in my profile I haven't ever asked a question before because I have always found my answer in the forums. Just tried the method outlined in post 1011 to no avail as a last shot. This time I am genuinely stumped as to what to do.
[Fire Original Android Development] glate:
It was discussed earlier in the thread. Either re-flash or follow these instructions:

http://xdaforums.com/showpost.php?p=64302530&postcount=766
[Fire Original Android Development] mmurphmsu:
Are you using an app to move your apps to your sd card? You may have to run a remount script
[Fire Original Android Development] seine16:
Thank you !
[Fire Original Android Development] MAGICMAN516:
Nope just using the native move to SD option in the APPS menu in settings. However I did some research and found that many people have had this issue with several different android devices and versions. So I doubt it's really a problem with the CM12.1 that we are using. I had just bought a new 64 gig SD card for the tablet and it may have something to do with that. I had a 32 gig in it while waiting for my 64 gig one to arrive. So this started after putting the new card in. I switched back to the 32 gig but haven't had a chance to test out my theory to see if it's the card or not. The consensus on the net for this issue is that I may have corrupted the card somehow. One guy fixed it by recreating the partition table. Others have fixed it with different cards. If no one else has the issue then I'll assume it's the card somehow.
[Fire Original Android Development] ssgelm:
I am having the same issue where gapps are wiped when doing an adb sideload from twrp.
[Fire Original Android Development] Katschunga:
Updated to the 2015-12-29 release via flashfire. Playservices kept crashing.

Reinstalled gapps. Playservice kept crashing.

Wiped everything apart from 3rd party apps and internal storage and reinstalled cm-12.1 and gapps. Playservice kept crashing.

Wiped everything apart from 3rd party apps and internal storage and reinstalled the 2015-12-23 release and gapps.

Everything is back working.
[Fire Original Android Development] glate:
I updated to 2015-12-29 via a dirty flash on TWRP. Play services keeps crashing. I've tried everything including a factory reset, formatting the system/data partition, reinstall GAPPS, reflashing the rom, etc and can't get it going.

I went so far as to follow https://github.com/opengapps/openga...re-open-gapps-related-what-can-i-do-to-fix-it which got me no where.

I'll try a previous version of GAPPs next I suppose? Failing that it looks like it's back to 2015-12-23 like you did.
[Fire Original Android Development] Deuces:
dirtyflashed latest cm / gapps / supersu via flashfire and no probs

appreciating your work
[Fire Original Android Development] der-mali:
I confirm: ROM dated 29-12-2015 seems to be a big mess:

Play Services crash, Google account(s) gone and can not add new account(s);

some other apps also crashed.

Went back to the 23-12-2015 ROM and this works perfectly!

All done with Flashfire, not via recovery.
[Fire Original Android Development] abacabie:
Play Services crash for me as well, installed from flashfire, full wipe first with pico gapps.
[Fire Original Android Development] sam tyler:
Sorry to report but getting Google Play services fails from 29 Dec 2015 update. even tried installing earlier play app and services, but still getting fail. (installed ROM, super su and Pico apps via twrp) in the end I got back into twrp and restored my backup.
[Fire Original Android Development] ggow:
- I'm not seeing any of these issues here

- Could some of you that are having problems with gapps after using flashfire to update send me the lastlog file

- then I can look into it
[Fire Original Android Development] nihil0:
Can I just flash the new image (20151229) over the older image with BLOCK_BASED_OTA support (20151222) without any user data lost?

adb reboot bootloader
fastboot boot TWRP_Fire_2.8.7.0_adb.img
adb push cm-12.1-20151229-UNOFFICIAL-ford.zip /external_sd/
install cm-zip from the recovery...
[Fire Original Android Development] Dark_N1ghtmar3:
Can I flash from slimrom to this or do I have to go to stock then flash?
[Fire Original Android Development] ggow:
- I have been able to now replicate the problem

- Will upload a new ROM in a minute.

- Link is going down now while the new one uploads

EDIT: New File is Up
[Fire Original Android Development] ggow:
New Build is Up

- Dated 29 Dec 2015 - PM Build

- Fixed Issues with upgrading ROM

- Tested by restoring backup of previous build

- Then dirty flashing new ROM with FlashFire

- Can someone let me know if it's working ok?
[Fire Original Android Development] Katschunga:
Hm.

Made a dirty flash with flashfire. 1st time I only wiped dalvik cache and cach partition. 2nd time I also wiped system data.

After each reboot no optimising of the apps and still on build Dec 22.

Strange.
[Fire Original Android Development] UCDguy:
Just did a full wipe and flashed the latest build. Get a play services crash after selecting wifi network on first boot up and can only proceed if I don't choose a network. Then get usual play services error after opening play store etc. Will revert back to an earlier build for now.
[Fire Original Android Development] x410x:
Seems to still be happening. Heres a list of how im going it:

Boot into TWRP

Wiped dalvik cache, cache, data, internal storage and system

Flashed the build you just uploaded and pico open gapps

Once I get to the setting up wifi part of the set up play services crashes, and you cant get any farther. I can skip setting up wifi but then if i try and add a google account, same thing.

---------- Post added at 05:45 PM ---------- Previous post was at 05:19 PM ----------

I also am have an issue with sd cards and usb otg storage. They never seem to mount, when they both work fine in TWRP and fire os. Whats odd is that it knows they are there as when I take out the sd card I get a notification that it was removed, but in the storage menu my only option is to erase it which does nothing if i press it.
[Fire Original Android Development] _AnAkIn_:
[MENTION=5749760]ggow[/MENTION]: Do you have any plan to get this into the official CM so we can have official nightlies? :)
[Fire Original Android Development] ggow:
- I have linked the previous version in Post #2 in case of problems

- I'll Also link back to this in the OP until understand the issues and they are resolved
[Fire Original Android Development] x410x:
Wait a second, does CM not support exFAT? I thought that was just a base android thing. What all file systems does this support?
[Fire Original Android Development] Scot2001:
Two things:

-Firstly is there a possibility this will get to cm and we will get nightlies?

-Secondly, will there ever be a possibility of an unlocked bootloader on fire os 5.1.1 ( sorry its a bit off topic but I wouldn't feel comfortable flashing this if it wasn't with twrp and I am stuck on fire os 5.1.1)

Thank you, any assistance would be gratefully accepted!
[Fire Original Android Development] glate:
exFAT has been working since the Dec 10 build.

http://xdaforums.com/showpost.php?p=64242506&postcount=572
[Fire Original Android Development] qtotter:
first, i tried to install it with flashfire on the 20151222 build (system/cache/dalvik cache wipe), and it stopped installing at the beginning and rebooted into the 20151222 rom somehow.

secondly, i tried to installed it using TWRP (system/cache/dalvik cache wipe), and it was successfully installed this time. i didn't get google play service errors (i use edited open gapps 'super' 20151215) as other people faced, but amazon video kept crashing as well as a couple of other apps. i should have given it a clean flash?

i am reverting back to the 20151222 rom from a backup, and will try to find what was wrong with my steps.

thanks for your updates, and happy holidays, ggow!

qt
[Fire Original Android Development] ggow:
- Nothing wrong with what you did

- The issue lies with the changes I made for the new release

- Stick with the 20151222 until I have the issues resolved
[Fire Original Android Development] ggow:
- I have identified why the Google Play Errors are happening

- Will let you all know when it's all resolved

EDIT:

- Fixed the Google Play Services Errors

- These were a result of the WebView changes not been configured properly

- The setup wizard is working again without error

- Tomorrow I'll resolve the installation issues with FlashFire
[Fire Original Android Development] BoulderGeek:
I dirty flashed 12/29 build over 12/22. Google Now launcher went away.

Several apps such as Astro File Manager and Root Browser now force close when looking at file system. I flashed G Apps Nano zip and that made some things better.

Now having to use ADW launcher as Google Now is nonfunctional. Still trying to figure out exactly what I do and do not have. Things apparently worked better on 12/22.
[Fire Original Android Development] x410x:
Is there a certain way I need to format them? I've tried 3 different sd cards and 2 thumb drives, none of which worked. But all of them show up fine on my phone. Formatted one of them to fat32 and it worked just fine. All of them were just formatted using windows default format tool, just changed them to exfat in the drop down. Can anyone confirm that exfat is working on the 12-23 build?
[Fire Original Android Development] bullet25:
First build for 12/29 - Hulu and Amazon Prime would not play.

Couldn't try the pm build, father needed the tablet had to flash back to 12/22 build.
[Fire Original Android Development] sandman512:
Ok, so little problem here. Just tried to flash into TWRP and no go. It says my bootloader is locked, never had this problem.
[Fire Original Android Development] DB126:
No one can say for sure but I think the chance is slim as recent Amazon bootloaders have proven to be robust. More likely another vulnerability will be discovered that permits access to fastboot and (indirectly) a custom recovery.
[Fire Original Android Development] topcaser:
Since Google play service does not run any more, no app is able to start. Therefore I can't get into flashfire any more. How can I flash the new version now?

Sent from my Galaxy S5
[Fire Original Android Development] Dark_N1ghtmar3:
Can I flash this over slimrom or do I have to go back to stock using flashfire
[Fire Original Android Development] qtotter:
flash the official firmware that matches your bootloader from recovery mode, and get root, install flashfire and start from the beginning if your bootloader is 5.1.1 or higher. it takes only 10 minutes or so.
[Fire Original Android Development] topcaser:
I would loose all my data by doing this. Can't I try a dirty flash by invoking the fastboot method? Hope that the adb commands are still working...

Gesendet von meinem Fire Phone mit Tapatalk
[Fire Original Android Development] Doggy77:
Thank you for your work! I am happy with the 20151222-version - despite one issue:

If using either VLC or the included Musicplayer I encounter a crash (music hangs) and tablet reboots after approx. 15 seconds. First I thought it depends on the SD-card, but after removing the SD-card and putting the music (MP3) on the internal memory it still crashes.

- After the music was started it lasts about 10 to max. 30 minutes till it crashes.

- The tablet is not used in this time (is used as music player for kids with flight mode on and no connectivity at all).

- Tablet is connected to power supply and fully charged.

Does anybody out there experience the same issue? And is there any chance to get a hand on whats hapening (e.g. logfile or so)?

Best regards,

Doggy77
[Fire Original Android Development] _AnAkIn_:
[MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] qtotter:
kind of confused... if you are still on 5.0.1 bootloader, OF COURSE, you can run a custom recovery from bootloader by "fastboot boot XXXX.img" to dirty-flash the 20151222 ROM.

what has anything to do with adb commands?? you can always force powering it off by holding power button for awhile and then go into bootloader by holding [power]+[vol-up ] together.
[Fire Original Android Development] ggow:
- Yes I plans to do so

- I have some things to fix before that can happen

- For now the CM-12.1 repos aren't changing very much so in the mean time I'll provide builds as things evolve
[Fire Original Android Development] ggow:
- I haven't forgotten this

- The next build I'm doing will be mostly clean-up

- I'll take a look at this in the following for the build following the next

- Just want to get all the installation issues sorted for the next one before going forward
[Fire Original Android Development] ggow:
- Just been testing restoring / upgrading etc between build I am working on today and 2015-12-22

- It turns out this build has an installation bug which causes loss of Gapps and SuperSU on downgrade

- To workaround this just flash gapps and supersu alongside the rom

- This will be fixed in the next build
[Fire Original Android Development] fmc000:
Hats off man, your dedication is simply awesome.
[Fire Original Android Development] ggow:
Need Help

- I have a new build to test

- Are there a couple of people willing to test initially before I release it?

- Need a FlashFire User and TWRP user
[Fire Original Android Development] chetta:
I can do either flashfire or TWRP for you [MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] ggow:
Thanks, I'll PM you now
[Fire Original Android Development] glate:
I can TWRP if you still need someone.
[Fire Original Android Development] Chief_Nodnarb:
Willing to test with either. Let me know if it's still needed.
[Fire Original Android Development] ggow:
- Thanks for the offer :)

- Think we have it covered now.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 30 Dec 2015

- Change log on Post #2

- I had to revert using Google's Prebuilt WebView (was the cause of Google Play Crashes)

- Cleaned up FlashFire and TWRP installation

- From testing it seemed good

- Sorry for any troubles etc with the 29 Dec Build which hope all resolved now
[Fire Original Android Development] sandman512:
[MENTION=5749760]ggow[/MENTION], I can do either [MENTION=5749760]ggow[/MENTION], first, do I need to flash GAPPS AND SU?

Also, cannot boot intp TWRP anymore on the PC i have been using all along. This happened after the previous flash yesterday. Thoughts?

THANKS!

EDIT: Got it, for some strange reason, ADB was turned off.
[Fire Original Android Development] glate:
I just formatted a fresh SD card using Windows 10 as exFAT (changed the drop-down to 'default allocation size' not that it likely matters) and it was detected in the 12-30 build. I don't believe it was detected in the 12-29 build but a lot was broken with that so I'm not 100% sure.

[MENTION=5749760]ggow[/MENTION] it appears that 'Unmount SD Card' is missing from the Storage options though. I just compared against my hltetmo running the nightly build which has the option.
[Fire Original Android Development] Chief_Nodnarb:
Running smooth so far. Everything looks great. Haven't run into any bugs yet, granted I've only been running it for about 20 minutes. Great work [MENTION=5749760]ggow[/MENTION], keep up the awesome work. This makes this Amazon slate worth having!
[Fire Original Android Development] ggow:
- Flashing a CM ROM can't affect the ability to fastboot twrp because the ROM does not touch the bootloaders

- Dont know why that might be

- You should be able to just flash the ROM and SuperSU
[Fire Original Android Development] ggow:
- Is the new build (30 Dec 2015) working ok for you then?
[Fire Original Android Development] glate:
30-12-2015 working great for me. All issues I had with yesterday's build are resolved. Only thing that appears to be missing is the unmount option for SD card but I only put an SD card in to test for [MENTION=1744821]x410x[/MENTION] so it doesn't affect me at all.
[Fire Original Android Development] ggow:
- Thanks

- Will look into the SD card unmount option
[Fire Original Android Development] der-mali:
Build 30-12-2015 is working great!

Flashed with Flashfire from 22-12-2015.

GMail first was not working (Play Devices crashed) so I reflashed GApps (pico) and now everything is fine.

Root also still available without reflashing SuperSu.
[Fire Original Android Development] Katschunga:
I guess this is more of a flashfire related problem.

After several tries to install 12-29pm and 12-30 I'm still stuck on the 12-22 release. Strangely after installing 12-29am I had the known problems so I guess the installation process itself worked though I didn't check the release number back then.

Any ideas?
[Fire Original Android Development] sandman512:
Just to update, flashed via TWRP and everything seems to be up and running.
[Fire Original Android Development] ggow:
- Could you send me the lastlog file from /sdcard/flashfire
[Fire Original Android Development] :
i tried flashing from slimlp using flashfire and it was starting to flash but it wouldnt go pass from patching system image.... i was force to shutdown and got cynogen start up but stuck on bootloop now i have to go to stock image fireos 5.1.1
[Fire Original Android Development] ggow:
- I am still tuning up and fixing installer scripts and so on

- I am going to upload another release which deals with a bug coming from FireOS 5.1.1
[Fire Original Android Development] :
thank you ggow i appreciate your time on the fixes.
[Fire Original Android Development] ggow:
New Build is Up

- Change log is on Post #2

- [MENTION=3729270]Katschunga[/MENTION] and [MENTION=7173628]djflaco908[/MENTION] could you try with this version and send me your logs if necessary

- Everyone else NO need to to update if you are on the previous build from today
[Fire Original Android Development] Katschunga:
Still no difference for me... :(
[Fire Original Android Development] chetta:
I have a new issue. On the tablet that I used FlashFire for today's build.

Installed Google Launcher and when clicking home button it took me into GeL able to save as default.

The issue came when I attempted YouTube - unable to sign into my Google Account.

I uninstalled GeL and turned back to Trebuchet. Still same issue with YouTube.

I cleared data on YouTube - able to open and run videos but not able to sign into my account.

(not sure if YouTube issues related to GeL. I'm pretty sure I used YouTube before setting GeL as default - not positive - been doing a lot of testing today)

Later tonight, I will do some more troubleshooting but just wanted to inform you of this [MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] :
just flashed the new built and it worked,google play launcher also working
[Fire Original Android Development] ggow:
- I will look into this more

- I'll continue to focus on these installation issues until its solid
[Fire Original Android Development] glate:
I finally found this post! I remembered reading it a while back and couldn't find the DPI you suggested (213). I was searching for 217. Doh!

Regardless, thanks! 213 looks great. Have you found a better setting or settled on 213?
[Fire Original Android Development] :
thanks for bringing this info out here because i had no clue why everytime i sat a dpi no themes didnt want to install and sd card wasnt showing after changing the dpi setting. also theres an app on google play its dpi changer and you can set your desire dpi and edit your built.prob at the same time all in one single step.

---------- Post added at 01:56 AM ---------- Previous post was at 01:54 AM ----------

everything seems working good, i cant send you the logfile since i get a error doing so because is to long
[Fire Original Android Development] BoulderGeek:
I had all sorts of Play Services weirdness after dirty flashing 12/30 over my funky 12/29.

I wiped cache and Dalvik multiple times and tried pico and nano GApps 122515. Finally, it seems to have stabilized and improved.

Apps that would quit when nothing storage now work. Google Now launcher still doesn't show, but ADW works fine. So, I'm calling this build improved!

Thank you so much for this large effort, ggow! You are really working for the community.
[Fire Original Android Development] :
try going back to stock and root the tablet and use flashfire app with the new rom, it worked for me
[Fire Original Android Development] monza1412:
Glad it helped. I read somewhere that the nexus 7 was using that dpi, so I settled on that.
[Fire Original Android Development] theUsualSuspexx:
Flashed newest build & micro gapps with flashfire...So far everything is great. Huge improvement over fire os. Much appreciated
[Fire Original Android Development] sd_shadow:
well for stock rom, should be same for cm12.1

---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------

http://xdaforums.com/showthread.php?t=3245644

OTG Working on 2015 Fire (kffowi/ford)
[Fire Original Android Development] sandman512:
Ggow,

Looking to flash this ROM, just a few questions.

1) After flashing ROM, reboot or flash SUPER SU?

Is there a video on this, I just don't want to mess this up!

Thanks.
[Fire Original Android Development] sd_shadow:
flash SuperSU.zip before rebooting
[Fire Original Android Development] Awesomeslayerg:
Cant we intergrate supersu into the rom?
[Fire Original Android Development] csolanol:
Yup
[Fire Original Android Development] trentonpls:
How the hell did he manage to get CM to work with the stock recovery?
[Fire Original Android Development] sd_shadow:
You temp boot Twrp

2015 Fire: Booting TWRP, Rooting, Installing Gapps with Video
[Fire Original Android Development] Awesomeslayerg:
If ggow intergrated the rom with supersu then it would be easier just flashing the rom wouldnt?
[Fire Original Android Development] sd_shadow:
yes, but only about 60 secs faster
[Fire Original Android Development] Awesomeslayerg:
Less people complaining and dosent skip a step lol.
[Fire Original Android Development] sandman512:
Ok, going to go ahead and do this tonight, any known serious issues? Also, I have a book that I have been reading, will that be saved? Thanks.
[Fire Original Android Development] sd_shadow:
http://xdaforums.com/showthread.php?p=63884233
[Fire Original Android Development] gottifour:
Hey guys, forgive my ignorance but I'm trying to add these lines to my build.prop but don't understand where you say " between the system stuff and the additional build properties" is at.

Thanks for any info!
[Fire Original Android Development] zach61797:
OK when you open it it starts with all the system info in a group

Then it has sections that are double spaced then a group its labeled additional build properties make it as one of those double spaced sections above the additional but not in the system info