Database Users

[root]KindleFire HD 8.9 without computer tested and working

Alright, to start I have tested this and am currently using my rooted Kindle Fire with CM11. I also must say that this has only been used on my Kindle Fire HD 8.9, and I haven't tried it with the 7in variant, and I teccomend that you do not try it either. Also, I am not responsible in any way if you brick your device of mess it up any way otherwise. You must follow this procedure completely, no skipping anything at all. Let's begin.
1. Enable the function to install apps from unknown sources
2. Enable ADB debugging
3. Download Aptoide, install, and open
4. Search for vRoot, download, install, and open it
5. If an ad pops up, close it. There should be a green button that says "download apk". Note that this does not appear without ADB debugging enabled. Download the app and install it. This will grant you superuser access. However, you still don't have TWRP.
6. Open Aptoide, download and install supersu and supersu pro
7. To get TWRP, I used seokhun's guide here: http://forum.xda-developers.com/showthread.php?t=2277105, while skipping step 1
This method works as of August 02, 2014, 22:00. If you have any questions just ask.

HD or HDX?
Bigmaclover30 said:
Alright, to start I have tested this and am currently using my rooted Kindle Fire with CM11. I also must say that this has only been used on my Kindle Fire HD 8.9, and I haven't tried it with the 7in variant, and I teccomend that you do not try it either. Also, I am not responsible in any way if you brick your device of mess it up any way otherwise. You must follow this procedure completely, no skipping anything at all. Let's begin.
1. Enable the function to install apps from unknown sources
2. Enable ADB debugging
3. Download Aptoide, install, and open
4. Search for vRoot, download, install, and open it
5. If an ad pops up, close it. There should be a green button that says "download apk". Note that this does not appear without ADB debugging enabled. Download the app and install it. This will grant you superuser access. However, you still don't have TWRP.
6. Open Aptoide, download and install supersu and supersu pro
7. To get TWRP, I used seokhun's guide here: http://forum.xda-developers.com/showthread.php?t=2277105, while skipping step 1
This method works as of August 02, 2014, 22:00. If you have any questions just ask.
Click to expand...
Click to collapse
Is this post in the right place?

mullinsd5 said:
Is this post in the right place?
Click to expand...
Click to collapse
Not even close.
@OP
Please take this down so people don't try this on their HDX's and end up with an unrepeatable brick.

r3pwn said:
Not even close.
@OP
Please take this down so people don't try this on their HDX's and end up with an unrepeatable brick.
Click to expand...
Click to collapse
I would like to say that I did not post my thread here. It was moved. It works on the HD but not HDX (that I know of). I didn't post this here so I'm sorry for the confusion.

This guide, including the handoff for twrp and cm11 worked great for me. The root process was fool proof!! Thank you. CM11 is great on the HD 8.9.

ADB problem KFHD 8.9
hello, i have KFHD 8.9 with root. Now i want install TWRP. I have installed ADB and is functionally, i can run much codes, for example "adb shell getprop". But when introducing code for backup for my Kindle, show me this message: "[-] no such file or directory". Help, please.
{
"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"
}

Unable to download apks anymore
Amazon performed a system update that no longer allows me to download apk files. The option to download apps from unknown sources is clicked on. I always check to make sure. Before this update, I had no trouble downloading apps or apk files. I factory reset my kindle fire 10 3 times, and the damn update is still there. How can I root my kindle? I don't own a computer, and I can't download apks anymore. HELP!!

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)

[FIX] How to install Google+ (Google Maps Framework/App Incompatible With Device Fix)

I discovered a solution on how to make Google+ work on Phoenix OS. This might enable other apps to work as well, please report your findings.
Instructions:
Download and extract maps-framework.zip
Download latest Google+ APK (I used v9.18.0: APKMirror | Google Drive)
Using Root Explorer or a root file manager of your choice:
Copy com.google.android.maps.xml from the extracted folder and paste it into /system/etc/permissions. Perform a chmod of 644 on the file
Copy com.google.android.maps.jar from the extracted folder and paste it into /system/framework. Also perform a chmod of 644 on the file
To perform chmod in Root Explorer, click and hold on a file, click on the three menu buttons, click on Permissions, press Enter Octal, type in 644, and finally press OK twice. If you're using another root file manager, I could imagine the steps would be similar.
Restart Phoenix OS
Install Google+ APK that you downloaded earlier
Optional: If you want to update it to the latest version, open up the Play Store and update Google+ there.
How I discovered this solution is by trying to install Google+ APK through Lucky Patcher. When I tried to install it, it gave me this error message:
{
"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 performed a Google search on "Google Plus install failed missing shared library" and came up with these results which guided me to this solution:
https://forums.xamarin.com/discussion/2378/install-failed-missing-shared-library
http://www.slatedroid.com/topic/25334-fixing-the-install-failed-missing-shared-library-error/
https://forum.xda-developers.com/showthread.php?t=1382925
Here's proof that it works:

Astounding work. Thank you so much!

Did you get it to work on your device?

Reinstalling Phoenix and testing today...
Edit: worked like a charm! Also discovered that it would work using the "nodpi" version of G+
It won't recognize that the device is compatible to install it through the Play Store, but it will allow manual installation from APKMirror ^.^
You are a gawd walking amongst mere mortals, good sir.

The Wrath of Kahn said:
Reinstalling Phoenix and testing today...
Edit: worked like a charm! Also discovered that it would work using the "nodpi" version of G+
It won't recognize that the device is compatible to install it through the Play Store, but it will allow manual installation from APKMirror ^.^
You are a gawd walking amongst mere mortals, good sir.
Click to expand...
Click to collapse
Thanks for the findings And yeah, initially you have to install it manually, but after you restart your device, you will be able to update it from the Play Store to the new version. And I'm just a regular human, like you and anybody else that's on these forums

meanhacker said:
Thanks for the findings And yeah, initially you have to install it manually, but after you restart your device, you will be able to update it from the Play Store to the new version. And I'm just a regular human, like you and anybody else that's on these forums
Click to expand...
Click to collapse
And humble to boot
Anyway, I'll keep testing, but I suspect several failed installs are due to this same reason... we shall see.

The Wrath of Kahn said:
And humble to boot
Anyway, I'll keep testing, but I suspect several failed installs are due to this same reason... we shall see.
Click to expand...
Click to collapse
Cool, hopefully everything works out for you What failed installs did you mention?

At this point I don't recall specifically which others didn't install, but I'll keep you posted if I run into any more.

The Wrath of Kahn said:
At this point I don't recall specifically which others didn't install, but I'll keep you posted if I run into any more.
Click to expand...
Click to collapse
Sounds good. If I have to, I will also try to experiment modifying the model number in build.prop and see what benefits that will bring. Also, I read online somewhere that installing an older version of Google+ might work without having to copy those two files into /system. I might experiment it if the time is right

hey thank you for the info, now i cant install instagram because i get "your device isnt compatible with this aplication", so, if i follow this steps maybe i can install instagram right? i already try install instagram from external apk (downloaded from internet but doesnt work correctly, the app get stuck at white screen and never load) :crying::crying:

BEST27 said:
hey thank you for the info, now i cant install instagram because i get "your device isnt compatible with this aplication", so, if i follow this steps maybe i can install instagram right? i already try install instagram from external apk (downloaded from internet but doesnt work correctly, the app get stuck at white screen and never load) :crying::crying:
Click to expand...
Click to collapse
Give it a try and see if it lets Instagram install. The worst that can happen is you will be able to install Google+

@meanhacker have you tried any newer gms versions to see if they allow syncing for more apps? I suspect that it's locked down by the devs due to China's restrictions.

lollyjay said:
@meanhacker have you tried any newer gms versions to see if they allow syncing for more apps? I suspect that it's locked down by the devs due to China's restrictions.
Click to expand...
Click to collapse
I think I did, but it keeps saying that there was an error parsing the package... I will test out more. What about you?

meanhacker said:
I think I did, but it keeps saying that there was an error parsing the package... I will test out more. What about you?
Click to expand...
Click to collapse
No luck with anything newer so far.

Thank you
Thank you so saved my life awesome hit

thankyou222 said:
Thank you so saved my life awesome hit
Click to expand...
Click to collapse
I'm glad it helped you! Did you use this fix to make Google+ work or some other application?

Samsung pay on watch when rooted

Hello, I have a new one plus 8 pro and I am rooted. I also have a Galaxy watch and when I install Samsung pay on the watch it says call customer service device has been compromised even though I have magiskhide for all the Samsung modules. Does anyone have any ideas how to get this working?
Thank you in advance...

I have the same problem. Completely stock. So I wonder if it's a Samsung issue. I had the 6t rooted and I was able to use Samsung pay without any problems

Okay, I think I found the answer. In magisk settings, you need to rename the package to something else. It is the third option down in settings. After I change the name it worked like a charm and of course you have to hide the for Samsung modules in magiskhide...

aaronc_98 said:
Okay, I think I found the answer. In magisk settings, you need to rename the package to something else. It is the third option down in settings. After I change the name it worked like a charm and of course you have to hide the for Samsung modules in magiskhide...
Click to expand...
Click to collapse
Is this still working for you? It's definitely not working on my end with my Pixel. The newest Magisk Manager also does not allow you to select any apps to hide, it's a simple toggle on or off for Magisk Hide and renaming the Magisk Manager didn't do anything.
Did you have to reboot after the rename?

Valiante said:
Is this still working for you? It's definitely not working on my end with my Pixel. The newest Magisk Manager also does not allow you to select any apps to hide, it's a simple toggle on or off for Magisk Hide and renaming the Magisk Manager didn't do anything.
Did you have to reboot after the rename?
Click to expand...
Click to collapse
Sorry - the Pixel was like 4 phones ago. I dont have any further info for you...

aaronc_98 said:
Okay, I think I found the answer. In magisk settings, you need to rename the package to something else. It is the third option down in settings. After I change the name it worked like a charm and of course you have to hide the for Samsung modules in magiskhide...
Click to expand...
Click to collapse
UPDATED Post : see next post for my solution that worked.
Hi aaronc_98,
Hope this is actually still working for you on your OP8 Pro!
When you say you need to rename the package, what are you referring to exactly?? The Samsung Pay app or Hide the Magisk App (renaming) in App settings?
Please provide more details on a step-by-step process you did to make it work on your OP device...if still working.
I have OP6T and it has stopped working recently and can't find a way to get back.
My setup:
OP6T, OOS 10.3.11
Galaxy Watch 46mm, latest OS installed (Jun 15, 2021)
Galaxy Wear App, SPAY Watch Plugin up to date. (Jun 15, 2021).
Thanking you in advance!

plepew said:
Hi aaronc_98,
Hope this is actually still working for you on your OP8 Pro!
When you say you need to rename the package, what are you referring to exactly?? The Samsung Pay app or Hide the Magisk App (renaming) in App settings?
Please provide more details on a step-by-step process you did to make it work on your OP device...if still working.
I have OP6T and it has stopped working recently and can't find a way to get back.
My setup:
OP6T, OOS 10.3.11
Galaxy Watch 46mm, latest OS installed (Jun 15, 2021)
Galaxy Wear App, SPAY Watch Plugin up to date. (Jun 15, 2021).
Thanking you in advance!
Click to expand...
Click to collapse
UPDATE,
Got it all to work!
Preparation:
- Install Galaxy Wearable
- Update Watch to the latest
- Install SP Watch Plugin (do not launch it at all)
Magisk Setup:
- Hide the following apps in MagiskHide: Hit the shield, Hit "MagiskHide" and select the apps:
a) Google Play Services
b) Samsung Health
c) SP Watch Plugin
* You can add banking apps here as well
{
"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"
}
Next, recommend hiding the Magisk App itself for the setup. Here is how to do it:
- Hit "Settings" (within Magisk App)
- Hit "Hide the Magisk App" (I used MGKSettings).
Magisk will accept it and repopulate itself.
For good measure, I rebooted my device to recovery (TWRP in my case) wiped "Dalvik / ART Cache" and rebooted to system.
Once rebooted, go to the SP Watch Plugin App INFO (Do not launch the App), got to Storage & Cache & Clear Storage & Cache (should be 0 on both) for good measure!
Launch Galaxy Wear and (Strongly Recommended) scroll down to setup Samsung Pay and follow the steps. **(I don't recommend doing the SPay setup through the Watch Plugin.)**
If you get a notice within 10 seconds saying that the device is not secure (can't remember the message), you may have missed something and you need to start over with clean install of the SP Watch Plugin (storage & cache cleared).
Worst case they may have updated the Samsung Pay, Samsung Health Apps & OOS and it's been blocked again. Therefore we would need to restart the whole process from scratch or find another workaround.
PS. Some of you would probably like to restore or Un-Hide the Magisk App, so I went ahead and did it....so far SPay seems to be working. I have not reboot my device neither, which I rarely do. (I have rebooted my device several times since this post)
For any reason, in the coming days, there is an issue of any kind, I will report back here. If not, it's all good!
Hopefully this can help some of you out there!

worked for me, thanks a lot

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