Hey everyone I recently bricked my kindle fire because I was not careful enough about loading a custom ROM. Long story short I followed the instructions for a kindle fire HD7 instead of HDX7. Luckily, Amazon's customer service is WAY better than their operating systems because I was able to return my bricked device and get a new one within 3 days!
That being said, I was wondering if anyone here could provide a good, clear guide, or at least overview of the steps I need to take to install cyanogenmod 11 or some other custom ROM on my kindle fire hdx 7. I have been searching for a decent guide, but haven't been able to find one. Links to actual resources would be even better. I don't mind searching on my own, but I need at least enough information to not screw up my device again. Any help anyone could give me would be very appreciated! Thank you!
and just for reference my device is Kindle Fire HDX 7" THOR currently running FireOS 4.5.5
tropicallazerbeams said:
Hey everyone I recently bricked my kindle fire because I was not careful enough about loading a custom ROM. Long story short I followed the instructions for a kindle fire HD7 instead of HDX7. Luckily, Amazon's customer service is WAY better than their operating systems because I was able to return my bricked device and get a new one within 3 days!
That being said, I was wondering if anyone here could provide a good, clear guide, or at least overview of the steps I need to take to install cyanogenmod 11 or some other custom ROM on my kindle fire hdx 7. I have been searching for a decent guide, but haven't been able to find one. Links to actual resources would be even better. I don't mind searching on my own, but I need at least enough information to not screw up my device again. Any help anyone could give me would be very appreciated! Thank you!
and just for reference my device is Kindle Fire HDX 7" THOR currently running FireOS 4.5.5
Click to expand...
Click to collapse
Amazon support is usually quite responsive. Be aware device replacement for software issues under warranty is a one-time courtesy. You own the replacement (actually a refurb).
High level steps required to prep your device for CM11 (or Nexus v4):
- rollback to FireOS 3.2.8
- upgrade to FireOS 4.5.2
- root with Kingroot or other method
- block OTA (over-the-air updates) - step #1
- install Safestrap v4
- flash a Safestrap v4 compatible rom (currently CM11 or Nexus v4)
The above links are NOT click and execute! There are no step-by-step guides, helpful videos, comprehensive tutorials (despite titles suggesting otherwise), etc. You have to dive into the forums and wade through hundreds of posts (many off-topic/extraneous) to get feel for the detailed procedures. There are some outstanding posts but you'll need to find them. Be aware some steps carry significant risks including a full-on brick from which there is no recovery. Read instructions carefully and be sure to ask questions before taking action.
A few tips:
- download everything you need in advance storing them in uniquely named folders. Some steps mandate your HDX be isolated from any networks. While most items can be retrieved via USB tether it is much easier to simply head for the folder on your HDX when the file is needed.
- understand what USB debug means and know how to enable in FireOS
- install minimal adb + fastboot and learn basic adb commands such as 'install' and 'push'
- ES File Explorer is your friend; alway keep a copy of the apk on your device for installation when needed.
- never perform a 'factory reset' unless specifically advised to do so by someone experienced with HDX devices; many sad tales begin with 'I did a factor reset ...'
Good luck.
Wow, awesome, this was exactly what I was looking for. I just finished installing CM11, the whole process took me about an hour now that I understand what to do. Thanks for the guide, I have a feeling this will help more people than just me. I would add one more step for anyone else looking: When installing your custom ROM, go ahead and install gapps (https://wiki.cyanogenmod.org/w/Google_Apps) so that you can access the google play store from your new ROM.
Here are some decent video guides on how to use Safestrap in case anyone needed help with that:
(https://www.youtube.com/watch?v=K6fPF5UZsWw) General Safestrap usage
(https://www.youtube.com/watch?v=xR0WXCITq2Q) Specifically how to install a custom ROM
So I have just a few more questions now, CM11 can only access about 8 out of the 16GB on the device. Is there a way to expand that memory to the entire 16GB? I should probably just be satisfied with my progress so far, but I honestly would not miss the stock fireOS if it would give me more space.
When/if I need to update CM, do I need to flash each and every update via recovery?
Thanks for all the help so far, you da man!
tropicallazerbeams said:
Wow, awesome, this was exactly what I was looking for. I just finished installing CM11, the whole process took me about an hour now that I understand what to do. Thanks for the guide, I have a feeling this will help more people than just me. I would add one more step for anyone else looking: When installing your custom ROM, go ahead and install gapps (https://wiki.cyanogenmod.org/w/Google_Apps) so that you can access the google play store from your new ROM.
Here are some decent video guides on how to use Safestrap in case anyone needed help with that:
(https://www.youtube.com/watch?v=K6fPF5UZsWw) General Safestrap usage
(https://www.youtube.com/watch?v=xR0WXCITq2Q) Specifically how to install a custom ROM
So I have just a few more questions now, CM11 can only access about 8 out of the 16GB on the device. Is there a way to expand that memory to the entire 16GB? I should probably just be satisfied with my progress so far, but I honestly would not miss the stock fireOS if it would give me more space.
When/if I need to update CM, do I need to flash each and every update via recovery?
Thanks for all the help so far, you da man!
Click to expand...
Click to collapse
Based on a few reports CM11 works best in the stock slot. Seems WiFi won't enter a low power state in secondary slots resulting in excessive battery drain. Thoughts:
- backup up stock slot in SS recovery. Save archive off-device.
- backup cm11 slot, switch to slot slot and restore
- after stock slot w/cm11 confirmed ok delete secondary slot(s)
You'll have access to the full 16GB with ability to restore FireOS if needed.
---------- Post added at 08:00 AM ---------- Previous post was at 07:55 AM ----------
tropicallazerbeams said:
Here are some decent video guides on how to use Safestrap in case anyone needed help with that:
(https://www.youtube.com/watch?v=K6fPF5UZsWw) General Safestrap usage
(https://www.youtube.com/watch?v=xR0WXCITq2Q) Specifically how to install a custom ROM
Click to expand...
Click to collapse
Thanks - nice find.
@ggow - possible add to SS v4 OP or separate thread for newbies.
tropicallazerbeams said:
Wow, awesome, this was exactly what I was looking for. I just finished installing CM11, the whole process took me about an hour now that I understand what to do. Thanks for the guide, I have a feeling this will help more people than just me. I would add one more step for anyone else looking: When installing your custom ROM, go ahead and install gapps (https://wiki.cyanogenmod.org/w/Google_Apps) so that you can access the google play store from your new ROM.
Here are some decent video guides on how to use Safestrap in case anyone needed help with that:
(https://www.youtube.com/watch?v=K6fPF5UZsWw) General Safestrap usage
(https://www.youtube.com/watch?v=xR0WXCITq2Q) Specifically how to install a custom ROM
So I have just a few more questions now, CM11 can only access about 8 out of the 16GB on the device. Is there a way to expand that memory to the entire 16GB? I should probably just be satisfied with my progress so far, but I honestly would not miss the stock fireOS if it would give me more space.
When/if I need to update CM, do I need to flash each and every update via recovery?
Thanks for all the help so far, you da man!
Click to expand...
Click to collapse
Davey126 said:
Based on a few reports CM11 works best in the stock slot. Seems WiFi won't enter a low power state in secondary slots resulting in excessive battery drain. Thoughts:
- backup up stock slot in SS recovery. Save archive off-device.
- backup cm11 slot, switch to slot slot and restore
- after stock slot w/cm11 confirmed ok delete secondary slot(s)
You'll have access to the full 16GB with ability to restore FireOS if needed.
---------- Post added at 08:00 AM ---------- Previous post was at 07:55 AM ----------
Thanks - nice find.
@ggow - possible add to SS v4 OP or separate thread for newbies.
Click to expand...
Click to collapse
- Added links to the OP of Safestrap 4.0.1 thread
Okay I ran into one more problem. I followed your instructions on switching ROM-1 to ROM-STOCK, but when I was restoring the contents of ROM-1 to ROM-STOCK, the procedure failed. It didn't say why, it just showed up in red text saying "failed". So it rebooted, but since ROM-STOCK was selected and a restoration had just failed on it, nothing happens when I boot up. It is stuck on the grey kindle fire logo. Is there a way that I can get into safestrap?
tropicallazerbeams said:
Okay I ran into one more problem. I followed your instructions on switching ROM-1 to ROM-STOCK, but when I was restoring the contents of ROM-1 to ROM-STOCK, the procedure failed. It didn't say why, it just showed up in red text saying "failed". So it rebooted, but since ROM-STOCK was selected and a restoration had just failed on it, nothing happens when I boot up. It is stuck on the grey kindle fire logo. Is there a way that I can get into safestrap?
Click to expand...
Click to collapse
Well crap - that's not good. The symptoms suggest Safestrap v4 may have been damaged. I assume you tried waiting, rebooted multiple times, powered off/on, etc. Is there any indication Safestrap (or any environment beyond the grey boot screen) is present?
hehe, looks like I may have bricked my 2nd Fire....Tried waiting, rebooting and everything, still broke..... So Safestrap never really appeared to be damaged when it was rebooting after the installation failure. If I had to guess, I would say that ROM-1 and safestrap are totally fine, the only problem is that I can't access them because ROM-STOCK is selected. So what if I got my hands on one of those factory fastboot cables, do you think I could boot straight into fastboot, change my boot options to boot into recovery or my ROM-1?
tropicallazerbeams said:
hehe, looks like I may have bricked my 2nd Fire....Tried waiting, rebooting and everything, still broke..... So Safestrap never really appeared to be damaged when it was rebooting after the installation failure. If I had to guess, I would say that ROM-1 and safestrap are totally fine, the only problem is that I can't access them because ROM-STOCK is selected. So what if I got my hands on one of those factory fastboot cables, do you think I could boot straight into fastboot, change my boot options to boot into recovery or my ROM-1?
Click to expand...
Click to collapse
Sorry, with locked bootloader fastboot mode on HDX is practically useless, factory cable won't help you. Did you by any chance when you created ROM-1 slot changed data partition to bigger size? That would explain why restoration to STOCK slot failed. If you can't enter safestrap recovery at boot time, that means it IS damaged.
Yeah I did change the partition size when I created ROM-1. Thanks for all the help fellas, but it looks like I am right back where I started. Good thing my tablet was a gift
Im going to follow the process since I have at 4.5.2 rooted before.
How do I create the rom-1 to later install on stock without brick?
Or I should install directly to stock without doing rom-1?
alberto1414 said:
Im going to follow the process since I have at 4.5.2 rooted before.
How do I create the rom-1 to later install on stock without brick?
Or I should install directly to stock without doing rom-1?
Click to expand...
Click to collapse
Review the video in the Safestrap v4 OP for general usage info. For a variety of reasons I recommend only using the stock slot in SS v4. You should create a backup of the stock slot containing FireOS before flashing a new rom. Keep a copy off-device.
http://forum.xda-developers.com/showthread.php?p=61410598
Davey126 said:
Review the video in the Safestrap v4 OP for general usage info. For a variety of reasons I recommend only using the stock slot in SS v4. You should create a backup of the stock slot containing FireOS before flashing a new rom. Keep a copy off-device.
http://forum.xda-developers.com/showthread.php?p=61410598
Click to expand...
Click to collapse
When being on safestrap after back up the stock slot.
do I have to do anything before flashing the new rom? like some wipes os what?
Can help with steps?
1. wipe? what to wipe?
2. flash?
3. factory reset?
I saw the instructions on the hdx nexus v4. but it doesnt say anything before flash. I think they talk about a new rom slot. but mine has the fire os.
alberto1414 said:
When being on safestrap after back up the stock slot.
do I have to do anything before flashing the new rom? like some wipes os what?
Can help with steps?
1. wipe? what to wipe?
2. flash?
3. factory reset?
I saw the instructions on the hdx nexus v4. but it doesnt say anything before flash. I think they talk about a new rom slot. but mine has the fire os.
Click to expand...
Click to collapse
I suggest you do some additional reading to gain confidence in the process. Briefly:
- backup the stock rom slot before taking any other action (use backup option within Safestrap v4)
- nothing needs to be done before flashing a new rom (Nexus v4 or CM11 only)
- each rom has its own requirements but in general performing a factory reset from within Safestrap is recommended. This is NOT the same thing as doing a factory reset from the Kindle recovery menu. Never to that unless instructed by an experienced member of the community.
While others may be willing to do so I will not provide a 'step-by-step' as all the information you need is one of the following threads. Reading and gaining confidence the the best way to avoid a mistake that could cripple your device. Community members are happy to answer specific questions as you become familiar with the details.
Safestrap v4
Nexus v4
CM11 for HDX (Safestrap build)
Read through posts now, thanks for the help
m1kemyer5 said:
Read through posts now, thanks for the help
Click to expand...
Click to collapse
Just one note: if it says factory reset in the installation notes it's the standard wipe only, i.e. you open the wipe menu, and swipe to wipe - do NOT go into advanced wipe!
Now it so happens @ggow implemented a System-wipe-protection in Safestrap v4 to prevent more bricked devices, but usually you should NOT have any reason to open the advanced wipe menu. Wiping System in Safestrap v3.7x is lethal (doesn't concern Safestrap v4 users, but can't be mentioned often enough).
Hi to all looking to have a custom rom, I recommend CM11 because it gives you a safe try and the wifi works.
Many new people trying nexus v4 are stuck.
If you like me, new to these things go with CM11.
I started with fire os 4.5.5 and downgrade to 3.2.8 to later upgrade to 4.5.2 , root and safestrap 4. create a new rom slot with default(no modification on size). to later install there the CM11 and everything without touching the stock slot of fire os 4.5.2.
If any one wants my personal experience, simple PM I'll be glad to help. just in this particular situation I just explained.
Thanks to the dev that made this posible.
alberto1414 said:
Hi to all looking to have a custom rom, I recommend CM11 because it gives you a safe try and the wifi works.
Many new people trying nexus v4 are stuck.
If you like me, new to these things go with CM11.
I started with fire os 4.5.5 and downgrade to 3.2.8 to later upgrade to 4.5.2 , root and safestrap 4. create a new rom slot with default(no modification on size). to later install there the CM11 and everything without touching the stock slot of fire os 4.5.2.
If any one wants my personal experience, simple PM I'll be glad to help. just in this particular situation I just explained.
Thanks to the dev that made this posible.
Click to expand...
Click to collapse
Quick clarifications to @alberto1414's comments:
- both Nexus v4 and CM11 run equally well in the stock (default) slot of Safestrap v4. There is no significant difference in stability or performance.
- creating one or more secondary slots allows multiple roms to reside on the device at the same time; a reboot is required to switch between roms.
- CM11 can function in a secondary slot; Nexus v4 and FireOS v4 can not as WiFi only works in the stock slot.
- flashing either Nexus v4 or CM11 to the stock slot overwrites FireOS; however this is not a problem as FireOS v4.5.2 can be restored at a later time either from a backup created by the user or as a 'fresh' install using a custom version available here.
- individuals who flashed Nexus v4 to the stock slot are not "stuck"; they can restore or reinstall FireOS 4.5.2 as outlined above.
- creating/using a secondary slot in Safestrap v4 significantly increases battery consumption. Root cause has yet to be identified but it appears the device never enters 'deep sleep' when secondary slots are in use.
- permanent device storage is shared across slots. This can become a problem on 16GB or 32GB devices. In contrast, all available storage is available to the stock slot if secondary slots are not created.
- Safestrap compatible roms are created/tested in the stock slot. Functionality and stability in secondary slots is not assured.
Related
My KF HDX 7 is in 13.3.2.1, I had tried to up Gapps rom v2 but it don't work, I must factory reset and go back to stock rom.
Is there any rom that can my kindle can up???
Sory for my bad English
none.
tuilakhang said:
My KF HDX 7 is in 13.3.2.1, I had tried to up Gapps rom v2 but it don't work, I must factory reset and go back to stock rom.
Is there any rom that can my kindle can up???
Sory for my bad English
Click to expand...
Click to collapse
Do a manual upate to 13.3.2.2 ,root then the new thor rom will work with safestrap 3.75b02
jimyv said:
Do a manual upate to 13.3.2.2 ,root then the new thor rom will work with safestrap 3.75b02
Click to expand...
Click to collapse
Can you give me a link of 13.3.2.2 cause I had searched around but can't saw any link but 13.3.2.4
ok
tuilakhang said:
Can you give me a link of 13.3.2.2 cause I had searched around but can't saw any link but 13.3.2.4
Click to expand...
Click to collapse
There are multiple pages to these forums, for example if you open up the general section and you look at the bottom of the page it gives you option to go to the next page several pages worth of information there same goes with each subsection. There is also a( search this thread) option in the right upper of your page. If you are still reading by chance and you will find that updates you need for either Apollo or Thor on the bottom of page four in the general section.
Didnt already bricked one of your devices here? If you are one of the fellows that bricked I would advise you to learn how to use these forums efficiently before you break another device. If not then at the very least you need to do more homework at least figure out how to use this site efficiently into everyone's benefits. Most of us are here to help those that first at least are trying to help themselves. Good luck and enjoy.
Apparently pressing "ESC" in this window deletes all the text without being able to undo this.... so here goes again....
Sorry for the late reply, but i just saw your post in the developer's forum (Cpasjuste's Thor Gapps), where i cannot post due to my lurker nature.
i'm on the same FireOS version as you: 13.3.2.1
i had trouble getting Cpasjuste's ROM to work, because i was trying to use thor-gapps-13.3.0.0-v2. i didn't dare using thor-gapps-13.3.2.4-v1, because of the several warnings.
i then saw someone else having success with thor-gapps-13.3.2.4-v1 on an earlier version and thought i'd give it a try after all. i took the risk of closing the door to an unlocked bootloader, i took the risk of bricking my device. i decided to do this, because of my year long experience with custom ROMs, also on devices that were not intended to have them (Nook HD+, Kindle Fire...). i'm not sure, if the kernel is touched during the flash process, but i assum(ed) it isn't. i can boot into FireOS which still shows 13.3.2.1 as version, but who knows what has happened under the hood.
The ROM feels stable so far for such an early version. i haven't tested much, but the few apps I've been using regularly worked well. Ironically the amazon appstore crashed after about 20 seconds. Makes me think they are trying to block the "freed" devices, but it might just be a bug after all.
So, again, if you feel like risking to lose the possibility of an unlocked bootloader, if you want to risk or can afford to brick such an expensive device, you can try using thor-gapps-13.3.2.4-v1.
All i did, was to follow the instructions provided in Cpasjuste's thread exactly as they were.
Don't hold me accountable, it's already been a week, but if i recall correctly, these were my steps:
DIsable WiFi / Enable Airplane mode in FireOS (just to prevent automatic OTA updates)
Root device (i used towelroot)
Install Safestrap (i had to use Safestrap-Thor-3.75-os3.2.4-B02.apk, despite the instructions in the safestrap thread telling to use 3.72 on our version - another risk i took)
Boot into Safestrap
Backup Original ROM
Create ROM Slot (keep this new slot active/activated)
Restore Original ROM backup, but only the DATA partition
Wipe Cache + Dalvik Cache
Flash thor-gapps-13.3.2.4-v1.zip
Wipe Cache + Dalvik Cache
Boot into system
Q&A for [APOLLO/RECOVERY LOCKED] Safestrap Recovery v3.72/v3.75 [B02 2014-07-03]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [APOLLO/RECOVERY LOCKED] Safestrap Recovery v3.72/v3.75 [B02 2014-07-03]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Fire HDX 8.9 vs Kindle Fire HDX 8.9
Okay, so I have noticed that Hashcode built this for both the 7" and 8.9" versions of the Kindle Fire HDX, but does the 8.9" version here: http://forum.xda-developers.com/showthread.php?t=2612772
Does this support the 3rd generation Fire HDX 8.9" version? I noticed that the download links say it supports systems earlier than 14.3.2.1 and later than 14.3.2.1, but does it support the newer Fire HDX 8.9" system 4.1.1? Judging from what I have researched, I believe that there isn't much difference between 14.3.2.1 and 4.1.1. Has anyone tried to root or install CM on this newest version of the HDX 8.9 yet?
Thanks in advance.
WickdWzrd said:
Okay, so I have noticed that Hashcode built this for both the 7" and 8.9" versions of the Kindle Fire HDX, but does the 8.9" version here: http://forum.xda-developers.com/showthread.php?t=2612772
Does this support the 3rd generation Fire HDX 8.9" version? I noticed that the download links say it supports systems earlier than 14.3.2.1 and later than 14.3.2.1, but does it support the newer Fire HDX 8.9" system 4.1.1? Judging from what I have researched, I believe that there isn't much difference between 14.3.2.1 and 4.1.1. Has anyone tried to root or install CM on this newest version of the HDX 8.9 yet?
Thanks in advance.
Click to expand...
Click to collapse
No, it's not possible to mod FireOS 4 in any way.
Safestrap apk for Kindle Fire HDX 14.3.2.3.2
Hi I'm trying to install safestrap on my kfhdx, but all the links in the forums seem to be broken. Any suggestions on where I can find this download? Thanks a lot
j1mbo83 said:
Hi I'm trying to install safestrap on my kfhdx, but all the links in the forums seem to be broken. Any suggestions on where I can find this download? Thanks a lot
Click to expand...
Click to collapse
Available here.
Although I'm not sure why you want to install safestrap as the firmware version you are running (self reported as 14.3.2.3.2) permits flashing 'native' twrp which is far more robust. From there you can flash CM11 or Nexus 2.0.5. With a bit of work you can also unlock your bootloader which opens the door to CM12 and Nexus 4.x. None of these roms work with safestrap.
Safestrap is a primary used by those who cannot flash 'native' twrp (most newer Kindles) and/or if you wish to toggle between Fire OS and Nexus 1.01. Those are the only roms that work with safestrap. Also note you must take steps to block OTA while using Safestrap or risk bricking your device. At present the only method that works reliably is HDX toolkit.
Thanks for the reply, I'm obviously new to this but I've rooted my Kindle, installed Google play, but recently Google has been forcing updates of play services and I'm afraid to mess with anything else until I can either unlock bootloader it install custom recovery, if you could point me in the right direction on how to do this I'd appreciate it. Didn't know I could install twrp. Any directions in layman's terms would help, thanks.
j1mbo83 said:
Thanks for the reply, I'm obviously new to this but I've rooted my Kindle, installed Google play, but recently Google has been forcing updates of play services and I'm afraid to mess with anything else until I can either unlock bootloader it install custom recovery, if you could point me in the right direction on how to do this I'd appreciate it. Didn't know I could install twrp. Any directions in layman's terms would help, thanks.
Click to expand...
Click to collapse
Installing a custom recovery (twrp) is straight forward given your version of Fire OS. Please confirm you really are on v14.3.2.3.2 and OTA (over-the-air) updates have been blocked and if so, via which method. Did you roll your device back from a higher firmware version? Sorry for all the questions - want to make sure the foundation is solid before taking next steps.
Outline to install custom recovery:
- side load Flashify (here). You can also find/install this from Play Store if working on your device.
- download custom twrp (here); you want Apollo v2.8.6.0
- use Flashify to backup your current recovery (don't skip this step)
- use Flashify to flash (install) the twrp recovery image previously downloaded. You must use this image; don't go downloading/flashing a generic version!
When complete you device will reboot back into Fire OS as if nothing changed. You can verify twrp was correctly installed by powering down and then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears; release the vol-up button a few seconds alter. After a few moments a blue logo should appear and you will enter twrp recovery. Have a look around but don't change anything. Reboot you device and post back for further instructions (actually information on next steps; where the fun begins!) .
Be aware that any type of flashing can render your device unusable. The steps outlined above are relatively safe if you follow directions carefully and double check each action before executing. Ask questions in advance; don't panic and start doing unscripted stuff if something goes wrong.
I am running v14.3.2.3.2, I rooted the kindle and blocked OTA updates using hdx toolkit. I did this maybe about 7 months ago and never rolled back. Will these directions still work for me?
j1mbo83 said:
I am running v14.3.2.3.2, I rooted the kindle and blocked OTA updates using hdx toolkit. I did this maybe about 7 months ago and never rolled back. Will these directions still work for me?
Click to expand...
Click to collapse
Looks good. Just go slow and double check each step. Once twrp is installed and confirmed working you can then flash either the Nexus or CM11 rom which will give you unfettered access to the Play store and all the goodness of a 'generic' android device. Effectively your Kindle looses its identity as an Amazon tablet. Nexus (what I use) has proven rock solid but is getting a bit long in the tooth. CM11 is based on KitKat and only has a minor issues with bluetooth, LTE and occasionally wifi. Most users of this rom are quite happy and can easily work around the issues.
Prior to flashing a new rom you should make a complete backup of your current system in twrp and then store that image on another device. Also keep in mind that once you flash twrp it is very difficult to restore your device to full 'stock'. Assume a one way trip.
Edit: Forgot to mention LTE. At present none of the roms support LTE but that will likely change in the near future. If you have an LTE enabled tablet you'll have to decide if that or play store access is more important.
Thanks. Ok I installed flashify, then followed your link to download and install twrp and it has a note at the top that says to unlock boot loader. I don't think it is unlocked. How do I check this? And if it isn't, how would I go about unlocking it?
---------- Post added at 09:00 PM ---------- Previous post was at 08:11 PM ----------
Ok I successfully installed twrp, created a backup, and saved it to another device. Ready for the next step. Thanks for all your help.
Congrats. If you are asking how to know if you are unlocked, chances are good it is locked. You do not need to unlock the bootloader, but it is highly recommended as once successfully unlocked it is another failsafe, and opens up other roms (like cm 12). To unlock it, I suggest grabbing Draxie's automated (slightly) script from the original dev section. Know that the act of unlocking the bootloader is difficult, and will require you to learn more about your device, but it does pay off in the end.
j1mbo83 said:
Thanks. Ok I installed flashify, then followed your link to download and install twrp and it has a note at the top that says to unlock boot loader. I don't think it is unlocked. How do I check this? And if it isn't, how would I go about unlocking it?
---------- Post added at 09:00 PM ---------- Previous post was at 08:11 PM ----------
Ok I successfully installed twrp, created a backup, and saved it to another device. Ready for the next step. Thanks for all your help.
Click to expand...
Click to collapse
Congrats!! See post from lekofraggle (here) which I fully agree with. However, I think you can defer the bootloader unlock for a little while recognizing that it provides an important failsafe should you bork your device and is a prerequisite for some roms (eg: CM12).
Next step involves flashing a rom of your choice. Recognize all aps/data will be wiped; you'll be starting clean. However, anything previously purchased in the play store can be downloaded again assuming you use the same credentials when setting up accounts on the 'new' rom.
Choices:
- Nexus 2.0.5: JellyBean based, rock solid, near AOSP (unmodified Android). Info/links here.
- CM11: KitKat based, popular across numerous Android devices with useful extensions baked in. Some minor BT/WiFi flakiness on HDX devices. Info/links here.
Both roms can also be downloaded using the ROMs tab at the top of this page. Don't go trying anything else. You want HDX Nexus or CM11-Apollo. Magic Beans will also work but carries no significant advantage over the other two and hasn't see much development in recent months.
All ROMs can be flashed from twrp. Be sure to make a backup of your current environment first. Use caution in twrp if you are new to the tool; it's easy to mess things up including a full brick of your device.
I recommend you start with Nexus. It's a great rom that will serve you well; an upgrade (KitKat) is in the works and should be released in the not-too-distant future. CM11 is also a fine choice and offers greater compatibility with some of the more recent app releases. Both are further customizable via Xposed Framework but that's another discussion.
Ok thanks, I downloaded the zips, now I have just one more question (I know, I have a lot...). Do I need to wipe my system before installing new Rom?
j1mbo83 said:
Ok thanks, I downloaded the zips, now I have just one more question (I know, I have a lot...). Do I need to wipe my system before installing new Rom?
Click to expand...
Click to collapse
Keep asking! Lots of devices have died in the hands of ignorant users (not intended to be an insult...were are all ignorant until educated).
In theory you do not need to wipe the device but there have been scattered reports of strange behaviors after performing a 'dirty' flash. My recommendation is to perform a factory reset (under wipe) from within twrp. This will clear data, cache and dalvik while leaving system and internal storage intact. If you opt for an "advanced wipe" select the previous 3 plus system; leave internal storage alone. Do not format or repair; just asking for trouble.
As always make a backup before proceeding and store a copy of that off-device. Short term keep a copy on the device along with the rom image just in case you have to redo something and can't connect via tether. Rare but it does happen.
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
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?
Background: My kindle hdx 8.9 3rd gen was running FireOS 4.5.1 , then installed the kingroot, after that safestrap v4. Having the SS recovery installed, i make attempt to replace kingroot with supersu by flasing supersu v2. 46. It got stuck at logo white-yellow. I do a manufactory reset but still no hope.
Stupid me for not backing up the stock rom since i was confidence in the past was able to do it flawlessly.
Right now:
SS Recovery is accessible
ADB/Fastboot is accessible
Locked bootloader.
Any help would be appriciated.
firebird21 said:
Background: My kindle hdx 8.9 3rd gen was running FireOS 4.5.1 , then installed the kingroot, after that safestrap v4. Having the SS recovery installed, i make attempt to replace kingroot with supersu by flasing supersu v2. 46. It got stuck at logo white-yellow. I do a manufactory reset but still no hope.
Stupid me for not backing up the stock rom since i was confidence in the past was able to do it flawlessly.
Right now:
SS Recovery is accessible
ADB/Fastboot is accessible
Locked bootloader.
Any help would be appriciated.
Click to expand...
Click to collapse
- boot into Safestrap recovery
- use 'adb push' to copy the Fire Nexus install zip (here) to your device
- flash/install Nexus to the STOCK slot (includes GAaps and SuperSU)
You can switch to CM11 later if desired (overwrite Nexus in the STOCK slot) or move forward with unlocking the bootloader for access to the full suite of HDX roms.
Davey126 said:
- boot into Safestrap recovery
- use 'adb push' to copy the Fire Nexus install zip (here) to your device
- flash/install Nexus to the STOCK slot (includes GAaps and SuperSU)
You can switch to CM11 later if desired (overwrite Nexus in the STOCK slot) or move forward with unlocking the bootloader for access to the full suite of HDX roms.
Click to expand...
Click to collapse
Thank you for the quick answer.
Would install original stock OS be possible? in case i want to return it to amazon? Just bought it a week ago.
firebird21 said:
Thank you for the quick answer.
Would install original stock OS be possible? in case i want to return it to amazon? Just bought it a week ago.
Click to expand...
Click to collapse
Yes - but start with Nexus to get the device up and running with minimal risk. Reinstalling FireOS presents a few challenges given your previous actions. Post back if/when ready. Guessing you will want to stay on Nexus or go further and unlock the bootloader.
Davey126 said:
Yes - but start with Nexus to get the device up and running with minimal risk. Reinstalling FireOS presents a few challenges given your previous actions. Post back if/when ready. Guessing you will want to stay on Nexus or go further and unlock the bootloader.
Click to expand...
Click to collapse
It seems like the nexus has the same symptom. It's stucked at the loading logo.
firebird21 said:
It seems like the nexus has the same symptom. It's stucked at the loading logo.
Click to expand...
Click to collapse
Return to Safestrap recovery and perform a factory reset from the wipe menu (slider at bottom). Then reflash Nexus ROM.
Davey126 said:
Return to Safestrap recovery and perform a factory reset from the wipe menu (slider at bottom). Then reflash Nexus ROM.
Click to expand...
Click to collapse
Yes, this time it works.
firebird21 said:
Yes, this time it works.
Click to expand...
Click to collapse
Great. Enjoy your liberated HDX!
Davey126 said:
Great. Enjoy your liberated HDX!
Click to expand...
Click to collapse
Since the ROM was installed in Stock slot, should i be precautious of doing anything in future? I read the safestrap v4 thread that wifi will not work in second slot right, any update on this?
firebird21 said:
Since the ROM was installed in Stock slot, should i be precautious of doing anything in future? I read the safestrap v4 thread that wifi will not work in second slot right, any update on this?
Click to expand...
Click to collapse
No special precautions as some earlier limitations have been lifted. Avoid performing a factory reset from the native (not Safestrap) recovery menu as it can yield an unresponsive device that occasionally can not be recovered. Also try to keep a rom zip on the device at all times for emergency recovery.
Safestrap v4 is a special build for HDX with primary emphasis on allowing custom ROMs to run on a locked device running the native FireOS v4 kernel. There was never a need or intent to leverage secondary slots as was the case with Safestrap v3; in hindsight the developer probably should have disabled them. Aside from WiFi/BT radio issues processor management is also whacked. Only 2 of 4 processors will go online and both operate at maximum frequency. As a result the device never sleeps, performs poorly and has lousy battery life. None of these problems arise in the STOCK slot.
Keep in mind all 3rd gen devices can now be unlocked eliminating the need for Safestrap and opening the door to the full suite of custom ROMs including KitKat, Lollipop and Marshmallow variants. Unfortunately, the process is a bit involved as most steps are manual and require some technical experience.
Enjoy Nexus for now; it's a fine ROM that is fast, lean and energy efficient. Not to mention full access to Google Play Store/Services/apps and the ideal platform for Xposed extensions if you want even greater control over the hardware and user interface.
Davey126 said:
No special precautions as some earlier limitations have been lifted. Avoid performing a factory reset from the native (not Safestrap) recovery menu as it can yield an unresponsive device that occasionally can not be recovered. Also try to keep a rom zip on the device at all times for emergency recovery.
Safestrap v4 is a special build for HDX with primary emphasis on allowing custom ROMs to run on a locked device running the native FireOS v4 kernel. There was never a need or intent to leverage secondary slots as was the case with Safestrap v3; in hindsight the developer probably should have disabled them. Aside from WiFi/BT radio issues processor management is also whacked. Only 2 of 4 processors will go online and both operate at maximum frequency. As a result the device never sleeps, performs poorly and has lousy battery life. None of these problems arise in the STOCK slot.
Keep in mind all 3rd gen devices can now be unlocked eliminating the need for Safestrap and opening the door to the full suite of custom ROMs including KitKat, Lollipop and Marshmallow variants. Unfortunately, the process is a bit involved as most steps are manual and require some technical experience.
Enjoy Nexus for now; it's a fine ROM that is fast, lean and energy efficient. Not to mention full access to Google Play Store/Services/apps and the ideal platform for Xposed extensions if you want even greater control over the hardware and user interface.
Click to expand...
Click to collapse
That sounds good. You have been a great help to me.