yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] Sus_i:
APK/App is installed, now flash a magisk.zip with twrp too (rename the apk if there isn't a zip on github).

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Fire TV Android Development] asdfghjklqwert:
I did it said it is already installed.

/sdcard # twrp install Magisk-v20.4.zip

Installing zip file '/data/media/0/Magisk-v20.4.zip'

Installing zip file '/data/media/0/Magisk-v20.4.zip'

Checking for Digest file...

Skipping Digest check: no Digest file found

[amonet] Remove boot patch...

[amonet] OK

***********************

Magisk 20.4 Installer

***********************

- Mounting /system

- Target image: /dev/block/mmcblk0p5

- Device platform: arm

- Constructing environment

- Adding addon.d survival script

- Unpacking boot image

- Checking ramdisk status

- Magisk patched boot image detected

- Patching ramdisk

- Repacking boot image

- Flashing new boot image

- Unmounting partitions

- Done

[amonet] Install boot patch...

[amonet] OK

[amonet] Install recovery patch...

[amonet] ALREADY_INSTALLED

Done processing script file
[Fire TV Android Development] hasobist:
Hello!

Looks like the .zip was flashed properly.

Does the stick boot fine,if so which version of Magisk.apk did you install.

Cheers!
[Fire TV Android Development] asdfghjklqwert:
Yes. it boots fine. Magisk opens & I took a picture of the screen in post #287. My other stick has LineageOS 12.1 and Magisk runs fine.
[Fire TV Android Development] hasobist:
Hello!

Options:

Before trying all the possible options boot into recovery ,take a backup of all partitions except /cache

1.Try clear data and flash Magisk,see if it works

2.Clean flash the rom ,before which clear all partitions flash rom followed by Magisk,clear cache and dalvik and reboot then register.

If it ain't works then

3.You can take the backup of first stick,except /cache ,store the backup in TWRP folder /backup folder/serial no G......./backup of second stick and restore .

Before restore clear all the partitions restore all the partitions, flash Magisk ,clear /cache,/dalvik-cache and reboot.

Worth a try.......

Cheers!
[Fire TV Android Development] asdfghjklqwert:
Many thank yous for your help. I wiped a few time and reinstalled everything and flashed the prerooted rom & magisk. It seems to be working but i will mess with this weekend.
[Fire TV Android Development] hasobist:
Hello!

As say always "Don't mess with the tank unless you know what your doing" ,perhaps enjoy the little beast. It's always been my reliable at standby when in need.

Great it helped.......

Have a Good Weekend!

Cheers!
[Fire TV Android Development] SkiLL83:
Hi to everyone,

i've flashed the last rom version in trwp mode with magisk and later after reboot i can't pair my Firestick Remote (2nd gen),

i pressed the home key for more 2 minutes, the light blink after 10 seconds but after few seconds its stop

can you help me?

Thanks in advance
[Fire TV Android Development] hasobist:
Hello!

Try using fresh batteries.

Is this the remote you were using with tge stick?

You can try resetting the remote and give it a try.

Cheers!
[Fire TV Android Development] Gast2:
I save myself this way: I connect the AEROMAUS via OTG cable and connect my native one with it
[Fire TV Android Development] SkiLL83:
Thanks,

yes all done resolved i've reset the remote control following the procedures: https://www.amazon.com/gp/help/cust... hold the Left,the batteries from your remote.
[Fire TV Android Development] hasobist:
Hello!

Wonderful, you got it working.

Cheers!
[Fire TV Android Development] snam11:
i've tried latest version 5.2.7.3_r1 , but i can't get magisk to work, i've tried 25.1, 24.3, 23.0 with no dice.

all those versions work fine if i use the lineage rom.

i install them as usual: first on recovery via twrp install zip (also a clear cache/delvik just in case),than reboot and install same version apk, and than su command via adb.

but if i click on istalled apk it just crash once a button is pressed.
[Fire TV Android Development] hasobist:
Hello!

If you check my posts ,attached the Magisk .zip/.apk files for a fellow member in the community.

Flash Magisk ,clear /cache,dalvik-cache reboot and install the apk ,if lucky Magisk will prompt for full install,where the apk ain't need to be installed.

Cheers!
[Fire TV Android Development] snam11:
i've read the topic from last page to the first, i can't find your post nor the attached file, can you gimme the link?
[Fire TV Android Development] hasobist:
Hello!

Click on my profile,scroll down messages you'll find it.Will try search as well will link you to the same.

Edit- '[Magisk][Module] FireTV 4K Stick Add-Ons' https://xdaforums.com/t/magisk-module-firetv-4k-stick-add-ons.3979117/

Requisites are in the GDrive(All files)

Cheers!
[Fire TV Android Development] snam11:
thnx, i've also found this post in lineage:

[ROM] [unlocked] [tank] LineageOS 12.1

DISCLAIMER: We are not responsible for any damage, bootloop, bricked or broken devices and Relationships. Need an unlocked tank with amonet patched recovery https://xdaforums.com/fire-tv/development/unlock-fire-tv-stick-2nd-gen-tank-t3907002 This...

xdaforums.com

i suppose is the same files you have on the gdrive
[Fire TV Android Development] snam11:
i was noticing magisk 20.4 doesn't support zygisk, it was introduced from 24.1

is available a way to have it working?
[Fire TV Android Development] hasobist:
Hello!

The drive has a Zygisk version of Magisk.

Cheers!
[Fire TV Android Development] snam11:
yea, but is not working :D

that's why i asked in the first place.

latest supported magisk for tank is 25.1, but again, it doesn't work (at least on this prerooted image)
[Fire TV Android Development] hasobist:
Hello!

Personally never needed zygisk on tank.

Will check the version using and update you later.

Check if the attached works.

Cheers!
[Fire TV Android Development] snam11:
is the same apk i have, it doesn't work.

seems the only working combination is installing via twrp the v. 20.4 than the apk 22.1 or 7.5.1 (than update to 22.1 via the menu app).

is weird because via twrp you can install any magisk up to 25.1 (afaik there is also a modded version for ftv), but if you install the apk it just crash.

Even if i install the 20.4 via twrp and try to install 25.1 apk it just crash...

is a pity because the zygisk feature is a must have to hide stuff from apps
[Fire TV Android Development] hasobist:
Hello!

That's one of the reasons never tried on tank 5.x.x.x perhaps works on the Firetv 4k though.

Cheers!
[Fire TV Android Development] that1loserguy:
@AFTVnews.com i figure u might be able to help with something, i dont have a remote so to do setup i install tankxxxx-rooted.zip and magisk.zip and add my adb pubkey to the stick in twrp, then i reboot to os and install magisk.apk for root then use adb shell "am start -a android.settings.WIFI_SETTINGS" to open up wifi settings and navigate with scrcpy, then i connect the fire tv apps remote to my firestick and proceed with setup, but when i get to "connect network" and "scan network" it seems to skip them and take me to checking for updates, it finds one and downloads but fails to install, i cant proceed with setup and it asks me to restart my stick, i would really appreciate any help.
[Fire TV Android Development] that1loserguy:
i have also tried adb shell, su, pm uninstall -k --user 0 com.amazon.tv.oobe which uninstalls the setup wizard, but it leaves me at a black screen with 3 dots at the bottom right (a loading animation), i will leave it for 10 minutes and come back to a screensaver, making the screemsaver go away reveals the loading screen again, the issue will persist across reboots and i have to reflash the rom to fix it.
[Fire TV Android Development] Sus_i:
Did you try to skip the update like this?

How to Skip Software Updates during Initial Setup or Factory Reset on a Fire TV, Firestick, or Fire TV Cube

Since the latest software update for Fire TV devices is blocking the ability to use custom launchers, you may want to avoid updating a new or factory reset Fire TV.

www.aftvnews.com
[Fire TV Android Development] that1loserguy:
i will try it immediately, thank you for the response
[Fire TV Android Development] that1loserguy:
if it works, i will come back with a complete method of setting up a firestick without a remote
[Fire TV Android Development] AFTVnews.com:
I don't know if this still works, but I would try using TWRP to modify /system/build.prop so it thinks the installed OS version is higher than the latest one. You need to edit the ro.build.version.number value to be something like 987654321. Here's my really old guide for this that might help: https://www.aftvnews.com/how-to-blo...k-by-setting-a-custom-fire-os-version-number/
[Fire TV Android Development] SoulInfernoDE:
[MENTION=3991724]rbox[/MENTION] all my devices received the new update now. Could it be that amzon is pushing the update regularly now? ...if yes a prerooted would be nice.
[Fire TV Android Development] fax88:
I have 2 basic edition fire tv sticks (tank) v2. I can confirm that everything is compatible and the same. I've flashed both the stock image as well as the pre-rooted image. Basically, the rom is the exact same, when you 1st make a connection to the Amazon servers, It just downloads an different interface and disables some features, e.g. LiveTV , All the APK's are still in the rom, but its just disabled from the launcher. Alexa is available as you can pair the device with a voice remote, or control it with an amazon echo.
[Fire TV Android Development] KINDLE FIRE MURDERER:
Hello! I installed this ROM by wiping Dalvik, Cache, and Data, and then installing the zip, and Magisk. Now, whenever I turn my Fire Stick 2 on, it shows "optimizing, will take 10 minutes", and get stuck on pairing with my remote, which does not work. Is there something wrong with bluetooth, or is my remote messed up? Thanks!

EDIT: somehow bypassed that and got remote connected. next issue, it's stuck on "Scanning for networks". :(
[Fire TV Android Development] pennywisdom65:
What did you do to get your remote to connect?
[Fire TV Android Development] KINDLE FIRE MURDERER:
I went to my local tech shop, and as it turns out there was an Amazon guy with a Fire Stick demo. Somehow, his remote connected with my fire stick, and my remote connected with his, so we exchanged remotes! I think the second option would be to just get an OTG cable and keyboard and skip the first setup thing. I'm stuck on "Scanning for networks" though >_<
[Fire TV Android Development] KINDLE FIRE MURDERER:
Can anyone with a successful rooted Fire Stick 2 send their system / data / cache backups? It'd help a lot
[Fire TV Android Development] BostonDan:
Make sure you first upgrade to 5.2.6.7 first if you come from a room lower than 5.2.6.7. Otherwise there seems to be problems with pairing remotes and finding networks. The optimizing does take awhile.

Cheers,

B.D.
[Fire TV Android Development] KINDLE FIRE MURDERER:
Anywhere I can find the 5.2.6.7 rom for Fire Stick 2?
[Fire TV Android Development] rbox:
Sounds like you didn't follow the instructions in the unlock post where it said you should update to .9 first. You can get the .9 stock rom here: https://xdaforums.com/showpost.php?p=79068766&postcount=134
[Fire TV Android Development] KINDLE FIRE MURDERER:
Err, thanks for the response! What happened was my fire stick was on .9, I installed your awesome rooted rom, but deleted my data partition, and now am stuck on "searching for networks". someone above had mentioned that "updating" to .7 and then .9 would fix the wifi issue. nonetheless, I didn't see the .9 stock rom, I'll wipe my system and try installing that. Any tips you may have, to fix the "searching for network" issue? I'm desperate :(
[Fire TV Android Development] rbox:
Did you damage it?
[Fire TV Android Development] KINDLE FIRE MURDERER:
Nope! I'm pretty sure hardware wise it is fine, because right after installing twrp, I used it for a day or two (before installing the prerooted image). And then, wifi was working. :(

---------- Post added at 07:40 AM ---------- Previous post was at 07:18 AM ----------

Installing stock image again, wiped everything, stuck on "searching for networks" again.
[Fire TV Android Development] Michajin:
[MENTION=3991724]rbox[/MENTION] Is there anyway to use 2ndinit to give you an option to boot into recovery from booting? It is really nice to have that option on the firetv2. I don't know if it is possible, but i thought i would ask.
[Fire TV Android Development] rbox:
Unfortunately I have not been able to get the boot to recovery script to work for me. I need that to recover when I inevitably brick the thing while testing 2ndinit. I'll play around with it some more and see if I can get that working. Once that works, I just need to find the injection point which I'm sure will be similar to other fire tv devices.
[Fire TV Android Development] Michajin:
Great! thanks... if you want anyone to do testing, let me know.... i don't mind being the sacrificial lamb to achieve progress... I have an extra stick to toast if it gets to that....
[Fire TV Android Development] Sus_i:
Maybe you need a few more trys ;)

I tried the scripts about a hundred times with both of my sticks, onto two computers. From about 15 to 20 try outs with the sucessful message sending FACTORYM, it boots one time into TWRP. Same for the fastboot script. There were quite a few errors between the sucessful attempts, it shows not everytime the message sending FACTORYM.

If the bootlogo don't show "recovery mode" down in the left corner at start up, I've pulled the usb and run the script again...
[Fire TV Android Development] brentonv:
Thanks so very very much rbox for the latest patched firmware. Could I please make request version 5.2.6.0 as this appears to run fine on low powered tv usb ports. Later versions boot loop if not fully powered?
[Fire TV Android Development] rbox:
If someone can figure out how to get the URL for me, sure.
[Fire TV Android Development] brentonv:
[MENTION=3991724]rbox[/MENTION] not sure if you picked this up in the other thread but here is again the full 5.2.7.0 update "update-kindle-full_tank-288.6.3.9_user_639566220.bin" if you need it.

This upgraded my device from 5.2.6.3 to 5.2.7.0 in full. https://drive.google.com/file/d/1Lh_MvRLWRxgwtHHD0nzv1i9AL8Sxh-Jc/view?usp=drivesdk
[Fire TV Android Development] rbox:
I did see this, thanks. I've had family in town so haven't had a chance to take a look at it yet. I might have some time over the 4th of July weekend.
[Fire TV Android Development] forkup:
That link points to a text file.
[Fire TV Android Development] brentonv:
Yeah I forked up lol. Link was correct in other thread. Seems like rbox found it. Thanks for the mod [MENTION=3991724]rbox[/MENTION] ?
[Fire TV Android Development] theflashfromthecw:
5.2.7.0 makes Magisk install forever, Xposed has "low space available"

The rom works fine with only a couple problems with Xposed and Magisk installing. Xposed won't even install at all and it gives me a error 1.
[Fire TV Android Development] Sus_i:
This rom uses addon.d to preserve Magisk and any other addons.

Installed it on two sticks, no problems at all. Thanks [MENTION=3991724]rbox[/MENTION]
[Fire TV Android Development] hardy272:
You should try systemles xposed, just install the systemless version of xposed, enable it on Magisk Module, and flash the xposed zip, I´ve tried that way and seems to be fine (Although I haven´t tried any module on my xposed yet), also safetynet is ok, I could watch Netflix without any issue with both Magisk and Systemless xposed installed.
[Fire TV Android Development] brentonv:
Don't install Magisk modules from Magisk. It kills the boot loader. Needs to be installed from TWRP
[Fire TV Android Development] hardy272:
If I´m not mistaken, magisk modules are APKs, do they can mess with with bootleader? :confused:
[Fire TV Android Development] brentonv:
Magisk modules are zip files injected into the boot.img but doesn't work with this Magisk exploit. Instead the zip files need to be installed from TWRP. If installed from Magisk the system won't boot. Can someone else please confirm this for [MENTION=4373417]hardy272[/MENTION]
[Fire TV Android Development] Sus_i:
Yes, never ever flash zip files from FireOS, i.e. with magisk manager :D

First and best plugin is 'magisk manager for recovery', in case something gets wrong and a plugin needs to be disabled.
[Fire TV Android Development] Pretoriano80:
Magisk modules are not apks and are not injected into boot.img neither.

It should be fine to install Magisk modules from the manager, just make sure those modules are compatible, otherwise could cause issues (such the Firetv not booting anymore).

Playing with xposed it's already tricky and most of the times you are asking for troubles.

P. S. : Magisk modules cannot mess a bootloader.

P. S. 2 : Updating Magisk to latest and greatest could also bring issues, so be careful before pressing the "update" button!
[Fire TV Android Development] Sus_i:
Do this with the 'tank' device and it bricks directly. For safety reasons I flash zip's only with TWRP, since TWRP is aware of the amonet exploit and will patch zip's on the fly. ;)
[Fire TV Android Development] Future-Proof:
On 5.2.7.0, and I was wondering, just how far back can I downgrade using TWRP? I just bought my Fire Stick, and I'm finding that not only can I no longer bypass logging in with an Amazon account (as described here: https://xdaforums.com/showpost.php?p=75658474&postcount=3), but I can't get any game controllers to pair with the device at all, which I've read was a purposeful patch from Amazon. I'm wanting to go as far back as I can, so I thought I'd try the 5.2.6.8 image. Is there any risk to this?

Also, I've found even older, not-rooted stock firmware (here: http://www.aftvnews.com/amazon-fire-tv-fire-tv-stick-software-update-history/), but all of the files are .bin files, not .zip. Is that something that can just be flashed in TWRP?

Sorry for all of the questions, I'm a bit ignorant when it comes to recovery and downgrading. Thanks for any help!
[Fire TV Android Development] theflashfromthecw:
You can downgrade up to 5.2.6.3 for now on the Fire TV Stick 2 within TWRP. The update will say .bin at the end so in order for you to flash the file successfully, simply rename .bin (not the whole file name) to .zip. Thanks to the Amonet exploit, it patches the image files automatically so there's no need to patch the 5.2.6.8 image file. I'll give you a warning though. Before downgrading to this version, the new Fire TV Stick remote with the power button/volume buttons are incompatible since this is an older version before the new remote functionality even was announced.

Here's the .bin (rename the .bin to .zip)

https://drive.google.com/file/d/1kd0eBgebDUpKoKc8lvlZCFxqr4Gx_biz/view?usp=sharing

Don't worry about TWRP after flashing
[Fire TV Android Development] Future-Proof:
This is all fantastic, thank you so much for the info! I'll definitely be careful with the remote; I'm assuming that to navigate TWRP that I'd need to use a keyboard anyway, correct? At least I'll be able to use that to get around if I downgrade. Thanks again!
[Fire TV Android Development] hardy272:
I don't have an OTG so I can't use a keyboard, I managed to do this using TWRP commands, boot on recovery while the Firestick is connected to your PC using the commands:

adb shell
reboot recovery

Once TWRP shows up you can wipe (do not why but wipe system gave me error but the rom flashing is ok, anyway during flashing rom the system wipe itself), for example:

adb shell
twrp wipe data
twrp wipe cache

And to install a rom, or a flashable zip, assuming your zip is on our device storage's root:

cd /sdcard
twrp install rom_filename.zip

If you do not have your rom on your Firestick, you can transfer files to it by using adb command, assuming you have your rom_filename.zip in your working directory:

adb push rom_filename.zip /sdcad/rom_filename.zip

And then you can flash it using twrp commands.
[Fire TV Android Development] davidtgbe:
Hello,

I've followed the steps and unlocked my aftv stock 2nd gen from 5.2.7.0 with no errors. Then flashed custom room v 5.2.7.0 r1 and can't connect anymore to any wifi. Had done a factory reset, paired remote (push home 30 secs) and trying to search networks, but it keeps searching forever. Have seen previous posts with similar problems, but I'm not sure if there is a working solution...

Update:

I couldn't reboot on recovery because RSA fingerprint of my computer was not authorized after factory reset. No popup showed up on my firetv to allow the PC adb connection, maybe because the configuration process to select the language and network must be completed... and my device is stuck in searching networks...

So, since I'm unable to connect via ADB to the AFTV, I've tried to start from scratch and redo all the steps again. Result is I haven't been able to pass from step 1 of the process, despite of seeing my device connected correctly (with lsusb and dmesg). Result, by now, my AFTV is not booting anymore, but I can see it with lsusb and dmesg as mediatek phone.

Any help would be appreciated. Thanks!!

---

[ 3181.708612] usb 1-1.1.4.4: USB disconnect, device number 58

[ 3204.976237] usb 1-1.1.4.4: new full-speed USB device number 59 using ehci-pci

[ 3205.085005] usb 1-1.1.4.4: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00

[ 3205.085009] usb 1-1.1.4.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0

[ 3205.086133] cdc_acm 1-1.1.4.4:1.0: ttyACM0: USB ACM device

lubuntu@lubuntu:~$ lsusb

Bus 002 Device 004: ID 0930:0214 Toshiba Corp.

Bus 002 Device 003: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2

Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 004: ID 0bda:58f5 Realtek Semiconductor Corp.

Bus 001 Device 059: ID 0e8d:0003 MediaTek Inc. MT6227 phone

Bus 001 Device 007: ID 1997:2433

Bus 001 Device 006: ID 058f:6254 Alcor Micro Corp. USB Hub

Bus 001 Device 005: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader

Bus 001 Device 003: ID 058f:6254 Alcor Micro Corp. USB Hub

Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

---

Update: Device can boot but stuck on searching networks. I think WIFI is broken.
[Fire TV Android Development] hardy272:
Wierd. Try to short the Fire and then (while being shorted) connect the usb cable, It should be detected by the script
[Fire TV Android Development] brentonv:
Hey [MENTION=3991724]rbox[/MENTION] I've got a few devices still on 5.2.6.0 is there any way of extracting the recovery from it to build a new pre-rooted rom? Remembering that 5.2.6.0 still gives limited adb user=0 commands.
[Fire TV Android Development] rbox:
I don't know why anyone would want a 5.2.6.0 rom, but I need the update URL from amazon to make a rom.
[Fire TV Android Development] brentonv:
I'm after an older rom that supports the firetv settings app that is no longer compatible. 5.2.6.3 should be fine have you seen this post [MENTION=3991724]rbox[/MENTION]?
[Fire TV Android Development] rbox:
And does flashing that work?
[Fire TV Android Development] brentonv:
[MENTION=9818496]theflashfromthecw[/MENTION] does the rom you link to downgrade to 5.2.6.3? I'm not setup ATM for testing. And do you have any other versions for Rbox to patch?
[Fire TV Android Development] marcolrz:
My wifi is dead after flash this rom, even installing others roms the wifi don't work anymore :(
[Fire TV Android Development] kwiksi1ver:
Does it work on CM12.1?
[Fire TV Android Development] marcolrz:
Nop. Don't show any wifi network.
[Fire TV Android Development] Sus_i:
Have you tested this rom, flashed with TWRP recovery?
[Fire TV Android Development] ThEr3aLsLiMsHaDy:
Need to root to change TTL, just looked at my sticks software version and it says 5.2.7.1 , the downloads only go to 7.0 anyone have an update or can i use the 7.0 on 7.1