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.
Related
I just recieved a replacement Unit for my malfunktioning HDX 9.8. Current version on this thing is 14.3.0.2_user_302075320. I have just started it up to check the version and have not yet registered it or even connected it to a network. This time around I would like to be in control of things! What would be the appropriate thing to do with this version, if I want to :
1. Root it and keep it from auto-updating.
2. getting it safestrapped to be able to...
3. ...flash custom roms safely in the future,
Ive been looking around these forums to find out myself but information is scrambled and depending on version numbers and other things. The learning curve sure is steep here
/sebastian
My humble suggestion is to install TWRP (here) followed by the ROM of your choice. Each has pros/cons....stock is also an option. You will need to do some reading, plan carefully and be prepared for the unexpected. Keep that pup in 'airplane' mode to prevent debilitating OTA updates until you identify and apply an appropriate blocker. I think you will find the community quite willing to help with specific questions but you probably won't get a start-to-finish recipe. Lots of reading ahead but the rewards are worth it IMO. Good luck!
Thanks for the reply! Good to hear that airplane mode can be a temporary update blocker! I'll do some more reading up on TWRP to begin with then.
Device Manager said:
Thanks for the reply! Good to hear that airplane mode can be a temporary update blocker! I'll do some more reading up on TWRP to begin with then.
Click to expand...
Click to collapse
Be carefull and dont use airplane mode to block updates while in stock! At least one user reported that amazon can update your kindle even with airplane mode on! If you setup your wifi already, just turn-off / forget your wifi while in stock, or use OTA blocker ...
Forgetting all WiFi networks is good advise indeed! I have seen Kindle readers pop out of airplane mode on occasion; suppose the same could happen on Fire/HDX tablets although I have not personally experienced this. OTA blocker is great (what I use) but obviously requires root.
OK, thanks everyone!
I'm good so far! I first rooted with towelroot then went for the toolkit. Installed the ADB drivers, then SU, then OTA blocker. After that I Installed safestrap, made a backup and a new rom-slot, to which I restored the recovery. So now I should be OTA blocked and have a stock ROM recovery option. I hope I haven't made any terrible mistakes yet
I'm a happy camper! (as of yet
Now I will do som reading up on HDXposed and custom roms I guess. Does anyone have any suggestions? Is the Nexus rom a good option?
Thanks again!
Ok Iplayed around some and read up some more. Now I can definitely see the benefits of going for the custom recovery! I have a few remaining questions about the specifics about flashing TWRP that I cant seem to find the answer to. Hope somewone would be kind enough to help or point me in the right direction.
Do I need to uninstall safestrap before (or after) flashing TWRP?
Is "Copy image to SD-card root" the same as copying it to the device file system root? As in draging and dropping in windows perhaps?
What is the tool for issuing the commands mentioned in the TWRP install guide? (I have used ADB but only via the Toolkit aplication and I havent seen a command prompt for this around).
Sorry for lacking in some fundamentals on this... (being a noob on android stuff)
Never mind the above. All sorted. Up and running HDX Nexus 2.0.5. Great stuff!
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
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.
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.
So I just acquired a used 4th gen 16gb Fire HD 7"
Im trying to look around, and I keep reading conflicting info on what OS versions can root, do/do not downgrade, use this/that etc.
This is the info i have:
Model: Fire HD 7 (4th gen)
Fire os version: 5.3.1.1
In "noob friendly terms", can someone explain how (or what tutorial to follow) so I can root my tablet, and get TWRP installed so I can load custom roms (plan on replacing this crap fire OS)
ps: If I cant root, is there a way to get the play store, and block all future updates so eventually I can root when the community behind developing those roots catch up?
cheers!
Orvis25 said:
So I just acquired a used 4th gen 16gb Fire HD 7"
Im trying to look around, and I keep reading conflicting info on what OS versions can root, do/do not downgrade, use this/that etc.
This is the info i have:
Model: Fire HD 7 (4th gen)
Fire os version: 5.3.1.1
In "noob friendly terms", can someone explain how (or what tutorial to follow) so I can root my tablet, and get TWRP installed so I can load custom roms (plan on replacing this crap fire OS)
ps: If I cant root, is there a way to get the play store, and block all future updates so eventually I can root when the community behind developing those roots catch up?
cheers!
Click to expand...
Click to collapse
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here
Killa8 said:
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here
Click to expand...
Click to collapse
I see the downgrade works with 5.3.1 but does NOT specify if it does for 5.3.1.1. (do not want to brick)
Also, So when/if I risk downgrade to 4.5.3, i can then install TWRP and flash custom roms no problem, correct?
Cheers!
Orvis25 said:
I see the downgrade works with 5.3.1 but does NOT specify if it does for 5.3.1.1. (do not want to brick)
Also, So when/if I risk downgrade to 4.5.3, i can then install TWRP and flash custom roms no problem, correct?
Cheers!
Click to expand...
Click to collapse
Exactly
But the worse brick possible for a Fire can be recoverable in most cases (maybe not yours?) Anyway all this is risk ! Try by your own and see
Just to confirm, it does work with 5.3.1.1.
olliebean said:
Just to confirm, it does work with 5.3.1.1.
Click to expand...
Click to collapse
Are you referring to downgrading to 4.5.3 from 5.3.1.1?
If so, what tutorial/files did you use?
Cheers!
Orvis25 said:
Are you referring to downgrading to 4.5.3 from 5.3.1.1?
If so, what tutorial/files did you use?
Cheers!
Click to expand...
Click to collapse
Yes, I followed the tutorial here as linked by Killa8 above. Worked perfectly. You can root 4.5.3 with KingRoot, then install TWRP using the .bat script from section 101 of post #2, then following the guide in post #1 use TWRP to flash 5.3.1.1, the 5.3.1 bootloaders, and SuperSU/Xposed/Gapps as required.
@olliebean The tutorial you linked to, in turn seems to link to a tutorial to downgrade to 4.5.3 - however, when I click that link it takes me to a thread on unbricking? I'm a bit confused. I routinely flash HTC, Samsung and Nexus phones with ease and have even rooted and installed CM on the Fire Phones I bought not too long ago, but I'll be honest - the "tutorial" provided here is extremely confusing and unclear, largely due to to all the caveats and changes that have needed to be made as more and more recent OSes have come about. Given your success, could you be so kind as to provide a bit more guidance on how you downgraded to 4.5.3?
I'm confident that once downgraded to 4.5.3, I can root via Kingroot and then run the script to get TWRP on the device and then I'm home free.
Any and all input would be GREATLY appreciated!
@Zwitterion The tutorial here should do the trick - skip step 1 assuming you're currently on v5.x. I didn't bother with JmzFireHDTool either; I just left the temporary OTA block enabled. Not sure what the difference is but it did the job considering I only had 4.5.3 installed temporarily anyway.
olliebean said:
@Zwitterion The tutorial here should do the trick - skip step 1 assuming you're currently on v5.x. I didn't bother with JmzFireHDTool either; I just left the temporary OTA block enabled. Not sure what the difference is but it did the job considering I only had 4.5.3 installed temporarily anyway.
Click to expand...
Click to collapse
Thanks so much!! I'll report back if I have any issues but I'm hoping the rest of the tutorial linked by Killa8 is straightforward. Thanks for the tip on the JMZ tool as well. I agree it doesn't make a lot of sense since we are going to upgrade manually again anyway. But perhaps it blocks OTAs even after we arrive back at 5.3.1.1?
Zwitterion said:
Thanks so much!! I'll report back if I have any issues but I'm hoping the rest of the tutorial linked by Killa8 is straightforward. Thanks for the tip on the JMZ tool as well. I agree it doesn't make a lot of sense since we are going to upgrade manually again anyway. But perhaps it blocks OTAs even after we arrive back at 5.3.1.1?
Click to expand...
Click to collapse
make_space_v02.zip, which is flashed as part of the tutorial Killa8 linked to, should take care of that.
Ahhh, perfect. Out of curiosity, did you re-upgrade to the current FireOS or go the way of CM? I want something that helps with this atrocious battery life. I'm convinced it's Amazon's OS as I saw a huge increase in battery life when I replaced FireOS with CM on the Fire phones.
Just a note that all went smoothly. I decided to flash CM after downgrading to 4.5.3 and while flashing the CM11 ROM threw a mounting error for /userdata, the flash still worked perfectly. I suspect the error was due to the ROM being built for the HD 6 with a slightly different mount point for that partition.
Thanks for the help @olliebean!
I tried CM but had problems with the headphone volume being too low. Also I didn't want to go back to KitKat after being used to Lollipop. In the end I reinstalled FireOS 5.3.1.1 along with Gapps and Xposed, and changed the default launcher to Nova, which makes it feel pretty much the same as stock Android. As far as battery life goes, I installed Greenify and AppOps and blocked the Keep Awake permissions of Amazon Metrics Service Application, Content Management Service, and Google Play Services (these being the ones that showed up most in Wakelock Detector), and my battery life is fine.
olliebean said:
I tried CM but had problems with the headphone volume being too low. Also I didn't want to go back to KitKat after being used to Lollipop. In the end I reinstalled FireOS 5.3.1.1 along with Gapps and Xposed, and changed the default launcher to Nova, which makes it feel pretty much the same as stock Android. As far as battery life goes, I installed Greenify and AppOps and blocked the Keep Awake permissions of Amazon Metrics Service Application, Content Management Service, and Google Play Services (these being the ones that showed up most in Wakelock Detector), and my battery life is fine.
Click to expand...
Click to collapse
You know, you hit it on the head. I went on a trip today and both my daughters' complained they couldn't hear the movies playing. I check it out perplexed and, sure enough, finally realized this is a known bug. Pretty catastrophic for my purposes.
Going to do exactly what you did, thanks for the specific guidance! Much appreciated.
I should probably mention, I also used Titanium Backup to freeze all the built-in Amazon apps I wasn't using, which may well have had an effect on the battery life.
can someone recommend a good ROM for my 4th gen HD 7?
Looking for a more "classic" android experience.
Orvis25 said:
can someone recommend a good ROM for my 4th gen HD 7?
Looking for a more "classic" android experience.
Click to expand...
Click to collapse
This thread literally discusses your available options.