yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] gottifour:
Thanks so much for the response!

Are you using an app or is that screen shot in the settings somewhere? I see an option to add in ROM toolbox and build.prop editor but they aren't double spaced like your screenshot so I wasn't sure where to add it.
[Fire Original Android Development] sd_shadow:
Looks like he was using ES Note Editor, it is included with ES file manager
[Fire Original Android Development] gottifour:
Thanks!

That's actually where I was looking because I love that app and I thought it looked familiar. I didn't know that was an option though.

I will go there now.
[Fire Original Android Development] zach61797:
I go into the system folder and open it there and edit
[Fire Original Android Development] gottifour:
I see it now in es file explorer... I have always used an app to edit it instead of just going to the actual source.

Thanks again for the help guys!

Edit: That worked great thanks to all!
[Fire Original Android Development] kenokech2:
Where is your manifest.xml

I tried building your source yesterday but I couldn't find your manifest or any reference to it. And is Bitbucket better than Github?
[Fire Original Android Development] ssgelm:
Happy to report that 20151230-R01 fixes the need to reflash gapps! Thanks [MENTION=5749760]ggow[/MENTION] for your hard work on this!
[Fire Original Android Development] Katschunga:
Thanks a lot ggow!

If it works for everyone else maybe the error is just a problem in my installation. At the moment I'm too lazy to delete everything and start again from fireOS...
[Fire Original Android Development] ggow:
- This was going to be my next suggestion to you

- Sideload FireOS 5.1.1 through amazon Stock recovery

- Root

- Then try FlashFire again with the latest release

- Send me the logs if you have a problem
[Fire Original Android Development] ggow:
Mod for using prebuilt / stock boot.img

[MENTION=2511007]csolanol[/MENTION] & [MENTION=4375260]diegocr[/MENTION]

- I have made modifications which allow the signed boot.img to be automatically added instead of building a new one.

- No copying the boot.img manually anymore :)

- c64a467e81df55d72774d16d851182adb2839514

- d6eb4a41cf73673e27a7e7872274f93849eef265
[Fire Original Android Development] Katschunga:
Will do so...

Btw: Did you see my PMs with the logs?
[Fire Original Android Development] ggow:
- Yes I did

- I need a new log from you after you have tried to flash the new one if you still have problems
[Fire Original Android Development] jamesking420:
Hi,

Can I just "Dirty flash" the latest version over the 16/12/2015 version? If so, I guess I'd do this by booting in to the temporary custom recovery using fastboot, and then flashing via the recovery?

This doesn't appear to be covered in the first two posts. Sorry if I've missed it. :)
[Fire Original Android Development] ggow:
- Yes dirty flash the ROM, that should be it

- If you run into problems just go back to TWRP and dirty flash gapps (and supersu.zip if you use it)
[Fire Original Android Development] Katschunga:
-sideloaded fireOS 5.1.1 without wipe

-rooted with the supertool

-installed cm-12.1 and gapps with flashfire with wiping only system data, dalvik cache and cache partition

All my apps and their settings are still there, the version number is 12-30 and everything seems to run smooth.

Hopefully I will not run into any further problems now. When I do, a factory reset and a full wipe will follow.
[Fire Original Android Development] ggow:
- Good to hear you're up and running :)
[Fire Original Android Development] Fobos531:
How come you can boot CM with locked bootloader?
[Fire Original Android Development] sd_shadow:
Lots of Devices with locked bootloaders, can boot custom roms.
[Fire Original Android Development] schergr:
Google Play Games

Anyone else having trouble installing Google Play Games on the latest ver [30 Dec 2015-R01]. I get an error: Can't Install App "Google Play Games" can't be installed. Try again, and if the problem continue, get help troubleshooting. (Error Code: -505)

Anyone?

Appreciate any insights.
[Fire Original Android Development] Signor Rossi:
Hi, sorry, which Version of OpenGAPPS ?

ARM ?
[Fire Original Android Development] sd_shadow:
yes arm 5.1.1
[Fire Original Android Development] CharleySimmons:
How are you trying to install? Via play store or via sideload?

I haven't tried the 30 Dec 2015-R01 release, but seems like on the earlier release I had to sideload games.
[Fire Original Android Development] fmc000:
Searching this thread for "505" gives eight answers... Have you tried that before posting?
[Fire Original Android Development] sandman512:
[MENTION=5749760]ggow[/MENTION], fwiw every time I flash a new build, I just add the gapps and su zip file, seems to work for me.
[Fire Original Android Development] schergr:
Obviously I didn't think of it, otherwise I would have seen it, but thanks for pointing it out by being smug. happy New Year.
[Fire Original Android Development] DB126:
Agreed. Not sure why this is such a big deal. Does refreshing SU and Gaaps reset user configs (not that I have noticed)?
[Fire Original Android Development] topcaser:
I also got it running again after flashing today's build alongside with gapps. Thanks ggow

Sent from my Galaxy S5
[Fire Original Android Development] glate:
You forgot to mention that it's in the FAQ in post 3 as well ;) Pretty rough.

http://xdaforums.com/showpost.php?p=63834234&postcount=3
[Fire Original Android Development] fmc000:
It's not me being smug, it's just you being lazy and cluttering the thread. Totally against XDA netiquette.

---------- Post added at 08:09 PM ---------- Previous post was at 08:09 PM ----------

Yup, my fault indeed :D
[Fire Original Android Development] Signor Rossi:
What is the best way to get root after installing CM?

Gesendet von meinem KFFOWI mit Tapatalk
[Fire Original Android Development] :
You can either flash the supersu.zip or root it with the tools that rootjunky provides to root fireos 5.1.1. I haved rooted my fire with both methods and works like a charm

---------- Post added at 08:10 PM ---------- Previous post was at 08:07 PM ----------

You can either flash supersu.zip or root it with the supertool that root junky provided to root the fireos 5.1.1. I haves rooted my fire with both methods using custom ROMs and worked like a charm
[Fire Original Android Development] harold99:
I had exactly the same errors a few days ago building for another device I think maybe some files are corrupted
[Fire Original Android Development] Signor Rossi:
I just realized that I can simply enable root in the developer options.

Thanks

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1

---------- Post added at 10:30 PM ---------- Previous post was at 09:41 PM ----------

Sorry, I just realized Titanium Backup got root, but can't access the external SD card. Any ideas?

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] :
I don't think enabling root from developer option gives you root root,but I maybe wrong because I tried that on slimrom and it didn't give me root prompt for apps like flashfire. sorry I never used titanium backup so I can't respond to that question. But there's alot of wonderful people here thats willing to help you.
[Fire Original Android Development] qtotter:
funny... 2015-12-30-R01 also failed to install by flashsire and stopped in the beginning on my side... i was on 20151222. i tried multiple times, and it didn't work... any advice?

install from twrp works fine as usual...
[Fire Original Android Development] :
I was in your same position like 2 days ago. Try flashing the latest built but on fireos not custom ROM. So you have to start from scratch.stock,root,flash fire,flash the latest built with supersu.zip and gapps. If that doesn't seem to work then try flashing a different ROM that's not cm try RR or slimlp ROM and from there try to flash the new built of cm. That was my fix.
[Fire Original Android Development] nihil0:
Can I just flash the new image (30 Dec 2015-R01) over the older image with BLOCK_BASED_OTA support (22 Dec 2015) without any user data lost?

Like this:

adb reboot bootloader
fastboot boot TWRP_Fire_2.8.7.0_adb.img
adb push cm-12.1-20151230-R01-UNOFFICIAL-ford.zip /external_sd/
install cm-zip from the recovery...

Is this what you call Dirty Flashing?
[Fire Original Android Development] ggow:
- Yes you can flash over the older image

- Dirty flash means you are doing an upgrade of your Rom without wiping you data, cache, dalvik etc so yes
[Fire Original Android Development] Signor Rossi:
Anyone tested Titanium Backup yet?

If so, can you check if you can save the backups to the external SD card (sdcard1)?

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] ldeveraux:
Working for me with external card access through xposed !
[Fire Original Android Development] Signor Rossi:
Thanks, but I'm not a big fan of xposed.

Edit I installed a SD card fixer from the play store. It's working now

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] bl4cKz4cK:
I've skipped over the past 30ish pages but in case I missed anything: Are there any updates / fixes yet for the multiuser Bluetooth issue? I haven't seen anyone mentioning it and the last time I've tried it, the problem still seemed to occur.

Happy new year by the way, nice to see that there is still a lot of activity in this thread! Keep it up!
[Fire Original Android Development] Webern:
I flashed cm12.1 on a pre-5.1.1 device but now i have one with 5.1.1 i'm not sure what the process is. do you sideload flashfire, then use it to flash cm, supersu, gapps? is that it? where does twrp come into it, or does flashfire replace that step? what about the factory reset; when, if at all, is this done?
[Fire Original Android Development] :
You suppose to flash a ROM that matches your firmware because let say you was on fire os 5.1.1 and you flashed 5.0.1 stock image you will have a bricked fire tablet I don't think you will recover your tablet back if you downgraded your firmware that will be called hard bricked. And yes you use flash fire to flash the ROM and supersu,gapps. It should take 3 to 5 min when flashing is done.

---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------

What you did was correct you flashed cm 12.1 which is 5.1.1 on top of fireos 5.1.1 sounds normal to me. Also use the ROM specifically made for fire tablet. And remember if you want to go back to stock for any case flash the latest stock image from amazon or rootjunky has a copy either way.
[Fire Original Android Development] Webern:
Thanks. But that requires a rooted device. How are you rooting a stock, brand new device?
[Fire Original Android Development] sd_shadow:
http://xdaforums.com/showthread.php?p=62986666
[Fire Original Android Development] Signor Rossi:
https://www.youtube.com/watch?v=sVv1D_LNLTg

Here is the guide for the super tool

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] blueberry.sky:
I would expect a fix to be mentioned in the Release Notes / Changelog. Don't see it. You can also always search the thread for "bluetooth" to find any mention. Results are sorted by most recent.
[Fire Original Android Development] ldeveraux:
Well then you'd be better off on Slim...
[Fire Original Android Development] qtotter:
Thanks for your tip, but what you're saying is you cannot update cm by flashfire? I can use twrp, so it's not really an issue for me, but I would like know the reason why you cannot flash cm over cm using flashfire... That sounds kinda strange...

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

Well, not everyone wants to use xposed. Not everyone needs to use sd card as internal storage. For some people like me, sd fix app is good enough although he should have googled before he asked in the thread because it is part of Android security.
[Fire Original Android Development] ggow:
- Upgrading CM via FlashFire is working fine for me here so should work just fine for everyone else.
[Fire Original Android Development] Webern:
Thanks! I got there in the end.

---------- Post added at 10:19 ---------- Previous post was at 10:16 ----------

The root junky tools is the way to go. If you end up with fireos 5.1.1 and you flash cm but not supersu/gapps and need to reboot and flash gapps then flashfire won't run unless you're rooted so you have no choice at that point.
[Fire Original Android Development] Signor Rossi:
Why?

I already fixed the SD issue by installing a app for this.

Now Titanium Backup can access the external SD card fine.

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] qtotter:
I tried it multiple times, but flashfire stopped...
[Fire Original Android Development] Signor Rossi:
Did you get an error?

Give it some time. Flashing is quite slow, but worked fine for me.

Did you follow all steps from the video?

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] :
I don't know what was the particular problem that I couldn't flash cm over cm and doing a clean install. I also jumped back to stock to flash and it didn't work neither. I have no custom recovery install, I just use flash fire more safer in my opinion. But ggwo found it fix for flashing built r01 to fix the issue some like me was having. And boom that worked like a charm. Now I have xposed installed this latest built from ggwo is great.
[Fire Original Android Development] blueberry.sky:
FlashFire is actually riskier than using twrp recovery. FlashFire is in beta & seems a bit buggy. If you have the FireOS 5.1.1 bootloader then FlashFire is your only option otherwise twrp is better. You can check if you have the 5.1.1 bootloader just by trying to load twrp, it will fail (without harm) in 5.1.1.
[Fire Original Android Development] :
Maybe so,after the upgraded to 5.1.1 the bootloader is locked and supposedly twrp won't work if I had taken 5.1.1 before flashing the custom recovery. Thinking maybe you have a working custom recovery because maybe you flashed twrp before accepting the 5.1.1 upgrade am I right or wrong? Also I prefer flash fire because it doesn't flash a custom recovery,so let say if I ever had a hard bricked I can still use amazon recovery to recover the tablet using adb flash
[Fire Original Android Development] sd_shadow:
no, twrp can only booted, not flashed, so it is just temporary with 5.0.X
[Fire Original Android Development] :
Also I never wanted to run a custom because I was aware of flashing a custom recovery and since chainfire made more easy for us to flash ROMs without flashing a custom ROM what can be better? Well I had a bad expreicence once using a custom ROM it was my fault anyway. But I rather stick in my opinion in safer way. Lol I'm not saying flash fire is the best but for rookies like me it makes it way easier

---------- Post added at 10:10 PM ---------- Previous post was at 10:02 PM ----------

Ohhhh OK so it only boots in trwp but it doesn't flash custom recovery? Oh I thought it touches amazon recovery if I used twrp since people from others sites mention reboot in recovery in twrp. Mmmm so is twrp is safer than flashfire in your opinion?
[Fire Original Android Development] sd_shadow:
depends on what you consider safe, if fire is on 5.0.X, I don't think FlashFire will brick it, but if flash fails with FlashFire, you may have to boot twrp to fix it.

If the Fire has 5.1.X, booting TWRP is not an option, and some have reported that they could not boot stock recovery after trying to flash a rom with FlashFire.
[Fire Original Android Development] blueberry.sky:
On other devices you can install twrp (or other custom recoveries) but on the Fire we can't actually install twrp. Instead we only temporarily load twrp into memory. The stock amazon recovery is not touched.
[Fire Original Android Development] :
I see I thought using twrp or cm recovery you needed to touch the stocky amazon recovery. Thanks and I know I know I need a booya in my face lol now i know a new info for me to keep.

---------- Post added at 10:50 PM ---------- Previous post was at 10:45 PM ----------

Yes i accepted the upgrade to 5.1.1 and since I herd that after upgrading it twrp was in other words impossible to use because of the bootloader. But thanks for a other info. And yes I can still use amazon factory recovery after using multiple times flashfire. I think is being lucky some people can access factory recovery after using flashfire. Now that you mentioned that now I'm getting scared lol
[Fire Original Android Development] Scot2001:
Do you think there will ever be a way to use twrp on fire os 5.1.1, or even possibly cyanogen recovery. Any feedback would be much appreciated
[Fire Original Android Development] sd_shadow:
Always in motion is the future
[Fire Original Android Development] Fold0rDie:
I am unable to install the Google Play Games app. I keep getting "Google Play Games can't be installed...Error code: -505."

So I decided to flash to the latest 12.1 build and the Gapps micro package, but it still is giving me this error message. The solutions I found online I don't think apply to my situation with the Fire. Anyone else with some suggestions? Thx
[Fire Original Android Development] Scot2001:
Just download an older version of apk mirror. Then update. This has been mentioned earlier in the thread, if you would care to read
[Fire Original Android Development] sd_shadow:
http://xdaforums.com/showthread.php?p=63834234
[Fire Original Android Development] Shinyhead:
Not sure if the solution you have tried was installing an older version of the apk?
[Fire Original Android Development] qtotter:
it just stops and reboots without any errors on the screen. i found flashfire log in the internal strage. at the end, it says;

[UI] FlashFire - © 2015 - Chainfire
[UI]
[UI] Installing [/mnt/media_rw/sdcard1/cm-12.1-20151230-R01-UNOFFICIAL-ford.zip]...
[UI]
[OUT] Archive: /mnt/media_rw/sdcard1/cm-12.1-20151230-R01-UNOFFICIAL-ford.zip
[OUT] inflating: META-INF/com/google/android/update-binary
[OUT] inflating: META-INF/com/google/android/updater-script
[OUT] minzip: Extracted 3 file(s)
[OUT] about to run program [/tmp/install/bin/backuptool.sh] with 2 args
[ERR] grep: /tmp/gapps.prop: No such file or directory
[ERR] df: /tmp: can't find mount point
[ERR] sh: Available: bad number
[ERR] sh: Available: bad number

it seems like flashfire failed to create /tmp...
[Fire Original Android Development] blueberry.sky:
Maybe. If we can get kexec working properly then a safestrap bootloader will be possible & 5.1.1 Fires could use that to run a custom recoveries.
[Fire Original Android Development] Fold0rDie:
Thanks for responding to you and Shiny and apologies for missing the FAQ. I ended up installing the current APK via ADB after going through another XDA thread I Googled. Been a fun day :mad:
[Fire Original Android Development] :
Is kexec is a custom kernel for fire tablets? If so is it over clocked?
[Fire Original Android Development] sd_shadow:
kexec, abbreviated from kernel execution and derived from the Unix/Linux kernel call exec, is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running one. https://en.m.wikipedia.org/wiki/Kexec
[Fire Original Android Development] :
Thanks for the info [MENTION=4267571]sd_shadow[/MENTION]
[Fire Original Android Development] blueberry.sky:
Kexec is just how we can load custom kernels on devices with a locked bootloader, like the Fire. During boot the bootloader checks that the kernel has not been modified (if modified it won't boot). Kexec allows switching in a different kernel while the device is running, after it already passed the bootloader check. Wikipedia kexec
[Fire Original Android Development] qtotter:
i confirmed that flashfire only installed cm over cm when there is enough space left in /system (i don't know why.)

if you install cm + supersu + gapps mini, you will have 388MB left in /system. in this case, you can use flashfire to install cm over cm. i copied a dummy file (145MB) into /system, then flashfire stopped as i explained.

i installed gapps super with gapps-config.txt (by twrp), and there was only 235MB left in /system. i guess this was the reason, and flashfire users need to watch free space left in /system. it's more like a flashfire issue, not the rom.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 04 Jan 2016

- Change log on Post #2
[Fire Original Android Development] StackOverflow13:
Could someone please advise me as to how to get into twrp from fastboot mode (adb commands) running latest cm build bootloader 5.01. TIA. or better yet straight from CM?
[Fire Original Android Development] csolanol:
Boot your device in fastboot mode (volume up + power) and connect it to your computer. Type fastboot devices to ensure that your device is there. Move to the path where twrp image is and type: fastboot boot twrp_image_name.img
[Fire Original Android Development] StackOverflow13:
Sorry I was being an idiot had mine plugged into charge instead of connect doh!. sorry. Thanks for coming back so fast though , just building a bat file for for fast boot plus twrp from any rom.
[Fire Original Android Development] Signor Rossi:
Thanks for this Build, love it!

No offense, but why not use CM13?

Let me know if I can be any help?

Gesendet von meinem A0001 mit Tapatalk
[Fire Original Android Development] ggow:
- CM13 is not bootable on our current stock boot image which would mean a mandatory tethered boot - Not ideal

- Really need an unlocked bootloader
[Fire Original Android Development] Signor Rossi:
Ahhh, thanks.

CM12 is more then I could wish for ☺

Gesendet von meinem A0001 mit Tapatalk
[Fire Original Android Development] StackOverflow13:
I too am v happy with cm12 but i too would love to see cm13 however with all the cm13 builds I've seen for my phone sdcard is always an issue. But hey were tinkeres & love to play around?
[Fire Original Android Development] Shinyhead:
Stupid question but what capabilities does wifi display enable? Never tried this before.
[Fire Original Android Development] :
Thanks [MENTION=1531770]ggw[/MENTION]o,like your work
[Fire Original Android Development] der-mali:
This is so cool and a great coincidence!

Today's CM build got the WIFI Display enabled and also today (!) I got my (Amazon) Fire TV Stick.

Now I can cast my tablet's display on my TV.

To activate cast or WIFI display on your tablet go to:

Settings

(Device)

Display & lights

(Screen)

Cast screen

Select WIFI display in the top right corner menu and enable it.

It will show your tablet's display on your Smart TV, Fire TV Stick, Chromecast stick or whatever.

Your external device and your Fire tablet must use the same WiFi hotspot!

On your Fire TV Stick remote control long press the home button and chose "mirroring".

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

See my post #1265!
[Fire Original Android Development] Signor Rossi:
Small feedback from me on the latest build.

I lost some icons on the standard launcher. Not sure if it's just me.

I did wipe dalvik and system cache

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] ldeveraux:
why...uh...why would you want to do this?
[Fire Original Android Development] der-mali:
Why not?
[Fire Original Android Development] DB126:
Let's see...7" personal (entry level) display vs 42" family room TV for sharing HD photos, videos, etc. Hum, let me think.
[Fire Original Android Development] ldeveraux:
Ah ok, didn't know the fire was powerful enough to stream video
[Fire Original Android Development] theophile2:
Yeah but 1024 x 600 at 42"? Not sure I want to be able to count the pixels.
[Fire Original Android Development] DB126:
Depends on zoom (rather not), content and upscale algorithm on TV (if available). Beats hovering over a 7" screen showing granny the latest family pics. Pixels aren't a discussion point in that context.