I am reading the site the last couple of hours, and I can't find a step by step for Root. I can't Enable ADB because it is not there! So I guess the method for HD is not working? Please help me and sorry if it was asked, but I can't find it,
You can't root 4.5.3, you have to roll back to 3.2.8 (and root it, plus you can install Safestrap on that build and use the Nexus 1.0.1 ROM which is Jelly Bean but that's as far as you go) and then upgrade to 4.5.2 which is still rootable with the CVE exploit.
But with 4.5.3 you're stuck, and with 4.5.4 around the corner there's a chance that update could totally block all rooting period so, be aware of this - stay away from 4.5.4 (when it becomes available) if there's even a potential update or as long as you can, and within reason roll back to 3.2.8 then bump it to 4.5.2, root that build then disable the OTA capability and go from there.
To get ADB, go into Settings, Device, Serial Number - Tap Serial Number 7 times which gives you the Developer Options (just like tapping the build number in normal Android does). Once you have them (go back a menu) you can then enable ADB from there.
But again, the recommendation is to get off 4.5.3 (at least it's my recommendation if you want any possible root at all) as soon as possible.
The instructions are here, I just got an HDX on Wednesday and I've learned quite a bit in the past 48 hours or so (no that doesn't mean I've been lurking/reading/posting for the past 48 hours, of course). It's not that tough, but it does require actual reading with comprehension and not just skimming topics or barely reading the posts in threads.
atti_mac said:
I am reading the site the last couple of hours, and I can't find a step by step for Root. I can't Enable ADB because it is not there! So I guess the method for HD is not working? Please help me and sorry if it was asked, but I can't find it,
Click to expand...
Click to collapse
In addition to the comments from br0adband be aware adding gapps (Google Play Services, Store, etc) to Fire OS can be problematic as you can not completely purge the device of Amazon equivalents. It works but not without some annoyances. At present there is a broader issue with the current release of Google Play Services (v7.3)that is impacting a wide swath of devices including many rooted Kindles. Google will likely issue a fix but they do not seem in any hurry to do so.
A rooted HDX running Fire OS 4.x isn't like other Android devices. Root helps you get around some Amazon annoyances and add addition capabilities but it's nothing like pure Android. Even simple things like changing wallpaper can be a hassle.
If you want to move forward w/root see this post for further instructions.
Davey126 said:
In addition to the comments from br0adband be aware adding gapps (Google Play Services, Store, etc) to Fire OS can be problematic as you can not completely purge the device of Amazon equivalents. It works but not without some annoyances. At present there is a broader issue with the current release of Google Play Services (v7.3)that is impacting a wide swath of devices including many rooted Kindles. Google will likely issue a fix but they do not seem in any hurry to do so.
A rooted HDX running Fire OS 4.x isn't like other Android devices. Root helps you get around some Amazon annoyances and add addition capabilities but it's nothing like pure Android. Even simple things like changing wallpaper can be a hassle.
If you want to move forward w/root see this post for further instructions.
Click to expand...
Click to collapse
It said : "Put roolback file into the Internal storage folder of your Kindle." !
I downloaded a "mod-update-kindle-thor-13.3.2.8_user_713328020" folder and i have no idea where I have to copy it. I just did it to a main folder put it between the "Kindle" and "Movies" but it doesn't do anything when I want to do an update. Without wifi, didn't even start.
UPDATE, just realized i had to copy a "bin" file not a folder version. So now is downgrading. How to root 3.2.8? should i update to 4.5.2 first and root or root the 3.2.8?
update
I was able to downgrade , and upgrade to 4.5.2, rooted, and I was able to follow the other guides to disable OTA updates.
But when I try to install the Google play apps, it said at step 1 "aquire the GApps.."http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
So when I followed the link , it takes me here :http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
And Step 2 Boot into recovery to able to install Zip file....
I can't boot in recovery, the step by step guide said power on, and when i will see the "kindle fire" hold the power till turns blue and let it go. Mine newer turns blue just orange and if I let the power go nothing happen.
Will you guys help? I am so close!
Do not do the recovery instructions. Grab the file from the link and follow the instructions from this forum. If you are rooted, be very careful with stock recovery.
The spoiler is instead of installing the zip, unzip it and copy many of the files to their respective folders. Skip priv/app/ setupwizard.apk and priv/app/prebuiltgmscore.apk. install the gms core as a normal app and you are good to go... almost. Look around the HDX general threads for a fix to prevent google play services updating themselves.
Good luck
Sent from my KFTHWI using Tapatalk
a chinese root toolkit named Kingroot seems able to support Fire OS 4.5.3 now. Several guys tested it and succeeded.
but it contians a su manager named KingUser from the same company. if anybody can install SuperSU instead, you can have a try.
some one dont understand chinese? PM me, i can help.
BTW. Personally, I never recommend Chinese APPs from chinese companies. They use the APPs/Softwares to play a role as thief to steal your information, contacts, maybe more. And they always ask for more permissions.
For economic benefits, they can do anything.
FotixChiang said:
a chinese root toolkit named Kingroot seems able to support Fire OS 4.5.3 now. Several guys tested it and succeeded.
but it contians a su manager named KingUser from the same company. if anybody can install SuperSU instead, you can have a try.
some one dont understand chinese? PM me, i can help.
BTW. Personally, I never recommend Chinese APPs from chinese companies. They use the APPs/Softwares to play a role as thief to steal your information, contacts, maybe more. And they always ask for more permissions.
For economic benefits, they can do anything.
Click to expand...
Click to collapse
FYI recieved OTA 4.5.4 and it breaks root. Kingroot 4.1 no longer works.
koda1789 said:
FYI recieved OTA 4.5.4 and it breaks root. Kingroot 4.1 no longer works.
Click to expand...
Click to collapse
Must be a lucky day that I've just rooted 4.5.3 with Kingroot and disabled OTA today :fingers-crossed:
koda1789 said:
FYI recieved OTA 4.5.4 and it breaks root. Kingroot 4.1 no longer works.
Click to expand...
Click to collapse
Unbelievable. Had an HDX 7" with 13.3.1.0, rooted, was ready to unlock bootloader and install CM12. Received a surprise visit, and when I got back to my desk I was on 4.5.4...
Bad day...
Well, it could be worse, you could have gotten bricked during the update.
Davey126 said:
In addition to the comments from br0adband be aware adding gapps (Google Play Services, Store, etc) to Fire OS can be problematic as you can not completely purge the device of Amazon equivalents. It works but not without some annoyances. At present there is a broader issue with the current release of Google Play Services (v7.3)that is impacting a wide swath of devices including many rooted Kindles. Google will likely issue a fix but they do not seem in any hurry to do so.
A rooted HDX running Fire OS 4.x isn't like other Android devices. Root helps you get around some Amazon annoyances and add addition capabilities but it's nothing like pure Android. Even simple things like changing wallpaper can be a hassle.
If you want to move forward w/root see this post for further instructions.
Click to expand...
Click to collapse
Watch this video to fix that issue with Google Play Services...
[Fix] - Play store and COC not Working on Kindle …: https://youtu.be/7RxuP9X3Mgo
Ali Ejea Mc said:
Watch this video to fix that issue with Google Play Services...
[Fix] - Play store and COC not Working on Kindle …: https://youtu.be/7RxuP9X3Mgo
Click to expand...
Click to collapse
Thanks.
Another option now exists for locked devices that involves replacing FireOS with Nexus which natively supports the Play store. See: http://forum.xda-developers.com/showthread.php?t=3137840
Related
I now have a second Thor, and it's on 3.0.5. What kind of things can I do to this?
fdigl said:
I now have a second Thor, and it's on 3.0.5. What kind of things can I do to this?
Click to expand...
Click to collapse
Some suggestions:
-root and block OTA with HDX toolkit (link)
-install TWRP
-update bootloader to 3.2.3 (link)
-ROMS: Nexus 2.0.5 or CM11
-optional: unlock bootloader (thread)
-ROMS: as above plus CM12
Unlocking the bootloader is the most involved but opens additional options and (more importantly) offers a more robust recovery capability should things go wrong.
Most important thing you can do now is 1) stay off WiFi until OTA is effectively blocked; and 2) read, read and read some more. You've likely seen numerous 'brick' posts. Most were the result of rushed actions and/or incomplete research. Do your homework and ask questions along the way. Good luck.
Davey126 said:
Some suggestions:
-root and block OTA with HDX toolkit (link)
-install TWRP
-update bootloader to 3.2.3 (link)
-ROMS: Nexus 2.0.5 or CM11
-optional: unlock bootloader (thread)
-ROMS: as above plus CM12
Unlocking the bootloader is the most involved but opens additional options and (more importantly) offers a more robust recovery capability should things go wrong.
Most important thing you can do now is 1) stay off WiFi until OTA is effectively blocked; and 2) read, read and read some more. You've likely seen numerous 'brick' posts. Most were the result of rushed actions and/or incomplete research. Do your homework and ask questions along the way. Good luck.
Click to expand...
Click to collapse
Thanks! In Xposed Installer, the framework section is just blank white. No buttons or dropdowns, just white. Everything else in the app appears normal. I can't install the framework for HDXposed.
fdigl said:
Thanks! In Xposed Installer, the framework section is just blank white. No buttons or dropdowns, just white. Everything else in the app appears normal. I can't install the framework for HDXposed.
Click to expand...
Click to collapse
HDXposed is not on the list. There is no need for this module as it has long been depreciated and of questionable value given more current alternatives. Strongly suggest not installing stuff or traveling your own path. Also recommend uninstalling Xposed framework and any other 'system' level hacks/utilities until your devices is otherwise upgraded and stable. Just asking for trouble ...
While I have the pulpit don't mess with build.prop or any system file other than OTAcerts (even that can be avoided). If you are following a guide that indicates one/both should be modified you're in the wrong place. Post a question; someone will help you get back on track.
Davey126 said:
HDXposed is not on the list. There is no need for this module as it has long been depreciated and of questionable value given more current alternatives. Strongly suggest not installing stuff or traveling your own path. Also recommend uninstalling Xposed framework and any other 'system' level hacks/utilities until your devices is otherwise upgraded and stable. Just asking for trouble ...
While I have the pulpit don't mess with build.prop or any system file other than OTAcerts (even that can be avoided). If you are following a guide that indicates one/both should be modified you're in the wrong place. Post a question; someone will help you get back on track.
Click to expand...
Click to collapse
Oh, thanks for the info!
Anyways, I have Android Market working but Play Store just crashes while opening. I have the same version of Play Store running on the older Thor, but not this one. It just stops working, but behind the dialogue I can see another one under it, likely the Play Store agreement, but it closes when I close the stopped working dialogue. This makes Play Store unusable.
fdigl said:
Oh, thanks for the info!
Anyways, I have Android Market working but Play Store just crashes while opening. I have the same version of Play Store running on the older Thor, but not this one. It just stops working, but behind the dialogue I can see another one under it, likely the Play Store agreement, but it closes when I close the stopped working dialogue. This makes Play Store unusable.
Click to expand...
Click to collapse
Play Store works great on the three roms previously mentioned while various issues keep cropping up using it with Fire OS. I suggest you flash TWRP, the 3.2.3 bootloader update and Nexus 2.05. Each is relatively low risk (given your favorable starting point; many would love to have that device!) if you follow directions. In the end I think you will be much happier with the overall experience. Perhaps someone else can help if you want to continue with Fire OS 3.x and sideload gapps.
Davey126 said:
Play Store works great on the three roms previously mentioned while various issues keep cropping up using it with Fire OS. I suggest you flash TWRP, the 3.2.3 bootloader update and Nexus 2.05. Each is relatively low risk (given your favorable starting point; many would love to have that device!) if you follow directions. In the end I think you will be much happier with the overall experience. Perhaps someone else can help if you want to continue with Fire OS 3.x and sideload gapps.
Click to expand...
Click to collapse
I have Safestrap 3.72 on there, does that count as TWRP? Despite this, I'd prefer to keep Fire OS on here.
To get gapps working on fire is, look at the version of google play services. Some people have no problems. I am running 7.0.99 I think.
fdigl said:
I have Safestrap 3.72 on there, does that count as TWRP? Despite this, I'd prefer to keep Fire OS on here.
Click to expand...
Click to collapse
Nope. TWRP in Safestrap does not operate in 'native' mode. If you prefer Fire OS then your options are limited:
- create another slot in Safestrap and install Nexus 1.0.5 (note different version number) which offers full Play Store support. Make sure you preserve your existing copy of Fire OS in the base slot; bad things happen if it gets trashed. You can then toggle between Fire OS and Nexus although the two roms can not share applications (they operate independently)
- continue wrestling Play Store (and other Google components) on Fire OS 3.x.
- permit your device to upgrade to the version 4.x of Fire OS which is a modest improvement over 3.x. You will be faced with the same headaches getting Google Components to play nice with Fire OS but you will likely receive better community support. Please note this is a one way trip. Once you go beyond 3.2.6 you can not make the modifications required to run most non-Amazon roms like CM11/12.
Davey126 said:
Nope. TWRP in Safestrap does not operate in 'native' mode. If you prefer Fire OS then your options are limited:
- create another slot in Safestrap and install Nexus 1.0.5 (note different version number) which offers full Play Store support. Make sure you preserve your existing copy of Fire OS in the base slot; bad things happen if it gets trashed. You can then toggle between Fire OS and Nexus although the two roms can not share applications (they operate independently)
- continue wrestling Play Store (and other Google components) on Fire OS 3.x.
- permit your device to upgrade to the version 4.x of Fire OS which is a modest improvement over 3.x. You will be faced with the same headaches getting Google Components to play nice with Fire OS but you will likely receive better community support. Please note this is a one way trip. Once you go beyond 3.2.6 you can not make the modifications required to run most non-Amazon roms like CM11/12.
Click to expand...
Click to collapse
It seems that I got Play Store 4.6.17 to work, but I'm unable to download anything (will spam ANRs). In HDXposed, did the content provider fix have to do with any of this? I have it on the older Thor, but not on the new one. If it does, what would be the alternative way of applying that fix?
EDIT: Any version of Play Store is working, just unable to download/install from the store.
lekofraggle said:
To get gapps working on fire is, look at the version of google play services. Some people have no problems. I am running 7.0.99 I think.
Click to expand...
Click to collapse
I know how to get GApps working, it's just Play Store that's acting up.
fdigl said:
I know how to get GApps working, it's just Play Store that's acting up.
Click to expand...
Click to collapse
I meant play store. That is the problem most people are having. Take a look at the two threads in the general section.
Sent from my KFTHWI using Tapatalk
fdigl said:
Thanks! In Xposed Installer, the framework section is just blank white. No buttons or dropdowns, just white. Everything else in the app appears normal. I can't install the framework for HDXposed.
Click to expand...
Click to collapse
What version of Xposed Installer are you using?
Davey126 said:
HDXposed is not on the list. There is no need for this module as it has long been depreciated and of questionable value given more current alternatives. Strongly suggest not installing stuff or traveling your own path. Also recommend uninstalling Xposed framework and any other 'system' level hacks/utilities until your devices is otherwise upgraded and stable. Just asking for trouble ...
While I have the pulpit don't mess with build.prop or any system file other than OTAcerts (even that can be avoided). If you are following a guide that indicates one/both should be modified you're in the wrong place. Post a question; someone will help you get back on track.
Click to expand...
Click to collapse
EncryptedCurse said:
What version of Xposed Installer are you using?
Click to expand...
Click to collapse
I tried the latest, and v32 - the one that worked on my Thor on 3.2.5. The tablet in question is on 3.0.5, but installed TWRP and the 3.2.3 boot loader zip was flashed.
I just inherited a 3rd Gen Kindle Fire HDX 7" that is running latest firmware (4.5.5). I am a newb to Kindle but not Android devices
I want to run some apk not available in Amazon Apps (Guitar apps) . Is there a way to root this newest firmway to get google play store as well as Amazon's store. If not, can I side load APKS if I have them. I was surprised to see when I connected to my computer, I couldn't access directories - Is therer a way to access the system directories to sideload apks or do I need to email them/dropbox them etc?
Just not sure what I can do withthe 4.5.5 firmware as it seems like the latest updates are hard to modify.
Any advice would be appreciated.
Thanks,
Michael
guitar1969 said:
I just inherited a 3rd Gen Kindle Fire HDX 7" that is running latest firmware (4.5.5). I am a newb to Kindle but not Android devices
I want to run some apk not available in Amazon Apps (Guitar apps) . Is there a way to root this newest firmway to get google play store as well as Amazon's store. If not, can I side load APKS if I have them. I was surprised to see when I connected to my computer, I couldn't access directories - Is therer a way to access the system directories to sideload apks or do I need to email them/dropbox them etc?
Just not sure what I can do withthe 4.5.5 firmware as it seems like the latest updates are hard to modify.
Any advice would be appreciated.
Thanks,
Michael
Click to expand...
Click to collapse
You can obtain root and run different roms but the process is tedious and carries some risk. Basic steps: rollback to 3.2.8 -> upgrade to 4.5.2 -> root; block OTA -> install Safestrap v4 -> flash Nexus v4 or CM11. Each step takes time to research and instructions must be followed carefully to avoid an unrecoverable brick (especially during rollback). Kindles in general and HDX models in particular are easy to kill and nearly impossible to recover once they go belly up.
FireOS does allow for the installation of alternative market places (eg: 1mobile) and sideloading apps. Most apps work reasonably well although there can be problems as Amazon heavily customized AOSP Andriod as you can tell from the FireOS UI. Installing Google Play services/store is a significant challenge that tends to break easily and be full of compromises. Given the choice most HDX users will go for another rom vs fighting with a FrankenKindle comprised of Amazon/FireOS and Google components.
Best way to begin is start reading through the forums. There are no step-by-step guides although some individual posts contain a wealth of information. As you become more familiar with the procedures ask targeted questions. You'll generally get a prompt response if you have done your homework first. Good luck.
Davey126 said:
You can obtain root and run different roms but the process is tedious and carries some risk. Basic steps: rollback to 3.2.8 -> upgrade to 4.5.2 -> root; block OTA -> install Safestrap v4 -> flash Nexus v4 or CM11. Each step takes time to research and instructions must be followed carefully to avoid an unrecoverable brick (especially during rollback). Kindles in general and HDX models in particular are easy to kill and nearly impossible to recover once they go belly up.
FireOS does allow for the installation of alternative market places (eg: 1mobile) and sideloading apps. Most apps work reasonably well although there can be problems as Amazon heavily customized AOSP Andriod as you can tell from the FireOS UI. Installing Google Play services/store is a significant challenge that tends to break easily and be full of compromises. Given the choice most HDX users will go for another rom vs fighting with a FrankenKindle comprised of Amazon/FireOS and Google components.
Best way to begin is start reading through the forums. There are no step-by-step guides although some individual posts contain a wealth of information. As you become more familiar with the procedures ask targeted questions. You'll generally get a prompt response if you have done your homework first. Good luck.
Click to expand...
Click to collapse
Thanks, I am able to sideload apps from my Android phone, but have issues with some of my apps that I have license keys for only on Google Play and my Google account.
I am actually not interested in running custom ROMs, just acquiring Root on 4.5.5. From all that I have read, Root is not possible on 4.5.5 as of yet.
guitar1969 said:
Thanks, I am able to sideload apps from my Android phone, but have issues with some of my apps that I have license keys for only on Google Play and my Google account.
I am actually not interested in running custom ROMs, just acquiring Root on 4.5.5. From all that I have read, Root is not possible on 4.5.5 as of yet.
Click to expand...
Click to collapse
Correct. But you can obtain root on 4.5.2 and there is a bumpy path from 4.5.5 -> 4.5.2. I am not advocating that choice (quite the opposite) but stating for clarity. From a feature/functionality/stability perspective there is very little difference between subversions in the 4.5.x series through 4.5.5.
How do i downgrade my kindle fire to get root access or do i need to use fireroot?
thanks
50pounds said:
How do i downgrade my kindle fire to get root access or do i need to use fireroot?
Click to expand...
Click to collapse
This marks the second reference to 'fireroot' in less than a week. For the benefit of the poster any anyone else who may may stumble across this: fireroot does not work on HDX models and will likely brick the device.
To obtain root you must rollback to 3.2.8, upgrade to 4.5.2 and then use Kingroot or another proven method. The rollback is risky; those who choose this path should fully understand the procedure and follow directions carefully to avoid trashing their device. Note 4th gen 8.9" models (Saturn) can not be rolled back; there is no root option at present.
3.2.8 rollback discussion thread here. Spend some time reading before taking action. There are no scripts, videos or step-by-step noob guides. Post questions if unsure.
Cheers dave sorted it now ?
My main device is a lovely 5thGen Fire (the $49 one), but I just got a used 2014 HD7 (model identifies as 4th Generation) as a secondary. It showed up on my doorstep already updated to 5.1.2. (I think when the previous owner did a wipe, 5.1.2 got dumped on it)
I'm not interested currently in rooting, removing ads, and can put up with the bloat if needed. ALL I really need essentially is a working Google Play store on this HD7-4th-Gen. If that's possible without rooting or backloading previous OS versions I mean.
Under earlier versions of the OS I know there were ways to put Play on without rooting. My question is if there are easy tested scripts or methods to get Play on and working that definitely work under 5.1.2, or do I have to finagle some earlier version of the OS onto the device and root just to get Play now?
Thanks.
(just in case it's relevant, I already have the Developer options turned on, ADB allowed, and ES File Explorer installed from the Amazon Store, figuring the most likely approach to getting Play on might involve one or more of those)
snark.shark said:
My main device is a lovely 5thGen Fire (the $49 one), but I just got a used 2014 HD7 (model identifies as 4th Generation) as a secondary. It showed up on my doorstep already updated to 5.1.2. (I think when the previous owner did a wipe, 5.1.2 got dumped on it)
I'm not interested currently in rooting, removing ads, and can put up with the bloat if needed. ALL I really need essentially is a working Google Play store on this HD7-4th-Gen. If that's possible without rooting or backloading previous OS versions I mean.
Under earlier versions of the OS I know there were ways to put Play on without rooting. My question is if there are easy tested scripts or methods to get Play on and working that definitely work under 5.1.2, or do I have to finagle some earlier version of the OS onto the device and root just to get Play now?
Thanks.
(just in case it's relevant, I already have the Developer options turned on, ADB allowed, and ES File Explorer installed from the Amazon Store, figuring the most likely approach to getting Play on might involve one or more of those)
Click to expand...
Click to collapse
Your best bet is to go to the Gen 5 XDA forum:
http://forum.xda-developers.com/amazon-fire
The devices are literally identical if you want rootless GAPPS. So look for what's offered there.
The 4th gen is actually very lucky because it's possible to sideload FireOS 4, get TWRP, and be off to the races (no downgrade bricking if going to 4.5.3). For 5th gen, if you upgraded from 5.0.1, your options shrink considerably.
bibikalka said:
Your best bet is to go to the Gen 5 XDA forum:
http://forum.xda-developers.com/amazon-fire
The devices are literally identical if you want rootless GAPPS. So look for what's offered there.
Click to expand...
Click to collapse
They've pointed me right back here to this forum when I asked there.
I can't be the only person with a 4th Gen HD7 where it's been updated to 5.1.2 who JUST wants Google Play. That 5.1.2 update was pushed out to the 4th Gen devices in February, according to the System Updates screen on the device, so that's why a month later I'm thinking it's probable SOMEONE else out there has tried this. I just hope they see this thread.
Worst case I will go through the OS backdate and rooting stuff, but that actually seems like a heck of a lot more work (and risk) if a simpler approach to just get Play works. The key for me is just finding out if it really DOES work and which tools it works with. Is it as simple as tracking down an running an APK file for Play, or has there always been more involved (changing other background files or permissions)? And again, if someone has already done this work for 5.1.2 and HD74th Gen, where it's been documented.
I guess I'll give this a few days to sit here and see what pops up, and resort to the root approach if nobody comes along with info by then.
snark.shark said:
They've pointed me right back here to this forum when I asked there.
I can't be the only person with a 4th Gen HD7 where it's been updated to 5.1.2 who JUST wants Google Play. That 5.1.2 update was pushed out to the 4th Gen devices in February, according to the System Updates screen on the device, so that's why a month later I'm thinking it's probable SOMEONE else out there has tried this. I just hope they see this thread.
Worst case I will go through the OS backdate and rooting stuff, but that actually seems like a heck of a lot more work (and risk) if a simpler approach to just get Play works. The key for me is just finding out if it really DOES work and which tools it works with. Is it as simple as tracking down an running an APK file for Play, or has there always been more involved (changing other background files or permissions)? And again, if someone has already done this work for 5.1.2 and HD74th Gen, where it's been documented.
I guess I'll give this a few days to sit here and see what pops up, and resort to the root approach if nobody comes along with info by then.
Click to expand...
Click to collapse
Most of the people here are strictly volunteers, and usually work on things that are of personal interest or of broad general value. With Fire HDs 4th gen we are lucky that easy root was available since May 2015. So all the guides go through root because it's the most general and convenient way to customize the stock OS.
5th gen Fires had a bit of lag to get root, so people developed ways to get GAPPS installed under FireOS 5 without root. Also, the user base there is a lot bigger, so more people were looking into this. You'll have to do a big of research to find scripts that install only GAPPS, and do not try any of the Gen 5 specific tricks. Right now FireOS 5.1.2 has identical versions for both 4th and 5th gen, so any general FireOS 5 tricks would work on both generations.
So instead of being very surprised that nobody met your exact need, just do your research on the 5th gen forum, and when you find a script that works (as is or perhaps customized by you), do come back and post it here for future reference !
Good luck
snark.shark said:
I can't be the only person with a 4th Gen HD7 where it's been updated to 5.1.2 who JUST wants Google Play.
Click to expand...
Click to collapse
OK, here is your solution.
Option 1, try the classic :
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Just run the script in Amazon-Fire-5th-Gen-Install-Play-Store.zip , if it comes to worst, a factory reset will get you right back.
Option 2
Go here, follow the instructions to get adb talking to your Fire (drivers & all), make sure adb works:
http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804
Download the AutoRootScriptv4.14NODEBLOAT.zip file, unpack. In a DOS window, navigate to this unpacked WindowsAutoRootFire. DO NOT RUN THE BAT FILE !!!
Instead, type the commands :
Code:
adb install com.google.android.gms-6.6.03_(1681564-036)-6603036-minAPI9.apk
adb install GoogleLoginService.apk
adb install GoogleServicesFramework.apk
adb shell pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
adb install com.android.vending-5.9.12-80391200-minAPI9.apk
Launch Google Play Store.
thx
Does someone have an easier to follow guide for rooting and installing the Play store on a 4th gen Fire HD 7?
I've looked through a couple of the stickied guides and they're full of a lot of hard work and information but they're (IMO, and no offense) a little bit all unorganized/hard to follow/confusing, and seems a lot of it is outdated info now, since there are newer versions of Fire OS. They also assume you know the basics, which I don't. I've done similar things to other devices in the past but there were easy to follow guides.
If not, what are the basic steps I would need to specifically follow, if I want to update to the newest that still allows root?
Also what would updated in the future involve the same steps? I plan to give the FHD to my father. But I guess it would be OK if it stayed on the same OS version from here on out. Or, after installing Play, does it not require root anymore, to run Play, thus OTA updates would still work (which breaks root I think)?
This FHD has 4.5.5. I've enabled ADB on the FHD
I can't see the FHD's system folder (to disable OTA) through Windows Explorer. Does Android Studio have to be installed to do that? Android Studio requires the bloated Java to be installed, which I'd rather not do if possible.
Thanks
I just posted this: http://forum.xda-developers.com/fire-hd/general/root-os-5-1-2-kingroot-tools-play-store-t3371824. If it's too hard, please give me some feedback.
DoLooper said:
I just posted this: http://forum.xda-developers.com/fire-hd/general/root-os-5-1-2-kingroot-tools-play-store-t3371824. If it's too hard, please give me some feedback.
Click to expand...
Click to collapse
sounds like this package is everything you need to make it a android feel.
Hi there. I'm really confused about how to proceed and would appreciate some help.
I have a Kindle Fire HDX 7 (3rd Gen) on which I would like to wipe the Fire OS, and replace it with a working, functional Android ROM. I have some basic competence with installing software, flashing phones, etc., but am by no means an expert. I have both Windows & Linux PCs with which to connect.
A year or so ago I tried to get the tablet working with Google Apps, etc.. I can't remember precisiely what I did (!), but I think I used TWRP, I rolled back the operating system to 4.5.2, turned off the updates, and installed a Google Apps piece of software. The tablet then worked reasonably well, but not great. By that I mean I could web browse, and download and use some apps from the Play Store, but lots of stuff didn't work preoperly. At some time since then, the tablet decided it no longer wanted to install/update from the Play Store, and more of the apps have stopped working. I can still web browse.
TBH, I've got to the point where if I can't completely replace the OS then I think I'm just going to stop using it.
What steps should I take to get a 'proper' ROM working on the tablet?
Thanks very much in advance for any help,
Aaron
alhroot said:
Hi there. I'm really confused about how to proceed and would appreciate some help.
I have a Kindle Fire HDX 7 (3rd Gen) on which I would like to wipe the Fire OS, and replace it with a working, functional Android ROM. I have some basic competence with installing software, flashing phones, etc., but am by no means an expert. I have both Windows & Linux PCs with which to connect.
A year or so ago I tried to get the tablet working with Google Apps, etc.. I can't remember precisiely what I did (!), but I think I used TWRP, I rolled back the operating system to 4.5.2, turned off the updates, and installed a Google Apps piece of software. The tablet then worked reasonably well, but not great. By that I mean I could web browse, and download and use some apps from the Play Store, but lots of stuff didn't work preoperly. At some time since then, the tablet decided it no longer wanted to install/update from the Play Store, and more of the apps have stopped working. I can still web browse.
TBH, I've got to the point where if I can't completely replace the OS then I think I'm just going to stop using it.
What steps should I take to get a 'proper' ROM working on the tablet?
Thanks very much in advance for any help,
Aaron
Click to expand...
Click to collapse
There's a good chance you can replace FireOS with CM11 or Nexus, two popular ROMs that are well suited to this device. First order of business is to assess the current status of your device. What version of FireOS is currently installed? It it reasonably stable? Many times laying Google components over FireOS creates other issues that can interfere with components needed to support an alternative rom.
Davey126 said:
There's a good chance you can replace FireOS with CM11 or Nexus, two popular ROMs that are well suited to this device. First order of business is to assess the current status of your device. What version of FireOS is currently installed? It it reasonably stable? Many times laying Google components over FireOS creates other issues that can interfere with components needed to support an alternative rom.
Click to expand...
Click to collapse
Davey, thanks for the reply.
I've just checked, and the Fire OS version running on the tablet is 4.5.2.
The device is stable.
alhroot said:
Davey, thanks for the reply.
I've just checked, and the Fire OS version running on the tablet is 4.5.2.
The device is stable.
Click to expand...
Click to collapse
Next step is to allow the device to update to FireOS 4.5.5.1. While you could get by with 4.5.2 the newest rom builds require low level (kernel) components that get installed with 4.5.5.1. Replacing FireOS is the only way to get these pups on an HDX; there is no way to install them separately.
To obtain 4.5.5.1 you need to unblock OTA updates which typically involves renaming a file back to its original ID using a tool such as ES File Explorer. Search for a file starting with 'DeviceSoftwareOTA' which is typically located in /system/priv-app/. It will probably be called 'DeviceSoftwareOTA.bak' or something similar. Rename that to 'DeviceSoftwareOTA.apk', reboot and check for updates. You will loose root if 4.5.5.1 is successfully found/installed but you can get it back fairly easily.
FWiW - There are other methods of blocking OTA updates such as renaming the otacerts.zip file. That approach is less common on this device.
Davey126 said:
Next step is to allow the device to update to FireOS 4.5.5.1. While you could get by with 4.5.2 the newest rom builds require low level (kernel) components that get installed with 4.5.5.1. Replacing FireOS is the only way to get these pups on an HDX; there is no way to install them separately.
To obtain 4.5.5.1 you need to unblock OTA updates which typically involves renaming a file back to its original ID using a tool such as ES File Explorer. Search for a file starting with 'DeviceSoftwareOTA' which is typically located in /system/priv-app/. It will probably be called 'DeviceSoftwareOTA.bak' or something similar. Rename that to 'DeviceSoftwareOTA.apk', reboot and check for updates. You will loose root if 4.5.5.1 is successfully found/installed but you can get it back fairly easily.
FWiW - There are other methods of blocking OTA updates such as renaming the otacerts.zip file. That approach is less common on this device.
Click to expand...
Click to collapse
Bang on.
I renamed the file from '.bak' to '.apk', rebooted, and did a couple of updates cycles.
I'm now on FireOS 4.5.5.1 ...
alhroot said:
Bang on.
I renamed the file from '.bak' to '.apk', rebooted, and did a couple of updates cycles.
I'm now on FireOS 4.5.5.1 ...
Click to expand...
Click to collapse
Fantastic! Next step is to root with KingRoot (apk or tethered version). After that the good stuff starts happening. Sorry for piecemealing out details; I find it works better in the absence of an A to Z guide.
Be out-of-pocket for a few hours; will look for your response later.
Davey126 said:
Fantastic! Next step is to root with KingRoot (apk or tethered version). After that the good stuff starts happening. Sorry for piecemealing out details; I find it works better in the absence of an A to Z guide.
Be out-of-pocket for a few hours; will look for your response later.
Click to expand...
Click to collapse
Okay, I think that's all good ... Kingroot apk downloaded & installed, device rooted, turned on root explorer in ES File Explorer as a test: prompted for permission.
Davey, thanks again for your help.
So now for the good stuff ... ??? :good:
alhroot said:
Okay, I think that's all good ... Kingroot apk downloaded & installed, device rooted, turned on root explorer in ES File Explorer as a test: prompted for permission.
Davey, thanks again for your help.
So now for the good stuff ... ??? :good:
Click to expand...
Click to collapse
Excellent. Next step is to install Safestrap 4.0.1 which provides a pseudo recovery environment that supports the installation of custom roms. It looks a lot like TWRP (but isn't). You can snag the app from here; be sure to select the appropriate format. Once installed launch the app and install Safestrap recovery which is the component that does the heavy lifting.
Important: Once Safestrap recovery is installed never (never!) attempt a 'factory reset' - either from the stock recovery menu or from within FireOS. Doing so will brick the device with no possible recovery.
Now reboot. You'll notice a new screen that has a couple options at the bottom. Select the option that launches Safestrap recovery. Take a look around but don't change anything. When ready return to the home screen and then go into the backup section. Take a backup of your current FireOS installation (selection all partitions). You will want this should you every want to restore you device to it's current configuration. The resulting files will be quite large and should be copied to another device for safe keeping. Exit Safestrap and reboot into FireOS. Tether your device and copy the files to a suitable host. You seem to be familiar with ES File Explorer so should have no problem finding them. Should be in the TWRP directory located within sdcard (or just browse internal storage from the host machine).
Next step is to decide which rom to flash. Two are available/compatible with Safestrap 4.0.1: CM11 and Fire Nexus which are both KitKat based. Both are solid, feature complete and regularly updated with security patches. My daily driver on this device is Nexus as I prefer to build upon a pure Android foundation. That said, CM11 is a fine choice and my preferred rom on secondary devices as it contains a suite of nice UI enhancements minimizing post flash tweaks. FWIW - Lollipop+ roms are not an option as they require an unlocked bootloader which is not possible on your device.
Once you decide upon a rom I'll provide the final set of instructions (really best practices) for installing the rom and related components such as Google Play Services/Store. Feel free to read through the linked threads which contain numerous 'how-to' posts, especially the first couple posts in the rom threads. If all goes well you'll be running a custom rom by this time tomorrow.
Another step complete ...
I downloaded the Safestrap apk from the link contained in the thread, choosing THOR (HDX 7"), installed the app, then installed the recovery software. After a reboot I backed up, and then copied the resultant folder to a PC.
Question: The back up folder is really big (4GB) ... is it okay if I now delete the back up on the tablet? To do this, can I just delete with ESFE?
Duly noted about not doing a factory reset.
After having a read, I think I'm happy to go with the Nexus ROM - keeping things as clean as possible. It sounds like it's very solid with no real issues.
Davey, thanks once again for your precise and excellent help.
Cheers,
Aaron
alhroot said:
Another step complete ...
I downloaded the Safestrap apk from the link contained in the thread, choosing THOR (HDX 7"), installed the app, then installed the recovery software. After a reboot I backed up, and then copied the resultant folder to a PC.
Question: The back up folder is really big (4GB) ... is it okay if I now delete the back up on the tablet? To do this, can I just delete with ESFE?
Duly noted about not doing a factory reset.
After having a read, I think I'm happy to go with the Nexus ROM - keeping things as clean as possible. It sounds like it's very solid with no real issues.
Davey, thanks once again for your precise and excellent help.
Cheers,
Aaron
Click to expand...
Click to collapse
Super! Final step is to install Nexus. Grab the Thor (nickname for 3rd gen HDX 7) installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
Boot into Safestrap recovery. Use the File Manager (under advanced) to confirm the existence/location of the Nexus rom zip. Return to the home screen and then access the wipe menu. Use the slider at the bottom to perform a factory reset which wipes the data, cache and dalvik partitions. Note this is different that a stock 'factory reset' which was discussed in a previous post. Also note it is impossible to wipe the system partition in Safestrap v4 even if selected in the advanced section. I won't get into the reasons; just know it isn't necessary for the upcoming operation.
Return to the home screen and select install. Navigate to the folder containing the Nexus rom, select it and then and then swipe the slider at the bottom to install (flash) the zip which will overwrite FireOS. When complete (assuming no errors) reboot your tablet and select continue to fire up Nexus. First boot make take some time as caches are populated. However, anything over 5 min indicates a problem. Once Nexus starts I assume you know where to go from there. You can safely enable WiFi, register with Google and perform all other requested initialization steps.
A few final footnotes:
- Nexus is pretty bare bones; not even a browser in included in the base build. Head over to the Play Store to grab what you need
- While Google's stock launcher is nice I suggest replacing it with Nova which offers a superior AOSP experience along with robust customization
- Xposed Framework and associated modules offers some excellent additions to this rom if you wish to customize further (advanced topic)
- Once you are confident Nexus is stable you can delete the huge FireOS backup created in an earlier step. Either via ESFE or from Safestrap
You may be aware Safestrap supports multi-boot through the use of user created slots. Unfortunately, they do not work with this device and can lead to unrecoverable bricks. You'll see various cautions in the Safestrap, Nexus and CM threads. Short version: do not create or use secondary slots.
Aaron - Feel free to post any questions/concerns/comments. Someone from the HDX community will likely respond within 24-48 hours. On a personal note it's been awhile since I did a long hand 'step-by-step' which is a refreshing change of pace from the usual bullets. I appreciate your patience as I dusted off various cob webs and hope you make the most out of your newly liberated device.
Nice!
Nexus installed, and I'm using it right now ?
Absolutely superb help Davey. I was totally confused trying to work out how to go from where I was to where am now, and you've completely sorted me out. A massive thanks from me.
Everything seems to be working well (!) ... I'm going to test things out a bit more before deleting the FireOS back up folder. I think I messed around with the xposed framework before... I'll definitely take another look.
Seriously, thank you.
Cheers,
Aaron
alhroot said:
Nice!
Nexus installed, and I'm using it right now ?
Absolutely superb help Davey. I was totally confused trying to work out how to go from where I was to where am now, and you've completely sorted me out. A massive thanks from me.
Everything seems to be working well (!) ... I'm going to test things out a bit more before deleting the FireOS back up folder. I think I messed around with the xposed framework before... I'll definitely take another look.
Seriously, thank you.
Cheers,
Aaron
Click to expand...
Click to collapse
Great to hear! As an aside (not for me) don't forget to click the 'Thanks' button on XDA posts when appropriate, especially for newer members trying to build a reputation. Great working with you and gratified by the positive outcome.
Davey126 said:
Super! Final step is to install Nexus. Grab the Thor (nickname for 3rd gen HDX 7) installation zip from here. GAaps and SuperSU are built in so it's the only file you will need. Transfer that to a safe location on your device, preferably in a folder you create directly under sdcard. It is important this file (or it's successors) remain on your device at all times for emergency recovery. Putting it in the suggested location reduces the chance of accidental removal when wiping the (user) data partition. You can also place the folder directly under root (/) but be aware some file managers and tethers restrict access to high level directories.
Important: Unlike TWRP Safestrap v4.0.1 recovery has no ability to communicate with the outside world. Not by tether, wifi, bluetooth, adb, etc. It is fully isolated environment. If your rom becomes unstable (rare...but it does happen) your only recovery is using a previously created backup or a flashable rom image (as discussed above) resident on the device.
Boot into Safestrap recovery. Use the File Manager (under advanced) to confirm the existence/location of the Nexus rom zip. Return to the home screen and then access the wipe menu. Use the slider at the bottom to perform a factory reset which wipes the data, cache and dalvik partitions. Note this is different that a stock 'factory reset' which was discussed in a previous post. Also note it is impossible to wipe the system partition in Safestrap v4 even if selected in the advanced section. I won't get into the reasons; just know it isn't necessary for the upcoming operation.
Return to the home screen and select install. Navigate to the folder containing the Nexus rom, select it and then and then swipe the slider at the bottom to install (flash) the zip which will overwrite FireOS. When complete (assuming no errors) reboot your tablet and select continue to fire up Nexus. First boot make take some time as caches are populated. However, anything over 5 min indicates a problem. Once Nexus starts I assume you know where to go from there. You can safely enable WiFi, register with Google and perform all other requested initialization steps.
A few final footnotes:
- Nexus is pretty bare bones; not even a browser in included in the base build. Head over to the Play Store to grab what you need
- While Google's stock launcher is nice I suggest replacing it with Nova which offers a superior AOSP experience along with robust customization
- Xposed Framework and associated modules offers some excellent additions to this rom if you wish to customize further (advanced topic)
- Once you are confident Nexus is stable you can delete the huge FireOS backup created in an earlier step. Either via ESFE or from Safestrap
You may be aware Safestrap supports multi-boot through the use of user created slots. Unfortunately, they do not work with this device and can lead to unrecoverable bricks. You'll see various cautions in the Safestrap, Nexus and CM threads. Short version: do not create or use secondary slots.
Aaron - Feel free to post any questions/concerns/comments. Someone from the HDX community will likely respond within 24-48 hours. On a personal note it's been awhile since I did a long hand 'step-by-step' which is a refreshing change of pace from the usual bullets. I appreciate your patience as I dusted off various cob webs and hope you make the most out of your newly liberated device.
Click to expand...
Click to collapse
Hey Davey,
Thanks for reaching out to my thread and directing me to your conversation here. I followed all your steps and was able to successfully install the Nexus ROM and have everything running smoothly!!! Very happy! I had been hunting for a while to find a step by step instruction like yours!.
Thanks a lot!
P.S. Wasn't sure whether I should post this here or in my own thread but figured you were actively following this
One week on and I've been using my 'new' tablet quite a bit. It's been really solid with no crashes or problems whatsoever. Fantastic. I've now deleted the 4GB back up on the device, freeing up loads of space again.
I've had another good look at the Xposed framework, but frankly I'm so pleased to have the tablet running smoothly I think I'm just going to keep things nice and standard for now.
Davey, thanks (I found the button now!) again for sharing your knowledge, and giving your time and help. Very much appreciated.
Cheers,
Aaron
alhroot said:
One week on and I've been using my 'new' tablet quite a bit. It's been really solid with no crashes or problems whatsoever. Fantastic. I've now deleted the 4GB back up on the device, freeing up loads of space again.
I've had another good look at the Xposed framework, but frankly I'm so pleased to have the tablet running smoothly I think I'm just going to keep things nice and standard for now.
Davey, thanks (I found the button now!) again for sharing your knowledge, and giving your time and help. Very much appreciated.
Cheers,
Aaron
Click to expand...
Click to collapse
Hey Aaron, thanks for the follow-up. If you are happy with native rom/app capabilities there is no need to complicate matters. That said, if you every have a need for additional core functionality Fire Nexus, an AOSP clone, has proven to be an ideal platform for Xposed Framework and associated KitKat modules.
A tip of the hat to @ggow for his outstanding adaptation and ongoing support of this rom that is cornerstone of the post FireOS experience.
Enjoy your rejuvenated HDX!
Hi there. Thanks for this tutorial - I used it to install the Nexus ROM on my device. One weird thing; everything works, but I have NO sound? Any ideas why that might be?
skoop99 said:
Hi there. Thanks for this tutorial - I used it to install the Nexus ROM on my device. One weird thing; everything works, but I have NO sound? Any ideas why that might be?
Click to expand...
Click to collapse
Thoughts:
- a full power off/on (vs reboot) sometimes solves weird HW issues
- what version of FireOS was on the device prior to Nexus? 4.5.5.1 is recommended for the proper binaries
- might try a simple (dirty) reflash of Nexus in case something didn't 'take' on the first attempt (stranger things have happened)
Davey126 said:
Thoughts:
- a full power off/on (vs reboot) sometimes solves weird HW issues
- what version of FireOS was on the device prior to Nexus? 4.5.5.1 is recommended for the proper binaries
- might try a simple (dirty) reflash of Nexus in case something didn't 'take' on the first attempt (stranger things have happened)
Click to expand...
Click to collapse
Rebooted. I was on 4.5.5.1...
Will try a quick re-flash. ? Thanks!
Update, I have sound over headphones, but not over the speakers... :-S
skoop99 said:
Update, I have sound over headphones, but not over the speakers... :-S
Click to expand...
Click to collapse
Suggest you backup your current Nexus build from within Safestrap, then flash the Safestrap compatible version of cm11 to see if the problem persists. Yep, a bit of trial-and-error but not sure how else to diagnose. You could also try the Safestrap compatible build of FireOS (4.5.2; be sure it's the Safestrap build as a standard FireOs build will brick the device). Another option is to flash the Dolby enhancements which use a different suite of binaries. Post back if you need links to any of the above.