yashsingh1/xdaforums huggingface dataset:
[Fire TV Original Android Development] :
The device detected was a device not the device I am trying to unlock so the mode that it is in is irrelevant.

The device I am trying to unlock doesn't show up when I do lsusb but is recognized when shorted as the output below shows:

sudo] password for jim:

[2021-02-11 15:19:36.789857] Waiting for bootrom

[2021-02-11 15:20:55.590423] Found port = /dev/ttyACM0

[2021-02-11 15:20:55.593393] Handshake

[2021-02-11 15:20:55.594110] Disable watchdog

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

[2021-02-11 15:21:18.609137] Init crypto engine

Traceback (most recent call last):

File "/usr/lib/python3.9/site-packages/serial/serialposix.py", line 621, in write

n = os.write(self.fd, d)

OSError: [Errno 5] Input/output error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/main.py", line 143, in <module>

main()

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/main.py", line 28, in main

load_payload(dev, "../brom-payload/build/payload.bin")

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/load_payload.py", line 112, in load_payload

init(dev)

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/load_payload.py", line 9, in init

dev.write32(CRYPTO_BASE + 0x0C0C, 0)

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/common.py", line 157, in write32

self.dev.write(b'\xd4')

File "/usr/lib/python3.9/site-packages/serial/serialposix.py", line 655, in write

raise SerialException('write failed: {}'.format(e))

serial.serialutil.SerialException: write failed: [Errno 5] Input/output error

[jim@Xeon amonet]$ lsusb

Bus 002 Device 005: ID 043d:00bd Lexmark International, Inc. Printing Support

Bus 002 Device 004: ID 0a5f:0009 Zebra LP2844 Printer

Bus 002 Device 003: ID 046d:0809 Logitech, Inc. Webcam Pro 9000

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 004: ID 0461:4dfb Primax Electronics, Ltd USB Optical Mouse

Bus 001 Device 007: ID 04f2:0981 Chicony Electronics Co., Ltd Wireless Device

Bus 001 Device 006: ID 04b8:0812 Seiko Epson Corp. MFP Composite Device

Bus 001 Device 005: ID 0a05:7211 Unknown Manufacturer hub

Bus 001 Device 003: ID 0a05:7211 Unknown Manufacturer hub

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Other Fire TV 2's show up when I do lsusb, but not the one that I am trying to reconfigure even though I can short it and it is recognized and the script now fails.
[Fire TV Original Android Development] Seattleweather:
no prompts at all after i plug in A-A USB. still showing waiting for bootrom.
[Fire TV Original Android Development] Seattleweather:
same error message like mine: serial.serialutil.SerialException: write failed: [Errno 5] Input/output error
[Fire TV Original Android Development] Bertonumber1:
Try the above method. It is absolutely relevant what mode your device is in as k4y0z stated.

With the device and no short

So you run

sudo ./bootrom-step.sh

Plug in the DC power and wait 40 seconds

Then connect the USB a to a cable

Sometimes you may have to hit enter again sometimes you don't.

This gives the device a chance to go through the process before seeing the bootrom step.

Edit : this method has worked on many devices I've flashed with amonet. It is key to keep on trying many times. Sometimes leaving him an hour and go back to him is success

Regards
[Fire TV Original Android Development] :
My experience is that I was able to run the script, but was not able to get into fast boot after it rebooted. Now I can do lsusb when the device is powered on the USB cable attached, but it doesn't show up in the listing.

I can however short the device and the script will run, but eventually fails even with the update.
[Fire TV Original Android Development] k4y0z:
I am assuming you are @com-ments, if the device is detected by the script, it will also show up in lsusb or dmesg it may just not be visible for long.

You can try running something like this in a separate window to see what it is detected as:

watch -n 0.1 "lsusb|grep -i 0e8d"

You also previously said, the bootrom-step was completed without errors, does the device show the amazon logo when connected to a display?

Are your other devices detected by fastboot, when they're booted to fastboot?
[Fire TV Original Android Development] k4y0z:
No, it's the other way around, if preloader is gone (or device is shorted, or missing resistors) it will show up as MTK phone, if preloader is still there (or not shorted properly) it will show up as MTK preloader
[Fire TV Original Android Development] Bertonumber1:
Ah okay dude apologies I stand corrected. Anyways I've used this method a few times when struggling to connect the device to the script and it works a treat. (y)
[Fire TV Original Android Development] :
Thanks for the suggestion, but so far, I haven't had any luck. I am assuming that I short after powering on and waiting 40 seconds to plugin the USB cable. I am also using the newer version of the software 1.01.
[Fire TV Original Android Development] Bertonumber1:
The method I described works when you get serial protocol mismatch and i/o errors.

Just unpower Sloane and run the script with the USB cable disconnected. Then power on sloane and leave him for 40secs then plug in USB.

It usually works
[Fire TV Original Android Development] :
It

Oh ok... I tried that too, but the script will not run unless I short on my device.
[Fire TV Original Android Development] :
I had to create this account because the "-" in comm-ents seems to cause a lot of problems logging in and saving the password I just created. I didn't have any problems with the account name until after the forum software was upgraded.

I have been using Linux and flashing rooting for a long time and the other Fire TV units were rooted over a year ago when it could be done via software method on older versions of the OS. As my computer didn't recognize the Fire TV demo unit, I am pretty sure fastboot wouldn't either, but just to be sure I started my phone in fast boot and made sure it was listed using fastboot devices which it did.

fastboot devices

ZY227SCDGK fastboot
[Fire TV Original Android Development] :
Just curios if your device was one of the Demo units purchased off of Ebay or a regular Fire TV 2?
[Fire TV Original Android Development] Seattleweather:
No, it's not. it's firmware 5.2.7.4
[Fire TV Original Android Development] k4y0z:
You didn't address half of my questions.

And again the device is obviously being detected by the script.

Also it was already established, that the demo units are no different in regards to unlocking.
[Fire TV Original Android Development] :
How about you just f**k off and just go bother someone one else. Your responses are mostly unhelpful and a waste of my time. I am only stating my experience trying flash the demo unit and don't need any suggestions from you.
[Fire TV Original Android Development] k4y0z:
Great then I won't be wasting my time anymore trying to be helpfull. :rolleyes:
[Fire TV Original Android Development] Seattleweather:
same here
[Fire TV Original Android Development] Bertonumber1:
How about you show some respect to the ****in developer. Too many people on this forum take take take without giving nothing back in return. What way is that to speak to anyone let alone one of the people who put their time into the exploit you are failing to use right now , if it weren't for him and another few devs you wouldn't be sitting with the unlock script (failing, might I add) you're using to unlock the Sloane.

I suggest you educate yourself in the process properly as you've probably fkced it somewhere along the way or not followed the OP properly.

You state you got a device from eBay? A demo mode one?

Have you even considered you've been skanked with a dodgy device, hence why it's been flogged in the first place???? Pmsl

Funny how the unlock works on almost every other person's device.
[Fire TV Original Android Development] Bertonumber1:
Hey, can you show your output mate
[Fire TV Original Android Development] :
LOL. Respect is not just given it is earned. There is also a huge difference between respect and kissing someone's ass for no reason. I suggest you educate yourself in understanding what proper etiquette actually is or the reason I responded they way I did because you certainly don't know the context.

You also seem to not know what a demo Fire TV device is or read any information about them or that the process is far from foolproof and I am not the only one who is experiencing issues.. Are you the least bit knowledgeable of a bug report is? I am actually reporting my experience which may help developers to improve the performance of the software to perform the task it was intended to do. I don't need people suggesting that what I am reporting is not really real.

As unfortunate as it is, not everyone has been able to unlock their device as you suggest.
[Fire TV Original Android Development] Seattleweather:
Without shorting, and power on first, plug in USB 40s later, my linux could not detect the MT phone on USB at all. Bootrom-step stayed in waiting stage.

With shorting, I can see MT6227 when the short was on, and changed to MT67xx when i removed the short. However, i got serial.serialutil.SerialException: write failed error.

My setting were ADB debugging on, USB debugging off.

I also tried adb devices when I connected the Sloane, but it never showed up.

Here are all information. Thanks a lot for taking time and trying to help me.

And my device is not demo.
[Fire TV Original Android Development] Bertonumber1:
No problem mate that's what it's all about, we help each other.

Try with your USB debugging on iyw, though this shouldn't matter because the script connects directly with the box through adb and emmc.

Just keep trying is best advice I can give, sometimes I've sat for a day or two before finally succeeding, but you have to have a break. Sometimes if you leave it for an hour then go back it's better and seems to work.

Just keep trying, try different cables and USB ports.

Also try doing the short and as I say leave box on run script again and unplug power and usb a to a cable then power on, leave for 40 secs and plug USB in

Sloane is tough but you will get there eventually.. Maybe even try using the old script amonet 1.3 and flash the unlock with that????

Yeah keep trying
[Fire TV Original Android Development] Bertonumber1:
Nah, I don't need to educate myself mate I'm not the one sitting like a muppet with a locked device you fkin moron.

Like is said if it weren't for the developer you're slating (for no reason other than your own frustrations) and a few others WE wouldn't have this unlock. So yeah..... Show some fkin respect. They don't need to earn it, they put the hard work in and it speaks for itself...

Ain't about ass kissing either, I'm only saying what everyone else reading this thread is thinking right now.

Stop being a **** and show some respect. Don't come on a keyboard shouting odds you idiot You're out of order and thats all about it. Speak to others the way you would want to be spoken to. No, you're not the only one experiencing issues but you're acting like you are!!! Noone else is on here telling devs to **** off bar you...

Who is this clown, where did he crawl in from???

You'll get far in life with an attitude like that.

Prick.
[Fire TV Original Android Development] :
Sorry if I am not here to placate you and the other dimwits who are disrespectful to others. You need to catch up on what is going on before you go shooting off your mouth because you clearly don't have a clue. There was a reason I told the other poster to f**k of and if you don't see it, you just might have a problem too. Outside of your lack insight you don't seem to have much to offer so I don't see the need to deal with you either.
[Fire TV Original Android Development] Bertonumber1:
I know exactly what the problem is with you're device and why it's not flashing the images , probably other people do too. But you're so clued up and in the know ( telling people to **** off) well you can go figure it out yourself I hope you're Sloane electrocutes you and stays a brick. You're in demo mode you weapon
[Fire TV Original Android Development] Seattleweather:
Guys,

Looks like serial.serialutil.SerialException: write failed: [Errno 5] Input/output error is common with Amazon fire device. I tried all tricks, but the problem is showing up every time for me. Time for me to throw the trowel now.
[Fire TV Original Android Development] :
I am obviously experiencing the same issues, but the only real difference seems to have been I started out with a demo unit. It may be good to just step away for awhile and check back to see if the issue has been solved after some time.

I am going to check back this weekend to see if the other person who was going to try to unlock a few demo units is successful or not.

I would recommend just setting the device aside as our fortunes could change in the future.
[Fire TV Original Android Development] retyre:
In my experience, the Sloane is rather finicky about staying in BootROM mode (i.e., the first attempt always fails with a write error because the board leaves BootROM mode before much of the code is processed). Here's what I'd suggest:

-- Brick the preloader to start: Copy main.py to main_o.py and then edit main.py to remove most of the early checks and retain just the preloader-bricking part. Like so:

#!/usr/bin/env python3
import sys
import struct
import os
import sys
import time

from common import Device
from handshake import handshake
from load_payload import load_payload
from logger import log
from functions import *
from gpt import parse_gpt_compat, generate_gpt, modify_step1, modify_step2, parse_gpt as gpt_parse_gpt

def main():

minimal = False

check_modemmanager()

dev = Device()
dev.find_device()

# 0.1) Handshake
handshake(dev)

# 0.2) Load brom payload
load_payload(dev, "../brom-payload/build/payload.bin")

# Clear preloader so, we get into bootrom without shorting, should the script stall (we flash preloader as last step)
# 10) Downgrade preloader
log("Clear preloader header")
switch_boot0(dev)
flash_data(dev, b"EMMC_BOOT" + b"\x00" * ((0x200 * 8) - 9), 0)

if __name__ == "__main__":
main()

With this as main.py, run ./bootrom-step.sh and execute the short with the help of your fingers and toes. [If your toes won't cooperate, here's a suggestion: Leave the board-end of power always connected and plug the brick into a remote-controlled outlet or smart plug. Turn it on with voice or remote when you're ready to short.]

This will render the device in BootROM mode until the preloader is written back. Once there, turn off power, rename main_o.py back to main.py, run ./bootrom-step.sh, and turn the device back on with the USB plugged in. Press Enter to begin the process since the device is already in BootROM mode. If it fails, do NOT turn off power to the board. Do the following:

-- Unplug the USB cable.

-- Run ./bootrom-step.sh.

-- Plug in the USB cable. Press Enter to begin the writing process.

-- The writing process should complete as expected. If so, run ./fastboot-step.sh with the device in fastboot mode.
[Fire TV Original Android Development] Seattleweather:
Got serial protocol mismatch error when i did the first step.

mint@mint:~/Desktop/amonet1.0.1$ sudo ./bootrom-step.sh

[2021-02-12 05:18:59.775421] Waiting for bootrom

[2021-02-12 05:20:49.315341] Found port = /dev/ttyACM0

[2021-02-12 05:20:49.316772] Handshake

[2021-02-12 05:20:49.317806] Disable watchdog

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

[2021-02-12 05:20:55.245488] Init crypto engine

b'\xa0'

b'\xd4'

Traceback (most recent call last):

File "main.py", line 37, in <module>

main()

File "main.py", line 27, in main

load_payload(dev, "../brom-payload/build/payload.bin")

File "/home/mint/Desktop/amonet1.0.1/modules/load_payload.py", line 112, in load_payload

init(dev)

File "/home/mint/Desktop/amonet1.0.1/modules/load_payload.py", line 9, in init

dev.write32(CRYPTO_BASE + 0x0C0C, 0)

File "/home/mint/Desktop/amonet1.0.1/modules/common.py", line 158, in write32

self.check(self.dev.read(1), b'\xd4') # echo cmd

File "/home/mint/Desktop/amonet1.0.1/modules/common.py", line 93, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch
[Fire TV Original Android Development] :
I got a similar Serial error.

[2021-02-11 23:46:01.495541] Waiting for bootrom

[2021-02-11 23:47:01.043661] Found port = /dev/ttyACM0

[2021-02-11 23:47:01.045634] Handshake

[2021-02-11 23:47:01.046540] Disable watchdog

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

[2021-02-11 23:47:07.818478] Init crypto engine

Traceback (most recent call last):

File "/usr/lib/python3.9/site-packages/serial/serialposix.py", line 621, in write

n = os.write(self.fd, d)

OSError: [Errno 5] Input/output error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/main.py", line 38, in <module>

main()

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/main.py", line 28, in main

load_payload(dev, "../brom-payload/build/payload.bin")

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/load_payload.py", line 112, in load_payload

init(dev)

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/load_payload.py", line 9, in init

dev.write32(CRYPTO_BASE + 0x0C0C, 0)

File "/home/jim/Downloads/amonet-sloane-v1.0.1/amonet/modules/common.py", line 157, in write32

self.dev.write(b'\xd4')

File "/usr/lib/python3.9/site-packages/serial/serialposix.py", line 655, in write

raise SerialException('write failed: {}'.format(e))

serial.serialutil.SerialException: write failed: [Errno 5] Input/output error
[Fire TV Original Android Development] Rortiz2:
How about you respect the people who are trying to help you? Nobody is going to help you anymore if you treat people like that.
[Fire TV Original Android Development] :
Not everyone is trying to help.

Take a look at k4y0z replies and tell me how he is trying to help. The responses are more belligerent than helpful.
[Fire TV Original Android Development] Rortiz2:
Look man, I'm not going to argue with people like you. He clearly tried to help and you replied to him with rude stuff. II will not tolerate any more disrespectful responses in my thread.
[Fire TV Original Android Development] k4y0z:
It looks like it's failing before even loading the payload.
[Fire TV Original Android Development] retyre:
Yes, I'm not sure what's happening in #163. The error in #164 is along the lines of what I wrote. It can be fixed with a quick trigger (i.e., pressing Enter as soon as " * * * Remove the short and press Enter * * * " appears in the window) and a shorter code w/o the early checks.
[Fire TV Original Android Development] Sus_i:
Does the box led starts flashing white just with this error?
[Fire TV Original Android Development] k4y0z:
#164 also looks like it's failing before the payload is loaded.

Given how flaky sloane seems to be, it's probably still a good idea to move the preloader-bricking to the very beginning.
[Fire TV Original Android Development] k4y0z:
@retyre @Seattleweather

I did some debugging and the issue seems that sloane for some reason reboots after the initial handshake (even though watchdog is disabled)

I have attached a version with a workaround.

It does two things different:

It waits for the device to reboot, before telling you to remove the short.

It clears the preloader as the very first thing after loading the payload (as @retyre suggested)

Please test and let me know if that works.
[Fire TV Original Android Development] meohmy:
My Fire tv box was running the latest 5.2.7.6 pre rooted image, I installed the amonet-sloane v1.01 from twrp, wiped data and then installed update-kindle-full_sloane-36.6.6.2_user_662663720.zip and Magisk 21-4, then rebooted the Firetv via twrp. On reboot it goes directly to amazon without showing the twrp screen, when fully booted, Magisk is shown under apps but not installed, I have obviously done something wrong so tried to root using the oringinal root method using mtk-su. Using this original method , when using the command ./mtk-su I get the error message 'Failed critical init step 1'. Result is I don't know if the directory structure has been changed, can't install magisk through the Magisk app and am unsure as to what step to take next. The box works fine but I need advice on the best way to get twrp reinstalled.

Any suggestions appreciated
[Fire TV Original Android Development] brick00444:
Have you tried to "adb reboot recovery" ? It doesn't show twrp while booting but adb works to enter twrp.
[Fire TV Original Android Development] meohmy:
Thanks for the prompt reply, that worked thanks. I assumed that I had 'a senior moment' and missed a step and had completely forgotton about trying that command, so used to rebooting straight to twrp.
[Fire TV Original Android Development] Seattleweather:
Shown MT6227 Phone while shorting, but bootrom-step did not change. I tried to hit enter key, nothing happened. by the way the white light did not light up during this process.

$ ./bootrom-step.sh

[2021-02-12 18:12:02.072023] Waiting for bootrom
[Fire TV Original Android Development] k4y0z:
This one is supposed to take quite a bit longer until it tells you to "remove the short".

Can you provide a complete log?

It also seems you didn't use sudo
[Fire TV Original Android Development] Seattleweather:
I did again with new 1.02, the new main.py when through no problem. However, the LED never light up. After that, i switched the old back, but nothing happened. The LED never light up again. Is it dead?

mint@mint:~/Desktop/amonet1.0.1$ sudo ./bootrom-step.sh

[2021-02-12 18:21:00.495665] Waiting for bootrom

[2021-02-12 18:21:57.461570] Found port = /dev/ttyACM0

[2021-02-12 18:21:57.462349] Handshake

[2021-02-12 18:21:57.463711] Disable watchdog

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

[2021-02-12 18:22:00.925032] Init crypto engine

[2021-02-12 18:22:00.952517] Disable caches

[2021-02-12 18:22:00.953255] Disable bootrom range checks

[2021-02-12 18:22:00.972862] Load payload from ../brom-payload/build/payload.bin = 0x4760 bytes

[2021-02-12 18:22:00.975412] Send payload

[2021-02-12 18:22:01.900474] Let's rock

[2021-02-12 18:22:01.901694] Wait for the payload to come online...

[2021-02-12 18:22:01.905449] all good

[2021-02-12 18:22:01.905752] Clear preloader header

[8 / 8]
[Fire TV Original Android Development] k4y0z:
This does not look like the one I provided, but the modified one @retyre provided.

You'll have to run the normal one again (but this time you won't need to short)
[Fire TV Original Android Development] Seattleweather:
Correct. I used the modified one @retyre provided. Now nothing comes up. Now my LED does not come up, and plug in power nothing happens. Is it dead?
[Upgrading, Modifying and Unlocking] Motherboardcomputinginc:
Please!!!! please! help me out. I have iPhone 6 plus 64GB it is stuck on the apple logo with a progress bar. It happened when I was presented with an update notification. at first, it was running on IOS 12.0. After an update notification appeared, i connected the phone to iTunes and everything went well with no errors at all. but the phone never gets past the progress bar. It loads until it stops at the last 1-millimeter end. at stays there for even a day. I tried to flash it using the latest 3u tools , it flashes well with no errors at all but still the same thing happens. I tried DFU mode flash but still the same thing happens.

Surprisingly, if i connect it to pc, it shows everything well. I can even put in music, movies and other files. I have include all the pics.

please help its the only phone i have right now.