yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] TimmyP:
You want home button back on 6.2.7.3, and that is all you want? Root with this tutorial, uninstall\reinstall ftvxlauncher and your launcher, when you open ftvxlkauncer to select a default it will nag you about secure_settings, follow that link and enter that line with pc adb connection ($ pm grant de.codefaktor.ftvlaunchx android.permission.WRITE_SECURE_SETTINGS). Everything is as it was.

(just in case I also flashed Amazon_Launcher_Replacement.zip in twrp, magisk 20.4, and I have Fire TV settings.apk installed it looks like I didnt complete the steps for FireTV settings tho, never removed Amazon launcher, its still there. I do not believe any of this was necessary tho in getting FTVX to work again. No modules or anything in Magisk yet)

Oh and delete otacerts.zip. Do it with ES file explorer on your device natively. (adb install es.apk while device is in FireOS)

EDIT: YOU CANNOT USE WOLF LAUNCHER! (7/4/2020) it wont be detected by the native launcher picker. Use TV Launcher 3! This is a must at this point.
[Fire TV Original Android Development] SweenWolf:
Can you enlist the steps that you followed?
[Fire TV Original Android Development] SweenWolf:
Hey guys, need some info here.

I want to flash twrp to my stick to test my apps and i don't need root access, i don't care about that. I need to know if updating via FireOS ( from Update section) will cause any bootloop, I have no problem with that if i can reflash TWRP or unlock bootloader again.

And also if if breaks something in the System apps like prime video.

The FireOS downloads updates and install them either via the system, those i think are the updates to the /data partition, and i think updating will not cause any problem.

The second one requires recovery to install the updates (to the system partition). I have no experience with OTA updates with TWRP thats why I am asking. So will the recovery flash the update or will it throw the error because of meta-inf or will it break TWRP.

I just need TWRP access and not want Magisk, I read in some post that they needed magisk otherwise it was stuck in bootloop, can i please have a clarification on that. Thanks.
[Fire TV Original Android Development] Pretoriano80:
IIRC, TWRP will fail to install the update, no matter if it's OTA or FullOTA, so it shouldn't cause a bootloop.

As for system updates, those are installing just fine because most (if not all) of them are just apps updates (apk).

Also, TWRP has a "protection" mechanism that it won't flash "critical" partitions (bootloader, etc) even if those are included in the update package.
[Fire TV Original Android Development] SweenWolf:
Thanks for the info
[Fire TV Original Android Development] TimmyP:
Followed rooting guide.

Boot as normal.

Uninstall FTVLaunchX and custom launcher.

Reboot into Twrp flash magisk 20.4, Amazon_Launcher_Replacement.zip (pretty sure this line is optional)

Reboot into 6.2.7.3 and just fresh installed launcher, then FTVLaunch.

Open FTVLaunch it will nag about secure_settings. Exit app.

From PC adb shell connection: $ pm grant de.codefaktor.ftvlaunchx android.permission.WRITE_SECURE_SETTINGS

FTVLaunch works as normal. Still have Amazon Launcher etc.
[Fire TV Original Android Development] SweenWolf:
Not sure what fixed that, i have flashed TWRP without any system modification but not working, because it cannot, it would be so nice if you can pinpoint.
[Fire TV Original Android Development] 0815hoffi:
I Think com.amazon.firehomestarter is the point you must search
[Fire TV Original Android Development] SweenWolf:
Well, i cannot reach to that point, if i do something in twrp its not affecting the system, when i open /system/priv-app in twrp ten it is there, if i open the folder in system then its not there, reboot to recovey it appears again.

Flashing magisk is making my boot animations hang, not in bootlop but in freeze frame, have to check any other problems
[Fire TV Original Android Development] TimmyP:
I Just did it on debloated 6.2.7.3, had to restart a couple times. It defintely works. It will popup asking you to select a home launcher. It *may* be the Amazon_Launcher_Replacer working in tandem. So have that flashed.

Uninstall launcher and especially FTVx. Clearing storage doesnt work they must be reintalled. Then after about 2 reboots it started working.
[Fire TV Original Android Development] dcarvil:
I have a vague recollection of seeing a post on a similar problem. They finally found there were two system folders. TWRP was using one folder, but android was using the other folder. Sorry, I don't remember how they wiped both folders.
[Fire TV Original Android Development] SweenWolf:
Hey, long time.

So you have magisk zip for this?

I don't want to mess my stick because my thinking capability is exhausted right now.

---------- Post added 28-08-2020 at 12:03 AM ---------- Previous post was 27-08-2020 at 11:58 PM ----------

I will think about it when i start thinking properly again, anyway, good to know its working for you
[Fire TV Original Android Development] dcarvil:
Yes, I am using Magisk 20.4 available at https://github.com/topjohnwu/Magisk/releases/tag/v20.4 I think I had to adb install the Magisk Manager APK after installing Magisk, but it has been a while since I did it, so could be wrong.

One caveat with Magisk on the firestick 4k is to update it only by flashing from TWRP, never update from Magisk Manager or any other method besides TWRP.
[Fire TV Original Android Development] SweenWolf:
The problem is after flashing Magisk my stick is not booting up, the bootanimation sound is choppy. Only way is to restore boot.img.

Glad i took backup of whole system

Update:

Got it working,

When backing up system via TWRP, it backs up system.ext4 and system_image.emmc.

Don't restore system.ext, just restore system_image.emmc (System Image)

This will solve the two system partition problem and magisk problem, if anyone is having
[Fire TV Original Android Development] dcarvil:
It would be interesting to know if flashing a patched boot.img allows you to boot. You could get a patched image from one of the rooted roms in this forum, or patch your own on your phone (if Magisk is on your phone).

That's the standard procedure for rooting my phone - patch the boot image with Magisk, then flash the patched image.
[Fire TV Original Android Development] SweenWolf:
I got magisk working, and dual system partition problem is also solved.
[Fire TV Original Android Development] dcarvil:
For backups I do system image, vendor image, data, and boot. Restoring system and/or vendor partitions is not recommended.

Glad you found the problem.
[Fire TV Original Android Development] SweenWolf:
Its important to me to find and debug the problems on my own, that thing helps in future. :)
[Fire TV Original Android Development] Seattleweather:
never booted into TWRP

Mine has 6.7.2.3 ROM. and it never booted into TWRP. adb devices showed unauthorized. Anyone is having the same problem? Please help. Thanks!
[Fire TV Original Android Development] SweenWolf:
Have you entered this?

./fastboot-step.sh

After first command?

TWRP opens when you have already connected OTG on boot.
[Fire TV Original Android Development] SweenWolf:
This is great, every uodate whether OTA or FullOTA, they are installing just fine, i rollbacked to 7.1 and it downloaded 7.3 I thought it will not update the software but it opened the recovery (TWRP) and flashed 7.3 right away, everything is working as it should, thanks again.
[Fire TV Original Android Development] Seattleweather:
I did entered ./fastboot-step.sh after it's done. I can confirm that su is there and rooted. however, TWRP was not installed at all. I assume that I can install it since it's rooted now. Will TWRP 3.4.0-0 work with firestick 4K? How do I use adb to push and install it?

Thanks!
[Fire TV Original Android Development] SweenWolf:
Do not flash any other recovery

Pull the twrp from kamakiri.zip

adb reboot bootloader

fastboot flash recovery twrp.img

fastboot oem reboot-recovery
[Fire TV Original Android Development] Seattleweather:
TWRP will show up even without OTG attached when boot up? Just curious if mine was already installed, but for some reasons not shown up. Is there way to check where TWRP installed in the system file? Thanks a lot for your quick reply SweenWolf.
[Fire TV Original Android Development] SweenWolf:
adb reboot recovery
[Fire TV Original Android Development] SpaceMan5:
I unlocked my firestick and installed a pre-rooted ROM and now it will bootloop and is no longer detected by my computer. Can this be fixed or is it just dead?
[Fire TV Original Android Development] SweenWolf:
Attach OTG and plug the power, click cancel and wipe everything and try again.
[Fire TV Original Android Development] TimmyP:
No dont attach OTG when connecting to PC!

---------- Post added at 02:28 PM ---------- Previous post was at 02:26 PM ----------

Worst case scenario you just do the root again, get to recovery\fastboot. Magisk will root for you just flash it.
[Fire TV Original Android Development] SpaceMan5:
How do i do the root again without being able to connect to it on my pc to use adb commands? Will getting an otg cable and using a keyboard allow me to force it to boot to recovery?
[Fire TV Original Android Development] TimmyP:
Connect to PC, dont use OTG.

OTG stops PC from recognizing Fire Stick

PC should always detect it when you are rooting.
[Fire TV Original Android Development] SpaceMan5:
It doesn't get detected when i plug it into my pc anymore, I unlocked it got to twrp and installed the latest prerooted rom and ever since it just bootloops and will not get picked up when it's plugged into my pc.
[Fire TV Original Android Development] TimmyP:
the bootrom will when you root with linux. Just one cable no otg when connected to PC.
[Fire TV Original Android Development] SpaceMan5:
I've tried it with the linux bootrom and windows neither will pick it up as plugged in anymore.
[Fire TV Original Android Development] TimmyP:
Then its done.
[Fire TV Original Android Development] SpaceMan5:
Would it be possible to force it to recovery with a keyboard, wipe then hook it up to a pc to re flash a rom?
[Fire TV Original Android Development] SweenWolf:
Removed.
[Fire TV Original Android Development] zeroxia:
-----

EDIT:

Never mind, I realized the cable was a "charging only" one, and after replacing it with a data cable, it's working like before.
[Fire TV Original Android Development] TimmyP:
You can also interact with TWRP via adb shell.

eg (while in twrp).

adb push flashme.zip /sdcard/ (push zip/rom/whatever to stick)

adb shell twrp install /sdcard/flashme.zip (flash it)

adb reboot
[Fire TV Original Android Development] this.guy.lol:
How to book iso?

I am not familiar with how to do any of this can someone please hold my hand and tell me how to go about this. I have all the files needed on the USB I have no idea how to proceed. Please help me.

I have the ISO on USB I have the needed files on the USB. I have the iso set to UEFI from my Windows 10 computer. I used Rufus to do this.

I keep on getting errors when I try to load this from the boot menu it takes forever and then there's a error and then it says login root automatic login and then it just does what it does

---------- Post added at 07:35 AM ---------- Previous post was at 07:08 AM ----------

Do I need to redo Rufus or what exactly do I need to do in what format do I need to have the iso in? DD BIOS UEFI? I JUST REALLY WANT TO GET THIS THING ROOTED IT'S THE ONLY THING I HAVE IN MY HOUSE THAT IS NOT ROOTED AND IT'S BUGGING ME EVER SINCE I UPDATED TO THE LATEST FIREOS SORRY FOR THE CAP LOCKS.
[Fire TV Original Android Development] SweenWolf:
Use etcher

https://www.balena.io/etcher/

Use legacy BIOS instead of UEFI to boot.
[Fire TV Original Android Development] TimmyP:
Just a heads up. If you are trying to switch launchers you cant use Wolf, use TV Launcher 3. Wolf is NOT selectable in the native launcher picker after you play with a fresh install (of FTVlaunch), permission regrant, reboot. Give it a shot.

*You can also use ATV launcher if you wanna keep it like Wolf!
[Fire TV Original Android Development] SweenWolf:
https://xdaforums.com/showpost.php?p=83215549&postcount=381

You can select Wolf as default, and I modded ATV with some bug fixes, its not only ATV with a logo changed :( :(

(Clear your facts)
[Fire TV Original Android Development] Darkfact5249:
Launchers

Helllo,

How can i update the wolf launcher?
[Fire TV Original Android Development] SweenWolf:
https://xdaforums.com/attachment.php?attachmentid=5074645&d=1596687827

Download and update.
[Fire TV Original Android Development] TimmyP:
Yeah because you updated it. 15.1 did not identify as an android launcher, so it wouldn't invoke the launcher selection menu. I got lucky with it because I was using TV Launcher 3. Anyways....

Thank you for updating. Great launcher much nicer to look at than ATV.
[Fire TV Original Android Development] Darkfact5249:
Helllo i am flashing my second stick 4k but i do a dumb mistake. i dont select the correct permission for mantis.

and now i got denied.

mantis: /$ su

Permission denied

for com.android.shell

how can i fix it?
[Fire TV Original Android Development] TimmyP:
reflash magisk?
[Fire TV Original Android Development] dcarvil:
Open Magisk Manager, click the hamberger icon in upper left corner, superuser, enable Shell.
[Fire TV Original Android Development] Darkfact5249:
i try to erease the amazon launcher. but when i do the recovery command firestick go offline. its suppose to be in recovery.

[root@sysresccd ~]# adb reboot recovery

[root@sysresccd ~]# adb devices

List of devices attached

192.168.0.5:5555	offline

any advice?
[Fire TV Original Android Development] SweenWolf:
The stick will be in recovery, look at your TV screen.

WiFi and bluetooth doesn't work in recovery, so no wireless adb or FireTV remote will work.

So, ike i already told,

Use USB cable to connect to PC to enter the commands (in recovery or in system)

Use mouse to manually do things on the stick itself (in recovery)

Echo your commands to the recovery (in system)

Your choice.
[Fire TV Original Android Development] Bertonumber1:
Hey guys,,

After fkin my brand new fire tv 2 (couldn't get passed rpmb downgrade)

I dug out my 4k and successfully got it rooted,, was a dash to disable ota updates and the first time I had to reflash Magisk.

Now on 6.2.6.8 rooted with amazon.tv.launcher uninstalled completely (disabled and uninstalled)

Managed to disable fire tv launcher and keep atv launcher on spite of recent events blocking custom launchers.

After I disabled updates and wrote pm grant permissions with ftvlaunchx and atv launcher pro set as default within.

I reflashed the pre rooted rom again without wiping /data

This means now that when home button is pressed it stays with the atv launcher and doesn't go to that Amazon gunk.

Really happy with this and thanks to K4y0z + xyz rbox Sus_i. And everyone who's skill and input makes this happen for everyone.

Your work is always appreciated guys and its a pleasure learning the ropes here on the forums.

Cheers again

---------- Post added at 02:37 AM ---------- Previous post was at 02:20 AM ----------

[MENTION=7352779]SweenWolf[/MENTION]

Hey m8 you've done really well with your work lately. I know how much you have been working on this launcher thing. This might be useful I dunno.

I flashed pre rooted 6.2.6.8

Disabled and uninstalled ota updates and a couple of other scallywag type pests..

I wrote ftvlaunchx app to pm grant permissions.through remote adb.

Installed atv launcher pro

Set that as default within launchx

Disabled com.amazon.tv.launcher

Rebooted to TWRP

Wiped everything except /data

reflashed 6.2.6.8

rebooted (somehow lost root)

Reflashed Magisk

Rebooted system

Pressed home button to make sure settings menu was there in atv launcher (to access fire tv settings menu)

double checked com.amazon.tv.launcher was still disabled (it was)

Then hit home button and atv launcher remains reboot after reboot.. Press home button at your will no fire tv launcher

Perhaps you maybe be able to develop something with this as I don't have the skill I think I just kinda fluked it.

Anyway thanks again..

Regards

Ps I want to delete the com.amazon.tv.launcher. Apk do you think it will be safe to do so????
[Fire TV Original Android Development] SweenWolf:
You can delete it without any problems, the thing is you won't be able to access settings,

You need su if you are rooted and can use Launcher replacement

Or if you are not rooted, you need to use adb, which I'm currently working on,

But network adb is buggy on firestick 4k, so if yiu are doing this kinda thing and don't want to loose precious time, always authorize your pc for adb debugging and always keep the ADB debugging on, if without settings app you are not able to access network settings also, (if you are not connected, and firestick refuses to do so, happens sometimes)

Connect stick via usb and adb should again be fine.

Otherwise you are good to go.

What I have done with my stick

Unblocked bootloader

Flashed TWRP, done many tests with system.

Used magisk with many modules, at the end wiped everything, flashed stock 6.2.7.1 stock update, set it up.

As i also used OTG for some storage TWRP would create a delay, and i figured i longer needed TWRP because I don't intend to mess with system, because many people can't, so after few days, flashed the stock boot.img, so my system and bootloader is back to stock.

Thanks guys yet again, for whole rooting thing and hacked bootloader, that is awesome
[Fire TV Original Android Development] Bertonumber1:
What I have done with my stick

Unblocked bootloader

Flashed TWRP, done many tests with system.

Used magisk with many modules, at the end wiped everything, flashed stock 6.2.7.1 stock update, set it up.

As i also used OTG for some storage TWRP would create a delay, and i figured i longer needed TWRP because I don't intend to mess with system, because many people can't, so after few days, flashed the stock boot.img, so my system and bootloader is back to stock.

Thanks guys yet again, for whole rooting thing and hacked bootloader, that is awesome[/QUOTE]

Yeah I just tried to access settings there and my stick is freezing..

Damn Amazon.... They don't make it easy do they????

Will have to reflash later today as in getting android tv contact your provider error now.... Dunno what I've done

I'm scared to touch xposed Magisk modules as I've caused chaos on phones with it.. I tried rooting 2nd gen fire tv there also..... No luck.. I think they've made hardware revision on newer models with same as what they did with tank.

I'm just gonna stick with pre rooted 6.2.6.8 with atv launcher and keep fire tv launcher enabled to access settings..

Doesn't really seem like there's much else to do.

Anyway thanks again guys
[Fire TV Original Android Development] SweenWolf:
I have stock images of 6271, if you get the zip you can flash and custom launcher will work. If anyone need, i can TRY uploading it.
[Fire TV Original Android Development] Bertonumber1:
deleted
[Fire TV Original Android Development] Bertonumber1:
G4T0VM2402261N14	no permissions (user in plugdev group; are your udev rules wrong?);

hey there ,

anyone know the way around the set plugdev error with Firestick . dont have issues with usb mouse or anything , just the firestick prompts the plugdev error which i think is to do with androidrule51

laptop is a toshiba satellite c660 as root on linuxfx user Targeted1#

i dunno the 4k firestick id to target it on usb port (switched to this distro from ubuntu as it was doing exact same error)

any help greatly appreciated

thanks:good:
[Fire TV Original Android Development] SweenWolf:
https://stackoverflow.com/a/53887437
[Fire TV Original Android Development] Bertonumber1:
Hey Sweenwolf cheers again , only just got my device back to normal after the AFTV Magisk google apps mod done terrible things after the flash . thanks
[Fire TV Original Android Development] SweenWolf:
Lol, glad your stick is back to normal.
[Fire TV Original Android Development] Bertonumber1:
Hey guys ,

Sorry if this is a newbie question , how do I get out of bootloop (stuck on amazon logo ) I had some bad errors from ATV Xposed Magisk module ,

I done a full wipe and can only access TWRP with OTG cable .

Because I can only access TWRP this way , I can't push any ROM to the device as its not showing up with OTG cable plugged in ..

Hacked fastboot etc is still accessible via recovery but only with OTG so am I correct in thinking I need to do the fireos thing again ?

Cheers in advance
[Fire TV Original Android Development] SweenWolf:
You will need a usb hub then, borrow it from someone.
[Fire TV Original Android Development] Bertonumber1:
I have a hub , but there's no way to enter commands because of the OTG cable is ruining the straight connection between stick and laptop . if you know what I'm talking about ?

I've done this thousands of times but my minds went a blank lol

##Edit ### OK folks , I read back through the posts and saw [MENTION=5213625]Sus_i[/MENTION] wrote USB powered hub , USB flash with the required files , and Keyboard/airmouse does the trick .

Don't know why I didn't think of this . just overlooked it I think because I couldnt connect with PC ..

Cheers anyway :svetius:
[Fire TV Original Android Development] Skel40:
Do you know what's with the images folder with the stock rom? Just yesterday as a test and being able to reopen the shield in case of bricking (which it did) by rebooting into TWRP, adb shell reboot-amonet then decided to flash these commands:

fastboot flash logo logo.bin

fastboot flash system system.img (in stock rom folder)

fastboot flash preloader preloader.bin

fastboot flash vendor vendor.img

fastboot flash boot boot.img (it throws off an error in the fireiso os)

fastboot flash tz tz.img (doesn't exist after inputting the fastboot command)

And I get no signal on my Fire TV after flashing these partitions in the hacked fastboot. Usually flashing the system and vendor images in fastboot (while trying to put my 4K back to 100% stock as a test) will greet me with no signal of any kind so if there's a way to know how to return back to stock without TWRP and without the hacked fastboot then it would be great. I'm messing with my 4K to see the possibilities it can have after unlocking. A note as well. Rebooting into fastboot doesn't boot me into fastboot as it's supposed to but instead boots me back into the system as if I rebooted, I can only boot into the original fastboot by rebooting into the bootloader.
[Fire TV Original Android Development] Sus_i:
What kind of error message?

There isn't a tz partition at all ;)

Try:

fastboot flash tee1 tz.img

and

fastboot flash tee2 tz.img

Maybe take a look into the stock update script, if you want to know details...

:D
[Fire TV Original Android Development] SweenWolf:
https://xdaforums.com/showpost.php?p=83509209&postcount=2

This is what i did to get back to stock.

At first I was putting commands in the original bootloader but that wouldn't write anything to the system, then i remembered we have a hacked bootloader to flash original boot.img to the stick.

I could flash 7.1 on top of 7.3, while testing with these Updates if i wiped everything then sometimes my remote never paired and i had to start again, so flashi g any update to any version is just updating the partitions without any problems, and twrp will not allow important partitions to flash.

So i wiped everything, flashed stock image, it booted just fine, set up adb.

Rebooted to recovery and then again to hacked bootloader, there i flashed stock boot.img.

You know stock boot means no twrp,

I then resetted everything again, and I am back to stock.

And FOTA updator will do everything to write a system update.

Took me TWRP, a stock Image and hacked bootloader for that.

Maybe our devices are no same, I couldn't use the cap to short i had to short the pad to the ground, any change in the twrp system partition doesn't affect the system partition when the system is up.

Need SU for that, but I'm not a fan of su on this stick.

TWRP will get the job done for me.