New Build is Up
- Dated 21 December 2018
- Included / Ported relevant Security Patches up to December 2018
- Dated 21 December 2018
- Included / Ported relevant Security Patches up to December 2018
That's going to be a tough find given Open GApps is no longer producing Kitkat builds.Sorry if dumb question, what version of android Gapps do i download?
Sorry if dumb question, what version of android Gapps do i download?
That's going to be a tough find given Open GApps is no longer producing Kitkat builds.
- Dated 21 December 2018
- Included / Ported relevant Security Patches up to December 2018
Nope - stick with SuperSU or (preferably) the integrated root manager.
That's going to be a tough find given Open GApps is no longer producing Kitkat builds.
It would seem Android 4.4 builds are being produced irregularly. I am certainly savvy enough to select the proper architecture on the website; I do not use the Open GApps app. Today only Nano (my preference) and Pico builds are available. Last time I checked only Stock was available which is generally too large to for the system partition on a HDX unless other actions are taken.Well, I have to disagree.
First of all the OpenGaps-App fails, so you have to visit the website.
There 4.4 is greyed out, but only because ARM64 is preselected.
If you change to ARM (32 bit), 4.4 is available and a package from January, 10th at the moment is available for download.
When installing Gapps I discovered, CM11's reboot to recovery is not working (for me at least).
The OpenGapps-App was able to do this, so it's a shame to loose it.
It would seem Android 4.4 builds are being produced irregularly. I am certainly savvy enough to select the proper architecture on the website; I do not use the Open GApps app. Today only Nano (my preference) and Pico builds are available. Last time I checked only Stock was available which is generally too large to for the system partition on a HDX unless other actions are taken.
Google is constantly mucking around with Play Services/Framework and the portfillo of apps with strong dependencies. Incompatibility will eventually creep in unless all (or none) auto-update which isn't always the case. How long that takes is situational. I have gizmos that haven't seen a GAaps refresh in years. Others poop out once or twice a year. That said, you're probably safe on an Android 11 based ROM as the focus is elsewhere.Well, so OpenGapps is an unsave candidate for 4.4.
In the good old times when our HDX7 was a Top-Winner, I always used the same ZIP (for more than 1 year).
Especially when using Nano, there shouldn't be any disadvantage. Right?
Best to unlock the bootloader allowing installation of a much broader selection of custom ROMs. You'll be better served by Lineage 14.1 vs this aging ROM.First off I want to thank you for still providing updates for the kindle after all those years.
I recently digged out my hdx 7 and now want to update to this rom.
Even though I looked around the forum, I am kind of lost about how I should upgrade:
I am using your old HDX nexus ROM v2.0.5 .
When I boot to recovery, TWRP appears with version 2.8.6.0 . However, I read somewhere that this is probably not a 'real' recovery but only an emulated one.
When I boot into bootloader I only see the fire logo and [fastboot] with no actual version number. I assume this means I still have a locked bootloader.
How do I get to the required firmware versions (Stock base of .4.5.5.3 and Safestrap v4) without bricking my device? Do you recommend unlocking the bootloader and installing a 'real' TWRP version?
Best to unlock the bootloader allowing installation of a much broader selection of custom ROMs. You'll be better served by Lineage 14.1 vs this aging ROM.
https://xdaforums.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Existing firmware is irrelevant for 1-click and the equivalent manual unlock method. Both install an older bootloader with a signature forging vulnerability that is exploited to execute the unlock. 1-click automates this process in tosses in a few other 'nice to haves'. Once unlocked you can choose form any available HDX custom ROM - although most go with Lineage 14.1.I found the thread you linked but I am not sure if it works with my old firmware. Does it matter at all? Like, will this one click tool just install the latest bootloader?
Is there any other firmware that needs to be updated (like modem for phones)?
Where do I get that linage Version for the kindle? Can you give me a small step by step guide?
USB tethering isn't supported on 3rd gen HDX devices regardless of ROM; hardware limitation. OTG doesn't work either.
I remember when I was running the official FireOS ROM I could use the USB Tethering app to pull up a hidden menu where USB tethering was in. Same thing with the Nexus ROM, although I stopped using it because it was unstable (at least from my experience.)USB tethering isn't supported on 3rd gen HDX devices regardless of ROM; hardware limitation. OTG doesn't work either.
USB port is unpowered on 3rd (and likely 4th) gen HDX devices. Not even the measly 1-5 unit loads (100-500 mA) in the USB 2.0 spec. Whatever tethering you were doing had to be at a very low throughput rate.I remember when I was running the official FireOS ROM I could use the USB Tethering app to pull up a hidden menu where USB tethering was in. Same thing with the Nexus ROM, although I stopped using it because it was unstable (at least from my experience.)
[COLOR="gray"]
/*
* I am 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
- The Safestrap series of ROM's all use the stock 4.5.2 kernel and stock ramdisk
- There are differences in the way stock FireOS handles the hsic control of BT and WiFi
- Because we can't modify the ramdisk on these ROM's I can't control the handling of BT and WiFi the way I should or want to
- The Safestrap series of ROM's will probably always have this limitation on battery management as essentially it is a hack (an excellent one).
- On a very positive note, because of Safestrap and the ROM's we can say bye bye to FireOS even on a locked bootloader
- I did these ROM's for one reason, and that was to help out those with bootloaders that can't be unlocked.
- Now potentially everyone can run a custom/hacked ROM.