yashsingh1/xdaforums huggingface dataset:
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
You should have around 11.48 GB available storage, note that (like hard disk drives) the storage is calculated differently. The manufactures of storage devices (hdd, sdd, etc.) calculate with 1000 bytes, computer software with 1024 bytes. This leads to the problem that 16 GB are around 14.9 GB only, and around 3 GB are used for recovery, system, etc. partitions. So the 11.48 GB storage reported in device options are the maximum you can get with the standard partition size. Now you could change partition sizes in TWRP, but it's not recommended, because it can cause unpredictable problems.
[Kindle Fire HDX 7" & 8.9" Android Development] hurdubaiev:
Were the ones that got the mmc brick able to recover? Or was it a hard brick?
[Kindle Fire HDX 7" & 8.9" Android Development] Mr.Nik:
GPS does not work.
[Kindle Fire HDX 7" & 8.9" Android Development] murso74:
still dont' see it.
[Kindle Fire HDX 7" & 8.9" Android Development] jeryll:
How about now :)
[Kindle Fire HDX 7" & 8.9" Android Development] Droid_1:
See attached pic.
[Kindle Fire HDX 7" & 8.9" Android Development] murso74:
got it.. have to be on android.... can't even find that tab on a computer browser
[Kindle Fire HDX 7" & 8.9" Android Development] sherry478:
Is Bluetooth working on the latest build?
[Kindle Fire HDX 7" & 8.9" Android Development] Cpasjuste:
It should be partially working. This means it is correctly activated and we can see the device, I didn't go further. Also it will crash on deactivation but I think we can re-enable it after a few second's/minutes.
[Kindle Fire HDX 7" & 8.9" Android Development] Epedemic:
Some observations:

Flashed "stock" PA Gapps, which resulted in a zillion FC's from google play movies & tv, especially while doing the setup wizard. Maybe the DRM issue mentioned? I disabled the app and fortunately it stopped. But maybe best to stick with a lighter gapps package without google play movies & tv...

5GHz wifi is now stable for me :D However i have set "keep wifi on during sleep" to "never", which results in wifi turning off IMMEDIATELY every time the screen turns off (not normal behavior or something you want if you are streaming music for instance)

IMDB app crashes, as it seems to do on every HDX rom i've tried.

Prompts about no sim card inserted in the setup wizard, even though i have a wifi-only device (also a triangle indicating no cell service is in the status bar, as well as menus for mobile network connectivity)

Other than this, the rom is awesome. Keep up the good work guys! :D
[Kindle Fire HDX 7" & 8.9" Android Development] Cpasjuste:
Yes all this is related to the DRM problem, I'm sure we'll fix this soon !

I'll try to take a look for the IMDb app someday. For LTE stuff on WiFi devices I'll also see that later.

Thanks !
[Kindle Fire HDX 7" & 8.9" Android Development] Mr.Nik:
Do not install applications apk:

XCOM®: Enemy Within 1.2.0 build 12;

Unmechanical 1.03;

Sky Force 2014 1.36.
[Kindle Fire HDX 7" & 8.9" Android Development] DarkenedMatter:
Root isn't working for me. I can't update the binary either. Am I missing something? Worked on your cm11 for me but not here. I don't even see root options in the settings but i am told I have root but can't give anything permission.
[Kindle Fire HDX 7" & 8.9" Android Development] Cpasjuste:
You don't need to install root/supersu etc on this builds. You should remove them, enable developer options and enable root from there.
[Kindle Fire HDX 7" & 8.9" Android Development] DarkenedMatter:
Sorry, I had found that out right as soon as I posted this. Woke up from 2 hours of sleep and immediately started messing around with the ROM and noticed I had no root. I have fixed it now that you told me what to do, thank you. Nice job on getting things up and running.

Is there a way to remove the Mobile Network staus icon (signal strength) from the bar? I can't find it in the settings.
[Kindle Fire HDX 7" & 8.9" Android Development] slater_g:
Awesome work! Will test on my ApolloLTE as soon as it is released!
[Kindle Fire HDX 7" & 8.9" Android Development] murso74:
Someone help me out here... I can't find this gd download tab.
[Kindle Fire HDX 7" & 8.9" Android Development] jeryll:
Try to switch on javascript, or use another browser.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Make sure you aren't running an ad blocker (and nothing in the hosts file).
[Kindle Fire HDX 7" & 8.9" Android Development] Droid_1:
I using better battery stats and my device doesn't change into deep sleep.

It seems I m getting partial wake locks by 'SystemUpdateService' (must be part of Google play services).

Any idea how to fix that?
[Kindle Fire HDX 7" & 8.9" Android Development] andPS2:
it seems the deep sleep doesnt get reported correctly (in cpu spy) it takes a long

time after it will get reported but the battery time is fine and it is deep sleeping (at least for me)

also right now there are no error when using pa micro google apps so that is a good start for

everyone right now with this rom
[Kindle Fire HDX 7" & 8.9" Android Development] Cpasjuste:
And I'm on the DRM problem, I made some progress and some good reading about it. It seems there is some problems about 4.x DRM libs on 5.x. I'll continue the research :)
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
New Build is Up

- Not sure if it was recoverable as I wasn't able to investigate the devices in question

- My guess initially with the information I had was that they were not recoverable

---------- Post added at 20:07 ---------- Previous post was at 20:06 ----------

- Dated 2015-10-06

- Updated CM Code

- Added Multi-user support
[Kindle Fire HDX 7" & 8.9" Android Development] hurdubaiev:
Was there anything specific that trigerred the brick? Is the lateset version safe?

Thank you
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
- I am not certain what caused the brick. So as a precaution I reverted changes that I made to mmc driver in the kernel just in case.

- The new version should be ok, but I provide no guarantee or warranty.

- I personally use both SlimLP and CM-12 and have had no problems.
[Kindle Fire HDX 7" & 8.9" Android Development] scorvio:
Installed 0928 version, everything works fine, but sensors not working, no auto rotation, no auto dimming and microphone not working too. Tried slimlp 0928 with same result. Any suggestions?
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
- I tested 0928 version on both Apollo and Thor and sensors seemed to be working fine.

- I tested yesterdays build and that seems fine too.

- Maybe try a factory reset?
[Kindle Fire HDX 7" & 8.9" Android Development] hobbypunk90:
Since I had installed the "Mmc brick" version I get often error 504 in Google play, when I try to install an app, after 2-3 times it works, I did a factory reset already. Could this a problem with the Mmc?

Gesendet von meinem Kindle Fire HDX mit Tapatalk
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
- No, this has nothing to do with the MMC

- Check here: http://www.ibtimes.co.uk/how-fix-google-play-store-errors-android-device-list-issues-fixes-1447208
[Kindle Fire HDX 7" & 8.9" Android Development] scorvio:
I reverted back to stock ROM .4.5.5 (twrp version) still sensors not working.... Now running this ROM and recorded a logcat, would you mind take a look?
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
- Yes, that's fine, send logcats from stock and cm-12.1 and i'll take a look.
[Kindle Fire HDX 7" & 8.9" Android Development] derpadoodle:
Bootlooping after xposed install on latest build.

Do you have a link to the previous build so i can try that? All up to 27/09 worked fine for me, only updated because of the brick risk.

Disregard that, last night's xposed v75 update fixed the issue.
[Kindle Fire HDX 7" & 8.9" Android Development] scorvio:
Logs captured with liveboot while booting this ROM:

https://drive.google.com/file/d/0B9nt7__9tchJbGh6UXJNeGFoelU/view?usp=docslist_api

If you need logs for stock 4.5.5 ROM let me know, I'll revert to stock again. Thanks
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
- From the logs I can see you have Thor device

- Which version of CM-12.1 were you running?

- Can you also send me a dmesg output directly after boot

- The sensor service is failing to come up and lots of socket failures too.

EDIT:

- Try the following:

- Extract the NON-HLOS.bin from the attached firmware.zip

- Place it on your desktop

- Put your device into fastboot mode

- Open a terminal window and cd to the desktop

- then type the following command:

fastboot -i 0x1949 flash modem NON-HLOS.bin

- Let me know if this fixes the problem
[Kindle Fire HDX 7" & 8.9" Android Development] scorvio:
Done the suggestion above to fastboot flash the attached firmware, still the same issue though (using this CM 12.1 ROM latest 1006 version)...

Attached the dmesg log. thanks a lot

View attachment dmesg.log
[Kindle Fire HDX 7" & 8.9" Android Development] hobbypunk90:
thanks for the quick response :) i looked in the logcaat output, when i'm trying to install "Monument Valley" i got the Installation error code -18 all the time, do you know what this mean? :-/
[Kindle Fire HDX 7" & 8.9" Android Development] cq_:
Is there a change log from 9/28 to 10/6 ?

I jumped on the 9/28 update for the e-mmc kernel updates (and netflix support), what's changed/updated in the 10/6 version?
[Kindle Fire HDX 7" & 8.9" Android Development] ONYXis:
Greatest work, [MENTION=5749760]ggow[/MENTION].

I just bought cracked thor with old firmware and replace screen with one from my brick.

I unlocked bootloader and flash this. everything good.

Thank you.
[Kindle Fire HDX 7" & 8.9" Android Development] Oh_wow:
So its safe to uninstall safestrap 4 and flashify twrp....which is the most recent stable twrp for cm12?

thanks
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
No - if on Safestrap v4 you can not install native TWRP on your device. There is no rollback option. Your choice of roms is limited to Nexus v4 and cm11.
[Kindle Fire HDX 7" & 8.9" Android Development] Oh_wow:
Well that's a bummer... I love Nexus 4 but am having flashing withdrawals:)
[Kindle Fire HDX 7" & 8.9" Android Development] qingtest:
Note for the latest 1006 ROM:

After flashing (and wipe cache) the system will reboot one more time than previous ones.

Do NOT flash xposed module, it will result in infinite boot loop. (The previous ROM no problem)
[Kindle Fire HDX 7" & 8.9" Android Development] ^Apo^:
Is there anything like providing logs or something like that what a noob like me could do to support getting LTE working?

Maybe it would be possible to port the LTE stack from the CM11/Nexus release to the CM12.1 release? :)
[Kindle Fire HDX 7" & 8.9" Android Development] fryheit:
+1 for that!!
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Opinion: I think it comes down to developer resources - both time and equipment. Roms customized for HDX are largely supported by one individual (@ggow) who is spread thin across multiple projects and does not own a LTE device. Guessing he has a 'real job' and family life too. The LTE issue has been around for awhile across multiple roms and appears to be a tough nut to crack. Others have contributed logs when requested. Unfortunately, the vast majority of HDX devices are WiFi only. Until recently many owners could not even install a custom rom due to Amazon restrictions and poor documentation. Amazing how far development has progressed given the high hurdles.
[Kindle Fire HDX 7" & 8.9" Android Development] beatnixde:
Hi.

I would like to step in and help out here. I am a software developer and I own a LTE Thor device. And would love to have LTE up and running. Any hints were we should start with debugging are very much apprechiated. Besides dmesg - which does not show any issues in terms of USB device recognition - does someone have a clue how the next layer in Android would start picking up the hardware device and use it? I would get back an do more debugging...

Anyways, Thanks to everybody who brought this distribution that far for hdx devices.

Cheers

Tobias
[Kindle Fire HDX 7" & 8.9" Android Development] noonecanhide:
Hi, i own an Apollo LTE device. Would be nice if i can help out, too. I am a linux server specialist, but have above-average experience in java development, too. Never worked with android rom development, but i would give it a shot in Terms of testing, debugging or development
[Kindle Fire HDX 7" & 8.9" Android Development] gorthon:
I currently have CM 11 on my Thor device. I don't have SafeStrap, but installed it with the bootloader circumvention method that was made available at the beginning of the year, before the real bootloader unlocking became public. So I do have TWRP.

Question: is it possible to install this CM12 this way or do I really need to unlock my bootloader? If so, why / what is the difference to the CM 11 ROM?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Bootloader must be unlocked for any lollipop based rom and likely all future roms for hdx devices. Considerations (as I understand them):

- more robust recovery ability if something goes wrong

- extra work for dev customizing (signing) components for locked bootloader.
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
Just try to unlock the bootloader, can't screw up anything there. It either unlocks or fails. If you have trouble with Python, etc. just execute the required commands to get your ID & serial (PM me them), I'll create the unlock file for you then. Actual unlocking is a task you'll have to do yourself though. ;)
[Kindle Fire HDX 7" & 8.9" Android Development] slothdabski:
Is this process ppossible for an HDX running CM11 via safestrap?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Yes - unlock procedure has no rom/safestrap dependencies. Nothing changes once unlocked; everything continued to run as before. Except you now have the ability to flash hdx roms that have an unlocked bootloader prerequisite.

As [MENTION=6815340]Cl4ncy[/MENTION] said there is minimal risk associated with unlock attempts. Unlike rollback/flashing you are not going to harm/brick your device just by trying even if it fails.

Also note the prerequisites for unlocking: must be running FireOS <= v3.2.3.2 -or- be 100% certain bootloader is at that level. There is no mechanism for testing bootloader version independent of OS. You can NOT rollback if any version of FireOS > v3.2.6 has ever been installed on the device. Note Safestrap must be removed prior to rollback attempts or flashing either lollipop variant.
[Kindle Fire HDX 7" & 8.9" Android Development] slothdabski:
Ah so if I was running Fire OS 4.5.2 it sounds like I'm stuck with kitkat ROMs and safestrap? :(
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
Yep, no way to downgrade to a version below 3.2.8 (attempt would brick the HDX due to rollback protection by Amazon), and no way to unlock the bootloader either. Sorry.
[Kindle Fire HDX 7" & 8.9" Android Development] gorthon:
Just to make sure: so if I have a too recent bootloader I will only get an error message but not brick the device?

I am running TWRP Recovery und CM11 but the bootloader is locked. Before that, I was using SafeStrap, and as far as I remember I was using that with 3.2.4. Then probably downgraded to 3.1.0 in order to get TWRP and CM11, but given that this was more than half a year ago I can't remember exactly. And if I'm not mistaken there is no way of finding out the bootloader version without FireOS, right?
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
If you have the

real

TWRP you can unlock the bootloader. ;)

And yes, you can not brick anything by trying, it just won't unlock.

But which CM11 do you use anyway? If it's this version it requires an unlocked bootloader as well, so you sure you didn't unlock yet?

Try to check:

As [MENTION=5488402]Davey126[/MENTION] mentioned here you can open a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:

fastboot -i 0x1949 oem idme

You will only get a response if unlocked (requires Minimal ADB & Fastboot to be installed).
[Kindle Fire HDX 7" & 8.9" Android Development] gorthon:
Sorry for not answering yet. I'm trying to unlock right now and was going to answer with the result :)

I am 100% sure I don't have an unlocked bootloader. At the time the unlock procedure was not yet public. I installed the first available CM11, so the TWRP recovery I have is probably not the "real" one :)

I already created my unlock.img, but am still facing driver issues: first had to change the fire hdx in device manager to a standard usb composite device, only this way adb devices would show it. That worked for getting manfid and serial, but on adb reboot-bootloader the device disappeared and since then is not visible for adb anymore in fastboot mode. Now trying to find better drivers...
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
This CM11 requires an unlocked bootloader as well? :confused:

Did you try the fastboot command mentioned above to check the unlock status? Oh, regarding drivers, these should work with fastboot.
[Kindle Fire HDX 7" & 8.9" Android Development] gorthon:
This is the CM11 I am using. And I am 100% sure I had not unlocked the bootloader.

I write "had", because I just succeeded in unlocking it (found the drivers you were pointing me to a few minutes ago). Yeah! And many thanks!

I'm now stuck at installing the "real" TWRP: since I installed the drivers I get the adb offline problem when I'm in CM11, so I was unable to issue these commands through adb to flash the recovery:

adb shell
su
dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

So I thought well, I have root, so let's open a shell and issue the dd command there. It completed and then I could get to the real TWRP and install CM 12. It's not booting yet, but I tried to install it over CM11, which may not have been as good as a fresh install. Anyway, I'll figure it out.

Thanks to everyone who helped making this possible!
[Kindle Fire HDX 7" & 8.9" Android Development] Cl4ncy:
You must unlock the bootloader for CM12 to work!

But in the CM11 thread you mentioned it says a Fire OS version below 3.2.4 is required, so you should have 3.2.3.2 or lower, thus you should be able to unlock the bootloader. Can you still access TWRP?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Congrats on the bootloader unlock. Note you can also use Flashify (available in the Play Store or here: www.apkmirror.com/apk/christian-gollner/flashify/) to install TWRP. Be sure to backup you current recovery first (another advantage or using Flashify) and be 100% confident of your actions before committing. Flashing the wrong recovery (or selecting the wrong partition) can be a death sentence. Good luck.
[Kindle Fire HDX 7" & 8.9" Android Development] gorthon:
Yes, the unlocking worked, so I must have had 3.2.3.2 or lower. Probably 3.1.0 as I could imagine that I downgraded to that in February before installing CM11. I'm now thinking about upgrading the Bootloader to 3.2.3.2 but am not sure if it brings any advantages with CM12 and if it would re-lock the bootloader.

BTW, CM12 is working now, it just took quite some time to boot up the first time.

So basically what I did was:

1) play around with standard Windows composite USB drivers until the hdx showed up on adb devices while my system (CM11) was booted.

2) Issued the commands to get the serial and that other number

3) Used the python script to get unlock.img

4) Booted into fastboot and this is where the problem began: I did not have adb/fastboot access

5) Searched for quite some time till I found the correct drivers (the ones you posted the link to) and realized that adb devices does not list the hdx, but fastboot commands work anyway. Then realized that even the the fastboot devices commands only showed the possible fastboot parameters, the unlock command still worked.

6) Rebooted into CM 11 system in order to flash most recent TWRP recovery. ADB access did not work there anymore (showing adb offline). Issued the commands to flash the recovery from a root shell.

7) Booted into TWRP, flashed CM12 and Google Apps.

It took much longer than expected, but basically due to the driver issues and that it took me a while searching through the forums to find the solution. In the meantime I re-installed Android SDK and the Kindle ADB drivers, which was totally useless as they don't help for missing ADB access in fastboot.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
You should update to v3.2.3.2 ASAP as the bootloader comes into play during device initialization and is largely independent of rom choice. You can quickly/easily upgrade via TWRP or Flashify. Your existing rom/data will remain intact; bootloader stays unlocked.

Yep - Windows driver issues are often the largest hurdle in unlocking and tethered access. Keep fiddling...you will eventually find a combination that works. Best practice: plug device, uninstall *all* related entries in device manager, reboot both devices (HDX in desired mode), replug and let Windows install auto-install correct driver for current mode (assumes you have previously downloaded/installed recommended HDX drivers; see previous posts by [MENTION=6815340]Cl4ncy[/MENTION] for links). Unsophisticated but generally works.
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
New Build is Up

- Dated 2015-10-24

- Updated CM-12 Code
[Kindle Fire HDX 7" & 8.9" Android Development] cocoon4u:
Thx for keeping up to date! :highfive:

I will test it as soon as possible and report if there are any unknown errors.

Will there be a SlimLP update too?
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
Yes, SlimLP will be out tomorrow morning.

EDIT: Done :)
[Kindle Fire HDX 7" & 8.9" Android Development] Mr.Nik:
CM11 update too?
[Kindle Fire HDX 7" & 8.9" Android Development] ggow:
Yes I will be updating CM-11 at some point this week.
[Kindle Fire HDX 7" & 8.9" Android Development] 058515471:
cm 12.1 auto reboot sometimes. does anyone have the same problem?
[Kindle Fire HDX 7" & 8.9" Android Development] cybercat1:
yes, the same issue. Rotation bug, reboots, almost no BT...
[Kindle Fire HDX 7" & 8.9" Android Development] zXiC:
Almost no BT? So Bluetooth works sometimes or generally not at all?
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
Bluetooth is unreliable on CM12. Some have reported sporadic successes with devices that don't require authentication but generally it's a no-go. Nexus v4 or CM11 are better choices if you need BT connectivity.
[Kindle Fire HDX 7" & 8.9" Android Development] cybercat1:
Some says it works. But I still can't connect my BT keyboard, that's why I said: "almost"
[Kindle Fire HDX 7" & 8.9" Android Development] gorthon:
Does anybody else have the problem that the battery drains faster than on CM11 (and much faster than on FireOS)?

If I check battery in the settings I can't see which app used how much, all it says is "battery usage data isn't available".
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
This has not been widely reported. Try downloading a battery utility like GSam (free version is fine) to help identify the culprit.

Curious if you flashed 3.2.3.2 bootloader update after unlocking?
[Kindle Fire HDX 7" & 8.9" Android Development] johim:
I was wondering, I'm unlocked, twrp, and CM11. How do I check my bootloader version? I cant remember off of my head right now. Probably its displayed somewhere in TWRP or CM11 about info.
[Kindle Fire HDX 7" & 8.9" Android Development] DB126:
There is no mechanism for querying bootloader version independent of FireOS. Even then the two can be different. For example, you can flash bootloader version 3.2.3.2 and FireOS with still report 3.1.0.x in the UI. If uncertain you can simply reflash the suggested bootloader version (here) in twrp. Note there is always a small risk flashing anything; if you are not experiencing the symptoms shown in the post don't bother. Ya know, if it ain't broke don't fix it ...
[Kindle Fire HDX 7" & 8.9" Android Development] 1indwurm:
Hi I'm trying to build CM-based custom ROMs for thor, but it stuck on bootanimation.

Would you update Device Tree for cm-12.1 ?