I never rooted, ROMed my Kindle HDX 7 (64GB + LTE) because the working methods looked very dangerous for the tablet. However, I just got an HDX 7 64GB + LTE back from warranty repair. It has firmware 13.3.2.1 on it!
I'm back considering a root and android ROM, but things have changed a lot in 2015. There is a functioning bootloader unlock that exploits the qualcomm cubed root hash vulnerability. Does unlocking the bootloader significantly improve the safety of messing around with the HDX? Or is this thing still teetering on the edge of efuse brickdom if unlocked?
I'd like to dual boot this Kindle HDX with latest FireOS and a Android ROM (like NEXUS or CM11). I'm willing to go all Android ROM if retaining FireOS is dangerous. I've read about methods to brick the OTA update process to improve FireOS safety, but i would like to be on a modern xx.4.5.x version if FireOS is retained (i.e. want to update after bootloader unlock).
Is there a procedure to follow? It looks like towelroot, then bootloader unlock, then TWRP, then the NEXUS rom.
I regret I'm very rusty at the whole android ROM scene. I haven't flashed anything since the OS 2.1 days. The 4.0+ devices of the last 3 years are quite good and really didn't need such actions (particularly the Moto's).
In general, if it's still exceedingly dangerous to mess around with this tablet, i'll probably just let it update and suffer with FireOS again. Or maybe sell it.
Thank you for your guidance.
I'd suggest to root, install TWRP, (optional: update to 3.2.3.2 then, can be done via TWRP, if not done via TWRP it not only removes root, but also TWRP!, don't forget to re-root and disable OTA!), unlock the bootloader (might require these drivers) and install Nexus, CM11 or CM12 - your choice. Read the compatibility and installation notes carefully! If in doubt ask first, i.e. before you brick your kindle.
That's interesting? I would think an unlocked bootloader would be first (at least from prior experiences with the Moto G). Root->TWRP -> 3.2.3.2 -> root -> TWRP -> unlock bootloader -> CM12 sounds equally as dangerous as previous methods involving safestrap. Letting 3.2.3.2 re-assert itself over the hardware just sounds like more opportunities for disaster.
Should i go look at the other kindle fire forums for some background on these processes? The documentation of the HDX leaves much to be desired. I had a 1st gen Kindle Fire, but it was very easy to ROM.
Should i also get a USB OTG cable for saving/restoring FireOS firmware backups as well?
Again, thank you for your guidance.
etronz said:
That's interesting? I would think an unlocked bootloader would be first (at least from prior experiences with the Moto G). Root->TWRP -> 3.2.3.2 -> root -> TWRP -> unlock bootloader -> CM12 sounds equally as dangerous as previous methods involving safestrap. Letting 3.2.3.2 re-assert itself over the hardware just sounds like more opportunities for disaster.
Should i go look at the other kindle fire forums for some background on these processes? The documentation of the HDX leaves much to be desired. I had a 1st gen Kindle Fire, but it was very easy to ROM.
Should i also get a USB OTG cable for saving/restoring FireOS firmware backups as well?
Again, thank you for your guidance.
Click to expand...
Click to collapse
Well, the 3.2.3.2 update is optional, but you could do it first of course, then install TWRP, backup Fire OS from TWRP and move the backup to your PC, then unlock the bootloader, and use whatever ROM you want.
I think it's possible to just flash the 3.2.3.2 bootloader, unfortunately I can not provide a link to that info though.
Cl4ncy said:
Well, the 3.2.3.2 update is optional, but you could do it first of course, then install TWRP, backup Fire OS from TWRP and move the backup to your PC, then unlock the bootloader, and use whatever ROM you want.
I think it's possible to just flash the 3.2.3.2 bootloader, unfortunately I can not provide a link to that info though.
Click to expand...
Click to collapse
ah, i'll go read more of the HDX bootloader thread to see it's restrictions. I think i'll follow the amazon manual update process for 3.2.3.2 -> then root it -> install TWRP -> backup -> unlock -> then android ROM. Hopefully i can dual boot as well.
I'm going to read some more before attempting this. It looks like there are a few steps to break/prevent OTA updates for the HDX.
etronz said:
ah, i'll go read more of the HDX bootloader thread to see it's restrictions. I think i'll follow the amazon manual update process for 3.2.3.2 -> then root it -> install TWRP -> backup -> unlock -> then android ROM. Hopefully i can dual boot as well.
I'm going to read some more before attempting this. It looks like there are a few steps to break/prevent OTA updates for the HDX.
Click to expand...
Click to collapse
Root and OTA on/off can be done with HDXToolkit.
Read carefully, if in doubt ask first.
I'm not sure if dual boot works with TWRP on HDX devices.
Related
So I've been reading these forums for the last 3 or 4 hours and I seem to be in an endless loop. I'm hoping people can help me untangle this mess, and perhaps I can write this up for others to enjoy.
I just picked up a HDX 7" with 13.3.0.5 on it. I dont care about the stock software, my ultimate goal is to get CM12.1 running on it.
So I see this ROM is available...
http://forum.xda-developers.com/kin...ent/rom-cm-12-unofficial-apollo-thor-t3050199
So from previous ROMing I know I need to get TWRP installed to get that running. So I find this post...
http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
However, first step is to unlock the bootloader... so I find this...
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
That says the first step is to install the "vulnerable" 13.3.2.3 firmware. Ok great...
http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
That first step there is to install TWRP :/ Seems we have an infinite loop here. Can anyone explain the proper procedure for going from stock 13.3.0.5 to CM12.1 using these procedures?
TWRP can be installed on your current firmware, its just recommended that you use 3.2.3.2 as a base since it's the most up to date exploitable firmware. You can update without TWRP if needed, just place the Amazon update bin in the root of your internal storage and check for updates with WiFi disabled.
derpadoodle said:
TWRP can be installed on your current firmware, its just recommended that you use 3.2.3.2 as a base since it's the most up to date exploitable firmware. You can update without TWRP if needed, just place the Amazon update bin in the root of your internal storage and check for updates with WiFi disabled.
Click to expand...
Click to collapse
@insodus - I agree with derpadoodle and have puzzled over the conflicting guidance myself. I can also confirm flashing the latest TWRP on 13.3.0.x is fine followed by the 3.2.3 bootloader (only) upgrade. You can then proceed with unlocking your bootloader and installing CM12. Gab a nandroid or two along the way just in case (best done from within TWRP).
You will obviously need to root your current firmware before proceeding. Don't forget to block OTA if you plan to enable wifi anytime before dumping stock. Also note a few things still aren't 100% in CM12; CM11 might be a better short-term choice and can be installed on with a locked bootloader (unlocking is still recommended).
Davey126 said:
@insodus - I agree with derpadoodle and have puzzled over the conflicting guidance myself. I can also confirm flashing the latest TWRP on 13.3.0.x is fine followed by the 3.2.3 bootloader (only) upgrade. You can then proceed with unlocking your bootloader and installing CM12. Gab a nandroid or two along the way just in case (best done from within TWRP).
You will obviously need to root your current firmware before proceeding. Don't forget to block OTA if you plan to enable wifi anytime before dumping stock. Also note a few things still aren't 100% in CM12; CM11 might be a better short-term choice and can be installed on with a locked bootloader (unlocking is still recommended).
Click to expand...
Click to collapse
Ok, so if I dont care about the amazon firmware because I want CM only... I still should update to 13.3.2.3 before unlocking?
1- Root it (any preferable method? towelroot?)
2- Install TWRP
3- Update the bootloader to 13.3.2.3
4- Unlock bootloader
5- Flash cm image
insodus said:
Ok, so if I dont care about the amazon firmware because I want CM only... I still should update to 13.3.2.3 before unlocking?
Click to expand...
Click to collapse
The 13.3.2.3 bootloader update is quick and easy. This code remains on your device even with other roms. So yeah, you should apply the update.
insodus said:
1- Root it (any preferable method? towelroot?)
2- Install TWRP
3- Update the bootloader to 13.3.2.3
4- Unlock bootloader
5- Flash cm image
Click to expand...
Click to collapse
My preference is HDX toolkit as it avoids wifi, installs SuperSU and has other handy options. However, it is a tethered solution which can be a PiTA. Towelroot should work fine too; I have used both.
Although it involves little risk bootloader unlocking is not for the faint of heart. You can always flash CM11 after step #3 and play with that while researching the bootloader unlock procedure. A recent tutorial by travanx captures most of the steps in one post. You'll want to start about halfway down.
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Timmetjuh said:
Hello,
I'm hoping that someone can help me out with this.
Last December i bought a Fire HDX 7 (Thor). I immediatley followed the procedure to install Safestrap and the Thor Nexus ROM v2.0.1. Shortly after that my device got lost. Just last week I found it because my parents moved. After this I started looking around the internet to check if there are any 5.0 or 5.1 ROMs available. I found out they are indeed available.
What I want to do now is get rid of Safestrap, unlock the bootloader and install TWRP to be able to flash new ROMs. I want to start using TWRP because I'm used to working with TWRP.
The problem is that I can't seem to find a way to get this done, despite searching for it on this page for several hours. Can anyone help me on the right track? Would be very much appreciated.
Click to expand...
Click to collapse
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Davey126 said:
Your options are determined by the current version of Amazon firmware installed on your device. I assume you retained Fire OS in the base slot. Boot into that and poke around settings until you find the version number (should be 13.x.x plus some other gibberish). Post what you find and we'll go from there.
Caution: You should disable wifi immediately after booting into Fire OS to prevent an automatic update from Amazon from spoiling your day. At minimum an update will limit future options. I can also brick your device depending on firmware level and other previous mods (including safestrap). Disabling wifi in Nexus is not sufficient as the two roms operate independently.
Click to expand...
Click to collapse
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Timmetjuh said:
Could it be that I somehow deleted the Fire OS back then? Don't really remeber what I did exactly..
Click to expand...
Click to collapse
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Davey126 said:
Quite possibly. Enjoy Nexus; it's a good rom. Alternatively, follow the directions to see if you still have Fire OS installed. If at/below v3.2.6 then Lollipop is possible albeit with a lot of work and significant risk to your device. Otherwise you are limited to Fire OS and Nexus.
Seriously, if you don't recall what you did and can't figure out how start Safestrap in recovery mode be happy with what you have. There are no step-by-step guides. You have to read (a lot) and be prepared for numerous setbacks including an unrecoverable brick of your now working Kindle.
Click to expand...
Click to collapse
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Timmetjuh said:
Sorry for my late response.. I just started Safestrap and can only find 1 ROM slot, the Stock ROM slot which probably means that I deleted the original OS.
I did find some files on my laptop that brought some memories back. What I did back then is downgrade the original software to version 13.3.2.6 and than to 13.3.1.0. Does this create any new possibilities?
Click to expand...
Click to collapse
Timmetjuh said:
I just managed to create a new ROM slot and succesfully installed stock 13.3.2.6 on it, so now running on Nexus ROM and stock 13.3.2.6.
Click to expand...
Click to collapse
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Davey126 said:
Warning: Do NOT allow Fire OS to auto-update. Doing so will likely brick your device. Short term the best way to prevent this is to only boot into Nexus. If necessary I can walk you through blocking OTA. Seriously - stay out of Fire OS for now.
I am no Safestrap expert but I believe the rom in the 'base' slot becomes the default when you uninstall Safestrap. So you may have some shuffling to do. Another concern is whether removing/reinstalling Fire OS will impact the ability to recognize the OS once Safetrap is gone. You need a functioning version of Fire OS (and recovery) to follow the 'standard' rollback/update/flash procedures.
However, there may be a shortcut. If 13.3.1.0 was the base rom just prior to installing Nexus and wiping out Fire OS you then should be able to flash twrp without further prep. That would give you access to both Nexus variants and CM11. Unfortunately, there is no easy way to determine the bootloader version which is the component that really matters. It should match the last version of Fire OS that was natively installed before you overwrite it with Nexus.
Unfortunately, the recent install of 13.3.2.6 into a safestrap slot complicates matters. I believe installs within Safestrap leaves the bootloader untouched. But I can't be sure. A misstep can leave your device in an unrecoverable condition; don't go experimenting.
Let's see which recovery you have installed. Power down the device then restart holding power + vol-up. When the grey Kindle logo appears release the power key; vol-up can be released a few seconds later. What happens after the grey logo disappears?
Click to expand...
Click to collapse
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Timmetjuh said:
I see the following:
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Then I get the options to Reboot or to reset to Factory Default.
Oh, the Fire OS is not connected to any networks so it won't be able to update.
Click to expand...
Click to collapse
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It's not that I don't like the Nexus ROM, I just like to experiment with these things..
So I just installed TWRP with Flashify (started Flashify from NEXUS) and now I seem stuck at the grey Kindle fire logo. I'm just going to leave it alone for a few hours, hopefully it boots later today.
Davey126 said:
Ok - a working stock recovery. That's good.
I am conflicted on next steps. The scripted approach would have you uninstall Safestrap (assuming Fire OS had remained in slot 0), rollback to 3.1.0 and then install twrp. However, since slot 0 now contains Nexus I do not feel removing Safestrap is wise. Nor to I think reinstalling Fire OS in the base slow will yield a functioning system once Safestrap is gone.
The 'shortcut' would have you flash twrp recovery (via adb or Flashify) since your bootloader *should*_be at the right level due to a previous 3.1.0 rollback. However, if that is not correct you will end up with a borked recovery which is difficult to rectify.
In your shoes I would probably do nothing given the device is fully functional. The developer of the Nexus rom is working on a KitKat 'upgrade' which is close to being released; a Safestrap variant will hopefully follow. There's no shame in running Nexus. Upgrade to v4.4, add a few Xposed modules and you have fully supported, near AOSP environment that's only lacking a few eye candy elements from Lollipop.
Click to expand...
Click to collapse
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Timmetjuh said:
It still boots after a very long time, however I don't know if I get the possibility to enter recovery because it takes several hours to boot. Any more ideas?
Click to expand...
Click to collapse
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Davey126 said:
Power down device and attempt to enter recovery by pressing power + vol-up. Release the power button after the grey logo appears; vol-up can be released after a few seconds. What happens next? Likely one of the following (good -> bad):
- blue screen followed by twrp recovery
- stock recovery with only two options: factory reset and reboot
- continuation of grey kindle logo
Click to expand...
Click to collapse
I'm stuck at the grey Kindle logo..
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Timmetjuh said:
Did it! Managed to flash the stock bootloader, rollback and install TWRP. Now ready to flash CM11. Thanks for you help!
Click to expand...
Click to collapse
Congrats! Had a bad feeling after your earlier post; glad that was misplaced. Enjoy CM11 and all the goodness that comes from a liberated HDX.
At some point you should consider unlocking the bootloader. That will provide an important fail safe should things go wrong and opens the door to newer roms. Unlike previous flashes there is little/no risk in unlocking. It will either work or not with no adverse consequences. Unlocking can be a frustrating ride as the process involves multiple steps in unfamiliar territory but ultimately the benefits outweigh the effort IMO. Nothing that needs to be tackled right away but keep it on your radar ... especially if you plan to experiment with other roms.
Unlock bootloader
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
No. You can NOT unlock the bootloader! You can NOT downgrade to 3.2.4 and then further to 3.1.0/3.2.3.2! DON'T attempt to do so, you will brick your HDX!
Your only available option is to stay on 4.5.2 and use Safestrap v4 with either Nexus and/or CM11.
slothdabski said:
Hello davey,
I am also interested in getting from safestrap v4 to an unlocked bootloader in order to use a lollipop ROM. My 3rd gen hdx 7 started on 4.5.5 so I did OTA rollback to 3.2.8, upgraded to 4.5.2, then rooted and safestrapped. Unfortunately I lost my stock ROM, but I current have both CM11 and HDZ nexus v4 on 2 different ROM slots. What would be my best way to proceed? From my research so far, it would appear I need to flash hdx nexus 2.0, then flash rollback image to get to modified 3.2.4, and from there 3.1.0 stock update with will allow me to use python method to unlock BL. Is this all correct?
Thanks in advance for your guidance
Click to expand...
Click to collapse
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Davey126 said:
Unfortunately, you can not unlock your bootloader. Amazon introduced anti-rollback protection that will hard brick the device if rolled back below 3.2.8. Sorry, mate.
Click to expand...
Click to collapse
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
slothdabski said:
Thanks Davey, you have been very helpful replying to me in another thread also. My reason for seeking a ROM other, than Nexus v4 or CM11, is the kitkat bluetooth tether/VPN bug documented at code.google.com/p/android/issues/detail?id=62714 (sorry for no direct link, xda won't let me post them yet). A "work around" is to establish a wifi connection, even if it doesnt have internet access. This, for whatever reason, allows kitkat to forward the packets to apps on the kindle. I probably could get away with plugging in an old access point at work to enable the sharing sharing of my phones data connection with my safestrap kitkit kindle, but this isn't practical outside of my workplace.
FYI, I cant share my phone's connection via wifi because its an ATT note 4 with lollipop, a locked bootloader, and no permaroot available. I doubt there's a way to tether between 2 android devices via microUSB; but i'd be open to that too!
Thanks again for your wisdom and expertise!
Click to expand...
Click to collapse
I actually just got it working by running the following as SU in terminal emaulator
# ip route add default dev tun0 scope link
Not sure yet if I have to do this every time I tether, but if so, i think i can just make a script to execute automatically?
Hi guys,
I got my Kindle Fire HDX 8.9" and my first goal is obviously to get rid of the Fire OS...
My device is currently running 14.3.2.2
I directly started to KFHDX+ Toolkit 0.95 to get root, ota blocker and HDXposed.
But now I'm stuck and need to ask what is now the best way to get CM11 on my apollo.
So let's begin...
I seem to have two choices. Either installation of safestrap or TWRP.
While TWRP sound more complicated, but having more possibilities.
So I have the following two problems
a) Safestrap - it seems it requires XX.4.5.2
I have an older version, so I better not try to install Safestrap on it.
b) TWRP - seems to require .3.2.3.2 and I should unlock my bootloader
Slightly different version from what I use. But I'm not sure if it's compatible anyway... and I have no unlocked bootloader yet. So better not giving it a try
So should I upgrade by ota to the latest Amazon firmware and can use safestrap then? (is xx.4.5.2 the latest?)
Or is there an instruction how to update to .3.2.3.2 and unlock my bootloader as preconditions for TWRP?
Thanks for helping a 8.9 " newbie.
Always interesting to explore a new device, but sometimes hard to understand the simplest things
I'd suggest to update to 3.2.3.2 and use TWRP, it gives you more options, you probably will miss, if you'd update to 4.5.2 and use Safestrap.
I've Thor though, so I'm not exactly sure where you can find 3.2.3.2 for Apollo atm, the bootloader unlock procedure is described here, TWRP Installation here.
If you get stuck at the bootloader unlock procedure with "Waiting for device" in the fastboot prompt, and "Ready" on the HDX, you need to install the correct drivers (check device manager, the HDX is probably there with a yellow exclamation mark then - you're on Windows?).
Before you do anything be sure you have all correct files, and if in doubt ask first (i.e. before you brick your HDX).
Thanks for the link to this great explaination from ceyo14. I found the original post in the same thread, but it was hard to understand what to do. This is much more simpler than expected. I'm running windows.
Since I could not wait yesterday I also already started an experiment to go for 4.5.2 and use safestrap.
My bad is that it did not work. I was trapped in a bootloop and was glad to escape by holding volume down and power. Close call... So I removed safestrap again and I'm back to 0% progress but with 4.5.2.
So I think my next blocking point is the downgrade because I will not follow up the safestrap variant any more. I hope it's possible at all to downgrade and will search later for a tutorial. I assume it's not just copying 3.2.3.2 to internal storage and execute the update via settings
messiah said:
Thanks for the link to this great explaination from ceyo14. I found the original post in the same thread, but it was hard to understand what to do. This is much more simpler than expected. I'm running windows.
Since I could not wait yesterday I also already started an experiment to go for 4.5.2 and use safestrap.
My bad is that it did not work. I was trapped in a bootloop and was glad to escape by holding volume down and power. Close call... So I removed safestrap again and I'm back to 0% progress but with 4.5.2.
So I think my next blocking point is the downgrade because I will not follow up the safestrap variant any more. I hope it's possible at all to downgrade and will search later for a tutorial. I assume it's not just copying 3.2.3.2 to internal storage and execute the update via settings
Click to expand...
Click to collapse
Hm, that was probably a bad idea, I don't think you can downgrade to 3.2.3.2 anymore. You will most likely brick your HDX. So no more unlocked bootloader and TWRP for you, sorry.
You must use the new Safestrap with 4.5.2, and read the requirements carefully!
Cl4ncy said:
Hm, that was probably a bad idea, I don't think you can downgrade to 3.2.3.2 anymore. You will most likely brick your HDX. So no more unlocked bootloader and TWRP for you, sorry.
You must use the new Safestrap with 4.5.2, and read the requirements carefully!
Click to expand...
Click to collapse
@Cl4ncy is correct. You'd better block OTA (or stay off WiFi) or your device will be pushed to 4.5.4 which present a whole new set of headaches. Word of advice: Read up before taking chances. If you 'can not wait' and start trying stuff at random save yourself some time and just toss your device in the trash now (sorry for the harsh comment).
Hi, no problem I will get a another one and will return the current
For safestrap 4.0.1 I rooted the device and have 4.5.2 - pre conditions fulfilled. Boot loop anyway. So I don't now what else should I do...
The strange string is that my device is showing version 14.3.0.0, even I installed 4.5.2 - that must be a remaining of a script I executed to force the Kindle HDX to update to 4.5.2 (http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204)
(My HDX 8.9 did not take the 4.5.2 update)
messiah said:
Hi, no problem I will get a another one and will return the current
For safestrap 4.0.1 I rooted the device and have 4.5.2 - pre conditions fulfilled. Boot loop anyway. So I don't now what else should I do...
The strange string is that my device is showing version 14.3.0.0, even I installed 4.5.2 - that must be a remaining of a script I executed to force the Kindle HDX to update to 4.5.2 (http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204)
(My HDX 8.9 did not take the 4.5.2 update)
Click to expand...
Click to collapse
Upgrade did not fully complete as evidenced by the mismatch between build.prop version and those shown elsewhere. Who knows what else might be missing. FrankenKindle.
flashed a second device sucessfully to CM 12.1 with unlocked bootloader, thanks for the help!
I just got a 3.0.5 thor from the store.
I'm looking to have root / gapps / and a full backup if my tablet cannot boot.
If a custom rom, like CM11 works well, i'd be good witht that too
after browsing posts, i see people talking bout downgrade to 3.2.8, and hdx toolkit that works on 3.1-3.2.7, and some poepl talking bout 4.2.5 being the one to be on
so basically, i have a super low version, what should I upgrade to, to be able to do all that stuff ^^
wzzupp548 said:
I just got a 3.0.5 thor from the store.
I'm looking to have root / gapps / and a full backup if my tablet cannot boot.
If a custom rom, like CM11 works well, i'd be good witht that too
after browsing posts, i see people talking bout downgrade to 3.2.8, and hdx toolkit that works on 3.1-3.2.7, and some poepl talking bout 4.2.5 being the one to be on
so basically, i have a super low version, what should I upgrade to, to be able to do all that stuff ^^
Click to expand...
Click to collapse
Your best best is to unlock the bootloader (can only be done if the device has never been upgraded past 3.2.6) which will allow you to flash several custom roms including Nexus, CM11 and CM12. Basic steps:
- upgrade to 3.1.0 (stock)
- root and block OTA using HDX toolkit
- flash twrp (custom version for HDX)
- update bootloader to 3.2.3.2 (custom build)
- unlock bootloader (a bit tricky)
- flash the rom of your choice
- enjoy!
Some things you don't want to do:
- connect to wifi without blocking OTA (you'll quickly be ungraded to a higher firmware with fewer options)
- upgrade past 3.2.6 you will permanently loose the ability to unlock your device
There are threads discussing each of these areas. It will take some reading/research. A few of the tasks entail moderate risk; follow instructions carefully. Unlike other android devices if you brick and HDX with a locked bootloader you're pretty much done.
Edit: FireOS versions noted in red have been updated (previously stated 3.2.3 which was incorrect)
thnx, for the help, I shal get started, and let ya know how it goes
Davey126 said:
Your best best is to unlock the bootloader (can only be done if the device has never been upgraded past 3.2.3.2) which will allow you to flash several custom roms including Nexus, CM11 and CM12. Basic steps:
- upgrade to 3.1.0 (stock)
- root and block OTA using HDX toolkit
- flash twrp (custom version for HDX)
- update bootloader to 3.2.3.2 (custom build)
- unlock bootloader (a bit tricky)
- flash the rom of your choice
- enjoy!
Some things you don't want to do:
- connect to wifi without blocking OTA (you'll quickly be ungraded to a higher firmware with fewer options)
- upgrade past 3.2.3 you will permanently loose the ability to unlock your device
There are threads discussing each of these areas. It will take some reading/research. A few of the tasks entail moderate risk; follow instructions carefully. Unlike other android devices if you brick and HDX with a locked bootloader you're pretty much done.
Click to expand...
Click to collapse
Hey, so I purchased a Kindle Fire HDX 7" that came with the 13.3.0.5 firmware.
From what I was able to gather on here I was able to root, and disable the OTA , also installed xposed and HDxposed.
I might have got a little ahead of myself seeing I really want to get the bootloader unlock, twrp installed, and get a proper android OS rom installed.
All the posts I can find seem to be updated to only work on firmware .3.2.3.2 , and by flashing a rom using adb or a third party app to get twrp installed. From there it's smooth sailing to installing a custom rom.
So my question is , how the heck to I upgrade to firmware .3.2.3.2 without twrp already installed, and where can I find these .bins to get there?
Thanks for the help in advance.
Darmoktalk said:
Hey, so I purchased a Kindle Fire HDX 7" that came with the 13.3.0.5 firmware.
From what I was able to gather on here I was able to root, and disable the OTA , also installed xposed and HDxposed.
I might have got a little ahead of myself seeing I really want to get the bootloader unlock, twrp installed, and get a proper android OS rom installed.
All the posts I can find seem to be updated to only work on firmware .3.2.3.2 , and by flashing a rom using adb or a third party app to get twrp installed. From there it's smooth sailing to installing a custom rom.
So my question is , how the heck to I upgrade to firmware .3.2.3.2 without twrp already installed, and where can I find these .bins to get there?
Thanks for the help in advance.
Click to expand...
Click to collapse
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
- (recommended): remove Xposed and HDXposed as they are not needed and may present complications. If you used HDXposed to block OTA remove the block before uininstalling (make sure your device is in airplane mode!) and use HDX toolkit instead (here) which is a tethered solution that offers root and OTA blocking along with other capabilities.
- (optional): sideload ES File Explorer which can be used to locate/manage downloaded files and verify checksums along with a host of other capabilities.
- (optional): sideload Flashify which can be used to back-up your current recovery and flash various components from within a functioning ROM. Back-up your existing recovery and leave on device (small).
- flash twrp (here) using the adb commands shown in the post or Flashify from within FireOS. Be sure to grab the version appropriate to your device. Restart device using power+<vol-up> to validate twrp is working.
- (recommended): from within twrp take a full backup and copy to an external host (just in case ...)
- from twrp upgrade bootloader to 3.2.3.2 (here)
- from twrp backup your device and copy to an external host (very important; don't skip this step)
- (recommended): from twrp flash Nexus v2.0.5 (Jelly Bean) and associated gapps package over FireOS which will give you full access to Google Play and a more flexible platform to work through the bootloader unlock procedure. FireOS is fickle beast; best to remove it from the equation early. Also verifies all is well with twrp.
Bounce back when the above is working and we'll turn to bootloader unlocking. A word of caution: while the above steps are relatively safe any flash gone bad can yield a a non-recoverable brick. Follow the procedures carefully, verify checksums on downloaded images, think twice before acting and don't go off script. Ask questions if unsure. Good luck.
Davey126 said:
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
- (recommended): remove Xposed and HDXposed as they are not needed and may present complications. If you used HDXposed to block OTA remove the block before uininstalling (make sure your device is in airplane mode!) and use HDX toolkit instead (here) which is a tethered solution that offers root and OTA blocking along with other capabilities.
- (optional): sideload ES File Explorer which can be used to locate/manage downloaded files and verify checksums along with a host of other capabilities.
- (optional): sideload Flashify which can be used to back-up your current recovery and flash various components from within a functioning ROM. Back-up your existing recovery and leave on device (small).
- flash twrp (here) using the adb commands shown in the post or Flashify from within FireOS. Be sure to grab the version appropriate to your device. Restart device using power+<vol-up> to validate twrp is working.
- (recommended): from within twrp take a full backup and copy to an external host (just in case ...)
- from twrp upgrade bootloader to 3.2.3.2 (here)
- from twrp backup your device and copy to an external host (very important; don't skip this step)
- (recommended): from twrp flash Nexus v2.0.5 (Jelly Bean) and associated gapps package over FireOS which will give you full access to Google Play and a more flexible platform to work through the bootloader unlock procedure. FireOS is fickle beast; best to remove it from the equation early. Also verifies all is well with twrp.
Bounce back when the above is working and we'll turn to bootloader unlocking. A word of caution: while the above steps are relatively safe any flash gone bad can yield a a non-recoverable brick. Follow the procedures carefully, verify checksums on downloaded images, think twice before acting and don't go off script. Ask questions if unsure. Good luck.
Click to expand...
Click to collapse
Hey, thanks. I was able to get TWRP 2.8.7.0 flashed, and I made a backup first thing.
I ran into a problem however after installing the bootloader upgrade zip, I did a reboot after, and I'm only getting a black screen :/
I managed to get back in TWRP, should I restore that backup, or just move forward with installing the custom rom since I'll be overwriting fireOS anyway?
Thanks.
Ok, so I figured it was just a conflict with the version of FireOS since the recovery seemed to be functioning correctly.
I went ahead and installed the Nexus 2.0.5 rom and gapps. Success.. Boots into the rom fine, I tested some of the google apps, all is nice.
It appears to be working well, so I guess I'd be looking at installing a more updated roms, which needs an unlocked bootloader, yes?
Thanks again.
Darmoktalk said:
Ok, so I figured it was just a conflict with the version of FireOS since the recovery seemed to be functioning correctly.
I went ahead and installed the Nexus 2.0.5 rom and gapps. Success.. Boots into the rom fine, I tested some of the google apps, all is nice.
It appears to be working well, so I guess I'd be looking at installing a more updated roms, which needs an unlocked bootloader, yes?
Thanks again.
Click to expand...
Click to collapse
Great! Was a bit nervous (but not overly worried) after your first response. You took the path I would have recommended (flashing Nexus v2).
Suggestions before moving on to bootloader:
- make a backup of your system w/Nexus (just in case ...)
- reflash 3.2.3.2 bootloader update. There is no test for bootloader version; want to make sure you are on 3.2.3.2
Next step is to make sure you can access fastboot via Windows host. Linux and OSX also work (and are somewhat easier) but most of the tools/tips assume Windows. Take a peek at this post; expand to see full discussion if needed. Bounce back when everything is working. I am on the hunt for a very nice post from @Cl4ncy that details the bootloader unlock procedure. There are several other resources--just though s/he did a good job filling in detail. Stay tuned ...
Edit: A couple bootloader resources for you to ponder:
- procedure including links to various resources (here)
- post from @Cl4ncy referenced above (here)
You'll probably find the material a bit confusing at first. It's easier to answer specific questions than attempt to cover all the nuances. A lot depends on your experience with Android, Windows and the other tools referenced.
BTW - if you are using a 64-bit version of Windows > 8.0 (eg: 8.1, 10) you may need to disable the signed driver check. Bounce back if you have trouble installing the Kindle drivers referenced above.
Good luck - ask for help/clarification if needed!
---------- Post added at 04:00 PM ---------- Previous post was at 03:42 PM ----------
Darmoktalk said:
It appears to be working well, so I guess I'd be looking at installing a more updated roms, which needs an unlocked bootloader, yes?
Click to expand...
Click to collapse
Correct; bootloader needs to be unlocked for HDX variants of CM11, CM12 and Nexus v4 (and probably anything newer that comes along). See previous post for info on BL unlock procedure.
Davey126 said:
Great! Was a bit nervous (but not overly worried) after your first response. You took the path I would have recommended (flashing Nexus v2).
Suggestions before moving on to bootloader:
- make a backup of your system w/Nexus (just in case ...)
- reflash 3.2.3.2 bootloader update. There is no test for bootloader version; want to make sure you are on 3.2.3.2
Next step is to make sure you can access fastboot via Windows host. Linux and OSX also work (and are somewhat easier) but most of the tools/tips assume Windows. Take a peek at this post; expand to see full discussion if needed. Bounce back when everything is working. I am on the hunt for a very nice post from @Cl4ncy that details the bootloader unlock procedure. There are several other resources--just though s/he did a good job filling in detail. Stay tuned ...
Edit: A couple bootloader resources for you to ponder:
- procedure including links to various resources (here)
- post from @Cl4ncy referenced above (here)
You'll probably find the material a bit confusing at first. It's easier to answer specific questions than attempt to cover all the nuances. A lot depends on your experience with Android, Windows and the other tools referenced.
BTW - if you are using a 64-bit version of Windows > 8.0 (eg: 8.1, 10) you may need to disable the signed driver check. Bounce back if you have trouble installing the Kindle drivers referenced above.
Good luck - ask for help/clarification if needed!
---------- Post added at 04:00 PM ---------- Previous post was at 03:42 PM ----------
Correct; bootloader needs to be unlocked for HDX variants of CM11, CM12 and Nexus v4 (and probably anything newer that comes along). See previous post for info on BL unlock procedure.
Click to expand...
Click to collapse
Ok, so I've got adb+fastboot in a folder, booted the HDX into fastboot mode via TWRP restart>bootloader, got the PDAnet drivers installed, issued a fastboot -i 0x1949 devices command, and got a response "D0FBA0A034520HL7 fastboot" .. So it seems like it's talking to my device correctly?
EDIT:
Ok, so I had the eye of tiger and decided to go through with the unlock using CuberHDX.py, mashed my serials together to get my unlock, rebooted to fastboot, issued the flash unlock command for the .unlock file.. All green on my kindle screen "unlock code ok" .. Rebooted, and all is good.
I think.. It's done? Custom recovery, unlocked bootloader.
Darmoktalk said:
Ok, so I've got adb+fastboot in a folder, booted the HDX into fastboot mode via TWRP restart>bootloader, got the PDAnet drivers installed, issued a fastboot -i 0x1949 devices command, and got a response "D0FBA0A034520HL7 fastboot" .. So it seems like it's talking to my device correctly?
EDIT:
Ok, so I had the eye of tiger and decided to go through with the unlock using CuberHDX.py, mashed my serials together to get my unlock, rebooted to fastboot, issued the flash unlock command for the .unlock file.. All green on my kindle screen "unlock code ok" .. Rebooted, and all is good.
I think.. It's done? Custom recovery, unlocked bootloader.
Click to expand...
Click to collapse
TWRP & unlocked bootloader, you're ready for the wonderland of HDX ROMs then.
Be sure to install the correct one for your device, i.e. don't mix up Thor and Apollo ROMs.
Now you can decide, Nexus, CM11 or CM12 - your choice. Read the Installation notes and requirements carefully!
Cl4ncy said:
TWRP & unlocked bootloader, you're ready for the wonderland of HDX ROMs then.
Be sure to install the correct one for your device, i.e. don't mix up Thor and Apollo ROMs.
Now you can decide, Nexus, CM11 or CM12 - your choice. Read the Installation notes and requirements carefully!
Click to expand...
Click to collapse
Darmoktalk said:
Ok, so I've got adb+fastboot in a folder, booted the HDX into fastboot mode via TWRP restart>bootloader, got the PDAnet drivers installed, issued a fastboot -i 0x1949 devices command, and got a response "D0FBA0A034520HL7 fastboot" .. So it seems like it's talking to my device correctly?
EDIT:
Ok, so I had the eye of tiger and decided to go through with the unlock using CuberHDX.py, mashed my serials together to get my unlock, rebooted to fastboot, issued the flash unlock command for the .unlock file.. All green on my kindle screen "unlock code ok" .. Rebooted, and all is good.
I think.. It's done? Custom recovery, unlocked bootloader.
Click to expand...
Click to collapse
Congrats! You're ready to roll. Don't forget the occasional backup; don't flash anything not specifically customized for your device as you can still brick the puppy (although recovery is easier/possible with an unlocked bootloader). ROMs can be snagged from the top of the page (full xda site) or from appropriate threads in the HDX Android development forum. Have fun!
Thank you so much for the help. I came late to the game, and spent a few days reading through all the posts trying to piece together a starting point , and path to make it happen.
Learned a lot, thanks Davey126 for the walktrough and patience, and thanks Cl4ncy for the bootloader unlock instructions.
:good::good::good:
Hopefully this thread will also help others down the line.
Great job, keep it up
Could this be stickied? as it is a great how to/information spot.
Hi Davey126-
I tried following your procedure on a Thor with 13.3.2.8:
Davey126 said:
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
- (recommended): remove Xposed and HDXposed as they are not needed and may present complications. If you used HDXposed to block OTA remove the block before uininstalling (make sure your device is in airplane mode!) and use HDX toolkit instead (here) which is a tethered solution that offers root and OTA blocking along with other capabilities.
- (optional): sideload ES File Explorer which can be used to locate/manage downloaded files and verify checksums along with a host of other capabilities.
- (optional): sideload Flashify which can be used to back-up your current recovery and flash various components from within a functioning ROM. Back-up your existing recovery and leave on device (small).
- flash twrp (here) using the adb commands shown in the post or Flashify from within FireOS. Be sure to grab the version appropriate to your device. Restart device using power+<vol-up> to validate twrp is working.
- (recommended): from within twrp take a full backup and copy to an external host (just in case ...)
- from twrp upgrade bootloader to 3.2.3.2 (here)
Click to expand...
Click to collapse
I'm fine until I try to flash TWRP; using Flashify or ADB seems to work but the unit will not boot into recovery. If I flash the stock recovery back all is well.
Looking at the TWRP download page, there's a note that the bootloader must be unlocked. I used the 1-Click unlocker, and it fails with Unlock Code is NOT correct. I guess my bootloader is not 3.2.3.2
I'm kind of stymied at this point, I'm guessing that I can't start with 13.3.2.8? Any advice on how to proceed would be really appreciated
Bob_in_RI said:
Hi Davey126-
I tried following your procedure on a Thor with 13.3.2.8:
I'm fine until I try to flash TWRP; using Flashify or ADB seems to work but the unit will not boot into recovery. If I flash the stock recovery back all is well.
Looking at the TWRP download page, there's a note that the bootloader must be unlocked. I used the 1-Click unlocker, and it fails with Unlock Code is NOT correct. I guess my bootloader is not 3.2.3.2
I'm kind of stymied at this point, I'm guessing that I can't start with 13.3.2.8? Any advice on how to proceed would be really appreciated
Click to expand...
Click to collapse
You can't unlock or flash TWRP on a tablet with FireOS 3.2.8.
Your only options would be to stay on 3.2.8 and install Safestrap 3, or manually upgrade to 4.5.2 and install Safestrap 4.
Thanks! I was able to install a ton with safestrap.
Davey126 said:
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
Click to expand...
Click to collapse
Will this method also work starting from 13.3.2.4 Firmware or do I have to downgrade somehow first? Thanks.
Nana99 said:
Will this method also work starting from 13.3.2.4 Firmware or do I have to downgrade somehow first? Thanks.
Click to expand...
Click to collapse
You must downgrade first. Good news is you can use the downgrade images provided by @ggow, check page 2 here (page 1 is for 3.2.5/3.2.6 users who can NOT use those images!).
Is your HDX rooted and Safestrap installed? It won't get any easier then.
Any questions ask before you brick your HDX!
After the downgrade you can install TWRP, update the bootloader to 3.2.3.2, then unlock - try the one-click-solution first.
Be sure to create a backup of your current Fire OS via TWRP and move it to your PC before you flash any custom ROM!
Cl4ncy said:
You must downgrade first. Good news is you can use the downgrade images provided by @ggow, check page 2 here (page 1 is for 3.2.5/3.2.6 users who can NOT use those images!).
Is your HDX rooted and Safestrap installed? It won't get any easier then.
Any questions ask before you brick your HDX!
After the downgrade you can install TWRP, update the bootloader to 3.2.3.2, then unlock - try the one-click-solution first.
Be sure to create a backup of your current Fire OS via TWRP and move it to your PC before you flash any custom ROM!
Click to expand...
Click to collapse
Thanks. Yes my HDX is rooted and safestrap als well as Xposed and HDXposed is installed. I did all this over year ago shortly after I bought the device and never really touched it since then. However over time many things have stopped working correctly so I do want to upgrade to a more stabel version with gapps working or to a custom rom.
Please tell me which Firmware I have to downgrade to. Is it 3.1.0 or 3.2.3.2?
Thanks again for your support.
Nana99 said:
Thanks. Yes my HDX is rooted and safestrap als well as Xposed and HDXposed is installed. I did all this over year ago shortly after I bought the device and never really touched it since then. However over time many things have stopped working correctly so I do want to upgrade to a more stabel version with gapps working or to a custom rom.
Please tell me which Firmware I have to downgrade to. Is it 3.1.0 or 3.2.3.2?
Thanks again for your support.
Click to expand...
Click to collapse
The downgrade image is a modified 3.2.4 which claims to be 3.0.9, so you can "update" to 3.1.0, which is enough to install TWRP 2.8.7.0 (I'm not sure about TWRP 3.0.0-0, so install 2.8.7.0 and update to 3.0.0-0 via TWRP itself later, if you want to). There's no need to update to 3.2.3.2 then, as you can just update the bootloader (see above), which you should do via TWRP to solve a screen grafic issue.
Keep WLAN off/flight mode active during the procedure, you don't want to get updated by Amazon!
Cl4ncy said:
The downgrade image is a modified 3.2.4 which claims to be 3.0.9, so you can "update" to 3.1.0, which is enough to install TWRP 2.8.7.0 (I'm not sure about TWRP 3.0.0-0, so install 2.8.7.0 and update to 3.0.0-0 via TWRP itself later, if you want to). There's no need to update to 3.2.3.2 then, as you can just update the bootloader (see above), which you should do via TWRP to solve a screen grafic issue.
Keep WLAN off/flight mode active during the procedure, you don't want to get updated by Amazon!
Click to expand...
Click to collapse
Thanks once again. Everything worked perfectly. I downgraded with 3.2.4_rollback and "upgraded" to 3.1.0, rooted and installed twrp. Then updated the bootloader and installed nexus 2.05. Then unlocked the bootloader with 1-click. I then installed the nexus 4.0.5 rom along with the gapps. After that I installed CM13 together with open gapps and super-su.
Couldn't have done it without your help!!!:good::good::good:
Nana99 said:
Thanks once again. Everything worked perfectly. I downgraded with 3.2.4_rollback and "upgraded" to 3.1.0, rooted and installed twrp. Then updated the bootloader and installed nexus 2.05. Then unlocked the bootloader with 1-click. I then installed the nexus 4.0.5 rom along with the gapps. After that I installed CM13 together with open gapps and super-su.
Couldn't have done it without your help!!!:good::good::good:
Click to expand...
Click to collapse
Great! Enjoy your "free" HDX.