Related
Someone released this thing, firerooter, https://plus.google.com/app/basic/communities/115612726860884592519, to root the new kindle fire hd7 KFSOWI on fireos 4.5.2. It appears to work. I know the HDX is unsupported, as the author says... but are the versions of fire is on each device that different? It is open source, so I guess some coder could figure out what exploit is being used and port it to the of hdx 7. It might work out of the box, but I don't want to brick my device. I know it is done through fastboot, I was just wondering if anyone had looked at it or tried it yet
Sent from my KFTHWI using XDA Premium 4 mobile app
the link you refer to does not exist. Could you possibly upload fireoot for general access?
Is this what you are talking about? GitHub link is on the main page.
https://peniscorp.com/firerooter/
Claims it can root any FireOS version. Haven't tried anything myself.
Nope does not work.
jmw03j said:
Is this what you are talking about? GitHub link is on the main page.
https://peniscorp.com/firerooter/
Claims it can root any FireOS version. Haven't tried anything myself.
Click to expand...
Click to collapse
Just tried on my Kindle with Fire OS 4.5.2
AlexZap said:
Someone released this thing, firerooter, https://plus.google.com/app/basic/communities/115612726860884592519, to root the new kindle fire hd7 KFSOWI on fireos 4.5.2. It appears to work. I know the HDX is unsupported, as the author says... but are the versions of fire is on each device that different? It is open source, so I guess some coder could figure out what exploit is being used and port it to the of hdx 7. It might work out of the box, but I don't want to brick my device. I know it is done through fastboot, I was just wondering if anyone had looked at it or tried it yet
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Probably won't ever work. What happens (I'm fairly certain) is that it sends a modified, rooted, stock system image through fastboot. If it wasn't so easy to root the Kindle Fire HDs (not to be confused with the new ones), this would have worked on those as well. The HDXs aren't supported because it is not possible to flash via fastboot with a locked bootloader. You'll get the message "not allowed for locked hw" or something similar. With an unlocked bootloader (which is possible, somehow), this would work.
r3pwn said:
Probably won't ever work. What happens (I'm fairly certain) is that it sends a modified, rooted, stock system image through fastboot. If it wasn't so easy to root the Kindle Fire HDs (not to be confused with the new ones), this would have worked on those as well. The HDXs aren't supported because it is not possible to flash via fastboot with a locked bootloader. You'll get the message "not allowed for locked hw" or something similar. With an unlocked bootloader (which is possible, somehow), this would work.
Click to expand...
Click to collapse
Thanks for the info! I thought it didn't matter if the boot loader was locked or not as to if you could flash a through fastboot. I thought flashing always verified the image signature and that is what kept this from being done with this HDX (flashing a modified system image).
This is a big change on Amazon's part if this is the case if they are allowing unsigned images to be flashed to their new devices. If the boot loader is unlocked, you could probably flash TWRP, or some other custom recovery and root that way. I'd be much more comfortable rooting my device that way then someone's provided modified system image... but whatever...
I guess this means that there is no exploit to speak of, and it is just a tool that makes it easier... oh well. The author talks like it could be ported to other fire is devices, but it sounds like that is not the case.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Thanks for the info! I thought it didn't matter if the boot loader was locked or not as to if you could flash a through fastboot. I thought flashing always verified the image signature and that is what kept this from being done with this HDX (flashing a modified system image).
This is a big change on Amazon's part if this is the case if they are allowing unsigned images to be flashed to their new devices. If the boot loader is unlocked, you could probably flash TWRP, or some other custom recovery and root that way. I'd be much more comfortable rooting my device that way then someone's provided modified system image... but whatever...
I guess this means that there is no exploit to speak of, and it is just a tool that makes it easier... oh well. The author talks like it could be ported to other fire is devices, but it sounds like that is not the case.
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's not exactly correct. Amazon has never allowed flashing unsigned images on any of their devices, including the Kindle Fire HD line; it's just that people have found a way to unlock the bootloader.
Anyways, we should be expecting TWRP and all that good stuff very soon thanks to vortox: http://forum.xda-developers.com/showpost.php?p=57767482&postcount=27
EncryptedCurse said:
That's not exactly correct. Amazon has never allowed flashing unsigned images on any of their devices, including the Kindle Fire HD line; it's just that people have found a way to unlock the bootloader.
Anyways, we should be expecting TWRP and all that good stuff very soon thanks to vortox: http://forum.xda-developers.com/showpost.php?p=57767482&postcount=27
Click to expand...
Click to collapse
Yep. He must have misunderstood my post. System partitions aren't ever signature checked because they're just too damn large. It would take an eternity.
The HDX is a different beast entirely that doesn't use fastboot and the boot loader is totally locked down.
Best case scenario: the program does nothing.
Worst case scenario: bricked HDX
Anyone is working on finding a root method for 4.5.2 ? (I'm biting my hands every time I remember that first thing after powering my kindle on, was to upgrade it)
lol...me too..gutted..
Well then...
All I need to do is to install a custom Rom (Cynogenmod, cuz fire OS sucks) via TWRP, so if he can actually make that exploit work, I would be very happy that I can actually customize my kindle and use it to its full potential. The hardware is good, the OS, not so much.
FireOS is great actually... but the desire is to have Google Play as well.
Ask amazon yo roll it back. Explain you are getting random shutdowns and the OS is lagging. That's what I done.
veaceslav said:
Anyone is working on finding a root method for 4.5.2 ? (I'm biting my hands every time I remember that first thing after powering my kindle on, was to upgrade it)
Click to expand...
Click to collapse
Not sure about 4.5.2, but you CAN downgrade:
http://forum.xda-developers.com/kindle-fire-hdx/general/rollback-to-devices-upgraded-to-4-x-t2946946
Then root using Towelroot(what I did) or the HDX toolkit.
Tried it, it works with the 2 FIreOS versions (11.3.2.5 and 11.4.5.2) (for Amazon Kindle Fire 7 HD SOHO [2013, 3rd Gen])
Only issues I have with FireOS 4.5.2 is that even with XPosed Modules to block OTA Updates and System Updates, it still continues to download the 4.5.4 update (tho it never installs it) .... Secondly with 4.5.2, the wall papers have mysteriously disappeared from the framework-res.apk ....
11.3.2.5 is the way to go, albeit stone age vs 11.4.5.2. With 3.2.5, I can modify all the wallpapers, the lockscreen ad, the bootup logo, and not have to worry about it downloading system updates. I say 3.2.5 is the way to go because if you just want to root it for Wallpapers, you don't need all the extra stuff and really don't need the newer OS.
_RumRunner_ said:
Tried it, it works with the 2 FIreOS versions (11.3.2.5 and 11.4.5.2) (for Amazon Kindle Fire 7 HD SOHO [2013, 3rd Gen])
Only issues I have with FireOS 4.5.2 is that even with XPosed Modules to block OTA Updates and System Updates, it still continues to download the 4.5.4 update (tho it never installs it) .... Secondly with 4.5.2, the wall papers have mysteriously disappeared from the framework-res.apk ....
11.3.2.5 is the way to go, albeit stone age vs 11.4.5.2. With 3.2.5, I can modify all the wallpapers, the lockscreen ad, the bootup logo, and not have to worry about it downloading system updates. I say 3.2.5 is the way to go because if you just want to root it for Wallpapers, you don't need all the extra stuff and really don't need the newer OS.
Click to expand...
Click to collapse
Wrong forum; look here. Firerooter does not work with HDX devices.
ahhh yeah... i thought was just a general question if firerooter worked at all... my apologies.
Its nice to get a response though, considering the 2 I've posted that no one seems to know anything about
again my apologies!
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.
Hey guys. I have a bone stock HDX 8.9 that is stuck on fastboot. I'm very familiar with Android and previously this meant that the OS was corrupted and needed reinstall. Does that sound right in this case?
If so, how do I reinstall the OS on this thing?
rudeguy said:
Hey guys. I have a bone stock HDX 8.9 that is stuck on fastboot. I'm very familiar with Android and previously this meant that the OS was corrupted and needed reinstall. Does that sound right in this case?
If so, how do I reinstall the OS on this thing?
Click to expand...
Click to collapse
You can't from fastboot as it has been crippled by Amazon (locked bootloader). Do you know the generation of HDX (3rd/4th) and what version of FireOS was installed? There are a few unbrick techniques but they only work with older models.
Davey126 said:
You can't from fastboot as it has been crippled by Amazon (locked bootloader). Do you know the generation of HDX (3rd/4th) and what version of FireOS was installed? There are a few unbrick techniques but they only work with older models.
Click to expand...
Click to collapse
Thanks for the reply.
I do not know which Gen or what OS was on it. I am doing this for a friend since I figured it would be similar to other android tabs where I just fire up Odin and call it good. I still think I could get it working if I could get the drivers to install but I'm not having any luck with any of the solutions so far.
Do these things have a stock recovery I can boot it into?
rudeguy said:
Thanks for the reply.
I do not know which Gen or what OS was on it. I am doing this for a friend since I figured it would be similar to other android tabs where I just fire up Odin and call it good. I still think I could get it working if I could get the drivers to install but I'm not having any luck with any of the solutions so far.
Do these things have a stock recovery I can boot it into?
Click to expand...
Click to collapse
You have much to learn about Amazon devices in general and HDX models in particular. They are not conventional and lack much of the standardization and recovery capability of other phones/tabs. Tools like Odin and FlashFire do not work on HDX devices. Likely perma-bricked it.
There is a crippled recovery environment (<power>+<vol+up>) but it won't do you any good as no sideload support and the hopeful looking 'factory reset' only wipes cache, dalvik and data; the system partition remains untouched. Can't flash or boot a custom recovery like twrp. Unless the bootloader is unlocked the device is an island without a functioning rom.
Welcome to Amazon.
Davey126 said:
You have much to learn about Amazon devices in general and HDX models in particular. They are not conventional and lack much of the standardization and recovery capability of other phones/tabs. Tools like Odin and FlashFire do not work on HDX devices. Likely perma-bricked it.
There is a crippled recovery environment (<power>+<vol+up>) but it won't do you any good as no sideload support and the hopeful looking 'factory reset' only wipes cache, dalvik and data; the system partition remains untouched. Can't flash or boot a custom recovery like twrp. Unless the bootloader is unlocked the device is an island without a functioning rom.
Welcome to Amazon.
Click to expand...
Click to collapse
Thanks again for the reply.
So should I not waste anymore time on this thing? Just call it junked?
rudeguy said:
Thanks again for the reply.
So should I not waste anymore time on this thing? Just call it junked?
Click to expand...
Click to collapse
There's an outside possibility the bootloader can be unlocked (key to everything) but it would be a difficult trek. Not knowing what was on it before is a killer as only certain devices can be unlocked, mostly early Gen 3s that were never updated to FireOS v4.
Just to add to the misery: fastboot cables don't work on HDX devices. Amazon should include a packet of K-Y with every purchase.
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.
Hey, new to the forums and not very familiar with anything related to rooting, ROMs, or anything like that on these devices. I'm here because I'm pretty much stuck in a situation where if I don't update my Kindle OS the only app I use will become unusable (this kindle uses Fire OS 4.5.5.2 or Android KitKat 4.4 according to wikipedia)- the app I use will soon require Android 5.0 or higher- I'm already getting warning messages and I can't manually download the new versions of the app without errors. The exact model of my Kindle is HDX 8.9 (3rd gen) 4.5.5.2 OS, everything works fine.
I looked at some previous posts and saw some outdated information or info for people that already knew what they were doing. I got scared because I hear some people bricked their devices trying these things. So my question is, as a noob, should I attempt to install a new Android ROM or is it more advisable for me to just sell the tablet(s) and get something newer? Also, I'd like to add, I have 3 of these tablets for my business so this decision would apply 3x over.
MadixV said:
Hey, new to the forums and not very familiar with anything related to rooting, ROMs, or anything like that on these devices. I'm here because I'm pretty much stuck in a situation where if I don't update my Kindle OS the only app I use will become unusable (this kindle uses Fire OS 4.5.5.2 or Android KitKat 4.4 according to wikipedia)- the app I use will soon require Android 5.0 or higher- I'm already getting warning messages and I can't manually download the new versions of the app without errors. The exact model of my Kindle is HDX 8.9 (3rd gen) 4.5.5.2 OS, everything works fine.
I looked at some previous posts and saw some outdated information or info for people that already knew what they were doing. I got scared because I hear some people bricked their devices trying these things. So my question is, as a noob, should I attempt to install a new Android ROM or is it more advisable for me to just sell the tablet(s) and get something newer? Also, I'd like to add, I have 3 of these tablets for my business so this decision would apply 3x over.
Click to expand...
Click to collapse
Changing ROMs is the easy part. Preparing your device (specifically temperamental HDXs) to accept a custom ROM (rooting; unlocking the bootloader; dealing w/fastboot; etc) is not for the faint of heart. Suggest identifying someone in your business who has some experience tethering Android devices and/or rooting. With that advantage updating your portfillo should be fairly easy. Otherwise I would look for something else.