H,
You might have seen here http://forum.xda-developers.com/kindle-fire-hdx/general/success-downgrading-t3047619/post59263205#post59263205 I managed to relatively seamlessly get my HDX rooted, adds removed and Nova Launcher installed - also using a different lock-screen.
All good, but I am now concious that I should back it up - I know there are scores of threads re TWERP and Safestrap - but can someone offer me a quick bit of advice and I'll run with that?
Is TWERP safe - would defeat the object to risk my machine installing something that has been described in a thread in here as DANGEROUS?
Is there a safe way to backup/restore my current rooted device?
Thanks...
First, what OS version do you have?
Second, you don't need to backup, you can do it in case you mess around alot!
Third, TWRP and SafeStrap are completely different, if you can unlock bootloader then install TWRP and you are good to go, if you cannot unlock you could install SafeStrap (only up to 3.2.5 if im not wrong) and you can make a backup to your Stock rom slot.
Using Stock 3.2.8
No other Mods and to be honest not interesting in tweaking anymore - but would like to have a back-up and the ability to restore if needed.
aaronkatrini said:
First, what OS version do you have?
Second, you don't need to backup, you can do it in case you mess around alot!
Third, TWRP and SafeStrap are completely different, if you can unlock bootloader then install TWRP and you are good to go, if you cannot unlock you could install SafeStrap (only up to 3.2.5 if im not wrong) and you can make a backup to your Stock rom slot.
Click to expand...
Click to collapse
TWRP is out of the question, because to install it you need to have an unlocked bootloader (version below 1x.3.2.3).
Safestrap could be possible, I need a moment to check.
But i repeat no need to backup since not interested in tweaking anymore.
So, I am not sure if you can install safestrap, but I think twrp is not compatible.
aaronkatrini said:
TWRP is out of the question, because to install it you need to have an unlocked bootloader (version below 1x.3.2.3).
Safestrap could be possible, I need a moment to check.
But i repeat no need to backup since not interested in tweaking anymore.
Click to expand...
Click to collapse
Nope, safestrap up to 1x.3.2.5 check out here http://forum.xda-developers.com/showthread.php?t=2782159&page=28 post #278
Does this mean that there is no option to back up?
@myotai: There are several apk for backup...
@aaronkatrini
don't confuse people
Safestrap works on 3.2.8
(For proof, i quote from ggow's safestrap Rom for 3.2.8)
I am very proud to bring you HDX Nexus Safestrap ROM. This is for both the Kindle Fire HDX 7" and 8.9" WIFI only variants and brings full AOSP functionality which are using Safestrap. You must be running stock firmware .3.2.4 - 3.2.8
Click to expand...
Click to collapse
http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-rom-t3024526
futzmaster said:
@myotai: There are several apk for backup...
@aaronkatrini
don't confuse people
Safestrap works on 3.2.8
(For proof, i quote from ggow's safestrap Rom for 3.2.8)
http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-rom-t3024526
Click to expand...
Click to collapse
So...does this mean that I can use it on the HDX using 3.2.8 (Safely)?
futzmaster said:
@myotai: There are several apk for backup...
@aaronkatrini
don't confuse people
Safestrap works on 3.2.8
(For proof, i quote from ggow's safestrap Rom for 3.2.8)
http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-rom-t3024526
Click to expand...
Click to collapse
Mea Culpa, I did not read that, very good to have that cleared...
aaronkatrini said:
Mea Culpa, I did not read that, very good to have that cleared...
Click to expand...
Click to collapse
No no, everything is good, you tried to help :good:
The informations are spread almost randomly on several threads... hard to keep them together
So given that I am currently using 3.2.8 with Nova Launcher etc etc...what would be the advantage of using the ROM in the link previously posted?
myotai said:
So...does this mean that I can use it on the HDX using 3.2.8 (Safely)?
Click to expand...
Click to collapse
Hi Myotia - just an opinion here; others may have a different view. If your risk tolerance is low, device stable as-is, OTAs blocked (default on 3.2.8) and you won't be tinkering with other HDX builds then I wouldn't install SafeStrap. There is nothing fundamentally wrong with SafeStrap but the installation itself introduces some risks and opens 'opportunities' that many not always be beneficial. Downside is you can't reliably create a FULL system backup of all partitions using tools that run from within Android. Many do a fine job with data and other components but I have been screwed too many times trying to execute a full system restore from a dataset that wasn't created from recovery (TWRP) or via tether. Maybe others have had better luck.
If your main objective is to protect data then there are many fine tools in the Play Store that do that well.
Davey126 said:
Hi Myotia - just an opinion here; others may have a different view. If your risk tolerance is low, device stable as-is, OTAs blocked (default on 3.2.8) and you won't be tinkering with other HDX builds then I wouldn't install SafeStrap. There is nothing fundamentally wrong with SafeStrap but the installation itself introduces some risks and opens 'opportunities' that many not always be beneficial. Downside is you can't reliably create a FULL system backup of all partitions using tools that run from within Android. Many do a fine job with data and other components but I have been screwed too many times trying to execute a full system restore from a dataset that wasn't created from recovery (TWRP) or via tether. Maybe others have had better luck.
If your main objective is to protect data then there are many fine tools in the Play Store that do that well.
Click to expand...
Click to collapse
Thanks for that!
What about Titanium Back Up Pro? Seems to have been a good friend in the past? Is it not as functional without a custom ROM?
myotai said:
What about Titanium Back Up Pro? Seems to have been a good friend in the past? Is it not as functional without a custom ROM?
Click to expand...
Click to collapse
Titanium Backup is a great tool! As mentioned, just sharing my own experiences. I have yet to have a restore fail that was captured from recovery (assuming a healthy system). Once you find something that works you tend to stick with it. I haven't tried Titanium on an HDX. Others?
Davey126 said:
Titanium Backup is a great tool! As mentioned, just sharing my own experiences. I have yet to have a restore fail that was captured from recovery (assuming a healthy system). Once you find something that works you tend to stick with it. I haven't tried Titanium on an HDX. Others?
Click to expand...
Click to collapse
Titanium backup works great on CM11 for apollo, or nexus 2.0.5 for TWRP or Magic beanz 1.0.1 :good::highfive:
I'll try it on a rooted Stock with 3.2.8 then
myotai said:
I'll try it on a rooted Stock with 3.2.8 then
Click to expand...
Click to collapse
You certainly can try, but consider also that rooted stock isnt fully android compatible, there are several parts of real android system missing, removed by Amazon (or replaced by Fire OS "equivalent"), so is possible something will not work correctly.
I have similar experience with Lightning Launcher, which crashed when I try to add widget on stock rom - response from developer was clear - FireOs is not fully compatible with Android, therefore not supported.
Safestrap works on 3.2.8
Sent from my KFTHWI using XDA Free mobile app
Related
Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
well
reconminicon said:
Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
Click to expand...
Click to collapse
you could have accomplished most of that by one of the utilities in the development section and use same. 95 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
from what I read, after you have been rolled back BY Amazon you no longer need to OTA updates ?
jimyv said:
you could have accomplished most of that by one of the utilities in the development section and use same. 94 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
Click to expand...
Click to collapse
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
Edit: Just received a reply in another thread, it isn't currently possible to rollback 13.3.2.7. Hopefully it's not too far away though. =( If you did find a way too do it with 13.3.2.7 be sure to tell us how you did it then.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
jimyv said:
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
Click to expand...
Click to collapse
I bought it for my mother for Christmas and thought would be better with Andriod.
Got it out the box connected to the internet and it automatically updated to 4.5.1. I contacted Amazon using the SOS app and told them what I wanted to do and they rolled it back. They told me I would not get any future updates and customer service might be hard in the future as it would be running different software version. They requested TS to do it and said it would take two days. The update automatically came through and updated/backdated.
The SafeStrap version would of been the most recent as I think I downloaded it from their site.
The 2.0.2 Thor Rom I mentioned worked fine. The other one would not install. Cannot remember the message I was given but when going onto the Play Store Iand trying to download the daily newspaper it was saying designed for mobile. So I guess it was based on a mobile Rom. This was no good for me and thought my mother was getting along with the Amazon OS quite good. (As she is 67 and its her first device) so I ended up installing the Amazon OS from SafeStrap.
I ended up taking it back to Argos for an exchange, said it was switching itself of as I didnt know how to get rid of SafeStrap on boot and wanted the updates back. My mother loves it.
Amazon also removed the adverts free of charge but after the emplacement they are back. Need to SOS them again.
Hope this helps as I am no pro.
Sorry. Ignore it. Was 13.3.2.6 not 13.3.2.7
kindle fire hdx 14.3.2.8 (apollo 8.9)
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
dont try to rollback you will brick your device
undulus said:
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
Click to expand...
Click to collapse
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
jeryll said:
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
Click to expand...
Click to collapse
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Well
undulus said:
But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
I am glad you have working Nexus...
For downgrading using known method you must be on firmware xx.3.2.6, xx.3.2.5, xx.3.2.4. Several peoples reported that they bricked their device trying downgrade from xx.3.2.7! You can check here, but you have been warned, dont try that on your device!!! If you brick your device I cant help you, dont know how...
Default size for system partition is fine, I think...
undulus said:
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
Hi,
which version of Safetrap you installed? All links I see are for Apollo (in the thread linked above), and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
johim said:
Hi,
which version of Safetrap you installed? All links I see are for Apollo, and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
Click to expand...
Click to collapse
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
EncryptedCurse said:
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
Click to expand...
Click to collapse
I understand. Its all working now. Its more slow than usual thou.
Another question, once installed Nexus 2.0.2, do I need to root it? Any recommended method? I'm guessing I only need to flash supersu from safetrap, tried searchin in the safetrap topic, but its huge.
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.
Hi,
I´m on 14.1.3.0 firmware with my HDX 8.9 LTE. I rooted the device. Installed Nova Launcher, Xposed Framework, HDX Module, Safestrap, a.s.o.
Now I´m on it to clean up the device from all "kindle" and "amazon" soft. Has anyone an idea which system apps have to be on the device that i can use my services from google (gmail, calender, sync, a.s.o.). Maybe there is a list of it?
The best for me is an Gapps Rom for 14.1.3.0, but i don´t think this is available here?
Cheers
maluc said:
Hi,
I´m on 14.1.3.0 firmware with my HDX 8.9 LTE. I rooted the device. Installed Nova Launcher, Xposed Framework, HDX Module, Safestrap, a.s.o.
Now I´m on it to clean up the device from all "kindle" and "amazon" soft. Has anyone an idea which system apps have to be on the device that i can use my services from google (gmail, calender, sync, a.s.o.). Maybe there is a list of it?
The best for me is an Gapps Rom for 14.1.3.0, but i don´t think this is available here?
Cheers
Click to expand...
Click to collapse
You are playing with fire removing amazon apps from stock os. Before nexus and other roms came along I ran with a configuration similar to yours (no safestrap) and identified various amazon components that were annoying and/or aggressively ran in the background consuming resources. Many could be frozen but there were often unforeseen consequences. I had a couple scares with bootlooping and failure to boot that I was fortunate to recover from. Many 'kindle' components are baked into Fire OS and can't be easily removed/disabled.
My suggestion is to install a different rom. Nexus is very stable and gives a clean android experience. CM11/12 are great as well. Given you are on 1.3.0 I would suggest ditching Safestrap in favor of native twrp opening many more doors and, perhaps most importantly, a solid path to recovery should things go wrong. Although this is probably obvious, all remnants of Fire OS are removed with a different rom (aside from low level stuff you don't care about).
As a bonus you don't have to mess around with intalling Gapps with any of the roms currently available; it's already built in
Thanks for your really forthcoming infos. On Nexus i haven't got support for my mobile Internet (3g/LTE), right?
When i install CM11/12 i need to upgrade from 3.1.0 to 3.2.3 but i habe absolutely no idea how? I do habe a stock 3.2.3 but this is a .bin file - how do i flash this? Or can i flash the New Rom.ZIP in twrp anyway?
maluc said:
Thanks for your really forthcoming infos. On Nexus i haven't got support for my mobile Internet (3g/LTE), right?
When i install CM11/12 i need to upgrade from 3.1.0 to 3.2.3 but i habe absolutely no idea how? I do habe a stock 3.2.3 but this is a .bin file - how do i flash this? Or can i flash the New Rom.ZIP in twrp anyway?
Click to expand...
Click to collapse
To the best of my knowledge there is no explicit mobile support with nexus. If you need reliable 3g/lte then your best bet is to stick with stock until confirmed working 100% in CM11/12.
The 3.2.3 bootloader update posted here is flashable from within twrp or using a utility like flashify. However, I believe it assumes twrp (or cwm) is your primary recovery. I have no idea if it would work using flashify with stock recovery and safestrap. Perhaps someone more knowledgeable can comment on this. You might want to send a PM to ggow.
Set the 3.2.3 .bin file aside for now; you don't need it.
Last I knew (from this post) you had safestrap installed. Is that still the case? You really want to get safestrap out of the picture unless there is a good reason for retaining it. Make sure you know the correct procedure for uninstalling safestrap and restoring your preferred rom.
If you already have twrp installed *and* known good backup of your current system then you could move forward with the 3.2.3 bootloader update and then install CM11 which I believe works with a locked bootloader (recognizing it may not fully support 3g/lte). I believe the current CM12 builds do required an unlocked bootloader. You can unlock but it is not always a straight forward process.
removed safestrap, backed up my device and flashed Nexus. Works perfect...only LTE is Missing
I think I try CM11 next. Thanks for your support!
maluc said:
removed safestrap, backed up my device and flashed Nexus. Works perfect...only LTE is Missing
I think I try CM11 next. Thanks for your support!
Click to expand...
Click to collapse
There's an "unofficial" release of Nexus in the original thread with LTE compiled and it works quite well, alternatively CM11 LTE works great (on my Apollo) i'm sending and receiving SMS, haven't really tried calls yet but have used Facebook messenger to make and receive VOIP calls
EDIT: My bad, it's actually on Magic Beanz http://forum.xda-developers.com/showpost.php?p=59043532&postcount=73 which I would recommend over Nexus anyway (as long as you can get TWRP going).
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.
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.