I do not want to brick this device. Could someone give/list me steps that would root it using the 'safest' (aka hardest to mess up), install TWRP, and maybe then install a good ROM (CM13?)
Also, fire os 4.5.5
ADB works.
GameExpertNetwork said:
I do not want to brick this device. Could someone give/list me steps that would root it using the 'safest' (aka hardest to mess up), install TWRP, and maybe then install a good ROM (CM13?)
Also, fire os 4.5.5
ADB works.
Click to expand...
Click to collapse
Starting from 4.5.5 you can not install 'native' twrp or unlock the bootloader. Nor is their any path to allow this due due anti-rollback protections. Your safest path (which still holds risks) is to rollback to 3.2.8, upgrade to 4.5.2, root, install Safestrap v4 followed by one of two kitkat based roms: Nexus v4 or CM11. At present you can not install CM12 (lollipop) or CM13 (marshmallow) under Safestrap v4.
There are many posts detailing the above process; a few recent ones can be found here, here and here. Scroll through the entire thread for other examples along with a diary of user experiences.
Key points:
- be sure to keep wifi off (airplane/flight mode engaged) while passing through 3.2.8 and 4.5.2 until OTA is block. Receiving an update on 3.2.8 will brick your device. The consequences on 4.5.2 are less severe but still unpleasant.
- suggest downloading everything you need to your device in advance; put each component into a separate folder to be extracted/renamed as needed
- read, read and read some more before attempting anything. Ask questions as needed; never guess or assume. Make sure you know the expected outcome, potential consequences and fallback options for each step before executing
- Kindles in general and HDX models in particular are unforgiving relative to other devices. Tough to mod, easy to brick, nearly impossible to recover. If not 100% confident in your abilities enjoy your device as is (or be mentally prepared to toss it in the trash).
Davey126 said:
Starting from 4.5.5 you can not install 'native' twrp or unlock the bootloader. Nor is their any path to allow this due due anti-rollback protections. Your safest path (which still holds risks) is to rollback to 3.2.8, upgrade to 4.5.2, root, install Safestrap v4 followed by one of two kitkat based roms: Nexus v4 or CM11. At present you can not install CM12 (lollipop) or CM13 (marshmallow) under Safestrap v4.
There are many posts detailing the above process; a few recent ones can be found here, here and here. Scroll through the entire thread for other examples along with a diary of user experiences.
Key points:
- be sure to keep wifi off (airplane/flight mode engaged) while passing through 3.2.8 and 4.5.2 until OTA is block. Receiving an update on 3.2.8 will brick your device. The consequences on 4.5.2 are less severe but still unpleasant.
- suggest downloading everything you need to your device in advance; put each component into a separate folder to be extracted/renamed as needed
- read, read and read some more before attempting anything. Ask questions as needed; never guess or assume. Make sure you know the expected outcome, potential consequences and fallback options for each step before executing
- Kindles in general and HDX models in particular are unforgiving relative to other devices. Tough to mod, easy to brick, nearly impossible to recover. If not 100% confident in your abilities enjoy your device as is (or be mentally prepared to toss it in the trash).
Click to expand...
Click to collapse
So, from my assumptions, there are 2 major ways to mess up
1. OTA update.
2. Low battery
And IF I ever do this, I will click the 'forget' button on the wifi network AND set it into airplane mode, and also have it fully charged overnight and STILL plugged in,
What are some other risks that I can try to "eliminate"
GameExpertNetwork said:
So, from my assumptions, there are 2 major ways to mess up
1. OTA update.
2. Low battery
And IF I ever do this, I will click the 'forget' button on the wifi network AND set it into airplane mode, and also have it fully charged overnight and STILL plugged in,
What are some other risks that I can try to "eliminate"
Click to expand...
Click to collapse
There are risks throughout the process - a comprehensive detailing would never be complete. Your best defense is carefully reading instructions, understanding what is suppose to happen at each step (expected outcomes) and avoiding 'gotchas' which are well documented. Most disasters are the result of poor preparation, impatience and experimentation. Like anything else the work is relatively easy with manageable risk if do your homework. Keep reading until comfortable.
Add to your list:
- using files obtained from sources other than listed in the relevant threads (eg: stock 3.2.8 vs rollback file)
- performing a native factory reset (from the stock recovery menu) unless recommended by an experienced contributor
- performing a native factory reset after Safestrap v4 is installed (instant brick)
- activating/using secondary slots in Safestrap v4 and then attempting to swap backup images between slots
- flashing unsupported roms in Safestrap v4 (CM12/CM13, stock FireOS, etc)
- manually twiddling file permissions or messing with build.prop after obtaining root (there's an app for that if needed)
Davey126 said:
There are risks throughout the process - a comprehensive detailing would never be complete. Your best defense is carefully reading instructions, understanding what is suppose to happen at each step (expected outcomes) and avoiding 'gotchas' which are well documented. Most disasters are the result of poor preparation, impatience and experimentation. Like anything else the work is relatively easy with manageable risk if do your homework. Keep reading until comfortable.
Add to your list:
- using files obtained from sources other than listed in the relevant threads (eg: stock 3.2.8 vs rollback file)
- performing a native factory reset (from the stock recovery menu) unless recommended by an experienced contributor
- performing a native factory reset after Safestrap v4 is installed (instant brick)
- activating/using secondary slots in Safestrap v4 and then attempting to swap backup images between slots
- flashing unsupported roms in Safestrap v4 (CM12/CM13, stock FireOS, etc)
- manually twiddling file permissions or messing with build.prop after obtaining root (there's an app for that if needed)
Click to expand...
Click to collapse
I bricked a nextbook tablet with that last way (build.prop messing)
Will factory resetting from a custom ROM brick my device?
And don't worry, I won't be flashing stock fire OS.
Also, sorry if i'm asking too much, but since I don't see a place where the info is all together in one thread and not links to many others, could you either link me to a step-by-step tutorial or list them out yourself? Thank you
GameExpertNetwork said:
I bricked a nextbook tablet with that last way (build.prop messing)
Will factory resetting from a custom ROM brick my device?
And don't worry, I won't be flashing stock fire OS.
Also, sorry if i'm asking too much, but since I don't see a place where the info is all together in one thread and not links to many others, could you either link me to a step-by-step tutorial or list them out yourself? Thank you
Click to expand...
Click to collapse
As previously mentioned never do a factory reset from the native Kindle Fire recovery menu with Safestrap v4 installed. It will destroy the Safestrap environment and everything running within it regardless of rom.
Post #3 contains several links that should prove helpful. You'll need to do some reading.
Related
Hey guys ive got a hdx 7' RUNNING FIRE OS 3.2.4 everything i have been reading is saying that this version is somewhat unique in that there are a few roms availible mostly from safestrapp but most are not, twrp requires 3.2.3 and earlier as well as the bootloader unlock procedure. Can anyone point me in the direction on how to downgrade to one of the earlier versions. Currently i am rooted, ota disabled via: hdxtookit, i had safestrapp and a asop rom installed but was getting google play services stopped working error messages and restored to factory because i havent used the kindle in a year. Anyways i'm looking to get back into it and got cm 12.1 on my sgs3 and wanted to get something similar but keep runninginto problems with my version fire os. So just need a quick link to a roll back procedure in english and i should be able to do the rest from unlock - twrp - roms etc. I've been searching off and on the past few weeks but do not find anything definitive so i decided to finally ask to get an answer thanks for any and all help.
131 views no replies can anyone guide me to a solution?
rbkelley89 said:
131 views no replies can anyone guide me to a solution?
Click to expand...
Click to collapse
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
jeryll said:
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
Click to expand...
Click to collapse
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Davey126 said:
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Click to expand...
Click to collapse
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
rbkelley89 said:
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
Click to expand...
Click to collapse
Locate HDX toolkit in the Android Development thread and try to remove the OTA block that way. Keep WiFi off or you might receive an unwanted update.
Although not recommended twrp can be installed with a locked bootloader.
Travelling this week so can't get into more detail. Suggest you keep reading. Don't do stuff unless you are absolutely confident in your skills, knowledge, risks and expected outcome(s). Post questions. Many folks willing to help if you have done your homework. Sorry for brevity ...
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
XxD34THxX said:
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
Click to expand...
Click to collapse
The path I am suggesting does not involve modifying build.prop.
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice finding, I absolutely forgot that this existed, of course he can use that thread with rollback images to downgrade to x.3.1.0! Then he can install TWRP etc... (as I did in the past - proof below )
jeryll said:
Thank you sir, successfully rolled back to 14.3.1.0, installed TWRP 2.8.1.0 and now I will play a little with TWRP
Click to expand...
Click to collapse
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Davey126 said:
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
Click to expand...
Click to collapse
pquan2009 said:
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Click to expand...
Click to collapse
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
jeryll said:
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
Click to expand...
Click to collapse
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
rbkelley89 said:
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
Click to expand...
Click to collapse
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Davey126 said:
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Click to expand...
Click to collapse
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
rbkelley89 said:
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
Click to expand...
Click to collapse
You can grab stock images here. Be absolutely certain you snag the correct one for your device. Verify md5=c49c0363de4d8dfa5c87c1bdb88aa2ba with ES FIle Explorer (long click the file and select 'properties' from the 'more' menu). Note you will loose root and OTA blocking. Be sure to stay off wifi. Use HDX Toolkit (requires usb tether to Windows PC) to root 3.1.0 and reblock OTA if needed.
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.
Hi all,
I've been reading a fair bit, but I'm still not quite certain what the best path is for me with my device.
Current state: I did the rollback from 4.5.2 to 13.3.2.8_user_328003120. I installed Safestrap 3.75 and GGOW's excellent Nexus v1.0.1.
Kindle ROM is sitting in STOCK slot, and Nexus 1.0.1 is in Slot 1. It is rooted. I have not installed the OTA block, but the device is in airplane mode.
I have no data that I'm interested in preserving.
What I'd like to do is get the device to a point where I can install GGOW's newer version of Nexus ROM, and/or the CM series of ROMs. The tablet is used primarily for gaming, and some of the newer games won't run on the older version of Nexus ROM anymore.
SO - it seems to me that I have to go to a newer version of Safestrap (v4) to make this happen. Is this so? If that is so, what's the correct upgrade/migration path to make this happen? Again - I'm not worried about losing all of my data, but I would like to avoid brick, and (ideally), it would be nice to have good recovery options for the future.
Thanks for any help you can provide me!
CanadaDave77 said:
Hi all,
I've been reading a fair bit, but I'm still not quite certain what the best path is for me with my device.
Current state: I did the rollback from 4.5.2 to 13.3.2.8_user_328003120. I installed Safestrap 3.75 and GGOW's excellent Nexus v1.0.1.
Kindle ROM is sitting in STOCK slot, and Nexus 1.0.1 is in Slot 1. It is rooted. I have not installed the OTA block, but the device is in airplane mode.
I have no data that I'm interested in preserving.
What I'd like to do is get the device to a point where I can install GGOW's newer version of Nexus ROM, and/or the CM series of ROMs. The tablet is used primarily for gaming, and some of the newer games won't run on the older version of Nexus ROM anymore.
SO - it seems to me that I have to go to a newer version of Safestrap (v4) to make this happen. Is this so? If that is so, what's the correct upgrade/migration path to make this happen? Again - I'm not worried about losing all of my data, but I would like to avoid brick, and (ideally), it would be nice to have good recovery options for the future.
Thanks for any help you can provide me!
Click to expand...
Click to collapse
You best (really only path) is to upgrade to 4.5.2, root (use Kingroot), install Safestrap v4 and then flash either Nexus v4 or CM11 to the STOCK slot (not a secondary slot as was recommended with Safestrap v3). This will overwrite FireOS but it can be restored from the backup you create or from a 'custom' build of 4.5.2 if you forget/loose the all important backup.
Safestrap v4 provides a modest improvement in recovery options - but it is not nearly as robust as 'native' TWRP or fastboot with an unlocked bootloader (neither are options for you). You can still brick your device with a simple mistake or by going 'off script'. Many folks have gained a false sense of confidence with Safestrap installed. Think of SS v4 as an enabler for CM11 or Nexus v4, not a recovery or multi-boot tool.
Note CM12 and SlimLP can NOT be flashed under Safestrap v4. Only the two KitKat roms referenced above (or a custom version of FireOS should you want to return to stock).
My suggestion is your read through the Safestrap v4 thread (300+ posts!) to expand your knowledge of the process and become familiar with individual procedures. Look for excellent posts from @Cl4ncy and other experienced contributors. When you are ready to take the plunge post a succinct outline of the steps you plan to follow. Any 'gotchas' will quickly be identified by a member of the community.
Got it - thanks.
I've been through about half of that thread so far. The process is a bit long, so I'd like to break it up into a few chunks if I could.
Here's what I'm thinking my "cookbook" would look like to start. Note that I don't have any data that I wish to preserve at all in either the 3.2.8 FireOS or the Nexus ROM 1.0.1. Also note that my current state is that I have 3.2.8 in the stock slot and the Nexus ROM in Slot 1.
1) Ensure I'm in airplane mode (which I am)
2) Download the 4.5.2 stock rom here and put it in the root /sdcard.
3) Boot up 3.2.8 from the stock slot, go into "check for updates" and it should appear there.
4) Allow the update to take effect.
5) Boot into the 4.5.2 OS, ensuring that airplane mode is still on.
6) Uninstall Safestrap 3.75 by going into the "settings" area and uninstalling the package.
7) Reboot - this will take me into 4.5.2 in a "clean" state.
I think the biggest question is the uninstallation of Safestrap. I'm feeling like I might be doing that in the wrong order?
My next steps (and the second chunk of the cookbook) would be to root 4.5.2 using Kingroot, install the new version of Safestrap, back up 4.5.2 to a file on my PC, move 4.5.2 to one of the other ROM slots and install the new Nexus ROM in the stock slot, but I want to make sure I'm taking this slowly so not to brick the device, so I don't want to tackle that until the cookbook is done.
I know it's not of a ton of value compared to the work you do here, Davey, but once I'm done, I'll post the tutorial for everyone who is in my situation in a "clean" format once this is all done and working well so that people have a good starting point. I know a lot of people did the 3.2.8 rollback for Nexus 1.0.1, so they may be in a similar state.
Excellent post here: http://forum.xda-developers.com/showpost.php?p=61531925&postcount=52
Does my process look correct so far?
CanadaDave77 said:
Got it - thanks.
I've been through about half of that thread so far. The process is a bit long, so I'd like to break it up into a few chunks if I could.
Here's what I'm thinking my "cookbook" would look like to start. Note that I don't have any data that I wish to preserve at all in either the 3.2.8 FireOS or the Nexus ROM 1.0.1. Also note that my current state is that I have 3.2.8 in the stock slot and the Nexus ROM in Slot 1.
1) Ensure I'm in airplane mode (which I am)
2) Download the 4.5.2 upgrade file from here and put it in the root /sdcard.
3) Boot up 3.2.8 from the stock slot, go into "check for updates" and it should appear there.
4) Allow the update to take effect.
5) Boot into the 4.5.2 OS, ensuring that airplane mode is still on.
6) Uninstall Safestrap 3.75 by going into the "settings" area and uninstalling the package.
7) Reboot - this will take me into 4.5.2 in a "clean" state.
My next steps (and the second chunk of the cookbook) would be to root 4.5.2 using Kingroot, install the new version of Safestrap, back up 4.5.2 to a file on my PC, move 4.5.2 to one of the other ROM slots and install the new Nexus ROM in the stock slot, but I want to make sure I'm taking this slowly so not to brick the device, so I don't want to tackle that until the cookbook is done.
I know it's not of a ton of value compared to the work you do here, Davey, but once I'm done, I'll post the tutorial for everyone who is in my situation in a "clean" format once this is all done and working well so that people have a good starting point. I know a lot of people did the 3.2.8 rollback for Nexus 1.0.1, so they may be in a similar state.
Does my process look correct so far?
Click to expand...
Click to collapse
Almost (good detail/research!). Thoughts:
- You should remove all secondary slots and uninstall Safestrap recovery prior to upgrading to FireOS v4. SS v3 will not function properly under FireOS v4; results are unpredictable. Be sure to boot into FireOS v3 at least once prior to cleaning house to insure it remains functional. Then return to SS recovery, backup one or both slots (as a precaution should something go wrong) as space permits and then delete all secondary slots. Reboot to FireOS and uninstall Safestrap recovery via the SS app. Then uninstall SS v3 itself (keep a copy of the apk if possible). The above reflect a very conservative path; you may choose to skip/consolidate some steps. Just be sure Safestrap v3 recovery is not installed prior to upgrading to FireOS v4.
- Do not preform any type of 'wipe' or 'factory reset' in Safestrap v3. Not needed and potentially dangerous.
- Download any apks you may need immediately after upgrading before going to 4.5.2. Suggest Kingroot, ES File Explorer and SuperSU (latter as a precaution). Leave all in internal storage (root of SDCARD) which should remain untouched during the upgrade.
- After upgrading to 4.5.2 (with airplane mode engaged) perform the following steps: enable USB debug (settings menu), root with Kingroot, block OTA, install Safestrap v4, boot into SS recovery, take a backup of the stock slot, reboot into 4.5.2 and copy backup directory/contents to your PC. I'll leave it as an exercise to research the details behind those steps.
- Kingroot requires a brief network connection (less than 30 sec). Be aware Amazon may attempt to push an OTA update while connected to the network. Be sure to reenable airplane mode after Kingroot finishes and whack the partially downloaded OTA file if needed.
BTW - not trying to make things difficult; I feel there is significant value in the suggested 'homework' assignment as it will build your confidence, reduce the chance of mistakes (some of which can have dire consequences) and facilitate self-help should something go wrong.
Thanks for the props; what I 'do' simply reflects a regurgitation of info gleaned from others. They are the ones who make all this possible (@ggow in particular). That said, I am sure many will appreciate a 'how to' guide should you decide to publish.
LOL - I certainly didn't think you were trying to make things difficult by suggesting the homework! I want the device to work after I'm done monkeying around with it - and, honestly, it's a matter of pride to feel like I can at least partially feed myself.
Ironically, it took your help to help me feed myself... so, thanks.
Anyway - I've had some very good success! I'm now updated to 4.5.2, Kingrooted, ES File Explorer, Safestrap 4.01 installed, and a backup has been run.
What I did see was that it was trying to download an update during the Kingroot process, and that got to 80%. I'd like to kill that update file before I proceed any further, just in case wireless somehow gets turned back on. I don't see the file in the root of /sdcard, though - do you know where that file goes?
CanadaDave77 said:
LOL - I certainly didn't think you were trying to make things difficult by suggesting the homework! I want the device to work after I'm done monkeying around with it - and, honestly, it's a matter of pride to feel like I can at least partially feed myself.
Ironically, it took your help to help me feed myself... so, thanks.
Anyway - I've had some very good success! I'm now updated to 4.5.2, Kingrooted, ES File Explorer, Safestrap 4.01 installed, and a backup has been run.
What I did see was that it was trying to download an update during the Kingroot process, and that got to 80%. I'd like to kill that update file before I proceed any further, just in case wireless somehow gets turned back on. I don't see the file in the root of /sdcard, though - do you know where that file goes?
Click to expand...
Click to collapse
Congrats on progress to date! You're through the tough hurdles and almost ready for some real fun.
OTA updates are written to the root of sdcard. The partial may have been deleted when the connection severed.
Thoughts:
- The partial OTA, if present, will likely be large. Do a deep search for .bin in ES File Explorer. Make sure 'show hidden files' is enabled.
- You can block further OTA updates in FireOS v4 by renaming DeviceSoftwareOTA.apk to DeviceSoftwareOTA.bak
- There is no need for the above action if you intend to immediately flash cm11 or Nexus v4 to the stock slot in Safestrap which replaces FireOS and associated ota mechanisms.
I'm a noob to the club here and to many things discussed on the forums. I have a 3rd Gen Fire HDX 13.4.5.2 that I bought for my soon to be wife. I feel horrible that she doesn't like it as is. My bad. ADB is up and running well on my laptop. I even managed to reboot the device using such commands but don't want to brick it. But I realize that I know just enough to be dangerous. I haven't seen any threads on fast boot commands by which I can boot into TWRP and command the device into a custom ROM with Super SU and Gapps. Ibut I am still ignorant as to which .zip files need to be loaded into the device and the cable doesn't appear necessary. I have seen a thread on how to do this but it appears to be on a 1st Gen device when things were much more simple. I would like for he to use it for more than a table coaster! I stopped while I was ahead! A factory fast boot cable may get me directly into Recovery know that this may seem to simple to you, the Developers from which I'm asking but it is a hurdle I can't leap myself. I managed this on my Android phone, however this seems at least, monumentally more challenging. If I'm incorrect that this is possible, by all means, tell me but please be kind, as I'm learning and tell me the best way to achieve the desired results and not stop at making me feel any more stupid than I am feeling. I'm counting on you. She won't marry me until I fix it. Save a marriage! LOL!!!
Sandman1210 said:
I'm a noob to the club here and to many things discussed on the forums. I have a 3rd Gen Fire HDX 13.4.5.2 that I bought for my soon to be wife. I feel horrible that she doesn't like it as is. My bad. ADB is up and running well on my laptop. I even managed to reboot the device using such commands but don't want to brick it. But I realize that I know just enough to be dangerous. I haven't seen any threads on fast boot commands by which I can boot into TWRP and command the device into a custom ROM with Super SU and Gapps. Ibut I am still ignorant as to which .zip files need to be loaded into the device and the cable doesn't appear necessary. I have seen a thread on how to do this but it appears to be on a 1st Gen device when things were much more simple. I would like for he to use it for more than a table coaster! I stopped while I was ahead! A factory fast boot cable may get me directly into Recovery know that this may seem to simple to you, the Developers from which I'm asking but it is a hurdle I can't leap myself. I managed this on my Android phone, however this seems at least, monumentally more challenging. If I'm incorrect that this is possible, by all means, tell me but please be kind, as I'm learning and tell me the best way to achieve the desired results and not stop at making me feel any more stupid than I am feeling. I'm counting on you. She won't marry me until I fix it. Save a marriage! LOL!!!
Click to expand...
Click to collapse
Your best option is to root, install Safestrap v4 and then replace FireOS with either Nexus v4 or CM-11. That will transform the device into something akin to a Nexus 7 which will probably be more appealing to the intended recipient.
You can not install TWRP or a custom ROM on this device without the help of Safestrap as the bootloader is locked with no ability to unlock. Nor do you want to commingle GAaps (Google Play Framework/Service/Store in particular) with FireOS as they don't play well together on v4. FireOS v5 is much more accommodating but that is not an option for 3rd gen devices.
Set aside thoughts of layering on components via ADB and recovering with a factory/fastboot cable if things go bad. HDXs are sensitive devices that are easy to brick and nearly impossible to recover. Factory cables are useless on this device as is the fastboot environment with a locked bootloader.
Hopefully you have stayed of WiFi to prevent an auto-upgrade to FireOS 4.5.5. Device must be on 4.5.2 to run Safestrap v4. Rolling back from 4.5.5 -> 4.5.2 is not straight forward and entails some risk if instructions are not followed.
Path forward:
- as mentioned stay off WiFi until OTA (over-the-air) updates are blocked
- root with Kingroot. You will need to enable WiFi for a brief period. Watch for OTAs when connected. Once rooted immediately reboot tablet to flush the partially downloaded update. If you have a fast internet connection you may want to root from location with pokey public WiFi such as a coffee shop or library. You don't want the full 4.5.5 update to download while you are rooting.
- sideload ES File Explorer via 'adb install' and use it to block OTA by renaming DeviceSoftwareOTA.apk in /system/priv-app/ to something benign. Once complete you can safely reenable WiFi.
- install Safestrap v4. Once Safestrap is installed NEVER perform a factory reset from the native device recovery menu; your device will brick.
- from Safestrap recovery (which looks a lot like twrp) backup your existing FireOS installation
- download and flash either Nexus v4 or CM11
There are several threads and hundreds of posts covering the details associated with each step. Unfortunately, no guides or how-to videos. Suggest reading through the Safestrap v4, CM11 and Nexus v4 threads to get started. You'll also find related posts in the HDX General and Q&A forums. Ask questions as your knowledge evolves. Have a plan, know the expected (and unexpected) outcomes of each action, never assume or guess. The answer to "what could it hurt" is "everything".
Good luck.
Warning: Potentially long post ahead with mini-intro/rant
Hi XDA! I'm a noob new user/newbie when it comes to rooting. I have some (little) experience with jailbreaking my iPhone previously (It turned out very well), when the guy I paid to do so practically bricked my old one (SHEESH, you can't count on other people to do these things, better do them yourself) but have not tackled rooting Android devices yet.
I have a 3rd gen Kindle Fire HDX 7" (Thor).
Don't get me wrong, I love my Kindle. It's been an awesome pal for the past two years, aside from the loose charging port, the lack of interesting stuff on the Amazon appstore, and the inability to change or customize YOUR device, I decided it was time to "get my feet wet". I've been coming back to these forums over the past few months, in hopes of finding a root for 4.5.5.2 but I'd always chicken out in fear of bricking it. Eventually, I learned that to root, I need to rollback to a certain firmware.
OKAY, so I've done a little reading here and there in the past two hours (or more) and have gathered the following information so far (if there's something worth clarifying or expounding, please do!):
Point 1: The steps are, in order: Rollback to 3.2.8, upgrade to 4.5.2, root, block OTA, install Safestrap v4, and (optional) flash custom ROM.
My options are CM11 and Nexus 4 as of the moment (from what I've seen on these forums, but CM11 has been discontinued[????] and there's a newer version of HDX Nexus ROM v4 called Fire Nexus ROM somewhere if I'm not mistaken)
Question: Which do you suggest? CM11 or Nexus 4? What are the pros and cons of each?
Point 2: I understand that I need to download everything in advance and store them in a unique folder so that it'd be easier for me later on.
Question: Do you recommend that I factory reset my Kindle before anything else and THEN download everything I need in preparation? Won't these downloads be deleted/removed if I rollback my device to 3.2.8? I'm planning on creating a backup of these files on my PC in case something goes wrong or missing.
Point 3: I saw something that said
It was only tested with 14.4.5.2, but should also work with 13.4.5.2.
Click to expand...
Click to collapse
Question: What's the difference between 14.4.5.2 and 13.4.5.2? I haven't dug deep enough in the forums to know if there's an answer to the question, but I made this thread to clear up everything I'm unsure of.
Point 4: Before anything, I know I've got to understand the basics of ADB before even attempting any of this (like commands and such). In one of the threads, I saw this:
"Install minimal adb + fastboot......"
Click to expand...
Click to collapse
Question: What's the difference between minimal adb versus the whole package/thing? Shouldn't it be better to just download or install the full thing (no matter how big the file/program/application is)? What are the pros and cons?
YES, I know I have to understand what USB debug means and/or how to enable it. (I bookmarked an article for further reading soon, but already have enabled the setting within my device).
Other things I've gathered so far:
-Always have a copy of ES File Explorer along with other important files.
Never perform a factory reset unless specifically advised to do so by someone experienced with HDX devices....
Click to expand...
Click to collapse
-Use a Windows PC/laptop. I'm using a mac, which is basically useless for games and the like not ideal when rooting. (Tiny question. Do I really need to install Linux/Ubuntu even if I can use someone's Windows PC/lappy to root?
-To root successfully, I've got to enable mock locations from developer options (already did).
-Before installing/flashing custom ROMS, I need to make a backup of the stock ROM.
CONCERNS:
Known issues regarding safestrap include secondary slots which boot but the WiFi module doesn't load (Which means I have to flash Nexus v4 to the STOCK SLOT for now [?????] is there any workaround for this? Because from what I've read so far, tampering with the stock is a big NO-NO unless you know what you're doing or in this case, "...unless I know what I'm doing.".) Or at least any reassurance? A safe, fool-proof way of doing this without at least bricking my device (likely)?
That's all I've got so far. I've compiled everything the basic things I need to know in a notepad, from steps and instructions, to tuts and download links.
Apologies for my english, this is not my native language
Thanks to whoever can answer some of my questions! Cheers and good day :laugh:
Don't even think about using safestrap, it might as well be a death trap if u brick ur device ur screwed. The best thing u could do is downgrade to 3.2.8 https://forum.xda-developers.com/kindle-fire-hdx/general/rollback-13-3-2-8-rollback-ota-captured-t3046204 unlock your bootloader https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 (maybe get a tech savvy friend to help u with that one) it looks hard but it's actually very simple the way he explains it makes it more difficult than it really is. And if you want a stable rom with good user customization I'd get cm11. Also u don't really have to upgrade to 4.5.2 everything works great starting out from 3.2.8
CocoBun said:
Don't even think about using safestrap, it might as well be a death trap if u brick ur device ur screwed. The best thing u could do is downgrade to 3.2.8 https://forum.xda-developers.com/ki...lback-13-3-2-8-rollback-ota-captured-t3046204 unlock your bootloader https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 (maybe get a tech savvy friend to help u with that one) it looks hard but it's actually very simple the way he explains it makes it more difficult than it really is. And if you want a stable rom with good user customization I'd get cm11. Also u don't really have to upgrade to 4.5.2 everything works great starting out from 3.2.8
Click to expand...
Click to collapse
Agreed. Be sure to stay off the network while on 3.2.8; if the device takes an OTA update it WILL brick with no possible recovey. Use TowelRoot to root; quick/reliable on FireOS v3. No need to update to 4.5.2; doing so adds risk/complexity with no corresponding benefit.
KingOroot PC edition (yes KingORoot not Kingroot) will root 4.5.5.2 in less than a minute, used it very recently having previously rooted 4.5.5.1 with Kingroot. In both case unlock the bootloader flashed twrp and put nexus ROM on without issue
Mr McBoatface said:
KingOroot PC edition (yes KingORoot not Kingroot) will root 4.5.5.2 in less than a minute, used it very recently having previously rooted 4.5.5.1 with Kingroot. In both case unlock the bootloader flashed twrp and put nexus ROM on without issue
Click to expand...
Click to collapse
Yes, kingOroot was previously identified as a potential root solution for 4.5.5.2. Sometimes it works...other times not. Kinda like KingRoot on the 5th gen Fire. When it fails the leftovers can be onerous to deal with on unrooted device. If root is secured I recommend immediately unlocking the bootloader following by a comprehensive wipe before flashing a custom ROM. KingOroot does not enjoy a stellar reputation.