yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] hasobist:
Did you try the Android TV rom as the stock rom which it came with must be carrying traces of strings of the stick being blacklisted......

If you can create an empty backup and copy the files of AndroidTV rom to the same and restore will be of some help.

Cheers!
[Fire TV Original Android Development] Selocan20:
I'm happy to announce: it's done!

Now my blacklisted Fire stick 4K is a android TV Box without any dependings from amazon and no gapps installed also. Thats okay for me, i've installed total commander in which i put it in oobe.zip and with total commander installed i was able to install apk's i want like wolf launcher or netflix.

No problems so far, just the home button does not bring me back to home. but the 'guide button' does. its okay :-)
[Fire TV Original Android Development] hasobist:
Wonderful congratulations!

The only solution for the blacklisted at the moment.

Enjoy the new look of Firetv 4k.

You can freeze the leanback launcher and with Launcher manager ultimate in settings customized with Wolf launcher will launch the launcher on boot.

Also check the Magisk modules for Firetv 4k thread.

Happy to help.......

Cheers!
[Fire TV Original Android Development] RonRamon:
Greetings, you can make a summary of the steps from a fire stick with boot unlocked. what ROM did you use?
[Fire TV Original Android Development] hasobist:
Hello!

After unlocking the bootloader Selocan20 used the AndroidTV rom.......

Cheers!
[Fire TV Original Android Development] RonRamon:
Thanks for quick response. Which ROM to use? link? post?
[Fire TV Original Android Development] hasobist:
Hello!

Use the 6.2.9.5 old UI patched rom by Skel40 ,

Works charm for Firetv 4k

Thread 'Fire TV Stick 4K (mantis) Debloated Rom (Older UI) 6.2.7.1/2495, 6.2.9.5_4448, 6.2.9.7/4655' https://xdaforums.com/t/fire-tv-sti...2-7-1-2495-6-2-9-5_4448-6-2-9-7-4655.4084947/

Cheers!
[Fire TV Original Android Development] cityhunter_1919_xyz:
sorry. Wrong reply address
[Fire TV Original Android Development] hasobist:
Deleted
[Fire TV Original Android Development] cityhunter_1919_xyz:
I recommend installing Xposed(LSPosed) and Xposed edge(pro) modules.

Any home app can be assigned to the home button.

Also, by editing the keylayout file, you can smartly change the voice button and other buttons using Xposed edge.
[Fire TV Original Android Development] Selocan20:
Hey there,

Unlock Bootloader

wipe data, cache, dalvik and /system

Install Rom magisk and oobe.zip

Oobe was customized unzip it and create new folder with totalcommander and zip it again.

With total commander i was able to install apk from usb.
[Fire TV Original Android Development] hasobist:
Hello!

Can you link the OOBE.zip too

Will be of help for otbers in the same situation.

Thank you.......

Cheers!
[Fire TV Original Android Development] RonRamon:
Hello Selocan20. Remote control works for you?

I went another route, restore TWRP backup from burcbuluklu.

Do not perform any post-restore wipes. When it starts, it asks me to connect to Wi-Fi and an Amazon account, for that I enter through twrp, mount system and rename the OOBD apk with another extension, restart and there I start at the launcher's home. Already system is rooted and xposed, adb enabled. I tried to link but nothing,

it doesn't detect it, but the RC fire tv app did work on my smartphone.

Manage to install and update spotify, disney+, hbo max, netflix, magis tv, cx explorer. I tried with pluto TV and I couldn't, it sends me to download it from the amazon appstore.

Any suggestions for me to recognize control?

I already restarted it, took out batteries several times but nothing. Control I know it works because it works with other roms. And about the pluto app?
[Fire TV Original Android Development] Selocan20:
I have flashed the newest of this roms.

I don't really know the differences but everything seems to work fine with "my solutions". Only for the Home Button I have to use Guide Button but thats no Problem for me.
[Fire TV Original Android Development] hasobist:
Hello!

The same situation is a different experience than the same situation faced by others as it comes with different flavours.

If you try the same next time the experiences vary,the ultimatum that matters is a working device and a happy fellow member whose knock has been fruitful.

That's xda community, the experiences of many is a solution for many and a new added.

It's all about sharing and removing a little time for someones knock and share😊patience is the key.

Happy it worked for you both.

Cheers!
[Fire TV Original Android Development] RonRamon:
What remote do you have, with shortcuts to popular streaming platforms?
[Fire TV Original Android Development] Selocan20:
How can I install this for magisk 20.4?

Or should I update Magisk with TWRP to install newest LSPosed?
[Fire TV Original Android Development] hasobist:
Hello!

You can update Magisk Manager to 22.1

Never had success with LSposed requires higher API

The magisk module AFTV-MM-20221021 pre-installs the xposed module and xposed edge pro and also other apps which you can delete later.

Cheers!
[Fire TV Original Android Development] oldboy88:
I tried with and without short, model is

Software Version

Fire OS 6.2.9.7 (NS6297/4655)

FireTvHome Version

6460037.1

Serial Number

G4N0VM122045****

I only get Serial protocol missmatch, expected 0000 got 2001

Any chance to get this thing rooted or should i return?
[Fire TV Original Android Development] Skel40:
Return it while you can. 6.2.8.1 or 6.2.8.7 was the last known version to work and anything past it doesn't allow the unlock to go through?
[Fire TV Original Android Development] Selocan20:
Sorry but I need help again because of Error installing AFTV-MM-20221021. This is log:

Load microloader from recovery...

Remove boot patch...

OK

Updater process ended with Error: 1

Install boot patch

OK

Install recovery patch...

ALREADY_INSTALLED

Error installig zip file
[Fire TV Original Android Development] hasobist:
Hello!

Try installing the module from magisk manager.

Cheers!
[Fire TV Original Android Development] oldboy88:
Got another one, its 6.2.8.1, Serial G4N0VM1212144..... Doesnt show up via USB in bootrom-step.sh :(
[Fire TV Original Android Development] Skel40:
Have you tried sudo ./bootrom-step.sh and using an Amazon micro usb?
[Fire TV Original Android Development] oldboy88:
Thank you ... that was missing

"hacked fasboot" showing up, "sudo ./fastboot-step.sh" in terminal giving "1513 Aborted" (Screenshot) ... Doesnt install twrp i think.
[Fire TV Original Android Development] hasobist:
Hello!

Do Ctrl+C which cancels the process.

Try again sudo ./fastboot-step.sh

And when prompted waiting for device ,connect the stick TWRP should be installed and will boot into TWRP

If doesn't work try only ./fastboot-step.sh

Cheers!
[Fire TV Original Android Development] oldboy88:
Hi, thank you! Got the same message again for both ways writing the command:

[root@sysresccd ~/Desktop/kamakiri]# sudo ./fastboot-step.sh

waiting for any device

fastboot: core/libsparse/sparse.cpp:131: int write all blocks(struct sparse file *, struct output file *): Assertion pad >= 0' failed

/fastboot-step.sh: line 5: 2049 Aborted

(core dumped) fastboot flash recovery bin/twrp.img

[root@sysresccd ~/Desktop/kamakiri]# ./fastboot-step.sh

walting for any device

Terminal - root@sysresccd: /Desktop/kamakirí

fastboot: core/libsparse/sparse.cpp:131: int write all blocks(struct sparse file *. struct output_ file *): Assertion "pad >= 0' failed

/fastboot-step.sh: line 5: 2091 Aborted

(core dumped) fastboot flash recovery bin/twrp.img

EDit:

Ok, did it manualy from a win machine, took the twrp.bin from bin folder, and installed via fastboot flash recovery twrp.img, booting with fastboot oem reboot-recovery

Now in TWRP, thanks for your fast replys!
[Fire TV Original Android Development] hasobist:
Hello!

Wonder! why it did not just continue reboot followed by command and fastboot flashing the TWRP image,were you trying run fastboot from amonet folder and were you using fireos of Linux based system or a VM?

nonetheless you got it working,congratulations. If you connect it to a USB-OTG which will trigger TWRP for 5seconds and you can enter recovery using a USB mouse if needed apart from adb being an alternative too just in case.

Enjoy your unlocked stick......

Cheers!
[Fire TV Original Android Development] oldboy88:
Hi! Yes exactly, had loaded the fireiso-2.0.0-amd64.iso from the first post here and written it to a USB stick via balenaEtcher and booted from it.

Then loaded kamakiri-mantis-v2.0.1.zip, unpacked and opened the terminal console in the kamakiri folder and started ./bootrom-step.sh. After this has gone through, the command line only gave out, after entering ./fastboot-step.sh:

"fastboot: core/libsparse/sparse.cpp:131: int write all blocks(struct sparse file *, struct output file *): Assertion pad >= 0' failed

/fastboot-step.sh: line 5: 2049 Aborted

(core dumped) fastboot flash recovery bin/twrp.img"

... Then I booted my Windows 10 Machine, and flashed/ booted from there as described TWRP as recovery.

I have absolutely no idea why it didn't work in the Linux Live CD, but I'm glad that it finally worked from Windows, interacting with a mouse via otg also helped me yesterday when flashing FIREOS 6.2.9.7 Debloated (https://xdaforums.com/t/ fire-tv-stick-4k-mantis-debloated-rom-older-ui-6-2-9-7-4655.4084947/page-13#post-88864753)
[Fire TV Original Android Development] hasobist:
Hello!

Okay, may be a Linux based VM like Ubuntu would download all the necessary modules,always tried on the same never had problems.

Thank you!

Cheers!
[Fire TV Original Android Development] ErdbeerbaerLP:
Does this still work? I tried like three hours to get this working, but no luck. Getting Serial protocol mismatch every single time.

SN: XXXXVM099XXXXXX

FireOS 6.2.9.7
[Fire TV Original Android Development] hasobist:
Hello!

Return it if possible,as the versions 6.2.8.1 and older could be successfully unlocked,the higher versions are patched and can't be unlocked.

Cheers!
[Fire TV Original Android Development] ErdbeerbaerLP:
Now i need a downgrade method tho. Do they even exist without having root access prior?
[Fire TV Original Android Development] hasobist:
Hello!

Unfortunately no.

You can't do any as the efuse is burned.

You need an unlocked bootloader to make changes to the /system.

Personally have one which is patched

Used the TechdoctorUK apk to disable apps and the Launcher manager ultimate and Wolf Launcher for launcher support,can't add widgets though.

Cheers!
[Fire TV Original Android Development] Sus_i:
Even 6.2.8.7 is patched by default, but any older version will unlock fine.
[Fire TV Original Android Development] smogglet:
hi i am having problems when shorting the points and connecting to my pc (see picture) is there any hope for my firestick am i doing something wrong?

appreciete any help
[Fire TV Original Android Development] hasobist:
Hello!

Try without short,it works.

All looks good

Try runnin all the following commands again afresh,by opening a terminal in extracted folder of kamakari-2.0.1 by opening the folder:

sudo apt update

sudo add-apt-repository universe

sudo apt install python3 python3-serial python3-usb adb fastboot dos2unix

Make sure ModemManager is disabled or uninstalled:

sudo systemctl stop ModemManager

sudo systemctl disable ModemManager

After so,run sudo ./bootrom-step.sh

Connect the stick,let the script run to booting the stick to fastboot

Run sudo ./fastboot-step.sh

Should boot to recovery.

Let me know.......

Cheers!
[Fire TV Original Android Development] dom019:
Hi! I bought a firestick 4k and I managed to unlock bootloader and install fire os 6.2.7.3 (a lot old version). Now I can’t use the remote controller, it is the controller with netflix, youtube, disney+ buttons. I have two remote and it’s the same story, I cannot pair them and I can’t go through initial setup. I think that the issue is related to a kind of inconpatibility with the old version of fire os and the new generations remote. Anyway I can use my tv remote to allow adb, but I can’t skip the initial setup. I managed to connect to wifi my firestick and I can also use the fire tv app on my phone but I still can’t skip the initial setup, I also managed to go in settings and launch the amazon launcher but there is a kind of lock, I cannot open the amazon log in page and can’t see apps or home in the amazon launcher. When I reboot there is always the pairing screen. Can you help me to skip in some way this screen?
[Fire TV Original Android Development] hasobist:
Hello!

Since you're unlocked.

Do you have a USB-OTG?

if so you can boot to twrp using a usb mouse and you can flash the patched rom 6.2.9.0-Nightly by Skel40 or recover the stick.

It directly pairs the remote then wifi and to the registration screen.

Kindly provide more info and answer the above.

Cheers!
[Fire TV Original Android Development] dom019:
The problem is that I don’t want to change rom because this was an old rom with the patched sky go app. By the way I just managed to bypass that by installing a OOEB launcher found in this thread
[Fire TV Original Android Development] hasobist:
Hello!

Try resetting the remote and pair.

Cheers!
[Fire TV Original Android Development] dom019:
Already tried, I think it is not compatible with this rom os 6.2.7.3
[Fire TV Original Android Development] hasobist:
Hello!

Try with fresh batteries.

You can use Titanium backup to backup Skygo app with data and restore it back.

Or you can backup data using twrp and restore it after the setup of new rom,should work.......

Cheers!
[Fire TV Original Android Development] dom019:
It is not a matter of batteries, this 6.2.7.3 rom doesn’t support the 3gen remote controller, I cannot use titanium because this rom has some fix for skygo app, it won’t launch in another rom without these fixs
[Fire TV Original Android Development] hasobist:
Hello!

Can you forward me the skygo app your using.

What I meant was try pairing the remote with fresh batteries.

Did the stick boot?

Will check the skygo app on 6.2.9.0 and let you know as this version of Rom is patched to unblock blocked services by Amazon.

Thank you.......

Cheers!
[Fire TV Original Android Development] dom019:
Sky go apk is the latest version you can find on apk mirror, aptoide etc https://www.apkmirror.com/apk/sky-italia-s-r-l/sky-go-it/

The rom I’m using has some hdmi check bypass specific for this app, it will probably show some error when you try to launch the app on your rom, because it checks if the device is connected via hdmi.

The rom I’m using:

6.2.7.3-mantis-skygo

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

Maybe I’m not expressing myself well, the firestick boots, but I’m stuck on initial setup in the first-pairing screen, because my two remote controller (1 of the mantis fire and 1 from the fire 4k max) don’t pair. It is not a matter of fresh batteries, I think that these new gen remote controller are not supported by this old rom.

The stick boots, I have adb enabled and I also managed to connect the stick to wifi with adb, but I am stuck on this pairing screen
[Fire TV Original Android Development] hasobist:
Hello!

What I did was

Flashed the skygo.zip over 6.2.9.0 nightly without wiping data

Was trying the skygo 6.2.7.3.zip and tried flaghing over 6.2.9.0 by wiping /system,cache,dalvik

DID NOT WIPE DATA

mounted system in twrp

Went to Advanced then filemanager then system then priv-app then com.amazon.oobe click on it and long press the apk and rename it to .apkk(just add 'k")

Swipe to confirm then back click A level

Go to Device software Ota and rename

As the wolf launcher was already configured the

Stick booted fine and the remote 2nd gen remained paired and could use a fully functioning 6.2.7.3

-----------------------------------------------------------------------------

What you do is:

You'll need a USB-OTG and a usb mouse so that you can boot into twrp by clicking cancel.

Once in twrp

Go to mount click and tick system

Come out and then go to Advanced then file manager then system them priv-app then com.amazon.oobe and click and long press on apk from options seleck rename and rename it from .apk to .apkk swipe to confirm and back and reboot system.

Now you should directly go to the launcher screen

Then you rename the oobe.apkk to .apk

Should work.

Let me know........

Cheers!
[Fire TV Original Android Development] Skel40:
The package is com.amazon.tv.turnstile most likely (Fire TV Remote)
[Fire TV Original Android Development] hasobist:
Hello Skel40!

Was surprised to see the reverse way around work perhaps many times.

Cheers!
[Fire TV Original Android Development] Sus_i:
Yeah. ;) In case of blocked devices, probably the only way.

Do you know if it will work with the stock launcher?
[Fire TV Original Android Development] tsynik:
It need testing. Stock launcher needs account to work, but it can also be put to "Frozen" offline mode so only Settings will be accessible.
[Fire TV Original Android Development] aasoror:
Yes and it was working.

Nope, it was connected to wifi, updated to the latest OS but never logged into with an amazon account.

Thing is if I did break the capacitor, I can't see it (posted pictures couple of pages back).

Yup, that's similar to my situation, the only difference that first attempt to run the script was successful (script was waiting for the short, and kicked in once the short was applied), so whatever damage done seems it was afterward.
[Fire TV Original Android Development] k4y0z:
You would have to flash stock update-bin via TWRP first and then flash she stock boot.img from that same update-bin separately via hacked fastboot.

Amazon recovery should then be restored on first boot.

It will likely not work in a VM.

Sounds like you have an issue with your EFI-NVRAM, find out how to clear it from your current OS.

Typically it would be reset to factory defaults after clearing.

[MENTION=5665338]kigba[/MENTION] [MENTION=1047674]aasoror[/MENTION]

At this point it's unclear why this is happening.

For some reason the preloader is never loaded allthough it seems to flash without issues.

That is evidenced by the fact, that your device goes straight into bootrom without shorting and you see the message:

One reason why the preloader would not be executed is because of a signature mismatch.

If that is the case, that would mean your sticks are running a different firmware,

since the firmware-files that are available to me only contain one preloader (i.e. signed with the "standard" signature). [MENTION=1047674]aasoror[/MENTION], since your stick was working before, do you remember the exact firmware-versions it was on?

I did notice, that both of your sticks use a "hynix" EMMC, while most here seem to have a "sandisk".

That in itself shouldn't be a reason for the exploit not to work, but it may be an indicator.

So if you can give some details, when and where you bought the sticks that may help.

Also I would like to ask anyone else in this thread if anyone with a "hynix" EMMC has been successful running the exploit.
[Fire TV Original Android Development] aasoror:
Thanks for the reply k4y0z

note that first time the bootrom script executed it did work properly (waiting for short and completing without warnings or error messages), the proceed without shorting and the warning about rpmb came on all subsequent reruns.

Unfortunately no, because I never logged into the stick, just connected to my wifi and it pulled the latest firmware update (as of couple of weeks ago). I had it for roughly a year and only unpacked it because of your thread :)

Good eye, that might be a lead as well.

Amazon Canada, November 2018.

would be more than happy to run any diagnostic scripts on the stick if you want.
[Fire TV Original Android Development] kigba:
Hello. Yes, my friends have fire sticks with hunix memory and they successfully unlocked their devices. I know at least two people.
[Fire TV Original Android Development] Sus_i:
probably won't help, but besides sandisk I had SEC samsung chips here.
[Fire TV Original Android Development] extrem0:
I have two 4k sticks with hynix (one of them with broken capacitor) working fine after running the exploit. Both purchased on November 2018 from Amazon USA.
[Fire TV Original Android Development] k4y0z:
[MENTION=5665338]kigba[/MENTION] [MENTION=1047674]aasoror[/MENTION]

can you please run the bootrom-step from the attached file and send me the output in a PM (since it contains device specific information).
[Fire TV Original Android Development] aasoror:
With or without shorting?
[Fire TV Original Android Development] k4y0z:
Since it currently goes into bootrom either way, that wouldn't make any difference.
[Fire TV Original Android Development] t3ch42:
Appreciate the reply. Thanks!
[Fire TV Original Android Development] k4y0z:
[MENTION=5665338]kigba[/MENTION] [MENTION=1047674]aasoror[/MENTION]

From the output [MENTION=5665338]kigba[/MENTION] has sent me, it doesn't look like a signature issue.
[MENTION=1047674]aasoror[/MENTION] if you could also sent me your output to confirm that please.

Also please use the attached file wich will dump the boot0 partition after everything has been flashed.

Please send me the file, that is being created (boot0.dump)
[Fire TV Original Android Development] X04D:
Before I do anything stupid...should I plug in and update the Firestick first, or can I just do this out of the box?
[Fire TV Original Android Development] kigba:
thank you very much! My stick is alive thanks to your support! Installed twrp, adb commands work! Thanks again for your work! :)
[Fire TV Original Android Development] k4y0z:
What?

What did you do to make it work?
[Fire TV Original Android Development] Sus_i:
Yeah, do the initial setup, update until it's up-to-date, enable adb debugging and then do the unlock steps.

Edit: After the unlock, install magisk & mm, block updates with adb shell.

:laugh: :good:

How many bootrom-step attempts did you run?
[Fire TV Original Android Development] xam1988:
kigba's

boot0 dump

View attachment boot0.zip

And result:
[Fire TV Original Android Development] aasoror:
Just one, but now the system boots into a green screen (TWRP boots fine though, so it's not something physical with the HDMI).

---------- Post added at 08:26 PM ---------- Previous post was at 08:14 PM ----------

Nothing, just run the two scripts back to back. :good:

Is that zip flashing a different image?

Regardless, you just breathed life back into the stick, thanks for that :)
[Fire TV Original Android Development] Axecaster:
To clarify, can we use a linux system that successfully ran amonet, or must only the live ISO from the first post be used for mantis?
[Fire TV Original Android Development] Skel40:
Right! I was extracting 6.2.7.3 and I saw the turnstile package and saw 500+ kb .apk and I extracted 6.2.9.0 and found a 3,000+ difference. Update it and see. I'll find alternatives if needed @dom019
[Fire TV Original Android Development] dom019:
How can I update it to be it compatible with my remote?
[Fire TV Original Android Development] dom019:
Thank you, I’ll try today
[Fire TV Original Android Development] hasobist:
Hello!

Skel40 is trying to help out find a solution to patch the Rom for it's functionality and compatibility.

Cheers!
[Fire TV Original Android Development] dom019:
Thank you

I tried to install from twrp https://xdaforums.com/t/fire-tv-sti...s6290-recommended-scripted-patch-rom.4298357/

6.2.9.0 rom but when I reboot it is stuck on fire tv logo
[Fire TV Original Android Development] dom019:
Maybe can you link me the rom to install?
[Fire TV Original Android Development] hasobist:
Hello!

Thread 'Fire TV Stick 4K (mantis) [Patched] Cleaner Fire OS (NS6290)' https://xdaforums.com/t/fire-tv-stick-4k-mantis-patched-cleaner-fire-os-ns6290.4084947/

There you go.......

Cheers!