Unbrick Fire TV Stick 4K. Help!

Pachacouti

Senior Member
Jul 8, 2020
100
8
18
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 ;)
 

Bertonumber1

Senior Member
May 17, 2020
633
160
53
Glasgow UK
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 ;)
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
 

Sus_i

Senior Member
Apr 9, 2013
978
356
83
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
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

most likely its had a micro update
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.
 

Pachacouti

Senior Member
Jul 8, 2020
100
8
18
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...
 

Pachacouti

Senior Member
Jul 8, 2020
100
8
18
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...
 

navin23

Member
Sep 29, 2018
37
4
8
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


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
 

Sus_i

Senior Member
Apr 9, 2013
978
356
83
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.
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.

I will see if i can manually delete and copy back the partitions. If anyone has any ideas let me know. Thanks
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).
 
  • Like
Reactions: 0815hoffi

0815hoffi

Senior Member
Dec 22, 2019
378
113
53
Munich
github.com
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");
........
 

navin23

Member
Sep 29, 2018
37
4
8
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?
 

navin23

Member
Sep 29, 2018
37
4
8
Ok, I was able to get into fastboot and do an erase but still stuck at the firetv screen.

adb shell reboot-amonet
fastboot devices
fastboot erase userdata
Then a message comes up to format ext4 then erasing and finish.

then i when into twrp
./fastboot.-step.sh
adb shell
reboot
 

0815hoffi

Senior Member
Dec 22, 2019
378
113
53
Munich
github.com
Try this.

Download FW / Magist again.



Boot TWRP with USB Cable ( never used OTG )

adb shell twrp wipe cache

adb shell twrp wipe data

adb shell twrp wipe dalvik

adb shell twrp wipe /system

adb push Magisk-v20.4.zip /sdcard/Magisk-v20.4.zip

adb push ftvs4k_6.2.7.7.zip /sdcard/ftvs4k_6.2.7.7.zip

adb shell twrp install /sdcard/ftvs4k_6.2.7.7.zip

adb shell twrp install /sdcard/Magisk-v20.4.zip

adb shell reboot
 

Sus_i

Senior Member
Apr 9, 2013
978
356
83
Apart from a wipe system, I wonder if a wipe of the vendor partition is necessary to solve this kind of issue/brick...

Since there isn't a wipe button for vendor in TWRP, running an adb shell mkfs command for /dev/block/mmcblk0p10 or /dev/block/platform/soc/11230000.mmc/by-name/vendor should do the trick. After that, a rom + magisk flash is mandatory.
 
Last edited:

navin23

Member
Sep 29, 2018
37
4
8
0815hoffi - I tried your instructions but still no go. I had to re-root the stick since i don't have adb connection since this stick was never setup. I have access to twrp with an otg cable.

Sus_i - I tried to issued the command adb shell mkfs or shell mkfs or mkfs with the valve below but getting not found. I also has tried parted and twrp wipe vendor. I had to mount vendor partition to see it when i do and df. I cat the the partition but alot of unreadable text shows up. Is there another format command i can use to format that partition? I tired in fastboot to issue that command same result.

/dev/block/mmcblk0p10
/dev/block/platform/soc/11230000.mmc/by-name/vendor


~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 646136 156 645980 0% /dev
tmpfs 646136 36 646100 0% /tmp
/dev/block/mmcblk0p13
5557564 682240 4569972 13% /data
/dev/block/mmcblk0p13
5557564 682240 4569972 13% /sdcard
/dev/block/mmcblk0p12
499656 664 462296 0% /cache
/dev/block/mmcblk0p11
1074000 949020 108596 90% /system
/dev/block/mmcblk0p10
144660 52752 88888 37% /vendor
~ #



 

Sus_i

Senior Member
Apr 9, 2013
978
356
83
Sus_i - I tried to issued the command adb shell mkfs or shell mkfs or mkfs with the valve below but getting not found.
Yes, the command isn't complete, I don't want that some users damage something.
You've to complete the command yourself (i.e. add the filesystem, probably ext4 I guess).
 

navin23

Member
Sep 29, 2018
37
4
8
It still comes back not found.

~ # mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor/Filesystem
/sbin/sh: mkfs: not found
~ # shell mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor/Filesystem
/sbin/sh: shell: not found
~ # shell mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor/Filesystem ext4
/sbin/sh: shell: not found
~ # mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor/Filesystem ext4
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor /Filesystem ext4
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor /Filesystem
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/mmcblk0p10
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/mmcblk0p10 /Filesystem
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/mmcblk0p10 /Filesystem /ext4
/sbin/sh: mkfs: not found


~ # df /dev/block/platform/soc/11230000.mmc/by-name/vendor
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p10
144660 52752 88888 37% /vendor
 

0815hoffi

Senior Member
Dec 22, 2019
378
113
53
Munich
github.com
It still comes back not found.

~ # mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor/Filesystem
/sbin/sh: mkfs: not found
~ # shell mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor/Filesystem
/sbin/sh: shell: not found
~ # shell mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor/Filesystem ext4
/sbin/sh: shell: not found
~ # mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor/Filesystem ext4
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor /Filesystem ext4
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/platform/soc/11230000.mmc/by-name/vendor /Filesystem
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/mmcblk0p10
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/mmcblk0p10 /Filesystem
/sbin/sh: mkfs: not found
~ # mkfs /dev/block/mmcblk0p10 /Filesystem /ext4
/sbin/sh: mkfs: not found


~ # df /dev/block/platform/soc/11230000.mmc/by-name/vendor
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p10
144660 52752 88888 37% /vendor
Example: https://android.stackexchange.com/a/220609
But if you have no experience. Don't do it!!!!!
 

navin23

Member
Sep 29, 2018
37
4
8
Thanks i will have a look at it. I decided to go back to fastboot and do a format. I was able to format the vendor partition via fastboot, but still stuck at the firetv screen. If you find anything new let me know. Thanks for all your help

~ # reboot-amonet
[[email protected] ~/Desktop/kamakiri-mantis-v1.2-linux/kamakiri]# fastboot devices
G4N0VM0401 fastboot
[[email protected] ~/Desktop/kamakiri-mantis-v1.2-linux/kamakiri]# fastboot format userdata
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 1444859 4k blocks and 361440 inodes
Filesystem UUID: 1ecd7e7d-24c3-4428-8300-f4d8390810e6
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (2940 KB) OKAY [ 0.172s]
Writing 'userdata' OKAY [ 0.246s]
Finished. Total time: 0.550s
[[email protected] ~/Desktop/kamakiri-mantis-v1.2-linux/kamakiri]# fastboot format vendor
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 38400 4k blocks and 38400 inodes
Filesystem UUID: e0a03c83-67d8-448d-b976-d5ca9a394f43
Superblock backups stored on blocks:
32768

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'vendor' (132 KB) OKAY [ 0.010s]
Writing 'vendor' OKAY [ 0.033s]
Finished. Total time: 0.072s
[[email protected] ~/Desktop/kamakiri-mantis-v1.2-linux/kamakiri]# fastboot format cache
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 131072 4k blocks and 32768 inodes
Filesystem UUID: a7d2b04f-652f-4d4c-8684-739ae86d5922
Superblock backups stored on blocks:
32768, 98304

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'cache' (324 KB) OKAY [ 0.020s]
Writing 'cache' OKAY [ 0.056s]
Finished. Total time: 0.107s
[[email protected] ~/Desktop/kamakiri-mantis-v1.2-linux/kamakiri]#
 
  • Like
Reactions: Sus_i