yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] lebleu29:
adb can't find the device.

---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------

never mind, i figured out how to get into recovery. should i just restore stock firmware and then start again? thanks for your help.
[Fire Original Android Development] sd_shadow:
yes that is probably the best way
[Fire Original Android Development] DB126:
I do not think anyone has a definitive explanation why a small number of installs are failing. It is very concerning as the outcome is often a soft brick. Some have speculated the placement of wipe was the culprit and recommend moving it to the top. I agree as do others. That said, you claim placing wipe first bricks devices (or at least some devices). Further, you claim placing it last is the correct sequence based on personal experience and default behavior of FlashFire which always places wipe last. No one can take away your personal experiences. As for the placement of wipe I simply note that FlashFire remains in beta and may have some bugs. Only the developer can speak to the logic. To my knowledge he/she does not participate in the forums for this device. Failing guidance from the developer I'll stick to what others have recommended until root cause is identified.
[Fire Original Android Development] :
Well this is how it looks after selecting wipe first thenROM/supersu.zip/gapps.
[Fire Original Android Development] :
You see wipe was set to last by flashfire and that works for me. Now if I move wipe from the bottom to top then I'll have a bricked device
[Fire Original Android Development] ggow:
- FlashFire v0.26 is out

- There is mention in the release note of fixing issues with flashing CM

- I'll test this out a bit later in the evening
[Fire Original Android Development] :
Nice to know
[Fire Original Android Development] :
As chain fire said to select wipe before flashing a custom rom. this is how it looks and suppose to function. this is using the v26 of flashfire.

I went by the rules and wipe is at the bottom as usual
[Fire Original Android Development] :
See i wasn't in others words lying to some people here
[Fire Original Android Development] :
Add a wipe action before this flash meaning before you select a custom ROM select wipe first then ROM/su/gapps, and eventually wipe is set to perform last as mentioned. Thanks again
[Fire Original Android Development] Gllmour:
SlimROM

I have already installed a custom ROM - SlimROM. Now I want to install CM-12.1, I do everything right with flashfire and all that, but after second reboot, reset version of SlimROM is loaded.

What should I do?
[Fire Original Android Development] DB126:
The discussion here is illuminating and will hopefully bring a more consistent/reliable set of recommendations for utilizing FlashFire on this device. No one wants a brick.

No one is accusing you of 'lying'. Discourse does not equate to a personal attack unless one chooses to take it there.

---------- Post added at 07:44 AM ---------- Previous post was at 07:39 AM ----------

As you are using FlashFire I suggest waiting a few days before trying again. There is an active discussion on the proper configuration of this tool to avoid a possible brick. Better safe than sorry.
[Fire Original Android Development] :
[MENTION=5488402]Davey126[/MENTION] and [MENTION=4267571]sd_shadow[/MENTION] you were right, only if you are installing a new rom wipe needs to be on top but if you are installing updates then you don't need to setup wipe at first.

Got the reply from chainfire,

---------- Post added at 08:50 AM ---------- Previous post was at 08:44 AM ----------

I'll take that part back lol
[Fire Original Android Development] DB126:
Thank you for the prompt follow-up w/chainfire; make sense.

For the curious, the positioning of wipe in the operations sequence roughly corresponds to a 'clean' or 'dirty' flash depending on what options (partitions) are selected. When flashing a new rom it is usually best to wipe the system partition to avoid conflicts with the previous contents. If the data (some call it apps) partition is also included it is generally referred to as a 'clean' install. These steps are unnecessary when updating an existing rom to a newer release unless recommended by the developer. 'Dirty' installs have the advantage of retaining existing apps/settings but carry a small risk of things not behaving as expected (not to be confused with a brick or bootlooping; completely different problems). Those opting for a 'dirty' flash should consider wiping cache and dalvik (not system) as the last step as this often avoids startup weirdness but does extend the initial boot by several minutes as caches are rebuilt (often Android will detect significant changes and rebuild caches w/o an explicit wipe). This is not necessary on a 'clean' flash as the wipe operation is done as the first step and does not need to be repeated.

---------- Post added at 09:23 AM ---------- Previous post was at 09:23 AM ----------

For those who have left wipe as the last step and noted the system partition remains intact: it is quite possible FlashFire understands the order of operations and ignores a system wipe when it follows a system partition update. This is only speculation on my part; a follow-up with chainfire is needed to confirm.
[Fire Original Android Development] :
When I meant ( I'll take that back lol) was for saying people here thought I was lying. Flashfire remains a weird flashing tool especially to those who flashes randomly with wipe on top and not hitting a brick and for those with wipe at the bottom and not hitting a brick. Chains fire in others said that only when flashing a new rom wipe needs to be at top, so meaning for updates or other things no need no put wipe at first. Short words good understanding. [MENTION=5488402]Davey126[/MENTION] as of now whats going on with bootloader being unlocked? I have a friend from Germany that worked for assembling tablets and has a clue on what codes amzon is using and he also claims he haves the tools. But he won't get here in 2 weeks.
[Fire Original Android Development] :
This is chain fire response after my question.
[Fire Original Android Development] DB126:
I am not involved in efforts to unlock the bootloader on this device or identify other methods for working around Amazon restrictions. You'll need to follow other threads to track progress. Hopefully your friend can shed some light on the investigation!

---------- Post added at 10:14 AM ---------- Previous post was at 10:06 AM ----------

Interesting observation about leaving auto-mount unchecked. Not a lot of information in the related XDA forum beyond what is stated in the FlashFire instructions. I'll probably leave it unchecked going forward unless evidence mounts that it is needed.
[Fire Original Android Development] York_21:
Can't install it over SlimLP.

I'm using flashfire, no luck at all. Help will be appreciated.
[Fire Original Android Development] DB126:
What items are you including in FlashFire and in what order are they listed after the final addition? Did you change any defaults (eg: wipe options, auto-mount, etc)?
[Fire Original Android Development] nickhaven:
I went from slimLP to cm12.1. No issues here.

Make sure you flash fire looks exactly like the link below, the order, the options and triple check before flashing.

https://drive.google.com/file/d/0Bxl6L9mLcWDJNWxWQ0VONEc0VEU/view?usp=sharing
[Fire Original Android Development] :
If your updating roms or flashing gapps there's no need to put wipe first to perform. Here's the proof of the question I asked chainfire. [MENTION=5488402]Davey126[/MENTION]
[Fire Original Android Development] DB126:
Chainfire is entitled to his option. He is a well respected developer with a long history of delivering excellent products. However, those products target a broad spectrum of devices and custom roms - no two of which are identical. There are many situations where wiping partitions before/after an update to the system partition may not be not needed. In my personal experience (much, much less than Chainfire) wiping cache and dalvik on Amazon devices after flashing a rom yields better outcomes. It is an opinion, not a rule, which I will continue to share until proven unnecessary or dangerous. I have already outlined the consequences of wiping the system partition in a previous post. This seems to align with the prevailing option (supported by Chainfire) on the preferred configuration of FlashFire when used for this purpose.

Keep in mind FlashFire was not developed for the 2015 (5th gen) Kindle Fire although it seems to work fine

in most cases

as evidenced by the dozens/hundreds of successful installations reported in these forums. That said, it is beta software so some general recommendations may need to be tweaked for this device.
[Fire Original Android Development] :
Yes I have to admit that flashfire wasn't build specific for the fire. Is more like universal so anything may not go perfect. But at least is something that we can flash roms and not stay with boring fireos. Cm12.1 is so far the best for the tablet. I had issue with other 2 ROMs. Looking at flashfire now v26 looks more powerful and more scarier to mess with. I rather stick with v24 lol
[Fire Original Android Development] York_21:
Yes, those are the steps I'm using, but after "flashing" it reboots on SlimLP. I guess it has something to do with the cm download. I'll re-download it and try again.
[Fire Original Android Development] DB126:
Auto-mount recommendation for CM effectively answered in changelog for Flashfire v0.26 (keep it unchecked): https://plus.google.com/+Chainfire/posts/FjWwBm9vGyj

---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------

Suggest waiting as a new version of Flashfire is out (v0.26) and undergoing testing. A notable improvement is the handling of CM images which have sometimes proven problematic. [MENTION=5749760]ggow[/MENTION] will likely make an announcement when his evaluation is complete. Hang tight ...
[Fire Original Android Development] robnitro:
IBSS/ adhoc connect to, not working...?

Thanks for this rom!

I only have one issue.

I can see my adhoc wifi tether from my cellphone, but cannot connect to it. I put in the wep password and all but clicking connect does nothing.

Am I missing something, I thought that CM12 has ibss/adhoc built in?
[Fire Original Android Development] DB126:
I know this doesn't mirror your config but I can:

- seamlessly connect to mobile hotspot (using WPA2 PSK vs WEP)

- wireless connect to desktop shared folders via SMB

CM-12.1 build 20160126
[Fire Original Android Development] robnitro:
Are you connecting to an ad hoc or infrastructure wifi connection?

If infrastructure, its no different than any normal wifi. Unfortunately my windows mobile 6 phone can only do adhoc or usb tether. Even bluetooth on the HTC TP2 sucks so bad you cant use it to share lol. I stay with sprint 3g because I have a cheap unlimited plan!
[Fire Original Android Development] DB126:
Infrastructure. My mobile does not support ad-hoc networks. I have done this before on an older version of windows; more recently I have used internal (read easy/simple) functions which typically create an infrastructure connection. Can't find anything lying around (and working) that can establish an ad-hoc network for testing.

Not much help - sorry.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 03 Feb 2016

- Change log on Post #2

- On the weekend I should have some time test out FlashFire 0.26
[Fire Original Android Development] every1talk2me:
Since this device has very very limited internal storage, I am really curious if we will see CM13 development for this?

marshmallow could solve this issue as sd card can be used as internal storage.

Reason for asking:

I had installed just the play store on fire and then started to download big apps like Jurassic World, Fifa 15, 16 etc. And even when moved to sd card, they complain about low storage as from time to time they need to download 1 GB updates. So either the apps don't get downloaded/installed or they are useless as they can't get their required files from the server. Just play store and a couple of apps meant I just had 500MB left. No space for any other big app to even download now.

Any suggestions (I know some people mentioned OBB2SD), can gapps be moved to sd card?

Also, could someone please answer, how much internal storage is left after installing cm 12.1?
[Fire Original Android Development] glate:
CM13 pretty much requires a tethered boot (eww) or that the bootloader be unlocked. Until it's unlocked I wouldn't expect much for CM13 development.
[Fire Original Android Development] williamvito:
Has anyone on the latest 2-3 builds had success with having apps moved/stored/ran from the SD card?

I reverted back to rooted stock because of the issue, I'd prefer not to backup/wipe/flash/possibly have to restore unless I have to so any information that anyone could volunteer would be greatly appreciated, thank you!
[Fire Original Android Development] coopmaster:
One thing i have noticed in this room is that the move to sd card feature doesnt work, When you reboot those apps are gone forever. Dunno what this could be caused from. Also the wifi is sometimes very in and out. My device usually goes to not loading anything on chrome. Otherwise this is a solid rom.
[Fire Original Android Development] pbailey212:
KitKat has sd issues. Use this app and it will set permissions to let apps write to sd card. https://play.google.com/store/apps/details?id=jrummy.sdfix
[Fire Original Android Development] rdfry:
Link2sd is working fine for me
[Fire Original Android Development] DB126:
Available storage for apps/data will be approximately the same regardless of rom as partition sizes are preset and not easy to change. What you see in FireOS is pretty much what you'll have on CM and SlimLP (+/- a few hundred MBs).
[Fire Original Android Development] loocool2:
Nothing wrong with the 2/03 ROM, just needed to reboot seven times .
[Fire Original Android Development] fmc000:
Care to explain why? Was that related to the ROM upgrade?
[Fire Original Android Development] loocool2:
I was upgrading from the last build with xposed v80 (which works), no new gapps, supersu, and cleared dalvik and cache. I have live boot by chainfire turned on so I can see the logcat in real time and it seemed to say that the selinux needed to be defined, then just died after a few of those errors and started looping. Then somehow, it booted on the last try. IDK what happened. This has happened with the other builds, but only a few times, and even then I only had to reboot it once again.:confused:
[Fire Original Android Development] jeromeof:
I think the Apps moved to the SDCard are fine, but after a reboot the device / kernel runs something like a check disk making any apps unavailable for maybe 10-15 minutes until this process is finished. This process is a bit of a mess especially if there is a play store update as it tries to download the update then gets stuck as far as I can see.
[Fire Original Android Development] mmurphmsu:
I use Link2SD as well with no issues.
[Fire Original Android Development] kramalot:
No problems at all. Not using any special tools to move apps, just doing it from settings. Apart from the old problem of SD card apps becoming unavailable after removing a USB stick (requiring a reboot to restore them) all has been well all along.
[Fire Original Android Development] DB126:
Dirty flashed 20160203 over 20160126 using FlashFire v0.26 sequenced as follows:

- Wipe (Cache/Dalvik only)

- CM 12-1-20160203

- Open GAaps Nano 20160204

- SuperSU v2.65 (latest stable)

On initial boot ~75 sec on CM logo followed by 3-5 min rebuilding caches.

Zero issues.

Edit: Flashfire v0.27 is now out; see changelog for details.
[Fire Original Android Development] androidonkey:
Before flashing the update, did you select auto mount?
[Fire Original Android Development] DB126:
Nope - per guidance from app and FlashFire forum. Did not change default options (for zip).
[Fire Original Android Development] heavy2803:
I'm having troubles with latest build, I reflashed twice, clean install, clear cache. I'm Using micro gapps. I cant access any google account, google play services stop working. APP CRASH.
[Fire Original Android Development] JebusHerrl:
Hey guys,

I hope you can help me...

I'm new to this and now just trying to install the actual cm12.1 20160203 rom on my fire tablet 2015 7in with fireos5.1.1.

For this I've rooted the device with RootJunkys Supertool which installed SuperSU.

Then I've installed FlashFire 0.27 and gave it the requiered root rights.

Unfortunaltely the flash of cm12.1 doesn't work...

I become the warning message from FlashFire, that my /system partition is modified and this will porbably cause that the flash fails.

The FlashFire logs told me the same reason why it aborts the script.

Please can you tell me how I can make the partiton 'unmodified' so the flash process works?

I've already tried to make a factory reset (within fireOS and via boot recovery), but same result.
[Fire Original Android Development] Neffy27:
Not sure what to tell outside the steps others have already taken and mentioned throughout this thread.
[Fire Original Android Development] sd_shadow:
wiping cache and dalvik?
[Fire Original Android Development] qtotter:
The same question again?? The answer is it's impossible until someone finds a way to unlock bootloader...

Look for something like int2ext or other scripts...

---------- Post added at 09:27 AM ---------- Previous post was at 09:02 AM ----------

I'd flash only the latest cm12.1 first to check if it runs well. Then, I'd flash older gapps to see if Google service works. Lastly, I'd download the latest gapps again and confirm checksum before flashing it. You need to check each step one by one.

I dirty flashed 20160203 with the latest gapps super by flashfire, but everything works fine here.
[Fire Original Android Development] heavy2803:
Thanks, I solved installing old version of play services.
[Fire Original Android Development] DB126:
Please see this and this if you are planning to install/update CM 12-1 via FlashFire. Old news to many; hopefully save others from a non-recoverable brick.

Yes - I'm linking to my own posts (too lazy to find others) but same info has been repeated numerous times by others far smarter than me.
[Fire Original Android Development] JebusHerrl:
Okay...It worked now.

My solution was the following:

- root device with RootJunkys Supertool and SuperSU

- sideload FlashFire 0.27

- put CM, Open Gapps nano and SuperSU on SDcard

- start Flashfire and set the following sequence:

- wipe (system data, 3rd party apps, dalvik cache and cache partition)​

- flash ZIP cm12.1 with option 'mount /system read/write' enabled​

- flash ZIP superSU with option 'mount /system read/write' enabled​

- flash ZIP Gapps with option 'mount /system read/write' enabled​

- ignored the error message 'modified partition....' and flashed

- finished

Maybe this will help another guy. :)
[Fire Original Android Development] lebleu29:
Going from 5.1.1 and had lots of problems using FlashFire 0.24. Downloaded 0.26 and it worked flawlessly. Thanks to Nick Haven for helping me out.

Screenshot #1

Screenshot #2

Screenshot #3
[Fire Original Android Development] DB126:
Exact options I used; same outcome (flawless). Thanks for posting screen shots.
[Fire Original Android Development] Neffy27:
I've dirty flashed five times following many of the instructions posted but when I check "about tablet", it's never past the original build I initially flashed this ROM 22dec2015. Do I need to do a clean wipe?
[Fire Original Android Development] DB126:
Would seem the next logical step. Be aware that you may not be able to recover if you wipe and the new rom doesn't take (for whatever reason). Ponder if the update is worth the risk.
[Fire Original Android Development] Neffy27:
exactly my thoughts... Will probably continue to enjoy as is then... Thanks.
[Fire Original Android Development] doryx:
Thanks man, this worked for me!
[Fire Original Android Development] f1ux:
Can the OP be updated with a 'How to update' guide ?

I updated (no wipe) to the latest build from a January build by doing the following...

Using Flashfire

- Click the Red + button and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Cyanogenmod Zip

- Click the Red + button again and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Open Gapps Zip. ( If you don't I get play services stopped error )

- Click the Red + again and choose 'Wipe'

- ONLY tick Dalvik and Cache.

- Press the big FLASH button.
[Fire Original Android Development] joe90bentley43:
Hi all - eyes are going now after reading lots of posts. I have slim lp on my tablet at the moment. I want to put the latest cm on. Do I need to go back to stock then use flashfire to add CM. Or can I go straight to cm with flashfire?

Many thanks for any help!!!
[Fire Original Android Development] DB126:
Noted wipe was at the bottom which is fine for a 'dirty' flash. Wipe should be repositioned (dragged) to top for when installing a new rom.

---------- Post added at 08:29 AM ---------- Previous post was at 08:19 AM ----------

- no need to return to stock

- use FlashFire 0.26 or above

- wipe should be at top of list (you will need to move it) and include the system partition

- read other recent posts in this thread for additional details including screen shots of options used
[Fire Original Android Development] joe90bentley43:
thanks for the info much appreciated
[Fire Original Android Development] ggow:
- Has anyone tested this with FlashFire 0.27?

- If so then I'll update the OP with the info
[Fire Original Android Development] DB126:
Yes - no issues with 0.27. Dirty flash configured identically to recent 0.26 flash.
[Fire Original Android Development] ggow:
- OP Updated, thanks for the info
[Fire Original Android Development] raaj007singh:
will this rom works with lenovo A3300 hv? pls reply:confused:
[Fire Original Android Development] sd_shadow:
no, roms are device specific
[Fire Original Android Development] raaj007singh:
:good:

thanks...

I'm new to this type of work. what happen if i install this rom to my tab. will it damage.
[Fire Original Android Development] tonyt3rry:
I don't know what version I'm on is there a sound bug I'm finding YouTube has no sound until I go to all sounds and do it that way even tho the sound is already maxed even on silent it still

Has touch sounds
[Fire Original Android Development] DB126:
[MENTION=5749760]ggow[/MENTION] - it would appear you are not taking a position on the sequencing of 'wipe' in the FlashFire operations sequence when installing CM over another rom. No doubt you have seen Chainfire's guidance on this (0.26 release notes). Just want to confirm the irrelevance from your perspective so everyone is singing the same tune.
[Fire Original Android Development] ggow:
- I am going to experiment a bit tomorrow with going from fireos to cm and cm updates

- Also want to see that what happens if I revert the changes specific to getting flashfire to work in the first place with a view that chainfires changes should have fixed at least some of the initial problems

- I'll respond when I have gathered more information.
[Fire Original Android Development] doryx:
I used 0.27 with no issues as well.
[Fire Original Android Development] f1ux:
The instructions I posted are for UPGRADING. It says this in the post. Not changing from one ROM to another.

If you are upgrading CM to a newer build you do exactly as I stated in my instructions that are now in the OP.

You would only do a full-wipe if changing rom base.
[Fire Original Android Development] salopette:
Please help, I have made my fire7 death

Hello, you ask for help.

I have my Fire 7 5th ruined.

Had CM12 flashed over fastfire, and the tab is now hanging at the start on the CM logo.

I'm not into the recovery menu, it only light up the Amazon logo if I want to Recovery.

Fastboot is still working, but I just do not get ahead.

Sorry for my English, I am using Google translator. Thanks for any help