[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)

Search This thread

vanchienbmt

Member
Jul 7, 2012
24
2
All you need to know is written into the second post of this thread:
Unlocking with non-rooted Firmware
All you need to know is written into the second post of this thread:
Unlocking with non-rooted Firmware
sorry but i'm newbie, have you any videos for this method please
Thank you
 

atdog69

Member
Jan 28, 2022
13
0
You may use the boot-recovery.sh from the amonet zip in order to get into the 'new unlocked twrp'
Instead of the script you can also boot the 'old' twrp via bootmenu, then open adb shell and run the 'reboot recovery' command.

As soon as you boot the new twrp, 'format' data, then flash a new fireOS update-bin.zip + magisk.zip.
Hi Sus_i, thank you for your help. So when I use 'reboot recovery' (i can pick that in the adbLink gui from the Reboot-menu too) the box went to the white ama*zon logo but then with the ORANGE solid LED. After a few seconds it reboots to the (i think what you called) 'old TWRP'.

How and when do I have to use the 'boot-recovery.sh'? I have it extracted. To what directory must this go?
 

Sus_i

Senior Member
Apr 9, 2013
1,566
666
Hi Sus_i, thank you for your help. So when I use 'reboot recovery' (i can pick that in the adbLink gui from the Reboot-menu too) the box went to the white ama*zon logo but then with the ORANGE solid LED. After a few seconds it reboots to the (i think what you called) 'old TWRP'.

How and when do I have to use the 'boot-recovery.sh'? I have it extracted. To what directory must this go?
You need linux for the script, ubuntu or something like that... Extract it with ubuntu, open a terminal in the folder, type sudo su, then run ./boot-recovery.sh followed by connecting the usb a-a cable and the power supply of the box at the same time. The box should boot the new twrp. See the OP for details.

Anyways, if adb reboot recovery wont work for you, your unlock wasn't successful and something is messed up or damaged. So you may boot the old twrp, go to wipe, advanced wipe, format data. Then reboot to the old twrp, flash a prerooted rom from rbox. Then flash the amonet zip again. If you get some error messages, report back.
 

vanchienbmt

Member
Jul 7, 2012
24
2
solved, when i read 28 page this post i can do it.
Simple method, with newest firmware need open fire tv and do it with second post, run script on linux and connect DATA0 with GND and view on screen running script, all done

thanks @Sus_i very much.
 
Last edited:

atdog69

Member
Jan 28, 2022
13
0
You need linux for the script, ubuntu or something like that... Extract it with ubuntu, open a terminal in the folder, type sudo su, then run ./boot-recovery.sh followed by connecting the usb a-a cable and the power supply of the box at the same time. The box should boot the new twrp. See the OP for details.

Anyways, if adb reboot recovery wont work for you, your unlock wasn't successful and something is messed up or damaged. So you may boot the old twrp, go to wipe, advanced wipe, format data. Then reboot to the old twrp, flash a prerooted rom from rbox. Then flash the amonet zip again. If you get some error messages, report back.
Hi Sus_i, tried with Ubuntu (booted from USB-Stick) When running the command ./boot-recovery.sh, the following was shown:

[email protected]:/home/ubuntu/Downloads/amonet# ./boot-recovery.sh
Traceback (most recent call last):
File "handshake2.py", line 4, in <module>
from common import Device
File "/home/ubuntu/Downloads/amonet/modules/common.py", line 6, in <module>
import serial
ModuleNotFoundError: No module named 'serial'

As I said before I am totally unfamiliar with Linux, and can't find any sytem settings to activate the com port.

So I went back to Windows trying to do what you suggested with the old TWRP.
You wrote go to wipe, advanced wipe, format data.
I believe you mean "format data" next to the button "advanced wipe" right?
Or do you mean to wipe "data" (checking "data" and then Swipe)?
Anyway there are different errors every time. After trying to flash a prerooted rom I got this (but it had worked before!? As well as the amonet-sloane-v1.1. But when I reboot afterwards I'm going to the bootloop again. White ama*n followed by TWRP.....
On the screenshot it just hangs on "Copying" but it doesn't advance...

How do I know if it boots into the "new TWRP"? Does it look different to the old one? Does the white ama'*on logo show up first after booting there too?
 

Attachments

  • DSC_6342.JPG
    DSC_6342.JPG
    474.5 KB · Views: 17
Last edited:

Sus_i

Senior Member
Apr 9, 2013
1,566
666
How do I know if it boots into the "new TWRP"? Does it look different to the old one? Does the white ama'*on logo show up first after booting there too?
I guess there is something wrong with you eMMC storage, probably a faulty GPT.
You can try to flash a new GPT (grab the gpt-bin file from the gpt-fix zip in the OP) with adb shell if you like:
Code:
adb push gpt-sloane.bin /data/local/tmp/
adb shell
dd if=/data/local/tmp/gpt-sloane.bin of=/dev/block/mmcblk0 bs=512 count=34
exit
Then reboot into TWRP and try to format data.

If the box is still messed up (partition errors in twrp), your next option is to use the method from the second post, i.e. 'unbrick'
You need an usb a-a cable and to open your box for this...
Instead of the bootrom-step.sh you may use the gpt-fix.sh, in order to fix the GPT (you need to merge the gpt-fix zip into the amonet zip as a first step).
If you get some errors, copy/paste the terminal content. If you get into the new TWRP, make sure to format data...
 

atdog69

Member
Jan 28, 2022
13
0
No luck again...:

adb push gpt-sloane.bin /data/local/tmp/
gpt-sloane.bin: 1 file pushed, 0 skipped. 22.4 MB/s (17408 bytes in 0.001s)
adb: error: failed to copy 'gpt-sloane.bin' to '/data/local/tmp/gpt-sloane.bin': remote Read-only file system

Above from PC , the pic from box terminal...

I think there's no way but to open it...?



UPDATE:
Maybe I got a step forward? I get rid of that data folder i/o error as it seemed to be that 'system' did not mount automatically after booting. I did this after going into TWRP recovery:

installed amonet
(auto reboot)
mount system
installed prerooted rom 5.2.6.8
installed amonet (again) ALL OF THE ABOVE WITHOUT ANY ERRORS (besides the 'mount cache' (invalid argument)' error
(auto reboot)

adb reboot recovery (from adbLink menu (PC))
box reboots to white amaz*n logo with static ORANGE LED
seconds later goes to white amaz*on logo with pulsating white LED
followed by going to (I think old) TWRP
Then (if I let it 'Boot normally' and not go into 'Launch Recovery')
there will be the boot loop again with the white amaz*n logo (white LED) and TWRP screen rotatoring
 

Attachments

  • DSC_6348.JPG
    DSC_6348.JPG
    315.7 KB · Views: 6
Last edited:

Sus_i

Senior Member
Apr 9, 2013
1,566
666
Maybe I got a step forward?
Nope.

The eMMC chips on sloane are known to fail quite often...
You can do this:
then give Rortiz2 a PM, he can tell you if your eMMC is a cursed one.
 

atdog69

Member
Jan 28, 2022
13
0
Nope.

The eMMC chips on sloane are known to fail quite often...
You can do this:
then give Rortiz2 a PM, he can tell you if your eMMC is a cursed one.
Thank you Sus_i, pm'ed Rortiz2, if the eMMC is bad I don't need to go further...
 

atdog69

Member
Jan 28, 2022
13
0
Ok at last I did the shorting method described in #2.
There was an error message after 5.) and at he end reports a bad gpt...:

[2022-02-02 17:37:48.081670] Waiting for bootrom
[2022-02-02 17:38:05.259045] Found port = /dev/ttyACM0
[2022-02-02 17:38:05.261003] Handshake
[2022-02-02 17:38:05.264970] Disable watchdog
[2022-02-02 17:38:05.288951] Waiting for bootrom
[2022-02-02 17:38:13.451098] Found port = /dev/ttyACM0

* * * Remove the short and press Enter * * *


[2022-02-02 17:39:06.142558] Init crypto engine
[2022-02-02 17:39:06.375515] Disable caches
[2022-02-02 17:39:06.379861] Disable bootrom range checks
[2022-02-02 17:39:06.496834] Load payload from ../brom-payload/build/payload.bin = 0x4760 bytes
[2022-02-02 17:39:06.505065] Send payload
[2022-02-02 17:39:11.092831] Let's rock
[2022-02-02 17:39:11.097486] Wait for the payload to come online...
[2022-02-02 17:39:11.101744] all good
[2022-02-02 17:39:11.102095] Clear preloader header
[8 / 8]
[2022-02-02 17:39:12.496797] Check GPT
[2022-02-02 17:39:12.949994]
[2022-02-02 17:39:12.950431] Sector size (logical): 512 bytes
[2022-02-02 17:39:12.950863] Disk identifier (GUID): 57E14FDD-053E-48B1-B7F4-5B52586FE145
[2022-02-02 17:39:12.951094] Partition table holds up to 128 entries
[2022-02-02 17:39:12.951325] This partition table begins at sector 2 and ends at sector 33
[2022-02-02 17:39:12.951545] First usable sector is 34, last usable sector is 15269854
[2022-02-02 17:39:12.951760] Other partition table is at sector 15269887
[2022-02-02 17:39:12.952068]
[2022-02-02 17:39:12.952398] Number Start (sector) End (sector) Size Name
[2022-02-02 17:39:12.957634] 1 1024 1277 127.00 KiB PRO_INFO
[2022-02-02 17:39:12.958403] 2 2048 12287 5.00 MiB NVRAM
[2022-02-02 17:39:12.959158] 3 12288 22527 5.00 MiB TEE1
[2022-02-02 17:39:12.959888] 4 22528 32767 5.00 MiB TEE2
[2022-02-02 17:39:12.960604] 5 32768 34815 1024.00 KiB lk
[2022-02-02 17:39:12.961338] 6 34816 86015 25.00 MiB boot
[2022-02-02 17:39:12.961984] 7 86016 137215 25.00 MiB recovery
[2022-02-02 17:39:12.962243] 8 137216 139263 1024.00 KiB KB
[2022-02-02 17:39:12.962510] 9 139264 141311 1024.00 KiB DKB
[2022-02-02 17:39:12.962769] 10 141312 142335 512.00 KiB MISC
[2022-02-02 17:39:12.963025] 11 142336 158719 8.00 MiB LOGO
[2022-02-02 17:39:12.964743] 12 158720 182015 11.38 MiB EXPDB
[2022-02-02 17:39:12.964988] 13 182016 2659615 1.18 GiB system
[2022-02-02 17:39:12.965229] 14 2659616 3171615 250.00 MiB cache
[2022-02-02 17:39:12.965470] 15 3171616 15269854 5.77 GiB userdata
[2022-02-02 17:39:12.986369]
[2022-02-02 17:39:12.986613] Modify GPT
[2022-02-02 17:39:12.987084] Validate GPT
[2022-02-02 17:39:12.987414]
[2022-02-02 17:39:12.987500] Sector size (logical): 512 bytes
[2022-02-02 17:39:12.987596] Disk identifier (GUID): 57E14FDD-053E-48B1-B7F4-5B52586FE145
[2022-02-02 17:39:12.987672] Partition table holds up to 128 entries
[2022-02-02 17:39:12.987750] This partition table begins at sector 2 and ends at sector 33
[2022-02-02 17:39:12.987825] First usable sector is 34, last usable sector is 15269854
[2022-02-02 17:39:12.987898] Other partition table is at sector 15269887
[2022-02-02 17:39:12.987970]
[2022-02-02 17:39:12.988081] Number Start (sector) End (sector) Size Name
[2022-02-02 17:39:12.988346] 1 1024 1277 127.00 KiB PRO_INFO
[2022-02-02 17:39:12.988637] 2 2048 12287 5.00 MiB NVRAM
[2022-02-02 17:39:12.988876] 3 12288 22527 5.00 MiB TEE1
[2022-02-02 17:39:12.989122] 4 22528 32767 5.00 MiB TEE2
[2022-02-02 17:39:12.989367] 5 32768 34815 1024.00 KiB lk
[2022-02-02 17:39:12.989613] 6 34816 86015 25.00 MiB boot_x
[2022-02-02 17:39:12.989858] 7 86016 137215 25.00 MiB recovery_x
[2022-02-02 17:39:12.990096] 8 137216 139263 1024.00 KiB KB
[2022-02-02 17:39:12.990334] 9 139264 141311 1024.00 KiB DKB
[2022-02-02 17:39:12.990594] 10 141312 142335 512.00 KiB MISC
[2022-02-02 17:39:12.990846] 11 142336 158719 8.00 MiB LOGO
[2022-02-02 17:39:12.991094] 12 158720 182015 11.38 MiB EXPDB
[2022-02-02 17:39:12.991341] 13 182016 2659615 1.18 GiB system
[2022-02-02 17:39:12.991588] 14 2659616 3171615 250.00 MiB cache
[2022-02-02 17:39:12.991833] 15 3171616 3233055 30.00 MiB boot
[2022-02-02 17:39:12.992078] 16 3233056 3294495 30.00 MiB recovery
[2022-02-02 17:39:12.992316] 17 3294496 15269854 5.71 GiB userdata
[2022-02-02 17:39:13.008095]
[2022-02-02 17:39:13.008202] Flash new primary GPT
[34 / 34]
[2022-02-02 17:39:13.597928] Flash new backup GPT
[33 / 33]
[2022-02-02 17:39:14.307863]
[2022-02-02 17:39:14.308307] Sector size (logical): 512 bytes
[2022-02-02 17:39:14.308602] Disk identifier (GUID): 57E14FDD-053E-48B1-B7F4-5B52586FE145
[2022-02-02 17:39:14.308832] Partition table holds up to 128 entries
[2022-02-02 17:39:14.309063] This partition table begins at sector 2 and ends at sector 33
[2022-02-02 17:39:14.309280] First usable sector is 34, last usable sector is 15269854
[2022-02-02 17:39:14.309497] Other partition table is at sector 15269887
[2022-02-02 17:39:14.309708]
[2022-02-02 17:39:14.310033] Number Start (sector) End (sector) Size Name
[2022-02-02 17:39:14.310855] 1 1024 1277 127.00 KiB PRO_INFO
[2022-02-02 17:39:14.311569] 2 2048 12287 5.00 MiB NVRAM
[2022-02-02 17:39:14.312303] 3 12288 22527 5.00 MiB TEE1
[2022-02-02 17:39:14.313017] 4 22528 32767 5.00 MiB TEE2
[2022-02-02 17:39:14.313727] 5 32768 34815 1024.00 KiB lk
[2022-02-02 17:39:14.314437] 6 34816 86015 25.00 MiB boot
[2022-02-02 17:39:14.315183] 7 86016 137215 25.00 MiB recovery
[2022-02-02 17:39:14.315898] 8 137216 139263 1024.00 KiB KB
[2022-02-02 17:39:14.316610] 9 139264 141311 1024.00 KiB DKB
[2022-02-02 17:39:14.317316] 10 141312 142335 512.00 KiB MISC
[2022-02-02 17:39:14.318028] 11 142336 158719 8.00 MiB LOGO
[2022-02-02 17:39:14.318783] 12 158720 182015 11.38 MiB EXPDB
[2022-02-02 17:39:14.319039] 13 182016 2659615 1.18 GiB system
[2022-02-02 17:39:14.319484] 14 2659616 3171615 250.00 MiB cache
[2022-02-02 17:39:14.319734] 15 3171616 15269854 5.77 GiB userdata
[2022-02-02 17:39:14.340020]
Traceback (most recent call last):
File "main.py", line 146, in <module>
main()
File "main.py", line 84, in main
raise RuntimeError("bad gpt")
RuntimeError: bad gpt

After that I tried the next step: sudo ./fastboot-step.sh
but after "Press Enter to continue" I got an error message:

./fastboot-step.sh: Line 8: fastboot: Command not found

After booting the box went to the same procedere white ama*n logo and TWRP with all the red data, cache and system errors as before.

:-(((
 

Sus_i

Senior Member
Apr 9, 2013
1,566
666
Ok at last I did the shorting method described in #2.
There was an error message after 5.) and at he end reports a bad gpt...:

[2022-02-02 17:37:48.081670] Waiting for bootrom
[2022-02-02 17:38:05.259045] Found port = /dev/ttyACM0
[2022-02-02 17:38:05.261003] Handshake
[2022-02-02 17:38:05.264970] Disable watchdog
[2022-02-02 17:38:05.288951] Waiting for bootrom
[2022-02-02 17:38:13.451098] Found port = /dev/ttyACM0

* * * Remove the short and press Enter * * *


[2022-02-02 17:39:06.142558] Init crypto engine
[2022-02-02 17:39:06.375515] Disable caches
[2022-02-02 17:39:06.379861] Disable bootrom range checks
[2022-02-02 17:39:06.496834] Load payload from ../brom-payload/build/payload.bin = 0x4760 bytes
[2022-02-02 17:39:06.505065] Send payload
[2022-02-02 17:39:11.092831] Let's rock
[2022-02-02 17:39:11.097486] Wait for the payload to come online...
[2022-02-02 17:39:11.101744] all good
[2022-02-02 17:39:11.102095] Clear preloader header
[8 / 8]
[2022-02-02 17:39:12.496797] Check GPT
[2022-02-02 17:39:12.949994]
[2022-02-02 17:39:12.950431] Sector size (logical): 512 bytes
[2022-02-02 17:39:12.950863] Disk identifier (GUID): 57E14FDD-053E-48B1-B7F4-5B52586FE145
[2022-02-02 17:39:12.951094] Partition table holds up to 128 entries
[2022-02-02 17:39:12.951325] This partition table begins at sector 2 and ends at sector 33
[2022-02-02 17:39:12.951545] First usable sector is 34, last usable sector is 15269854
[2022-02-02 17:39:12.951760] Other partition table is at sector 15269887
[2022-02-02 17:39:12.952068]
[2022-02-02 17:39:12.952398] Number Start (sector) End (sector) Size Name
[2022-02-02 17:39:12.957634] 1 1024 1277 127.00 KiB PRO_INFO
[2022-02-02 17:39:12.958403] 2 2048 12287 5.00 MiB NVRAM
[2022-02-02 17:39:12.959158] 3 12288 22527 5.00 MiB TEE1
[2022-02-02 17:39:12.959888] 4 22528 32767 5.00 MiB TEE2
[2022-02-02 17:39:12.960604] 5 32768 34815 1024.00 KiB lk
[2022-02-02 17:39:12.961338] 6 34816 86015 25.00 MiB boot
[2022-02-02 17:39:12.961984] 7 86016 137215 25.00 MiB recovery
[2022-02-02 17:39:12.962243] 8 137216 139263 1024.00 KiB KB
[2022-02-02 17:39:12.962510] 9 139264 141311 1024.00 KiB DKB
[2022-02-02 17:39:12.962769] 10 141312 142335 512.00 KiB MISC
[2022-02-02 17:39:12.963025] 11 142336 158719 8.00 MiB LOGO
[2022-02-02 17:39:12.964743] 12 158720 182015 11.38 MiB EXPDB
[2022-02-02 17:39:12.964988] 13 182016 2659615 1.18 GiB system
[2022-02-02 17:39:12.965229] 14 2659616 3171615 250.00 MiB cache
[2022-02-02 17:39:12.965470] 15 3171616 15269854 5.77 GiB userdata
[2022-02-02 17:39:12.986369]
[2022-02-02 17:39:12.986613] Modify GPT
[2022-02-02 17:39:12.987084] Validate GPT
[2022-02-02 17:39:12.987414]
[2022-02-02 17:39:12.987500] Sector size (logical): 512 bytes
[2022-02-02 17:39:12.987596] Disk identifier (GUID): 57E14FDD-053E-48B1-B7F4-5B52586FE145
[2022-02-02 17:39:12.987672] Partition table holds up to 128 entries
[2022-02-02 17:39:12.987750] This partition table begins at sector 2 and ends at sector 33
[2022-02-02 17:39:12.987825] First usable sector is 34, last usable sector is 15269854
[2022-02-02 17:39:12.987898] Other partition table is at sector 15269887
[2022-02-02 17:39:12.987970]
[2022-02-02 17:39:12.988081] Number Start (sector) End (sector) Size Name
[2022-02-02 17:39:12.988346] 1 1024 1277 127.00 KiB PRO_INFO
[2022-02-02 17:39:12.988637] 2 2048 12287 5.00 MiB NVRAM
[2022-02-02 17:39:12.988876] 3 12288 22527 5.00 MiB TEE1
[2022-02-02 17:39:12.989122] 4 22528 32767 5.00 MiB TEE2
[2022-02-02 17:39:12.989367] 5 32768 34815 1024.00 KiB lk
[2022-02-02 17:39:12.989613] 6 34816 86015 25.00 MiB boot_x
[2022-02-02 17:39:12.989858] 7 86016 137215 25.00 MiB recovery_x
[2022-02-02 17:39:12.990096] 8 137216 139263 1024.00 KiB KB
[2022-02-02 17:39:12.990334] 9 139264 141311 1024.00 KiB DKB
[2022-02-02 17:39:12.990594] 10 141312 142335 512.00 KiB MISC
[2022-02-02 17:39:12.990846] 11 142336 158719 8.00 MiB LOGO
[2022-02-02 17:39:12.991094] 12 158720 182015 11.38 MiB EXPDB
[2022-02-02 17:39:12.991341] 13 182016 2659615 1.18 GiB system
[2022-02-02 17:39:12.991588] 14 2659616 3171615 250.00 MiB cache
[2022-02-02 17:39:12.991833] 15 3171616 3233055 30.00 MiB boot
[2022-02-02 17:39:12.992078] 16 3233056 3294495 30.00 MiB recovery
[2022-02-02 17:39:12.992316] 17 3294496 15269854 5.71 GiB userdata
[2022-02-02 17:39:13.008095]
[2022-02-02 17:39:13.008202] Flash new primary GPT
[34 / 34]
[2022-02-02 17:39:13.597928] Flash new backup GPT
[33 / 33]
[2022-02-02 17:39:14.307863]
[2022-02-02 17:39:14.308307] Sector size (logical): 512 bytes
[2022-02-02 17:39:14.308602] Disk identifier (GUID): 57E14FDD-053E-48B1-B7F4-5B52586FE145
[2022-02-02 17:39:14.308832] Partition table holds up to 128 entries
[2022-02-02 17:39:14.309063] This partition table begins at sector 2 and ends at sector 33
[2022-02-02 17:39:14.309280] First usable sector is 34, last usable sector is 15269854
[2022-02-02 17:39:14.309497] Other partition table is at sector 15269887
[2022-02-02 17:39:14.309708]
[2022-02-02 17:39:14.310033] Number Start (sector) End (sector) Size Name
[2022-02-02 17:39:14.310855] 1 1024 1277 127.00 KiB PRO_INFO
[2022-02-02 17:39:14.311569] 2 2048 12287 5.00 MiB NVRAM
[2022-02-02 17:39:14.312303] 3 12288 22527 5.00 MiB TEE1
[2022-02-02 17:39:14.313017] 4 22528 32767 5.00 MiB TEE2
[2022-02-02 17:39:14.313727] 5 32768 34815 1024.00 KiB lk
[2022-02-02 17:39:14.314437] 6 34816 86015 25.00 MiB boot
[2022-02-02 17:39:14.315183] 7 86016 137215 25.00 MiB recovery
[2022-02-02 17:39:14.315898] 8 137216 139263 1024.00 KiB KB
[2022-02-02 17:39:14.316610] 9 139264 141311 1024.00 KiB DKB
[2022-02-02 17:39:14.317316] 10 141312 142335 512.00 KiB MISC
[2022-02-02 17:39:14.318028] 11 142336 158719 8.00 MiB LOGO
[2022-02-02 17:39:14.318783] 12 158720 182015 11.38 MiB EXPDB
[2022-02-02 17:39:14.319039] 13 182016 2659615 1.18 GiB system
[2022-02-02 17:39:14.319484] 14 2659616 3171615 250.00 MiB cache
[2022-02-02 17:39:14.319734] 15 3171616 15269854 5.77 GiB userdata
[2022-02-02 17:39:14.340020]
Traceback (most recent call last):
File "main.py", line 146, in <module>
main()
File "main.py", line 84, in main
raise RuntimeError("bad gpt")
RuntimeError: bad gpt

After that I tried the next step: sudo ./fastboot-step.sh
but after "Press Enter to continue" I got an error message:

./fastboot-step.sh: Line 8: fastboot: Command not found

After booting the box went to the same procedere white ama*n logo and TWRP with all the red data, cache and system errors as before.

:-(((

Try the bootrom-step, until you get a message about rebooting into fastboot...
 

atdog69

Member
Jan 28, 2022
13
0
Try the bootrom-step, until you get a message about rebooting into fastboot...
Well I did that already? It's step No. 2 (at post #2) ?

2. Start the script:
Code:
sudo ./bootrom-step.sh

It should now say Waiting for bootrom.

Maybe you meant fastboot-step?

I now find out the problem above with file not found. I had to install fastboot first.
Now I can run the fastboot.sh script. But then after "Press Enter to continue"
all I'll get is < waiting for any device >

I think it's about that gpt error I got with the shorting method?

Traceback (most recent call last):
File "main.py", line 146, in <module>
main()
File "main.py", line 84, in main
raise RuntimeError("bad gpt")
RuntimeError: bad gpt


Is there anything to repair that? I already flashed the gpt-fix (via TWRP) but it seems not to have done anything...
 
Last edited:

atdog69

Member
Jan 28, 2022
13
0
So I can ignore that bad gpt message as it could vanish by trying?

I have an old boot.img, from 1st rooting my device. Could that be helpful?

I think I have that problem with the bootloop.
When I use "lsusb" it always showed up in Preloader mode, can't get rid of that...
 
Last edited:

Sus_i

Senior Member
Apr 9, 2013
1,566
666
So I can ignore that bad gpt message as it could vanish by trying?
Yeah, it could, i.e. it will be messed up if the script errors out in between...
I have an old boot.img, from 1st rooting my device. Could that be helpful?
No...
When I use "lsusb" it always showed up in Preloader mode, can't get rid of that...
Preloader is the first boot stage just after bootrom, so you can ignore that.
Try the bootrom-script again...
 

Rortiz2

Senior Member
Mar 1, 2018
2,405
1,789
Barcelona
Ok at last I did the shorting method described in #2.
There was an error message after 5.) and at he end reports a bad gpt...:

[2022-02-02 17:37:48.081670] Waiting for bootrom
[2022-02-02 17:38:05.259045] Found port = /dev/ttyACM0
[2022-02-02 17:38:05.261003] Handshake
[2022-02-02 17:38:05.264970] Disable watchdog
[2022-02-02 17:38:05.288951] Waiting for bootrom
[2022-02-02 17:38:13.451098] Found port = /dev/ttyACM0

* * * Remove the short and press Enter * * *


[2022-02-02 17:39:06.142558] Init crypto engine
[2022-02-02 17:39:06.375515] Disable caches
[2022-02-02 17:39:06.379861] Disable bootrom range checks
[2022-02-02 17:39:06.496834] Load payload from ../brom-payload/build/payload.bin = 0x4760 bytes
[2022-02-02 17:39:06.505065] Send payload
[2022-02-02 17:39:11.092831] Let's rock
[2022-02-02 17:39:11.097486] Wait for the payload to come online...
[2022-02-02 17:39:11.101744] all good
[2022-02-02 17:39:11.102095] Clear preloader header
[8 / 8]
[2022-02-02 17:39:12.496797] Check GPT
[2022-02-02 17:39:12.949994]
[2022-02-02 17:39:12.950431] Sector size (logical): 512 bytes
[2022-02-02 17:39:12.950863] Disk identifier (GUID): 57E14FDD-053E-48B1-B7F4-5B52586FE145
[2022-02-02 17:39:12.951094] Partition table holds up to 128 entries
[2022-02-02 17:39:12.951325] This partition table begins at sector 2 and ends at sector 33
[2022-02-02 17:39:12.951545] First usable sector is 34, last usable sector is 15269854
[2022-02-02 17:39:12.951760] Other partition table is at sector 15269887
[2022-02-02 17:39:12.952068]
[2022-02-02 17:39:12.952398] Number Start (sector) End (sector) Size Name
[2022-02-02 17:39:12.957634] 1 1024 1277 127.00 KiB PRO_INFO
[2022-02-02 17:39:12.958403] 2 2048 12287 5.00 MiB NVRAM
[2022-02-02 17:39:12.959158] 3 12288 22527 5.00 MiB TEE1
[2022-02-02 17:39:12.959888] 4 22528 32767 5.00 MiB TEE2
[2022-02-02 17:39:12.960604] 5 32768 34815 1024.00 KiB lk
[2022-02-02 17:39:12.961338] 6 34816 86015 25.00 MiB boot
[2022-02-02 17:39:12.961984] 7 86016 137215 25.00 MiB recovery
[2022-02-02 17:39:12.962243] 8 137216 139263 1024.00 KiB KB
[2022-02-02 17:39:12.962510] 9 139264 141311 1024.00 KiB DKB
[2022-02-02 17:39:12.962769] 10 141312 142335 512.00 KiB MISC
[2022-02-02 17:39:12.963025] 11 142336 158719 8.00 MiB LOGO
[2022-02-02 17:39:12.964743] 12 158720 182015 11.38 MiB EXPDB
[2022-02-02 17:39:12.964988] 13 182016 2659615 1.18 GiB system
[2022-02-02 17:39:12.965229] 14 2659616 3171615 250.00 MiB cache
[2022-02-02 17:39:12.965470] 15 3171616 15269854 5.77 GiB userdata
[2022-02-02 17:39:12.986369]
[2022-02-02 17:39:12.986613] Modify GPT
[2022-02-02 17:39:12.987084] Validate GPT
[2022-02-02 17:39:12.987414]
[2022-02-02 17:39:12.987500] Sector size (logical): 512 bytes
[2022-02-02 17:39:12.987596] Disk identifier (GUID): 57E14FDD-053E-48B1-B7F4-5B52586FE145
[2022-02-02 17:39:12.987672] Partition table holds up to 128 entries
[2022-02-02 17:39:12.987750] This partition table begins at sector 2 and ends at sector 33
[2022-02-02 17:39:12.987825] First usable sector is 34, last usable sector is 15269854
[2022-02-02 17:39:12.987898] Other partition table is at sector 15269887
[2022-02-02 17:39:12.987970]
[2022-02-02 17:39:12.988081] Number Start (sector) End (sector) Size Name
[2022-02-02 17:39:12.988346] 1 1024 1277 127.00 KiB PRO_INFO
[2022-02-02 17:39:12.988637] 2 2048 12287 5.00 MiB NVRAM
[2022-02-02 17:39:12.988876] 3 12288 22527 5.00 MiB TEE1
[2022-02-02 17:39:12.989122] 4 22528 32767 5.00 MiB TEE2
[2022-02-02 17:39:12.989367] 5 32768 34815 1024.00 KiB lk
[2022-02-02 17:39:12.989613] 6 34816 86015 25.00 MiB boot_x
[2022-02-02 17:39:12.989858] 7 86016 137215 25.00 MiB recovery_x
[2022-02-02 17:39:12.990096] 8 137216 139263 1024.00 KiB KB
[2022-02-02 17:39:12.990334] 9 139264 141311 1024.00 KiB DKB
[2022-02-02 17:39:12.990594] 10 141312 142335 512.00 KiB MISC
[2022-02-02 17:39:12.990846] 11 142336 158719 8.00 MiB LOGO
[2022-02-02 17:39:12.991094] 12 158720 182015 11.38 MiB EXPDB
[2022-02-02 17:39:12.991341] 13 182016 2659615 1.18 GiB system
[2022-02-02 17:39:12.991588] 14 2659616 3171615 250.00 MiB cache
[2022-02-02 17:39:12.991833] 15 3171616 3233055 30.00 MiB boot
[2022-02-02 17:39:12.992078] 16 3233056 3294495 30.00 MiB recovery
[2022-02-02 17:39:12.992316] 17 3294496 15269854 5.71 GiB userdata
[2022-02-02 17:39:13.008095]
[2022-02-02 17:39:13.008202] Flash new primary GPT
[34 / 34]
[2022-02-02 17:39:13.597928] Flash new backup GPT
[33 / 33]
[2022-02-02 17:39:14.307863]
[2022-02-02 17:39:14.308307] Sector size (logical): 512 bytes
[2022-02-02 17:39:14.308602] Disk identifier (GUID): 57E14FDD-053E-48B1-B7F4-5B52586FE145
[2022-02-02 17:39:14.308832] Partition table holds up to 128 entries
[2022-02-02 17:39:14.309063] This partition table begins at sector 2 and ends at sector 33
[2022-02-02 17:39:14.309280] First usable sector is 34, last usable sector is 15269854
[2022-02-02 17:39:14.309497] Other partition table is at sector 15269887
[2022-02-02 17:39:14.309708]
[2022-02-02 17:39:14.310033] Number Start (sector) End (sector) Size Name
[2022-02-02 17:39:14.310855] 1 1024 1277 127.00 KiB PRO_INFO
[2022-02-02 17:39:14.311569] 2 2048 12287 5.00 MiB NVRAM
[2022-02-02 17:39:14.312303] 3 12288 22527 5.00 MiB TEE1
[2022-02-02 17:39:14.313017] 4 22528 32767 5.00 MiB TEE2
[2022-02-02 17:39:14.313727] 5 32768 34815 1024.00 KiB lk
[2022-02-02 17:39:14.314437] 6 34816 86015 25.00 MiB boot
[2022-02-02 17:39:14.315183] 7 86016 137215 25.00 MiB recovery
[2022-02-02 17:39:14.315898] 8 137216 139263 1024.00 KiB KB
[2022-02-02 17:39:14.316610] 9 139264 141311 1024.00 KiB DKB
[2022-02-02 17:39:14.317316] 10 141312 142335 512.00 KiB MISC
[2022-02-02 17:39:14.318028] 11 142336 158719 8.00 MiB LOGO
[2022-02-02 17:39:14.318783] 12 158720 182015 11.38 MiB EXPDB
[2022-02-02 17:39:14.319039] 13 182016 2659615 1.18 GiB system
[2022-02-02 17:39:14.319484] 14 2659616 3171615 250.00 MiB cache
[2022-02-02 17:39:14.319734] 15 3171616 15269854 5.77 GiB userdata
[2022-02-02 17:39:14.340020]
Traceback (most recent call last):
File "main.py", line 146, in <module>
main()
File "main.py", line 84, in main
raise RuntimeError("bad gpt")
RuntimeError: bad gpt

After that I tried the next step: sudo ./fastboot-step.sh
but after "Press Enter to continue" I got an error message:

./fastboot-step.sh: Line 8: fastboot: Command not found

After booting the box went to the same procedere white ama*n logo and TWRP with all the red data, cache and system errors as before.

:-(((
Your box is completely dead. The script erased the Preloader (header) and you said it still boots, so the eMMC went into read-only mode.
 

atdog69

Member
Jan 28, 2022
13
0
Your box is completely dead. The script erased the Preloader (header) and you said it still boots, so the eMMC went into read-only mode.

Hm, ok. So " your box is completely dead" means there's no way to fix it? Yes I got some errors about read-only too.
But the eMMC looks intact but in read-only mode?
Sorry for the questions I really can't follow as I am no specialist in linux/android stuff.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Using the short method, make sure you are making good contact with the correct spot on the chip. With the short in place, and everything else connected to the unit and ready to go, power the unit (plug it in) and wait a few seconds. If the unit's power light comes on (lights up) then you do not have a good short. Unplug the unit and readjust the short contact and power up again. Keep doing this trial and error until you can power up the unit and the power light does not come on. Next, run your script on the computer such that it says "waiting for boot rom" and then, plug your usb to usb into your computer (it should already be plugged into your sloan device). Your computer screen should react with "remove short", at which poiint you remove the short. The script should run from there. Your problem may very well be more involved than this, but this is what i would try first. Remeber, when you first power up the unit, the power light should not come on if you have a good short on the correct spot of the chip.

    Once you are in TWRP, Install amonet 1.01. After you install amonet 1.01, be sure you FORMAT (not wipe) the data. Then, click on Install, and install the sloane version of your choice. Finally, install Magist v23 if you want adminstrative privleges. Reboot system and you should be good to go. Good luck.

    Hope this helps.
    1
    My device took an update this p.m. Now has OS 5.2.8.8 (676742620). Had to adb reboot recovery and re-install Magist v23. Everything looks good, except now I have to de-bloat again. I guess practice makes perfect.
    1
    My device took an update this p.m. Now has OS 5.2.8.8 (676742620). Had to adb reboot recovery and re-install Magist v23. Everything looks good, except now I have to de-bloat again. I guess practice makes perfect.
    Also, I was finally able to capture the update url using logcat. After piecing things together, this is what I came up with if anyone wants to try it.

  • 10
    Read this whole guide before starting.

    This is for the 2nd gen Fire TV (sloane)

    Current relase: amonet-sloane-v1.1

    NOTE: This process does not require you to open your device if you're already rooted or you have TWRP.
    NOTE: If something goes horribly wrong and your device gets bricked, you'll have to open it and unbrick it through bootrom (post 2).
    NOTE: This process will modify the partition-table (GPT) of your device.

    NOTE: Your device will be reset to factory defaults (including internal storage) during this process.
    NOTE: Flashing prerooted ROM will disable unlocked TWRP. It's recommended to flash an stock update.bin
    until that gets sorted out.

    To update to the current release if you are already unlocked, just flash the zip in TWRP.

    What you need:
    • A Linux installation or live-system
    • A a-a cable
    1. Download the attached zip-file "amonet-sloane-v1.1zip".
    2. Copy the zip-file to the internal storage of the box or copy the zip-file to an external SD/USB storage and connect it to the box.
    3. Reboot the FireTV to rbox's TWRP recovery and flash the zip-file.

    NOTE: If you are on firmware 5.2.7.3 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
    If you chose the brick option, you need to continue with bootrom-step-minimal.sh:




    NOTE: Please refer to the #2 post on how to prepare your environment before proceeding.
    NOTE: If you use this method to unlock the device you don't need to flash the unlock-zip once you're in TWRP.

    Once the zip-file finished flashing, disconnect the device and run:
    Code:
    sudo ./bootrom-step-minimal.sh
    Then plug the device back in.

    The device will reboot to hacked fastboot mode (Static Amazon White Logo + white blinking LED).
    Then run:
    Code:
    sudo ./fastboot-step.sh


    After that, the device will reboot to unlocked TWRP. Then go to Wipe > Format Data and type "YES".
    You can now install Magisk from there.

    Important information

    NOTE: This has nothing to do with the unlock process.

    You have 10 seconds to force TWRP to keep ADB over USB active by using
    Code:
    adb wait-for-recovery && adb shell setprop twrp.usb.mode 0

    In the new partitioning scheme your boot/recovery-images will be in boot_x/recovery_x respectively, while boot/recovery will hold the exploit.
    TWRP takes care of remapping these for you, so installing zips/images from TWRP will work as expected.

    Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.) (If you do anyway, make sure you flash them to boot_x/recovery_x)

    Should you accidentally overwrite the wrong boot, but your TWRP is still working, rebooting into TWRP will fix that automatically.

    TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).

    For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).

    It is still advised to disable OTA.

    Very special thanks to @k4y0z and @t0x1cSH for making all this possible by porting the LK exploit to sloane and implementing the RPMB-key derivation for sloane.
    Special thanks also to @xyz` for making all this possible and releasing the original amonet exploit for karnak.
    Special thanks also to @retyre for porting the bootrom-exploit to mt8173.
    Special thanks also to @Sus_i and @DanielF50 for testing.
    Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.
    5
    I would advise you pull your ROM's boot.img, patch it with MagiskManager & then flash this manually via hacked fastboot, otherwise it won't work & you'll probably brick your device again.

    Don't worry, magisk flashing in TWRP works (now). ;)
    5
    When I tried to install Magisk in TWRP it failed. It isn't that big of a problem as I am running one of Rbox's pre rooted ROMs but just thought it was odd.

    It was Magisk 19.5? I believe, can't remember off the top of my head.
    You are probably using rbox-twrp instead unlocked twrp.
    I don't think there's any reason to use an old Magisk release either.

    Unfortunately the update overwrote the prerooted version with a standard unrooted version and you would have to go through the whole process again to unlock, but you would have to use the latest prerooted version once it is available so there no updates to mess it up. and then block future updates after that. I decided to just wait for the newest prerooted version so I don't have to go through the process again.

    The good thing is that it is a fully functional unit for reasonably cheap.
    Can you please stop giving nonsense advice?
    1. There is no reason to redo the unlock.
    2. We currently DO NOT recommend using the prerooted ROM together with the unlock.
    5
    In case someone needs some newer 'full OTA update' packages of the stock rom, only for sloane:

    Fire OS 5.2.7.3 (652614020).

    Fire OS 5.2.7.4 (656638420).

    Fire OS 5.2.7.6 (659654620).

    5.2.7.6 is the latest OS (as of today).
    Don't forget to rename the file, i.e. .bin to .zip.
    5
    According to Amazon the latest software update is Amazon Fire TV (2nd Generation): Fire OS 5.2.7.8 (664657320) not 5.2.8.8.
    but I haven't found a link for it yet.

    Me too. Where to find link for full stock Fire OS 5.2.7.8 (664657320)? I'd like to keep my practice demo up to date.

    Fire OS 5.2.7.8 (664657620) for sloane:


    md5: 087cef3f082b0017231e8b938feaeec7