Database Users

4.4.2 (KOT49H) update fails on rooted device

Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.

Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse

amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/

Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred

Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.

I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..

I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.

[Q] Can someone help me resolve a root access issue?

I have a Advent Tegra Note 7
Upgraded to kitkat and OTA 2.4.1
Used Tomsgt supertool 2.4.1 tool to root, installed TWRP (and made a backup image of my freshly installed system)
I've since added some games and apps and spent a fair bit of time customizing the system, but when I attempt to run Titanium Backup it tells freezes when "asking for root rights" so I ran "root checker basic" from playstore, which tells me I don't appear to have proper root access..
Here's a break down of what I've done, I've tried to keep it conscise...
I have tried installing a SuperSU, SuperUser and SU Update fixer, Also reinstalling the SuperSU-v1.94.zip using both cwm and twrp... Still no proper root access.
Ideally I'd like to try some other things to get root access before reflashing and having to reinstall my apps and settings, can anyone help or suggest anything else I could do.? I can't think of anything I could of accidentally done to break root access, this is still quite a clean system just setup in the past two days.
P.S.When using the supertool impacter tool and scan for usb driver I get a "no such device" error, even though the device is listed in the previous screens.. also I suspect the correct drivers are there as ADB seems to work fine

they flashing SuperSU-v1.99r4.zip from http://download.chainfire.eu/447/SuperSU/. I haven't had issues with root via either method.
If that fails you can use the n7root.img which is downloadable here: https://github.com/linux-shield/shield-root/blob/master/root_tn7.img?raw=true then go into fastboot mode and then type fastboot boot root_tn7.img. DO NOT USE FASTBOOT FLASH BOOT with this image as it will make it bootloop, just use fastboot boot command.

SOLVED
Thanks for the pointers hacktrix2006.. I tried supersu-v1.99r4.zip also v2 no luck. Had a quick look for how to get into fastboot mode.. couldn't access it from the bootloader.. so decided to take a backup image and restore to stock kitkat 4.4.2 via tomsgt latest tool 2.4.1 including doing Wipe data. then reinstalled TWRP then applied root.... AND noticed a screen saying something like ROOT ACCESS MAY BE FAULTY.. WOULD YOU LIKE TO FIX THIS.. I also think there was a warning about "be careful this action is irreversable" - I suspect the previous time I hadn't understood this properly and selected NO !! Anyway this time I said yes and now have ROOT YAY!
Now I start a re setup of the system and installation of apps etc.. I guess it's often a bit smoother 2nd (or 3rd 4th etc) time around
OK thx again for the encouragement, plus now I have a little more experience to offer someone else who may be struggling in this area.

no problem!

AFTV stick FW 5.2.1.0 Build 550145120

Hello Fire TV lovers
First to my situation. My AFTV sticks is running FW 5.2.1.0 550144920 and is rooted by Kingo Root. Even after doing an factory reset the stick stays still rooted without running again or installing the Super User app. When doing a factory reset there will be shown an screen at first start after reset with something like "optimizing system..." and runs about 3-5 minutes before the first screen is showing where you can connect the remote.
As some users got already the update for the new 5.2.1.0 build I am still waiting for it. But yesterday I believe I have found the update files in the "./cache" directory... The name is "update-montoya_montoya-550144920-to-550145120". But AFTV sticks still says theres nothing new... I have done a factory reset and the file is still in the cache directory but the update is still not installed. Any ideas?
The file is only about 5.5 mb and when extracting it there is not much more than some patches to the first 5.2.1.0 build. So it seems that this is not an full fw update but only a little patch. That maybe the reason why it is still rootable...???
Does anybody have other AFTV stick update files? Maybe any user got an full update file to newest build?
@rbox do you have some ideas what we can do with this? maybe installing an old fw by replacing the "new" file?
And does someone know if full updates are different from device to device? So not the same file for AFTV 1, AFTV 2 and AFTV stick?
Here is the files if someone is interested... --> https://www.dropbox.com/s/j3esv7xefzk35be/update-montoya_montoya-550144920-to-550145120.bin?dl=0

cuki3r3k83bln said:
Hello Fire TV lovers
First to my situation. My AFTV sticks is running FW 5.2.1.0 550144920 and is rooted by Kingo Root. Even after doing an factory reset the stick stays still rooted without running again or installing the Super User app. When doing a factory reset there will be shown an screen at first start after reset with something like "optimizing system..." and runs about 3-5 minutes before the first screen is showing where you can connect the remote.
As some users got already the update for the new 5.2.1.0 build I am still waiting for it. But yesterday I believe I have found the update files in the "./cache" directory... The name is "update-montoya_montoya-550144920-to-550145120". But AFTV sticks still says theres nothing new... I have done a factory reset and the file is still in the cache directory but the update is still not installed. Any ideas?
The file is only about 5.5 mb and when extracting it there is not much more than some patches to the first 5.2.1.0 build. So it seems that this is not an full fw update but only a little patch. That maybe the reason why it is still rootable...???
Does anybody have other AFTV stick update files? Maybe any user got an full update file to newest build?
@rbox do you have some ideas what we can do with this? maybe installing an old fw by replacing the "new" file?
And does someone know if full updates are different from device to device? So not the same file for AFTV 1, AFTV 2 and AFTV stick?
Here is the files if someone is interested... --> https://www.dropbox.com/s/j3esv7xefzk35be/update-montoya_montoya-550144920-to-550145120.bin?dl=0
Click to expand...
Click to collapse
1) Do you have updates disabled (router or through ADB)? If so enable them and try again.
2) You are rooted why not erase file from ./cache and let it downloade it again, make sure updates are enabled.
3) Is no way to install an older firmware without having recovery, rbox did not release recovery for firestick as of yet.
4) updates are different from unit to unit so do not do install anything release so far or you will brick your stick.

hmmh ok have done nothing but file was removed and everything is like was before... no update done yet...
ota updates are not disabled...

Factory reset won't get rid of root. You have to uninstall it via the SuperSU app using the 3 dots in the right hand corner to remove the keep root backups.

No need for removing root Just wondering why I recieve the update file for newer 5.2.1.0 build but it wont be installed...
If I have root or not is not really interesting for me because I use my AFTVS for BS and RetroArch only... Rooting it was just for fun and is not much usefull as long as rbox does not provide us with recovery and prerooted fw

Before installing an incremental software update, the Fire TV and Fire TV Stick check the integrity of system and recovery. On a rooted device, that integrity check fails and the update is not installed. That is why the incremental update @cuki3r3k83bln found in /cache was just sitting there and never got installed. Normally, after the integrity check fails, the device will then download a full version of the software update. The full update will include a complete copy of system and recovery so it doesn't care about the current state of the device. If installed, the full update will wipe out root (and TWRP if present).
For whatever reason, version 5.2.1.0_550144920 is not downloading the full update of 5.2.1.0_ 550145120 after the integrity check fails. I noticed the same thing happen on a rooted FIre TV 2. I got the Fire TV 2 to download the full 5.2.1.0_550145120 by downgrading to the pre-rooted 5.0.5.1 ROM. On 5.0.5.1, it did the usual download of the incremental update, then failed the integrity check, then download the full 5.2.1.0_550145120 update.
I don't know if the old Fire OS 3 process of manually upgrading/downgrading the OS still works on Fire OS 5. I haven't tried it, but you can try to downgrade to a stock full version. If you downgrade successfully, I'm sure it will then update to 5.2.1.0_550145120. Here are full updates if you want to try:
5.0.5 (537174420) Full
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
5.0.5.1 (537175520) Full
https://amzdigital-a.akamaihd.net/o...te-kindle-montoya-54.5.3.7_user_537175520.bin
Personally, I would suggest just sitting and waiting. Rbox is working on TWRP and pre-rooted ROMs for the Stick. When that's released, you'll be able to downgrade safely if you want. Or, more likely, Amazon will figure out why the Stick is not downloading the latest full update and fix it before then.
Lastly, if you connect via ADB and run the command
Code:
adb shell pm clear com.amazon.device.software.ota
it will cause the device to forget that it failed the integrity check. This will make it re-download the incremental update and redo the integrity check. I would do this once a day in hopes that Amazon fixes the issue preventing the full update from downloading.

AFTVnews.com said:
Before installing an incremental software update, the Fire TV and Fire TV Stick check the integrity of system and recovery. On a rooted device, that integrity check fails and the update is not installed. That is why the incremental update @cuki3r3k83bln found in /cache was just sitting there and never got installed. Normally, after the integrity check fails, the device will then download a full version of the software update. The full update will include a complete copy of system and recovery so it doesn't care about the current state of the device. If installed, the full update will wipe out root (and TWRP if present).
For whatever reason, version 5.2.1.0_550144920 is not downloading the full update of 5.2.1.0_ 550145120 after the integrity check fails. I noticed the same thing happen on a rooted FIre TV 2. I got the Fire TV 2 to download the full 5.2.1.0_550145120 by downgrading to the pre-rooted 5.0.5.1 ROM. On 5.0.5.1, it did the usual download of the incremental update, then failed the integrity check, then download the full 5.2.1.0_550145120 update.
I don't know if the old Fire OS 3 process of manually upgrading/downgrading the OS still works on Fire OS 5. I haven't tried it, but you can try to downgrade to a stock full version. If you downgrade successfully, I'm sure it will then update to 5.2.1.0_550145120. Here are full updates if you want to try:
5.0.5 (537174420) Full
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
5.0.5.1 (537175520) Full
https://amzdigital-a.akamaihd.net/o...te-kindle-montoya-54.5.3.7_user_537175520.bin
Personally, I would suggest just sitting and waiting. Rbox is working on TWRP and pre-rooted ROMs for the Stick. When that's released, you'll be able to downgrade safely if you want. Or, more likely, Amazon will figure out why the Stick is not downloading the latest full update and fix it before then.
Lastly, if you connect via ADB and run the command
Code:
adb shell pm clear com.amazon.device.software.ota
it will cause the device to forget that it failed the integrity check. This will make it re-download the incremental update and redo the integrity check. I would do this once a day in hopes that Amazon fixes the issue preventing the full update from downloading.
Click to expand...
Click to collapse
Surely if you manage to downgrade a stick using the method you have mentioned you can stop it upgrading by not using the official charger (plug usb into tv etc).
If this is possible it would be quite good for many users of the stick who would like to be on 5.0.5 to then be able to use the home button click double click feature in firestarter 3.2.3 ? i know i certainly would but unsure if the method would brick the device ?

Downgrade is possible
@AFTVnews.com WOW!!! Big Thx Downgrading worked perfectly!!!
What have I done? Very simple...
1. Downloaded the 5.0.5.1 FW from AFTVnews.com link above and then followed the tutorial he has linked...
2. Renamed the filename to update.bin
3. Pushed the update.bin via adbLink from Mac to AFTV stick
4. Opened ADB Shell via adbLink on Mac and moved update.bin from "sdcard" to "cache" directory...
Code:
su
cd /sdcard
mv ./update.bin /cache/
5. Then done some more steps from AFTVnews guide...
Code:
cd /cache/recovery
echo --update_package=/cache/update.bin > command
adb reboot recovery
Few seconds after this the recovery process started and some minutes later my AFTV stick rebooted back and was running 5.0.5.1 without problems. I startet ADB Shell again and the "su" command was not working anymore so my device has been "derooted". Some minutes later I checked the update status and the stick started downloading newest 5.2.1.0 build. After rebooting and waiting some minutes everything worked fine and then I have done a factory reset and now I am using a clean and fresh 5.2.1.0 AFTV stick
So lets say: FW 5.0.2.1 can be downgraded
I don't know if this helps someone but maybe someone would like to use older versions or we could run an prerooted room without custom recovery or or or...

cuki3r3k83bln said:
@AFTVnews.com WOW!!! Big Thx Downgrading worked perfectly!!!
What have I done? Very simple...
1. Downloaded the 5.0.5.1 FW from AFTVnews.com link above and then followed the tutorial he has linked...
2. Renamed the filename to update.bin
3. Pushed the update.bin via adbLink from Mac to AFTV stick
4. Opened ADB Shell via adbLink on Mac and moved update.bin from "sdcard" to "cache" directory...
Code:
su
cd /sdcard
mv ./update.bin /cache/
5. Then done some more steps from AFTVnews guide...
Code:
cd /cache/recovery
echo --update_package=/cache/update.bin > command
adb reboot recovery
Few seconds after this the recovery process started and some minutes later my AFTV stick rebooted back and was running 5.0.5.1 without problems. I startet ADB Shell again and the "su" command was not working anymore so my device has been "derooted". Some minutes later I checked the update status and the stick started downloading newest 5.2.1.0 build. After rebooting and waiting some minutes everything worked fine and then I have done a factory reset and now I am using a clean and fresh 5.2.1.0 AFTV stick
So lets say: FW 5.0.2.1 can be downgraded
I don't know if this helps someone but maybe someone would like to use older versions or we could run an prerooted room without custom recovery or or or...
Click to expand...
Click to collapse
Awesome. I'm glad it worked out. Thanks for reporting back that downgrading still works.

Is this usable for the Fire TV Box Gen. 1 to downgrade and make it rootable?
Gesendet von meinem E6653 mit Tapatalk

Why not? Try it out... Have tried it just for fun and it worked ? Would do it for you but have the stick only

cuki3r3k83bln said:
Why not? Try it out... Have tried it just for fun and it worked �� Would do it for you but have the stick only
Click to expand...
Click to collapse
i tried the steps posted yesterday and couldnt get it to work, any chance you could post the exact steps you used ? id like to downgrade my firestick to 5.05 to get back the firestarter features. thanks

cuki3r3k83bln said:
Why not? Try it out... Have tried it just for fun and it worked ? Would do it for you but have the stick only
Click to expand...
Click to collapse
I think I first need the Firmware files ver. 5.05 for AFTV, not AFTV Stick. Can someone help me out?
Gesendet von meinem E6653 mit Tapatalk

sconnyuk Well you have to download the 5.0.5.1 from ATVnews his link, rename it to update.bin and then push it via adbfire on mac or pc (or you can use apps2fire on android devices)... I did simply that and then I did open the adb shell and simply typed what I have written... Your device has to be rooted via Kingo Root to access the cache directory... What have you done or what errors did you get?

i get
cannot stat 'update.bin : No such file or directory
after i try push update.bin to /cache
im using windows 10 64bit
---------- Post added at 08:55 PM ---------- Previous post was at 08:51 PM ----------
my stick is 5.2.1.0 rooted with super user (kingo) and trying to push the 5.0.5 file AFTVnews posted.

Hmmh did you try to use adbLink and then you simply need to select "sdcard" as destination folder for uploading it? sorry dont know how and where you uploadet your file...

I have adb drivers installed on windows pc. i have followed all steps posted by AFTVnews until i get to adb push update.bin /cache and i get the error cannot stat 'update.bin' : No such file or directory
Im now going to try adblink with your added commands and see what i get.

Ok, tried the way you did it with the adblink tool and it worked
Thanks for posting your success as i would of just gave up.
This is good to know and i guess theres alot of people who have updated from 5.0.5 and lost firestarter features who would like them back.
All my apps are intact, i did have to re-run kingoroot to get root.
I have disabled updates straight after booting to my downgraded 5.0.5 stick. (pm disable com.amazon.device.software.ota), thanks cuki3r3k83bln and AFTVnews, im sure there is alot of people who will use this info to do as i just did.

Next project is how to mount a good working NFS folder as directory into filesystem OR using external usb disk with y-otb-cable but that will be done when we got a prerooted rom because I dont trust kingoroots exploit not much

cuki3r3k83bln said:
Next project is how to mount a good working NFS folder as directory into filesystem OR using external usb disk with y-otb-cable but that will be done when we got a prerooted rom because I dont trust kingoroots exploit not much
Click to expand...
Click to collapse
Im wanting to try replacing Kingo roots SuperUser app with chainfires SuperSu.
I know a few people have tried this without success on 5.2.1.0 im wondering if its different on 5.0.5 ?
Im fairley sure that a messed up stick that wont boot because of changed su files is recoverable as i recovered my stick after deleting su files in root folder. Others have had non booting sticks from using various methods to change to SuperSu and with the way ive pointed out to them of getting it back up and running it seems they have had success also.
The way to do it is to plug the stick into a pc/laptop and run kingo roots windows tool to root it, this in turn replaces the modified su files and gets the stick back up and running.
Have you any idea on a version of Chainfires Su that could work ?

Fire TV 3 (needle/stark): TWRP

Disclaimer: If you go through with this and encounter issues, I (or the others here) will try to help you, but the risk is all yours.
I see a few posts mentioning TWRP for the AFTV3, so here it is for the pendant (needle): link. Extract twrp.img from the archive, copy it to /sdcard, and flash as follows:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/recovery
Note: You will need a Y (OTG) cable to connect a mouse and/or a keyboard.
I have tested this on the pendant (needle), but it should also work for the cube (stark).
You can also boot or flash this from fastboot (reboot bootloader or run from aml_reboot in the root thread) if you so desire.
To enter recovery from a terminal running on the AFTV3:
Code:
reboot recovery
To enter recovery from ADB:
Code:
adb reboot recovery
For those interested, here's what I did:
-- Rather than build from scratch, I used an existing TWRP for Amlogic's S905X as the base. Quite a few of them are here.
-- You can't just use a random TWRP and expect it to work on the AFTV3 (due to hardware and partition mismatch). I first replaced (and repacked) the ramdisk with that from needle's boot image (using magiskboot).
-- While TWRP booted up, USB OTG was absent. Without OTG, TWRP is not of much use (w/o OTG, I used openrecoveryscript as a workaround). Turns out the random TWRP images lack the correct USB modules. I extracted the correct modules from the AFTV3, copied them to the TWRP image, and everything works.
If something doesn't work, please post here.

Great job, i flashed it from fastboot.
adb reboot bootloader (or install a app that will reboot into bootloader)
fastboot flash recovery C:\(this TWRP version)
Seems to be functional.
the old Firestick 1's you could control the mouse from a adb shell. I dont know how to make that functional for those without a OTG.

Confirmed, it works on the cube (stark) as well...

That's really a great job. As stated here: https://forum.xda-developers.com/showpost.php?p=78958467&postcount=165 I (hopefully soft) bricked my pendant trying to install Google services. Now it just reboot at the white amazon logo. Ordered a OTG cable to test TWRP but was trying random versions. Now this confirmed woirking version is a life saver to me. Now I just have to find a way to remove the offending google service apk.
Thanks again.

Sorry to bother again.
I still have my pendant in bootloop (bad google service installation).
Tried OTG cable but using it doesnt let me go in fastboot mode and I dont know how to navigate in recovery without it.
Since now the pendant is rooted and can recover OTA files maybe my next attempt could be to try to find a .bin rom file and flash it using fastboot?
If so does anyone know if there is such a file yet (pre rooted version should be great)?
Thanks.

Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.

Michajin said:
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Click to expand...
Click to collapse
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.

2WhlWzrd said:
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
Click to expand...
Click to collapse
Would the update fail anyway if I replaced Amazon recovery with TWRP?

Michajin said:
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Click to expand...
Click to collapse
No, TWRP would be over written by an OTA update.

2WhlWzrd said:
No, TWRP would be over written by an OTA update.
Click to expand...
Click to collapse
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...

Michajin said:
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Click to expand...
Click to collapse
There is a difference between writing outside of TWRP and with TWRP, it's hard to overwrite something that's doing the writing.
If you read in the first post of the tank rooting thread, the author explicitly states: "Only ever flash boot/recovery images using TWRP",
anything outside of that will not be root aware. Better to be safe, than sorry.

How may I get the "su". It said, I don't have permision.

eSephiroth said:
How may I get the "su". It said, I don't have permision.
Click to expand...
Click to collapse
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.

2WhlWzrd said:
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
Click to expand...
Click to collapse
If you didn't root the device, how can you have superuser?

eSephiroth said:
If you didn't root the device, how can you have superuser?
Click to expand...
Click to collapse
I assumed you were already rooted. Since you are not, start here:
[ROOT] Rooting the FireTV Cube and Pendant with FireFU
Anything from firmware 6.2.5.8 and up, the exploit has been patched.

This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.

eSephiroth said:
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
Click to expand...
Click to collapse
This isn't the root thread. But yeah, it's the only thing we've got for these devices, so we make it work

Hi,
I was able to recover my Pendant using a finally working OTG cable and using mouse with your TWRP and finally delete the offending google.gsm app so thanks a lot for that.
The only thing I noticed is that adb doesn't work for me once booted into TWRP (I wanted to use adb backup to backup bigger partitions directly to my PC). Is that just my issue or it's happening for everyone?
Thanks.
Pino.

moving it to the right place.

anyone have interest in the update files? If i turn on my update, download the update, but before rebooting copy the .bin file to a different folder, delete from the cache folder then disable updates again. I can share the file if anyone wants it to see if we can modify to keep root and update? I am thinking i might download it, move it and change it to a .zip, then reboot into TWRP. Flash the update and flash magisk before a reboot. Anyone have thoughts about risk of a BRICK?

Please help me with an OTA update

Hi everyone. I'm new here on XDA and this is my first post so if I'm doing this wrong, please let me know below or provide a link if my problem has already been solved, thank you.
I have an s8+(SM-G955F, dream2ltexx/dream2lte), running 9.0.0. I have both, TWRP(3.3.1) and Magisk(latest) + edxposed(for what is worth). I am also running a custom kernel A2N. I received a week ago an OTA update and I would like to apply it. This is my first ever OTA update on a rooted device so I read a ton of posts and tutorials in the past few days, also backed up everything using TWRP. From what I understood(and please feel free to correct me if I'm wrong or show a better solution) I need to first install the default recovery image, lose TWRP, unroot, do the OTA and after that, reinstall TWRP and Magisk(I think I also need to return to stock kernel, not sure).
Important: I would very much like to not factory reset my phone if this is possible.
Now, I have a few questions:
1. Where can I get my default recovery.img ? (I tried to find it on https://desktop.firmware.mobi/device:468 but they don't have anything for android 9)
2. Do I also need to get and install my default kernel ? If so, where can I also get it ?
2. After I flash the recovery.img what is the best thing to do with Magisk ? (completly uninstall or just restore image ?)
3. After everything is done, will flashing TWRP require to remount the partitions ?(because that will also mean I have to factory reset at some point)
4. It would also be super helpful if you could provide me a link from where I can download OTA updates as zip files(if there exist such a place). The version that I need is: G955FXXS8DTC1
I cannot thank you enough for everything and sorry for the long post
Hope you have a safe, beautiful day !
P.S. I already tried to do the OTA update after backup. It tried to flash it throw TWRP and, of course, it failed(error: 7)