yashsingh1/xdaforums huggingface dataset:
[7" Kindle Fire HD Android Development] :
Not sure, I'm using 2.65 myself.
[7" Kindle Fire HD Android Development] ipdev:
In twrp, (Advanced - Terminal) type

echo SYSTEMLESS=false>>/data/.supersu

(Only space is between echo & SYSTEMLESS.) Then go back and install su.

- running beta 2.72
[7" Kindle Fire HD Android Development] kotey:
I don't know of this is not a weird thing to ask...

We know that this rom took 4 mins to boot.

My guess is it's related to camera/sound driver error...

Using chainfire's LiveBoot shows all the reds are exactly that...

So, let say for the time being, drop the support for camera (it doesn't work yet, anyway) so that we got 1 minute boot, probably...

Just saying.
[7" Kindle Fire HD Android Development] monster1612:
Nice find. Could you enable all logcat buffers & levels, the "display kernel message log" option, and the "save logs" option (preferably from a clean flash of the ROM)? After that, reboot, upload the /cache/liveboot.log file, and then disable the "save logs"option afterwards. I think that would likely speed up the debugging process.
[7" Kindle Fire HD Android Development] sslove32:
I'm getting in late on this as I rooted and flashed CM12 and haven't kept up. I found this thread and it perked my interest so I downloaded this and attempted to flash but got a failed message. I'm using TWRP 2.6.x.x

Could this be the issue? Thanks for your work on this.
[7" Kindle Fire HD Android Development] monster1612:
Yep, you'll need to update your TWRP version to either 2.8.7.x or 3.0.x, both of which are available in the 7" development thread. Flash the chosen TWRP image via fastboot, type fastboot -i 0x1949 oem recovery to boot into that image, and then flash CM13 like normal. Also flash gapps in that same pass if you prefer them, as you'll need to do so before the first boot or else go through constant force closes until you manually grant the required permissions to each core Google app.
[7" Kindle Fire HD Android Development] wizahh101:
Is there any way to speed up boot time from 4 1/2 minutes to 1-2 minutes?
[7" Kindle Fire HD Android Development] alexander_32:
[MENTION=6751354]transi1[/MENTION] gave me a permission to post this.

Here is the latest build (MOB30M):

https://www.androidfilehost.com/?w=files&flid=68326

DON'T FLASH SUPER SU AND USE IT AT YOUR OWN RISK.
[7" Kindle Fire HD Android Development] mikeataol:
I installed this from stock, opengapps pico, formatted cache and data as f2fs, it boots fine

but the touchscreen does not respond in any way. cant even get past the first setup screen...

EDIT: I flashed the toybox/temp_touch fix (attached) and got touchscreen functionalilty
[7" Kindle Fire HD Android Development] alexander_32:
I just needed to check if compiling works with transi's github repositories, so nothing new (except the version of Android - MOB30M). Does Camera work in this build?
[7" Kindle Fire HD Android Development] mikeataol:
Nope...
[7" Kindle Fire HD Android Development] alexander_32:
Ok, thanks for letting me know. Hopefully, transi will fix it in the future. And I will bring new CM MM based ROMs in the near future.
[7" Kindle Fire HD Android Development] RogUK:
Worked for me from stock Amazon android, now running 6.0.1. Was only using it as a Kindle ebook reader, but lots more options now.

Thanks
[7" Kindle Fire HD Android Development] alexander_32:
Quick Fix for camera:

http://xdaforums.com/kindle-fire-hd/7-development/cm13-quick-camera-fix-t3421847
[7" Kindle Fire HD Android Development] alexander_32:
NEW BUILD (MOB30Z) with 3.0.72+ kernel.

https://www.androidfilehost.com/?fid=24591000424960031

Installation: full wipe / flash ROM + GApps / wipe cache + dalvik cache.
[7" Kindle Fire HD Android Development] skalnas:
Thanks very much for this build! I was having problems with earlier and different versions of cm13 with the wifi not connecting automatically. However, it is working normally with this build.
[7" Kindle Fire HD Android Development] :
I made a few changes to the wifi scan interval settings that might trigger reconnects more often, as a workaround for issues caused by the old bcmdhd firmware. Thanks for the feedback.
[7" Kindle Fire HD Android Development] ipdev:
Working for me.

update-kindle-7.5.1_user_5174320

kfhd7-u-boot-prod-7.2.3

kfhd7-twrp-3.0.2-3-recovery

kfhd7-freedom-boot-7.4.6

cm-13.0-20160827-UNOFFICIAL-tate

open_gapps-arm-6.0-pico-20160828

BETA-SuperSU-v2.77-20160827190633
[7" Kindle Fire HD Android Development] alexander_32:
Wait, you're successfully using latest CM 13 build with flashed SuperSU?
[7" Kindle Fire HD Android Development] ipdev:
:confused: Is SuperSU a problem?

I've been installing it on everything for quite a while, some devices require help but most just flash the zip without problem. (I apologize for a double post.)

I've been away from these too long. :eek: (tate and jem)

Just updated stock fireOS to the most current on both and re-rooted.

Both now seem to run fine.

Red recovery logo is a great idea, and looks sharp..

tate

update-kindle-7.5.1_user_5174320

kfhd7-u-boot-prod-7.2.3

kfhd7-twrp-3.0.2-3-recovery

kfhd7-freedom-boot-7.4.6

cm-13.0-20160827-UNOFFICIAL-tate

open_gapps-arm-6.0-pico-20160828

BETA-SuperSU-v2.77-20160827190633

jem

update-kindle-8.5.1_user_5159720

kfhd8-u-boot-prod-8.1.4

kfhd8-twrp-3.0.2-2-recovery

kfhd8-freedom-boot-8.4.6

cm-13.0-20160827-UNOFFICIAL-jem

open_gapps-arm-6.0-pico-20160828

BETA-SuperSU-v2.77-2016082719633
[7" Kindle Fire HD Android Development] alexander_32:
Thank you for your feedback. In the past, flashing SuperSU caused bootloop.
[7" Kindle Fire HD Android Development] :
It still will, because by default it installs as systemless which patches boot which isn't supported here. You need to either echo SYSTEMLESS=false into the /data/.supersu config file or use a forced system mode installer like the one here.
[7" Kindle Fire HD Android Development] alexander_32:
Thanks for link, but I don't really need SuperSU.
[7" Kindle Fire HD Android Development] Droidriven:
I haven't updated the stock on my KFHD7 2012 even once since I got it, its still on the first stock version. I haven't flashed anything much on it in over two years. Can you link to me to the files and threads you updated to latest and rerooted with?
[7" Kindle Fire HD Android Development] :
If you aren't already using a custom rom/recovery on it, then just follow the steps here.

Get the latest twrp build here and the newest cm13 build here.

After the rom, flash an arm 6.0 gapps package from here (preferably a smaller one, but if using stock package, exclude enough that it'll fit on the system partition with a .gapps-config file like this).

You should probably use the built in root superuser in cm13, but if you prefer supersu, use the installer from here.

And that's it.
[7" Kindle Fire HD Android Development] Droidriven:
I already have CM13 and newest TWRP.

You missed my point, I have the custom stuff flashed over the first stock firmware build, I was asking about what you used when you updated stock and re-rooted, I'd like to update the stock OS then root and flash recovery/ROM. If I just wanted recovery and CM13 I'd leave it the way it is.

I'll do some searching, I just wanted to narrow what I will be chasing.
[7" Kindle Fire HD Android Development] :
Unless you're implying that you're reverting to stock, what would be the point of flashing the newest stock firmware only to flash a custom rom afterwards? There are no special partitions like modem that would be updated. System would just be overwritten making it a waste of time.
[7" Kindle Fire HD Android Development] Droidriven:
I won't do it then, I thought there might be updates in there somewhere, I don't follow the stock versions, seems like there would have been some patches and improvements in stock along the way, oh well.
[7" Kindle Fire HD Android Development] :
I would suggest you do some searching as to how android actually works. Custom roms include the device vendor's files; they don't work by using a pre-installed stock rom as a base. The bootloader is also purposely kept as an older version as I've heard the exploit to allow loading the second bootloader may have been patched in more recent versions. For these kindles, there is no special partition that would benefit from flashing a newer stock rom beforehand.
[7" Kindle Fire HD Android Development] Droidriven:
Lol, I know how android works, you didn't get what I said, but thanks for trying to tell me something that you thought I didn't understand.

Who said anything about a custom ROM being based on stock in any kind of way?

If you know android so well then you also know that when you flash a custom ROM, that ROM isn't the only software on the device, there is still stock stuff(bootloader, modem, etc..) that the custom system is flashed on, it is that stock stuff that remains after flashing that I assumed would have been updated in stock somewhere along the way, hence the thought of updating the underlying stock then reflashing custom. I guess you just didn't understand and assumed I was just another idiot.

There is nothing for you to "teach" me or take me "to school" on. I just haven't followed anything about this device in a very long time, it sits in a drawer forgotten about and doesn't get used, I do like keeping all my devices up to date when I can, even if they aren't being used.
[7" Kindle Fire HD Android Development] :
I call "stuff" partitions. System happens to be one of them.

Recognizing your shortcomings is key to being able to learn. You can have the last word/rant. I'm done replying to you.
[7" Kindle Fire HD Android Development] Droidriven:
And your point is?

"Stuff" meant whatever partitions may have been updated, "stuff" was used instead of specific partition names because updates may have applied to one or more partitions or not, the updated partitions would have been the "stuff" I was referring to and the partitions that weren't updated would have not been the "stuff" I was talking about, "stuff" meant any unnamed piece or part that might have been updated.

Get it?

I've been here a long time dude and I've seen many like you come and go. Mind your own shortcomings because when it comes to this community and everything to learn here, I'm fine and will continue to be that way, I teach as much (or more) as I learn here. Learn who you're actually talking to before you try to astound them with something that you think you know over them and you'll avoid showing your own shortcomings.

And I didn't rant, I merely stated that you misunderstood and assumed I was a fool that you had to explain something to when I'm not, which is exactly what happened. No big deal, just letting you know you were way off base, no need to be offended by it.
[7" Kindle Fire HD Android Development] ipdev:
[MENTION=6677866]alexander_32[/MENTION] [MENTION=6322935]r3t3ch[/MENTION] [MENTION=5691352]Droidriven[/MENTION]

I apologize for the delay, I got caught up in other threads and devices. :silly:

First off let me mention I am not r3t3ch.

r3t3ch responded to posts quoted to me and I have absolutely no problem with that. ;)

I just wanted to make it clear I do not agree with all responses relating to my original quoted posts.

To alexander_32.

My dumb. I forgot about that. :silly:

(Haven't had that problem for some time.) I forced SuperSU into system install instead of systemless. (Skips boot image patcher.)

To r3t3ch.

I jump between devices and roms. Some support systemless, others do not. I force system or systemless install of SuperSU if needed depending on the device and rom.

echo "SYSTEMLESS=false>>/data/.supersu"

Seems to work the best for me.

To Droidriven.

update-kindle-7.5.1_user_5174320

https://www.amazon.com/gp/help/customer/display.html?nodeId=201016350

kfhd7-u-boot-prod-7.2.3

kfhd7-freedom-boot-7.4.6

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

kfhd7-twrp-3.0.2-3-recovery

http://xdaforums.com/showpost.php?p=68383208&postcount=30

cm-13.0-20160827-UNOFFICIAL-tate

http://xdaforums.com/showpost.php?p=68388886&postcount=150

open_gapps-arm-6.0-pico-20160828

http://opengapps.org

BETA-SuperSU-v2.77-20160827190633

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

I just restored my secondary tate to my older fireOS. (Now charging.)

I'll update and root it tomorrow. I will post the steps used and, if I can get, the update log.
[7" Kindle Fire HD Android Development] crazynapkinman:
what kernel are people using for cm13 on KFHD7, if any custom ones at all that are compatible?
[7" Kindle Fire HD Android Development] crazynapkinman:
Also, i flashed supersu (latest beta) and got bootlooped. Idk but after flashing all the custom bootloader and twrp and cm13 (without wiping) i was able to obtain root with cm superuser (whereas before root wasnt installed properly according to root checker app)

Just relaying my experience with flashing supersu on the kfhd7.
[7" Kindle Fire HD Android Development] alexander_32:
NEW BUILD (MOB31E)

https://www.androidfilehost.com/?fid=24591000424964049

Installation: Full wipe/flash ROM + Open GApps

SUPERSU INSTALLATION
[7" Kindle Fire HD Android Development] skalnas:
Softbricked on cm13

Hope this is the right thread. I had been using the prior build of cm13 on my kindle fire hd(tate). I dl and installed yesterdays version. Upgrade went fine, but I didnt have root access. In the past I had to flash su with cm 13, I had used supersu 2.78 system mode zip I had found on xda.. I couldnt find that and flashed 2.77 beta in twrp. Problem is that installed in system less mode and patched something and now I am softbricked and cannot get into recovery. I do have a twrp backup. I just get the orange kindle fire logo which keeps rebooting. Looks like I need to reflash the recovery in twrp. I tried to do so via adb using my fastboot cable. However, I cannot get the device to be recognized in win8.1 64 bit. Nothing shows up under adb devices. Device manager shows android adb devices. When I try switching driver to composite adb interface

windows give an error windows found software for your device but encountered an error(device cannot start)code 10. I tried reinstalling adb and fastboot drivers. Anyone have any suggestions to get adb to work with fastboot so I can reflash the recovery.
[7" Kindle Fire HD Android Development] :
First of all, system mode supersu is here (you could also just have used the .supersu config file). I wish [MENTION=6677866]alexander_32[/MENTION] would just post that link with the rom link so people would stop softbricking for the umpteenth time.

Second, you obviously have a driver problem. ADB ≠ fastboot so your question isn't exactly valid, but you probably have both installed fine either way. You need to clear all android device usb drivers you have installed and reinstall the kindle driver (or this), then select composite interface from device manager. If you have many devices and install all their drivers, usually this becomes a mess.
[7" Kindle Fire HD Android Development] alexander_32:
Unfortunately, I can't edit [MENTION=6751354]transi1[/MENTION] threads. But I'll add the link everywhere I can.

---------- Post added at 06:38 PM ---------- Previous post was at 05:47 PM ----------

SUPERSU INSTALLATION
[7" Kindle Fire HD Android Development] skalnas:
Thanks r3t3ch!

Just realized what I was doing wrong. After reading your reply I realized I was not issuing the fastboot commands from adb. Turns out reflashing the boot.img from the latest cm13 got me up and running again! All this because I wasn't careful enough and downloaded the wrong supersu zip,

won't make that mistake again!

Alexander, I am wondering if it will be necessary to flash gapps and supersu after dirty flashing/upgrading versions? After I updated to yesterdays version I had to reinstall gapps

and did not have root access, so I was attempting to reflash supersu as I had done with the prior build. Don't remember having to do that in cm 11 and cm 12, typically had just wiped dalvik and cache between updated builds. Thanks
[7" Kindle Fire HD Android Development] :
I think the kindle cm update script tends to wipe system before writing to it, so reflashing every additional system modification is probably necessary. Also gapps for each version of android differ a good deal. It may be necessary to reapply whatever patches are necessary to get certain gapps to run correctly.
[7" Kindle Fire HD Android Development] alexander_32:
As I remember, you are flashing GApps and SuperSU once (at the beginning), then you just flashing updated ROM versions and that's all. Personally, I've never tried to update my BeanStalk by dirty flashing (it was always a full wipe), but I did it a lot of times with CM12.1 based ROMs.
[7" Kindle Fire HD Android Development] skalnas:
Yes, when flashed gapps and cm 13 together, as well as su zip initially when installing cm13(clean install) from cm11. No problem doing it each dirty flash, was just curious.
[7" Kindle Fire HD Android Development] GhostCode64:
Do you think you will do Cm14 when it comes out? I really want to use Android 7.0
[7" Kindle Fire HD Android Development] :
Overclock Mod

I patched in the OMAP4460 overclocking from this kernel and it is working well so far. Read more about kindle overclocking experiences here. By default it still runs at stock speed; you need to use kernel aduitor to configure the CPU settings. I am personally using 1632Mhz as max cpu freq with interactive governor and hispeed_freq tuned to 1500Mhz and haven't run into any issues so far.

WARNING

: Not many kindles can go to 1747Mhz and be stable. If you want to try it, disable apply on boot, switch to performance governor, and select 1747 as the max cpu freq. If the system freezes, simply hard power cycle by holding the power button, you cannot go that high. As always, you do everything at your own risk.

[Download here] (flash from twrp, Install > Install Image > select boot)
[Galaxy S II Q&A, Help & Troubleshooting] 74n4705:
Soo... I have a S2 and S3. I use the S2, today I woke up for my phone freezing on Samsung Logo. I tried booting Recovery, froze on Team Win logo, so I guessed that something is the software went wrong. I decided to flash some Recovery from Odin and boot into Recovery. I Googled, downloaded one recovery, flashed it via Odin, didn't work, tried another one, didn't work, I would put out the battery every time between tries. And boom it wont turn on, only gets warm in the camera region. So I tried all the combinations of putting it the power with and without battery, pushing all the button combinations etc. I told myself I'll deal with it later, need a phone right now. So I used a spare phone my brother game me, an S3. It had a stock ROM and I wanted to flash JB on it. I rooted the S3, downloaded TWRP for Odin, flashed it with Odin, it didn't work, it booted me to a stock recovery, so I rebooted the phone, it went to Samsung logo, I removed the battery to go faster to Download Mode and try something else, and it wont turn on. What happened and what can I do to fix that? I really need a phone for tomorrow. Please help.
[8.9" Kindle Fire HD Android Development] transi1:
LS unofficial builds for the JEM

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.

download:

new: https://www.mediafire.com/folder/iiuqc32f8z6ce/jem

old: https://www.mediafire.com/folder/5olnizsgh2jz5/jem

old: https://www.mediafire.com/folder/dtsa7p6v17436/jem

backup before flash, gapps need for upgrade, don`t flash SuperSU

http://opengapps.org/ (arm, 6.0)

Kernel auditor - Low memory killer - Very aggressive

If you install Gapps after the ROM has been booted for the first time you either need to wipe data and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.

bluetooth lte-version fix: https://xdaforums.com/kindle-fire-hd/8-9-inch-help/kindle-fire-hd-8-9-bluetooth-rom-t3315904
[8.9" Kindle Fire HD Android Development] jaramosp:
Great news!!
[8.9" Kindle Fire HD Android Development] transi1:
build 20160215 (backup before flash, gaaps need for upgrade): http://www.mediafire.com/download/njvq7ur336ca9rm/cm-13.0-20160215-UNOFFICIAL-jem.zip
[8.9" Kindle Fire HD Android Development] monster1612:
Transi, you are brilliant!! All we need now is TWRP 3.0.0 (and maybe official CM13 nightlies ;)), and we're halfway there. :D
[8.9" Kindle Fire HD Android Development] The_GreaseMan:
Thanks for this rom , I am having an error though that I need some help with. All the info first

Kindle fire HD 8.9- Rooted by following the cm kindle fire HD 8.9 wiki

Installed Recovery TWRP 2.8.7.0, device was wiped and internal storage formatted before each of the following roms were tested

gapps were downloaded from open gapps .org, the arm mini version was used with each respective rom. gapps were installed by adding the zip file to the list of items to be installed by twrp.

ROMS installed

CM 11

CM 12

CM 13

[resurrection remix 5.6.1] [jem] [6.0.1 marshmallow]

AICP - 11.0 - M 6.0.1 jem - unofficial

On each ROM either Bluetooth turns itself on and off constantly if you attempt to turn it on or the unfortunately Bluetooth share has stopped warning will constantly pop-up until the kindle is restarted.

After going through 5 roms I figure it must something I did wrong as the Bluetooth was working with the stock rom before I rooted the kindle , any ideas on what I should try to get Bluetooth working on this?
[8.9" Kindle Fire HD Android Development] gatalon:
I think maybe something wrong with your bluetooth module, it is a hardware issue i think.
[8.9" Kindle Fire HD Android Development] monster1612:
Can you enable Bluetooth and then get a logcat? Bluetooth works fine on my jem, so you must have a hardware issue.
[8.9" Kindle Fire HD Android Development] The_GreaseMan:
Funny, I am pretty sure it was working when I was stock.

Grabbing the logcat now and will post it shortly.
[8.9" Kindle Fire HD Android Development] jaramosp:
Deep Sleep Issues fixed?
[8.9" Kindle Fire HD Android Development] transi1:
coming soon
[8.9" Kindle Fire HD Android Development] jaramosp:
o.k., thanks!! excellent work!
[8.9" Kindle Fire HD Android Development] transi1:
build 20160218 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/ivxy6e83x0sp4fr/cm-13.0-20160218-UNOFFICIAL-jem.zip

deep sleep fixed
[8.9" Kindle Fire HD Android Development] mrbender666:
cool man!

are you going to port fix on AICP ?

thank you
[8.9" Kindle Fire HD Android Development] jaramosp:
deep sleep issue fixed, thanks!! this rom is very smooth and stable. A question, cast screen worked in kitkat cm11 with mirror enabler by r3pwn, since cm12 this fix don't work., do you can enable it in this rom?
[8.9" Kindle Fire HD Android Development] airdrome_eagle:
Thank you, it's very good ROM

---------- Post added at 02:25 AM ---------- Previous post was at 02:04 AM ----------

Hey, it do not rotate screen, :(
[8.9" Kindle Fire HD Android Development] gatalon:
Like this rom, love you man, better than cm12.