yashsingh1/xdaforums huggingface dataset:
[Fire HD 6 and 7 Original Android Development] oneballnoa:
Alright thank you for everyones ideas so far. I've been trying to run King Root over and over again for the last week because at first it kept failing at 30% but then once it got to 55% so I kept switching internet sources and trying in different places because I thought it might be failing due to the connections. This morning I tried it again in my house and miraculously it worked. So not I have working root which is great.

My next step was to download TWP the openrecovery 2.8.6 ariel img that was linked above. I flashed it via flashify after granting root and it flashed well. I then rebooted and tried to get into recovery, but it just brings up the amazon logo, tries to get into recovery, fails, then brings up the amazon logo again and boots up regularly.

I then figured I would try to install recovery a different way, so I downloaded TWRP manager but I don't see any Kindle devices except the old Kindle Fire otter device. I don't see ariel anywhere.

I also tried rebooting to recovery with the adb command from my computer but it does the same thing. It tries to get into recovery but never quite gets there and then reboots.

Thanks for your help so far though, the KingRoot was a great idea and at least now I have root which is nice for lucky patcher and things like that. At this point I might just take it the way it is for now, but my main problem is being unable to flash a GAPPS package since I can't get into recovery. If anyone has any further ideas let me know, but thanks for helping me get this far.
[Fire HD 6 and 7 Original Android Development] rlattin24:
Here's how I installed TWRP

Download a Terminal Emulator, I sideloaded Rom Toolbox Lite because the offerings on Amazon App Store aren't that great

https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en

https://drive.google.com/file/d/0B1StTqIkqpWcRVpqT1dndmdjeTQ/view?usp=sharing

I uploaded it to my drive if you're unable to get it from Play Store.

Open Rom Toolbox Lite and go into Root Browser and find openrecovery-twrp-2.8.6.0-ariel.img

Move openrecovery-twrp-2.8.6.0-ariel.img to the Sdcard directory on your Fire HD and rename it to recovery.img

Now open Rom Toolbox Lite and open Terminal Emulator and enter the following

su

cd sdcard

dd if=recovery.img of=/dev/block/mmcblk0p7

close and open a new terminal emulator window

su

reboot recovery
[Fire HD 6 and 7 Original Android Development] oneballnoa:
Tried this word for word. Every command was accepted. After I issued the last reboot recovery command I crossed my fingers but the same thing happened. The amazon logo is shown then the screen goes black (as if it should go bring up the TWRP touch layout), but then nothing happens and the Amazon logo comes back up and then proceeds to boot normally. I'm starting to think that when I followed.... http://xdaforums.com/showpost.php?p=62011272&postcount=2 I must have screwed something major up.

That page shows this ...."A bit of background. Fire HD boots TEE1 -> UBOOT -> recovery. With 4.5.3, we lucked out that TEE1 & UBOOT accepted unsigned recovery (aka TWRP). No such luck with 5.2.x - TEE1 & UBOOT expect signed recovery (for example, stock one). That's why I had everybody overwrite TWRP with stock recovery in post #1 as the last step in the upgrade. Otherwise after the upgrade to 5.2.x, TWRP would still be sitting in recovery, and being unsigned, it cannot boot !!! A few bricks were created because of this last point. But with the stock 5.2.0 recovery (which it will boot), at least there is an option to sideload another update file.

So, the key to running TWRP while in 5.2.x is to overwrite the 3 key components together (TEE1, UBOOT, recovery), and then return things to 5.2.x once TWRP is no longer needed."

So I think one of the commands I ran must have permanently changed the structure of the TEE1 or UBOOT that they are talking about. But I'm not technical enough to figure out how to reverse any of the commands in that guide.

Oh well, root and CM still beats the hell outta Amazon OS.
[Fire HD 6 and 7 Original Android Development] rlattin24:
Yeah that sucks was hoping this would work for you. I'm not very technical either and start panicking doing things like this out of fear thatt he same thing that happened to you would happen to me even with following directions.

You could try again one more time but instead of

Su

Reboot recovery

From main page of rom toolbox lite scrolling down to rebooter and selecting recovery that way.

I had a problem one time after flashing the recovery.img where it would do what you says just boots normally but after looking around it was a bad download of Twrp so I downloaded the file again and it worked.

If this doesn't work then I'm out of ideas, Sorry ?
[Fire HD 6 and 7 Original Android Development] mikeearwood:
Is anyone else having a problem with the microphone not working?
[Fire HD 6 and 7 Original Android Development] Diesen_Dev:
Yeah, same here(
[Fire HD 6 and 7 Original Android Development] mikeearwood:
Microphone

Is there any way to get the microphone to work?
[Fire HD 6 and 7 Original Android Development] Diesen_Dev:
I don't think so. Maybe in the next update(s) it'll be fixed.
[Fire HD 6 and 7 Original Android Development] Legendarybane98:
I need a custom recovery

I have the Amazon Fire Hd 6 and i rooted it but i cant get a custom recovery to install on it and i want one so that i can flash this rom on my device. can anyone help how or where can i get a working custom recovery for mine :confused:
[Fire HD 6 and 7 Original Android Development] noahajac:
Is this for the Kindle Fire HD 7 4th Gen (2014)?
[Fire HD 6 and 7 Original Android Development] Diesen_Dev:
Yes. And also for HD 6 (same hardware).
[Fire HD 6 and 7 Original Android Development] Legendarybane98:
I found a way to do it thanks everyone that replied, the rom is great can't wait till it complete
[Fire HD 6 and 7 Original Android Development] noahajac:
How did you unlock the bootloader and get TWRP on?
[Fire HD 6 and 7 Original Android Development] Legendarybane98:
Anyone tired to use Pandora on this ROM, when I try it just skips through all the song uncontrollably and when you plug in headphones there is no sound?
[Fire HD 6 and 7 Original Android Development] Diesen_Dev:
There is a problem with the headphone audio in this rom. Biggest bug for me. Didn't tried Pandora, but it sounds very very quiet in any other apps.
[Fire HD 6 and 7 Original Android Development] rlattin24:
Its the same with Slacker Radio, it just keeps skipping every song. Sadly I had to go back to Fire OS because of this :(
[Fire HD 6 and 7 Original Android Development] bluesforte:
ggow -- did you ever post your sources for this? I'd like to see what you have in the device tree so far.
[Fire HD 6 and 7 Original Android Development] JUSTINMARMER:
It's been 60 days with no development. Pretty sure this is dead now.
[Fire HD 6 and 7 Original Android Development] Surprisekitty:
Please finish this. I want to have stock Android on my device :C
[Fire HD 6 and 7 Original Android Development] ggow:
I'm not done with this yet. I purchased a new laptop with a skylake processor which I have been having issues with, its back with the retailer at the moment for diagnosis. Working out of temporary machine with limited capacity. Will continue when I get my new machine back and it's setup correctly.
[Fire HD 6 and 7 Original Android Development] scapeghost:
Thanks for your work on this tablet, ggow. I'm running your CM12 build on my 2015 Fire 7", and loving it. Looking forward to a Netflix-capable build on the 2014 HD7 so my kids can geek out on it, sans all the caveats of running a hybrid Amazon rom with GApps.
[Fire HD 6 and 7 Original Android Development] ggow:
The trouble is mediatek haven't released any information or source code relating to the mt8135 chipset which this device uses. The only reason we have the kernel source is Amazon I'm guessing is trying to stay on the right side of the GPL rules. The HAL interfaces aren't standard, which is why video playback is broken on this current build. From the looks of things frameworks/av project has had the custom treatment too. I am still looking into what can be done. I have started work on lollipop build which might yield a better result. But because the bootloader is locked testing this is long winded so may take some time.
[Fire HD 6 and 7 Original Android Development] lubaixun:
Thank you for your ROM, ggow. One question, when I use a headset, the volume is too small. How can I set it louder? Thank you!
[Fire HD 6 and 7 Original Android Development] ggow:
This is something I'm not sure about myself. When I'm up and running again I'll be looking into all of this.
[Fire HD 6 and 7 Original Android Development] lubaixun:
I found an app called SpeakerBoost. It makes the sound louder.
[Fire HD 6 and 7 Original Android Development] ggow:
Cool, that should give a clue how to fix it in the build :)
[Fire HD 6 and 7 Original Android Development] tenderchkn:
Thank you for your continued work on getting us a ROM, ggow! I hope that you are able to get all the issues worked out soon.
[Fire HD 6 and 7 Original Android Development] davigar:
Thanks ggow for the work!

Enviado desde mi SM-N910F mediante Tapatalk
[Fire HD 6 and 7 Original Android Development] ggow:
- Deleted
[Fire HD 6 and 7 Original Android Development] ggow:
FlashFire

- FlashFire appears not to be working with the HD6

- The application opens but when I press the Flash Button the screen just goes blank with backlight

- Forcing the device to reboot the device reboots into FireOS (5.1.2)

- Has anyone else had any experience of FlashFire on this device?
[Fire HD 6 and 7 Original Android Development] ggow:
I have asked Chainfire about Flashfire support here
[Fire HD 6 and 7 Original Android Development] davigar:
Thanks for your effort ggow. I continue with CM11 and it's very fast!! Thanks!!

Enviado desde mi Fire HD7 mediante Tapatalk
[Fire HD 6 and 7 Original Android Development] ggow:
I'll push another release very soon until Flash fire is working then I can try for a feature complete cm12
[Fire HD 6 and 7 Original Android Development] Remolten:
Is bluetooth likely something that can be fixed?
[Fire HD 6 and 7 Original Android Development] ggow:
At the moment, not without input from Amazon/MediaTek
[Fire HD 6 and 7 Original Android Development] spenceboy98:
Have you gotten your laptop back? Any progress?
[Fire HD 6 and 7 Original Android Development] x1xmadex1x:
This saved my tablet. Thank you very much! Waiting for the next release.
[Fire HD 6 and 7 Original Android Development] ggow:
- My laptop has again gone back for repair due to the cooling system hence the downtime.

- I'll try and get a temporary machine setup again.
[Fire HD 6 and 7 Original Android Development] CrimsonKnight13:
Your situation would have me demanding a better model from them... That's a bad cooling design.
[Fire HD 6 and 7 Original Android Development] Stoffl_:
Is the camera not working properly a CM issue or driver related like bluetooth ?

Not being able to videoskype or take snapshot is the only thing keeping me from flashing this. :D
[Fire HD 6 and 7 Original Android Development] ggow:
That's exactly what I've said to them. Or I'll have my money back to get another machine. The cooling seems adequate. I think the thermal interface paste is failing.
[Fire HD 6 and 7 Original Android Development] ggow:
New Build is Up

- Dated 12 May 2016

- Security Patches Up to and including May 2016

- Updated CM-11 Code
[Fire HD 6 and 7 Original Android Development] CrimsonKnight13:
I'll be testing it later today. Thanks!
[Fire HD 6 and 7 Original Android Development] JUSTINMARMER:
I lost root after installing this "update". I have rerooted with kingroot, but now I can't seem to replace kingroot with supersu. Did this "update" fix any of the many problems with this rom, or just security patches? Can you link to the previous release that doesn't lose root?
[Fire HD 6 and 7 Original Android Development] JUSTINMARMER:
I ended up doing a factory reset and reinstalled this rom, that seemed to fix everything the "update" broke. Still no video or bluetooth. I don't see that being fixed anytime soon since it's already been 5 months. Can someone help me get back to stock? I've tried downloading the 4.5.3 bin and changing it to zip, but I get an error in twrp that says it's not full ariel and that it's "omni" or something. Has anyone ever been able to get back to stock from this rom? Please help. Thanks.
[Fire HD 6 and 7 Original Android Development] JUSTINMARMER:
Okay, nevermind, I got it done. Went back to stock and now running FireOS 5.1.2 Blueshade with root and gapps. Everything working. Will come back to this if any further development picks up.
[Fire HD 6 and 7 Original Android Development] Mancobbler:
Do you know when Netflix and Youtube will be working? That's really the only reason I'm avoiding this
[Fire HD 6 and 7 Original Android Development] Mancobbler:
Do you know when OMX will be working?
[Fire HD 6 and 7 Original Android Development] brabe1979:
Do we think this development is still active? I would love to see if finished
[Fire HD 6 and 7 Original Android Development] spenceboy98:
I've seen the developer working on his room for the normal Amazon Fire, so I'm hoping he hasn't given up on this one. And maybe one day we'll get a cm12 or 13 rom. But I'm just being hopeful.
[Fire HD 6 and 7 Original Android Development] ggow:
Not given up. Just on hold until FlashFire is working for this device on fireos 5.x
[Fire HD 6 and 7 Original Android Development] parataxis:
CM-11 Kindle Fire HD 6"

Hi there,

Just installed CM-11 latest build on my Kindle Fire HD 6", however the headphone volume is FAR too low to even hear it that much... any suggestions? I've tried all the tricks but none of the files exist like in other CM-11 stock builds... curious if anyone knows of a solution. (also tried SpeakerBoost, which attenuates the volume for my single external speaker but alas, not headphones.)

Thank you
[Fire HD 6 and 7 Original Android Development] whackerpacker:
Video Playback

Hey guys! Thanks [MENTION=5749760]ggow[/MENTION] for the awesome CM build!

I'm still new to the forums here and I'm not a developer at all, so having XDA as a source of information has been a huge help with rooting my KFARWI. Everything works great aside from the already mentioned issues with the camera and video playback (haven't used Bluetooth).

I've been unable to watch any videos on the device since flashing CM11 but managed to find a pretty lame workaround to watch videos. If you have a Chromecast, you can stream the content directly to your TV with no error. I can't speculate why this happens, but I hope the info might be valuable to someone.

Thanks again!
[Fire HD 6 and 7 Original Android Development] crazyramen:
Did you get Netflix working with Chromecast? Whenever I tried to open the Netflix app, it stayed on the loading screen for at least 10 minutes then crashed.
[Fire HD 6 and 7 Original Android Development] kode103:
I followed the instructions properly. However, I am not able to play any Hulu/Google Play Videos at all. (in addition to the Netflix/YouTube). Anyone else run into this problem? I doubt that the installation of the Gapp 4.4 is to blame. (wanst sure if to install 6.0)
[Fire HD 6 and 7 Original Android Development] CrimsonKnight13:
Video doesn't work by default, which has been stated earlier in this thread. My daughter has discovered that Firefox will play Youtube, so maybe Netflix & Hulu might work through the browser's built-in codecs.
[Fire HD 6 and 7 Original Android Development] Skrccm:
Hi, is it possible to provide the modules in order to get nfs/cifs/samba working?

Great work, thanks!
[Fire HD 6 and 7 Original Android Development] whackerpacker:
Netflix No Worky

I haven't been able to get Netflix or Hulu to work. HBO will cast to the Chromecast with no issues as will YouTube. A strange occurrence I've come across is when viewing some pages via the Facebook app somehow allows playback of videos on the device. I think the one that works most reliably is the RT News page. Almost every link to YouTube will play directly on the Fire as long as it's streaming through the RT site. There are others that do the same thing but I can't remember them specifically. Hopefully this is relevant information to somebody..
[Fire HD 6 and 7 Original Android Development] bluesforte:
Likely is related to using software OMX vs the one from hardware. Most apps/places should use hardware, but there are probably some video types that use software. I'm looking into the OMX problems right now and think it *might* be solvable (even if 'solving' it is to use the software decoder).
[Fire HD 6 and 7 Original Android Development] ggow:
OMX

- I have been working on the OMX issues.

- The Youtube app is now mostly working

- VLC app seems to now play HD video properly too

- Netflix is still not working yet - but working on it.

- Facebook videos are still not working - but working on it.

- New build is coming shortly.
[Fire HD 6 and 7 Original Android Development] ggow:
New Build is Up

- Dated 18 Sep 2016

- Security Patches Up to and including September 2016

- Some OMX features fixed

- Youtube Fixed

- VLC now plays HD video
[Fire HD 6 and 7 Original Android Development] spenceboy98:
Nice! I'm glad you're still working on this! Maybe one day if Chainfire can get Flashfire working for our device, we can finally get an L/M/N rom? I'm not requesting one by any means, I'm just curious as to if you have any intentions of attempting one in the future.

Also, with newer Cyanogenmod's it's easier to connect a Wiimote to your device, but I haven't been able to on my Fire HD (neither stock nor this rom). The problem is that it asks for a pin to pair the device, but the wiimote does not have a pin. With newer Cyanogenmod, it just connects without a pin and is usable as an input device. Maybe this can be fixed with a newer build (unless I'm mistaken, then I apologize for asking)?
[Fire HD 6 and 7 Original Android Development] ggow:
If flashfire becomes compatible then sure I will consider making a newer CM ROM.

I'm still looking into Bluetooth, it should be possible to get it working.

I'll continue working on it. I'll state if I discontinue work on anything I'm doing. Otherwise assume it's still active.
[Fire HD 6 and 7 Original Android Development] ggow:
Might be able to get CIFS working. Will look into it before the next build
[Fire HD 6 and 7 Original Android Development] Skrccm:
Thanks for replying. I actually managed to find a different approach to the problem I was encountering, so I don't really need CIFS anymore. Don't worry about it if its not a priority.

Thanks again!
[Fire HD 6 and 7 Original Android Development] jetlego:
Hello,

I have been trying to change the maximum cpu frequency to a lower value from within both the settings and various root cpu control apps, but the frequency immediately resets to default. Is there any way to fix this, or is this impossible due to limitations of the kernel

Also, nice to see OMX finally working to some degree!
[Fire HD 6 and 7 Original Android Development] ggow:
I looked at kernel sources and yes, the frequency settings are limited due to the kernel.
[Fire HD 6 and 7 Original Android Development] whackerpacker:
NVRAM WARNING: Err = 0x01

Hey there [MENTION=5749760]ggow[/MENTION],

First of all I wanted to say thanks for the update. And second, I have a quick question regarding the WiFi. I'm getting an error NVRAM WARNING: Err = 0x01. I haven't noticed any particular problems, but I figured I'd share. Is this something you've encountered?

---------- Post added at 06:13 AM ---------- Previous post was at 06:11 AM ----------

Hey there [MENTION=5749760]ggow[/MENTION],

First of all I wanted to say thanks for the update. And second, I have a quick question regarding the WiFi. I'm getting an error NVRAM WARNING: Err = 0x01. I haven't noticed any particular problems, but I figured I'd share. Is this something you've encountered?
[Fire HD 6 and 7 Original Android Development] ggow:
Yes, that issue is on my list.
[Fire HD 6 and 7 Original Android Development] masterrer:
[MENTION=5749760]ggow[/MENTION],

On a scale from 1 to 10 how do you value the chance of solving the camera and video playback issues in this build?

And what is so different between the 2014 HD's compared to the 2015 Fire 7 for which you managed to produce a stable CM build?

Appreciate your efforts in keeping the 4th gen Fire HD community alive!
[Fire HD 6 and 7 Original Android Development] ggow:
This uses a different soc and very different structure with regard to the internals of the binaries.

The fire 7" has much more compatibility in the binaries.

Can't say on a scale but I am still unpicking it.
[Fire HD 6 and 7 Original Android Development] gascomm:
good news. after breathing life into my (long bricked) hd6 via [MENTION=4469251]powerpoint45[/MENTION] 's linux iso tool, kingroot and and this thread.

I'm guessing this OMX issue might also be impacting on the bbc iplayer and all4 apps - which do everything but play video locally (can use chromecast on both). looking forward with anticipation for these final bugs getting ironed out and the hd6 becoming the machine it's been yearning to be.

love xda, love you devs, love the hd6 rising phoenix-like from the flames of fireOS.
[Fire HD 6 and 7 Original Android Development] Diesen_Dev:
Is sound in headphones already fixed?
[Fire HD 6 and 7 Original Android Development] powerpoint45:
If anyone is interested I have put together an overview of the ROM on YouTube: [youtube]_xwEmFJKzJ0[/youtube]
[Fire HD 6 and 7 Original Android Development] ggow:
New Build is Up

- Dated 17 Oct 2016

- Ported Google's October 2016 security patches.
[Fire HD 6 and 7 Original Android Development] gascomm:
wonderful, thank you ggow. I've just flashed todays build (17/10/2016) and can report that the nvram warning in the network list has gone/fixed. i'm wondering if the omx vid issue which is affecting netflix, iplayer & xbox smartscreen etc is close to a fix? and Bluetooth? is it a known bug? anyways, thank you - I look forward to the last few bugs getting resolved & wish you and whoever else may be working on this the best of luck & good wishes.

UPDATE : oof. I seem to have lost root since wiping & flashing. supersu hasn't permission and kingroot hasn't worked after numerous root attempts. I've probably done something moronic - i'll reflash the earlier cm11 which was working fine.
[Fire HD 6 and 7 Original Android Development] ggow:
To fix root, just reflash SuperSU via TWRP.
[Fire HD 6 and 7 Original Android Development] gascomm:
well, I've flashed SuperSU-v2.78-201609011115.zip & SR1-SuperSU-v2.78-SR1-20160915123031.zip alternately with no success.

I still have working TWRP but root does appear to have been lost after upgrading the ROM. no biggy, although I will miss adaway.

I'm wondering if I may have toggled the SuperSU option to update the recovery.... could that have corrupted root?
[Fire HD 6 and 7 Original Android Development] ggow:
Try SuperSU 2.46
[Fire HD 6 and 7 Original Android Development] gascomm:
yes, that's worked after a full wipe & flash of cm11, gapps & SU.

again, cheers! im loving my transformed hd6 and am having trouble not bidding on a 16gb model. aaargh.
[Fire HD 6 and 7 Original Android Development] spenceboy98:
I got my 16 GB hd6 for 25 bucks on eBay.

The only things keeping me from using this ROM as a daily driver is Bluetooth and Netflix. Bluetooth mostly because I hate not being able to play my Gameboy games without a wiimote.
[Fire HD 6 and 7 Original Android Development] gascomm:
I hear you & agree with the desire for CM11 to get Bluetooth & OMX (?) fixed in future updates. such a lovely little device - so much more without the cr*ppy amazon OS.

god bless CM11 & all those devs working toward a fully functioning rom.

oh, I've just realised that the extended power / reboot to recovery just hangs. I'm using Restart [root] from XDA labs which does work.
[Fire HD 6 and 7 Original Android Development] steven1193:
Any word on GPS working/fix? Or is it just my fire that it doesn't work on?
[Fire HD 6 and 7 Original Android Development] ggow:
No GPS on this device