yashsingh1/xdaforums huggingface dataset:
[Fire TV Q&A, Help & Troubleshooting] navin23:
This when i set my pc and putty to 921600 baud copied from putty clipboard.

▒▒▒▒▒▒▒▒▒

.

.

.

BpL`39H@@D▒@l▒|▒▒`▒▒1|@@D @D@@▒▒ ▒▒B@\▒▒H H#d▒@1@L▒▒▒▒\▒1d`\▒!▒

▒▒@$▒B@▒d@Hb @B▒L@▒ d@H▒H@@▒@H

`

▒!▒1▒@\▒d▒

@▒▒L

H 0,▒ ▒@L@X▒DqfD▒ x\D@d▒|▒<▒ ▒@Ȁ@D▒ ▒▒ b@▒"▒$^▒▒▒p▒DD▒\d,8▒|@^▒<▒

▒X▒▒"L▒8@@▒▒▒|b▒▒" ▒▒BH$

df`▒▒q▒▒▒2▒ B1@▒dd▒`▒▒q@@ L B1@b▒$▒H.▒L@▒L<L"▒b▒▒▒"▒▒▒bbB▒▒▒▒▒bB▒@@▒<L"▒f

D▒▒▒ N▒

L@▒ ▒@8b▒

b▒▒@p▒1▒|@ B H▒@H▒▒DD@D▒▒▒|▒▒`▒.B▒▒ H

S@@▒$ę▒@@@▒$ęb▒X▒▒ ▒▒X▒DqfD▒ x\D@d▒|▒<▒ ▒@Ȁ@D▒ ▒▒ b@▒"▒$^▒▒▒p▒DD▒\d,8▒|@^▒<▒

▒X▒▒"L▒8@@▒ly▒x|D.D ▒▒BH$

df`▒▒q▒▒▒2▒ B1@▒dd▒`▒▒q@@ L B1@b▒$▒H.▒L@▒L<L"▒b▒▒▒"▒▒▒bbB▒▒▒▒▒bB▒@@▒<L"▒f

D▒▒▒ N▒

L@▒ ▒@8b▒

b▒▒@p▒1▒|@ B H@▒LFH▒$▒ ⋀bD,▒▒H▒2▒

▒▒ BH▒▒▒ ▒"▒"▒2▒▒@H@@Dd▒▒▒▒▒▒▒H xD@$dLL "▒▒H

D"D▒▒1▒D▒▒H, "D@D"▒▒0▒L ▒LD ▒▒1▒▒@▒▒▒ ▒▒▒▒"DL ▒1

DlB# sd▒▒▒

@▒▒H@1 L@@@

▒

@`D@D"

▒ ▒@`Bc▒

▒▒@X̹ ▒@@`D<L▒D▒1▒1▒ F@▒ ▒▒▒DB#nq▒!@@▒@<@▒▒&▒ ▒▒▒&`BFBDBLLH

HL

@<@▒▒▒▒ $▒▒▒▒▒▒▒8L

▒@@▒▒▒▒▒▒L▒f1@▒

B▒@D@$dLL "▒▒H

D"D▒▒1▒D▒▒H, "D@D"▒▒0▒L ▒LD ▒▒1▒▒@▒▒▒ ▒▒▒▒"DL ▒1

DlB# sd▒▒▒

@▒▒H@1 L@@@

▒

@`D@D"

▒ ▒@`Bc▒

▒▒@X̹ ▒@@`D<L▒D▒1▒1▒ F@▒ ▒▒▒DB#nq▒!@@▒\"▒D▒▒<▒!@@▒@@B▒▒

D@F▒▒@▒▒1▒fd▒▒`▒

▒@DD@D▒d

▒@

▒́d▒▒▒D@▒▒▒1▒▒L Hb L"`^FX

▒@DFd

`▒▒|d▒▒|▒

▒@▒@^BDd▒▒▒

D.▒@▒B▒▒▒▒

▒ BFD@ ▒D

B▒# 1▒▒@▒d▒@

.▒▒▒▒▒@@▒@▒`@

▒ ▒▒

@▒@"▒▒`

B▒▒▒1@▒"B▒▒▒8▒

H@@D▒▒▒&FF▒b▒▒▒bB▒#BD.BL"H

@▒bD@

▒▒▒B

▒@▒`

ȑ|▒▒1▒▒n▒$▒

@▒"B ▒▒ b▒▒▒▒▒▒▒▒1#▒▒@lAXLD ▒B"▒@@▒b<`L"`^FX

▒@DFd

`▒▒|d▒▒|▒

▒@▒@^BDd▒▒▒

D.▒@▒B▒▒▒▒

▒▒▒"y▒▒`▒▒!̄|D@DHq

@`▒▒▒@ H|▒▒"▒▒ #▒HD▒▒n@Ȅ

@@

y$▒▒@▒▒|@▒▒ bb▒q▒

d.▒▒▒"▒▒ #Dp dB ▒8\▒$` ▒▒▒@ ▒▒▒ ▒p▒1▒1▒@▒ ▒|D.▒d▒

▒L\nH▒▒▒DD▒`"< ▒

$D\▒F▒

1 ▒D▒▒D!▒▒@X&▒D@B@

▒1▒▒L@@▒LDD▒1N▒p`▒@L

▒B▒q▒b▒▒▒"▒"▒▒",▒▒1@▒"▒▒ BB▒@▒"▒▒q▒1▒y$nB0@`▒▒ #$d▒ ▒q▒1▒@@F▒▒&@▒#▒ȁ&1▒qL@d▒ @X&▒▒@"$@D▒8▒D@"▒▒bH▒ ▒ ▒▒@@b▒ @▒X"D▒N▒▒@"▒▒▒▒▒▒▒▒▒`▒▒▒▒,`▒▒▒a▒▒▒▒

▒▒X"D▒L1D@b▒ ▒▒

@▒"▒▒ #@▒▒▒b▒q@.|fB▒▒▒&▒▒

H▒ "b▒▒LHnB▒dx@,▒▒▒

B▒#▒p▒▒qL▒▒Dy▒▒▒▒▒bB▒#▒▒X!▒L▒<b^cy▒ ▒p▒▒▒▒

▒X

L▒<"▒D▒q▒▒L 2ȁ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
[Fire TV Q&A, Help & Troubleshooting] 0815hoffi:
You need a Usb to uart ttl converter like this.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
All GND solder pads on the stick will work, as long RX goes to TX and vice versa.

I guess your cable lacks a signal converter chip and thats the reason we see only garbage in the log.

I've a cheap 3 bucks USB to TTL UART bought from amazon, black board with CP2102 chip.

My setup was always 115200 baud in the windows settings and 921600 in putty.

(y)

If you power/connect the fireStick and the UART adapter via USB ports on the same PC, it may work without any soldered GND connection... But ofc, a GND to GND wire is best.
[Fire TV Q&A, Help & Troubleshooting] navin23:
Ok, I got a red board uart ttl converter and i was able to get some logs. Thanks again.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Thanks. The clipboard.txt log out of your zip is nice and clean, seems complete and it looks good, at least for me.

@k4y0z Maybe you can take a look at his log too, please :)

Here is a quick TL/DR of this thread for you:

Some people tried to clone a 4k stick with a TWRP backup = fails.

A restore back to factory default / stock fails.

Wipe System, Cache, Dalvik, Data and a clean install of stock rom doesn't help.

Re-do of the unlock, stock-rom + magisk flash doesn't help.

GPT-fix + stock-rom + magisk flash doesn't help.

Format data, system and vendor via hacked BL + a clean stock-rom flash doesn't help.

TWRP and hacked BL works fine. Idme data looks good.

The fireSticks refuse to boot, so adb logcat isn't accessible.

Do you want tell how to switch printk.disable_uart, in order to get a linux kernel bootlog with the serial console?

Regards^^
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
I aint got the red board, but if navins logs look good, then I'm prob in same boat, gave up flashin it for now, no point repeating myself too much, all I can do is read and if anyone needs a tester, mines ready and waiting lol
[Fire TV Q&A, Help & Troubleshooting] Madan2harsha2578:
Plz suggest any one game pad for vu premium 43inch android 4k tv , wireless are with wire
[Fire TV Q&A, Help & Troubleshooting] navin23:
I was having a look through the clipboard log and from (910) to (2400) there is a jump and a kernel not match.

read_func hook

[910] [LK_BOOT] KERNEL partition magic not match

[910] no mkimg header in kernel image

[910]

read t

Unlock UFBL: device is unlocked

[2400] [LK_BOOT] ROOTFS partition magic not match
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
So is this causing you any problems?
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
I don't think so,

lets see what k4y0z says
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
I finally got back into mine after trying every stock I could find, and failing, try this:

Grab origional stock firmware, that was on your firestick when you bought it, mine was 6.2.6.8, so I'll post using this version, your's may be different, but I'll bet the process works for all.

I: load fireiso, then do the short, but use ./gpt-fix.sh

2: Device will boot into fastboot, from here:

fastboot erase userdata

fastboot erase tee1

fastboot erase tee2

fastboot erase boot

fastboot erase logo

fastboot format /vendor

fastboot format system

3: disconnect firestick

4: Do short again, because you just wiped boot

5: When in fastboot, unplug.

6: Rebooted to win (7 x64) to use latest platform-tools:

fastboot flash boot 6.2.6.8boot.img (taken from stock)

fastboot flash recovery twrp.img

7: Rebooted into fireiso, Do both steps in Kamakiri

8:

adb push update-kindle-mantis-NS6268-Origional.zip /sdcard/update-kindle-mantis-NS6268-Origional.zip

adb shell twrp wipe cache

adb shell twrp wipe data

adb shell twrp wipe dalvik

adb shell twrp wipe /system

Do push again to be sure

adb push update-kindle-mantis-NS6268-Origional.zip /sdcard/update-kindle-mantis-NS6268-Origional.zip

and then

adb shell twrp install /sdcard/update-kindle-mantis-NS6268-Origional.zip

adb shell reboot -p

Voila, back to origional stock!

Notes: I noticed we are told to flash the boot after installing stock, I flashed the stock boot BEFORE flashing stock. All previous attempt's had me flashing respective boot.img (for respective firmware version, AFTER)

Makes sense, dunnit?

Edit2: I'm in Scotland, it updated to 6.2.7.6/2933 just for the record, I wanted to install the 7.7, but thought twice, as maybe being too high got me the boot?

Then while writing this and seting adb I notice it's updating to 6.2.7.7/3027, so once done I can go back to the rooted 7.7...
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
No, not really :unsure:

Can't see why only an old stock.bin is supposed to work!? Every stock fw should work.

Idk why multiple wipes are better than a single wipe.

Whats about tee2 and logo. Do you want them empty, can't see a flash command for these?

Anyway, I'm happy that you've solved your problem and I'm curious if it'll work for someone else too. :D
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
Hi, as @Sus_i mentioned the firmware shouldn't matter what version (I'm in Scotland too 6.2.7.7 is current update.bin latest pushed via fota).

I'm sure k4y0z script downgrades rpmb anyway when the stick imgs is being flashed. It shouldn't matter. I have went from 6.2.6.8 to 6.2.7.3 then to 6.2.7.7 back to 6.2.7.6 with no problems.

The only problem I ever faced was trying to clone one stick to another, boot/recovery partition seems to not play nice.

Good you got it working though

Regards
[Fire TV Q&A, Help & Troubleshooting] navin23:
It doesn't work for me for people that try to clone their stick.

fastboot format userdata

fastboot format vendor
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Sus_i

I think you need to go back to school, no offence, but what part of kamakiri dont you get?

Tee1 and 2 would NOT be blank, because Kamakiri flashes them, at the first flash of kamakiri, if I wiped them, it would not matter, because after the 2nd reflash of kamakiri, they would be restored, an update takes care of the rest!

To me its obvious, obviously I've flashed an update, rooted, POSSIBLY with different tee1 and or tee2, so after reading all the stuff in the 63/4 page, I thought that if kb is being incremented, by Tee1 and/or 2, then going back to origional as best I could would do the trick, maybe it did, maybe it didn't, but if kb is empty, (cant wipe or erase it) then flashing tee1 and 2 would correct anything tee1 and 2 had previously set kb to depending on what rooted update I flashed, who knows? From what I've read, no-one knows (yet)...

My thinking was kb is the incrementation like boot.img USED to use, blocking downgrades for unrooted users, who couldn't change this, again, I may be right, I may be wrong.

Most likely it was flashing boot like navin suggessted, in windows using LATEST fastboot, since again what I've read, twrp wont flash protected partitions, ie, boot.img. So I used windows, which would'nt let me boot into fastboot unless I did what I described.

Kamakiri fastboot needs an update, oh yeah, we gotta do that ops work too... it's not just fastboot OR Glib, but after that? Kamakiri was written in 2019, this is now 2021! 20 updates of glib later... (joke..)

Only 2 or 3 post's mentioned flashing the boot of the stock AFTER flashing the stock, and in my opinion, IT MAKES SENSE to flash stock boot.img BEFORE flashing the stock it was extracted from, in WINDOWS!

Flash stock boot before flashing stock, taken from the stock to be flashed?

The rest I honestly dont know. I gave my best to show what worked for me, when no-one else suggested anything but wiping the usual, which did not work for MOST with the black screen.

Go figure :)

#

Navin, thanks for pointing out to flash boot.img in windows, no-one else thought of that :)

Edit: I'd like to point out I previously wrote that I'd tried flashing boot, and got passed the initial fire logo to the white animation screen which blacked out before I could see the orange writting.
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Note:

fastboot format /vendor

Duno 'bout cloning (yet) - just saying how I got out of my black screen.
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Oh, and something I've never seen in any firestick 4k thread:

How to enable developer MENU

hold the Center button for a second; then (still holding down Center), press the Down button too. Hold both buttons for about 3-4 seconds. Then release both buttons and press the remote's Menu button

I might be old, but still learning :)

Edit, when making Fireiso 2021, please make the ethernet connection automatic like the wifi, because I dont like using wifi for my work, and most certainly dont have the time to constantly try to get an ip in order to constantly update fastboot only to constantly be reminded glib needs updated, amongst what else?
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
Hi, I don't think Tee1 and Tee2 is your problem I think your problem lies in rpmb being upgraded after you flashed the latest zip somehow but this could be amazon related in new update bins 6.2.7.6 and 6.2.7.7 , I could be wrong? Idk....

In respect of FB needing updated, this has been pointed out a few times now yourself included. To update it in Archh Linux simply run:

pacman -Sy fastboot

This as you say is only because the kamikiri exploit is outdated now but there are posts explaining how to update via terminal.

Sweenwolf and I can't remember who else described how to flash boot/recovery imgs with windows fastboot connected to the mantis..

Return to stock post describes

Fastboot flash boot boot.img

Fastboot flash recovery recovery.img

This is included in the unlock 4k thread somewhere but it's like looking for the end of a strand of spaghetti in a bowl of fkin spaghetti..

Anyway good you got it working mate

Maybe the OP should be updated with a new updated kamikiri and the additional point you make for returning to stock as sub-post
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Lol. Many thanks for your advice to me. Maybe you're right.

As far as I know kamakiri flashs only tee1, but I'm glad that you telled me about. Maybe you show me the line of code in the script that flashs tee2? I'd like to learn something...

I admit too, that I've never heard anything about your fact, that we have to flash the boot.img with fastboot just infront a rom flash with TWRP. I wonder why in every rom such a boot.img is included!? Maybe because twrp flashs the boot.img always during a flash?? No?

Anyway. Thanks again for your input mate.
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Bertonumber1

I agree with the rpmb bit, isnt that flashed by Kamakiri, I've read also tee copies to tee1 and to tee2 (maybe twice, tee2, could be tee1 & tee2 IN tee2, (modems do same, two copies in one partition) my theory, since it's twice the size?) I agree with the bit where after the 7.6/7.7 updates I could no longer downgrade, explaining my fight with flashing anything, navins suggestion was a wee godsend, I'm not really a linux guy, I do kali wifi stuff, thats it, but fireiso was too much of a pain to update when i was rebooting it 10-20 times a day just to use that and windows, in the end, windows fixed it...

All fastboot commands work, in windows, it's just TWRP that cant flash, prob due to out of date fastboot, now we know the reason, unless twrp really wont flash these partitions, because they are protected, everything else I got twrp on... flashes fine, note the error code I posted earlier that navin caught onto, I think this is why people thought twrp was protecting boot... strange...

Sus_i

I dont read code unless I really need to, but Kamakiri clearly flashes tee, it says so in terminal when shorting,, I basically tried every partition one by one, going down then in order, in the end, what I wrote was how far I got doing same thing over and over until I wiped whatever the unknown problem was, in the end, I posted what I did in the hope it works for others, keep in mind I flashed my sticks retail version 6.2.6.8, ie, version on stick when I bought it, restoring to stock is all I really did, and write how I finally got out of being unable to downgrade. Writing logo and all other partitions was easy, I FLASHED STOCK without Magisk, stock writes ALL.

The partitions I flashed were not flashed because I knew what I was doing, they were flashed because I didn't, it's called testing lol

Edit: As a side note, I am a qualified electronics engineer, and have been for the last 40 years, and I'm now 52. My daughter won a competition at 14 years old, quite simply, she got to build her robot in the basement of Ferantti, MOD stuff u know :)

2 the noobs: MOD = Ministry of Defence!

True hackers know nothing, real hackers went to college, True hackers TEST, real hackers COPY OTHERS WORK.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
It flashs the TZ image to tee1, yes... but for tee2 there isn't a flash part in kamakiri.

But we can easily write to it with fastboot or via dd in a root shell.

That is only valid for flashing a stock rom with the amazon 'stock recovery'.

You see, if you flash a stock rom with twrp recovery, twrp won't flash all the images to the given partitions.

In fact twrp skips most of them and flashs only system, vendor and boot.

Take a look into a TWRP log and in the first post of the 4k unlock thread, if you want to see details.

And ofc that is absolutely unrelated to magisk, tbh.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Idk why you think that tee2 is somehow bigger than tee1 or only half filled? And idk why there should be a pin or checksums.

If you take dd images of both tee partitions, you see that tee2 is just a 1:1 backup of tee1. Thats it.

kb = KeyBox is used for DRM management, nothing to do with OS downgrade things.

Notes for everyone thinking about to try this:

It isn't only tee1 and 2 involved, there is also some unique data...

I doubt that kamakiri will fix a blank formatted kb, as it flashs always the same old tz, i.e. there isn't a reason for the boot process to update kb (no tz update = no kb update). It will most likely remain blank, expect DRM issues.

It's not recommended to format unique stuff. ;)
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Sus_i,

You've completely missed my point.

Lets just say that kb has unique data, after you root with kamakiri.

Then you get blackscreened.

You are told to downgrade or at least flash stock, But nothing you read works.

Now here's what you dont get:

What if the unique data prevented the downgrade in the first place? What if this was the ACTUAL problem? It would appear to be, at least others mention it.

I already mentioned having previously wiped ALL partitions in my attempts to get out of the blackscreen. I simply did not wipe kb during these wipes at this time, because according to kamakiri, kb doesn't exist, so I had to find the correct syntax to wipe it ANYWAY.

My firestick is running better than it did.

Not because I wiped what your saying not to, but because I'm correct, and you are cwrong.

kb is empty when flashing kamakiri.

In fact it is wiped by the kamakiri reflash, you see, Tk writes to tee1, & /or Tee1 writes to Tee2, one or both write to kb, and if kb is not wiped isn't it possible that this is the incrementation that decides what you can flash? So in effect kamakiri resets all three! Wether we wipe them or not, kamakiri does. Oh wait, (take the piss time lol) Tee 1 writes to Tee2, then both write CHECKSUM of each image to kb, all while running the first step in kamakiri, correct? - Cwrong. This is hypothesis.

I just made sure they were wiped!

by doing

fastoot format '' <-Thats 2 ' , not the " used in quotes.

My blackscreen (drm issues if you say so) were solved, no more blackscreen! Oh, and I'll point out that depending on your hdmi LEAD, this may be a green screen, as I found out changing mine ;)

With regards to your first question, Why do I think they are bigger, because R_box sez so, and because mine were, and if you read many others logs rather than nitpicking... as for why there would be checksums, that part was me saying, sound's like modem security, applied to the firestick, albeit in a different way, this part was hypothesis on my part, hence I MAY BE Right or I may be wrong. Kb is a checksum of Tee 1 & Tee2, yes, unique huh? So your Tee1 and Tee2 are identical, just like in modem security.

It was my idea way back in 2010 to apply a mirror image, for modem security on sbh. In fact it was BADad who banned me, an electronics engineer, for showing how to short the isp pin, he then took the credit, now where have you read that? Have you also read my being granted copyright notice (as in I OWN it..) to the hack used by the fbi when they hacked some san-whatever's iphone? I INVENTED IT.

Dont tell other's not to do what worked for me, just because you never solved the problem.

I never solved the problem, I got OUT of it.

Solve problems instead of creating them.

This is not an attack, it is me stating facts and theories with someone's sad attempts to bring me down to their level.

No dis-respect intended :)

My ability to find what other's cant is because I DONT know, what those who know it all DO, I'm not a train stuck on the same track, I'm an all terain kinda chap!

I did the work, and it worked for me, a week all in, but hey...
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
What's going on here then? :)

Did you get your stick working then @Pachacouti? Don't think I've seen a fellow Scot on the forums before. Hey what's up :cool:I've just took my old bricked mantis out of the drawer and got him operational again but tbh I prefer the Sloane box to the 4K stick. I had installed the mantis 4K magisk addons for the Leanback launcher and Google functions (not a good idea) I then had to wipe everything and use fastboot to wipe userdata and... Well... Wipe everything as you describe. But we are good to go and it's working now

Regards
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
lol, alright man, won't pick up any of your bs again... pointless^^
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
It's my fault, I think different, flawed logic used to explain something when I honestly admit to not being able to express myself after so long learning what I read, from retina burnout to I'm too old to go into explanation, I showed a path I took, then explained my flawed logic, for in that flawed logic is the answer you seek, wether you knew the answer or not I dont know, I have yet to find it, but my search ended when I knew it worked, and I wrote my noes here... ok next challenge.. I like thinking like this, it allows me to be free of a mind that can't create and has to listen to a voice.

That voice tells you, what you know, I dont hear voices. I create what you learn, because I'm too far ahead of what it is you know. I know we're both right, explaining different branches that lead to the same path, either could be a cause, or a failure.

The hacker in me says this. People know what they know, the code is there for all to see if you know where to look. I dont see it like that. I ripped open a transistor radio, not to see how it worked, but where the sound was coming from. My dad walked in and says, put it back together. I was 4 yrs old. I'm still looking for where that sound came from today, in my search, I read, the eyes catch on, and write it somewhere...

To quote Riddick.. It was my plan...
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
I want some of what you're on mate.. It may not be a good idea to endulge in hallucinogenics whilst browsing the web.

Now... I managed to brick, unbrick, download stock and gapps and flash my stick again, about the same amount of time it's taken to even attempt to decipher what you're on about???

So you claim to have the wisdom... share it, but share it in an uncondescending and helpful manner, we help each other out here it's what we do.

If you're as knowledgable (and capable) as you say. After all you stated you're "too far ahead of what it is you know" then how about grabbing the source and helping out with Los 14 Mantis on Git? Or maybe having a look at Sloane development now he's unlocked??

Do something productive and help others out who may not be as blessed or fortunate to be as well informed as you seem to be instead of all this philosophy nonsense and talking sh*t that ain't doing anybody good.

"the hacker in you says" I don't know anyone who would openly brag about being one.. Esp on an open forum.
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Lol, I like it, it's like, wtf did I just do... trying to remember the copy n pasted lines aint that much fun... I aint a hacker, I'm better, it's like, discovering what hackers then write scripts for...

It's more 'analogy' than drugs, dont do 'em, but alas, sitting indoors on lockdown aint that good for thr brain...

I do electronics. I post what works, and my idea's always turn out to be either correct or true, and they're all based on what others have written. Aquarius rules, and will do for the next 26.000 odd years...

In the end, the constant updating put me off even using online anymore, it's simply not worth it in my opinion, and now that everythings being shutdown, I wonder how long it's gonna take governments to realise if we cant afford to use online, then bang goes their tracing everyone... Big brother getting too greedy does us all a favour!

Nah, seriously, If I chip in with a way, that's probably THE way, but I'm too old to keep up with the updates, all I really need is someone who can turn what I give into goodness...

Kinda like a translator.
[Fire TV Q&A, Help & Troubleshooting] pav2019:
Hello,

yesterday i bought firestick tv lite and connected but it was showing as "no signal"

for other tvs it working i have checked my neighbors one..

though i have HDMI port its not working.

its SAMSUNG LCD TV. (LA32C350D1)

any suggestions??
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
Hi there how's things? OK if another Hdmi is not an option u can use an Hdmi to RCA converter and use the rca jack's on your TV (provided it has them)as an input solution for your stick.

Also try changing the default resolution on the stick as sometimes this can be the culprit.