Develop Bugs

Unable to revert to stock rom =[

I was messing around with ROM's one day and saw one that said, "Flash to 1.47 without having to reroot" or something along those lines. I tried it and it worked perfectly. Today I tried to undo the root and flash back to stock using the "[How To] [FIXED!!] Unroot and return to stock" post on Android Central forums.
However, halfway through the update, it fails. I want to return back to stock so I can flash the new Froyo update that is out but I don't know what I did so nothing will update.
I even tried to update directly to Froyo. No go.
I did a NAND restore to my 1.32 build. Still gives me an error.
Is there a way to go back to the Stock bootloader and stock recovery? Maybe that might help?
If there is any other information I can give please let me know.

sekigah84 said:
I was messing around with ROM's one day and saw one that said, "Flash to 1.47 without having to reroot" or something along those lines. I tried it and it worked perfectly. Today I tried to undo the root and flash back to stock using the "[How To] [FIXED!!] Unroot and return to stock" post on Android Central forums.
However, halfway through the update, it fails. I want to return back to stock so I can flash the new Froyo update that is out but I don't know what I did so nothing will update.
I even tried to update directly to Froyo. No go.
I did a NAND restore to my 1.32 build. Still gives me an error.
Is there a way to go back to the Stock bootloader and stock recovery? Maybe that might help?
If there is any other information I can give please let me know.
Click to expand...
Click to collapse
this should be q and a!
turn your phone on while holding down on volume.
can you see option for recovery? what happens when you click it?

message for noobs: NEVER try to unroot to upgrade if you want to keep root. always WAIT until someone posts a ROOTED version for your eager beaver.
now why were you trying to unroot?
when in doubt, you can always start over by following instructions here.

Sorry. Didn't know about the Q+A thing. Guess I need a mod to move it.
I hit recovery and it says:
Android system recover
use vol-keys to nvaigate. power-key to select
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Flash zip from sdcard
-Wipe
-Partition sdcard
-Other
-Power off

sekigah84 said:
Sorry. Didn't know about the Q+A thing. Guess I need a mod to move it.
I hit recovery and it says:
Android system recover
use vol-keys to nvaigate. power-key to select
-Reboot system now
-USB-MS Toggle
-Backup/Restore
-Flash zip from sdcard
-Wipe
-Partition sdcard
-Other
-Power off
Click to expand...
Click to collapse
Ok, things aren't totally screwed yet.
Go here:
http://forum.xda-developers.com/showthread.php?t=740667
Follow the instructions and install a rooted version of Froyo. Why go back to stock? This is exactly what you'd be installing with stock, but you have root.

tatnai said:
message for noobs: NEVER try to unroot to upgrade if you want to keep root. always WAIT until someone posts a ROOTED version for your eager beaver.
now why were you trying to unroot?
Click to expand...
Click to collapse
I wanted to undo it so I can test the stock HTC non-rooted rom. Which didn't flash over my rooted 1.47 build. So I thought that if I revert to stock it should flash. Thats where I'm stuck at currently ><
I did a data, cache, dalvik wipe. Restored back to a 1.32. Got the OTA update. Downloaded and tried to install and got the following error:
Build: RA-evo-v1.7.0.1
Finding update package...
Opening update package...
Verifying update package...
E:No signature (56 files)
E: Verification failed
Installation aborted.
I also can't use the RUU to get back to 1.32 or 1.47

Saturn2K said:
Ok, things aren't totally screwed yet.
Follow the instructions and install a rooted version of Froyo. Why go back to stock? This is exactly what you'd be installing with stock, but you have root.
Click to expand...
Click to collapse
Will do. Sorry for the slight lag in replies. 5 minute newbie limit on posts;
I'll try this and see if it works.

sekigah84 said:
I wanted to undo it so I can test the stock HTC non-rooted rom. Which didn't flash over my rooted 1.47 build. So I thought that if I revert to stock it should flash. Thats where I'm stuck at currently ><
I did a data, cache, dalvik wipe. Restored back to a 1.32. Got the OTA update. Downloaded and tried to install and got the following error:
Build: RA-evo-v1.7.0.1
Finding update package...
Opening update package...
Verifying update package...
E:No signature (56 files)
E: Verification failed
Installation aborted.
I also can't use the RUU to get back to 1.32 or 1.47
Click to expand...
Click to collapse
IF you manage to get back to stock and IF you install the unrooted HTC OTA, you will lose root until/unless the devs come up with a way to root it. Is that what you're actually trying to do?

smw6180 said:
IF you manage to get back to stock and IF you install the unrooted HTC OTA, you will lose root until/unless the devs come up with a way to root it. Is that what you're actually trying to do?
Click to expand...
Click to collapse
Yep. I want full stock.

I just want to know that I will be able to return to stock for repair purposes. Its scaring the crap out of me atm not being able to return to stock lol

[Q] Trouble with updating OTA to JB

I'm currently using the stock rom from Google (4.0.4) after updating it from 4.0.1 which originally shipped with my device (manually, not OTA). Just yesterday I decided to update my phone to JB through the OTA update. It downloads perfectly fine but when it reboots into the installation, I get the error with the android mascot and red exclamation mark.
-- Install /cache ...
Finding update package ...
Opening update package ...
Verifying update package ...
Installing update ...
Verifying current system ...
assert failed: apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.0/by-name/radio:12583168:8b7209e8c3a6d73254ad92069aabe693beffd6bd:12583168:47b1799049e32ef2c0746ca716f5277a83768b96")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I'm pretty sure it manages to download perfectly fine since the file is still in my cache (filename is f946a4120eb1.signed-yakju-JR003C-from-IMM761.f946a412.zip) Anyone able to help me with this?

spaceinvad3rs said:
I'm currently using the stock rom from Google (4.0.4) after updating it from 4.0.1 which originally shipped with my device (manually, not OTA). Just yesterday I decided to update my phone to JB through the OTA update. It downloads perfectly fine but when it reboots into the installation, I get the error with the android mascot and red exclamation mark.
I'm pretty sure it manages to download perfectly fine since the file is still in my cache (filename is f946a4120eb1.signed-yakju-JR003C-from-IMM761.f946a412.zip) Anyone able to help me with this?
Click to expand...
Click to collapse
You do not have the XXLA2 radio flashed. You need to flash that before applying the update.

Thanks for that. I've also got another question. I currently can't access clockwork mod through the recovery menu, after updating it to 4.0.4 I wasn't able to access it anymore. I've tried the rom manager from the play store but it says something that I don't have permission. I think I forgot to install the super user when I initially installed the update to 4.0.4.

I agree, you have to be careful with each rom's compatibility. 4.0.4 brought with it new radios which I believe most if not all jb roms are based on. You can flash the new radios after rooting and unlocking the device. If you manually root the phone, you'll know if you successfully pushed su to your sd card.
Sent from my Galaxy Nexus using xda app-developers app

spaceinvad3rs said:
Thanks for that. I've also got another question. I currently can't access clockwork mod through the recovery menu, after updating it to 4.0.4 I wasn't able to access it anymore. I've tried the rom manager from the play store but it says something that I don't have permission. I think I forgot to install the super user when I initially installed the update to 4.0.4.
Click to expand...
Click to collapse
1) every ota update disables root access.
2) every ota update places two files on your device that re-flash the stock recovery every time you boot your phone.
3) the android laying on its back with the exclamation point IS the stock recovery.
4) you need to flash cwm, flash the su package, then rename/delete this file: /system/etc/install-recovery.sh and you are all set.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] OTA JSS15R While Rooted

Currently trying to update my Nexus 7 to JSS15R (8MB OTA that may have helped multitouch issue?)
I am running rooted stock ROM, unlocked bootloader etc. Current build number is JSS15Q.
I've heard the newer versions of SuperSU have the OTA fix built in. I haven't been able to update though. I noticed there was an update and I went to update my Nexus 7. It went to update like it should, but I got an error and it never changed.
Flashed the OTA fix thinking it would help. No.
Forced OTA update by stopping Google Framework. No.
Flashed SuperSU 1.65 and tried to update again. No.
Any suggestions on what I should do? Manually flash the update without loosing root or an data?

Did you reflash the ota after you flashed supersu?
What was the error message?

sfhub said:
Did you reflash the ota after you flashed supersu?
What was the error message?
Click to expand...
Click to collapse
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.

When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.

church said:
When I did the j to q update while rooted the ota had an error as well. I had to install the full q rom from google. (I'm stock with root and I changed the system font) But this time around when I got the r ota I double checked what version supersu was runing and its at 1.65. I applied the r ota with no errors.
Click to expand...
Click to collapse
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.

datallboy said:
Yeah I'm running 1.65 currently, but the update won't show up anymore. Check for updates and there's nothing.
Click to expand...
Click to collapse
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.

church said:
If its like the last issue with J to Q. You are updated but it doesn't show the name change in system. I could be wrong. It should have already been downloaded to your tablet. Check with a root explorer to find the ota zip or download the R ota found somewhere on this forum and manually flash it. I'm glad I didn't have to mess with anything this time around.
Click to expand...
Click to collapse
I found a zip for the ota update, don't remember where, but should I be able just to flash it with TWRP without loosing anything?

It will lose the option to blend milkshakes

church said:
It will lose the option to blend milkshakes
Click to expand...
Click to collapse
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.

Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.

church said:
Oh you're using twrp? Disregard what I said. I'm coming from stock with stock recovery and rooted.
Click to expand...
Click to collapse
Stock recovery is on my device. I'm temporarily booting TWRP with the Nexus Toolkit so I can flash things.

datallboy said:
I read the new SuperSU versions have the OTA fix built in which allows OTA update.
When I initially went to update before everything, it rebooted then just came up with the "open android guy" with an error. Not sure what it exactly said, but I ran into the problem when I updated to JSS15Q.
I updated to JSS15Q by flashing the SuperSU OTA update fix with temporary TWRP. It then went through no problem. I followed that same method this time, but it didn't work.
Click to expand...
Click to collapse
Next time you have an error with stock recovery (android fallen down) press/hold power, then press/release VolUp, then release Power.
This will show you the error log.
As to your current problem, if your unit won't download and notify you about JSS15R download it by hand and place in your virtual sdcard, then temporary boot into tarp and choose install, selecting the ota zip.
---------- Post added at 08:58 PM ---------- Previous post was at 08:55 PM ----------
datallboy said:
Not asking for sarcasm, just solutions. Will I lose root or any data? Or is it just like OTA update if I do it manually.
Click to expand...
Click to collapse
Install the ota update.zip, then before reboot, immediately install supersu.
Do it that way and you won't lose root.

Forced OTA and it failed. I had already flashed the superSU.zip before
If you can't read this is the log...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check ("/system/build.prop" [numbers and letters]
E: Error in /cache/(update file.zip)
(Status 7)
Installation aborted.
Any way to manually flash the update? Because SuperSU OTA isn't working.

So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.

Guhrasoh said:
So, you modified the build.prop, restore your backup of the original and it will work. Or flash the full factory image.
Click to expand...
Click to collapse
Now that you mention it I tweaked it with PimpMyRom. I'll take that off and try to update.

I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.

datallboy said:
I am a bit late, but I tried fixed my build.prop to its original state and I still can't OTA update...
I noticed on stock recovery there's an option to update with ADB. Is there an update file I can use to just manually install the update? I know the JSS15R update didn't do much, but I would like to know for future reference and when Android 4.4 is released.
Click to expand...
Click to collapse
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.

sfhub said:
The same OTA update.zip you used before is used to do sideload in adb as well.
You'll also get the same errors if you have modified files.
If you post the errors, they can be diagnosed.
If you modified a lot of files, sometimes it is easier using the factory images.
Click to expand...
Click to collapse
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.

datallboy said:
Status 7 error, the log is posted in one of the above posts. I use "PimpMyROM" for a short while, which modifies the file. I deleted all the tweaks that went into the build.prop.
Click to expand...
Click to collapse
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.

sfhub said:
Unless you are very careful with your edit or made a backup, you need to get the real file. When you edit, even if you have an extra space left over, the sha1 checksum check will fail.
Click to expand...
Click to collapse
I'll probably just backup apps + data and use JSS15R factory image. Made the mistake of not making a backup of my build.prop.
Good thing it's a Nexus Device!

[Q] failed to update rooted nexus 7 2013 from 4.4.3 to 4.4.4

Hi everyone,
I posted this thread in General Discussion Q&A and then found this forum, so I posted once again in hoping to get some solution.
I have updated my rooted Nexus 7 2013-LTE using the method described here from 4.4.2 to 4.4.3 succesfully:
liliputing.com/2014/06/upgrade-nexus-android-4-4-3-without-losing-root.html
I used SuperSU and Xposed framework was temporarily uninstalled. However, when I tried the same procedure to update from 4.4.3 to 4.4.4, following errors are appearing:
file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/debuggerd" has unexpected contents.
"/system/bin/debuggerd" has unexpected contents.
E:Error in /cache/0c3dd9bfb71f2b8437be322e6cab5832ce2b4d35.signed-razorg-KTU84P-from-KTU84L.0c3dd9bf.zip
(Status 7)
Installation aborted.
It seems that file debuggerd is somehow changed (my guess by stickmount app). Is it correct that I have to replace the one installed in my /system/bin/ with the original one to continue updating to 4.4.4? Does anyone have the original debuggerd file nexus 7 2013-lte 4.4.3?
Thx u all

hood2ts said:
It seems that file debuggerd is somehow changed (my guess by stickmount app). Is it correct that I have to replace the one installed in my /system/bin/ with the original one to continue updating to 4.4.4? Does anyone have the original debuggerd file nexus 7 2013-lte 4.4.3?
Thx u all
Click to expand...
Click to collapse
Did you try uninstalling stick mount first? That should put the original debuggerd back.

Did you flash back to the stock recovery before accepting the OTA?

meekrawb said:
Did you try uninstalling stick mount first? That should put the original debuggerd back.
Click to expand...
Click to collapse
I tried uninstalling stickmount, but the debuggerd file is still unchanged. The OTA update is still failed. Anyway, thank u for suggesting an idea.

nhizzat said:
Did you flash back to the stock recovery before accepting the OTA?
Click to expand...
Click to collapse
Nice thing to update using method described in:
liliputing.com/2014/06/upgrade-nexus-android-4-4-3-without-losing-root.html,
is that you move forward with what you have. Will try flashing back to the stock revovery if that simpler method not working .

Not sure why anybody would make a guide on how to update without losing root. Worried about losing data and settings? Sure. Worried about losing root? Never.
If you want simple, you can either use adb sideload with the stock recovery or flash the OTA in a custom recovery like you would any other zip file. If you find you don't have root, flash SuperSU.zip again.

Finally, I used NRT to flash to 4.4.4 using system image with option not to wipe data. Many thanks to nhizzat and meekrawb.

Rooted 2nd gen fire tv being auto updated to 5.0.5.1 and losing root!

I have rooted 2 boxes now to 5.0.5 and after having them fully up and running updates blocked etc. I leave and come back to find that the device has updated to 5.0.5.1 and has lost root. It also no longer has team win recovery on it anymore. How is this even possible? The second one I watched automatically do some update in twrp I didn't get to see what was all on the screen but when it booted the root was gone. I checked adb the updates are still turned off but appears that the recovery was wiped and none of the root stuff works like google play, xposed framework.. nothing.

I would say that you didn't block updates using the best possible method using a terminal to enter pm disable com.amazon.device.software.ota. My rooted box is still rooted. In fact when I click on check for software updates it throws an error message which is just what you want.
I hear the new update method is using SSL and going over HTTPS which can't be blocked using other methods as the contents are encrypted.
You do know you can still use the rooting method that uses an A to A USB cable to root again? You'll just have to install rooted 5.0.5 to do it and stay on 5.0.5. I have a Mac guide for this on my site. marksmods.com
As far as you seeing and update happen and TWRP doing something, it was probably that screen that appears saying Running OpenRecovery Script with the message Patching system image unconditionally which is what happens when updating.

PhoenixMark said:
I would say that you didn't block updates using the best possible method using a terminal to enter pm disable com.amazon.device.software.ota. My rooted box is still rooted. In fact when I click on check for software updates it throws an error message which is just what you want.
I hear the new update method is using SSL and going over HTTPS which can't be blocked using other methods as the contents are encrypted.
You do know you can still use the rooting method that uses an A to A USB cable to root again? You'll just have to install rooted 5.0.5 to do it and stay on 5.0.5. I have a Mac guide for this on my site. marksmods.com
As far as you seeing and update happen and TWRP doing something, it was probably that screen that appears saying Running OpenRecovery Script with the message Patching system image unconditionally which is what happens when updating.
Click to expand...
Click to collapse
But I did use the terminal pm disable updates, like I said it still says that updates are blocked even after it ran this update. But shouldn't the recovery stop it from updating even if it does download the latest update? And yes it did say patching system unconditionally but it did this all on its own while I was not touching the device. I also just tried rerooting it and it seems twrp was never wiped but now it will not read any usb device so I cannot install any rooted zips. Is it possible they have found a way to bypass the recovery?

danknasty said:
But I did use the terminal pm disable updates, like I said it still says that updates are blocked even after it ran this update. But shouldn't the recovery stop it from updating even if it does download the latest update? And yes it did say patching system unconditionally but it did this all on its own while I was not touching the device. I also just tried rerooting it and it seems twrp was never wiped but now it will not read any usb device so I cannot install any rooted zips. Is it possible they have found a way to bypass the recovery?
Click to expand...
Click to collapse
If you had pre-rooted ROM 5.0.5_r1 or 5.0.5_r2 installed, recovery wouldn't have stopped the update. TWRP would install the OTA update just fine. I have personally confirmed this. It wasn't until 5.0.5_r3 that rbox disabled stock recovery.
That said, I haven't actually tried to see what happens if 5.0.5_r4 (latest version) downloads an OTA update. I'll test it in a few minutes and report back.
UPDATE:
Well, I just finished testing it out and it turns out TWRP will install the OTA update on the latest 5.0.5_r4 ROM. So blocking updates is mandatory and you shouldn't rely on TWRP to reject the installation. Even though @rbox disabled the stock recovery, it looks like TWRP is flexible enough to accept Amazon's update.
Specifically, I rooted a 5.0.5.1 Fire TV 2 with rbox's method and installed the 5.0.5_r4 pre-rooted ROM. I did not block updates in any way and the box received the 5.0.5.1 ota update, which incidentally was the full update and not an incrimental one. The box rebooted into TWRP and installed the ota update within TWRP. I recorded the whole thing with my capture card, if you want to see it @rbox.

AFTVnews.com said:
If you had pre-rooted ROM 5.0.5_r1 or 5.0.5_r2 installed, recovery wouldn't have stopped the update. TWRP would install the OTA update just fine. I have personally confirmed this. It wasn't until 5.0.5_r3 that rbox disabled stock recovery.
That said, I haven't actually tried to see what happens if 5.0.5_r4 (latest version) downloads an OTA update. I'll test it in a few minutes and report back.
UPDATE:
Well, I just finished testing it out and it turns out TWRP will install the OTA update on the latest 5.0.5_r4 ROM. So blocking updates is mandatory and you shouldn't rely on TWRP to reject the installation. Even though @rbox disabled the stock recovery, it looks like TWRP is flexible enough to accept Amazon's update.
Specifically, I rooted a 5.0.5.1 Fire TV 2 with rbox's method and installed the 5.0.5_r4 pre-rooted ROM. I did not block updates in any way and the box received the 5.0.5.1 ota update, which incidentally was the full update and not an incrimental one. The box rebooted into TWRP and installed the ota update within TWRP. I recorded the whole thing with my capture card, if you want to see it @rbox.
Click to expand...
Click to collapse
But I AM blocking the updates. In fact I was able to reroot downgrade to the preroooted 5.0.5 r4.... updates blocked again through the pm disable command. I even tried updating before I went to sleep and got an error. I wake up to an updated and unrooted 5.0.5.1 again. And again still showing me that updates are blocked even after this update.... sorry guys I just realized I was using the fire os 3.0 method of disabling as I was using the function in the adbfire program. I am going to try again by manually typing these adb commands hopefully this time it does not auto update. I guess we did stumble across a new finding however from this.

AFTVnews.com said:
If you had pre-rooted ROM 5.0.5_r1 or 5.0.5_r2 installed, recovery wouldn't have stopped the update. TWRP would install the OTA update just fine. I have personally confirmed this. It wasn't until 5.0.5_r3 that rbox disabled stock recovery.
That said, I haven't actually tried to see what happens if 5.0.5_r4 (latest version) downloads an OTA update. I'll test it in a few minutes and report back.
UPDATE:
Well, I just finished testing it out and it turns out TWRP will install the OTA update on the latest 5.0.5_r4 ROM. So blocking updates is mandatory and you shouldn't rely on TWRP to reject the installation. Even though @rbox disabled the stock recovery, it looks like TWRP is flexible enough to accept Amazon's update.
Specifically, I rooted a 5.0.5.1 Fire TV 2 with rbox's method and installed the 5.0.5_r4 pre-rooted ROM. I did not block updates in any way and the box received the 5.0.5.1 ota update, which incidentally was the full update and not an incrimental one. The box rebooted into TWRP and installed the ota update within TWRP. I recorded the whole thing with my capture card, if you want to see it @rbox.
Click to expand...
Click to collapse
So this is something I didn't even think would happen, but it makes perfect sense. The update gets downloaded and it writes the /cache/recovery/command file to tell recovery to update. It reboots in to recovery. Stock recovery is disabled so the box reboots normally. TWRP starts for bootmenu and says "Hey, there is a command file present, let me run it". And then it installs the update. I'll disable that and release it with a prerooted 5.0.5.1.

rbox said:
So this is something I didn't even think would happen, but it makes perfect sense. The update gets downloaded and it writes the /cache/recovery/command file to tell recovery to update. It reboots in to recovery. Stock recovery is disabled so the box reboots normally. TWRP starts for bootmenu and says "Hey, there is a command file present, let me run it". And then it installs the update. I'll disable that and release it with a prerooted 5.0.5.1.
Click to expand...
Click to collapse
Awesome thanks for making it idiot proof for people like me.

@rbox, thanks for your efforts.
I just got my Fire TV a week ago, used kingroot, then installed recovery, then installed the prerooted 5.0.5 all using @AFTVnews.com guide and had everything set up nicely but woke this morning to find the new update installed and wiped everything.
Anyone know if I can use the same kingroot & recovery method on the new ROM to get TWRP back so I can install the prerooted ROM again?

Swifty said:
@rbox, thanks for your efforts.
I just got my Fire TV a week ago, used kingroot, then installed recovery, then installed the prerooted 5.0.5 all using @AFTVnews.com guide and had everything set up nicely but woke this morning to find the new update installed and wiped everything.
Anyone know if I can use the same kingroot & recovery method on the new ROM to get TWRP back so I can install the prerooted ROM again?
Click to expand...
Click to collapse
kingroot doesn't work in 5.0.5.1. You need to use the method with the A to A usb cable. It's all documented in my install recovery post here and aftvnews.com

Thanks very much, will check out the guides and get the soldering iron out as I don't think I have USB A - A

Swifty said:
Thanks very much, will check out the guides and get the soldering iron out as I don't think I have USB A - A
Click to expand...
Click to collapse
Exact guide you need is here: http://www.aftvnews.com/firetv2root

Glad you posted this question. Great stuff here. Sounds like my blocking method should protect me from the update then...