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.
EDIT: Problem is resolved. After I learn very much:
I made a video, cause there is no helpful video with Safestrap 4. Only with Version 3 and this way is wrong now!
I also write a blog about that helpful storry and links that will help other's.
Hello,
i started to root my Apollo 8.9/LTE with Tutorials from here and a translation in german. I live in germany.
http://www.android-hilfe.de/thema/r...r-kindle-hdx-8-9-apollo-fire-os-4-5-2.693547/
http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
Root Tool
Thats what i do
Rollback to OS 3.2.8 was great
Update to 4.5.2 was also ok
I rootet my Apollo, it works - i tested it
After that i renamed the DeviceSoftwareOTA.apk from Kindle in the priv-app
Now i copied all needed GAPPS files to the system Folder except the descripited
After that i restart my Apollo and now the Problems start
After restart
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Folder with Images
The Google Assistent start immediately after restart
I have to choise a Language but there was no german
Also i had no WIFI Connection, so the Assistent start the Option to connect with WIFI
This work, but at the wifi there is a X and in the Assistent i habe no Internet connection
I use my SIM Card to get a internet connection (This work) but the Assistent need a WIFI
Also i lost my root and get Denied when i try to copy/change with a older version befor April 15 or delete the GAPPS Files in the system Folders
I can start/install Apps with apk, at the apollo i only can use the settings. I have no menu or keys
Thats what i tried
I can use adb and install ES Datei Explorer or SuperSu
I used KingRoot, it dosn't work
I copied the mod Rollback to 3.2.8 bin File in the root folder, but Apollo dont use this file, maybe cause i renamed the OTA Systemfile
I made a reset of the Apollo, but the google Assistent is in the systemfiles and start even after a reset
My Apollo
Has Fire OS 4.5.2
The DeviceSoftwareOTA.apk is renamed
I only can Read NOT Write in the system folders
I can use adb and connect to the Apollo
I tried so much the last 2 days so i hope you got a hint for me.
Gatam77 said:
Hello,
i started to root my Apollo 8.9/LTE with Tutorials from here and a translation in german. I live in germany.
http://www.android-hilfe.de/thema/r...r-kindle-hdx-8-9-apollo-fire-os-4-5-2.693547/
http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
Root Tool
Thats what i do
Rollback to OS 3.2.8 was great
Update to 4.5.2 was also ok
I rootet my Apollo, it works - i tested it
After that i renamed the DeviceSoftwareOTA.apk from Kindle in the priv-app
Now i copied all needed GAPPS files to the system Folder except the descripited
After that i restart my Apollo and now the Problems start
After restart
Google Folder with Images
The Google Assistent start immediately after restart
I have to choise a Language but there was no german
Also i had no WIFI Connection, so the Assistent start the Option to connect with WIFI
This work, but at the wifi there is a X and in the Assistent i habe no Internet connection
I use my SIM Card to get a internet connection (This work) but the Assistent need a WIFI
Also i lost my root and get Denied when i try to copy/change with a older version befor April 15 or delete the GAPPS Files in the system Folders
I can start/install Apps with apk, at the apollo i only can use the settings. I have no menu or keys
Thats what i tried
I can use adb and install ES Datei Explorer or SuperSu
I used KingRoot, it dosn't work
I copied the mod Rollback to 3.2.8 bin File in the root folder, but Apollo dont use this file, maybe cause i renamed the OTA Systemfile
I made a reset of the Apollo, but the google Assistent is in the systemfiles and start even after a reset
My Apollo
Has Fire OS 4.5.2
The DeviceSoftwareOTA.apk is renamed
I only can Read NOT Write in the system folders
I can use adb and connect to the Apollo
I tried so much the last 2 days so i hope you got a hint for me.
Click to expand...
Click to collapse
Nice post; well documented.
You made some serious mistakes (come back to that later) and have a challenge ahead recovering your device. Based on others experiences there is some type of conflict between gapps and the stock launcher. That is probably why you are not seeing soft buttons, keyboard, etc. The only known solution is to temporarily use a different launcher to regain control of your device long enough to reroot. Problem is your device will revert back to the stock launcher on a number of different events including pressing the home key which frequently doubles as 'back' on FireOS. You then have to reinstall the non-stock launcher or find some way to make FireOS treat it as primary.
General overview:
- grab a copy of Nova or Apex (other launchers will probably work too)
- install via 'adb install' (research if unfamiliar)
- if all goes well you should regain temporary use of soft buttons and keyboard
- stay away from home key if possible as it will immediately restore the compromised stock launcher
- attempt to reroot your device with Kingroot. This should be safe given OTA is blocked. You many need to install Kingroot via adb. Once launched Kingroot needs an internet connection to do its magic; hopefully it will pick that up via your sim card
- you can also try rooting with CVE-2014-4322 exploit.
Once you are rooted there are several paths that can be pursued. Since you have a LTE device installing Safestrap and a different ROM probably isn't the best option. Nor is reinstalling gapps on FireOS as you will face an ongoing series of battles (conflicts) between Amazon and Google frameworks. You may need to roll back and upgrade again to fully resolve the launcher conflict.
Discussion for a different post. See if you can get rooted first.
Davey126 said:
You made some serious mistakes (come back to that later)
Click to expand...
Click to collapse
maybe you mean in a later post. Or do you mean, that i crash some Fire OS Framework with the GAPPS framework
Davey126 said:
Apex
Click to expand...
Click to collapse
I take Apex, i am familar with it.
Davey126 said:
You many need to install Kingroot via adb. Once launched Kingroot needs an internet connection to do its magic
Click to expand...
Click to collapse
i install kingroot 4.1 allready on the Apollo and also the software in my pc. Then i start the windows software but root didn't work. - Maybe because i dont have a internet connection on the Apollo??
Davey126 said:
you can also try rooting with CVE-2014-4322 exploit.
Click to expand...
Click to collapse
I used the cve20147911.apk from here (it work one time, bevor the GAPPS), but i try this one.
Davey126 said:
You may need to roll back and upgrade again to fully resolve the launcher conflict.
Click to expand...
Click to collapse
I couldn't rollback now. Is the reason that i dont have root?
Gatam77 said:
I couldn't rollback now. Is the reason that i dont have root?
Click to expand...
Click to collapse
You can't change FireOS versions because you previously blocked OTA by renaming DeviceSoftwareOTA.apk. This file is required to perform rollbacks/upgrades. You will need to obtain root permissions to restore the original filename.
Davey126 said:
You can't change FireOS versions because you previously blocked OTA by renaming DeviceSoftwareOTA.apk. This file is required to perform rollbacks/upgrades. You will need to obtain root permissions to restore the original filename.
Click to expand...
Click to collapse
OK. With this file the update Start. But befor the Update load from amazon Website this takes first a look on the SDCard. Wright?
Gatam77 said:
OK. With this file the update Start. But befor the Update load from amazon Website this takes first a look on the SDCard. Wright?
Click to expand...
Click to collapse
After enabling OTA put your device in airplane/flight mode to prevent updates from downloading. Make sure your device is stable (starts/functions normally) before attempting a rollback/update. I also advise allowing your device to upgrade to 4.5.5 (you will loose root) and then restart the rollback procedure from there.
Davey126 said:
Nice post; well documented.
You made some serious mistakes (come back to that later) and have a challenge ahead recovering your device. Based on others experiences there is some type of conflict between gapps and the stock launcher.
Click to expand...
Click to collapse
Thx for your words.
I installed a launcher and restart but also had no buttons. But a other way was it.
I GOT IT!!
I dont have permission on system folder with ES Datei Explorer, but now i use adb.
I found a post here how to change permission with adb
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Now i rename the file with mv MYNAMEOFOTA to DeviceSoftwareOTA.apk
After i used the gifroot Files But i got a message that it wouldnt work with this kernel.
So i dont know exactly which way was it.
But now to my serious mistakes. Can you tell me please what you mean? Cause I love this amazon hardware but I hate the amazon Fire OS and i love GMail, sheets, Maps, and other good apps from Google. So i need root.
All works bevor i push the GApps. So what is the better way. I know I have to read much more bevor i start again. Cause the Apollo is tricky.
I wait for a answer of you bevor i rollback to 3.2.8. I can wait.
Gatam77 said:
Thx for your words.
I GOT IT!!
I dont have permission on system folder with ES Datei Explorer, but now i use adb.
I found a post here how to change permission with adb
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Now i rename the file with mv MYNAMEOFOTA to DeviceSoftwareOTA.apk
After i used the gifroot Files But i got a message that it wouldnt work with this kernel.
So i dont know exactly which way was it.
But now to my serious mistakes. Can you tell me please what you mean? Cause I love this amazon hardware but I hate the amazon Fire OS and i love GMail, sheets, Maps, and other good apps from Google. So i need root.
All works bevor i push the GApps. So what is the better way. I know I have to read much more bevor i start again. Cause the Apollo is tricky.
I wait for a answer of you bevor i rollback to 3.2.8. I can wait.
Click to expand...
Click to collapse
Congratulations! Glad you were able to make some progress. Unfortunately, you are not out of trouble yet. Do not change permissions on any other files as FireOS is very sensitive and sometimes will not start if permissions are not as expected. Especially on 'system' files and folders.
Two concerns with the approach you took:
- using an outdated mod guide not published on XDA. Some of the techniques are old or no longer recommended
- attempting to install GApps on FireOS. Amazon and Google frameworks do not play nice together. While some have got it to work acceptably there are almost always problems, some quite serious.
A better approach is to use a twrp (recovery) emulator called Safestrap. Once installed you can install a limited selection of high quality ROMs that offer full access to the Google Play store. You may be familiar with the names: Nexus and CM11. They essentially turn your Kindle into a generic android tablet. You can even use native Amazon apps like Kindle reader.
The downside is LTE is not well supported by these roms. If you use your tablet off WiFi and need LTE then you have a tough decision to make:
1) Forgo LTE in favor of a rom with full Google Play access
2) Retain LTE and FireOS with limited access to Google services and apps
You don't have to make that decision now. First step is to rollback to 3.2.8, upgrade to 4.5.2, obtain root and block OTA. In a previous post I suggested upgrading to 4.5.5 first. I am stepping away from that suggestion to streamline the process. However, there is additional risk going from 4.5.2->3.2.8 because if anything goes wrong you could end up bricking your device. Going from 4.5.2->4.5.5 is less risky but adds another step.
There are many posts on XDA detailing the rollback/upgrade/root/blockOTA/Safestrap/rom process. Start here and spend some time reading. I did not pick this thread because it was the 'best'; just one I happen to remember contributing to in recent days. But it will lead you to other helpful posts that lead to even more posts ...
As always:
- ask questions if unsure; never assume or guess
- keep WiFi off (airplane/flight mode engaged) to prevent OTAs when upgrading or rolling back. Consequences are large: an OTA can (and likely will) permanently brick your device.
- make sure you fully understand the procedures, expected outcomes and recovery options if things go wrong
- only use files posted on XDA (links ok too)
- a fresh mind helps; take a break when tired. Your device will wait.
Good luck.
Davey126 said:
Two concerns with the approach you took:
- using an outdated mod guide not published on XDA. Some of the techniques are old or no longer recommended
- attempting to install GApps on FireOS. Amazon and Google frameworks do not play nice together.
The downside is LTE is not well supported by these roms. If you use your tablet off WiFi and need LTE then you have a tough decision to make:
1) Forgo LTE in favor of a rom with full Google Play access
2) Retain LTE and FireOS with limited access to Google services and apps
As always:
- ask questions if unsure; never assume or guess
- a fresh mind helps; take a break when tired. Your device will wait.
Good luck.
Click to expand...
Click to collapse
The again a lot.
I need my Mobile Internet. Not really LTE but at least 3G! But LTE get better here in Germany so it would be nice.
I like CM. I already flashed my Samsung S3, my wife S3 Mini, and my 2 Amazon's Tate.
That's why I bought the Apollo and hope after 1 year or so there will be a custom ROM with LTE working. So if someone interested I will flash a Custom Rom, life a time without Mobile Internet and help the developer with sending log files, or other needed things.
No I started reading! But I will post again here that other can read and learn from my mistakes.
Gatam77 said:
The again a lot.
I need my Mobile Internet. Not really LTE but at least 3G! But LTE get better here in Germany so it would be nice.
I like CM. I already flashed my Samsung S3, my wife S3 Mini, and my 2 Amazon's Tate.
That's why I bought the Apollo and hope after 1 year or so there will be a custom ROM with LTE working. So if someone interested I will flash a Custom Rom, life a time without Mobile Internet and help the developer with sending log files, or other needed things.
No I started reading! But I will post again here that other can read and learn from my mistakes.
Click to expand...
Click to collapse
FYI - you can find the Safestrap compatible CM11 rom thread here. As I recall some aspects of LTE/3G work ok. Skim through the posts for more detail. Might be a non-issue for your needs.
Davey126 said:
You don't have to make that decision now. First step is to rollback to 3.2.8, upgrade to 4.5.2, obtain root and block OTA. In a previous post I suggested upgrading to 4.5.5 first. I am stepping away from that suggestion to streamline the process. However, there is additional risk going from 4.5.2->3.2.8 because if anything goes wrong you could end up bricking your device. Going from 4.5.2->4.5.5 is less risky but adds another step.
Click to expand...
Click to collapse
After i was short befor to brick my Apollo, maybe I would first Going from 4.5.2 > 4.5.5 and then 3.2.8 > 4.5.2.
But i dont read a hint with a link to 4.5.5. Can I download ist from here Davey?
Also i take a look in my router and he block some IPs when I used Kingroot on my PC yesterday.
14.17.41.155
202.77.59.49
163.177.71.157
120.198.203.149
103.7.29.30
They come from Hongkong and Bejiing. Is it possible that that was the reason Kingroot couldn't root my Apollo?
Gatam77 said:
After i was short befor to brick my Apollo, maybe I would first Going from 4.5.2 > 4.5.5 and then 3.2.8 > 4.5.2.
But i dont read a hint with a link to 4.5.5. Can I download ist from here Davey?
Also i take a look in my router and he block some IPs when I used Kingroot on my PC yesterday.
14.17.41.155
202.77.59.49
163.177.71.157
120.198.203.149
103.7.29.30
They come from Hongkong and Bejiing. Is it possible that that was the reason Kingroot couldn't root my Apollo?
Click to expand...
Click to collapse
I can't speak to what IPs Kingroot uses. There have been various reports of it being slow or temporarily not working. Perhaps due to network congestion. Usually clears up after a few hours.
If you have restored DeviceSoftwareOTA.apk you can simply enable WiFi (disable airplane/flight mode) and allow the device to receive an OTA and self-update to 4.5.5. This is actually a good test OTA functionality is working which is also required for manual rollbacks/upgrades.
There is another option that does not involve rollbacks/upgrades: If you can obtain root you can then attempt to install Safestrap v4 followed by CM11 or Nexus v4 (you can also 'repair' FireOS using this method). Both Kingroot and Safestrap require interactive access. You don't need to type anything (so keyboard doesn't need to display), just tap an on-screen button or two. You would need to install apks via adb and then have enough control over your device to launch the app. Not easy or intuitive.
I will caution there is risk with either path (upgrading FireOS or installing Safestrap on a dysfunctional device). You have to weight the risks and take the course the feels most comfortable. There are no guarantees.
Reminder: do not do a 'factory reset' from the native recovery menu unless recommended by an experienced contributor, especially after rooting or installing Safestrap.
Now all is ok again. I am so joyful.
First Download Safestrap from here
Downloaded and Follow the instructions here
Now i can start with a new and clean Android on a good Amazon Hardware
Installed Safestrap on my damaged Fire OS 4.5.2
Than install a recovery in the Safestrap APP
After that i made a slot with 1200 System/1500 Data/1000 Cache
Active the slot
go into Wipe Menu and Swipe to perform a factory reset
Go in the Install Menue and install CM11, GAPPS and SuperSu
Now i started in CM11
Again thx to Davey126.
My stock ROM is still the damaged where I mixed amazaon and google framework. What can i do?
Active the Stock slot, start into my damaged Fire OS
Push with adb a Fire OS 4.5.5 to the sdcard
Or make a OTA over the WLAN from amazon?
Or (in the video says: NEVER touch the stock at Safestrap) Install a Fire OS bin in Safestrap to witch slot?
Gatam77 said:
Now all is ok again. I am so joyful.
First Download Safestrap from here
Downloaded and Follow the instructions here
Now i can start with a new and clean Android on a good Amazon Hardware
Installed Safestrap on my damaged Fire OS 4.5.2
Than install a recovery in the Safestrap APP
After that i made a slot with 1200 System/1500 Data/1000 Cache
Active the slot
go into Wipe Menu and Swipe to perform a factory reset
Go in the Install Menue and install CM11, GAPPS and SuperSu
Now i started in CM11
Again thx to Davey126.
My stock ROM is still the damaged where I mixed amazaon and google framework. What can i do?
Active the Stock slot, start into my damaged Fire OS
Push with adb a Fire OS 4.5.5 to the sdcard
Or make a OTA over the WLAN from amazon?
Or (in the video says: NEVER touch the stock at Safestrap) Install a Fire OS bin in Safestrap to witch slot?
Click to expand...
Click to collapse
Excellent - glad to hear the progress!! However, there are some important changes needed that will greatly improve your CM11 experience (battery life, performance, stability). Some of this contradicts information in the video and recommendations from other versions of Safestrap.
The use of secondary slots is not recommended in Safestrap v4:
WiFi only works with CM11; Nexus v4 and Stock FireOS will fail to make a connection
Only 2 of 4 CPU cores are utilized resulting in poor performance under load
CPU runs at maximum speed at all times (no throttling) resulting in high battery use when idle
GPU does not throttle
Device never enters 'deep sleep'; radios remain active at all times
Backups can not be migrated between slots; flashing a secondary slot backup to the stock slot will brick device
Slot storage must be allocated in advance and can not be adjusted (must delete/recreate/reflash rom)
Recommended path:
Delete secondary slot (this will destroy your CM11 installation)
Flash CM11, GApps, SuperSu in stocki slot; this will overwrite FireOS in stock slot
This means your device will be running CM11 with no access to FireOS. However, if needed you can replace CM11 with FireOS 4.5.2 from this thread. Note the images are customized for Safestrap; flashing a unmodified stock image will brick your device.
Miscellaneous:
NEVER perform a 'factory reset' from the native recovery menu; your device will brick
Make a backup of the stock slot from within Safestrap (it will be large); move to a host PC for safe keeping
Always keep a flashable copy of CM11 image on the device (in the root of sdcard) for emergency recovery. Safestrap v4 can not communicate via wifi, bluetooth or tether. If CM11 fails to boot your only option is to reflash an OS (CM11, Nexus or FireOS) from within Safestrap recovery. If a Safestrap compatible/flashable image is not already on the device you can not recover from this type of failure.
Safestrap may appear to be a full blown recovery but it is actually a TWRP emulator that runs within the system partition and has dependencies on other Amazon components (bootloader, native recovery, etc) that remain on your device from the previous FireOS 4.5.2 installation. Be careful with advanced tools that run at a low level. It is possible to 'damage' your device to an extent that it can not be recovered. Ask first if uncertain.
questioning asking
This is so interesting. So sorry for my allways following questions. You said I should ask, but maybe also other can have a answer for me. This also cost your time.
So if you can't answer its ok. Or if there are only some hint words that will be a help for me to find out more. Whatever.
I am more than thankfull for that help to find out more about Android.
Davey126 said:
However, there are some important changes needed that will greatly improve your CM11 experience (battery life, performance, stability). Some of this contradicts information in the video and recommendations from other versions of Safestrap.
Click to expand...
Click to collapse
Ok, a next thing that i can search for.
I see some of my Apps close very often. Special Play Store
Davey126 said:
Delete secondary slot (this will destroy your CM11 installation)
Flash CM11, GApps, SuperSu in stocki slot; this will overwrite FireOS in stock slot
Click to expand...
Click to collapse
With secondary slot you mean the ROM Slot 1, cause the Stock will be the first slot maybe?
I don't will go back to the Fire OS cause i have a Fire TV Stick and a Raspberry for that. If i still think so in some months i also can flash the Stock Rom with a CM Image? But its not necessary cause i have my CM11 or maybe in the future CM13 in the ROM Slot 1. Or are they more reasons for that step?
Davey126 said:
NEVER perform a 'factory reset' from the native recovery menu; your device will brick
Click to expand...
Click to collapse
Whats do you mean special with "native recovery"?
That i start with the StockRom into my FireOS and after that i make a factory reset?
Davey126 said:
[*] Always keep a flashable copy of CM11 image on the device (in the root of sdcard) for emergency recovery. Safestrap v4 can not communicate via wifi, bluetooth or tether. If CM11 fails to boot your only option is to reflash an OS (CM11, Nexus or FireOS) from within Safestrap recovery. If a Safestrap compatible/flashable image is not already on the device you can not recover from this type of failure.
[/LIST]
Click to expand...
Click to collapse
I will do this! But...
I dont know, at this time, so much from safestrap. But i take look in it, and i can use ADB Sideload, Mount a USB Storage. Maybe also to reboot into the Download.
Is a push from adb or a Backup on a USB not also a way to restore a damaged Custom ROM.
Like
Start into Safestrap
Wipe my Slot with the CM11 or delete ist and create it again
Push with adb a new file of CM11, GApps, SuperSu into my data permission
And after that flash it to the Data Partition
Davey126 said:
[*] Safestrap may appear to be a full blown recovery but it is actually a TWRP emulator that runs within the system partition and has dependencies on other Amazon components (bootloader, native recovery, etc) that remain on your device from the previous FireOS 4.5.2 installation. Be careful with advanced tools that run at a low level. It is possible to 'damage' your device to an extent that it can not be recovered. Ask first if uncertain.
[/LIST]
Click to expand...
Click to collapse
How i can find out what Low Level tools are?
I think a recovery like TWRP is one.
I also use Tasker or BusyBox. They can make also deep things on my system. Also Low Level?
When ends the Low Level and start the Deep System?
Gatam77 said:
With secondary slot you mean the ROM Slot 1, cause the Stock will be the first slot maybe?
Click to expand...
Click to collapse
Yes - delete all ROM slots (1-n) that you created. Bottom line: you only want to use the Stock slot.
Gatam77 said:
I don't will go back to the Fire OS cause i have a Fire TV Stick and a Raspberry for that. If i still think so in some months i also can flash the Stock Rom with a CM Image? But its not necessary cause i have my CM11 or maybe in the future CM13 in the ROM Slot 1.
Click to expand...
Click to collapse
You do not want to maintain multiple slots (ROM images) in Safestrap v4. When you switch ROMs you overwrite the existing ROM in the Stock slot. You can overwrite CMxx with FireOS. At present CM12 and CM13 are not compatible with Safestrap v4. Do not attempt to flash any ROM image other than those specifically listed as "Safestrap Compatible".
Gatam77 said:
Whats do you mean special with "native recovery"?
Click to expand...
Click to collapse
"Native recovery" is the one supplied by Amazon accessible via <power> + <vol-up> from a cold start. NEVER use the 'factory reset' function from this menu when Safestrap v4 is installed; your device will brick.
Gatam77 said:
I dont know, at this time, so much from safestrap. But i take look in it, and i can use ADB Sideload, Mount a USB Storage. Maybe also to reboot into the Download. Is a push from adb or a Backup on a USB not also a way to restore a damaged Custom ROM.
Click to expand...
Click to collapse
None of these features work with Safestrap. Think of Safestrap as a virtual machine with ROMs running inside (technically inaccurate but conceptually convenient). You can only make full use ADB after portions of the ROM are up and running. If the ROM is damaged/unbootable you must do all repairs from within Safestrap. At present Safestrap v4 can not communicate with the outside world; all repair tools/images must be 'on board' (preloaded).
Gatam77 said:
Start into Safestrap
Wipe my Slot with the CM11 or delete ist and create it again
Push with adb a new file of CM11, GApps, SuperSu into my data permission
And after that flash it to the Data Partition
Click to expand...
Click to collapse
Probably repetitive but you do not want to recreate ROM Slot 1. Delete it and then flash CM11 (or Nexus v4 or FireOS) to the Stock slot.
Gatam77 said:
How i can find out what Low Level tools are?
I think a recovery like TWRP is one.
I also use Tasker or BusyBox. They can make also deep things on my system. Also Low Level?
Click to expand...
Click to collapse
- You can not use 'native' TWRP on your system as the bootloader is locked and can not be unlocked. Safestrap emulates TWRP.
- Tasker and BusyBox are fine
- Be careful with Xposed modules or other 'tweaks' that might cause your device to become unbootable.
Bottom line: enjoy CM11 and the apps that can be installed from the Play Store. Resist the temptation to customize further. If your device freezes or becomes unbootable you may not be able to recover.
Davey126 said:
Yes - delete all ROM slots (1-n) that you created. Bottom line: you only want to use the Stock slot.
Click to expand...
Click to collapse
Short Post
Oh my god. Again I trust a old Video. More later
So i install again.
First i make a backup (over WLAN) from my Stock Rom. I didn't get connection over USB at my PC neither connect a USB Stick to the Micro USB Slot. That's may what you mean that Sfestrap works like a virtual mashine.
So i CHECK if all files are at my root folder in the stock
After that i Wipe the Stock Rom
After that Flash all needed files and install like the last time but this time into the Stock Rom
Gatam77 said:
Short Post
Oh my god. Again I trust a old Video. More later
So i install again.
First i make a backup (over WLAN) from my Stock Rom. I didn't get connection over USB at my PC neither connect a USB Stick to the Micro USB Slot. That's may what you mean that Sfestrap works like a virtual mashine.
So i CHECK if all files are at my root folder in the stock
After that i Wipe the Stock Rom
After that Flash all needed files and install like the last time but this time into the Stock Rom
Click to expand...
Click to collapse
Good! Please confirm that you are now running CM11 in the Stock slot.
Assuming 'yes' you can (and should) remove all other slots if still present. Benefits:
- recover 3-4 Gb of permanent storage on your device and return it to the stock slot
- avoid potential confusion while in Safestrap recovery which could possibly lead to a bricked device
Once everything is stable boot into CM11 and move the large backup files to a host via tether (fastest), WiFi or Bluetooth. You do not need to keep backups on your device for recovery purposes; only the smaller ROM image.
You can not attach a flash/thumb drive or any other USB device (including keyboards/mice) to the micro-USB port as HDX devices lack OTG support at the hardware level. An unfortunate design choice by Amazon and can not be fixed via software or special cables.
Keep in mind the HDX is a sensitive device. After flashing a ROM there rarely a need to return to the Safestrap recovery environment. Exceptions:
- flash a newer version of ROM (release release notes carefully)
- make periodic backups of your existing system and data partitions
Davey126 said:
Good! Please confirm that you are now running CM11 in the Stock slot.
Click to expand...
Click to collapse
I will do. At the moment it is still in Slot 1 and i recharge battery to 100%.
Maybe tomorrow . Because there is no video with this, i try to make a movie while making all this steps.
Assuming 'yes' you can (and should) remove all other slots if still present. Benefits:
- recover 3-4 Gb of permanent storage on your device and return it to the stock slot
Click to expand...
Click to collapse
So i Flash my CM11 to the Stock Rom. And AFTER That i remove the other Slots.
After that I can recover storage back to the Stock ROM?
You do not need to keep backups on your device for recovery purposes; only the smaller ROM image.
Click to expand...
Click to collapse
After all works with the Custom Rom on the Stock Rom, i leave the ZIP file on my device after the flash. All other like GAPPS i also can thether later, if i need this again.
Gatam77 said:
So i Flash my CM11 to the Stock Rom. And AFTER That i remove the other Slots.
After that I can recover storage back to the Stock ROM?
Click to expand...
Click to collapse
Correct. Although the goal is to delete all secondary (non-stock) slots there is no benefit to removing the slot that is currently hosting CM11 until you have confirmed the reflash of CM11 to the stock slot. This leaves you with a working ROM should something go wrong.
An 'idle' secondary slot does not present a problem just being there. However, it consumes considerable space and increases the possibility of making a fatal mistake while working in Safestrap recovery. Ultimately the decision is yours whether to keep or discard secondary slots. However, you want your primary slot to be stock. Hope this makes sense.
Gatam77 said:
After all works with the Custom Rom on the Stock Rom, i leave the ZIP file on my device after the flash. All other like GAPPS i also can thether later, if i need this again.
Click to expand...
Click to collapse
Correct.
I have a 4th Gen Kindle HDX which is rooted (Kingroot). I tried install GAPP (minimal) the other day. I overwrote some files (stupid I know) and rebooted the system. Now there is no menubar or launcher. I can't swipe in from the sides or tap to reveal a home/back overlay. I also can't update manual or OTA. When the system boots it boots into the settings window (thankfully), so I'm able to change settings (ADB enabled, wifi) and importantly use the special offers to launch the browser from which I've installed es explorer. I really want to get my Kindle back ideally to the latest Kindle OS WITH functional Google Store. Can anyone help? ideas suggestions.
Thanks
bnbliss said:
I have a 4th Gen Kindle HDX which is rooted (Kingroot). I tried install GAPP (minimal) the other day. I overwrote some files (stupid I know) and rebooted the system. Now there is no menubar or launcher. I can't swipe in from the sides or tap to reveal a home/back overlay. I also can't update manual or OTA. When the system boots it boots into the settings window (thankfully), so I'm able to change settings (ADB enabled, wifi) and importantly use the special offers to launch the browser from which I've installed es explorer. I really want to get my Kindle back ideally to the latest Kindle OS WITH functional Google Store. Can anyone help? ideas suggestions.
Thanks
Click to expand...
Click to collapse
Recovery approach is to adb install an alternative launcher (Apex, Nova) that will allow you to regain some control over your device - hopefully enough to restore the damaged files. The solution is not a panacea; if you touch the 'home' button FireOS will revert to the damaged launcher and you will have to repeat the cycle all over. A present there is no way to reload FireOS on 4th gen device so your options are limited. A factory reset will not restore launcher functionality. If you deleted files recovery will be almost impossible.
If the device remains under warranty contact Amazon for a one-time courtesy exchange.
I was able to install an alternate launcher and as you mentioned there is limited functionality. I wish there were a way to be able to force the device to upgrade to the latest FireOS or to reinstall the default framework as I'm pretty sure that's what got messed up during my attempted GAPP upgrade.
Describe step-by-step your steps. Which files exactly you replaced/changed except gapps.
bnbliss said:
I was able to install an alternate launcher and as you mentioned there is limited functionality. I wish there were a way to be able to force the device to upgrade to the latest FireOS or to reinstall the default framework as I'm pretty sure that's what got messed up during my attempted GAPP upgrade
Click to expand...
Click to collapse
Might consider contacting Amazon to see if they will manually push FireOS v5. Would be risky as an unstable device might not take the OTA well. You would likely 'own' the problem if out of warranty.
At some point a stock image > 4.5.5.1 should become available. You might be able to use that to force a more controlled upgrade. A Safestrap build for 4th gen devices seems unlikely at this point which is the other method used for reinstalling FireOS.
For future reference GApps and FireOS v4 is like Russian roulette. A few can keep the cylinder from rotating but most suffer some type of wound from the experience. Just a matter of time.
The only files changed were GAPP files.
bnbliss said:
The only files changed were GAPP files.
Click to expand...
Click to collapse
The only files changed were GAPP files.
ONYXis said:
Describe step-by-step your steps. Which files exactly you replaced/changed except gapps.
Click to expand...
Click to collapse
Thanks guys. An interesting thing happened when put a launch chooser on the device. Once I chose Nova launcher and then because I had nothing to lose chose Kindle launcher I suddenly had a functional Kindle. I rebooted the Kindle and everything is back to normal with the exception being I still can't update to the latest OS which I'd like to do. Thanks again everyone I appreciate the knowledge shared on these boards.
bnbliss said:
Thanks guys. An interesting thing happened when put a launch chooser on the device. Once I chose Nova launcher and then because I had nothing to lose chose Kindle launcher I suddenly had a functional Kindle. I rebooted the Kindle and everything is back to normal with the exception being I still can't update to the latest OS which I'd like to do. Thanks again everyone I appreciate the knowledge shared on these boards.
Click to expand...
Click to collapse
Great! Nice when the HDX gods are in a good mood
Did you make any effort to block OTA? Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk. If not there or renamed (perhaps with a .bak extension) that is your problem.
Caution: do NOT touch DevicesoftwareOTA Contacts.apk. Alter/rename that file and you'll own a brick
90% there
Davey126 said:
Great! Nice when the HDX gods are in a good mood
Did you make any effort to block OTA? Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk. If not there or renamed (perhaps with a .bak extension) that is your problem.
Caution: do NOT touch DevicesoftwareOTA Contacts.apk. Alter/rename that file and you'll own a brick
Click to expand...
Click to collapse
Thanks Davey for all your help. I had renamed the DeviceSoftwareOTA to prevent OTA updates. I renamed it back, restarted and the 4.5.5.1 download downloads but fails on installation. I've manually downloaded and put it on the Kindle. It's recognized but fails to install also. I then tried devices --> reset to Factory Defaults. The Kindle reboots into Fastboot mode. Strange. I'll dig around and see what I can find. I can't even tell you how happy I am that the HDX Gods have smiled on me, perhaps thanks to your intercession. :laugh:
-bnbliss
bnbliss said:
... I had renamed the DeviceSoftwareOTA to prevent OTA updates. I renamed it back, restarted and the 4.5.5.1 download downloads but fails on installation. I've manually downloaded and put it on the Kindle. It's recognized but fails to install also. I then tried devices --> reset to Factory Defaults. The Kindle reboots into Fastboot mode. Strange. I'll dig around and see what I can find.
Click to expand...
Click to collapse
Thoughts:
- there may be an inconsistency in the system partition that is hampering installation
- typically a factory reset from the native recovery menu (<power>+<vol-up> from cold start) allows balky images to progress
- however, you installed GAaps on FireOS v4 which may be a wildcard
- rebooting to fastboot is weird ...
- verifying you executed the 'Factory Reset' from the native Kindle Recovery menu, correct?
- also assume there was no attempt to install Safestrap or any other 'recovery' tool
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.
UPDATE: So since I am able to navigate through the settings, I did some digging around, and it seems that the Amazon Launcher isn't running (that maybe why the nav bar was missing). Is there any way I could try to open it through ADB? I tried installing another Launcher, it's installed however there's no way I can open it.
So my Kindle Fire HDX was performing not too well so I then did a factory reset, after it rebooted it would have the language selection screen, after I select English it then takes !e to the screen where I need connect to wifi. After I connected to my network, I can't go any further, I can only navigate through the settings app instead of completing the setup. The home, back, and search buttons are missing. Is there anything I can do to fix it? Any help is appreciated!
bigboolean said:
UPDATE: So since I am able to navigate through the settings, I did some digging around, and it seems that the Amazon Launcher isn't running (that maybe why the nav bar was missing). Is there any way I could try to open it through ADB? I tried installing another Launcher, it's installed however there's no way I can open it.
So my Kindle Fire HDX was performing not too well so I then did a factory reset, after it rebooted it would have the language selection screen, after I select English it then takes !e to the screen where I need connect to wifi. After I connected to my network, I can't go any further, I can only navigate through the settings app instead of completing the setup. The home, back, and search buttons are missing. Is there anything I can do to fix it? Any help is appreciated!
Click to expand...
Click to collapse
You are correct. Unfortunately, it's a tough nut to crack as the home button is mapped exclusively to the crippled stock launcher. You can sideload an alternative launcher but once you hit 'home' the loop usually resumes. Try using 'adb install' to sideload Nova. It will temporarly become the default launcher. Attempt to set the language and perform other initilization tasks while staying away form the 'home' button. You'll probably have to repeat the process several times as home is often the only way to exit various settings paths. Post back your findings. Worse case you may have to consider installing Safestrap and a custom rom to regain control of your device.
Which device (7" or 8.9") and version of FireOS?
So I was able to go to the settings and click Applications - Special Offers - and then click on the orange internet link, and then download and install king root, safestrap v4, and then download, and flash the Fire Nexus ROM.
bigboolean said:
So I was able to go to the settings and click Applications - Special Offers - and then click on the orange internet link, and then download and install king root, safestrap v4, and then download, and flash the Fire Nexus ROM.
Click to expand...
Click to collapse
Excellent! Clearly a better place to be than struggling with FireOS's wonky launcher and permission issues.
Just in case you didn't note a few Safestrap v4 best practices:
- never perform a 'factory reset' from the stock recovery menu with SS installed; device will brick with little chance for recovery
- roms should only be installed (flashed) to the stock slot replacing the previous contents; secondary slots do not work well with Safestrap v4
- important: always retain a flashable rom (Nexus zip) in an accessible folder on the device for emergency recovery as there is no way to grab this file or any other if you can only boot into Safestrap (no native adb support)
Davey126 said:
Excellent! Clearly a better place to be than struggling with FireOS's wonky launcher and permission issues.
Just in case you didn't note a few Safestrap v4 best practices:
- never perform a 'factory reset' from the stock recovery menu with SS installed; device will brick with little chance for recovery
- roms should only be installed (flashed) to the stock slot replacing the previous contents; secondary slots do not work well with Safestrap v4
- important: always retain a flashable rom (Nexus zip) in an accessible folder on the device for emergency recovery as there is no way to grab this file or any other if you can only boot into Safestrap (no native adb support)
Click to expand...
Click to collapse
Oh okay, I'll need to put the zip back on my tablet, just for emergencies like you said. I actually don't plan on installing any other roms at the moment. One thing that I'll miss is that I can't buy anymore kindle exclusive games (good thing I backed up the apks for ones I already bought with APK Extractor).
bigboolean said:
Oh okay, I'll need to put the zip back on my tablet, just for emergencies like you said. I actually don't plan on installing any other roms at the moment. One thing that I'll miss is that I can't buy anymore kindle exclusive games (good thing I backed up the apks for ones I already bought with APK Extractor).
Click to expand...
Click to collapse
Might still be able to via official Amazon Underground app (Google for proper link).
Davey126 said:
Might still be able to via official Amazon Underground app (Google for proper link).
Click to expand...
Click to collapse
Yeah I already checked, I'm glad I extracted those apks the day I bought those games. Oh yeah if you still have a FireOS tablet I recommend you should buy Til Mornings Light, Tales From Deep Space, and Lili: Path of Geos.