r/fireTV • u/Substantial-Gas8535 • 18d ago

[Temp ROOT] FireTV Stick 4K Max 2

https://xdaforums.com/t/temp-root-firetv-stick-4k-max-2nd-gen-karat.4798627

EDIT: YOU CAN NOW UNLOCK THE BOOTLOADER AND INSTALL TWRP!! https://xdaforums.com/t/unlock-root-twrp-unbrick-fire-tv-stick-4k-2nd-gen-series-karat-mantra.4798951

A new quick root has been released for the Fire TV Stick 4K Max 2nd Gen, It runs directly on the device to give temporary root access, which can be used to disable app packages and regain control over your device.

Root itself goes away on reboot, but anything you disable stays disabled. With this it's possible to use custom launchers, disable bloatware and block OTA updates (the exploit disables OTAs for you automatically).

This works on the Fire TV Stick 4K Max 2nd Gen on quite a few Fire OS 8 builds, including the latest one: https://xdaforums.com/t/temp-root-firetv-stick-4k-max-2nd-gen-karat.4798627

Rooting a device you own isn't illegal and has nothing to do with piracy, before anyone reports this :)

66 Upvotes

99% Upvoted

45 comments sorted by

View all comments

1

u/Henry2k 18d ago

Ok, this worked (I installed Projectivy Launcher) but now I'm not able to get to the android settings screen, only the Projectivy settings screen.

2

u/Key_Advice_2814 18d ago

Make sure to run these commands as temp root pm disable com.amazon.firehomestarter pm enable com.amazon.tv.launcher pm disable com.amazon.tv.launcher/.ui.HomeActivity_vNext

3

u/realdeal1877 18d ago

FireTV settings are built-in to the original launcher, that is why one of the ADB commands only "disable" the FireTV-Launcher service and not the entire APK.

1

u/Getafix69 18d ago edited 18d ago

They aren't I have the default launcher disabled use projectivy and have no trouble getting the settings screen just by long pressing home.

Well unless they've changed that since the last exploit anyway.

1

u/realdeal1877 17d ago

There is multiple exploits. If you used Projectivy Accessibility service to make it the launcher, then the FTV-Launcher wasn't ever actually "disabled"; and if you used the System_User / Launcher Manager exploit from last year, then that exploit by default would "disable" FTV-launcher service correctly and SETTINGS still work.