Database Users

How to revive a TF101G in 2021 (with Play Store) - Eee Pad Transformer General

I'd like to share my experiences about bringing a good old TF101G back to life in 03/2021. My report is heavily based on the instructions of javidben (05/2020).
Ingredients​Required:
A microSD card, SD card or USB drive
TWRP 2.8.1.1 by Team Win Recovery Project, @sidneyk, @josteink, @timduru
Katkiss 6.0.3.4 by @timduru
Super User 2.52 Beta by @Chainfire
Xposed Module by @rovo89 (03/2021: v3.1.5)
Xposed Framework SDK23 by @rovo89 (03/2021: v89)
MicroG Services Core by the microG Team, @MaR-V-iN (03/2021: v0.2.17.204714)
MicroG Services Framework Proxy by the microG Team, @MaR-V-iN (03/2021: v0.1.0)
NanoDroid-microG by @Setialpha (03/2021: v23.1.2.20210117)
F-Droid by Team F-Droid (03/2021: v1.11)
MiXplorer by @HootanParsa (03/2021: v6.53.7)
PeaZip by PeaZip SRL (03/2021: v7.8.0) or any other tool to extract a ZST compressed file
Optional and recommended:
fsync_on.zip by @timduru to avoid random reboots caused by corrupted data
Katkiss V2.2.0 by @timduru
Wakelock v3 by @Dark3n to avoid reboots in deep sleep (TF101G only)
Instructions​On your PC​
Download all files and save everything except PeaZip on the SD card.
Open NanoDroid-microG-???.zip and extract the file system/priv-app/PhoneSky/PhoneSky.apk.zst.
Use PeaZip to decompress PhoneSky.apk.zst to PhoneSky.apk.
Rename PhoneSky.apk to com.android.vending.apk and save it on the SD card.
On the tablet​
Boot into TWRP 2.8.1.1 Recovery (Hold Vol Down and Power Button).
Wipe/Format Data.
Flash (in order):
Katkiss 6.0.34
SuperUser 2.52 Beta
optional: fsync_on
optional: KatKiss V2.2.0
Xposed SDK 23
Reboot into Android. Do not enable Wi-Fi yet.
Once in Android, select the SD card notification and setup the SD card as external memory.
Touch the notification again to see a simple file explorer showing the files on the SD card.
Copy the following files to the Downloadsdirectory in internal memory:
F-Droid
MiXplorer
MicroG Services Core
MicroG Services Framework Proxy
Xposed Module
Go to the app drawer, open app Downloads and install in order:
F-Droid
MiXplorer
MicroG Services Core (com.google.android.gms-???.apk)
MicroG Services Framework (com.google.android.gsf-???.apk)
Xposed Module
Go to the app drawer, open F-Droidand
Go to settings, enable Expert Mode and Unstable updates
Turn on Wi-Fi and refresh F-Droid Repository
Search & Install Apple UnifiedNlp Backend
Search & Install NominatimNlpBackend
Go to the app drawer, open MicroG Settings and
Go to Self Check, grant all permissions and enable Battery optimizations ignored
Go to Google device registration and enable it
Go to Google Cloud Messaging and enable it
Go to Location modules and enable Apple Wi-Fi; if possible, enable Nominatim.
Go to the app drawer, open Xposedand
Go to Download, search FakeGApps and install FakeGApps 2.0
Go to Modules tab and activate FakeGApps
Reboot the device.
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything but Play Store checklisted.
Go to the app drawer, open MiXPlorerand
Copy file com.android.vending.apk to Root/system/priv-app
Select the file com.android.vending.apk, press Info (top right), select Permissions and set to 755 (executable).
Go to Root/data/app and create empty files
com.android.vending
com.android.vending-1
com.android.vending-2
Select the empty files, press Info (top right), select Permissions and set to 755 (executable).
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything checked.
Reboot your device.
Go to the app drawer, open MicroG Settings, select Account and login into your Google account.
For TF101G only (to prevent reboots in deep sleep):
Install Wakelock
Enable Wakelock Processor
Go to Settings and enable Autostart on boot
App compatibility​Although the TF101G runs Marshmallow, a lot of Marshmallow-compatible apps do not work on the device. The reason is that the CPU does not support the NEON instruction set. Nowadays, most apps expect a NEON-compatible CPU. Google dropped support of non-neon phones and tablets with Android 4.2 in 2013. My observation is that apps compiled for Android <4.2 have a good chance to work without problems on the device. So, if you're looking for a certain app in of the apk portals, filter by target platform Android <4.2 (Jelly Bean).
These specific versions do work on the TF101G:
Chromium 76 for Tegra2 by @decatf
Fennec 59 for Tegra2 by schmaller
Firefox 52.0.2
VLC 3.0.13
Kodi 17.6 without NEON instructions by tetramarreta
Remarks​Flashing NanoDroid no longer possible from v22​In the previous tutorials, the ZIP files NanoDroid-FDroid and NanoDroid-Patcher have been recommended instead of installing the APKs. I found out these ZIPs are not usable anymore because the zstd binary within them is not compatible with the TF101. Trying to flash these files results in an error message
Code:
failed to decompress /system/app/FDroid/FDroid.apk.zst
I found out that the binary zstd.arm that is part of the ZIP crashes with a Illegal instruction on the device. The same file works on a Raspberry Pi (also armv7), so I guess it's compiled against the NEON instruction set. Maybe an older version (v21.0) from the NanoDroid Archive works, but I didn't try. NanoDroid #197 addresses this issue.
Backup feature broken in TWRP 2.8.1.1​It seems that the Backup feature does not work in TWRP 2.8.1.1. When starting a backup, the screen turns off (feels like a little crash); when turned on again, TWRP is still on the same page but no backup was created and no process is running. Using an older version (e.g. twrp-2.6.3.0-7_tf101g.zip) works. So as a workaraound, you can flash the old TWRP, do the backup and finally flash 2.8.1.1 again.
Credits​Thanks to @timduru for the great KatKiss ROM. Thanks to the community for all the infos and details in >1.500 posts allowing a 10-year old device to do a good job in 2021.
All I did was reading, executing and documenting the steps described in the
Tutorial of @javidben (05/2020)
Tutorial of @alexchandra (12/2018)
Tutorial of @EpicCentr (11/2018)

-christian- said:
I'd like to share my experiences about bringing a good old TF101G back to life in 03/2021. My report is heavily based on the instructions of javidben (05/2020).
Ingredients​Required:
A microSD card, SD card or USB drive
TWRP 2.8.1.1 by Team Win Recovery Project, @sidneyk, @josteink, @timduru
Katkiss 6.0.3.4 by @timduru
Super User 2.52 Beta by @Chainfire
Xposed Module by @rovo89 (03/2021: v3.1.5)
Xposed Framework SDK23 by @rovo89 (03/2021: v89)
MicroG Services Core by the microG Team, @MaR-V-iN (03/2021: v0.2.17.204714)
MicroG Services Framework Proxy by the microG Team, @MaR-V-iN (03/2021: v0.1.0)
NanoDroid-microG by @Setialpha (03/2021: v23.1.2.20210117)
F-Droid by Team F-Droid (03/2021: v1.11)
MiXplorer by @HootanParsa (03/2021: v6.53.7)
PeaZip by PeaZip SRL (03/2021: v7.8.0) or any other tool to extract a ZST compressed file
Optional and recommended:
fsync_on.zip by @timduru to avoid random reboots caused by corrupted data
Katkiss V2.2.0 by @timduru
Wakelock v3 by @Dark3n to avoid reboots in deep sleep (TF101G only)
Instructions​On your PC​
Download all files and save everything except PeaZip on the SD card.
Open NanoDroid-microG-???.zip and extract the file system/priv-app/PhoneSky/PhoneSky.apk.zst.
Use PeaZip to decompress PhoneSky.apk.zst to PhoneSky.apk.
Rename PhoneSky.apk to com.android.vending.apk and save it on the SD card.
On the tablet​
Boot into TWRP 2.8.1.1 Recovery (Hold Vol Down and Power Button).
Wipe/Format Data.
Flash (in order):
Katkiss 6.0.34
SuperUser 2.52 Beta
optional: fsync_on
optional: KatKiss V2.2.0
Xposed SDK 23
Reboot into Android. Do not enable Wi-Fi yet.
Once in Android, select the SD card notification and setup the SD card as external memory.
Touch the notification again to see a simple file explorer showing the files on the SD card.
Copy the following files to the Downloadsdirectory in internal memory:
F-Droid
MiXplorer
MicroG Services Core
MicroG Services Framework Proxy
Xposed Module
Go to the app drawer, open app Downloads and install in order:
F-Droid
MiXplorer
MicroG Services Core (com.google.android.gms-???.apk)
MicroG Services Framework (com.google.android.gsf-???.apk)
Xposed Module
Go to the app drawer, open F-Droidand
Go to settings, enable Expert Mode and Unstable updates
Turn on Wi-Fi and refresh F-Droid Repository
Search & Install Apple UnifiedNlp Backend
Search & Install NominatimNlpBackend
Go to the app drawer, open MicroG Settings and
Go to Self Check, grant all permissions and enable Battery optimizations ignored
Go to Google device registration and enable it
Go to Google Cloud Messaging and enable it
Go to Location modules and enable Apple Wi-Fi; if possible, enable Nominatim.
Go to the app drawer, open Xposedand
Go to Download, search FakeGApps and install FakeGApps 2.0
Go to Modules tab and activate FakeGApps
Reboot the device.
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything but Play Store checklisted.
Go to the app drawer, open MiXPlorerand
Copy file com.android.vending.apk to Root/system/priv-app
Select the file com.android.vending.apk, press Info (top right), select Permissions and set to 755 (executable).
Go to Root/data/app and create empty files
com.android.vending
com.android.vending-1
com.android.vending-2
Select the empty files, press Info (top right), select Permissions and set to 755 (executable).
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything checked.
Reboot your device.
Go to the app drawer, open MicroG Settings, select Account and login into your Google account.
For TF101G only (to prevent reboots in deep sleep):
Install Wakelock
Enable Wakelock Processor
Go to Settings and enable Autostart on boot
App compatibility​Although the TF101G runs Marshmallow, a lot of Marshmallow-compatible apps do not work on the device. The reason is that the CPU does not support the NEON instruction set. Nowadays, most apps expect a NEON-compatible CPU. Google dropped support of non-neon phones and tablets with Android 4.2 in 2013. My observation is that apps compiled for Android <4.2 have a good chance to work without problems on the device. So, if you're looking for a certain app in of the apk portals, filter by target platform Android <4.2 (Jelly Bean).
These specific versions do work on the TF101G:
Chromium 76 for Tegra2 by @decatf
Fennec 59 for Tegra2 by schmaller
Firefox 52.0.2
VLC 3.0.13
Kodi 17.6 without NEON instructions by tetramarreta
Remarks​Flashing NanoDroid no longer possible from v22​In the previous tutorials, the ZIP files NanoDroid-FDroid and NanoDroid-Patcher have been recommended instead of installing the APKs. I found out these ZIPs are not usable anymore because the zstd binary within them is not compatible with the TF101. Trying to flash these files results in an error message
Code:
failed to decompress /system/app/FDroid/FDroid.apk.zst
I found out that the binary zstd.arm that is part of the ZIP crashes with a Illegal instruction on the device. The same file works on a Raspberry Pi (also armv7), so I guess it's compiled against the NEON instruction set. Maybe an older version (v21.0) from the NanoDroid Archive works, but I didn't try. NanoDroid #197 addresses this issue.
Backup feature broken in TWRP 2.8.1.1​It seems that the Backup feature does not work in TWRP 2.8.1.1. When starting a backup, the screen turns off (feels like a little crash); when turned on again, TWRP is still on the same page but no backup was created and no process is running. Using an older version (e.g. twrp-2.6.3.0-7_tf101g.zip) works. So as a workaraound, you can flash the old TWRP, do the backup and finally flash 2.8.1.1 again.
Credits​Thanks to @timduru for the great KatKiss ROM. Thanks to the community for all the infos and details in >1.500 posts allowing a 10-year old device to do a good job in 2021.
All I did was reading, executing and documenting the steps described in the
Tutorial of @javidben (05/2020)
Tutorial of @alexchandra (12/2018)
Tutorial of @EpicCentr (11/2018)
Click to expand...
Click to collapse
I can also confirm that Spotify 8.4.30.688, Elementum 0.1.74 (installed from zip manually), MX Player 1.10.50, BubbleUPnP 3.2.3, and Netflix 4.16.4 are working perfectly under @timduru's ROM.

Can you add an Tutorial how to root tf101G i cant find anything.
I don't have usb option in recovery mode only boot android and wipe cache/data.
Got it: https://forum.xda-developers.com/t/...bricks-all-devices-27-d.1681155/post-77935324

-christian- said:
I'd like to share my experiences about bringing a good old TF101G back to life in 03/2021. My report is heavily based on the instructions of javidben (05/2020).
Ingredients​Required:
A microSD card, SD card or USB drive
TWRP 2.8.1.1 by Team Win Recovery Project, @sidneyk, @josteink, @timduru
Katkiss 6.0.3.4 by @timduru
Super User 2.52 Beta by @Chainfire
Xposed Module by @rovo89 (03/2021: v3.1.5)
Xposed Framework SDK23 by @rovo89 (03/2021: v89)
MicroG Services Core by the microG Team, @MaR-V-iN (03/2021: v0.2.17.204714)
MicroG Services Framework Proxy by the microG Team, @MaR-V-iN (03/2021: v0.1.0)
NanoDroid-microG by @Setialpha (03/2021: v23.1.2.20210117)
F-Droid by Team F-Droid (03/2021: v1.11)
MiXplorer by @HootanParsa (03/2021: v6.53.7)
PeaZip by PeaZip SRL (03/2021: v7.8.0) or any other tool to extract a ZST compressed file
Optional and recommended:
fsync_on.zip by @timduru to avoid random reboots caused by corrupted data
Katkiss V2.2.0 by @timduru
Wakelock v3 by @Dark3n to avoid reboots in deep sleep (TF101G only)
Instructions​On your PC​
Download all files and save everything except PeaZip on the SD card.
Open NanoDroid-microG-???.zip and extract the file system/priv-app/PhoneSky/PhoneSky.apk.zst.
Use PeaZip to decompress PhoneSky.apk.zst to PhoneSky.apk.
Rename PhoneSky.apk to com.android.vending.apk and save it on the SD card.
On the tablet​
Boot into TWRP 2.8.1.1 Recovery (Hold Vol Down and Power Button).
Wipe/Format Data.
Flash (in order):
Katkiss 6.0.34
SuperUser 2.52 Beta
optional: fsync_on
optional: KatKiss V2.2.0
Xposed SDK 23
Reboot into Android. Do not enable Wi-Fi yet.
Once in Android, select the SD card notification and setup the SD card as external memory.
Touch the notification again to see a simple file explorer showing the files on the SD card.
Copy the following files to the Downloadsdirectory in internal memory:
F-Droid
MiXplorer
MicroG Services Core
MicroG Services Framework Proxy
Xposed Module
Go to the app drawer, open app Downloads and install in order:
F-Droid
MiXplorer
MicroG Services Core (com.google.android.gms-???.apk)
MicroG Services Framework (com.google.android.gsf-???.apk)
Xposed Module
Go to the app drawer, open F-Droidand
Go to settings, enable Expert Mode and Unstable updates
Turn on Wi-Fi and refresh F-Droid Repository
Search & Install Apple UnifiedNlp Backend
Search & Install NominatimNlpBackend
Go to the app drawer, open MicroG Settings and
Go to Self Check, grant all permissions and enable Battery optimizations ignored
Go to Google device registration and enable it
Go to Google Cloud Messaging and enable it
Go to Location modules and enable Apple Wi-Fi; if possible, enable Nominatim.
Go to the app drawer, open Xposedand
Go to Download, search FakeGApps and install FakeGApps 2.0
Go to Modules tab and activate FakeGApps
Reboot the device.
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything but Play Store checklisted.
Go to the app drawer, open MiXPlorerand
Copy file com.android.vending.apk to Root/system/priv-app
Select the file com.android.vending.apk, press Info (top right), select Permissions and set to 755 (executable).
Go to Root/data/app and create empty files
com.android.vending
com.android.vending-1
com.android.vending-2
Select the empty files, press Info (top right), select Permissions and set to 755 (executable).
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything checked.
Reboot your device.
Go to the app drawer, open MicroG Settings, select Account and login into your Google account.
For TF101G only (to prevent reboots in deep sleep):
Install Wakelock
Enable Wakelock Processor
Go to Settings and enable Autostart on boot
App compatibility​Although the TF101G runs Marshmallow, a lot of Marshmallow-compatible apps do not work on the device. The reason is that the CPU does not support the NEON instruction set. Nowadays, most apps expect a NEON-compatible CPU. Google dropped support of non-neon phones and tablets with Android 4.2 in 2013. My observation is that apps compiled for Android <4.2 have a good chance to work without problems on the device. So, if you're looking for a certain app in of the apk portals, filter by target platform Android <4.2 (Jelly Bean).
These specific versions do work on the TF101G:
Chromium 76 for Tegra2 by @decatf
Fennec 59 for Tegra2 by schmaller
Firefox 52.0.2
VLC 3.0.13
Kodi 17.6 without NEON instructions by tetramarreta
Remarks​Flashing NanoDroid no longer possible from v22​In the previous tutorials, the ZIP files NanoDroid-FDroid and NanoDroid-Patcher have been recommended instead of installing the APKs. I found out these ZIPs are not usable anymore because the zstd binary within them is not compatible with the TF101. Trying to flash these files results in an error message
Code:
failed to decompress /system/app/FDroid/FDroid.apk.zst
I found out that the binary zstd.arm that is part of the ZIP crashes with a Illegal instruction on the device. The same file works on a Raspberry Pi (also armv7), so I guess it's compiled against the NEON instruction set. Maybe an older version (v21.0) from the NanoDroid Archive works, but I didn't try. NanoDroid #197 addresses this issue.
Backup feature broken in TWRP 2.8.1.1​It seems that the Backup feature does not work in TWRP 2.8.1.1. When starting a backup, the screen turns off (feels like a little crash); when turned on again, TWRP is still on the same page but no backup was created and no process is running. Using an older version (e.g. twrp-2.6.3.0-7_tf101g.zip) works. So as a workaraound, you can flash the old TWRP, do the backup and finally flash 2.8.1.1 again.
Credits​Thanks to @timduru for the great KatKiss ROM. Thanks to the community for all the infos and details in >1.500 posts allowing a 10-year old device to do a good job in 2021.
All I did was reading, executing and documenting the steps described in the
Tutorial of @javidben (05/2020)
Tutorial of @alexchandra (12/2018)
Tutorial of @EpicCentr (11/2018)
Click to expand...
Click to collapse
Does this still work? I will try it. Thank you if you can reply.

roguedes said:
Does this still work?
Click to expand...
Click to collapse
At least it did in 03/2021 - I'd like to encourage you to try it and share your experiences here.

Could you please tell me if there is any Tegra 2 compatible video conference app left?

Hi Christian, thanks a lot for this tutorial.
I've done it two times, with Always the same problem : my paid apps are not recognized as paid...
Could you please help me on that point ? Thanks for answer.
Edit : when trying to manage my account on Google play store, this app crash.

zgildasz said:
Hi Christian, thanks a lot for this tutorial.
I've done it two times, with Always the same problem : my paid apps are not recognized as paid...
Could you please help me on that point ? Thanks for answer.
Edit : when trying to manage my account on Google play store, this app crash.
Click to expand...
Click to collapse
Sorry, I can't help with that problem, maybe someone else has an idea.

Ok. Anyway thanks again for what you did. Wonder if I can buy again a cheap app just to check if this is possible and stable.

I would like to know also. ASUS should at least consider android Go as an option, despite the terminal has been released on the market 10 years ago.

Related

Trick to get play store and root on Phoenix OS 2.0.0
After installation replace system.IMG in phoenix os directory with this: https://mega.nz/#!rYBRlbLY]https://mega.nz/#!rYBRlbLY
Decryption key: 4x2UmG4Xq0r96u_7h_PwfqC5OjQNHR_Gv88fIL1d2BA
Extract it using any zip or 7z software
then download MicroG apps from here and install them all except MicroG store: https://microg.org/download.html
Give root access.
Then download google play store from here: http://www.apkmirror.com/apk/google-...-apk-download/
Rename play store.apk to Phonesky.apk
After that download lucky patcher from here: MOD Edit :-Links Removed as per Rule 6. Do Not Post or Request Warez. XDA Forum Rules
Now install google play store as normal apk.
Then open settings, go to accounts, add account, google.
Sign in into it.
After that open lucky patcher and give root permission and click on rebuild and install below.
Then go to downloads and select the play store apk (Phonesky.apk) and install it as system app and reboot.
After reboot open play store and use it.
Will try to make it more simple ASAP

How can i get root permission?
On phoenixos release it doesn't have root access
Have your system image root access?

Hi
The file is not on MEGA (file no longer exist). Can you reup please?
Thanks

Almost there. I dont get the second last step "...and click on rebuild and install below". Where is "rebuild" option ?
Edit: Also I wasn't able to sign in after installing play store the first time, it just hung on "Just a sec...".

How long shall we wait?

Saeem said:
How long shall we wait?
Click to expand...
Click to collapse
I'm waiting for 1.5 - 2 months

arcsnim said:
I'm waiting for 1.5 - 2 months
Click to expand...
Click to collapse
Don't wait anymore. visit their website you will have the solution. :laugh::good:

Well this solution works but you get msg from YouTube or twitch telling you need play services. I think microg is not 100% compatible with all apps.
Here is what you can do assuming you're rooted:
install lucky patcher, download from apkmirror playservices and framework compatible with your hardware, run lucky and click on rebuild, go to your download folder, click on playservices and choose install as normal APK, not system app, don't reboot yet, choose now framework and install as system app, reboot and login to your account. I used it also with latest 7.1 64b.. Enjoy

Requirements
1) root
2)Magisk v14 or 14.3 app AND TWRP recovery for flashing
3)latest Google photo app from play store
4)android 7.0 to8.0
5) knowledge of flashing
Download files from This link
1) BY magisk module:
https://forum.xda-developers.com/on...photos-t3694140?_e_pi_=7,PAGE_ID10,7137433206
Installation Instructions
Copy the correct module as per your Magisk version to your phone's internal memory
Open Magisk Manager
Go to the Modules section
Click on the "+" Floating Button and select the module zip
Reboot
OR
2) BY recovery :
U can flash recovery flashable zip from this LINK AND reboot
https://forum.xda-developers.com/oneplus-3/themes/flashable-zip-google-lens-pixel-2-t3693859
Follow the instructions.....
https://youtu.be/omi9QD7ok-8
You have to take photo for which u want information and then go to google photo app and then open that image and use google lense for that....... It's tedious but useful
NOTE: I AM NOT RESPONSIBLE FOR ANY THING KEEP BACKUP

Before following this guide, you'll want to grab the MSM unbricking tool, specifically for this device (not the global or other Oneplus 8 versions). Use it if you brick yourself.
Here's how I got microG to work on my Visible Oneplus 8 running Oxygen OS 11:
Unlock the boot loader and flash Lineage's instantnoodle recovery (The small recovery image ~96MB, not the large rom file)
Reboot into recovery and adb sideload the Magisk zip file, from the recovery's 'Apply Update'.
Follow this guide to enable signature spoofing, but with the following few changes:
Place this specialized hook services file ( 11-hook-services-OxygenOS.jar.dex ) in the same folder as 11-hook-services.jar.dex.
When you get to the `java -jar` command in the guide, do this instead:
Code:
java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services-OxygenOS.jar.dex 11core-services.jar.dex
Do not install the microG provided in the guide! But go ahead and install your `spoof_AVDapi30.zip` through magisk as the guide says.
Confirm that signature spoofing is working (you can download Signature Spoofing Checker from F-droid)
Inside the magisk app, search for and install the plugin "microG installer Revived". Reboot.
Grant microG all the permisisons that you can in microG settings' Self-Check.
Tap and install GmsCore.apk located at '/system/priv-app/GmsCore/". You need to do this step even though its already installed because until you do this, it will only be installed as a system app. Doing this installs it as a user app, which fixes the location permission issue (somehow this issue is encountered). If it doesn't fix it right away you may need to reboot.
Open the microG settings again, and give yourself the location settings (and SMS if still needed)
I hope this helps someone. I know I had a lot of frustration because so much that works for other instantnoodles simply doesn't work on this device. Instantnoodle custom roms like lineageOS (as of writing this) and automated patchers like smali and nanodroid don't work, so at least we have this one option.

Ciao @Calebdvn
Trying to apply this fix on OP6 OOS11.1.2.2 but nothing happends
trying the standard method I were stuck at bootlogo, using this file the system volta, but, signature spoofing Is not working
Caould you kindly support me ?

As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"

Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?

Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?

Sus_i said:
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Click to expand...
Click to collapse
It works on Android 9, but on Mantis (4K with 7.1.2) dialog worked with Magisk 20.4 (old manager) and broken (don't have any focus so user can't press any button in it) with any Magisk 21+ and new Manager GUI

mamcho said:
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Click to expand...
Click to collapse
hm, it's apk from studio, tesed it on TWRP from Fire TV 4K and it installs fine. Try to disable digest check in TWRP options.

Im on sloane and disabling digets check doesnt change anything. I ve read that 24.3 is problematic for sloane. 23.0 works tho

Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
BTW: guys on magisk github page asnwer really bad to your suggestion, no reason to do that
The manager UI is not tv-friendly so it's really easy to press update by mistake. It was the 1st thing I though when I saw it after installation...

Noisemaker00 said:
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
Click to expand...
Click to collapse
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.

tsynik said:
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
Click to expand...
Click to collapse
So the steps are:
uninstall current magisk-manager version
download and rename your .apk to .zip
reboot to twrp and flash the zip
reboot the system
is it correct?

hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.

mamcho said:
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
Click to expand...
Click to collapse
Yes, probably it's some kind of bug in Magisk. When hiding, Magisk replaced with stub app, which download full apk from https://github.com/tsynik/Magisk/releases, but failing to load it's classes and initialize app context.
Fixed with v25.1.FTV release

tsynik said:
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Click to expand...
Click to collapse
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks

What I did was to rename .apk to .zip, flash with twrp. manager was not to be found on apps. then I manually installed the .apk and it appeared on apps.

yakovperelman69 said:
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
Click to expand...
Click to collapse
I am having the same issue
BTW to uninstall rename the apk to uninstall.zip then flash it in twrp

I have a tank (2nd gen stick) with latest firmware (5.2.9.5 at time of writing)
Now that Magisk v26 has dropped support for android 5, it would be wise to release a final version for old fire sticks.
Anyway the UI does not start at all, both on your fork and on the original v25.2 . (and, both of them do not remember superuser permissions - they get asked every time)

I just tried to flash Magisk v26.1 via TWRP. FireOS6 (mantis - FTV4K)
First fresh Kernel followed by Magisk v26.1.zip.
All seams to work but I noticed that the repacking step went unusual fast!
After rebooting and updating Magisk app to v26.1 it seams to work.
But now I get after a fresh start/reboot a warning message in Magisk app that an reflash is necessary!
I now went back to 25.2 (again Kernel + Magisk.zip) and all is good again.
I do not know what happens here or if something went wrong or if 26.1 is not fully compatibe to FireOS6 (Android 7)...
Anyway - Just wanted to let you all know.

Hello guys,
ive been using magisk module of ios emoji (from here) just fine on 1.1.7. Then I updated on 1.1.8 (via OTA method - lost root, fastboot booted patched boot.img - rooted again) and the module suddenly stopped working - simply doesnt appear anywhere. I tried to delete it, install it again, reboot device, but no luck. Tried even different modules of iOS emojis, still not working.
My ionly other module Fullscreen/immersive gestures is working fine after the update. Magisk app updated on thle latest version.
Any idea what could be the issue?
Thank you!

Try this: https://forum.xda-developers.com/t/...dex-facebook-samsung-twemoji-windows.3418801/
Create Magisk Module and Flash it over Magiskt, the internal flash method from app is not working properly.
If its not working download FX File Manager > Grant Root and delete all Folders in \Root\data\fonts\files
Restart your phone and you should get the iOS Emoji's. It could be that you need to delete these folders in \files again after the next Gboard Update

paper88 said:
Try this: https://forum.xda-developers.com/t/...dex-facebook-samsung-twemoji-windows.3418801/
Create Magisk Module and Flash it over Magiskt, the internal flash method from app is not working properly.
If its not working download FX File Manager > Grant Root and delete all Folders in \Root\data\fonts\files
Restart your phone and you should get the iOS Emoji's. It could be that you need to delete these folders in \files again after the next Gboard Update
Click to expand...
Click to collapse
You're a life saver, thank you so much, I really appreciate it, worked perfectly!

paper88 said:
Try this: https://forum.xda-developers.com/t/...dex-facebook-samsung-twemoji-windows.3418801/
Create Magisk Module and Flash it over Magiskt, the internal flash method from app is not working properly.
If its not working download FX File Manager > Grant Root and delete all Folders in \Root\data\fonts\files
Restart your phone and you should get the iOS Emoji's. It could be that you need to delete these folders in \files again after the next Gboard Update
Click to expand...
Click to collapse
I couldn't get it to work no matter what procedure I tried to follow. Currently running on 1.1.7 with the 16.4 beta magisk module but I have zero luck.
I just noticed that I'm a beta tester of GBoard. Can it have an impact? Not sure if anyone tried it with Beta version.