Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RuntimeError in load_payload #2

Open
MommyKnowsBest2020 opened this issue Jul 16, 2020 · 1 comment
Open

RuntimeError in load_payload #2

MommyKnowsBest2020 opened this issue Jul 16, 2020 · 1 comment

Comments

@MommyKnowsBest2020
Copy link

MommyKnowsBest2020 commented Jul 16, 2020

Hello,

I always get the following runtime error:

root@sysresccd ~/Downloads/kamakiri]# ./bootrom-step.sh
[2020-07-16 22:04:48.877144] Waiting for bootrom
[2020-07-16 22:05:41.301124] Found port = /dev/ttyACM0
[2020-07-16 22:05:41.315745] Handshake
[2020-07-16 22:05:41.327922] Disable watchdog

      • If you have a short attached, remove it now * * *
      • Press Enter to continue * * *

[2020-07-16 22:09:04.490157] Load payload from ../brom-payload/stage1/stage1.bin = 0x27C bytes
[2020-07-16 22:09:04.515385] Let's rock
[2020-07-16 22:09:04.517902] Waiting for stage 1 to come online...
Traceback (most recent call last):
File "main.py", line 119, in
main(dev)
File "main.py", line 24, in main
load_payload(dev)
File "/root/Downloads/kamakiri/modules/load_payload.py", line 85, in load_payload
raise RuntimeError("received {} instead of expected pattern".format(data))
RuntimeError: received b'' instead of expected pattern

What I'm doing wrong?

I'm using fireiso v1.0.0 and trying to root my fire tv stick 4k from Amazon. I've booted the iso in a VirtualBox environment, if it is important. What can I do?

@qwertyinme
Copy link

unless it's a hypervisor level VM, it might not work with your host OS.

Have you tried to boot the ISO natively? as in - burn .ISO to CD/DVD/USB and boot to it via the BIOS/UEFI menu, otherwise that looks to be a problem with the actual payload, if it'd be python v2/v3 conflict it wouldn't go as far as it did

this might help anyone else having similar problems in the current year of our Lord 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants