Updating from 6.2.6.3 should be no problem at all if you did the unlock with kamakiri 2.x, then your stick got already all images needed to work fine up to 6.2.7.7 (and now you can re-do the bootrom-step without to short).
[[email protected] ~/Desktop/kamakiri]# ./bootrom-step.sh
[2023-01-05 13:51:18.465124] Waiting for device
and booted up to stick, with only MobilePhones Hotspot and only 2G data rate, skipped inital update with MENU + BACK, log in my account etc, set ADB +unknown devices ON - And checked the Version.... And of course cleared the updated files (after the pictures were made)... That all works without any new Software download/installation...
I initially had no luck without the shorting using the method here and with the ubuntu guide the 3/lite thread. After trying that, I returned here with the FireOS.iso and with shorting got identified like you. Mine was also new @ 6.2.6.3 old but younger thna yours!
It's funny how stressful this was, and I've been doing CE mods for decades. But this was the first time I was a follower and sweaty palms uncomfortable at the though of killing a $20 stick!!!
Totally Right! I also have some rooting history with phones and Samsung TV. I didn't not hesitate to root my 1000 EUR TV (2012 series) with less expirenence than now... Actually I didn't want to root anymore. Sometimes it eats just time... Hunting for updates/new ROMs/Kernels etc... But that happens if there is some free time because of new years hollidays. And did not accept my own dumbness to update the first stick out of the box! Look here
forum.xda-developers.com
Thats fine, will unlock 100%.
forum.xda-developers.com
Yes - And thanks again to you as well. Your discussion with Iceweasel helped a lot...Edit: Just saw your later post, glad that it worked out fine for your stick
mantis:/ # ls -lZ /data/misc/adb/adb_keysNVM after restarting the laptop and stick a 4th time something's different and the request appeared again on the stick. I unchecked the option to always accept hoping that will prevent this in the future.
Hi there
Nevermid... Just noticed that Pretoriano80's Kernel (which I'am at 6.2.7.7 - 3033) as insecure ADB - Therefore no ADB RSA Keys are needed - And no popub came up - Even if file (on FireTV) /data/misc/adb/adb_keys is deleted/renamed.
Again we are fiddling at the same place - I wonder why?
Even if its not needed for your case anymore - To reset the RSA Key its needed to delete/rename files on the sending and receving side (one side should be enough as well, but to keep it clear... both)
Basically you don't need to wipe anything infront or after a flash... especially not data, since there are all your settings, account, apps and so on stored. If you disable updates this setting gets also stored on data.
I questioned wiping data every time I did it... seemed counter productive unless wanting to roll back to do something like have to walk through initial setup.
The roms I have are also safe to flash as well. I have downgradable roms without the efuseDepends on you, if you like the old fireOS launcher use 6.2.7.7 (renamed to zip):
and if you like the new launcher UI then flash rbox 6.2.8.1r2.
Don't wipe anything, rom flash is enough.
If you want to flash a more recent fireOS at some point, make sure you think twice, i.e. keep your efuse from burning: @SweenWolf uploaded a patch somewhere which deletes the efuse burn script and @Pretoriano80 does also similar patches including his awesome custom kernel:
[KERNEL][FireTV Stick 4K] Custom Kernel For AFTV 4k - 6.2.9.4
Warning !!! Use this kernel on your own risk...
I had the same symptoms with an unopened 4K obtained from a private sale.
I was in trouble with the same error before, but I was told by this reply.
./bootrom-step.sh./fastboot-step.shecho "--update_package=/path/to/zipfile" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery
