yashsingh1/xdaforums huggingface dataset:
[Fire TV General] TimmyP:
Just root and use FTVLaunchX. Re-grant security ($ pm grant de.codefaktor.ftvlaunchx android.permission.WRITE_SECURE_SETTINGS from pc adb). I think this is easiest for people who want home button back.

EDIT: Just did it on debloated 6.2.7.3, had to restart a couple times. It defintely works. It will popup asking you to select a home launcher. It *may* be the Amazon_Launcher_Replacer working in tandem.
[Fire TV General] Darkfact5249:
After i do these. The process for add more space with usb is still the same as before? With remote adb shell?
[Fire TV General] sjude68:
screen is blank

I followed the above procedure. After booting the firestick the launcher is disabled. But I am getting a blank screen.

Pressing Home key on the remote gets the screen where apps, sleep, mirroring and settings is available. I cannot open any apps and the settings also gives a blank screen.

How do I install the app for the launcher.
[Fire TV General] 0815hoffi:
Point 1.

Install Launcher of your choice.

Maybe Wolf Launcher

https://xdaforums.com/showpost.php?p=83215549&postcount=381

https://xdaforums.com/attachment.php?attachmentid=5074645&d=1596687827

#adb install Wolf_Launcher_0.1.6-FireTV.apk

Or in TWRP.

adb shell mount -o rw /system

adb push Wolf_Launcher_0.1.6-FireTV.apk /sdcard/WolfLauncher.apk

adb shell "mkdir /system/priv-app/WolfLauncher/"

adb shell "chmod 0775 /system/priv-app/WolfLauncher/"

adb shell "chown root:root /system/priv-app/WolfLauncher/"

adb shell "cp /sdcard/WolfLauncher.apk /system/priv-app/WolfLauncher/WolfLauncher.apk"

adb shell "chmod 644 /system/priv-app/WolfLauncher/WolfLauncher.apk"

adb shell reboot
[Fire TV General] TimmyP:
Why do all that? ^^^ Just install Wolf .16 or Tv Launcher 3, or any launcher that Android detects as a launcher (wolf was missing this until last version, so it didnt invoke the menu).

Use FTVLaunch, set permissions, select launcher, reboot, Android menu pops up, tell it to use your launcher "always," works every time. Might have to select Launcher 2x in FTVx (I think it is just used for booting, since the native launcher picker pops up).
[Fire TV General] 0815hoffi:
native launcher picker only pops up if you disable or remove com.amazon.firehomestarter and com.amazon.tv.launcher

Then no need to use FTVLaunchx....

But you lost Settings and Store.

For Settings use my NewSettingsRoot.apk

My Amazon_Launcher_Replacement.zip delete also

com.amazon.firehomestarter and com.amazon.tv.launcher.
[Fire TV General] SpaceMan5:
After i did this voice searching new apps doesn't work.. is there a workaround for this or is that only avail with the stock launcher?
[Fire TV General] 0815hoffi:
Only with Stock Launcher
[Fire TV General] TimmyP:
This is not true. I still have full Amazon functionality. I also have your settings app working fully too with Wolf. To enter back to Amazon I pin "home" to my homescreen, otherwise I never see anything Amazon ever. Even boot logo changed with debloated rom.

FTVLaunchX still works on boot to start your custom launcher, while retaining the Amazon one. You can have it all and root.
[Fire TV General] SpaceMan5:
Are you on the newest update? I got rid of my launcher and i also don't have the store.. Would like that back so it's not annoying to get new apps.
[Fire TV General] 0815hoffi:
[MENTION=869891]TimmyP[/MENTION]

Ok.

Can you check with root and rw /system if you have

this Folders and apk's ?

/data/app/com.amazon.tv.launcher-1/

/data/app/com.amazon.firehomestarter/

/data/data/com.amazon.tv.launcher/

/data/data/com.amazon.firehomestarter/

/system/priv-app/com.amazon.firehomestarter/com.amazon.firehomestarter.apk

/system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk

What Launcher comes up if you press the Homebutton?
[Fire TV General] TimmyP:
If I press home button Wolf .16 comes up. (you can not use a lower version)

/data/data/com.amazon.tv.launcher/ is the only one from that list that remote adb shell was able to find.

*and if I install a new launcher, the launcher picker comes back up. Same as regular Android.

---------- Post added at 07:20 PM ---------- Previous post was at 07:15 PM ----------

Yeah. Debloated 6.2.7.3. I posted a ton about getting it to work, but the confusing culprit was everyone was using Wolf launcher... which before .16 was not flagged as an Android launcher, so it didn't trigger the native launcher picker. I was using TV Launcher 3 and it was flagged the whole time, which is why I saw the launcher picker, and nobody else did.
[Fire TV General] 0815hoffi:
Thanks

Okay, I'll give it a try.

Maybe this is the solution.

Not delete

/data/data/com.amazon.tv.launcher

--‐-----

I think only com.amazon.firehomestarter must be remove to get the Launcher picker....

I will check this , maybe i can create a new LauncherReplacer.
[Fire TV General] Darkfact5249:
How can i update launcher when a new one is post?
[Fire TV General] 0815hoffi:
Flash Stock OS and then reflash the new Zip.
[Fire TV General] 0815hoffi:
I have tested.

Unfortunately I cannot reproduce it.

So if the store is needed , use the Stock Launcher.

If you want if back Flash Stock Rom or copy the backuped apk´s back in TWRP.

Boot twrp.

adb shell mount -o rw /system

Restore Apps

adb shell "mkdir /system/priv-app/com.amazon.firehomestarter"

adb shell "chmod 0775 /system/priv-app/com.amazon.firehomestarter/"

adb shell "chown root:root /system/priv-app/com.amazon.firehomestarter/"

adb shell "mkdir /system/priv-app/com.amazon.tv.launcher"

adb shell "chmod 0775 /system/priv-app/com.amazon.tv.launcher/"

adb shell "chown root:root /system/priv-app/com.amazon.tv.launcher/"

adb shell "cp /sdcard/com.amazon.firehomestarter.apk /system/priv-app/com.amazon.firehomestarter/com.amazon.firehomestarter.apk"

adb shell "cp /sdcard/com.amazon.tv.launcher.apk /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk"

adb shell "chmod 644 /system/priv-app/com.amazon.firehomestarter/com.amazon.firehomestarter.apk"

adb shell "chmod 644 /system/priv-app/com.amazon.tv.launcher/com.amazon.tv.launcher.apk"

adb shell reboot
[Fire TV General] 0815hoffi:
New Version

https://xdaforums.com/fire-tv/general/root-firetv-launcher-switcher-stick-2-5-t4161017
[Fire TV General] ktjensen:
just saw this thread posted on REDDIT firetv group. then the message was deleted. Assume this will only work for a true ROOTED firestick, and only with the proper long list of ADP commands? Will await the TDUK version when that comes out as prefer something easier to run. Unles someone says different and its easy to get the launcher changed so it works once again with current OS.
[Fire TV General] 0815hoffi:
You can use TWRP flashable Amazon_Launcher_Replacement.zip, it will delete the Amazon Launcher, only way back is to flash full rom.

Only one command.

twrp install Amazon_Launcher_Replacement.zip

Or use without Root [MENTION=7352779]SweenWolf[/MENTION] App.

https://xdaforums.com/showpost.php?p=83468741&postcount=461

But currently only with root and my Settings App

com.markus.firetools.apk

you can access all Amazon Settings.
[Fire TV General] dougie175:
[MENTION=10401573]0815hoffi[/MENTION] Great work, this is a lot quicker and easier than manually putting in each line of command like I was doing, I understand you have a new version available now to switch between custom and Amazon launcher but I prefer the whole setup with the Amazon launcher deleted so the only option is to end up at Wolf Launcher.

You kindly made a custom FireTools with restart at the top on your other thread, when you get some time could I be really cheeky and ask if you could possibly make another custom FireTools with the following setup in the order below, it would be very tidy for myself, my worry is if the kids start playing and choose the “disable custom launcher” they end up back at a blank screen because I have deleted everything previously.

Reboot

My FireTV

Display and Sound

Network

Bluetooth and Remotes

Accessibility

Applications

Preferences

Equipment

Notifications

Amazon Account

If you can complete that it would be really appreciated, I think it would be a great little setup for most people as its clean and tidy like the original 1 but with the added benefit of the reboot option

Thank You
[Fire TV General] 0815hoffi:
[MENTION=5465895]dougie175[/MENTION]

yes I can do, but it takes a few days until I have time
[Fire TV General] dougie175:
No rush that would be great thanks very much
[Fire TV General] 0815hoffi:
Update 1st Post
[Fire TV General] 0815hoffi:
see OP
[Fire TV General] dougie175:
Hello

Sorry no trying to be pushy at all just wondered if you had chance to take a look at this for me yet?

Thanks very much appreciate your time
[Fire TV General] 0815hoffi:
Hi,

already changed see 1st Post.

Version 1.1.
[Fire TV General] dougie175:
Great thanks. I will have a play with it this evening, extract just the apk and overwrite the current settings I have

Thanks
[Fire TV General] 0815hoffi:
Yes you can or flash in TWRP
[Fire TV General] Pachacouti:
Back again... Well, I did manage to get back into my 4k, but it's been nothing but trouble since. I got back into my 4k that I'd flashed 7.7 over 7.1, which worked after countless flashes. What got me back in was testing update 7.3, and when it booted and showed me the white firetv screen after a few days, I was like, at last... after booting, it downloaded 3 full updates! These updates booted finally showing my fireOS version was 7.6, a version lower than the 7.7 that bricked it.

So after finally installing stbemu pro 1.2.8, I was watching live tv again. However, next day, lo and behold, plugged it in, and got the blackscreen again. I think about how I flashed the launcher from here, and after another flash of 7.7 over 7.6 I decided NOT to flash any launchers this time, stbemu actually worked this time on 7.7, but would not origionally, suggesting to me the launcher was at fault. I gave up with the launcehrs when I realised it was more awkward to get into system settings, and pressing root 'grant' was impossible in the time it gave to do so, only the launchers created these problem's, however, here I am again, because after turning on my 4k using 7.7, with no launcher, blackscreened again.

I have erased/formtted every visible partition, and this time I cannot even re-produce the steps I took to flash the 7.3, nothing works to actually wipe or delete whatever is causing the blackscreen, leading me to believe what-ever they are updating, I can only assume they are placing it in whatever recovery/ramdisk is used to protect root, kinda like an older boot image sometimes wont flash over a newer boot.

Would it be possible to get a list of all partitions it is safe to wipe, when in amonet, and why do fastboot commands not work when in amonet to flash boot.img?

I reckon amazon are just looking at our accounts to see what we use, then send an update to force the blackscreen..
[Fire TV General] Pachacouti:
Well, gave it another bash, no go, and after so many tests, all I can say is somethin is clearly being retained even after formatting all found mounted dirs. I suppose this means it is possible that amazon have found a way to write to a directory that I cant find.

Why is it, regardless of erase/format command, files from previous os are still visible?

So I look to amonet and do a df:

Filesystem 1K-blocks Used Available Use% Mounted on

dev 6072232 0 6072232 0% /dev

run 6095388 94208 6001180 2% /run

/dev/mmcblk0p1 15540736 941240 14599496 7% /run/archiso/bootmnt

cowspace 262144 1892 260252 1% /run/archiso/cowspace

/dev/loop0 886784 886784 0 100% /run/archiso/sfs/airootfs

airootfs 262144 1892 260252 1% /

tmpfs 6095388 0 6095388 0% /dev/shm

tmpfs 6095388 0 6095388 0% /sys/fs/cgroup

tmpfs 6095388 16 6095372 1% /tmp

tmpfs 6095388 1508 6093880 1% /etc/pacman.d/gnupg

/dev/sda1 234429436 205124940 29304496 88% /run/media/root/Studio

and I notice so many tmpfs, is this expected, if not, how do I remove the offeding dirs that may hold whatever causes blackscreen? Or wipe/erase/format? This df was taken after formatting all I could find in fastboot, which has no effect...

Edit: For instance, how would I get rid of airootfs?
[Fire TV General] Pachacouti:
Well, finally biting the bullet, I've attempted to reflash EVERY stock update since 6.2.7.1, with no joy. Still stuck on no firetv screen, the one that SHOULD appear after the fire tv first boot screen. I've wiped and or formatted every partition I could find, to no avail, despite being succesfull before, so whatever you do, do not install this launcher, because the op says to reflash stock which does NOT work, no matter what version. I believe by installing this, you'd be as well throwing your stick in the bucket, because no-one can actually help anymore, it's all ok when we're testing, but when they feck it up, it's us that lose out, as denoted by lack of op input...

it sems that no matter what we do, we cannot downgrade anymore. The flash's appear all ok, but there is no boot up after the first black firetv logo. Lets see how good them devs are now lol... DONT DO IT!!
[Fire TV General] SweenWolf:
I don't understand some bits here,

Are you using root just to change your launcher?

What black screen are you talking about.

Does it comes right after the kernel or does it come after your system is booted (after white firetv animations)

If its later then is the Amazon Hud launching or not? Amazon hud comes on long pressing home button.

And one thing, To change your launcher you do not need root.
[Fire TV General] 0815hoffi:
removed
[Fire TV General] Pachacouti:
Actually, it has quite a lot to do with this script.. It has been made clear that the only way to get rid of this is to do a stock reflash. Well, this is now turning out to be impossible! Every previous version flash's, everything looks fine, but when booting it boots the first black fire logo, and does NOT go to the white firetv logo. In fact, at one point, three flash's ago, I thought I'd cracked it, when I saw the white begin to show, but fade to black?

Strange how I've succesfully flashed countless times, wiping the dirs you posted in that order, but I cannot go back to an earlier version, and cannot install latest, all appears fine, but something is being retained somewhere. Something that is preventing the 2nd boot logo, the white one from showing.

If you had the decency to add a version number to the newsettings.apk, instead of every version having same name... seems whike I always used the 1.03 version, you now on what version? And do you make this clear when naming you apk? But then there are enough posts here pointing out that you now run the risk of AMAZON bricking your device for using this launcher, correct?

Everything I've read USED to work. My stick is fine. It flash's fine.

Get ready for lots of firestick users comin for the quick fix...

If the big red capitals are meant for me, I'll point out it's not a good idea to shout at this earth monkey, who gets to hold you on a tesyract cross in front of the flames before throwing you into the burning pit.

Edit: And may I take this time to point out that some need to learn the difference between wipe/erase/format when it comes to system.
[Fire TV General] 0815hoffi:
Ok,

I misunderstood.

I'm sorry.

I was just surprised that you have posted it here.
[Fire TV General] Pachacouti:
I posted here due to having flashed NewSettings.apk, which turned out to be a different version from the one I had been using... I have tried everything I can get my hands on, and one thing became apparent, is that I cannot write a boot.img in amonet/fastboot, and I believe this error is related to the actual problem, I copied the error from fireiso adb:

fastboot flash boot boot.img

fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.

Aborted (core dumped

I'll take this to the unbrick, sorry for any inconvienience :)
[Fire TV General] 0815hoffi:
Had a similar problem with Fireiso.

My solution was 1st root script running in fireiso.

Reboot to Windows with connected stick.

Running fastboot under Windows.

Drivers FireTV:

https://s3.amazonaws.com/android-sdk-manager/redist/fire_devices_usb_driver.zip

For Fastboot.exe use google.
[Fire TV General] Pachacouti:
My problem here would be turning off the laptop the firestick is connected to, if I run the fireiso first script to boot fastboot, I'd lose fast boot rebooting the laptop in order to use windows.. :P
[Fire TV General] 0815hoffi:
Have you maybe a powered usb hub....

Or try with the Alternative Windows Version of

Kamakiri.

https://github.com/esc0rtd3w/firestick-loader/blob/master/rooting/mantis/kamakiri-mantis-v1.2-win.zip?raw=true
[Fire TV General] Pachacouti:
I've only got a usb power bank or two, sad that they dont act as a hub, but thanks for the windows version of Kamakiri, never knew this existed!

Edit, not working, invalid syntax, but I know python is a steamin pile of **** that should be dropped, what version of python?

>>> ./bootrom-step.cmd

File "<stdin>", line 1

./bootrom-step.cmd

^

SyntaxError: invalid syntax

>>>

tried without ./

>>> bootrom-step,cmd

Traceback (most recent call last):

File "<stdin>", line 1, in <module>

NameError: name 'bootrom' is not defined

>>>

Due to origional pins being messed up through so much testing is to use a pair of needle point tweezerz (pink lol) so I hold tweezers on points, hit return after typing cmd in the window, then plugging in the usb to guarantee I got a connection, dont think this works in windows judging by last error?

Do I require a different tutorial for this version of kamakiri?
[Fire TV General] 0815hoffi:
I have not testet the mantis Version but there is also a Tank stick 2 Version with included Phyton that works for me on Tank.

https://github.com/esc0rtd3w/firestick-loader/blob/master/rooting/tank/archive/amonet-tank-v1.2.2-win-original.zip?raw=true

Maybe you can customize the Tank Version for mantis
[Fire TV General] Pachacouti:
Well, thanks ever so much for your help, but re-programmin my laptop is not really what I had in mind, clearly the version you mentioned does not work, due to python not havin a clue anymore, python sux... Just goin to test my home made otg to see if twrp will fix anything...
[Fire TV General] Pachacouti:
removed, posting in wrong thread
[Fire TV General] SweenWolf:
Can you please clearify what you are trying to achieve,

I am unable to understand when you are flashing what.

Do not flash boot.img from fastboot it will remove your twrp also,

Only update the boot.img from twrp itself.
[Fire TV General] Pachacouti:
I understand this, but can wipe boot, put it back, and flash a twrp too, I'm trying to load ANY rom that gets me passed the 2nd screen, or animation screen, I moved my prob to the unbrick thread, as navin23 has same prob:

https://xdaforums.com/t/unbrick-fire-tv-stick-4k-help.4021923/page-4#post-84363665
[Fire TV General] abcdef2015:
I have just installed ftvs2k-5.2.7.7 on Tank using your scripts from github (great guide and tools, BTW!).

I wanted to check if it's possible to also install WolfLauncher 0.1.9 without breaking the system using the latest version of firetools (from github) while keeping leanbackonfire as a fall back.
[Fire TV General] 0815hoffi:
Yes its possible, i also use ATV Launcher
[Fire TV General] n4m3less:
Hi @0815hoffi and thanks for your great work!

On my tank (fire os 5.2.8.2 rooted) with the latest version of firetools (your github) the items to enable or disable the custom launcher do not appear. I have tried both with wolf launcher 1.9 and with leanbackonfire 1.49
[Fire TV General] 0815hoffi:
Yes i removed that.

Use the adb commands:

adb shell su -c "pm disable-user --user 0 com.amazon.tv.launcher"

adb shell su -c "pm disable-user --user 0 com.amazon.firehomestarter"

Github is the latest Version.

No update Anymore, i switched to mi tv sticks.

Sorry
[Fire TV General] Sus_i:
lol, really? No love for the new fireTV-4k-Max stick? ;)

I like xiaomi, but never got one of the Mi TVsticks :)
[Fire TV General] 0815hoffi:
Yes ;-)

Not the fastest one , but ok with tweaks :)

https://xdaforums.com/t/app-firetv-...e-launcher-without-root.4176349/post-85844663
[Fire TV General] Kireej:
How in the world do I enter adb commands to a fire stick?
[Fire TV General] Meitei:
adb connect <IP of FireStick>
[Fire TV General] Meitei:
And there is probably a prompt coming up on the fireStick, which you have to agree with.
[Fire TV General] chopwell20:
use adblink or adb connect 192.168.1-- your stick ip.
[Fire TV General] Gast2:
NewSettingsRoot.apk Where can I download?
[Tilt, TyTN II, MDA Vario III General] Jimllfixit:
Hi Guys,

Hope you can answer this weird problem.

All of a sudden my TyTN 2 would not select key infromation within a message (SMS, E-mail etc)

When i open an SMS it will go straigh to the bottom of the message, and when i scroll up it will not put a box round the senders number or name like it used too.

I have looked in the settings to see if there is something i have missed but to no availe.

Am i right in saying that i may need to perfrom a hard reset?

Regards

Rich
[Galaxy Tab S2 Q&A, Help & Troubleshooting] oocubain:
I'm writing this because in all my searching I couldn't find a short guide of how to install the Stock firmware using Heimdall. I had a T710 that was failing to boot any ROM I put on it with TWRP. So I decided to put Stock back on it.

obtain stock firmware, mine was named BTU-T710XXU2DRH1-20181005080953.zip

unzip in a new directory, for me this resulted in a single file: T710XXU2DRH1_T710BTU2DRH1_HOME.tar.md5

untar with:

tar xvf *.tar.*

For me this resulted in the following

boot.img

cache.img

hidden.img

recovery.img

sboot.img

system.img

get the output of print-pit:

heimdall --print-pit >pit.txt

in the print-pit output, for each entry, look at

Partition Name

and

Flash Filename

. This will help you determine which file goes with which partition name.

boot to download mode (Power+VolDown) and use heimdall to flash the parts you want. For me this was:

heimdall flash --BOOT boot.img --CACHE cache.img --HIDDEN hidden.img --RECOVERY recovery.img --BOOTLOADER sboot.bin --SYSTEM system.img

after the flash the system will automatically reboot. You'll get the throbbing Samsung icon for a while as it does stuff and then it will boot.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] Xenobio:
Thanks a lot for this. You saved my T810.

I had decided to upgrade my 6-year-old tablet to LineageOS and idiotically missed the first critical step of enabling OEM Unlock. I tried to flash TWRP using Heimdall and softbricked it... It could only boot into download mode and for some reason, Odin could not recognise it, only Heimdall.

I downloaded the latest version of the stock firmware using Frija and followed your method, worked perfectly and I now have stock Nougat.

Still can't figure out why the OEM Unlock button doesn't appear in the Developer settings for me, so can't install Lineage, but at least everything is working again.
[Touch Pro2, Tilt 2 Windows Mobile General] arturbuyan:
Hello, pls help me a find old roms for my htc touch pro 2.

Mobile loading only bootloader and have 0.79 SPL.

Window can't loading(

I find Vodafone UK 1.14.161.6 (50207) R3.44.25.27 and Orange UK 1.90.61.0 (70819) WWE R4.49.25.17

Original links dont work(((
[Touch Pro2, Tilt 2 Windows Mobile General] Vik Vasilev:
Did you find any roms? It would be great if you could share them here :)
[Touch Pro2, Tilt 2 Windows Mobile General] Keigo_Akashi:
Looking for a ROM too, especially the German T-Mobile ROM.