Related
Hello!
A few weeks ago, HTC sends me an update to fix the Heartbleed Bug from Android 4.1. On my device I have root and Xposed. If I install the update, would it remove my root and Xposed? It's my first Android Update after rooting
Thanks,
Weely_XD
I think you have to go back to full stock (Rom,recovery,bootloader locked) to update, so yes update remove root.
Could someone that installed this confirm if root was lost or not?
Thanks!
I will not be changed
romy25 said:
I will not be changed
Click to expand...
Click to collapse
of course not, but what about your phone, LOL
Well, I went ahead and installed the stock recovery and this OTA-update.
Everything seemed fine so I re-installed a new copy of TWRP (same version number as I had before)... Confused me totally. It was asking me to root again as soon as I quit recovery, which I did a few times... But I could never finish the installation of SuperSU. It always failed...
I was messing around with this for 2 days, until I for some reason tried to install TWRP from another "old" file I found on my computer (the exact same file I used when i rooted my phone the first time).
Now everything worked fine...
I guess the other recovery image was corrupt, incorrect, or something else...
Well, the mess was sorted out at least, and I still have root, did not have to reset my phone, and everything else seems to be OK.
Thanks! :good:
I have been working on a new version of Safestrap. This aims to allow devices that aren't unlockable and running update-kindle-xx.4.5.2_user_452004120 to install HDX Nexus ROM v4.xx.
I am looking for a Thor and Apollo tester to confirm that they can indeed install Nexus ROM v4 with this.
I have confidence that this works, but if you agree to do this please understand as usual that you do so at your own risk.
So far the new version has been tested on unlocked devices to confirm compatibility and works fine.
The next stage is to test on locked devices, which as I have said have high confidence that it will work.
The prerequisites for test are:
- Must be running stock update-kindle-xx.4.5.2_user_452004120 firmware
- Must be rooted
Things to be aware of with the new version:
- Secondary slots boot, but the WiFi module does not load
- Since the secondary slots work but have no WiFi, you will need to flash Nexus v4 to the stock slot
Let me know if are interested in helping with this.
ggow said:
I have been working on a new version of Safestrap. This aims to allow devices that aren't unlockable and running update-kindle-xx.4.5.2_user_452004120 to install HDX Nexus ROM v4.xx.
I am looking for a Thor and Apollo tester to confirm that they can indeed install Nexus ROM v4 with this.
I have confidence that this works, but if you agree to do this please understand as usual that you do so at your own risk.
So far the new version has been tested on unlocked devices to confirm compatibility and works fine.
The next stage is to test on locked devices, which as I have said have high confidence that it will work.
The prerequisites for test are:
- Must be running stock update-kindle-xx.4.5.2_user_452004120 firmware
- Must be rooted
Things to be aware of with the new version:
- Secondary slots boot, but the WiFi module does not load
- Since the secondary slots work but have no WiFi, you will need to flash Nexus v4 to the stock slot
Let me know if are interested in helping with this.
Click to expand...
Click to collapse
I'm interested in test. how can i apply for tester?
zamtang said:
I'm interested in test. how can i apply for tester?
Click to expand...
Click to collapse
I'll PM you.
I got brave
so yeah had the problem of being on nexus rom for SS but i had no backup of 3.2.8 to return to so i did the following and it worked
downloaded 3.2.8 rollback file
made a backup of Nexus rom system partition
wiped system, data, cache, dalvik
flashed 3.2.8 rollback after i renamed it to .zip from .bin
bit nail with butterflies
success
poweroff
power on tablet
amazon logo
fire logo
lockscreen
breathe out
im gonna update to 4.5.2 just gotta get rid of safestrap then Im in for testing.
Update
On Thor @zamtang confirmed he can get into Safestrap recovery
Now waiting for confirmation that HDX Nexus ROM v4 is running.
Still awaiting a Tester for Safestrap on Apollo...
LittleGreenSony said:
so yeah had the problem of being on nexus rom for SS but i had no backup of 3.2.8 to return to so i did the following and it worked
downloaded 3.2.8 rollback file
made a backup of Nexus rom system partition
wiped system, data, cache, dalvik
flashed 3.2.8 rollback after i renamed it to .zip from .bin
bit nail with butterflies
success
poweroff
power on tablet
amazon logo
fire logo
lockscreen
breathe out
im gonna update to 4.5.2 just gotta get rid of safestrap then Im in for testing.
Click to expand...
Click to collapse
Congrats!! Rolled the dice and won!
Be mighty careful around the 4.5.2 update. Those who received it via OTA (may have been 4.5.3/4.5.4) were treated to a hard brick with no known resolution. Best do the update manually using the procedure/files outlined in this thread. Stay off wifi until 4.5.2 upgrade is complete.
Saturn is fine with 4.5.4, but I assume you are talking about apollo/thor
XxD34THxX said:
Saturn is fine with 4.5.4, but I assume you are talking about apollo/thor
Click to expand...
Click to collapse
Yes I am talking about Apollo and Thor, If anyone can loan me a Saturn that is rooted then I will work on Safestrap for it.
Thor Safestrap - Nexus ROM v4 working
@zamtang has confirmed Safestrap and Nexus ROM v4 is working.
Thank you zamtang for taking a leap of faith, it's not something I would ask without been confident and without serious consideration.
Attached is a screenshot provided by zamtang.
hi~
I'm interested in test. how can i apply for tester?
TAE WON SEO said:
I'm interested in test. how can i apply for tester?
Click to expand...
Click to collapse
Hello, do you have an Apollo device?
I am interested in testing safestrap and the new nexus rom... is there any chance that this will hard brick my device? If yes, what percent?
Well...
Davey126 said:
Congrats!! Rolled the dice and won!
Be mighty careful around the 4.5.2 update. Those who received it via OTA (may have been 4.5.3/4.5.4) were treated to a hard brick with no known resolution. Best do the update manually using the procedure/files outlined in this thread. Stay off wifi until 4.5.2 upgrade is complete.
Click to expand...
Click to collapse
my device had no safestrap but it was rooted decided to let it auto update so turned on wifi and checked for update. the update centre said no update found, so went and downloaded 4.5.2 from amazon that was taking a lot longer than it should. checked the update center again. a glitchy 4.1.1 was downloading with the download bar glitching from view. i then let it continue pausing 4.5.2 download it then promptly rebooted and attempted to install 4.1.1 the screen went black through the update. hard brick.. i have my warranty and i have another one coming.
here's a tip don't update to 4.1.1 if you are rooted.
hoping to get a kindle with <3.2.6 my first one was originally that <version
LittleGreenSony said:
my device had no safestrap but it was rooted decided to let it auto update so turned on wifi and checked for update. the update centre said no update found, so went and downloaded 4.5.2 from amazon that was taking a lot longer than it should. checked the update center again. a glitchy 4.1.1 was downloading with the download bar glitching from view. i then let it continue pausing 4.5.2 download it then promptly rebooted and attempted to install 4.1.1 the screen went black through the update. hard brick.. i have my warranty and i have another one coming.
here's a tip don't update to 4.1.1 if you are rooted.
hoping to get a kindle with <3.2.6 my first one was originally that <version
Click to expand...
Click to collapse
Yeah I would say as a rule never let them auto-update.
Update -Apollo
@paul26rem has confirmed that Safestrap came up good on his Apollo.
Now awaiting confirmation that HDX Nexus ROM is running.
EDIT: Confirmed - Apollo Safestrap is good - Nexus v4 running on it.
LittleGreenSony said:
my device had no safestrap but it was rooted decided to let it auto update so turned on wifi and checked for update. the update centre said no update found, so went and downloaded 4.5.2 from amazon that was taking a lot longer than it should. checked the update center again. a glitchy 4.1.1 was downloading with the download bar glitching from view. i then let it continue pausing 4.5.2 download it then promptly rebooted and attempted to install 4.1.1 the screen went black through the update. hard brick.. i have my warranty and i have another one coming.
here's a tip don't update to 4.1.1 if you are rooted.
hoping to get a kindle with <3.2.6 my first one was originally that <version
Click to expand...
Click to collapse
For the benefit of others ...
NEVER take an OTA update on 3.2.8. Every reported incident has resulted in a hard brick. Keep WiFi off until OTA is blocked. The only effective method is via HDX toolkit. Renaming otacerts won't work on 3.2.8.
@ggow Any idea when this version will be released for Thor or if I could help test it? It would be awesome to have 4.5.2 with Safestrap.
RJDTWO said:
@ggow Any idea when this version will be released for Thor or if I could help test it? It would be awesome to have 4.5.2 with Safestrap.
Click to expand...
Click to collapse
Been out for several weeks! See: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-safestrap-v4-0-1-t3137840
Thread Closure
Hello @Moscow Desire,
Would you mind closing this thread.
Cheers, ggow
ggow said:
Hello @Moscow Desire,
Would you mind closing this thread.
Cheers, ggow
Click to expand...
Click to collapse
No problem
Thread closed at OP request
MD
I had taken over a thread in the General Forum (regarding rooting 4.5.4) to discuss this issue because I thought it was related to root, but after further work I don't think that to be the case. Anyway, here is where this stands:
When I open the amazon instant video app everything loads properly. Recently played, watchlists, prime videos, etc. Whenever I tap a video to watch via streaming or attempt to download I receive the error LICENSE_ERROR. I followed all of amazon's instructions to try and resolve this including: 1) clear app cache and clear app data. 2) Deregister and reregister device and 3) factory data reset. None of these solved the issue.
I contacted amazon again today regarding this and they escalated this and they said they will email me within 24-48 hours with a proposed resolution. If anyone has had this issue and figured out how to resolve it please let me know. Otherwise, I'll continue the process with amazon. Thanks.
I have the exact same problem. I even completely uprooted and it did not fix. After about 30 minutes on the phone, they are sending me a new tablet.
It works fine in the 5.2 developer build, but not in 4.5.3 or 4.5.4. I have cycled a couple times to confirm. I even tried sideloading older versions of the apk. Some versions crash, some give the error. I also tried all the steps you did.
It must be a key issue on amazon side, why does it work in lollipop but not stock even when fresh (wiped all partitions) ?
I would have stayed on the preview, but skype was not working for me.
Wow, this sounds crazy. Did it ever work for you guys before you got root?
It just seems that if you replace everything by stock, the Video should work. A way to do this is to install 4.5.2 via TWRP, replace TWRP with the standard recovery, and then trigger a regular update to 4.5.3 by putting the file on the device. This way it'll be full 4.5.3 stock, updated via the proper procedures. This should be fairly quick to do.
4.5.4 to stock unrooted 4.5.3?
bibikalka said:
It just seems that if you replace everything by stock, the Video should work. A way to do this is to install 4.5.2 via TWRP, replace TWRP with the standard recovery, and then trigger a regular update to 4.5.3 by putting the file on the device. This way it'll be full 4.5.3 stock, updated via the proper procedures.
Click to expand...
Click to collapse
Wondered how to do this. Won't, but want to learn, so I have some questions.
- "install 4.5.2 via TWRP": Take /recovery out of 4.5.2 bin, zip the rest and then flash with twrp?
- "replace TWRP with the standard recovery": How? Not with TWRP, right? Think you said twrp won't write over itself.
- "trigger a regular update to 4.5.3 by putting the file on the device": Put 4.5.3 bin into /cache and update through settings?
(idk. Maybe you already posted this. If yes, sorry )
Thank you!
bibikalka said:
Wow, this sounds crazy. Did it ever work for you guys before you got root?
It just seems that if you replace everything by stock, the Video should work. A way to do this is to install 4.5.2 via TWRP, replace TWRP with the standard recovery, and then trigger a regular update to 4.5.3 by putting the file on the device. This way it'll be full 4.5.3 stock, updated via the proper procedures. This should be fairly quick to do.
Click to expand...
Click to collapse
It did work before root. But I don't remember if it ever worked with root.
I did 5.2, back to 4.5.3 via the adb method in the downgrade thread. Didn't work. Let upgrade to 4.5.4, still didn't work. I will try going back to 4.5.2, I didn't think of that. It sounds like from DoLooper's post it is beyond my capability. Can I just push 4.5.2 from 5.2 like I did before?
jgNewb said:
It did work before root. But I don't remember if it ever worked with root.
I did 5.2, back to 4.5.3 via the adb method in the downgrade thread. Didn't work. Let upgrade to 4.5.4, still didn't work. I will try going back to 4.5.2, I didn't think of that. It sounds like from DoLooper's post it is beyond my capability. Can I just push 4.5.2 from 5.2 like I did before?
Click to expand...
Click to collapse
Yep, if you downgrade from 5.2.0, and do a factory reset, you should have the full stock. That's actually simpler, than messing with TWRP. Everything is overwritten, I cannot think of what survives. Unless, there are some partitions where it "remembers" that you had root at some point.
Also, if Video works in 5.2.0, but not in stock 4.5.3 when you downgrade, I wonder why ...
---------- Post added at 01:00 PM ---------- Previous post was at 12:56 PM ----------
DoLooper said:
Wondered how to do this. Won't, but want to learn, so I have some questions.
- "install 4.5.2 via TWRP": Take /recovery out of 4.5.2 bin, zip the rest and then flash with twrp?
- "replace TWRP with the standard recovery": How? Not with TWRP, right? Think you said twrp won't write over itself.
- "trigger a regular update to 4.5.3 by putting the file on the device": Put 4.5.3 bin into /cache and update through settings?
(idk. Maybe you already posted this. If yes, sorry )
Thank you!
Click to expand...
Click to collapse
It looks like TWRP blocks recovery update (by disabling the scripts), so there is even no need to remove recovery files. It's possible to flash over recovery partition in TWRP, I tried this already, and it worked without errors. For testing, I flashed TWRP on top of TWRP. It runs from memory, so overwriting it is OK.
Getting back to full stock guide :
http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267
Sorry, I was MIA on my own topic here for awhile.
Glad to hear I wasn't the only one having the issue. I also went to the developer build, but I didn't try to get back to it to see if it works. I wonder if something there triggered the app to stop working? Regardless, I do know it was working before that because I watched a few shows when I first got the tablet. Ever since I went root upgrades, downgrades, etc. was when I had the problem.
So, similar to the other poster I worked with Amazon to get a new device. My question for anyone who has returned a Fire HD before is whether or not I need to get everything fully back to stock before I send to them or they'll "know" I rooted and voided warranty. If so I'll follow the guide posted elsewhere in this thread before I send it back. Good feedback, thanks for everyone's help.
Instant Video works on my rooted 5.2 tablet. No idea why doesnt work on 4.5.x, but i think ill just stay on this version and not bother with the return.
Heres the deal I have a kindle fire HDX 8.9" (Apollo) On firmware version 14.3.2.4_user_324002120 and was wondering if it is possible to unlock the bootloader.
Montisaquadeis said:
Heres the deal I have a kindle fire HDX 8.9" (Apollo) On firmware version 14.3.2.4_user_324002120 and was wondering if it is possible to unlock the bootloader.
Click to expand...
Click to collapse
Yes. Procedure involves a rollback to FireOS 14.3.1.x, installation of TWRP recovery, updating the native bootloader and then working through the unlock procedure (tedious for some). Once complete you can flash several HDX compatible roms including Nexus v4, CM11, two lollipop variants (CM12, SlipLP) or stick with FireOS provided you don't want to install gapps.
If needed I can post an outline and link to contributor supplied guides in a day or so ... or perhaps someone will jump in with the gory details. Or you also can browse through the forums. I'd wait for more info as it's pretty easy to brick your device (no recovery) if you go off script. In no case should you tweak build.prop or flash different versions of FireOS without specific instructions.
"If needed I can post an outline and link to contributor supplied guides in a day or so..."
This would be highly appreciated! Thanks!
fabische said:
"If needed I can post an outline and link to contributor supplied guides in a day or so..."
This would be highly appreciated! Thanks!
Click to expand...
Click to collapse
With 3.2.4 you could use the rollback images provided by @ggow. Check page 2 of this thread (page 1 is about 3.2.5/3.2.6 users, who can NOT use the rollback images!).
This would require rooting with HDX Toolkit and installing Safestrap 3.75. With Safestrap v3.7x note that factory reset means standard wipe only! Do NOT open advanced wipe menu, and especially do NOT wipe system! Keep WLAN off/flightmode active to avoid getting updated by Amazon, (re-)root and disable OTA via HDX Toolkit after downgrade, then flash TWRP, update 3.2.3.2 bootloader via TWRP, unlock bootloader and flash ROM of your choice - be sure do create a backup of your Fire OS in TWRP and move it to your PC before you flash any custom ROM!
Read the info, and ask first if you have questions, i.e. before you brick your HDX.
Cl4ncy said:
With 3.2.4 you could use the rollback images provided by @ggow. Check page 2 of this thread (page 1 is about 3.2.5/3.2.6 users, who can NOT use the rollback images!).
This would require rooting with HDX Toolkit and installing Safestrap 3.75. With Safestrap v3.7x note that factory reset means standard wipe only! Do NOT open advanced wipe menu, and especially do NOT wipe system! Keep WLAN off/flightmode active to avoid getting updated by Amazon, (re-)root and disable OTA via HDX Toolkit after downgrade, then flash TWRP, update 3.2.3.2 bootloader via TWRP, unlock bootloader and flash ROM of your choice - be sure do create a backup of your Fire OS in TWRP and move it to your PC before you flash any custom ROM!
Read the info, and ask first if you have questions, i.e. before you brick your HDX.
Click to expand...
Click to collapse
cheers mate! Just wonder how I can rollback my Apollo from 14.4.5.2 to 14.3.2.4 which is required to unlock the bootloader.
All the instructions that I can find state that you cannot rollback below 14.3.2.8....
fabische said:
cheers mate! Just wonder how I can rollback my Apollo from 14.4.5.2 to 14.3.2.4 which is required to unlock the bootloader.
All the instructions that I can find state that you cannot rollback below 14.3.2.8....
Click to expand...
Click to collapse
You can't. Any attempt to rollback below 3.2.8 will brick your device (anti-rollback protection). There is no way to unlock the bootloader on a device that has been upgraded (or began life) above 3.2.6.
However, with 4.5.2 you can root, install Safestrap v4 and then have a choice of CM11 or Nexus v4. Post back if you need assistance.
Davey126 said:
You can't. Any attempt to rollback below 3.2.8 will brick your device (anti-rollback protection). There is no way to unlock the bootloader on a device that has been upgraded (or began life) above 3.2.6.
However, with 4.5.2 you can root, install Safestrap v4 and then have a choice of CM11 or Nexus v4. Post back if you need assistance.
Click to expand...
Click to collapse
Thanks for the quick reply! Basically, I have constant issues with GAPPS running on my rooted 4.5.2 Apollo. For the last six months I have simply blocked any updates of Google Play Services (+chattr command). This was fine for a while, however, meanwhile apps like Google+ & Photos are working less than satisfying. I have updated Google Play Services today which eventually killed my Google Play Store. I managed to get back to the previous so-so state because I had backed up the Google Apps files with Titanium backup. Though my "simple" aim remains to have a working Gapps package on my system. However, the safestrap method, for some strange reason, is currently no option: when I install safestrap 4.1 and try to enter recovery the system goes into a black screen.
To cut a long story short my longterm plan now is to rollback to 3.2.8 again, upgrade to 4.5.2., root and reinstall Gapps manually (or is there a quicker option?). Possibly, Safestrap will work again then too.
Does this make any sense to you?
cheers!
fabische said:
THowever, the safestrap method, for some strange reason, is currently no option: when I install safestrap 4.1 and try to enter recovery the system goes into a black screen.
To cut a long story short my longterm plan now is to rollback to 3.2.8 again, upgrade to 4.5.2., root and reinstall Gapps manually (or is there a quicker option?). Possibly, Safestrap will work again then too.
Does this make any sense to you?
cheers!
Click to expand...
Click to collapse
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.
Thoughts:
- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image
- suggest you upgrade to 4.5.5 first. Based on limited feedback the risk of a minor FireOS v4 upgrade is less than rolling back.
- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)
- you should uninstall GAaps before upgrading/downgrading.
- there is increased risk if you previously changed permissions on system files to block OTA, etc.
- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.
- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
Davey126 said:
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.
Thoughts:
- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image
- suggest you upgrade to 4.5.5 first. Based on limited feedback the risk of a minor FireOS v4 upgrade is less than rolling back.
- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)
- you should uninstall GAaps before upgrading/downgrading.
- there is increased risk if you previously changed permissions on system files to block OTA, etc.
- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.
- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
Click to expand...
Click to collapse
Thanks, davey126. Before I set off for this next adventure: what is your guess that we will see an unlocked bootloader for current fire OS versions in the future? (this might save a lot of trouble)
fabische said:
Thanks, davey126. Before I set off for this next adventure: what is your guess that we will see an unlocked bootloader for current fire OS versions in the future? (this might save a lot of trouble)
Click to expand...
Click to collapse
Close to (effectively) zero. A new vulnerability would have to be discovered followed by an exploit to leverage it. 3rd gen devices have been discontinued; we don't even have root for 4th gen devices. I suspect few resources are being expended on this device. All the (Amazon) excitement surrounds the new $50 USD tablets that have been rooted and have a selection of custom roms. HDX is quickly becoming a beautiful dinosaur. Hi specs are out, cheap is in.
Davey126 said:
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.
Thoughts:
- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image
- suggest you upgrade to 4.5.5 first. Based on limited feedback the risk of a minor FireOS v4 upgrade is less than rolling back.
- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)
- you should uninstall GAaps before upgrading/downgrading.
- there is increased risk if you previously changed permissions on system files to block OTA, etc.
- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.
- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
Click to expand...
Click to collapse
Am I in serious trouble now?
I have followed to downgrade path by first updating (my 3rd Gen Apollo) from 4.5.2 to 4.5.4 and then to 4.5.5. Next was the 3.2.8-downgrade file:
mod-update-kindle-apollo-14.3.2.8_user_714328020.bin
However, starting this downgrade always results in a "Last update failed" message.
It turns out that there are two different 4.5.5 update files.
update-kindle-22.4.5.5_user_455001820
update-kindle-14.4.5.5_user_455001320
I have updated to the more recent "455001820" which actually refuses the downgrade to 14.3.2.8.
Seems I am stuck now?
Can I at least root update-kindle-22.4.5.5_user_455001820?
Thanks!
UPDATE:
Stuck where I was, I allowed my apollo to go online again. It found a newer 4.5.5 Fire os update and I let it download and run through. It now seems that I am on the latest version of 4.5.5. However, with this setup I am still unable to downgrade to 3.2.8. Every attempt to do so delivers a "Last update failed" message...
AFTERTHOUGHT
Could it make any difference if I factory reset the device (i.e. with regards to the downgrading process)? I have also noticed that I did not uninstall GAPPs before updating Fire OS to 4.5.5. However, I did manage to uninstall Google Apps and then also deleted google related files by searching with ES Explorer.
fabische said:
Am I in serious trouble now?
I have followed to downgrade path by first updating (my 3rd Gen Apollo) from 4.5.2 to 4.5.4 and then to 4.5.5. Next was the 3.2.8-downgrade file:
mod-update-kindle-apollo-14.3.2.8_user_714328020.bin
However, starting this downgrade always results in a "Last update failed" message.
It turns out that there are two different 4.5.5 update files.
update-kindle-22.4.5.5_user_455001820
update-kindle-14.4.5.5_user_455001320
I have updated to the more recent "455001820" which actually refuses the downgrade to 14.3.2.8.
Seems I am stuck now?
Can I at least root update-kindle-22.4.5.5_user_455001820?
Thanks!
UPDATE:
Stuck where I was, I allowed my apollo to go online again. It found a newer 4.5.5 Fire os update and I let it download and run through. It now seems that I am on the latest version of 4.5.5. However, with this setup I am still unable to downgrade to 3.2.8. Every attempt to do so delivers a "Last update failed" message...
AFTERTHOUGHT
Could it make any difference if I factory reset the device (i.e. with regards to the downgrading process)? I have also noticed that I did not uninstall GAPPs before updating Fire OS to 4.5.5. However, I did manage to uninstall Google Apps and then also deleted google related files by searching with ES Explorer.
Click to expand...
Click to collapse
I do not think the different subversion of 14.4.5.5 are significant in your situation although good to know they exist.
Yes - I would try a factory reset as others have reported success when update (rollback) files fail to process. This is one of the few cases where benefits of a factory reset outweigh risks. Make sure usb debugging is enabled as it may prove beneficial if your device has trouble restarting after the reset.
Davey126 said:
I do not think the different subversion of 14.4.5.5 are significant in your situation although good to know they exist.
Yes - I would try a factory reset as others have reported success when update (rollback) files fail to process. This is one of the few cases where benefits of a factory reset outweigh risks. Make sure usb debugging is enabled as it may prove beneficial if your device has trouble restarting after the reset.
Click to expand...
Click to collapse
Thanks, davey126. I have made factory reset on my device. I will try to downgrade later today. With regard to unlocking the 4.5.5. bootloader there has been an interesting development: a couple of days ago somebody managed to crack the 4.5.5 bootloader - unfortunately for the Kindle HD 7 (3rd Gen, 2013) only. What is your guess: could this prove useful for the HDX? Could this become a Safestrap alternative? Is it worth the wait?
http://forum.xda-developers.com/kin...ment/unlock-kfsowi-bootloader-unlock-t3262770
fabische said:
Thanks, davey126. I have made factory reset on my device. I will try to downgrade later today. With regard to unlocking the 4.5.5. bootloader there has been an interesting development: a couple of days ago somebody managed to crack the 4.5.5 bootloader - unfortunately for the Kindle HD 7 (3rd Gen, 2013) only. What is your guess: could this prove useful for the HDX? Could this become a Safestrap alternative? Is it worth the wait?
http://forum.xda-developers.com/kin...ment/unlock-kfsowi-bootloader-unlock-t3262770
Click to expand...
Click to collapse
Aside from sharing a generational identifier the two tabs have little in common. It's possible there is some similar code in the bootloader...but that seems unlikely. The real issue imo is the number people working on HDX vs HD variants. Only a few talented devs (I'm not one of them) tinkering with the former which is now discontinued.
Installing Safestrap does not decisively close the door to leveraging future BL exploits should one become available. I also think we may see some progress on a LP/MM rom for SS over time. Fingers crossed!
Davey126 said:
Aside from sharing a generational identifier the two tabs have little in common. It's possible there is some similar code in the bootloader...but that seems unlikely. The real issue imo is the number people working on HDX vs HD variants. Only a few talented devs (I'm not one of them) tinkering with the former which is now discontinued.
Installing Safestrap does not decisively close the door to leveraging future BL exploits should one become available. I also think we may see some progress on a LP/MM rom for SS over time. Fingers crossed!
Click to expand...
Click to collapse
Thanks again, Davey126. All is well now.
It all turned out as you predicted: downgrading 3.2.8 was possible after I made a factory reset on 4.5.5.
The rest was easy: upgrading back to 4.5.2 and rooting.
Your second prediction also proved correct: Safestrap 4.0.1 was not working properly on my fire os stock ROM. However, by going through this whole down- and upgrading process again Safestrap couldn't run smoother as it runs now. Finally, a working Safestrap opened the road (Hallelujah!!) to GET RID OF FIRE OS ONCE AND FOR ALL. I am now on rooted CM11 with GAPPS and starting to explore a new, liberated tablet! One more reason to celebrate!
fabische said:
Thanks again, Davey126. All is well now.
It all turned out as you predicted: downgrading 3.2.8 was possible after I made a factory reset on 4.5.5.
The rest was easy: upgrading back to 4.5.2 and rooting.
Your second prediction also proved correct: Safestrap 4.0.1 was not working properly on my fire os stock ROM. However, by going through this whole down- and upgrading process again Safestrap couldn't run smoother as it runs now. Finally, a working Safestrap opened the road (Hallelujah!!) to GET RID OF FIRE OS ONCE AND FOR ALL. I am now on rooted CM11 with GAPPS and starting to explore a new, liberated tablet! One more reason to celebrate!
Click to expand...
Click to collapse
Excellent - glad everything went as hoped. I suggest you glance through previous posts to make sure everything is configured to give you the best experience.
Enjoy your liberated HDX.
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
DroidDogg said:
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
Click to expand...
Click to collapse
Be happy 4.5.5.1 didn't take when SafeStrap recovery was installed; device would have bricked. Assume you used the Safestrap compatible variant of 4.5.2 (here). After flashing that (stock slot only; never use secondary slots in SS v4) reboot device and remove Safestrap recovery via SS app. Power down and boot into stock recovery via <power>+<vol-up> and perform a factory reset (you'll loose all apps/data). Reboot again and initialize FireOS. It should then accept OTA updates.
Be 100% sure Safestrap recovery is uninstalled prior to doing a factory reset.
Curious - why to you want 4.5.5.1? Offers no advantage over 4.5.2 if running custom ROMs. Nor will it automatically update to FireOS v5 as Amazon has no plans to release a v5 update for 3rd gen devices.
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
DroidDogg said:
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
Click to expand...
Click to collapse
DroidDogg said:
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
Click to expand...
Click to collapse
IDK - should work. You can try downloading the latest version of FireOS here; installation instructions here. Also verify OTA apk is installed and properly named (here).
It's likely 4.5.x is the terminal release of FireOS for 3rd gen devices; potential buyers will not be severely disadvantaged on 4.5.2.
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
As previously posted - IDK and I do not think anyone else does either. What I do know is every flash (some which appear questionable) presents another failure opportunity that could yield an unrecoverable device. Keep experimenting and posting results; others will learn from your efforts. Just recognize the risk and know when to say 'good enough'. Pushing from 4.5.2 to 4.5.5.1 buys you no additional capability/functionality/stability at this time.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
Do you checked if the DeviceSoftwareOTA.apk is there? (which @Davey126 mentioned above).
I was in the same situation and had to rename it back, which I'd renamed before as described in the OTA blocking tutorial. http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
mzk1 said:
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
Click to expand...
Click to collapse
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Davey126 said:
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Click to expand...
Click to collapse
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
mzk1 said:
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
Click to expand...
Click to collapse
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Davey126 said:
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Click to expand...
Click to collapse
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
mzk1 said:
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
Click to expand...
Click to collapse
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Davey126 said:
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Click to expand...
Click to collapse
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
mzk1 said:
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
Click to expand...
Click to collapse
Yep - that would be my choice too. Take note there are two Nexus builds, one for devices that have a 4.5.5.1 kernel, the other for older kernels. Try the former first as it as actively maintained and has a broader feature set. Links below:
old: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
new: http://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931