Related
How do I un-trust a CA on the Android? I'm not sure if this is an OS level issue (as in OS X) or browser lever (as with Windows).
Since *.android.com has been compromised in the digiNotar debacle, I would like to remove them as a trusted CA.
As a related question, how can I also purge the DNS cache?
Se my sig for device and ROM versions.
Walt
Android keeps its certs in
/system/etc/security/cacerts.bks
Preventing modification on non rooted devices (gingerbread is a bit better but still not full access..)
A program might have its own certs (such as firefox on osx) but I don't think I've seen such in the wild.
You may find something useful in this post related to one of the roms I distribute (and links contained in it):
http://forum.xda-developers.com/showpost.php?p=17303669&postcount=2832
(Don't worry as most security updates go its being [mostly] ignored.......)
Thanks, ezterry.
The program ran OK on CM7 - it says it deleted the certificate; I assume it really did it
Walt
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Well said buddy.
I consider myself a fairly advanced android and linux user and I've customised the heck out of my n4 but I'm leaving my hdx as it is for now.
Good advise there.
Now if only mayday had a pro feature to help with rooting... haha
Can we set jcase up with a webcam? Lol
Sent from my Nexus 4 using Tapatalk
GSLEON3 said:
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
Click to expand...
Click to collapse
Safestrap! Safestrap!
http://forum.xda-developers.com/showthread.php?t=2556677
Firstly, this was posted before SafeStrap. Plus, I highly doubt even Hashcode would recommend new users mess with SafeStrap right now. I'm by no means a master developer, but I've been around a long time & I've participated in some pretty cool low level hacking with some of the old timers & I'll be the first to say that there is some funky stuff going on in the HDX. Amazon has not exactly gone out of their way to make modding safe or easy. Plus there's not a whole lot out there yet that requires an custom recovery. It may be fine for you or I, but it can open a whole other host of issues if used improperly.
Sent from my KFJWA using XDA Premium HD app
Hey there I am new to this forums! Got a kindle yesterday (as a gift) and moved straight to xda to see what's cooking unfortunately I was a bit disappointed because there is no "cooking" at all. I hope this has to do with the fact that it's a new device and nobody has tried to make some roms for it yet... Nevertheless I am quite happy with it, although this fire os is a pretty pain in the eyes. Thank God I have managed to get the YouTube app sync with my Google account, plus some other gapps like drive. Well that's it for the moment, I just didn't want to make a new thread so I posted in here. So what do you think, will there be some good roms for this device? And/or maybe we could use those for the kindle fire hd?
Sent from beneath my cloak of magic
Thanks for the info I'm super new at this but was thinking buying one of these. But now that I am acquainted with Flashing ROMs and stuff it's sort of a deal breaker if it's not being done. If I can't modify it, whats the point?
HDX rooting?
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
Patience good people. Each day a few qualified devs get a little closer ... all on their own free time. A crack might be right around the corner.
Well, it's almost June and development for the Kindle tablets seem to still be very slow, what's the story?
blackfox003 said:
I bought a Fire HDX 7" to replace a Nook HD+ for better HW. I thought I read you could root it or at least get the google play store on it, but it appears that is not the case. I guess I misunderstood what I read. Really disappointed now.
Any new news on rooting these things?
Click to expand...
Click to collapse
You can get root and the Google Play Store on an older firmware, just not any of the newest couple. Yet (I hope).
Good to go: I was able to use hdx-toolkit with my router blocking
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
sabasc said:
Hey everyone.
In case this helps, I was able to ensure that my kindle didn't update by blocking all Internet access at my firewall (Verizon FiOS router) for the device. I looked up its MAC address under "Wireless" -> "Wi-Fi" and configured a rule to block all access.
I confirmed my device version via Apps -> Settings -> System Updates -> Current Version: 13.3.1.0 (factory fresh!)
Then, using my PC I ran the hdx-toolkit 0.94 and after resolving an initial snag (the toolkit couldn't access my device) I was able to do steps 1 (driver), 5 (check if rooted which also checks connectivity), 8 (towelroot), 2 (SuperSU), 5 (confirm root), 4 (block OTA) from the toolkit menu.
Note, the toolkit doesn't want to run from a network share. I copied it down onto my computer's local hard disk first.
My specific issue preventing the ADB setup was I didn't realize the Microsoft driver (to make the device show up as a USB phone device) was blocking the ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install without error. Symptom of the driver conflict was the end of the installer sequence said "driver not installed correctly or need to reboot".
I am using Windows 8 on a Dell desktop
Click to expand...
Click to collapse
I'm sorry I missed this. Great advise though.
A default Microsoft driver was blocking the Amazon ADB driver from coming up. After uninstalling the Microsoft driver (under device manager - Portable devices for the device "kindle") and installing the device driver for Android Composite ADB Interface, I was able to get the ADB driver to install. --Win8/Win8.1
Click to expand...
Click to collapse
The toolkit needs to be run locally because well the adb connection won't go through your share to your computer.
GSLEON3 said:
Guy's the HDX is a fairly new device, the complete line has not even begun shipping yet & development is in it's infancy.
Currently, you can root your device, but it is HIGHLY recommended that you WAIT.
Currently, there are NO, ZERO, NONE, utilities or consistent fixes for soft bricked devices. This is not good, as currently there are several things that can soft brick this device.
In no circumstances should you do any of the following:
Remove apps or any files from the system folder or any sub-directory.
Restore previous veersions of Kindle apps from a Fire HD.
Make any modifications to any of the build.prop settings, or add any lines to the build.prop
Working but not advised at this time:
Adding any files or apks to the system partition or any sub-directory
There are numerous instances of modifications causing bootloops, soft bricks & KILLING ADB access. To my knowledge, I am the only person that has successfully recovered ADB access & for all the money in the world, I could not tell you how.
If you are not extremely proficient with reverse engineering software, or you don't know all the relevant ADB commands because you have been hacking devices for years, I STRONGLY suggest you wait to even root until further development progress has been made.
If you ignore this warning, you are likely going to be on your own in trying fix it, or you may be waiting months for a consistent fix to be found.
If you like taking risk & tinkering & you like to burn hundred dollar bills just for the pretty orange flame, well, by all means, go right ahead. Just realize right now, there may not ever be a recovery for your particular dilemma & in all likelihood by ignoring this warning, you've already made your warranty null & void.
Click to expand...
Click to collapse
Is this still the case? Just wondering if this thread needs to be updated because some of what's written here seem to contradict what I've read people are doing with their hdx.
my 8.9HD ver. 8.5.1
Is my kindle an HDX?
ant17 said:
Is my kindle an HDX?
Click to expand...
Click to collapse
No, you can find anything related to your kindle here
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
hfpop said:
Hello,
Just to make sure I understood all the info published around:
A Kindle Fire HDX running FireOS 4.5.2 cannot be brought to a state where it can be jailbroken and and alternate ROM installed.
Even the downgrade performed by Amazon operators is to a version too high to allow jailbreaking and installing other ROM.
Am I correct with this assessment?
Click to expand...
Click to collapse
to an extent yes,most custom roms cannot be installed but if you rolled back you can still root and instal the hdx nexus 2.0.2 rom which is pretty much most of what the device needs
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
hfpop said:
@Davengerr: I understand that I can rollback to 3.2.8 and need at most 3.2.6 to install nexus 2.0.2. No?
Click to expand...
Click to collapse
i have it on 3.2.7 on my device and this here lists what you can do with a 3.2.8
http://forum.xda-developers.com/kin...o-13-3-2-7-t2993089/post58150015#post58150015
@Davengerr: Thank you. All worked out greatly.
I have been doing a lot of indepth reading regarding the whole process of loading Lollipop on a Kindle Fire HDX 7.
I thought I had the process understood but have realised I might have a problem. It seems that there is a loop where you need to ROOT the Kindle in order to rollback the ROM, but all the rooting methods seem to rely on having a 13.3.2 or earlier ROM in order to ROOT it.
It seems that the vulnerabilities which allowed the zergRush root method have been fixed, as have the TowelRoot vulnerabilities. These are the only two methods I have found so far after extensive searching.
I am not certain which ROM my Kindle will have since I have ordered it as present for my wife off of Ebay. It maybe that its got an old ROM and all will be OK, but I would rather not waste my time and possibly brick the Kindle by trying outdated fixes.
I have loaded Android-SDK and Android-Tools onto my Opensuse system, but I understand that I can only "adb push" a rollback ROM if I have already ROOTed the Kindle.
Any guidance to avoid a horrible mistake would be much appreciated.
Stephen
What version of FireOS are you on?
EncryptedCurse said:
What version of FireOS are you on?
Click to expand...
Click to collapse
Wont know until it arrives at the weekend. Will post details then.
Looking at Kingroot as a possible option.
Stephen
Shoog03 said:
Wont know until it arrives at the weekend. Will post details then.
Looking at Kingroot as a possible option.
Stephen
Click to expand...
Click to collapse
Make sure that you don't connect to WiFi.
Your tablet may very well come with an older firmware that'll allow you to unlock the bootloader and install TWRP (allowing access to Lollipop or Marshmallow ROMs).
EncryptedCurse said:
Make sure that you don't connect to WiFi.
Your tablet may very well come with an older firmware that'll allow you to unlock the bootloader and install TWRP (allowing access to Lollipop or Marshmallow ROMs).
Click to expand...
Click to collapse
Yep, will switch off WIFI first thing and then try pushing out the mod-update-kindle-thor-13.3.2.8_user_713328020.bin rollback ROM using adb or gMTP (a Linux utility).
Definately want to go down the TWRP route. Am I to assume that if its a later ROM then accessing the bootloader and installing TWRP is permanently blocked ?
Fingers crossed that this has been sat lingering in a cupboard for the last year and a half.
Stephen
Shoog03 said:
Yep, will switch off WIFI first thing and then try pushing out the mod-update-kindle-thor-13.3.2.8_user_713328020.bin rollback ROM using adb or gMTP (a Linux utility).
Definately want to go down the TWRP route. Am I to assume that if its a later ROM then accessing the bootloader and installing TWRP is permanently blocked ?
Fingers crossed that this has been sat lingering in a cupboard for the last year and a half.
Stephen
Click to expand...
Click to collapse
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
EncryptedCurse said:
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
Click to expand...
Click to collapse
Thats good to know.
There are so many redundant instruction sets out there that it is very confusing.
Will post the OS when I get it and hopefully get a good pointer to the right strategy.
Stephen
EncryptedCurse said:
Don't get ahead of yourself. You should check what firmware it comes with first, and only then evaluate your options; you shouldn't just blindly push the 3.2.8 update.
In order to unlock the bootloader, you'll need FireOS 3.2.3.2 or below. With the more recent versions, Amazon has included anti-rollback protection, which will permanently brick your device if you try to downgrade to anything past 3.2.8. Logically, this means that you'll be out of luck should your device come with FireOS 4 — at most, you'll be able to run a Kit Kat ROM on Safestrap, and others options will be, unfortunately, out of reach.
Click to expand...
Click to collapse
Further elaboration: If the device arrives with FireOS 3.2.6 or lower you can rollback and unlock the bootloader. The exact path depends which version is on the device. 3.2.7 (rare) is effectively the same as 3.2.8. As noted keep WiFi off (or airplane/flight mode engaged) as an OTA can push and unwanted update and further restrict your options.
Davey126 said:
Further elaboration: If the device arrives with FireOS 3.2.6 or lower you can rollback and unlock the bootloader. The exact path depends which version is on the device. 3.2.7 (rare) is effectively the same as 3.2.8. As noted keep WiFi off (or airplane/flight mode engaged) as an OTA can push and unwanted update and further restrict your options.
Click to expand...
Click to collapse
Great.
Is the OTA switch off method where you delete the DeviceSoftwareOTA.apk file still working ?
Stephen
Shoog03 said:
Great.
Is the OTA switch off method where you delete the DeviceSoftwareOTA.apk file still working ?
Click to expand...
Click to collapse
Depends on FireOS version. Renaming (don't delete) DeviceSoftwareOTA.apk works fine on v4. FireOS v3 seemed to have a more elaborate mechanism. Best use HDX Toolbox to kill OTA and related services.
You may not need to kill OTA at all if your intent is to root, rollback, unlock and flash a custom ROM. Depends on the version of FireOS on the device.
Davey126 said:
Depends on FireOS version. Renaming (don't delete) DeviceSoftwareOTA.apk works fine on v4. FireOS v3 seemed to have a more elaborate mechanism. Best use HDX Toolbox to kill OTA and related services.
You may not need to kill OTA at all if your intent is to root, rollback, unlock and flash a custom ROM. Depends on the version of FireOS on the device.
Click to expand...
Click to collapse
There is another one of those Catch 22 situations going on here. Assuming I cannot start by rolling back the first thing I will need to do is load up a version of ES File Manager. However this is available through the Amazon App store, but in order to install it I will have to enable the WIFI to download it - which runs the risk of a OTA kicking in at the same time. So I would rather use adb to push the APK of ES File manager out to the Kindle - but here is the second catch I need a file manager to install the pushed APK. I have been digging into using adb install but what I have found so far suggests that it wont install the ES File Manager. See this for a person asking a similar question (and not getting an answer):
http://forum.xda-developers.com/kin...help-installing-es-file-explorer-adb-t3018469
It seems the only way to get started is to engage WIFI, and that runs the distinct risk of taking me to a bad place through OTA.
Stephen
Shoog03 said:
There is another one of those Catch 22 situations going on here. Assuming I cannot start by rolling back the first thing I will need to do is load up a version of ES File Manager. However this is available through the Amazon App store, but in order to install it I will have to enable the WIFI to download it - which runs the risk of a OTA kicking in at the same time. So I would rather use adb to push the APK of ES File manager out to the Kindle - but here is the second catch I need a file manager to install the pushed APK. I have been digging into using adb install but what I have found so far suggests that it wont install the ES File Manager. See this for a person asking a similar question (and not getting an answer):
http://forum.xda-developers.com/kin...help-installing-es-file-explorer-adb-t3018469
It seems the only way to get started is to engage WIFI, and that runs the distinct risk of taking me to a bad place through OTA.
Click to expand...
Click to collapse
No catch 22 - "adb install app.apk" works fine for ES File Explorer. Skip the Amazon store; grab a copy from here.
Bigger challenge will be rooting if it arrives with FireOS v4 as the most popular tool (Kingroot) requires a brief internet connection to perform its magic. But the process is manageable if carefully monitored; dozens/hundreds have done it.
Again - let's see what version of FireOS is on the device. That will determine next steps and clarify any obstacles you may face.
Davey126 said:
No catch 22 - "adb install app.apk" works fine for ES File Explorer. Skip the Amazon store; grab a copy from here.
Bigger challenge will be rooting if it arrives with FireOS v4 as the most popular tool (Kingroot) requires a brief internet connection to perform its magic. But the process is manageable if carefully monitored; dozens/hundreds have done it.
Again - let's see what version of FireOS is on the device. That will determine next steps and clarify any obstacles you may face.
Click to expand...
Click to collapse
OK thanks, so all I have to do is
adb install <path to app on kindle>app.apk
In my specific case the full instructions will go:
adb kill-server
adb start-server
adb devices <confirm kindle present>
adb push /home/stephen/Desktop/Fire_HDX_7/ES-File-Explorer-4.0.4.1.apk /sdcard/Download/
adb install /sdcard/Download/ES-File_Explorer-4.0.4.1.apk
adb kill-server
Cheers
Stephen
Shoog03 said:
OK thanks, so all I have to do is
adb install <path to app on kindle>app.apk
Click to expand...
Click to collapse
adb install <path to app on PC>app.apk
I find it easier to copy the apk into the directory where minimal adb and fastboot lives. Streamlines installs/pushes as no path is needed. (I actually employ symlinks to an apk repository but that's another topic).
Davey126 said:
adb install <path to app on PC>app.apk
I find it easier to copy the apk into the directory where minimal adb and fastboot lives. Streamlines installs/pushes as no path is needed. (I actually employ symlinks to an apk repository but that's another topic).
Click to expand...
Click to collapse
So it finally arrived (only took about 3 weeks thanks to Ebays ****ty GSP delivery fraud).
It looks brand new, so might be a reconditioned unit. Its a third generation Thor running OS 4.5.5.1 with a Build date of 13 November 2015 (which seems very late and may present an issue in itself).
The roll back thread seems to indicate that it is possible to roll-back the 4.5.5.1 using the mod-update-kindle-thor-13.3.2.8_user_713328020.bin image. I have plugged the Kindle into my Linux box and it appears as an android device, and I dragged and dropped the rollback image to the Download folder. However it will not allow me to check for updates since it requires a working Internet connection to proceed.
I have attempted to place the bin file straight into the sd card next to the Internal Storage folder, but this is root privileged and I have not yet rooted the device.
So its seems it back to the situation that the first step has to be rooting - which means switching on the WIFI to run Kingroot.
So wanting to be extremely cautious at this stage is there any advice as to how to proceed.
I also pushed out a copy of ES_File manager and tried to install using adb install but got this
[email protected]:~> adb devices
List of devices attached
D0FBA0A034530BHD unauthorized
[email protected]:~> adb install /sdcard/Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: /sdcard/Download/ES-File-Explorer-4.0.4.1.apk
[email protected]:~> adb install /Internal storage/Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: storage/Download/ES-File-Explorer-4.0.4.1.apk
[email protected]:~> adb install /Download/ES-File-Explorer-4.0.4.1.apk
Invalid APK file: /Download/ES-File-Explorer-4.0.4.1.apk
Click to expand...
Click to collapse
Stephen
OK, I didn't follow the instructions for the rollback precisely. I placed the rollback file into the internal storage folder and it found it straight away and is currently installing and doing its first reboot.
Stephen
So i am now running the rollback 13.3.2.8
What next ?
Best root method and then install safestrap and Kitkat and call it a day ?
Stephen
Managed to sideload ES_File_explorer by copying the file into my adb folder and running adb install.
Now I am downloading the update ROM 4.5.2
Will then sideload cve20147911.apk
Stephen
Successful upgraded to 4.5.2
So I installed Superuser and unlocked the root, but when I try to use ES_File_explorer to access the root it prompts with needs ES-permissions manager plugin. It offers to download it but that means switching on WIFI. I have tried to get the .apk file but don't find a good candidate, does anyone have any pointers.
Don't want to switch on the WIFI until OTA is disabled for which I need the permissions manger plugin.
Stephen
Shoog03 said:
Successful upgraded to 4.5.2
So I installed Superuser and unlocked the root, but when I try to use ES_File_explorer to access the root it prompts with needs ES-permissions manager plugin. It offers to download it but that means switching on WIFI. I have tried to get the .apk file but don't find a good candidate, does anyone have any pointers.
Don't want to switch on the WIFI until OTA is disabled for which I need the permissions manger plugin.
Stephen
Click to expand...
Click to collapse
Took the long rollback/upgrade road - 4.5.5.1 can be directly rooted with Kingroot. Assuming you secured root there is no need to tweak permissions. Simply rename DeviceSoftwareOTA.apk (details).
I am furious. I did not realized that Fire HDX 8,9, (3rd generation) v4.5.5.1 is totally different OS from "normal Android OS" and now I wonder what can I do about it.
How can I uninstall Amazon Android OS and replace it with normal Android OS.
Can that be done? If yes HOW?
I have been searching and reading here, but I am even more confused (yes I am Fire HDX newbie). I would really appreciate if I can get clear and logical instructions HOW can I do that for my unit.
I managed to install Kingroot and was able to login to my Google Play account as I have 2 Android phones (Samsung S2 and Leagoo Lead 1), but when I login and tried to download RootChecker, Google Play does NOT show (recognize) my FireHDX, it only shows my other 2 phones. So that's not good for me.....
Any help will be greatly appreciated as the way is my Fire now is useless.
TIA
Ivone said:
I am furious. I did not realized that Fire HDX 8,9, (3rd generation) v4.5.5.1 is totally different OS from "normal Android OS" and now I wonder what can I do about it.
How can I uninstall Amazon Android OS and replace it with normal Android OS.
Can that be done? If yes HOW?
I have been searching and reading here, but I am even more confused (yes I am Fire HDX newbie). I would really appreciate if I can get clear and logical instructions HOW can I do that for my unit.
I managed to install Kingroot and was able to login to my Google Play account as I have 2 Android phones (Samsung S2 and Leagoo Lead 1), but when I login and tried to download RootChecker, Google Play does NOT show (recognize) my FireHDX, it only shows my other 2 phones. So that's not good for me.....
Any help will be greatly appreciated as the way is my Fire now is useless.
TIA
Click to expand...
Click to collapse
Likely find what you need in the following thread (one of several btw). Read, go slow, reread to confirm understanding, ask if unsure, ignore internet/youtube guidance from 'experts' not familiar with this device. HDX devices are easy to brick and tough/impossible to recover if you stray off the beaten trail.
http://forum.xda-developers.com/kin...artially-fire-os-to-proper-rom-t3421623/page4
fwiw - I am penning this on a 3rd gen HDX thor (7") running Fire Nexus which is my primary device (3-4 hours per day) despite having access to numerous other computing gizmos with far better headlines. Yep, lowly kitkat on a 2+ year old (unlocked) tablet. Go figure. You can duplicate that 98% of that config with minimal effort.
Thanks Davey, I am reading all the post in that thread you posted. Looks like I am on the right path.
I have 4.5.5.1 and Kingroot installed already on my Fire and working. Installed ES File Explorer and tested. I am rooted. !
Next step is to install Safestrap 4.0.1 - right?
After that I will go with HDX Nexus ROM v4 (as I red it's the best for my Fire HDX)
Then will proceed with HDX Nexus ROM installation ...
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery (HOW do I do that?)
- You should eventually end up in safestrap recovery
Once I do that the instruction is: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-safestrap-v4-0-1-t3137840
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Which one do I download THOR or APOLLO? (little confused here)
Also, should I delete any or all aplications that I downloaded and installed from Amazon?
Will everything work normal such as: Wifi, AGPS etc? Any known issues with my FireHDX?
TIA
Ivone said:
Thanks Davey, I am reading all the post in that thread you posted. Looks like I am on the right path.
I have 4.5.5.1 and Kingroot installed already on my Fire and working. Installed ES File Explorer and tested. I am rooted. !
Next step is to install Safestrap 4.0.1 - right?
After that I will go with HDX Nexus ROM v4 (as I red it's the best for my Fire HDX)
Then will proceed with HDX Nexus ROM installation ...
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery (HOW do I do that?)
- You should eventually end up in safestrap recovery
Once I do that the instruction is: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-safestrap-v4-0-1-t3137840
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Which one do I download THOR or APOLLO? (little confused here)
Also, should I delete any or all aplications that I downloaded and installed from Amazon?
Will everything work normal such as: Wifi, AGPS etc? Any known issues with my FireHDX?
TIA
Click to expand...
Click to collapse
Response to questions:
- HDX 7" = Thor; HDX 8.9" = Apollo (you want Apollo)
- reboot to recovery: you will be prompted (or just shutdown & restart)
- no need to delete existing applications
- everything works in Nexus - WiFi, Bluetooth, location services (no GPS unless you have LTE model), Play Store, etc. No significant issues.
Davey126 said:
Response to questions:
- HDX 7" = Thor; HDX 8.9" = Apollo (you want Apollo)
- reboot to recovery: you will be prompted (or just shutdown & restart)
- no need to delete existing applications
- everything works in Nexus - WiFi, Bluetooth, location services (no GPS unless you have LTE model), Play Store, etc. No significant issues.
Click to expand...
Click to collapse
Davey, I have not abandon the OS changing process, I am just VERY scared. Since my post, I have been reading and reading like crazy hundreds pages trying to understand between all the info what exactly is related to only my FireHDX, but did NOT found exact instruction. A lot for HD, HDX 7 etc. It looks like that my Fire is not very popular
I will write again my setup.
Fire HDX 8,9, 4.5.5.1, (3rd generation), 16GB, 4G/LTE, free space left 6.86GB, all stock. Only extra apps I installed are: Opera, GPS Test, KingRoot that I used to Root (working), ES File Explorer that I used to change the permissions like this > Root Explorer>Mount R/W>changed permission to RW in: /system and /mnt/sqfs
I have Windows 7, 32
I am a complete chicken to proceed further.
I imagine next step is to install Safestrap but I am not sure what is the latest version for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE
(it looks like Safestrap 4.0.1 is the one I should use - correct?) If yes should I follow your instruction BELLOW from other thread?
Next step is to install Safestrap 4.0.1 which provides a pseudo recovery environment that supports the installation of custom roms. You can snag the app from here (got the URL - np), be sure to select the appropriate format (APOLLO). Once installed launch the app and install Safestrap recovery which is the component that does the heavy lifting.
Now reboot. You'll notice a new screen that has a couple options at the bottom. Select the option that launches Safestrap recovery. From home screen 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 (will transfer to my PC.). 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).
What is the correct slot that I should use? I just found the answer = Stock slot!
Do I have to download some drivers to my PC for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE and transfer them to Fire directory? If yes, what drivers and where should I place them. (found the answer - 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)
Apollo Nexus ROM will be my prefer choice, but wonder if everything will work.
I know that you answer that, but then you mention 4G/LTE, is that mean it will work as well or my SIM/phone/data will not work.
Is there any known issue (what will NOT work) on my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE once I change to Apollo Nexus ROM?
Also I like to ask you if CM11 will have any advantage over Nexus on MY Fire HDX. Just wonder (as you said it has nice GUI etc.)
I red tons and tons of yours and other people posts and I am VERY great full for all your time and help you offer to newbie like me. Your dedication is awesome.
UPDATE
I took the plunge and installed Safestrap and all is fine (checked few times)
I downloaded Nexus Apollo and placed it into folder that I created in the FireHDX Internal Storage. I don't see or know how I can create folder in the root directory in
my Fire sdcard.
I am trying to follow your instructions from your other post:
Nexus Apollo installation zip. 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. (HOW) 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.
That's exactly my concern - will my Apollo Nexus folder get deleted when I install it Nexus on the Stock Slot. Does it wipe ALL the folders in the Internal Storage?
Can I/ should I move the ApolloNexus folder using ES File Explorer 3.0.5 in to Fire Device directory or Root and will I be able to access it after the wipe.?
I am stuck..................!
TIA
Attaching image where is the folder now - is it safe there?
Ivone said:
Davey, I have not abandon the OS changing process, I am just VERY scared. Since my post, I have been reading and reading like crazy hundreds pages trying to understand between all the info what exactly is related to only my FireHDX, but did NOT found exact instruction. A lot for HD, HDX 7 etc. It looks like that my Fire is not very popular
I will write again my setup.
Fire HDX 8,9, 4.5.5.1, (3rd generation), 16GB, 4G/LTE, free space left 6.86GB, all stock. Only extra apps I installed are: Opera, GPS Test, KingRoot that I used to Root (working), ES File Explorer that I used to change the permissions like this > Root Explorer>Mount R/W>changed permission to RW in: /system and /mnt/sqfs
I have Windows 7, 32
I am a complete chicken to proceed further.
I imagine next step is to install Safestrap but I am not sure what is the latest version for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE
(it looks like Safestrap 4.0.1 is the one I should use - correct?) If yes should I follow your instruction BELLOW from other thread?
Next step is to install Safestrap 4.0.1 which provides a pseudo recovery environment that supports the installation of custom roms. You can snag the app from here (got the URL - np), be sure to select the appropriate format (APOLLO). Once installed launch the app and install Safestrap recovery which is the component that does the heavy lifting.
Now reboot. You'll notice a new screen that has a couple options at the bottom. Select the option that launches Safestrap recovery. From home screen 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 (will transfer to my PC.). 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).
What is the correct slot that I should use? I just found the answer = Stock slot!
Do I have to download some drivers to my PC for my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE and transfer them to Fire directory? If yes, what drivers and where should I place them. (found the answer - 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)
Apollo Nexus ROM will be my prefer choice, but wonder if everything will work.
I know that you answer that, but then you mention 4G/LTE, is that mean it will work as well or my SIM/phone/data will not work.
Is there any known issue (what will NOT work) on my Fire HDX 8,9, 4.5.5.1, 16GB, 4G/LTE once I change to Apollo Nexus ROM?
Also I like to ask you if CM11 will have any advantage over Nexus on MY Fire HDX. Just wonder (as you said it has nice GUI etc.)
I red tons and tons of yours and other people posts and I am VERY great full for all your time and help you offer to newbie like me. Your dedication is awesome.
UPDATE
I took the plunge and installed Safestrap and all is fine (checked few times)
I downloaded Nexus Apollo and placed it into folder that I created in the FireHDX Internal Storage. I don't see or know how I can create folder in the root directory in
my Fire sdcard.
I am trying to follow your instructions from your other post:
Nexus Apollo installation zip. 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. (HOW) 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.
That's exactly my concern - will my Apollo Nexus folder get deleted when I install it Nexus on the Stock Slot. Does it wipe ALL the folders in the Internal Storage?
Can I/ should I move the ApolloNexus folder using ES File Explorer 3.0.5 in to Fire Device directory or Root and will I be able to access it after the wipe.?
I am stuck..................!
TIA
Attaching image where is the folder now - is it safe there?
Click to expand...
Click to collapse
Looks like you made some progress (good!) but have the following questions/concerns:
>> Nexus zip location: fine where it is (as shown in your screen shot)
>>Compatibility: no rom is perfect including FireOS. While Fire Nexus is time proven and stable some issues remain:
- 4G/LTE voice does not work
- 4G/LTE data can be finicky; depends on your carrier
- Some Play Store apps (especially games and social media) show as 'incompatible' but typically can be sideloaded without further issue
- Some apps rotate screen 90/180 degrees from 'features' orientation; easily fixed using one of several methods
- Native spell checker crashes foreground application if a replacement word is selected (keyboard spell checkers work fine)
- some browsers/sites mistake big, beautiful, high-res HDX for desktop and do not automatically present mobile version (not a big deal)
- no OTG (external dongle/storage) support...nor is there on FireOS or any other rom for this device; hardware limitation
- GPS is slow and can not be used for driving guidance or games like Pokémon. Same with FireOS. However, static mapping apps are fine.
Yikes - seems like a long list!! Yet an equivalent FireOS manifest would consist of dozens of bullets and take up multiple pages. My wonderful mobile 'issue' list is 3-4x longer. Pick your poison.
Davey126 said:
Looks like you made some progress (good!) but have the following questions/concerns:
>> Nexus zip location: fine where it is (as shown in your screen shot)
>>Compatibility: no rom is perfect including FireOS. While Fire Nexus is time proven and stable some issues remain:
- 4G/LTE voice does not work
- 4G/LTE data can be finicky; depends on your carrier
- Some Play Store apps (especially games and social media) show as 'incompatible' but typically can be sideloaded without further issue
- Some apps rotate screen 90/180 degrees from 'features' orientation; easily fixed using one of several methods
- Native spell checker crashes foreground application if a replacement word is selected (keyboard spell checkers work fine)
- some browsers/sites mistake big, beautiful, high-res HDX for desktop and do not automatically present mobile version (not a big deal)
- no OTG (external dongle/storage) support...nor is there on FireOS or any other rom for this device; hardware limitation
- GPS is slow and can not be used for driving guidance or games like Pokémon. Same with FireOS. However, static mapping apps are fine.
Yikes - seems like a long list!! Yet an equivalent FireOS manifest would consist of dozens of bullets and take up multiple pages. My wonderful mobile 'issue' list is 3-4x longer. Pick your poison.
Click to expand...
Click to collapse
Thank you Davey for the detail explication.
Wow, what a disappointment with all the Nexus rom issues. Oh well, that will scrap my Vodafone appointment today. In that case I will research alternatives (if they exist). Basically I was going to use it MAINLY for Waze or Sygic navigation and calls. I am not in to games, music, movies etc.
Co you have any idea how is CM11 behave with my type of Fire? Or what would you suggest?
Thanks again for your time and help.
One more time my apologies rambling about the setup request. I have read about so many problems and bricking that put me in the panic mode.
Ivone said:
Thank you Davey for the detail explication.
Wow, what a disappointment with all the Nexus rom issues. Oh well, that will scrap my Vodafone appointment today. In that case I will research alternatives (if they exist). Basically I was going to use it MAINLY for Waze or Sygic navigation and calls. I am not in to games, music, movies etc.
Co you have any idea how is CM11 behave with my type of Fire? Or what would you suggest?
Thanks again for your time and help.
One more time my apologies rambling about the setup request. I have read about so many problems and bricking that put me in the panic mode.
Click to expand...
Click to collapse
You will not be able to use a HDX for dynamic navigation regardless of app or rom - including FireOS. The integrated GPS 'chip' is has proven unreliable and is too slow to keep up with rapidly changing locations. It is also slow to acquire satellites (minutes) and often needs a reboot if the GPS appears unresponsive. Works fine for static location apps/maps using Google's fused location services. Static mapping/location apps are less reliable on FireOS; many will not work at all. Sorry for the bad news ...
Davey126 said:
You will not be able to use a HDX for dynamic navigation regardless of app or rom - including FireOS. The integrated GPS 'chip' is has proven unreliable and is too slow to keep up with rapidly changing locations. It is also slow to acquire satellites (minutes) and often needs a reboot if the GPS appears unresponsive. Works fine for static location apps/maps using Google's fused location services. Static mapping/location apps are less reliable on FireOS; many will not work at all. Sorry for the bad news ...
Click to expand...
Click to collapse
What can I say, big disappointment and dumb decision to buy Kindle.
I may try to sell my Kindle that I used once or twice (just playing around ) and buy something else.
BIG thanks again Davey and sorry wasting your time.
Ivone said:
What can I say, big disappointment and dumb decision to buy Kindle.
I may try to sell my Kindle that I used once or twice (just playing around ) and buy something else.
BIG thanks again Davey and sorry wasting your time.
Click to expand...
Click to collapse
Not a waste of time if useful knowledge was exchanged. Despite the disappointment HDX tablets are wonderful devices that can perform many tasks better than contemporary high-end alternatives. Unfortunately, navigation is not one of them.
Davey126 said:
Not a waste of time if useful knowledge was exchanged. Despite the disappointment HDX tablets are wonderful devices that can perform many tasks better than contemporary high-end alternatives. Unfortunately, navigation is not one of them.
Click to expand...
Click to collapse
Oh well, your right. I am also believer that everything is good for something....
BTW: is it complicated to bring my KF back to stock with out any negative consequences?
Can I just delete Safestrap?
Ivone said:
Oh well, your right. I am also believer that everything is good for something....
BTW: is it complicated to bring my KF back to stock with out any negative consequences?
Can I just delete Safestrap?
Click to expand...
Click to collapse
Assuming you have not installed a custom rom simply uninstall Safestrap recovery from the within Safestrap app and then close and uninstall the Safestrap app itself.
Davey126 said:
Assuming you have not installed a custom rom simply uninstall Safestrap recovery from the within Safestrap app and then close and uninstall the Safestrap app itself.
Click to expand...
Click to collapse
Ok, thanks a lot... (no rom installed)
Just checking if there is any news on that matter. Or maybe any new stable Android I can install. As of now I'm just using my HDX 8.9 to watch movies when travelling. Thx!
antonioroc said:
Just checking if there is any news on that matter. Or maybe any new stable Android I can install. As of now I'm just using my HDX 8.9 to watch movies when travelling. Thx!
Click to expand...
Click to collapse
Your question is not entirely clear but it is now possible to install a wide array of high quality custom ROMs on any 3rd (not 4th) gen HDX representing Android 4.4 (KitKat) to 7.1 (Nougat). All offer full access to Google Play along with the amenities that come with native Android and a well stocked app store. That said, if you are only using your HDX to watch movies FireOS remains a solid choice
Thanks for replying. Do you have a tutorial on how to install 7.1 (Nougat) into 8.9 3rd Thor?
antonioroc said:
Thanks for replying. Do you have a tutorial on how to install 7.1 (Nougat) into 8.9 3rd Thor?
Click to expand...
Click to collapse
You have to root FireOS (or pursue a somewhat more complex alternative) and then unlock the bootloader to enable installation of Android 7.x based ROMs on this device. The prep work can be a bit daunting for those new to tinkering with Android devices. The following thread is a good starting point.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
I'm just not getting there
I've been following this post for some time trying to do the same with my 3rd Gen fire HDX 8.9. I'm on OS version 4.5.5.3 and can't seem to get into the system by doing any of the turn-on procedures (turn-on, wait then hold power button, power and volume up, etc.). Has Amazon locked us out with the latest update? Did I buy this and get stuck with a useless (nearly) box of rocks? I have ES File manager, Safestrap 4.01 and Kingroot installed and I'm able to get to the root directory, but I'm lost after that.
Bobkuwait said:
I've been following this post for some time trying to do the same with my 3rd Gen fire HDX 8.9. I'm on OS version 4.5.5.3 and can't seem to get into the system by doing any of the turn-on procedures (turn-on, wait then hold power button, power and volume up, etc.). Has Amazon locked us out with the latest update? Did I buy this and get stuck with a useless (nearly) box of rocks? I have ES File manager, Safestrap 4.01 and Kingroot installed and I'm able to get to the root directory, but I'm lost after that.
Click to expand...
Click to collapse
Not sure what you are trying to do but sounds like the wrong procedure. You can follow along in this thread as I assist another Apollo user with a similar configuration unlock the bootloader in preparation for installation of a custom ROM. Please note you will NOT be able to use this device for dynamic navigation regardless of ROM.
Just not getting there
Davey126 said:
Not sure what you are trying to do but sounds like the wrong procedure. You can follow along in this thread as I assist another Apollo user with a similar configuration unlock the bootloader in preparation for installation of a custom ROM. Please note you will NOT be able to use this device for dynamic navigation regardless of ROM.
Click to expand...
Click to collapse
I want to put a full version of Android on my Kindle Fire HDX 8.9 3rd generation. I've followed along on the website. and cannot seem to get a bootloader to open on my Kindle. Running OS 4.5.5.3. I have downloaded several ROMs (CM 12.1, CM 14.1 KK Nexus for fire, but cant get to the bootloader to run any of them. Is there a step-by-step guide anywhere? I was able to get my Nook to the CM 12 platform quite easily.
Well that was an adventure. I inadvertently ended up with an upgrade to VS9854CA over-the-air which predictably killed my root and wiped my setup. Life sucked, but livable until the screen started doing the flashy fade to back lockup. Now I've got to do something - I really don't want a new phone, I like my LG G3 even if the carrier is basically Evil Corp.
First things first: I had to fix the screen. I noted that the newer ROM was making the phone hotter. That's a side effect of what is truly an improvement in responsiveness from my old old version. I also noted that it seemed to get better if I manipulated the covers. Loose part somewhere? Quick search on the forums turned up this thread: "[GUIDE] Fix Display Flickering, Overheat and Constant Rebooting" with thanks to @IngJulian_RVLX. Reading it showed a basic problem to be sure but wasn't an entire fix. It did give me the idea what was needed though. So I disassembled the phone and re-flowed the main chips with a heat gun (NOT a hair dryer - not hot enough, focused enough, and way too much airflow, and DEFINITELY NOT a toaster oven - this will fry other components), then cleaned the board. Using silicon pad I placed one on the top of the main chip on the "front" (faces the display when assembled and has the big shield on it), then another piece over that one the length of the metal shield. Then I put another piece of silicon pad on the chip on the back side under the smaller metal shield. Reassemble the phone. Power up. Okay, we're working again without the annoying flashy fading screen.
So now the problem is getting root and TWRP back. Again the search: "Root for LG G3 VS985 Android 6.0 47A". Thanks to @annoyingduck and @roirraW "edor" ehT. I found a 10B .tot file and flashed that successfully. Only one big problem - adb would not find the phone! Turns out the identifier pulled in a G3 device and not the VS985 device for which I had a debug stack. Not to worry, stump is an apk so I should be able to upload right? Nope, it's offline. Well the suggested alternative, kingroot.net, exists try that. Yup that worked - I'm now rooted and victimized by all the bloatware kingroot brings with it.
Rather than debloat the kingroot I figured it does no harm in the moment. So let's get TWRP back so I at least have a recovery. Of course the CodeFire team has what I need and TWRP is installable as an app now. The first time I rooted it was a manual load with dd - progress! Just search the Play Store for TWRP, load and go. Nice work guys!!!
Okay so how to get up to the latest version possible and still keep root? Because, hey as long as I'm in here why not? Searching I find this: "[Guide] [VS985] Flash Back To Stock - KDZ Method". Yup, once more @annoyingduck to the rescue - a repository of .KDZ files along with more helpful experience. I managed to find this thread as well: "[TOOL] KDZ and TOT Extractor" with thanks to @bullghost. Still not quite what I need yet. I found "VS985 47A - Stock Flashable Firmware" with thanks to @xdabbeb. That's the ticket! So flashed that (and the bootstack) and now I'm at least a marshmallow 6.0 version. Lost root, but kingroot was able to root (and bloat).
Now to get rid of kingroot and put on superSU instead. Search found this: "How to Remove/Replace Kingroot (KingUser) with SuperSu". There, that's better! After a reboot I have to manually remove the last vestiges of kingroot but SuperSU is happily running and the bloatware is gone. Now I can restore the phone to it's prior level of function. Play Store restored my apps, I did have to reconfigure my home screens, but I'm now back in business. What's more I've got an upgrade that I like.
Whoops! An OTA update flashes on my screen!!! NO!!!!! Okay, calm down. This took several searches to find so basically here's what I needed to do:
1. Delete the files in the /cache/fota directory - this allowed the OTA to fail without updating my phone.
2. Find the "System updates" in the application manager - there are two of them and you have to select 'system' in the drop down to see them. One of them can be disabled the other cannot.
3. Find /system/app/FOTA and rename the LGFOTA.apk file to LGFOTA.apk.bak
No, using hiddenmenu.apk or the ##PROGRAM985 or any other method does not work. Apparently Evil Corp. doesn't pay attention to this anymore and that's why I got the original update that killed me. Thanks to this post for the tips: "[PSA] NO OTAs!! | Keep Root/Unlock | How-To: Block OTA, DL SW/FW, Update Manually" and h/t to @autoprime.
So now I've got some work to do, because there's some fun to be had. I've managed to get the VS985CA .KDZ and extracted it. I've got the .img files ready. Now I just have to add su and busybox to the system image under linux and then I can flash these files to the phone using FlashFire (again CodeFire team - what can I say, you guys rock). Time to make the chimichungas!
Moral of the story here is this:
I've been playing around with android phones and root since my HTC Incredible. Xda-Developers has always been a source of good information but it only works if you use it. I found the original hiddenmenu.apk and it was the forums that gave me the invocation command to bring it up - somewhere in the original VS985 root thread I'm there contributing that information. Do the searches and you can find the answers you need without being annoying. Also give it time - these people I've mentioned throughout this post (along with many more) are working as fast AND as carefully as they can to bring the best solutions possible to problems. But you do have to do your part, if you aren't going to put the time in to learn at least the basics by reading the forums than this isn't your rodeo. I'm no expert but I do know how to think, experiment, and I have some background in linux and have some familiarity with android application development so I could understand something of what this device is doing and how it's built. If you lack that and you're going to play here my best advice is to have a backup phone - 'cause you're going to brick yours a few times before you learn that these basics are required, even if you're not going to be a "cool ROM" developer. That's the dues you pay to play. The experienced folks will realize my mistakes made, as I do, in this post. That's because they are the experts and I am not. Did I get where I wanted to get? Yes. Was it elegant? No. But having paid the dues I never needed to ask. Just admit to myself that I needed to get smarter and dug in. Besides, it was kinda nice not to be bugged by the phone for a day.
Quick update to the above...
The task to kill is com.lge.lgdmsclient. It took ES Task manager to find it. I moved the offending apps off to quarantine on my SD card after setting them to disable in the ES Task manager and no more OTA updates.