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

[vanchienbmt]

All you need to know is written into the second post of this thread:
Unlocking with non-rooted Firmware

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

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...

forum.xda-developers.com

All you need to know is written into the second post of this thread:
Unlocking with non-rooted Firmware

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

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...

forum.xda-developers.com

sorry but i'm newbie, have you any videos for this method please
Thank you

 

[Sus_i]

sorry but i'm newbie, have you any videos for this method please
Thank you

No, sry, there isn't a video at all, you need to read the guide from the second post

 

[vanchienbmt]

No, sry, there isn't a video at all, you need to read the guide from the second post

but my fire tv is normal with this method i need open my device ?

 

[atdog69]

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]

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.

 

[Sus_i]

but my fire tv is normal with this method i need open my device ?

Ofcourse, you need to open the box up and you need an usb a-a cable...

 

[vanchienbmt]

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.

 

[atdog69]

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?

 

[Sus_i]

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:

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]

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

 

[Sus_i]

Maybe I got a step forward?

Nope.

The eMMC chips on sloane are known to fail quite often...
You can do this:

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

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...

forum.xda-developers.com

then give Rortiz2 a PM, he can tell you if your eMMC is a cursed one.

 

[atdog69]

Nope.

The eMMC chips on sloane are known to fail quite often...
You can do this:

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

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...

forum.xda-developers.com

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]

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]

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]

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...

 

[Sus_i]

Well I did that already? It's step No. 2 (at post #2) ?

The bootrom-step script needs to run up to the end, otherwise the unlock isn't in place...
Try again and again until you reach the reboot fastboot message...

 

[atdog69]

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...

 

[Sus_i]

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]

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]

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.