yashsingh1/xdaforums huggingface dataset:
[Fire TV Q&A, Help & Troubleshooting] Donphillipe:
I plugged the Windows formatted USB stick in the PC (eFat works for read like this but has problems with backing up to it but you are OK reading off an eFat), downloaded the zip file to the stick., plugged the stick into the powered hub where the mouse is plugged in and the hub is powering the AFS through an internal or extra OTG, powered off and back on the stick which booted to TWRP, clicked cancel to get TWRP Menu, clicked Install, clicked Select Storage, looked at the file sizes of all the storage options and selected the one that matched the total capacity of the stick, then opened the folder where the zip restore file was, selected the full zip restore image and slid the slider to the right with the mouse to begin install. I then saw the text going across the TV screen stating which directories were being restored, then it stopped, then I selected the option to wipe the two caches and clicked the reboot option and the the firestick rebooted with no TWRP menu this time but back to the black and white menu, then to the orange over white background where the device takes a long time to go through its initialization sequence and then after a few minutes it boots back into the option to pair the remote, sign on and do all that stuff again. I did a complete initial configuration again and checked out the quality of the restore by signing in and poking around, then got up my nerve and applied the exploit once more.
[Fire TV Q&A, Help & Troubleshooting] rpmuploads:
Hi! I have exactly the same problem as @Simpson84. I've cloned the 4 partitions (system image, vendor image, data and boot) from one 4K stick to another (same model) via TWRP backup / restore, and now the stick which I've restored into is stuck at the black screen with with fire tv logo (does not reach the white and orange screen boot with the 3 dots). I have access to TWRP and I've already tried everything I could remember:

- flash stock images (update-kindle-mantis-NS62* - tried with several versions)

- wiping cache, dalvik and data

- flash rooted images

- re-run exploit again

- rename backed-up partitions from win to img and flash with fastboot

However, the result is always the same. The normal boot does not get past the black screen with white logo.

Does anyone know any other possible solution?

Thanks!
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
Redo the unlock process.

Then format data (type "yes) and then push your rooted rom and magisk back to mantis /sdcard.

Reflash

Wipe dalvik and cache

Reboot

Don't rename any partitions just let kamikiri do its work
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
If you can get into twrp, maybe try the 'format' data option, type yes, then wipe system/vendor, cache, dalvik, then install the kamakiri.zip and the latest stock rom followed by magisk.
[Fire TV Q&A, Help & Troubleshooting] rpmuploads:
Many thanks both to @Bertonumber1 and @Sus_i :)

I tried your suggestions but the 4k stick keeps stuck at the black and white logo. I have another two 4k sticks, one for android development and testing and another one for the living room, so I don't really need it. I just wanted to fix it for the challenge and because it seems that there's nothing wrong on the hardware side.

You can see in the attached images my attempt to recover.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Looks almost ok from here.

Only thing to remember is that you've to flash magisk behind the stock rom, as the last step just before the reboot... If you flash Magisk infront the rom, Magisk gets overwritten during the stock boot image flash.

In case that won't help, I would flash the kamakiri GPT-fix from here:

https://xdaforums.com/showpost.php?p=82629101&postcount=838

Extract the two files from the zip in the kamakiri folder, make sure that the gpt-mantis.bin file goes to the bin folder... then run this using the fireISO:

./gpt-fix.sh

(you need to short again).
[Fire TV Q&A, Help & Troubleshooting] rpmuploads:
Thanks @Sus_i. Indeed I'm always flashing the rom first and then magisk.

I've shorted the stick again and ran successfully ./gpt-fix.sh but it's still stuck at the black and white logo.

Probably I'll try to install the LineageOS to see what it looks like.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Unfortunately, there isn't a lineage rom for the 4k.

Have you tried to install a rom + magisk behind the gpt-fix?

If yes, I can't think of a reason why the stick won't boot at this point.
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
You may try returning the stick to stock,

https://xdaforums.com/t/fire-stick-4k-return-to-stock.4163417/

lock the bootloader again and do the whole process over.

I had this problem before with mantis and the only way I could get it to work again (Unlocked/Rooted) was by locking it down back to stock, letting the stick do all the ota updates :

Then after doing the short process over.

Adb Push to /sdcard

6.2.7.1 prerooted (or a rom of your choice)

Magisk 21.1 zip

Install prerooted first

Then flash magisk

Wipe dalvik/cache

Reboot

It's a pain in the ass and a long way to go but it workes in my case anyway. If your sticks not working then it's worth a shot
[Fire TV Q&A, Help & Troubleshooting] rpmuploads:
Thanks @Sus_i. Yes, I've tried to install a rom + magisk behind the gpt-fix, but it is still stuck in the black and white logo.

Thanks @Bertonumber1, I'll try your suggestion and I'll let you know.
[Fire TV Q&A, Help & Troubleshooting] rpmuploads:
Thanks @Bertonumber1, I tried your suggestion, locking the bootloader again and doing the whole process over, but it still doesn't pass the b&w logo. I've attached step by step images.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
@rpmuploads

Just curious, have you tried to boot the stick without the otg stuff? Powered via the orig. usb cable/power supply?
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
yep , id second that .....its the only thing else that i can see stopping your 4K booting up as everything else seems bang on.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Yeah, could be a power issue, can even mess up rom installs with TWRP.

To make sure, I would short again, do the kamakiri stuff and as soon it boots into TWRP, use TWRP commandline in order to install a rom and magisk, wipe cache, dalvik and data (with the orig. cable).
[Fire TV Q&A, Help & Troubleshooting] rpmuploads:
I've just tried it now - still the same.

This all started when I did a twrp restore from backed-up partitions (system image, vendor image, data, and boot) from another stick (exact same model, i.e. Model E9L29Y). It seems that the restore has overwritten specific information for the stick, which is not able to be recovered by any means. I've also tried to launch Android Studio while the stick is stuck at the logo to see if I could see any error messages in the logcat, but at this stage the stick is still not connecting through adb.

I did a restore from another stick trying to fix a minor issue:

When I used to access menu Settings > Fire TV > About, instead of displaying the information (Serial number, version installed, etc) I was kicked out to the main settings menu again. The error in the logcat was related with some java virtual function not existing - getPictureQuality. This was only happening with a rooted rom, if I reverted back to the stock then the "About" option was working correctly. The other stick from which I was trying to clone was also rooted but didn't had this issue.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
System, vendor and boot gets replaced during a rom install. Data and internal storage should be ok, as you wiped/formatted it already. So its nothing special left from your TWRP restore.

All the device unique stuff (like the serial no, mac address, etc) stored in boot1 area should be ok, a data loss is really rare, but who knows. You can do a quick check if you like with TWRP, mount system and then run the 'idme print' command in adb shell. In the printout should be the serial of the stick, BT and Wifi mac_addr, board_id, bootcount, the header of KB and DKB partition and so on. If you do this, don't post your unique data here.

Edit: Have you tried the sideload option described in the posting here?

https://xdaforums.com/t/unbrick-fire-tv-stick-4k-help.4021923/post-81843717
[Fire TV Q&A, Help & Troubleshooting] rpmuploads:
Thanks @Sus_i.

I've executed the 'idme print' command and the output seems ok.

I've also tried sideloading a stock rom as the thread you've indicated suggests. Still stuck at black and white boot.
[Fire TV Q&A, Help & Troubleshooting] 0815hoffi:
Have you tried

# fastboot erase userdata
[Fire TV Q&A, Help & Troubleshooting] 0815hoffi:
Or

Wipe /system in twrp and than flash firmware.zip
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
This is really weird I had the same thing happen on one of my mantis, but as soon as I flashed stock and locked bl then done the short process again.

It worked but only after I unplugged otg and made sure I was using the actual amazon cable and plug.

There must be a Corrupt boot partition or something @rpmuploads
[Fire TV Q&A, Help & Troubleshooting] rpmuploads:
Hi @0815hoffi and @Bertonumber1

I tried the # fastboot erase userdata and wipe /system and flash firmware, but still the same.

Many thanks for your help anyway :)

I think I'll call it a day.

For everyone else reading this, please be reminded that trying to clone a 4k stick to another using twrp backup/restore is very likely to brick your device for good (although I'm still curious to know why/how).

Cheers,

Rui
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
Maybe leave it a week and go back to it.

These amazon devices are good for miraculously coming back to life.
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Mine went to black screen too, however... it seem's to be connecting via wifi, and doing things,adb is fine, but no main page... It might have something to do with the fact I deleted my amazon account after rooting it, worked flawless, then again, perhaps they've updated the 4k, perhaps they've changed the server addy for firestick auth, but I reckon I should still be able to at least view the menu, aargh....
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
You could try a shell command

adb shell

su

pm enable com.amazon.tv.launcher

pm enable com.amazon.firehomestarter

Failing that you could always use easyfiretools to install a custom launcher and use that to navigate
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
well, woke up this morning and thought I'd try reflashing mantis-6.2.7.1-rooted_r1, which is what I had on it since last posting regarding this, done the fireiso, wiped dalvik and cache, rebooted hoping for a fresh start, nada, went past fire logo to black screen. Before I did this, I got past this screen to the android logo of mantis-6.2.7.1-rooted_r1, which then went to black screen....

So I decided maybe it's time to upgrade since it's blackscreening, so I fireiso the mantis-6.2.7.7-rooted_r1, and i got the same result, black screen after fire logo, and I cant quite use adb shell, because I cannot start the firestick to enable debug in order to adb shell/su...

perhaps I've missed a beat between mantis-6.2.7.1-rooted_r1 and mantis-6.2.7.7-rooted_r1?

Any help at all would be appreciated, my head hurts straining the eyes to see whats left of the short pads lol...

Edit: I also noticed since flashing mantis-6.2.7.7-rooted_r1, I cannot reflash the first mantis-6.2.7.1-rooted_r1 which worked so well for so long...
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
That should still be possible. Maybe re-push the 6271 zip and magisk to /sdcard.

In case you run a 'format' data (Button in wipe section) and then a rom flash + magisk, the stick should just work as a new one. If not, check the power supply/cable. Besides that, make sure that the thermal paste/pad and the heatshield is in place ( if there was one^^ ) .
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Hmm.. dont have an otg splitter to use twrp buttons, cant swipe, this is what I did:

./bootrom-step.sh

./fastboot-step.sh

adb push mantis-6.2.7.7-rooted_r1.zip /sdcard/

adb shell

twrp install mantis-6.2.7.7-rooted_r1.zip

twrp wipe cache

twrp wipe dalvik

reboot -p

My power is a 2.5 mA powerbank, runs perfect, it's not power, all is flashing a-ok, I've tried direct into pc too, in order to flash, it flash's fine, power is not the prob, my prob is getting past the black screen, cant get to amazon login, it's just a black screen after fire logo, before I flashed this lates 7.7, I at least saw the android logo of the old 7.1 version.

All I did was unplug it for the night, next day, blackscreen, most likely its had a micro update or sumat blocking it getting to start screen?
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
I understand what youre saying about power supply , as @Sus_i says also. Power shouldnt be ruled out here with regard to booting into fireos...if you could try with proper amazon adapter and cable plugged into the wall, not usb ports on pcs etcetera, these sticks are known for being fussy , even low batteries can cause to not boot to fireos in some rare reported cases 🙄

If power is then ruled out try formating data and if all else fails short it again from scratch .
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Ok, used origional as new previously unused Amazon power supply for this stick, just fireiso'd again, it will NOT downgrade to the 7.1 version that crashed, this only happened after I tried the 7.7 version, so something is preventing a downgrade, prob magisk, as I think I flashed latest magisk zip, which makes sense, twrp is fine, just cant downgrade, so its flashed with the latest here, and I cant get passed fire logo :(

edit: I flashed Magisk 20.4.zip and it flashed fine, no errors in fireiso except not being able to find 7.1 after sending it to sdcard... but 7.7 was found?
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
Wierd ! So are you booting up to the fireos on 7.7??Not meaning to sound daft but did you rename 7.1 from bin to zip when you adb pushed , i would try doing the whole thing over again tbh ...i had similar experience when i flashed a magisk addon and couldnt get to boot or even get to recovery .
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
I didn't rename anything, I flashed the zip as it came... I have done this before, so it's not like I f'd up somewhere, it's like after th fire logo, 30 seconds of dark before it fades to black screen where it would normally start into connect to wifi, after showing the android logo present in the 7.1 version. I just plugged it in last night expecting to watch a movie, got past the fire logo to the android logo, after android logo, it blackscreened where I would expect to see leanback launcher, which is what I used, all worked fine until this point. When I resorted to flashing, I simply used fireiso I have on a dedicated 16 gig sd card, booted it up, flashed 7.7, then magisk, flashed dalvik and cache, rebooted hoping to have fixed it, but only got passed fire logo, android logo no longer shows, duno if it's still that or another, cause it blackscreens before I can start to input wifi details :(
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Hmm.. what else I remember, was that after I rant the boot script, the firestick rebooted before I could do the 2nd command, but it did boot back into twrp, did 2nd command, then flashed the rom, followed by magisk, 20.4, but no joy, I've repeated the same, and expect it to do same, so I'm downloading the stock 7.1 just now, I'll grab the 7.7 stock too, then get at it till I figure it, I do however think it's been forced some update, as I seem to remember a kind of short freeze happening once or twice while watching using modbro, just put that down to lag/buffering as it was raining at the time, I'll post back with logs when I get them...
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
Your best bet is to start over my friend , i know you have done this before and i dont mean to sound undermining , its hard to portray in writing what is meant sometimes , be careful with version 7.7 as it breaking a lot of things such as audio passthrough in kodi for some members .

Amazon devs seem to be hell bent on breaking things just now by pushing sinister ota bins through so be cautious incase there are any unknown hidden nasties that could prevent certain things f4om working by flash etc.....

I would try to format data

Wipe everything

Resend your zips (if using usb flash , try direct push and install from sdcard itself )

even try patching boot.img in magisk manager beforehand , rebooting to hacked bl and using pc fastboot flashing the img to bootx .

If that fails short the mofo again and go back to 6.2.7.3 or your last working rom
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Lol, thanks for the advice, I had origionally done this over and over often enough to know something is not quite right this time round. I have noticed a few oddities that I never noticed before...

When I load up fireiso, I see in the explorer left pane, Devices: AFTMM, and in Network, it shows mtp://Amazon_AFTMM_G070VM1602140DDA/ which changes when doing the first step. earlier, it rebooted itself after the first step, of it's own accord, and booted into twrp rather than the fastboot mode required for the 2nd step, and when I ran the 2nd step and got into twrp, the explorer pane then shows some 'omni amazon' maybe I just never saw these because I was'nt looking for them b4. In the omni, I can see previously flashed zips, including leanback, and my pushed background etc...

So this time, I did it all over again, same result, black/blank screen after fire logo.

I reckon what you say has happened, after all, I actually deleted my amazon account around 6 months ago, the one used for the firestick, and I'm surprised it lasted so long without an actual account, perhaps they cleared out the old account's, and sent an update to ensure this, because before I resorted to fireiso, even though the screen was black, I noticed in my tomato router, that the firestick was still active, and sending/receiving data, but I tried the stock, same result, black screen on start, no point in logs, since they are a-ok with regards to the actual flashng...

I guess others will be looking to fix this too soon if amazon has indeed sent an update, or cleared out the old accounts... I'll prob try again in a few days when my parrot shuts up long enough to let me concentrate, I wonder if he's saying, give up, it aint worth it...

Thanks for the help ;)
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
What youre describing happened to another 4k stick owner a few weeks back after he tried to clone another stick (his other one) I guess the "AFTMM"means you had the magisk addons , playstore , leanback etc ?

The omni mantis/fire thingy is just how linux defines the connected device in that mode.

The magisk/playstore/leanback addons thingy changes the device name ij terminal/adb permanently somehow ( well until it is edited back).

Its funny you mention about using your stick without the account .Today i also noticed this with my 2nd gen sloane 5.2.7.6 , whenever i booted the box and the custom launcher appeared ( amazon launcher / firehomestarter disabled) i would get an annoying login webpage appearing fullscreen size , and it wouldnt let me enter credentials .when i closed the screen using task manager another nag would appear with "authenification error" . I even tried disabling com.amazon.oobe which deals with registration etcetera.

The only way round this was to reflash stock prerooted 5.2.7.3 , register and login and disable everything again.

Anyway no problem mate dont give up perhaps you could try going back to stock again, locking him down and then redoing the process over
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Ok, if you can't use the gui, the only way to format data is via hacked fastboot:

Boot into TWRP, connect with adb shell, type: reboot-amonet

Then run fastboot devices and in case you can see the sticks serial, run this for a format data:

fastboot format userdata

fastboot reboot

That's the point about formating data, make sure that the filesystem is fine and ofc it cleans all installed stuff from data and /sdcard.
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Only givin in 4 a wee while, in the hope of refreshing my memory, and I can imagine there have been a few changes since the 7.1 version. I do reckon however that it is account related, maybe they started matching macs for the ban hammer, send a script to stop it passing into the main screen to connect to wifi, seems enough when I think about it, as it ran flawless, I didn't have gaps, playstore or anything amazon related, and had alot of the amazon address's blocked in my router, making me think perhaps they changed an addy or so, and obviously after the first wipe I'd have to log back into my wifi, but origionally the wifi had connected to router, even though I could not get to amin screen, I first thought it was the leanback launcher had reached it's eol, but hey, another day...
[Fire TV Q&A, Help & Troubleshooting] Pachacouti:
Well, I got it working again, but cant go back to the version I was using. Seems there have indeed been a few updates, including the stbemu no longer working, no streams are getting played, just black screen, every url :(

kinda pointless having one now...
[Fire TV Q&A, Help & Troubleshooting] navin23:
I have the same issue with doing a Backup/Restore with TWRP from one 4k stick to another.

I'm stuck at the firetv black screen. When i type idme print nothing shows up. I have to install Markus-TWRP.zip and then it shows my stick info for that session. If I reboot and go back into twrp and idme command doesn't work again. I tried flashing 3, 5 and 6 partitions but still the same firetv black logo screen.

I will see if i can manually delete and copy back the partitions. If anyone has any ideas let me know. Thanks

https://xdaforums.com/t/firetv-1-bueller-prerooted-stock-images-5-2-7-3_r1.2882337/page-17

board_id: 2902001400130018

serial: G4N0VM0401

mac_addr: F0F

mac_sec: E8N1RV

bt_mac_addr: F0F0A

bt_mfg: 0

wifi_mfg: 0

product_name: 0

productid: 0

productid2: 0

bootmode: 1

postmode: 0

bootcount: 194

manufacturing: P4N1HG0800861SWW

unlock_code:

device_type_id: AKPGW064GI9HE

dev_flags: 0

fos_flags: 0

usr_flags: 0

KB:

4b 42 50 46 28 13 00 00 38 13

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

DKB:

30 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

mfg.locale: en-US
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Most likely that is because you forgot to mount system, i.e. the command only works in case system is mounted ;)

Btw, forget about idme, it looks good.

Forget about this too, the fireTV 1 bueller is based on a different SOC, won't work at all.

Maybe go with a clean ROM install, then wipe dalvik, cache, then 'format' data (or use the format userdata command in hacked fastboot).
[Fire TV Q&A, Help & Troubleshooting] 0815hoffi:
Markus-twrp.zip

......

ui_print(" Amazon Launcher Replacemnet ");

ui_print(" by 0815hoffi ");

ui_print("Mounting system partition...");

run_program("/sbin/mount", "/system");

run_program("/sbin/mount", "/data");

........
[Fire TV Q&A, Help & Troubleshooting] navin23:
Ok, I mounted the system and idme command works now. I flashed update-kindle-mantis-NS6268_user_2315_0003255372676.zip, then wipe dalvik, cache, and 'format' data in twrp. I'm getting the same firetv with black background. I also used an otg cable via laptop usb and then amazon cable with the wall adapter.

To get into the hacked fastboot do i need to do the rooting process again?
[Fire TV Q&A, Help & Troubleshooting] 0815hoffi:
No need to root again.

Just

adb reboot recovery

when the stick opens TWRP

adb shell reboot-amonet