Database Users

Zpad v.1029 Clean

If coming from a GTab build, you must wipe data/cache. Otherwise you will have FC's or UID mismatches.
This is an update.zip full update to Zpad v.1029. Based off Roebeet's build with Market and Google apps. Flashes system, (Bekits clockwork 0.7)recovery, and boot.
Rooted
Removed all unusable apks.
Removed zpad launcher, replaced with Launcher2.apk
Added Gallery3D
Added Music Mod
Added Superuser, su, and busybox
-v0.2-
0.8 Clockworkmod recovery thanks to Bekit
More stock apps: email, deskclock, search
Working YouTube
Dolphin HD browser
Applanet(full market)
Updated superuser.apk
Build.Prop tweak for UI
TapNTap keboard
-v0.3-
Fixed Live Wallpaper
Stock Settings via gmcbay
Android boot animation
Removed blackmarketapp, easily found and not in the purpose of this build
-1106 boot.img (flash over 0.3)-
Fixes time/date reset issue
Some ZPad applications remain that aren't terrible, and browser because it is tied with framework. This is stable, no wifi issues, and fast. Let me know if you have any problems.
{
"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"
}
0.1 Download: OLD
0.2 Download: OLD
0.3 Download: http://www.megaupload.com/?d=ST5E1F63
1106 boot.img: http://www.megaupload.com/?d=6YUAG5IV
Installation:
Place update.zip in sdcard.
Run update.zip from clockworkmod recovery.
If running zpad or gtab recovery, unpack recovery.rar to sdcard. Then reboot in recovery mode by holding + and power.
Recommended Changes:
Speed up animations in spareparts
Speed up scrolling in advanced if using LauncherPro

Saved for additional growth.

I didn't see the link to v.1029 but I did see it over at tegratabs. Also you mention in the post over there that flash does not work? does that mean the flash apk from the folio does not work with this build... that would keep me from installing from the 1106 update...
And lastly just to echo so many others, Thanks for your hard work on tracking this stuff down and packaging it up... you have really helped make an unusable device quite awesome.
...John.

eagle17 said:
I didn't see the link to v.1029 but I did see it over at tegratabs. Also you mention in the post over there that flash does not work? does that mean the flash apk from the folio does not work with this build... that would keep me from installing from the 1106 update...
And lastly just to echo so many others, Thanks for your hard work on tracking this stuff down and packaging it up... you have really helped make an unusable device quite awesome.
...John.
Click to expand...
Click to collapse
Sorry, that is from early on when we did not have the flash apk. Maybe I'll add that to a new build if I get a chance. I have been working on getting the next version of zpad which should have flash stock.
You can definitely use flash on zpad if you add it yourself.

Do I need to flash .01 thru .03 and the 1106 or just .03 and the 1106?
Also over at tegra.com board there is a very easy way to flash clockwork onto this badboy, it is the last post in the clockwork thread posted by photonmedia

I think if you use the v.1029 update.zip it has everything... otherwise I did the .3 and then the 1106.. and then just copied the flash apk and ran it to install it.
I am very happy with this so far... very stable
@Rothnic ,
is the v.1029 the same as 1106 update?
thanks

Links are temporarily unavailable

I'm having a problem with the 1106, it is saying that the boot.img is corrupt and wrong crc #? Anyone know what to do?

bjn813 said:
I'm having a problem with the 1106, it is saying that the boot.img is corrupt and wrong crc #? Anyone know what to do?
Click to expand...
Click to collapse
what steps are you using?
what are you flashing from ?
are you using cwm?

Yes I'm CWM 8, I'm using the install from sdcard then choose update.zip, I choose the one I want. Then it says "assert failed: package_extract_file("boot.img", "/tmp/boot.img")
Error in sdcard/update.zip
(status 7)

bjn813 said:
Yes I'm CWM 8, I'm using the install from sdcard then choose update.zip, I choose the one I want. Then it says "assert failed: package_extract_file("boot.img", "/tmp/boot.img")
Error in sdcard/update.zip
(status 7)
Click to expand...
Click to collapse
It sounds like something is messed up with either the update or clockwork. I'd try reapplying clockwork recovery and redownloading the update.zip.

eagle17 said:
I think if you use the v.1029 update.zip it has everything... otherwise I did the .3 and then the 1106.. and then just copied the flash apk and ran it to install it.
I am very happy with this so far... very stable
@Rothnic ,
is the v.1029 the same as 1106 update?
thanks
Click to expand...
Click to collapse
v.1029 is a total package of v.1029 boot.img plus system.img. Zpad Clean 0.3 is just a cleaned up version of this total package.
I only have the 1106 boot.img at the moment that still works with the v.1029 system.img. I am working on getting the whole 1106 firmware.
One option you can do is take the 1106 boot.img and paste it into the update.zip for v.1029 Zpad Clean 0.3.

rothnic said:
One option you can do is take the 1106 boot.img and paste it into the update.zip for v.1029 Zpad Clean 0.3.
Click to expand...
Click to collapse
That is what I tried and that is where I get the error that it is corrupt and the bad CRC #(all 0's) using winrar. I am using my work computer and if you know about Altiris it won't even let me use the Altiris Image Explorer on it the boot.img

hopefully here someone can help me out, anyone got a link to that specific task manager, i cant seem to find it on the market?

Wipe Data/Cache
I'm sure this is obvious to many of you, but what exactly is meant by "you must wipe data/cache"? What specific action do I need to take -- is there a menu option in recovery mode or is this something I need to do from the Settings menu in the TapNTap interface?

biffripken said:
I'm sure this is obvious to many of you, but what exactly is meant by "you must wipe data/cache"? What specific action do I need to take -- is there a menu option in recovery mode or is this something I need to do from the Settings menu in the TapNTap interface?
Click to expand...
Click to collapse
in clockworkmod recovery these are things you do before flashing a new rom.

Got it now, don't know what was going on with it going on my computer to tablet. I just downloaded straight to tablet and moved the zip to the root of the internal sdcard and it worked. Also has anyone ran benchmark with this rom cause I did and its not very good 525. Anymore possible tweaks/lag fix coming?

bjn813 said:
Also has anyone ran benchmark with this rom cause I did and its not very good 525. Anymore possible tweaks/lag fix coming?
Click to expand...
Click to collapse
i think that has to do with the drivers being young - the tegra2 hardware is really new. the only other rom that is "fast" is cyanogenmod and i don't think it will bench much higher.

bjn813 said:
Got it now, don't know what was going on with it going on my computer to tablet. I just downloaded straight to tablet and moved the zip to the root of the internal sdcard and it worked. Also has anyone ran benchmark with this rom cause I did and its not very good 525. Anymore possible tweaks/lag fix coming?
Click to expand...
Click to collapse
That shouldn't be a quadrant score. Those tend to be in the 1800+ range.

1106
Sorry for the Noob question but how exactly to I "flash" the 1106 boot.img file? I've successfully installed the v.03 update and everything's fine except the time/date resets on reboot. Just can't seem to figure out how to do the next step
Also, has anyone tried the Subsonic app? Can't get it to work on this version although it did work on TnT Lite. It's the best app I've seen so far for streaming music from my home server, both home and away on all our devices (iTouch, DX, and now Gtab.)
I do appreciate the hard work everyone on these forums has provided with customizing this tab and helping with problems. Man this tablet would be 100x better if some of the folks on this forum and the tegra forum were involved in getting this tab developed. Here's hoping that Viewsonic provides us with a decent firmware update.
Tony

PhilZ Touch 6.59.0-CWM 6.0.5.1 Micromax A120

CENTER]Head to the Main thread for full feature list
http://forum.xda-developers.com/showthread.php?t=2201860[/CENTER]
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something.
I have tested maximum stuff and it works fine
{
"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"
}
Instruction​Flash the recovery via sp flash tool(RECOMMENDED)
Can use Mobile uncle tools from PlayStore also.
Download​Custom Kernel Thread : http://forum.xda-developers.com/android/general/kernel-xpro-custom-kernel-micromax-a120-t2977089
Credits
@Phil3759 Main developer Source
@yuweng For his tutorials
@mr-illusionist For testing

Is this a KITKAT recovery?

Yes jellybean as well as KitKat

Hi.
Thank you for this good recovery! I'm using it from this rom: http://forum.xda-developers.com/android/general/rom-wiko-kitkat-rom-mmxa120-clones-t2981756
But, I have found two bugs:
1) USB don't work at all. It's possible to fix it? I like to have ADB access in the recovery.
2) The option for "Re-root System (superSU)" don't work. I executed it multiple times, boot to Android, download SuperSU, but then the program says "no su binary available". You know why this function don't work?
Regards!

manos78 said:
Hi.
Thank you for this good recovery! I'm using it from this rom: http://forum.xda-developers.com/android/general/rom-wiko-kitkat-rom-mmxa120-clones-t2981756
But, I have found two bugs:
1) USB don't work at all. It's possible to fix it? I like to have ADB access in the recovery.
2) The option for "Re-root System (superSU)" don't work. I executed it multiple times, boot to Android, download SuperSU, but then the program says "no su binary available". You know why this function don't work?
Regards!
Click to expand...
Click to collapse
SuperSu will not work as i have removed su binary to reduce size of the recovery. And about adb access I dont have device so didnt try will confirm with someone

Siddhesh.K15 said:
SuperSu will not work as i have removed su binary to reduce size of the recovery. And about adb access I dont have device so didnt try will confirm with someone
Click to expand...
Click to collapse
Ok,
So please, can you publish two different versions? One with su binary and one without. Then the user can select if it's partition maps has sufficient space.
Related to USB port. How I can access to shell with this recovery? From the mobile, from USB, from wifi, or whatever... ?

manos78 said:
Ok,
So please, can you publish two different versions? One with su binary and one without. Then the user can select if it's partition maps has sufficient space.
Related to USB port. How I can access to shell with this recovery? From the mobile, from USB, from wifi, or whatever... ?
Click to expand...
Click to collapse
I would have never removed su if the recovery partions is of size more than 6 mb but unfortunately it is of 6mb only and su binaries in recovery are old u can SuperSU zip and get root access LINK
If you are using kk rom then i will advice u to use Superuser instead of supersu. because supersu fails to elivate some permissions in mtk kk roms.
And for access try usb otg

Siddhesh.K15 said:
I would have never removed su if the recovery partions is of size more than 6 mb but unfortunately it is of 6mb only and su binaries in recovery are old u can SuperSU zip and get root access LINK
If you are using kk rom then i will advice u to use Superuser instead of supersu. because supersu fails to elivate some permissions in mtk kk roms.
And for access try usb otg
Click to expand...
Click to collapse
Ok,
Related to SuperSU, I recommend to remove the option in the recovery or put a mode when the su binary is loaded from the SD card, like the load of the Aroma FileManager.
In reference to USB, don't work at all! If I try in the Philz to enable "usb otg" it don't work. What I can do?
Thank you!

Hi,
Because no posts about fixing the USB problem. Plase, can the author publish the source code of this port?
Thank you!

Android 7.0 & Systemless Root (CTS fail)

SOLVED - Flashed suhide (linked in post 2) leaving this here for anyone else that struggles
Hi all, I'm trying to get Systemless root working with Android 7.0.
In the developer previews it was still passing CTS, as Android Pay was fully working; however now that "full" android 7.0 has been released my device is failing CTS profile match as soon as I flash SuperSU (2.77 or 2.78).
I've even tried the old ways of using the old commands in TWRP terminal
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
I'd like to be able to use Android Pay on 7.0, but still have root functionality for things like Tasker.
Is there any way to get it working currently?
(other than Magisk, I don't want to have to open an app, disable root, use android pay, go back to Magisk, enable root every single time.. Kinda defeats the point of android pay being easy to use)

Have you checked out suhide by Chainfire? I'm still on 6.0.1 but it passes safetynet now. Google has changed the detection so even systemless root fails now. I haven't had s chance to use AP for a purchase though. Others state in this thread that it works.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
Sent from my Nexus 6P using XDA Labs

swallowingled said:
Have you checked out suhide by Chainfire? I'm still on 6.0.1 but it passes safetynet now. Google has changed the detection so even systemless root fails now. I haven't had s chance to use AP for a purchase though. Others state in this thread that it works.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
Success! Thank you, I'll give AndroidPay a try and edit this to let you know

pk92 said:
Success! Thank you, I'll give AndroidPay a try and edit this to let you know
Click to expand...
Click to collapse
I'm very curious as well, let us know either way!

It was all working well for a couple of days by now SafetyNet has a "Response payload validation failed"
{
"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"
}
I've been unsuccessful in googling, and AndroidPay is no longer functioning.

pk92 said:
It was all working well for a couple of days by now SafetyNet has a "Response payload validation failed"
I've been unsuccessful in googling, and AndroidPay is no longer functioning.
Click to expand...
Click to collapse
Yeah sadly everyone is getting that now with suhide. Like chainfire said, it'll be a never ending cat and mouse game. Have you tried Magisk by any chance yet? http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I have not but it looks like people have been able to get it to work using that. With it you can unmount root temporarily and supposedly Android Pay works at that point.

DanRyb said:
Yeah sadly everyone is getting that now with suhide. Like chainfire said, it'll be a never ending cat and mouse game. Have you tried Magisk by any chance yet? http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I have not but it looks like people have been able to get it to work using that. With it you can unmount root temporarily and supposedly Android Pay works at that point.
Click to expand...
Click to collapse
Magisk is really a last resort, I'd rather not have to open the app, unroot, use AP, open magisk, and reroot every time I need to make a payment. It kind of defeats the point of the convenience of Android Pay

pk92 said:
Magisk is really a last resort, I'd rather not have to open the app, unroot, use AP, open magisk, and reroot every time I need to make a payment. It kind of defeats the point of the convenience of Android Pay
Click to expand...
Click to collapse
I hear ya but I think this is going to be the norm. It won't be easy to have root AND Android Pay play nicely side by side. Not when big banks are involved. Google has to do all they can to stop it.
May I ask what you use root for? Only reason is because I too like to use Android Pay but like making a few modifications to my system, namely the Emoji font file, system font file, custom ad-blocking hosts file and an overlay file. I manually make all my changes to /system in TWRP and none of them trip up SafetyNet/Android Pay.
Of course if you're using actual apps that require root, my solution won't work for you.

DanRyb said:
I hear ya but I think this is going to be the norm. It won't be easy to have root AND Android Pay play nicely side by side. Not when big banks are involved. Google has to do all they can to stop it.
May I ask what you use root for? Only reason is because I too like to use Android Pay but like making a few modifications to my system, namely the Emoji font file, system font file, custom ad-blocking hosts file and an overlay file. I manually make all my changes to /system in TWRP and none of them trip up SafetyNet/Android Pay.
Of course if you're using actual apps that require root, my solution won't work for you.
Click to expand...
Click to collapse
+DanRyb would mind telling me how you use TWRP to install say system fonts, etc? While I generally root, I'm enjoying Pay on stock for now, but would like to make a few mods also. Thanks.

jackpollard said:
+DanRyb would mind telling me how you use TWRP to install say system fonts, etc? While I generally root, I'm enjoying Pay on stock for now, but would like to make a few mods also. Thanks.
Click to expand...
Click to collapse
I do it manually through adb command line but you could use a flashable zip too if you find one with the font you like. If making manual changes through adb, just boot into TWRP, go to Mount and make sure you check off /system. Fonts are all in /system/fonts. I replace a bunch of the Roboto*.ttf ones with a font I found like over a year ago. I also replace the emoji font with a custom one of my own which is NotoColorEmoji.ttf.
I'm not sure exactly WHY yet but it seems a custom kernel is needed to respect the changes I made. I attempted last night with just a simple modified boot image that removed the force encryption but all the changes I made in /system I couldn't see once booted. After I installed a custom kernel (I use ElementalX), I was able to make my changes and actually see them. I'm not sure if it has to do with dm-verity or not but I'm still learning as I go. Obviously I can't tweak any of the custom kernel settings using an app (since I don't have root installed) but for me that's OK.

DanRyb said:
I do it manually through adb command ....
Click to expand...
Click to collapse
Thanks for the details, I think I will make a nandriod and play a bit. Again, thanks!

I use root for Tasker, TiBu, AdAway, SDMaid, Nova Launcher (for quicker pull down)

[Q] Safety net issues / temporarily deactivating SU

Hi
Are there any knows workarounds on how to pass safety net? I'm running LineageOS 15.0, and just tried logging into Snapchat - failed. Guess that's the safety net working.. Anyone have any ideas on how to get around this?
Thanks,
- H

hhaznadar85 said:
Hi
Are there any knows workarounds on how to pass safety net? I'm running LineageOS 15.0, and just tried logging into Snapchat - failed. Guess that's the safety net working.. Anyone have any ideas on how to get around this?
Thanks,
- H
Click to expand...
Click to collapse
Always search:
https://forum.xda-developers.com/showthread.php?p=72138574

smitharro said:
Always search:
https://forum.xda-developers.com/showthread.php?p=72138574
Click to expand...
Click to collapse
Thank you for your response. Yes, I should have mentioned that I did do some research prior to posting, but the results I found, all either (as you link to) required Magisk SU, or (official?) CyanogenMod/LineageOS based ROM's (as shown here: https://labs.xda-developers.com/store/app/com.bhb27.isu ).
The reason I posted my question being that I am using SuperSU and the unofficial LineageOS 15.0 by vache (https://forum.xda-developers.com/g5-plus/development/rom-lineageos-15-0-t3673573 ), and therefore - by all definitions - am not eligible for any of those solutions.
But you're right - I should've made that clear. Tho, one could make the argument that you also could've made ur point in a slightly less presumptuous, arrogant and wannabe superior way
- H

hhaznadar85 said:
Thank you for your response. Yes, I should have mentioned that I did do some research prior to posting, but the results I found, all either (as you link to) required Magisk SU, or (official?) CyanogenMod/LineageOS based ROM's (as shown here: https://labs.xda-developers.com/store/app/com.bhb27.isu ).
The reason I posted my question being that I am using SuperSU and the unofficial LineageOS 15.0 by vache (https://forum.xda-developers.com/g5-plus/development/rom-lineageos-15-0-t3673573 ), and therefore - by all definitions - am not eligible for any of those solutions.
But you're right - I should've made that clear. Tho, one could make the argument that you also could've made ur point in a slightly less presumptuous, arrogant and wannabe superior way
- H
Click to expand...
Click to collapse
Didn't intend to be arrogant. Sorry for giving you that impression. I'm using Los 15 by vache too. In 'the old days' I used SuperSU, but, imho, that's outdated. Magisk has become the new standard for me, in combination with the safeteynet fix, it's perfect. It passes the safeteynet and you can download and use all 'root critical' apps like Pokémon Go, Netflix, Snapchat, 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"
}

smitharro said:
Didn't intend to be arrogant. Sorry for giving you that impression. I'm using Los 15 by vache too. In 'the old days' I used SuperSU, but, imho, that's outdated. Magisk has become the new standard for me, in combination with the safeteynet fix, it's perfect. It passes the safeteynet and you can download and use all 'root critical' apps like Pokémon Go, Netflix, Snapchat, etc.
View attachment 4297590
Click to expand...
Click to collapse
No problem
Cool, thanks. I have been away from "the android game" for some years, but have just recently got this Moto G5.. so yea, I don't really know what's "new" in the world of android customization. When I was doing this last time, it was all about Superuser, CM, Xposed framework, and apps like 4ext, a2sd, titanium, etc.. the old times..
Anyways, thank you for the update. A quick question; what would you recommend as the best procedure for switching over to Magisk - can I just flash it over the SuperSU, or would you recommend the whole big backup and clean re-install approach..?
- H

Well, imho you have 2 basic options.
1. Make a Titanium Backup, go to TWRP, wipe cache, dalvik-cache, system and data. Reinstall LOS15, gapps and magisk. After setting up your device reinstall your apps using Titanium Backup. Install the safeteynet fix AFTER the first boot with magisk installed. So basically this is a clean install.
2. Go to TWRP. Wipe just the system partition. Reinstall the rom, gapps, magisk and, after a reboot, the Safetynet fix. All your apps should still be there... No garantee, but it should work.
Good luck!

smitharro said:
Well, imho you have 2 basic options.
1. Make a Titanium Backup, go to TWRP, wipe cache, dalvik-cache, system and data. Reinstall LOS15, gapps and magisk. After setting up your device reinstall your apps using Titanium Backup. Install the safeteynet fix AFTER the first boot with magisk installed. So basically this is a clean install.
2. Go to TWRP. Wipe just the system partition. Reinstall the rom, gapps, magisk and, after a reboot, the Safetynet fix. All your apps should still be there... No garantee, but it should work.
Good luck!
Click to expand...
Click to collapse
Hehe yea, that was pretty much what I was thinking as well.. think I'm gonna go with option 1 - better safe than sorry..
Thanks a lot for your help!
- H

[ROOT][MANTIS][FIRESTICK 4K] Custom Launcher Support and System Patches

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...