yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] hasobist:
Hello @SweenWolf !

Happy to have you back!

Thank you loads for all your time,support,work and contribution much much appreciated.

As always Love the Wolf Launcher, Alas the much long awaiting patch update is back.

As it's a Magisk Module ,can work on any firmware,is it?

Latest firmware has blocked apps from using adb.

Post in thread 'Update blocks apps from using ADB -- NS6702/5093 -- PS7668/4007 -- RS8103' https://xdaforums.com/t/update-bloc...5093-ps7668-4007-rs8103.4657266/post-89360265

Thank you once again........

Cheers!
[Fire TV Android Development] SweenWolf:
Thanks

It is not a magisk module, maybe one day I make one. except "fossettings.odex" and "settings.odex" all the other files most likely will work on any other firmware. but these two files will not work if theres too much changes in the files, like if you flash these two files in upcoming firmware it will work, but if amazon has added some critical code to these two apps in future and the device searches for then your device WILL stuck in bootloop, so these two may or may not work work in future unless myself or some other tweaks it.

I will look into it but as I have only one working Amazon device I may wait for the update to come to Firestick 4K or it depends.

And I forgot to patch protection in this build, update coming right up
[Fire TV Android Development] SweenWolf:
AdepFOS patch for Blacklist disabling
[Fire TV Android Development] SweenWolf:
UPDATE: Fixed Protected Package, OP Updated.

Sadly bricked my Mantis again, now in preloader, will have to reunlock. Hopefully its not dead.

UPDATE: All good
[Fire TV Android Development] hasobist:
Hello @SweenWolf !

Thank you for your prompt reply,much appreciated.

The Magisk Module will be great, a universal patch.

Thank you loads for all........

Cheers!
[Fire TV Android Development] hasobist:
Hello!

Oh okay ain't good.Faced it many times ,luckily was back whenever re-unlocked:)

Thank you........

Cheers!
[Fire TV Android Development] Skel40:
This would be in front of AdepFOS? I can make a script for this

Thank you!
[Fire TV Android Development] Skel40:
@SweenWolf, I have compiled all the patches you have including CLH, com.amazon.tv.forcedotaupdater.v2, com.amazon.tv.launcher, com.amazon.tv.settings.v2, com.amazon.venezia, com.amazon.vizzini, DeviceSoftwareOTA, PackageInstaller as root priv-app with proper scripting. I kept the settings and launcher at lower versions to prevent the ad banner as the home selection upon bootup.
[Fire TV Android Development] SweenWolf:
ok.

If you just want to test it, just do a normal install of the app from any file manager (The rom must have CLH Patches). you don't have to push any app to the system. I mean it was treating Launcher Manager as Harmful app :LOL:
[Fire TV Android Development] nomobytes:
Here is the latest update with the local adb killer code-

https://d1s31zyz7dcc2d.cloudfront.prod.ota-cloudfront.net/2024/2/1/8dfc5e57-2993-4b1b-9bf2-fb5e31910317/update-kindle-mantis-NS6702_user_5093_0010034079108.bin
[Fire TV Android Development] Skel40:
I'll take a look at this firmware for changes. Thanks for the .bin
[Fire TV Android Development] crazyazz:
I take it if your on this firmware you can no longer access root to follow your guide?
[Fire TV Android Development] Skel40:
If on stock with stock recovery after 6.2.8.1, no chance. Rooting isn't available anymore after unlocking since 6.2.8.1. 6.2.8.1 was the last known firmware to allow the micro usb kamakiri unlock. I noticed this new update is outside com.amazon.adep operations. There's an unknown system file causing this adb blockage. Studying what happened is needed, stay on 6.7.0.1 if not already.
[Fire TV Android Development] crazyazz:
Thanks for the reply, I'm new to the firestick so its too late for me. I'm on this evil new firmware, found out when I got sick of the amazon launcher and found out they blocked ABD app usage 🥹
[Fire TV Android Development] Skel40:
03-03 17:33:48.048 236 592 I qdqservice: QService::getAutoMode
03-03 17:33:48.052 236 592 I qdqservice: QService::getAutoMode
03-03 17:33:48.063 236 592 I qdqservice: QService::getAutoMode
03-03 17:33:48.077 1414 1414 I kso.PM.GenericPlacement: reportEventsToService - reporting 1 events to service.;
03-03 17:33:48.095 236 236 I hwcomposer: [PLTC] planeAlpha = 77
03-03 17:33:48.095 236 236 I hwcomposer: [PLTC] planeAlpha = 77
03-03 17:33:48.112 236 236 I hwcomposer: [PLTC] planeAlpha = 133
03-03 17:33:48.112 236 236 I hwcomposer: [PLTC] planeAlpha = 133
03-03 17:33:48.128 236 236 I hwcomposer: [PLTC] planeAlpha = 179
03-03 17:33:48.129 236 236 I hwcomposer: [PLTC] planeAlpha = 179
03-03 17:33:48.145 236 236 I hwcomposer: [PLTC] planeAlpha = 211
03-03 17:33:48.145 236 236 I hwcomposer: [PLTC] planeAlpha = 211
03-03 17:33:48.162 236 236 I hwcomposer: [PLTC] planeAlpha = 233
03-03 17:33:48.162 236 236 I hwcomposer: [PLTC] planeAlpha = 233
03-03 17:33:48.179 236 236 I hwcomposer: [PLTC] planeAlpha = 245
03-03 17:33:48.179 236 236 I hwcomposer: [PLTC] planeAlpha = 245
03-03 17:33:48.195 236 236 I hwcomposer: [PLTC] planeAlpha = 252
03-03 17:33:48.195 236 236 I hwcomposer: [PLTC] planeAlpha = 252
03-03 17:33:48.212 236 236 I hwcomposer: [PLTC] planeAlpha = 254
03-03 17:33:48.212 236 236 I hwcomposer: [PLTC] planeAlpha = 254
03-03 17:33:48.314 236 262 I qdqservice: QService::getAutoMode
03-03 17:33:48.427 769 1013 W bt_btif : bta_hh_le_input_rpt_notify uuid=0x2a4d srv_handle=79 is_bl_svc_primary=1 rpt_id=1 len=3
03-03 17:33:48.428 607 652 I AmazonProfileService: Reporting top activity: ComponentInfo{com.wolf.apm/com.wolf.apm.ShellActivity}
03-03 17:33:48.428 607 652 I AmazonProfileService: Event is not filtered because it is not in filter key list.
03-03 17:33:48.428 607 652 I FireTVKeyPolicyManager: Dynamic key mapping has been enabled
03-03 17:33:48.429 607 652 I KeyMapManagerUtil: Unknown remote sku id 0. Fetch remote sku id from system property

services.jar/services.odex?
[Fire TV Android Development] Skel40:
That sucks..there's no luck on stock.
[Fire TV Android Development] crazyazz:
Yea makes me sick, I always had control of my devices in the past. Might have to look for something else on principal alone. Only hope I suppose is a work around is discovered to get ADB back for apps.
[Fire TV Android Development] Skel40:
Yes it does...your best luck is swapping the device for an exchange or get a different device. 6.7.0.2 is a kill switch for adb. I consider this as the end of Fire TV customization. It was nice having control....now its gone forever...blocking updates is recommended
[Fire TV Android Development] Skel40:
@SweenWolf 6.7.0.2 smali for services.jar. I extracted the classes.dex after extracting services on Apktool
[Fire TV Android Development] dashriprock007:
Looks like Amazon did something to block clearing OTA updates on 6.7.0.1 I get an error

SecurityException: Cannot clear data for a protected package: com.amazon.device.software.ota

When trying to clear the OTA...TDUK 's OTA clearer doesnt work anymore =(
[Fire TV Android Development] hasobist:
Hello!

Is your stick unlocked and rooted?

Cheers!
[Fire TV Android Development] dashriprock007:
No its not., i thought a while back these wernt able to be rooted
[Fire TV Android Development] SweenWolf:
First I'll have to flash 6.7.0.2 I think.
[Fire TV Android Development] SweenWolf:
Yeah, they comes under Protected Packages.

It will only work if you have CLH installed, which requires TWRP.
[Fire TV Android Development] Skel40:
6.7.0.2/5093 No Magisk/Magisk Rom. CLH is added with OTA patches for now and an updated TZ.
[Fire TV Android Development] dimelotu:
worked for me. Thanks both!
[Fire TV Android Development] Skel40:
You're welcome!! More updates are on the way. 👍
[Fire TV Android Development] DarkZone-World:
Hi,

i have a big problem. After install i can‘t login to my account. What can i do?

Maybe Amazon blocked my Stick?
[Fire TV Android Development] hasobist:
Hello @DarkZone-World !

What did you install and which firmware version are you on?

Cheers!
[Fire TV Android Development] DarkZone-World:
I installed 6.7.0.2 from 6.2.8.1.
[Fire TV Android Development] hasobist:
Hello @DarkZone-World !

Try deregister and re-register,if you ain't wiped data while installing the rom.

If it ain't works,login into Amazon and deregister all your devices ,sometimes flashing roms we exceed the limit.

Hope it helps!

Cheers!
[Fire TV Android Development] DarkZone-World:
Thanks for your help, i‘ve deregister but i can‘t reregister :( After login it says username or password is incorrect. I tryed to disable oobe but without login the stick is not useful.
[Fire TV Android Development] hasobist:
Hello @DarkZone-World !

Did you try restoring the data after flashing the rom, normally it breaks registration sometimes remote as well?

Try clearing /data,cache and dalvik and flash magisk if on root and complete the OOBE set up.

If ain't works,

If it's okay, why not try clean install.

Wipe /system,cache,dalvik and data

Flash rom followed by magisk and then busybox optional and complete the OOBE set up.

Should get resolved.

If it doesn't, less chances from your Amazon account go to manage devices or so and deregister all of them or the ones you feel are linked to your stick.

Let me know how it goes.

Cheers!
[Fire TV Android Development] SweenWolf:
Can you rollback to 6.7.0.1?

Your remote might get unpaired, reset by pressing home button for 10 seconds

Since you cannot login, clear data, cache, Dalvik cache before installing rom
[Fire TV Android Development] DarkZone-World:
Did you mean rollback to 6.2.8.1? When i try this than i stuck on setupscreen checking for updates, then the Message comes failed checking. This Part i can‘t skip.
[Fire TV Android Development] SweenWolf:
Either compile the rom by yourself by following OP https://xdaforums.com/t/root-mantis...port-and-system-patches.4461275/post-87068393

Or flash precompiled from https://xdaforums.com/t/fire-tv-stick-4k-1st-gen-mantis-rom.4298357/post-85253401

And I meant 6.7.0.1 because that's the latest version which is supported by CLH
[Fire TV Android Development] hasobist:
Hello @DarkZone-World !

can you boot into TWRP?

Cheers!
[Fire TV Android Development] DarkZone-World:
I will try this. Thanks!

Yes TWRP work fine.
[Fire TV Android Development] DarkZone-World:
View attachment 6079268

I tryed to flash 6.7.0.0 and stuck at this screen. I can‘t login. :(
[Fire TV Android Development] hasobist:
Hello @DarkZone-World !

Just answer all the questions asked properly, helps troubleshoot problems.

How did you flash the rom/Did you follow the instructions of wiping data as well before flashing the rom?

Good to go with Skels patched 6701.

Cheers!
[Fire TV Android Development] DarkZone-World:
Yes i wiped data befor flashing. I‘ll try now 6701.
[Fire TV Android Development] DarkZone-World:
So now i've installed 6701 but the same problem, i can't login. When i double press home CLH is opening. What can i do?
[Fire TV Android Development] hasobist:
Hello @DarkZone-World !

Try a clean install wipe /system,cache,dalvik,cache

Install skels patched rom 6701 followed by magisk

Clear /cache,dalvik and reboot

Let me know how it goes.

Cheers!
[Fire TV Android Development] hasobist:
When in CLH popup click the first option to activate CLH and the second option to select your launcher (from the options of apps)

Cheers!
[Fire TV Android Development] DarkZone-World:
Nothing really works. I can't install an apk either. Without a login everything seems useless.
[Fire TV Android Development] DarkZone-World:
I spoke to Amazon. They send me a new Stick. Anyway, thanks for the Help.
[Fire TV Android Development] hasobist:
Hello @DarkZone-World !

So your stick was blacklisted ,due to the delivery issues hence you were issued a new one isn't it?

Wonder when did you purchase the stick and unlock as well.

If your stick is blacklisted ,you can still use it and download third party apps.

Feel the new delivered is patched with the latest firmware and can't be unlocked.

Anyways keep the old unlocked ,which can be used when Lineage OS is released for firetv 4k.

Happy to help........

Cheers!
[Fire TV Android Development] DarkZone-World:
I bought the stick last November. I have some hope to unlock the new one :D
[Fire TV Android Development] nomobytes:
Nice work @SweenWolf.

Before applying your patch I updated to 6.7.0.2 stock firmware rooted with Magisk 27.0 under embedded TWRP 3.6.1_9-0 with stock launcher. Then I noticed that MouseToggle version 1.12 would be stuck in the 'starting' mode following a power cycle and requires manual intervention to bring it up (either from the Mobile app or a remote adb shell command sequence:

/data/local/tmp/.mousetoggle/nmouseg stop
/data/local/tmp/.mousetoggle/nmouseg start &

Of course, if you are on a rooted device you can issue the above commands from a local shell as you don't require local adb commands, but this reliance on manual intervention is unacceptable and not practical in many use cases. So here is what I did-

1. Rebooted to recovery

2. Flashed stock 6.7.0.1 under TWRP

3. Flashed your 6.7.0.1 patch file (btw Magisk is not included in your zip as implied in your OP)

4. Flashed Magisk 27.0

5. Wiped Dalvik and Cache

6. Rebooted to System

-------

At this point I didn't have any 3rd pary launchers, yet, but wanted to test the basic functionality of your shortcuts and anti-update countermeasures.

- Double click Home brought me to the CLH screen

- Long Press Menu from within CLH didn't bring me to the hook screen until I manually started the settings activity-

am start -n com.wolf.cl/.SettingsActivity

- Long Press Home brings me to the Amazon HUD screen

- Long Press Back didn't appear to do anything (what is its function?)

- Check for Updates indicates never checked (as intended?)

Q1. Why doesn't the Custom Launcher Handler app show up in 'Your Apps & Channels'? It appears in Applications-->Manage Installed Applications but only allows Force stop, Clear data, Clear cache (like typical system apps) so I can't start the SettingsActivity from a gui to get to the CLH screens and hook settings. Is this by design?

Q2. I didn't follow the Fire OS update and modify the stock firmware zip as instructed in the OP, as the 6.7.0.1 patch file has the appropriate META-INF, patched boot.img, system/framework and system/priv-app APKs. TWRP's built-in safeguards continue to protect me from unwanted preloader, lk, and tz updates during stock firmware flashing, if I am correct.

Q3. Do 3rd party launchers pose any risk after applying your 6.7.0.1 patch? Are they visible to Amazon?

Q4. Stock firmware 6.7.0.2 kills local adb functionality. Are there workarounds for unlocked rooted mantis devices on the horizon?

@SweenWolf Thanks for your contributions over the years.

-nomobytes
[Fire TV Android Development] nomobytes:
I thought that a blown efuse has been inconsequential with the introduction of kamakiri-mantis-v2.0.1 as shorting is no longer required.
[Fire TV Android Development] SweenWolf:
[ROOT][MANTIS][FIRESTICK 4K] Custom Launcher Support and System Patches

CUSTOM LAUNCHER HANDLER (FIRESTICK 4K) - 6.7.0.2 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...

xdaforums.com

I had to short my stick
[Fire TV Android Development] Skel40:
I had too as well. My device had 6.2.7.7/3033 stock prior to unlocking. I shorted it once and the usb method started working after flashing pre-rooted firmware.
[Fire TV Android Development] Skel40:
I'm focusing on a work in progress for adb. I hope I get it running properly soon. More work needs to be done
[Fire TV Android Development] SweenWolf:
Don't worry take your time, I might look into it when i get free time
[Fire TV Android Development] Skel40:
Thanks. I took a look at BackupManagerService and saw the adb lines. I need to recompile the smali contents into classes.dex, test and work bit by bit with the progress.
[Fire TV Android Development] nomobytes:
S

I also had to short my mantis devices when the exploit first came out. But if you still have a locked, but unlockable-capable device the current exploit doesn't require shorting, period. Are you suggesting that some unlockable-capable devices in the field can only be unlocked via the old exploit?

Will a device that was originally unlocked via kamakiri <2.x always require shorting, even if is updated with the kamakiri 2.01 code, (as most of us have done by flashing the updater zip)? Even if we perform the 2.01 exploit again on our unlocked devices?

Please clarify.

-nomobytes
[Fire TV Android Development] Skel40:
Yes from my device at the time, USB unlocking wouldn't register through on 2.0.1 several times until I actually had to short it only once and usb method worked soon after. Very weird dealing with that issue. It would always require shorting if below 6.2.8.1 since 6.2.8.1 was the last firmware to allow USB shorting with a burned efuse. My 4K has two functional unlocking methods. If I have burned the efuse and only had the USB method, wiping the system and rebooting wouldn't be possible as it's not suggested in doing so on the Lite (Sheldon) device without unfortunately not having the hardbrick shorting method so to me it's unknown when it might happen with other not unlocked devices.
[Fire TV Android Development] SweenWolf:
ADB fixed for 7602 but left to add CLH patches to the system
[Fire TV Android Development] hasobist:
Hello @SweenWolf !

You meant for firmware 6702,isn't it?

That's indeed commendable.

Wondered how you remove the bugs reading between the lines,would love to learn,indeed interested.

Thank you for all your time and support much appreciated.

Awaiting the patch for the said firmware.

Many Thanks once again for all that you and the developers do.

Happy Easter wishes to you and all the wonderful members of the community and family and a Good Weekend as well.

Kind regards Placid D'souza........
[Fire TV Android Development] SweenWolf:
Patched Files
[Fire TV Android Development] hasobist:
Hello @SweenWolf !

Thank you loads,much appreciated.

Cheers!
[Fire TV Android Development] SweenWolf:
CLH is updated, will be included in future release.

For now you can simple update the app. (from Package Manager)

DOTA should now allow App Updates on the System (haven't checked OOBE bypass or OS update but it should block them) it also needs a simple update from Package Manager.

App updates are disabled by default to enable them (First update both these apk) Double click [HOME]

Under Developer's Shortcut, Click on "FTV OTA App"

And Allow App Updates by pressing the Button, after that click on "check for updates" and then "Install Updates" or you can use Amazon settings for that.

Can anyone check OOBE bypass on older version? just rename the DOTA.apk to DeviceSoftwareOTA.apk and put it in the /system/priv-app/DeviceSoftwareOTA/
[Fire TV Android Development] hasobist:
Hello @SweenWolf !

Currently running Skels patched 6702 firmware.

Done as directed.

Updated CLH and FOTA apps.

The update check throws the update error.

CLH updated over the old version gets installed.

The home button click does not bring up the CLH menu ,just goes to home,the Wolf Launcher screen.

Also installed the security app and the package installer,the layout looks wonderful.

Let me know if any needs to be looked into.

Thank you for all.......

Happy Easter!

Cheers!!
[Fire TV Android Development] SweenWolf:
Did you flash 6702 patch before updating CLH anf FOTA?
[Fire TV Android Development] SweenWolf:
If you are dirty installing the patch then you should clean dalvik-cache and cache as well
[Fire TV Android Development] hasobist:
Yes was already on the patched firmware and then updated both the apps.

Cheers!
[Fire TV Android Development] hasobist:
Did not realize you released the patch,thought was only the requisite apks:)

Will update you shortly.

Thank you.......

Cheers!
[Fire TV Android Development] SweenWolf:
When you double tap [Home] button, does the Shortcuts come up or not, if not then you'll have to flash the 6.7.0.2 patch that i posted yesterday even if you have a patched firmware, becuase that will have latest patches on them (sorry if i got this wrong)

After that the two apks will work normally.

Is your ADB working normally now?
[Fire TV Android Development] hasobist:
Hello @SweenWolf !

Doubly pressing the home button brings the CLH options.

Have this option of protected packages.

Will the apps get updated by default or does the FOTA needs to be unchecked keeping system updates checked.

ADB never gave a problem before as well perhaps never noticed as ADB dependent apps worked well and works now as well.

EDIT:Checked for updates results in update error.

Never initiates updates.

All looks good.

Thank you.......

Cheers!
[Fire TV Android Development] SweenWolf:
On a stock ROM without any other patch these are the behaviors which you'll see.

Version excluding 6.7.0.2 v2 patch :

Last Checked: Never​

Your system is up to date.​

​

6.7.0.2 v2 patch:

Last Checked: (Will show last checked date and time)​

Your system is up to date.​

​

OR​

​

Downloading...​

System Components​

​

OR​

​

Install Update​

​

​

(This will allow App updates but will not allow OS updates on System, It is the expected behavior)​

​

​

You shouldn't see "Update Error" this was the behavior of very early patch, regardless you shouldn't see this on 6.7.0.1

On a stock 6.7.0.2 you will not be able to use Mouse Toggle or Launcher Manager or other adb apps anymore.
[Fire TV Android Development] hasobist:
Hello @SweenWolf !

Installed the V1 patch 6702 and updated CLH,adep final(security app),package installer and FOTA

When updates checked it ends in update error.

May be it's patched firmware by Skel40 6702.

Will install the patched 6702 V2 and update you.

EDIT: Installed V2 of the patch ,checked for updates resulting in as mentioned.,works well.

Will update the firmware to stock 6702 later and check for the behaviour of adb apps and will update you accordingly.

Thank you

Cheers!
[Fire TV Android Development] nomobytes:
When OTA updates are enabled from the OTA dashboard, some are being automatically installed after being downloaded, without hitting the install button. I noticed this with the 'com.amazon.minitv.android.app' package. Is this related to the use of a 3rd party launcher or is the package flagged as long overdue?

My steps:

1. Extracted boot.img from your 6702 V2 Patch

2. Patched boot.img from magisk (for later use)

3. Installed the stock 6.7.0.2 firmware from the twrp command line

4. Installed your 6.7.0.2 patch from the twrp command line

5. Wiped cache/dalvik and rebooted.

I tested basic functionality without root using a few 3rd party launchers including flauncher, alauncher (a fork of flauncher) and wolf launcher (of course)

6. Rebooted to recovery and flashed the magisk patched boot.img to the boot partition from the gui.

Retested functionality again, with root.

Update blocking is working, but I was surprised after I enabled app updates from the FireTV OTA Debug Menu, and hit check for updates, the miniTV app downloaded and immediately installed, with the same behavior when I checked for updates from the My Fire TV-->About-->Check for Updates screen (after enabling from your modified OtaDashboard.

Borh Flauncher and and Alauncher are being killed and restarted with a long (> 10 seconds) startup time, and I'm not sure what is triggering this.

Local ADB is working fine using Remote ADB Shell but I can't get some apps to work (Permission Manager X) using local adb, so I'm forced to go in as root.

Mouse Toggle automatically starts on boot and the gui starts/stops the service as expected.

-nomobytes