[ROOT][MANTIS][FIRESTICK 4K] Custom Launcher Support and System Patches - Fire TV General

CUSTOM LAUNCHER HANDLER
(FIRESTICK 4K) - 6.2.9.0
​This is a method to enable certain features disabled/blocked by Amazon, and this method does require TWRP to be installed on the device.
This does not require any root access so you don't need to have Magisk Installed on your device.
This does require you to have a patched system boot image (boot.img) installed on the device, there are two ways of doing that.
Flash the patched boot.img (attached below) to boot partition of your device using TWRP (DO NOT USE HACKED BL/FASTBOOT). Magisk can be flashed after it if you want root access.​
Install Magisk, magisk will patch the boot.img​
As always backup your device before modifying it, in case anything goes wrong just flash the rom again without wiping anything, it will revert all the changes made to your device.
Features:
Unblocks 3rd Party Accessibility Service Access
Enables AppWidget support
Disables OOBE forced updates
Disable System OTA Updates
Gives option to remove Package Protection from individual Amazon Apps
Allows you to set any app as Custom Launcher
Root / Magisk is not required
Displays and gives option to stop Recent Apps and Background Apps
No Boot delay on using a custom launcher
Full voice search support with any third party launcher
Supports rebooting to recovery (Without root / adb)
Requirements:
Unlocked Bootloader
TWRP Access
Patched Boot Image (Either Flash the attached boot.img or just install Magisk) Not required but recommended
FireOS version 6.2.9.0
Instructions:
Flash Patched boot.img (Recommended)
Open TWRP, Click Install > Select the Patch File > Swipe to Flash.
Clean Cache/Dalvik Cache and Reboot (First boot will take some time)
Upgrading FireOS using TWRP:
download latest bin file. (e.g. mantis.bin)
download some archive tool (e.g. 7-zip)
rename the bin extension to zip (e.g. mantis.zip)
open "mantis.zip" using "7-zip" and delete all folders from zip file
now open "Scripts.zip" and extract it (download from attachment)
put the extracted folder "META-INF" into "mantis.zip"
put patched boot.img into "mantis.zip"
flash the "mantis.zip" using TWRP
Tutorial: https://youtu.be/GOOLxsSUQJo
Demo:
INFO:
Double Tap [Home] twice to open CLH shortcut menu (only works when CLH is enabled)
System will send com.wolf.action.DOUBLE_TAP_HOME, com.wolf.action.LONG_BACK_PRESS when Home is pressed twice and when back button is long pressed. (it will also create a home event), you can disable then using "settings put secure CL_DISABLE_HANDLE_BACK_LONG_PRESS 1" and "settings put secure CL_DISABLE_HANDLE_HOME_DOUBLE_TAP 1" using adb shell. Disabling DOUBLE TAP using this will also disable CLH menu. you can listen to those broadcast by creating broadcast listeners.
To disable protected apps using adb shell or by Debloat Toolbox, first you will need to uncheck those apps from "Procted Packages" from CLH shortcut menu.
OTA are disabled but if you still encounter issues just clear run this in adb shell "pm uninstall com.amazon.device.software.ota" to clear any updates to the app itself and then clear settings app using "pm clear com.amazon.tv.settings.v2" to clear its database.
If you don't have root and are not able to use ADB (and has removed TWRP bootmenu), you can use CLH's "Reboot to Recovery" option to reboot to TWRP. It doesn't use ADB or Root.
If you want to exclude some app from Permissions check just add android:sharedUserId="com.sween.wolf" in the manifest of that app.
SCREENSHOTS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[RESERVED]

[RESERVED]

[RESERVED]

Wow, this great work! I love the new features.
But everything is either Plus or Max these days. It should be 'Launcher Manager Plus' or 'Launcher Manager Max'

Can you make anything like this for firestick lite?

Tejas tedi said:
Can you make anything like this for firestick lite?
Click to expand...
Click to collapse
Without a device i will not be able to test the patches. I don't want to make someone's stick a paperweight.
Maybe I will create a version but will not be able to maintain it.

How I can set unlocked bootloader on the stick?

SweenWolf said:
I don't want to make someone's stick a paperweight.
Click to expand...
Click to collapse
Nothing to worry about as long as the preloader is untouched
and maybe a bit easier, since there isn't an efuse to keep from burning
Finnzz said:
It should be 'Launcher Manager Plus' or 'Launcher Manager Max'
Click to expand...
Click to collapse
--> Launcher Manager Pro Plus +

Can i use it for old firmware??

Thank you for your hard work! I'm having a problem with my FireStick after I flashed patch 6.2.9.0 my stick won't boot anymore . It just gets to the FireTV loading screen and doesn't get any further. What can I do?

Zerollama said:
Thank you for your hard work! I'm having a problem with my FireStick after I flashed patch 6.2.9.0 my stick won't boot anymore . It just gets to the FireTV loading screen and doesn't get any further. What can I do?
Click to expand...
Click to collapse
Have you flashed patched boot image?

anphabvn said:
Can i use it for old firmware??
Click to expand...
Click to collapse
You shouldn't, your stick will bootloop

SweenWolf said:
Have you flashed patched boot image?
Click to expand...
Click to collapse
Thank you, yeah I had flashed the boot image too. I ended up reflashing my stick with the full firmware and it's booting again now. I'll stick to the regular the Launcher Manager for now.

@SweenWolf can you create Wolf Laucher Manager with root supported? Old LM use adb only to work !!!

del...

Related

[A70B/IT2 HC][3.2.81 update] Enabling SDE and rooted firmware package

First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.
*reserved*
Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!
Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again
LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.
Hi mrew42,
Thanks a lot! Much appreciated!
Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81
Letama, can you may be make the same for 3.2.81?
Yes, it will come soon...
3.2.81 is up and instructions on first post updated if you upgrade.
Great
http://www.jbmm.fr/?p=27601
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!
Thanks, will try it out soon.
Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.
ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.
I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?
No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!
lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.

[Root] Found working chinese root (need translation)

There is a working Chinese root tutorial over on the BB board of Zuk.cn. Can someone translate it? Just downloading the files.
http://bbs.zuk.cn/z2/t116621/
There was a post in zukfans.eu community where SuperSU and xposed packages were shared. If you have TWRP installed then you could flash these, but I can't confirm that because I don't have the phone (yet). If you try these, then please share how it went.
(as a new member I can't post a link yet but you can find it under "ZUI 2.0 ROM (Development & Multi Language)" department in Zukfans.eu)
I can confirm that this root is working with Zuk Z2 pro
Anyway i can help with providing boot.img etc?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
iceagezero said:
I can confirm that this root is working with Zuk Z2 pro
Anyway i can help with providing boot.img etc?
Click to expand...
Click to collapse
The Chinese guide is a translation of the Italian guide with translated twrp. If a device is able to flash twrp you can simply install SuperSu and gain root.
No you can't you need this modified supersu! And after that I had to reinstall the normal supersu. To Grant su rights
Unlock bootloader in this web site:
http://developer.zuk.com/bootloader_2
Use this command:
adb reboot bootloader
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
fastboot -i 0x2b4c oem unlock-go
Click to expand...
Click to collapse
Download "recovery-TWRP-3.0.2-20160712-ZUK_Z2-CN-wzsx150.img"
Link: http://pan.baidu.com/s/1bpjyaXx code: 225n
Use this command to flash recovery:
fastboot.exe -i 0x2b4c flash recovery recovery-TWRP-3.0.2-20160712-ZUK_Z2-CN-wzsx150.img
Click to expand...
Click to collapse
It must return "OKAY".
Reboot and get into recovery:
adb.exe reboot revocery
Click to expand...
Click to collapse
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
Unlock bootloader will erase all your data include internal storage...
@iMaeGoo
Thanks for the instructions!
Is the TWRP you link to any different to the one found at zukfans.it/2016/07/10/disponibile-twrp-per-zuk-z2-pro/ (sorry, I‘m not allowed to post links yet) ?
@all
Which SuperSU do I have to use? Can I just use the one from download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip ? Or do I have to use another one? Because @iceagezero talked about a modified one.
Thanks!
Tek5 said:
@iMaeGoo
Thanks for the instructions!
Is the TWRP you link to any different to the one found at zukfans.it/2016/07/10/disponibile-twrp-per-zuk-z2-pro/ (sorry, I‘m not allowed to post links yet) ?
@all
Which SuperSU do I have to use? Can I just use the one from download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip ? Or do I have to use another one? Because @iceagezero talked about a modified one.
Thanks!
Click to expand...
Click to collapse
1. Your "Disponibile TWRP per ZUK Z2 Pro" is for Z2 Pro(Z2121), and my "TWRP-3.0.2-20160712-ZUK_Z2-CN-wzsx150.img" is for Z2(Z2131), it's different, don't flash the wrong one.
2. You can get Root access in TWRP, it includes the newest SuperSU Pro 2.76, you can find it in "Advanced" in TWRP, you can also download ZIP and install it.
iMaeGoo said:
1. Your "Disponibile TWRP per ZUK Z2 Pro" is for Z2 Pro(Z2121), and my "TWRP-3.0.2-20160712-ZUK_Z2-CN-wzsx150.img" is for Z2(Z2131), it's different, don't flash the wrong one.
2. You can get Root access in TWRP, it includes the newest SuperSU Pro 2.76, you can find it in "Advanced" in TWRP, you can also download ZIP and install it.
Click to expand...
Click to collapse
Thanks for your answers!
1. Do you also have one for Z2 Pro, or is ist also totally fine to use the one I linked to?
2. Is this by default included in the current TWRP versions or is this a special feature of your version you linked to?
Tek5 said:
Thanks for your answers!
1. Do you also have one for Z2 Pro, or is ist also totally fine to use the one I linked to?
2. Is this by default included in the current TWRP versions or is this a special feature of your version you linked to?
Click to expand...
Click to collapse
Here it is: http://bbs.zuk.cn/z2/t116639/ (for Z2 Pro Z2121)
Download link: http://pan.baidu.com/s/1o88eesM Code: 6i5j
* delete redundant languages, keep English, add Chinese language, default chinese.
* modify the default configuration, such as the default time zone for the East eight area, the default screen brightness, the default shock, default 24, the default return button in the right, the default Chinese, and so on.
* modify the default configuration file path, so that you can reduce the possibility of conflicts with other compiled versions.
The adjustment and optimization of Chinese characters and *, re modify all items one by one comparison, more accurate and understandable, user-friendly. Also added to enable the closure of the display MTP display, file operation results show that the operation of the page title display, modify permissions, and so on the rights of the text display UI.
* modify unlock interface, adjust the slide to unlock a highly. Only in this way can effectively prevent the misoperation (original unlock and unlock a highly consistent and unlock at the end of may repeat sliding to direct the operation of the corresponding action).
* unlock more partitions of backup and restore, such as modern baseband partition, splash boot screen partition, partition TZ, RPM, bootloader, persist, and OEM, convenient brush before the underlying backup file, brush but also restore the underlying file.
* add the.Bin and.Mbn format image files to the brush, so that you do not need a zip brush pack, as you can brush to write the underlying file. The original only supports.Img format image file brush. (must pay attention to the election of the partition!!!!!)
* solve the use of analog operation, the interface card die bug (analog operation is mainly used to test the theme, not the actual operation).
* add manually install supersu features in the advanced options >root system. Twrp comes with the root way is to brush the completion of each restart, if the system does not have root, he will prompt root. On this basis to add a display of the root system options to facilitate the manual operation.
* modify built-in root, add latest supersu (2.76) for the latest finished crack version (from the network, thanks to dusty), and add the root of Android version 6.0 system support.
* fix some buttons and buttons on the interface to operate, and add the support of the home button on the bottom of the phone. Press the home key to correspond to the home button.
* default open adb/usb debug mode, in rec mode to facilitate the operation of the phone through the computer command line
* MTP is enabled by default, under the condition of rec mobile phone can also be connected to the computer, convenient file copy and.
* modify the logo interface, the main interface to modify the page header, Zuk Z2 Pro Zhuanban display and joined the team name, author name.
* fix some logical relations, modify some of the interface display, the temporary repair page Center shows the mouse bug.

Sense Ui For Mi MAX

Sense Ui For Xiaomi Mi MAX
Disclaimer-
Code:
Follow the steps correctly otherwise you may brick your device.
It will erase all your data, so we advise you first to take a complete backup of your phone and then proceed.
Ensure that your phone has at least 50-60% charged to prevent the accidental shutdown in-between the process.
hit thanks if this helpful For You
Whats working-
Everything-
htc camera
htc gallery
htc launcher
htc internet
htc music
htc widget
htc video
htc file manager
hotspot widget
htc location service
weather[not work]
Note- You can install and update all apps from play store, because it detect your Device as htc10 or m9[ according build prop values]
Requirements-
A Rooted Device with cm or cm based Rom installed
custom Recovery
200MB free space in system
Always Step by Step Bcz i am a Blogger too-
1. htc apps installation-
First of all Download htc apps From bellow
Put Downloaded Zip into Root of sd card
Reboot Device into recovery[twrp]
Clear catch , dalvik catch
on Recovery Click on install zip from sd card Navigate Downloaded htc apps zip file
Confirm install, wait for success
Go back and reboot System Now,
2. Flashing htc framework, htc Camera, htc gallery-
Download htc Zip file From Bellow and transfer into Device storage/-internal/external
reboot into recovery [twrp]
Clear catch Dalvik catch,
on Recovery Click on install zip from SD card
Navigate Downloaded htc Zip file and Confirm install, wait for success
Go back/ reboot system Now Done,
3. Flashing Boot logo/splash screen-
Download htc Boot Logo For mi MAX From below{ this is not tested on mi max, RS- 1080px1920] you can create own htc logo HERE
and paste in adb folder
open cmd on adb folder
Connect your phone to pc via usb with usb debugging enabled
type adb reboot bootloader to boot device into fastboot mod,
then type fastboot flash splash htcsplash.img to flash splash img
Done type fastboot reboot
4. Flashing Bootanimation-
Download htc Bootanimation from Bellow
Run Root explorer and Replace stock boot animation in system/media folder
set permission
Done,
5. Changing build prop values-
Go to system folder and edit build.prop file
replace values like this
For htc 10-
ro.product.model=MSM8996 for arm64
ro.product.brand=htc
ro.product.name=pmewl_00531
ro.product.device=htc_pmewl
ro.product.board=msm8996
ro.product.manufacturer=htc
for htc M9-
ro.product.device=htc_himauhl
ro.product.name=himauhl_htc_europe
ro.product.manufacturer=htc
ro.product.model=HTC One M9
ro.product.brand=htc
6. Changing Imei-
Install xposed framework according your Device
Download install and enable this module [xposed imei changer] from xposed/module
reboot Device
run xposed imei Changer and replace origenal imei by htc m10 imei[we can't offer this]
Done,
7. Changing UI-
Download and Install this Theme[sense ui] From bellow
Run theme manager and apply sense ui theme
Done reboot Phone,
8. Change Android iD-
Change android id using android id Changer,
9. Done-
XN Logos said:
Sense Ui For Xiaomi Mi MAX
Disclaimer-
Code:
Follow the steps correctly otherwise you may brick your device.
It will erase all your data, so we advise you first to take a complete backup of your phone and then proceed.
Ensure that your phone has at least 50-60% charged to prevent the accidental shutdown in-between the process.
hit thanks if this helpful For You
Whats working-
Everything-
update-
Theme Now Working, You can Use Different Color for Binkfeed up to 30 Color available which is work for all htc app,
Photo Editor Now working, update gallery app from play store,
Weather now Working, update app From play store, Don't update other apps otherwise it cause force Close,
message App working, Direct use From play Store,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Great. Will try
Fabulous effort Bru
Weather is not working ...it force closes every time ...tested on Dave himself RR 7th august rom

Android O, Busybox, ElementalX, Root, Suhide WORKING!

As of right this second 9/13/2017 i have gotten SuperSU ElementalX kernel, SUHide and Busybox working, and YES it survives reboot
Instructions that i used
Flash new September Factory image
Boot phone setup password.ect
reboot using the modified TWRP.img in the other thread here"
Flash Boot.img to both slots from September Factory update
Flash ElementalX, SuperSu.zip and SUHide.zip reboot
when phone loads up installed meefik's Busybox
changed install path to /system/bin
and unselected replace existing applets
and BOOM BABY
ENJOY
let me know if it works for you guys
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ne0ns4l4m4nder said:
As of right this second 9/13/2017 i have gotten SuperSU ElementalX kernel, SUHide and Busybox working, and YES it survives reboot
Instructions that i used
Flash new September Factory image
Boot phone setup password.ect
reboot using the modified TWRP.img in the other thread here"
Flash Boot.img to both slots from September Factory update
Flash ElementalX, SuperSu.zip and SUHide.zip reboot
when phone loads up installed meefik's Busybox
changed install path to /system/bin
and unselected replace existing applets
and BOOM BABY
ENJOY
let me know if it works for you guys
Click to expand...
Click to collapse
Glad to hear this is working for you, it's not really anything that hasn't been covered in more depth in other threads / guides...
As a note; You would only lose root, if you flashed a kernel, but didn't flash SuperSU after && or by installing busybox into the wrong location or by replacing the system applets...
Personally, I install busybox into /sbin/supersu/bin because it has the advantage of not touching the /system partition at all - so for example; I can flash a a full factory image (rather than OTA), using flash-all script (removing the -w argument to not wipe data) and retain busybox.
Cheerz
Have you got any advice about viper/arise? I just need it and than I'm good to go :good:
TENN3R said:
Have you got any advice about viper/arise? I just need it and than I'm good to go :good:
Click to expand...
Click to collapse
Not really, no. I don't use viper or arise. I would say read through the related threads on them. There is bound to be good instructions.... sometimes I read through the comments, in particular; the last couple of pages on a given thread, as sometimes there is useful information.
I pretty much have a similar setup to your device, plus substratum and a few other root apps and tweaks. (Fdroid, adaway, afwall, etc).
Good luck.
Is there a difference in flashing the boot.img versus flashing the image minus the -W? I've been trying and trying but I always end up with boot loops and it going back to stock recovery. Usually the boot Loops start right away when I'm first rebooting the system. Last night I got Elemental and root installed it worked fine for about 30 minutes then started bootlooping and ended up at stock recovery again.
I used Busybox v1.27.2 from osm0sis
What I do:
- Flash the September update (I do a full wipe)
- Boot up, finesh the setup and set a pin
- boot modded twrp
- Enable MTP and copy the Files (BusyBox v1.27.2, EX Kernel 2.0.1, SuperSU v2.82 SR3 & Suhode v1.0.8)
- Flash EX Kernel, SuperSU, Suhide and BusyBox
- reboot and enjoy
PS: passing with Substratum is also no problem
Flash sr4 to prevent bootloop: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Sent from my Pixel using Tapatalk
trying to apply adaway seems to remove root and break twrps ability to mount /data
KittyRgnarok said:
trying to apply adaway seems to remove root and break twrps ability to mount /data
Click to expand...
Click to collapse
Adaway was giving me problems too. Started using Brave browser and haven't looked back. https://www.brave.com/
Installing busybox in /system/bin didn't work for me. Flashing Busybox from osm0sis did.
brownkid said:
Installing busybox in /system/bin didn't work for me. Flashing Busybox from osm0sis did.
Click to expand...
Click to collapse
Use meefix busybox not stericson
Droid1019 said:
Adaway was giving me problems too. Started using Brave browser and haven't looked back. https://www.brave.com/
Click to expand...
Click to collapse
This is the best adblocker for android, it uses dns block lists like pi-hole and root isn't needed since it uses the vpn interface:
https://f-droid.org/packages/org.jak_linux.dns66/
Sent from my Pixel using Tapatalk
Stericson Busybox has been updated for Android O.
https://forum.xda-developers.com/pixel-xl/how-to/busybox-oreo-t3672140/page2
Droid1019 said:
Adaway was giving me problems too. Started using Brave browser and haven't looked back. https://www.brave.com/
Click to expand...
Click to collapse
Adaway works great if you change the "Target hosts file" to "/data/data/hosts"
I installed the updated Stericson Busybox to /sbin/supersu/xbin and all working great.
KittyRgnarok said:
trying to apply adaway seems to remove root and break twrps ability to mount /data
Click to expand...
Click to collapse
I disagree, I dont have a problem with adaway.
TENN3R said:
Have you got any advice about viper/arise? I just need it and than I'm good to go :good:
Click to expand...
Click to collapse
Viper4arise does work but only with the older release...for me at least. I tried many times and ways with magnumopus and it wouldn't work. Using the 2.94 deurotomy aroma installer it's installed and processing.
devilsadidas said:
Viper4arise does work but only with the older release...for me at least. I tried many times and ways with magnumopus and it wouldn't work. Using the 2.94 deurotomy aroma installer it's installed and processing.
Click to expand...
Click to collapse
Same here. At least we have something
devilsadidas said:
Viper4arise does work but only with the older release...for me at least. I tried many times and ways with magnumopus and it wouldn't work. Using the 2.94 deurotomy aroma installer it's installed and processing.
Click to expand...
Click to collapse
To which older release of viper4arise are you referring to?

Fire TV Tank 5.2.8.2 OTA Zip

Download:
Updated to 668700420
Fire TV Tank 5.2.8.2 OTA Zip 668700420.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it the new UI?
Yes new Ui
0815hoffi said:
Yes new Ui
Click to expand...
Click to collapse
How (good/bad) is it working? Do you like it?
For me it works good, but i have disabled the Amazon Launcher ;-)
Sus_i said:
How (good/bad) is it working? Do you like it?
Click to expand...
Click to collapse
tank with the new UI is laggy as hell, compared to the "old" UI.
Ok, then I'll skip this update^^
I guess they want to drive us into the trade-in of all the older (unlocked) fire TV devices^^
They offer $3.00 for every tank, sloane, bueller and even the cube. Lol.
Thats a really awesome offer
Someone here should make a new thread about this opportunity
Amazon Trade-In: Get Paid for Your Used Items
Trade in Fire tablets, Kindle E-readers, streaming media players, and more for an Amazon.com Gift Card.
www.amazon.com
0815hoffi said:
For me it works good, but i have disabled the Amazon Launcher ;-)
Click to expand...
Click to collapse
Hello, I have a rooted fire stick (tank) with build 5.2.7.3. I too have disabled Amazon Launcher and replaced it with ATV launcher and Markus Firetools for settings.
Prime Video app used to work fine but since two days it is showing 'error code 8056' though the app version is matching to the one on the app store. More over it is forcing to update the OS. I tried clearing data, cache, updating the app through app store but it did not work.
Is it safe to update to 5.2.8.2 build through magisk to fix this error? Will it loose root access? Will it blow the efuse and lock the bootloader? I'm much worried about that. Pls clarify.
Edit: I have blocked and disabled the OTA updates as well. So it stays on 'Checking now' on the update screen.
Enable ota Updates over ADB and you can pass the update Screen. Then disable it again.
Yes you have root if you have flashed magisk.
But there is anything changed from Amazon, you can delete System Files, but can not write to system "no space left".
I think Amazon dynamic resizes the System Partition, currently i have found no solution for that.....
Maybe @Sus_i have a idea for that.
Can I allow ota access and let it update automatically to 5.2.8.2 or flash the zip manually through twrp? What's the correct way?
I would Flash manual over twrp ( Flash Firmware and Magisk ) and then allow ota.
0815hoffi said:
I would Flash manual over twrp ( Flash Firmware and Magisk ) and then allow ota.
Click to expand...
Click to collapse
Ok, what version of magisk is suitable for this device? Can I just rename the Magisk-v23.0.apk → Magisk-v23.0.zip and install it through twrp?
Use 20.4, 23 not working without mouse to accept root request.
20.4
kjay7 said:
Prime Video app used to work fine but since two days it is showing 'error code 8056'
Click to expand...
Click to collapse
Same here.
Will try to disable updates completely somehow and check what happens than...
EDIT: has somebody tried to completely remove the updater APKs, instead of just disabling them?
Should be (tank):
Code:
com.amazon.tv.forcedotaupdater.v2
com.amazon.device.software.ota"
com.amazon.device.software.ota.override
0815hoffi said:
But there is anything changed from Amazon, you can delete System Files, but can not write to system "no space left".
I think Amazon dynamic resizes the System Partition, currently i have found no solution for that.....
Click to expand...
Click to collapse
Remount the system r/w doesn't work?
Guys, here's the thing. I have wiped system, data, cache and installed 5.2.8.2 and magisk 20.4 through twrp. After the initial boot, did the basic setup. Noticed something weird with the prime video app. When I open the app or say 'open prime video' through alexa, it throughs the error code 8056 and says update required. Where as when I say 'search prime video' or 'search <movie>', the prime video app opens successfully and doesn't show any error! How can this be fixed?
BTW the build installed is 5.2.8.2 but on the update screen 5.2.8.0 is shown as new update!
Sus_i said:
Remount the system r/w doesn't work?
Click to expand...
Click to collapse
Remount works, same on TWRP "No space left on device"
I can delete but not write.
I have noticed this problem, i don't really need write access on my Stick.
But it is funny.
Maybe its a Problem with my Stick or Amazon has changed anything. ;-)
See Log-File
kjay7 said:
Guys, here's the thing. I have wiped system, data, cache and installed 5.2.8.2 and magisk 20.4 through twrp. After the initial boot, did the basic setup. Noticed something weird with the prime video app. When I open the app or say 'open prime video' through alexa, it throughs the error code 8056 and says update required. Where as when I say 'search prime video' or 'search <movie>', the prime video app opens successfully and doesn't show any error! How can this be fixed?
BTW the build installed is 5.2.8.2 but on the update screen 5.2.8.0 is shown as new update!
Click to expand...
Click to collapse
Make all Updaten and then disable OTA.
Maybe you must flash tz.img like the 4K Stick.
I have no Amazon Prime, so i can´t Test it.
0815hoffi said:
Remount works, same on TWRP "No space left on device"
I can delete but not write.
Maybe its a Problem with my Stick or Amazon has changed anything. ;-)
Click to expand...
Click to collapse
Just tried it from fireOS 5278 via adb shell and yeah, same here, no space left...
Edit: I thought maybe no free inodes, tried to run 'df -i' but no avail
Edit2: More than enough inodes free on system.
Is it possible for you to upload 'Fire OS 5.2.8.0 (668694820)' ota zip file? Though 5.2.8.2 is installed on the device, it is fetching 5.2.80 from the amazon server as an update and prompting to install that version. Can't install that from Firestick UI, so I need the zip file.

Categories

Resources