yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Just to confirm you are now running CM-13, correct? Got confused with all the background detail.

---------- Post added at 09:41 AM ---------- Previous post was at 09:21 AM ----------

Sorry, you didn't follow "all the steps what Mr.ggow wrote" as prerequisites clearly state your device must have an unlocked bootloader with twrp installed. You have neither - nor is your device eligible to be unlocked. Your device was running Safestrap (presumably v4) which emulates twrp and only supports 3 roms: Nexus (two builds); CM11 and a custom build of FireOS 4.5.2. By flashing CM13 you likely destroyed the underlying environment which limits/eliminates recovery options.

Without a functioning ROM you can not 'push' files to the device or communicate with the outside world in any way. You are limited to files currently resident on the device which hopefully contains either: 1) a backup of your previous FireOS or Nexus installation; or 2) a copy of the Nexus zip that was originally used to install the rom. If you do not have or can not find either of these files/repositories then the device is unrecoverable short of main/daughter board replacement.

[MENTION=7363565]Brainlin[/MENTION] - you can not use adb to communicate with a device (or at least this device) w/o a functioning ROM. Safestrap v4 does not support MTP or any other mechanism for data exchange within the recovery environment. Nor can the device be restored via 'factory reset' from the stock recovery menu. The outcome of such an attempt is typically a permanent soft-brick.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] donharden2002:
Yes, running cm13 now.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] torus1989:
so i guess there is no even a hope to do something like this http://xdaforums.com/showpost.php?p=51175866&postcount=2 ?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Anything is possible but odds are long. The linked thread is quite old. Last updated 2 years ago, long before Safestrap v4 existed. I didn't read through the details.

I take it you are not able to boot into Safestrap recovery or do not have a flashable Nexus image or backup of your previous build.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AndyYan:
How do I compile this from source properly? I've built CM13 for other devices, but have never come across Bitbucket-hosted sources. I've set up my roomservice.xml to look like this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="bitbucket"
fetch="https://bitbucket.org/" />
...
<project name="Kindle-Fire-HDX/android_kernel_amazon_hdx-common" path="kernel/amazon/hdx-common" remote="bitbucket" />
<project name="Kindle-Fire-HDX/android_device_amazon_hdx-common" path="device/amazon/hdx-common" remote="bitbucket" />
<project name="Kindle-Fire-HDX/android_device_amazon_thor" path="device/amazon/thor" remote="bitbucket" />
<project name="TheMuppets/proprietary_vendor_amazon" path="vendor/amazon" remote="github" revision="cm-13.0" />
</manifest>

...but repo sync tells me "fatal: Couldn't find remote ref refs/heads/cm-13.0" and breakfast tells me "Default revision cm-13.0 not found in android_device_amazon_thor. Bailing. Branches found: cm-12.1". It seems there's no cm-13.0 branch - how would I deal with this?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] jeffersonx:
is a safestrap version of this rom planed or are there any technical restictions for this?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Seems unlikely as Safestrap utilizes the stock kernel which remains KitKat based. Kernel can not be changed on a device with a locked bootloader.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] klofisch:
Hello,

i installed the current version. It seems ok,...but i see the boot animation since 5 minutes? Whats the matter?

...Peter
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Did you do factory reset in TWRP, if you didn't you need to
[Kindle Fire HDX 7" & 8.9" Original Android Develop] klofisch:
i had followed your instructions and did the reset before installing CM12. I am using TWRP 2.8.7.0 and i have an Apollo.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I made a new build on the 29th March, however screen rotation does not work now on either my apollo or thor device. I can release it if you would like it. If not I'll debug it first and then release.

EDIT: I downgraded back to the 19th Feb release and screen rotation started working again - I guess something has changed or is broken in the CM repositories.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] klofisch:
its not about rotation,.... it just doesnt get over boot animation :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- Post #331 was not directed at you specifically.

- I don't know what might be causing that if you have done a factory reset.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] n1cklan:
When will be next update?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- See Post #331

- Please read at least the last few posts before asking questions - Thanks
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
which gapps package did you flash?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] klofisch:
i tried without,...same thing,....and also with CM12

------------

after 3min CM12 started

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

and now,...also CM13 works, after a dirty flash from CM12. Gapps not installed yet. really strange
[Kindle Fire HDX 7" & 8.9" Original Android Develop] rurika:
Hi, the rom work great but I have an issue with screen rotation.

Tried flash http://xdaforums.com/kindle-fire-hdx/development/twrp-flashable-3-2-3-bootloader-upgrade-t3025504 and enable rotation on launcher setting still not help.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I'm looking into this at the moment.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AndyYan:
[MENTION=5749760]ggow[/MENTION] Post #325, please?

If you don't want me to build using your sources, just put it straight, I'll back off from it (and from buying the device).

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- Calm down, I'm extremely busy right now.

- Also have a lot of stressful stuff going on in real life

- When did I say I didn't want you to build using the sources in the OP?

- Everything you need is on the OP.

- You don't even need to fiddle with roomservice.xml

- Just sync the individual repositories then...

- Generate the vendor tree using the extract-files script with the proprietary-files.txt in the device tree and build - that's it.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] rurika:
Yes, finally. After I try to flash several times and now the rotation works!!!! I don't know if it gonna help but this is the way that work for me.

Before flash this ROM make sure that you not lock the screen rotation. (Mine was locked before flash this ROM so I unlock rotation and flash this ROM). After reboot. The first thing I do is enable rotation on launcher setting.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I'll try that, thanks, but still need to find out why it works ok for me in the build on the OP, but not at all on the new build I'm working on.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] klofisch:
[MENTION=5749760]ggow[/MENTION]. U do great.

---------- Post added at 04:38 PM ---------- Previous post was at 04:31 PM ----------

about the screen rotation issue. i had my cm13 running finally, without gapps. The screen was allways in potrait-mode. Then i went to twrp did a factory reset, flashed gapps (20160331) and supersu 2.42,...and cleared the dalvik cache. After booting again,screen rotation is working. There is might be something messed up in the initial configuration.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AndyYan:
I was in too much of a hurry, sorry...

The thing is, I don't have the device yet, so I can't extract the proprietary files from the device, so I'm using TheMuppets for that purpose.

Also, the error here points to android_device_amazon_thor. It says it doesn't have a cm-13.0 branch to build from.

Will see if syncing manually via git clone helps.

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
You can extract the files from the Amazon stock firmware:

Unzip the stock Amazon 4.5.5.1 firmware and run the extract-files script against the system folder path so you don't need the device to extract the files

For the repositories just sync the master. There are no other branches.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Seems the rotation issues are more widespread. There are some Samsung devices and the one plus one that have or are experiencing the issue.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AndyYan:
Thanks for the tip.

I did write roomservice.xml so that it syncs the entire branch instead of cm-13.0 (usually I only sync cm-13.0 to save bandwidth), because I observed the repo beforehand and didn't find cm-13.0 there.

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Let me know when you've managed to build it.

I'm looking into what's happened in the CM repos to stop sensors from working.

Be interesting to see if your experience is the same.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AndyYan:
Well, just got news... I verified that the device my friend purchased for me is not unlocked (it has Safestrap but the seller tricked my friend into believing it's proper TWRP), so I'll have to have him return it, which also means I won't be building this. Thanks for helping nonetheless.

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Oh that's a shame, let me know if you manage to get a device and we can continue the setup you of your build environment.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AwlsomeAlex:
Hey [MENTION=5749760]ggow[/MENTION], how do you unlock the Bootloader of a Kindle Fire HDX 7"? I've been searching but I can't really trust anyone (I have root capabilities) also, do you think FlashFire will work as an alternative to TWRP? (If not how do you flash TWRP?) Thanks, I really wanna update this outdated tech.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Hello,

See here
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AwlsomeAlex:
Okay [MENTION=5749760]ggow[/MENTION], but it says 8.9", will it still work with 7"? (Also is there a one-click option?) Finally, what about FlashFire, would that work or does TWRP need to be flashed?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
The unlock procedure will work with the 7"

To run CM-13.0 you need an unlocked bootloader.

Just using FlashFire will not be enough
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AwlsomeAlex:
Okay thanks [MENTION=5749760]ggow[/MENTION] . One more question, how do you flash TWRP? Is there an app I can use once the Bootloader is unlocked?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
You can use Flashify
[Kindle Fire HDX 7" & 8.9" Original Android Develop] AwlsomeAlex:
Okay, thanks. I'll give this firmware a try once I get home and install drivers.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] mmidders:
Any luck with the sensor issue?

I've just acquired an HDX 8.9 3rd gen, rooted, unlocked bootloader, TWRPd and installed your ROM (Thanks!) and I'd like to offer my help with anything you might need, especially fixing the sensors as I'm itching to play GOF2 HD on this crispy display.

I've been a programmer since I taught myself BASIC at age 11 (quite some time ago now!) and I might be a little rusty through lack of practice over the last few years, but I have a fair amount of free time and would be happy to catch up on the latest tech.

Slàinte

mmidders
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I'm going to spend some time looking into it this evening. I've just sync the repos to today's current and rebuilding.

Are you seeing the sensor issues with the build on the OP?

That one seems to work fine for me.

Any help would be appreciated, everything required to build cm13 is on the OP :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] mmidders:
Thanks for the response, I'll get back to you when I've built my dev environment; I trashed my last linux install when I DBANd my system. :)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] Koetermann:
Hi ggow,

today I finally unlocked the bootloader on my thor, so I was able to install your CM13 ROM. Thanks for your work.:good:

As far as I see everything works. Just one thing I don't understand:

I can activate Bluetooth, but the Kindle thor will not pair do any other device. Tried it with my Smartphone N5x and my Bose Soundlink Mini. With the Bose it's very strange: Everytime when I try do pair I get an error message like wrong code. But the Bose Soundlink doesn't need a code to pair.

Any ideas how I can get BT to pair to other devices especially to the Bose Soundlink Mini? Has anyone the same issue?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Could you send me some logcat of trying to connect to bluetooth devices?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] mmidders:
Yes, have no sensors at all using the build from the OP. Have just double-checked by reinstalling with MD5 check. Checked that it wasn't my device by reverting to Fire OS and the sensors are all working there.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
With the build on the OP, for me sensors are working fine. So there is a problem for some devices for sure. Haven't been able to narrow down what the issue is yet.

With the latest build I'm working on no sensors at all. If I load the build from the OP again then sensor functionality is all good again.

I'm now wondering if I'm leading myself up the garden path with this.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
If iam right there are different versions of HDX 7/8.

If we could clear which versions have the sensor problem we may come closer to a solution.

I have a HDX 7 Wifi only 32GB, Sensors not working (was working with other firmware)

Maybe the Version in witch the Sensors work is the LTE Version due to different Hardware...

I don't think that the flash size matters (in Terms of different Hardware) but maybe there are different sensors in the LTE Version....

Just saying...
[Kindle Fire HDX 7" & 8.9" Original Android Develop] state00000:
:good:

HDX 7 Wifi 16GB

Sensors not working
[Kindle Fire HDX 7" & 8.9" Original Android Develop] itsmeinarizona:
HDX 7 Wifi 16GB

Sensors working (tested using Sensor Kenetics app)

13.0-20150225-UNOFFICIAL-thor

3.4.0-perf-gd928a96 (Feb 5 2016)
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
Thanks for your reply

Its about those Versions:

cm-13.0-20160219-UNOFFICIAL-thor.zip

cm-13.0-20160219-UNOFFICIAL-apollo.zip

Thank you.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
I'll do another release this by tomorrow evening. I'll keep the links to the previous release alive in tandem.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] travanx:
Does anyone else get random lag/pauses? I cleared dalvik cache and it helped a lot, but there is still some type of lag when doing things. Enough that I just order a Shield K1. I want to use the HDX with CM13 as a device that I can control the house with, so lag isn't very other person friendly. I am on the latest rom posted by OP.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
New Build is Up

- Test Release Dated 14 April 2016

- Updated kernel with latest from CAF branch LA.BF.1.1.3-01210-8x74.0

- Fixed "Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat" error

- Sensors not working after syncing sources - in progress...

- On the OP there are links to the February Release and the new Test Release

- Let me know if Sensors are working for you on the Test Release - I'm guessing that they won't be working.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Can't comment on the latest CM13 builds but 'lag' and HDX are two terms one doesn't often see together. While the Snapdragon 800/Adreno 330 combo is a couple generations back it does an admirable job on Thor (7") devices and likely most Apollos outside intense gaming. I happen to run Nexus (buttery smooth) but saw no performance issues w/CM11 or CM12.1. Might want to dig a little deeper to make sure a rogue app isn't causing the behaviors.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] schr01:
The sensor is not working on my flashed test relaese dated 14 april 2016.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
Were the sensors working on the February build?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] schr01:
Yes, the sensors are working on my flashed February build?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
OK, thanks that's the same for me.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] travanx:
That's what I thought. This rom works so well that I will take the little bit of issue I am having over wiping the device yet again. Its a perfect remote for iRule.

Any suggestions on how to find a rogue app?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] :
What´s your Hardware?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Standard android investigative work. Get yourself a task manager/viewer, cpu monitor and/or battery monitor. See what's sitting in memory, burning CPU (especially background task), possibly read/writing to storage or swapping which can introduce lags. Guessing there's a pig with dirty trotters in your app mix.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
FYI - there may be a hw component to the wifi issue as this behavior has been reported at some point on almost every HDX rom including FireOS. It was a significant problem on FireOS v3 prior to 3.2.4; believe 3.2.6 cured most (albeit not all) occurrences. Still happens to me on rare occations; running Nexus v4 (unlocked thor). Almost always requires a reboot.

Love the positive reports coming in on CM13. Looking forward to giving it a whirl!
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
New Build is Up

- Dated 04 Dec 2015

- Change log on Post #2

- Factory Reset will be required for this release

- Cameras are working but need a good testing

- HDR probably isn't working

- Next I'll try and get Bluetooth working

- Project Status Table Updated
[Kindle Fire HDX 7" & 8.9" Original Android Develop] andPS2:
i dont think it is hardware related since it worked on CM 12.1...

now i have a bigger problem though i am stuck in a boot loop (that is in the version

without the camera fix)

have to read guides what to do...

p.s. vol + and power does not boot into recovery

the cm 13 image boots though after a while it reboots

p.s.s. ok fastboot is working still
[Kindle Fire HDX 7" & 8.9" Original Android Develop] andPS2:
now i am really screwed it seems

i cant get adb devices or fastboot devices to recognize the hdx

tried under windows on two computers (with getting adb drivers)

and under linux (where it used to work with android 5)

maybe android 6 issue?

my recovery seems to be messed up as i cant boot into it

sometimes i have like 30 seconds in the image so should i try a factory reset?

or is that even more dangerous?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- The first step is to get TWRP working, if fastboot is working you should be able to reload TWRP.

- Once TWRP is working, do a factory reset in TWRP and reboot
[Kindle Fire HDX 7" & 8.9" Original Android Develop] andPS2:
i got fastboot to work under ubuntu with

fastboot -i 0x1949

but adb doesnt work so how can i push the thor recovery image to the device?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- If you have an unlocked bootloader - do the following

- Download TWRP 2.8.7.0 from here

- Then type the following:

sudo fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img
[Kindle Fire HDX 7" & 8.9" Original Android Develop] andPS2:
i did reflash the recovery however i cant seem to get into it

neither by power & + nor by long press power button and reboot recovery

output:

fastboot -i 0x1949 flash recovery signed-thor-twrp-2870.img

target reported max download size of 536870912 bytes

sending 'recovery' (9220 KB)...

OKAY [ 0.368s]

writing 'recovery'...

OKAY [ 0.681s]

finished. total time: 1.049s

i now shows the kindle fire logo goes black shows the logo again

ocassionaly i can get into my cm13 which reboots pretty fast

(no time for factory reset under settings)

there is no fastboot reboot recovery command

p.s. can i flash this back to stock with fastboot somehow?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] DB126:
Sorry, should have clarified the WiFi issue you describe has been seen previously. Appears to be a characteristic of the hardware components (not your specific device) vs a flaw in CM13. That said, some tuning or use of different binaries may be possible to reduce the frequency.

I realize you are wrestling with a more serious problem; hope that works out.
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- I would NOT attempt to factory reset from the OS

- Is something wrong with your volume + button, maybe that's the reason you can't access recovery?

try this to get into recovery:

- Power up the tablet in fastboot mode and type the following to boot the recovery:

sudo fastboot -i 0x1949 boot signed-thor-twrp-2870.img
[Kindle Fire HDX 7" & 8.9" Original Android Develop] andPS2:
---------- Post added at 03:12 PM ---------- Previous post was at 03:08 PM ----------

[/COLOR]

it only shows a black screen just like when using the buttons

i dont think the button is broken either

bootloader is unlocked

p.s. its mounting all kinds of partitions though on ubuntu desktop

output:

fastboot -i 0x1949 boot signed-thor-twrp-2870.img

downloading 'boot.img'...

OKAY [ 0.311s]

booting...

OKAY [ 0.068s]

finished. total time: 0.380s
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
on the blackscreen:

- can you access adb?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] andPS2:
unfortunately not

but i see partitions on ubuntu desktop

like 13 gb which is the whole device one with blowfush.sh and many more
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- ok, that is strange that the recovery boots to a black screen

- what events led to this?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- That does not sound good - sounds like a hardware fault of some kind
[Kindle Fire HDX 7" & 8.9" Original Android Develop] andPS2:
well i rebooted the device pretty often cause of this wlan bug

then yest i left it out with like 70% battery

this morning it was empty and in this loop

might be a hardware fault since my normal cm 13 image boots

but then after a while reboots

sometimes it freezes sometimes minor graphic errors

can i try another recovery?

p.s. bbl
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
trying to find the stock recovery image for thor
[Kindle Fire HDX 7" & 8.9" Original Android Develop] andPS2:
i kinda wanna try erase system so the cm logo disappears in case

i send it back... ;)

p.s. careful as i am i found stock recovery which i did before installing

twrp

i have Linux 3.4.0-gb86c9c5-07481-g3790b10.img and Not recognized Recovery-Version.img

(13.3.1.0)

and boot.img + recovery.img ( 13.3.2.4)

which one should i flash just the recovery.img from 13.3.2.4?
[Kindle Fire HDX 7" & 8.9" Original Android Develop] ggow:
- Yes flash the one from 13.3.2.4, that will be fine

- And yes fastboot erase system partition

- If you do get into stock recovery then also perform a factory reset

- Could you send me the thor 13.3.2.4 stock recovery image?