Amazon Instant Video not working - Fire HD 6 and 7 Q&A, Help & Troubleshooting

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.

Related

[Q] Removing Root to do OTA Lolipop?

As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.

[Q] Dev Edition 5.0.1 Want Root Only, No Recovery

I have converted my AT&T M8 to stock Dev Edition following this thread. Worked a treat.
http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
I'm going on a vacation and want to use my phone as a transfer spot for photos taken with a DSLR. To do that, I will need to be able to copy/move files from the camera's SD card onto my phone's SD using USB OTG.
I understand that if I keep the stock recovery, loader, etc and only achieve root, then I will be able to get any OTA that becomes available. I will also be able to use one of the methods to enable writing to the SD of the phone.
So, the question is, how to get root without changing anything that will impact the OTA ability?
Hope I was clear in what I have and what I'm looking for.
No Direction?
Nobody?
GHammer said:
Nobody?
Click to expand...
Click to collapse
I've never heard of anyone wanting just root, so I'm not sure. But if your bootloader is unlocked you can try TowelRoot and see if that works and just install SuperSu through the playstore.
Unique
Ha! I'm unique.
Actually, I like Sense, and Lollipop is fine. I just didn't loike all the crap AT&T forced onto the phone and Uber was the last straw.
So, I want to keep the phone 'stock' except for accessing the extrenal SD.
I'll give Towelroot a shot and see how it goes.
GHammer said:
Ha! I'm unique.
Actually, I like Sense, and Lollipop is fine. I just didn't loike all the crap AT&T forced onto the phone and Uber was the last straw.
So, I want to keep the phone 'stock' except for accessing the extrenal SD.
I'll give Towelroot a shot and see how it goes.
Click to expand...
Click to collapse
Maybe I'm just off base here, but once the bootloader is unlocked, can't you just fastboot TWRP recovery, install SU (zip) file via recovery, then fastboot stock recovery and end up with a stock rooted device? Or does Lollipop not allow this?
DanGeorges said:
Maybe I'm just off base here, but once the bootloader is unlocked, can't you just fastboot TWRP recovery, install SU (zip) file via recovery, then fastboot stock recovery and end up with a stock rooted device? Or does Lollipop not allow this?
Click to expand...
Click to collapse
Hmmmm, perhaps just booting a recovery and installing SU would work.
See why I asked?
Guess this will wait for the weekend now. Restoring a phone takes more time than I have and it looks like I'm in uncharted territory.
Again, my objective is to have an OTA acceptable system with root.
Thanks for the two ideas, and of course, I'm open to others.
GHammer said:
Hmmmm, perhaps just booting a recovery and installing SU would work.
See why I asked?
Guess this will wait for the weekend now. Restoring a phone takes more time than I have and it looks like I'm in uncharted territory.
Again, my objective is to have an OTA acceptable system with root.
Thanks for the two ideas, and of course, I'm open to others.
Click to expand...
Click to collapse
I had a rooted device (4.4.2) and when I wanted the OTA to 4.4.4, I kept the root, but re-fastbooted the stock recovery so that the OTA would work. It kept my root (I think), and then I just re-installed TWRP so that I could still do backups..
I hope that someone with more knowledge than I will chime in if I'm wrong (or right).
DanGeorges said:
I kept the root, but re-fastbooted the stock recovery so that the OTA would work.
Click to expand...
Click to collapse
This is what I would suggest. There may be other ways (root without custom recovery). But I know for certain that the following will work: flash TWRP, flash SU or SuperSU to root. Than flash back to stock recovery.
You will be on stock recovery, have root, and should not impact OTA (provided all system files are also stock and not altered by root).
You can also try to fastboot boot TWRP (and then flash SU/SuperSU) without actually flashing TWRP. I'm not certain this will work, but I think it does under LP. I think something on 4.4.4 broke this ability, but then it came back.
Weekend Project
I will try the boot TWRP method first, and if that fails, I'll flash TWRP, get root, then go back to stock recovery.
This is now just an exercise to see which method works as the stock File Manager reads the USB and can copy files to the SD. I had not tried since 4.4.4. but did yesterday and it works for any kind of file.

7'' (Thor) Stuck on rooted 13.3.2.1

I modded my HDX with root and Xposed. I want to make the manual update from 3.2.1 to 4.5.2 , but the bin update files i tried (3.2.8 and 4.5.2) didn't work. It said that they are invalid.
Do I have to edit the build props for this? Seems strange to me, because those are real updates not downgrades.
I did a factory reset, but 4.5.2 update still is "invalid". (got it from here: http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813)
Why do you want to update to 4.5.2?
You'll lose your chance to unlock the bootloader and install TWRP.
EncryptedCurse said:
Why do you want to update to 4.5.2?
You'll lose your chance to unlock the bootloader and install TWRP.
Click to expand...
Click to collapse
It was due to the fact that my touchscreen isn't working correctly and I wanted to try to fix it with an update.
For the update process everything worked (creeping through various update processes) and I am now on rooted CM11 with xposed and everything I wanted (using safestrap v4).
Sadly though a the old problem occured like always: The touchscreen wasn't fixed at all.
I'd see this thread as closed and will start another one about the tochscreen problem as it's a whole new topic.
EDIT: If somebody is interested which way I went for the update or about the broken display see my new post: http://forum.xda-developers.com/kin...-7-touchscreen-partly-broken-display-t3308106

[Help Needed] Flashed 4.5.2 cant update update failed

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

[Fire HD 6] Downgrade to 4.5.3 to root, went back to 5.3.1 and lost TWRP

Hi guys,
first of all I want to salut everybody here as I am completely new to the Android world and that's indeed the best resource online. Thanks for that.
Now my big problem. As from the title, I downgrade my Fire HD 6 (4th gen) to 4.5.3 with adb sideload to root it with kingroot and everything went fine. I have then installed TWRP and everything went fine. I have then used TWRP to go back to 5.3.1 and I lost root and recovery. I managed to gain my root privileges back but as for the recovery not a chance. I tried to install TWRP again with dd from adb shell (as I can su) but once again nothing. Checking with fastback getval all, I do have a locked bootload:
Is this the reason why TWRP doesn't run anymore?
If yes, how can I unlock it back?
Is this what's meant with boot loader loop?
Thank you all in advance!
Edit 1:
maybe cuber.py may help but I can't find this file.
Edit 2:
ok found the tools here https://forum.xda-developers.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689
Edit 3:
I tried with cuber.py but the tool can't sign the img because it's not ANDROID. That's what it says. Now I am really stuck. Help please!
LM
I was in the exact same situation, so maybe I can offer some insight. I also have an HD 6 running 5.3.1 that I have downgraded to get root then upgraded a few times. Let me say that I am still learning too, and am by no means an expert but I can try to help.
As far as losing root, i'm not sure as that never happened to me. Did you flash the most up-to date SuperSu with TWRP or did you just answer yes when TWRP prompted you if you wanted root privileges? Flashing a SuperSu through TWRP will give you the SuperSu icon on your home screen once you upgrade back to 5.3.1, whereas just letting TWRP grant root access won't. You will still have root, but without the icon there's no direct control over it (at least not that I could find) so it's still there, just hidden.
My TWRP also replaced by the stock recovery upon updating back to 5.3.1. As far as I know, this is unavoidable. I believe it's as you suspect and is due to the 5.3.1 bootloader being locked. This would also explain why the process for rooting 5.3.1 is so involved as opposed to just using something like Kingroot. I also don't think there's anyone still doing active development on the HD 6 / HD 7.
If you really want to have both root and TWRP, you could try downgrading to an older OS that still has the feel of 5.3.1. I'm not sure about any other versions, but 5.1.1 is rootable via Kingroot (which should mean that it has an unlocked bootloader) and has the same exact UI as 5.3.1. So if you're feeling adventurous try downgrading to 4.5.3, installing TWRP, and upgrading to 5.1.1 instead of 5.3.1 (just be sure to block automatic updates!) and see if TWRP is still active. If so, root with Kingroot and you're good. If you still don't have TWRP, at least you're no worse off than you were.
If you do try this, please post your results here. I might try this myself. I am currently running stock. As I said, I went through the process a few times. For some reason SuperSu was causing erratic behavior in some of my apps and when I tried to switch my SU app to kingroot I lost root completely. I really didn't care about root enough to repeat the whole process again, but if I could keep TWRP it might be worth it. Anyway, good luck.
P.S. You may need to try rooting with Kingroot several times for it to work. I know for a fact that it can root 5.1.1 since I've done it on my own HD 6 when I was running 5.1.1. I'm not sure why it fails, but keep trying and eventually it will get root access. You may have to try 6 or 7 times but eventually it will work.
I went back and re-read this thread more carefully:https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and it turns out that TWRP doesn't play well with any 5.X.X bootloaders. Oh well, I was kind of hoping my idea would work. It turns out that you can use TWRP on your current rooted 5.3.1, but only on a temporary basis. Refer to the above thread post #2 for instructions. Basically, you put the correct 5.3.1 bootloader on your device then run AutoTWRP which will flash 4.5.3 bootloaders and TWRP for you. Reboot into recovery and you have your TWRP. You can then do whatever you want. The downside is that since you are running a 4.5.3 bootloader you can't get back into your OS, only TWRP. And once you flash your 5.3.1 bootloader to get back into your OS, TWRP no longer works. I know it's a pain in the arse having to connect to a PC and run a batch file every time you need to use TWRP, but at least it's a sort of workaround.

Categories

Resources