[UNLOCK][ROOT][TWRP][UNBRICK][DOWNGRADE] Fire 7 (ford and austin).

[moon2oon]

plz help me

 

[surfrock66]

Anyone have a tip for getting the short working on the 7th gen? I've got it open, put a dollop of solder on the pad, and still I only get lsusb to show up as "preloader". Is there a preferred short point? Should I disconnect the battery?

 

[VaD_3r]

When I run bootrom-steps.sh its gets stuck on on "Handshake" and it doesnt do anything when I press the on and left volume button. I have a FORD model and I downgraded the firmware. Anyone know what to do?

 

[moon2oon]

same problem plz help

 

[DIYBrickLayer]

What is a preloader?

 

[moon2oon]

i need short video bro i cant understand whole process i try many times but i failed

 

[cnviper]

Hello, I used 5th Gen: amonet-ford-v1.4.1.zip to downgrade Ford 16g ，The is flashed After that, it died. I'd like to know why,.

 

[cnviper]

root@ubuntu:~/Desktop/fire7-2015/amonet-ford-v1.4.1/amonet# '/root/Desktop/fire7-2015/amonet-ford-v1.4.1/amonet/bootrom-step.sh'
[2021-07-19 02:26:47.356615] Waiting for bootrom


[2021-07-19 02:27:06.539664] Found port = /dev/ttyACM0
[2021-07-19 02:27:06.543788] Handshake
[2021-07-19 02:27:06.551767] Disable watchdog

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

[2021-07-19 02:27:06.559937] Init crypto engine
[2021-07-19 02:27:06.975389] Disable caches
[2021-07-19 02:27:06.981383] Disable bootrom range checks
[2021-07-19 02:27:07.164145] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes
[2021-07-19 02:27:07.165496] Send payload
[2021-07-19 02:27:15.982870] Let's rock
[2021-07-19 02:27:15.990997] Wait for the payload to come online...
[2021-07-19 02:27:16.600913] all good
[2021-07-19 02:27:16.601150] Check GPT
[2021-07-19 02:27:16.916273] gpt_parsed = {'KB': (2048, 2048), 'DKB': (4096, 2048), 'EXPDB': (6144, 35584), 'UBOOT': (41728, 2048), 'boot': (43776, 32768), 'recovery': (76544, 32768), 'MISC': (109312, 1024), 'LOGO': (110336, 7168), 'TEE1': (117504, 10240), 'TEE2': (127744, 10240), 'system': (137984, 2457600), 'cache': (2595584, 512000), 'userdata': (3107584, 27428063), '': (0, 1)}
[2021-07-19 02:27:16.916400] Check boot0
[2021-07-19 02:27:17.125485] Check rpmb
[2021-07-19 02:27:17.336931] Clear preloader header
[8 / 8]
[2021-07-19 02:27:17.753350] Downgrade rpmb
[2021-07-19 02:27:17.759387] Recheck rpmb
Traceback (most recent call last):
File "main.py", line 156, in <module>
main()
File "main.py", line 114, in main
raise RuntimeError("downgrade failure, giving up")
RuntimeError: downgrade failure, giving up

 

[cnviper]

This is 5th 16g, 7th, no problem

 

[ndoggac]

Wow, thank you so much for this!! Talk about breathing new life into this aging tablet. Hated the FireOS with a passion! LineageOS is fairly buttery on this tablet, I was pleasantly surprised!

Couldn't get the bootloader using the highlighted pin on the 7th gen (Austin) after about 10 attempts, but got it first time with the two surface mount caps highlighted in another picture in the thread (just "east" of pin). Also made the mistake of doing an install of Magisk BL from within the app once booted up, and got a boot loop and had to start all over in TWRP. You can install the magisk app, and enable super user, but do not install magisk bootloader (first option) from within the app. Download a new magisk apk, rename to a zip file and flash it from TWRP. I've turned "check for updates" off in Magisk app.

Still seeing the auto-rotate issue in LineageOS, is there a fix for that? It stinks cause there's no manual override either. I wouldn't mind if I could just set it to portrait or landscape, it doesn't have to be automatic. Oh well, still way better than before! I might try out Ultimate Rotation Control or something to see if I can override?

 

[ndoggac]

Because I had problems unlocking my Fire 7th gen, I will give my experience to you.
(yes, the post above is about the 5th gen - that's right, I own both)

All the images and how-tos discribe to shorten a pin next to the cpu before plugging USB in. I tried that over and over again. But: That's not right! This does not work.

There are two tiny resistors nearby the ram. These resistors have to be shortend.

I've attached a better picture of this.

I hope that helps.

Thanks so much for this!!! Tried 10 times with highlighted pin with no luck. Used your picture and worked first time!! This is post #1815 in this thread. The 7th gen picture on the first post should be updated with this. Also, both pictures attached in the first post are titled as the same generation, so its even more confusing.

 

[boris099]

When I run bootrom-steps.sh its gets stuck on on "Handshake" and it doesnt do anything when I press the on and left volume button. I have a FORD model and I downgraded the firmware. Anyone know what to do?

I had the same problem. So I decided to use Ubuntu (just took the latest version) and it just worked (used MXLinux before but this not working for what ever reason)
I only applied "sudo apt install python3 python3-serial adb fastboot" cause the rest is already included!

Maybe this hint should be added to the OP?

 

[struct_de]

Initial post didnt work for my fire 7" 5th gen (Ford). I had to disconnect the battery before shortening the described pin. After that everything worked perfectly.

I had to search a lot of posts in this threat before finding the hint. Would be nice if this could be incorporated in the original post.

jba

 

[devsphoto.com]

Because I had problems unlocking my Fire 7th gen, I will give my experience to you.
(yes, the post above is about the 5th gen - that's right, I own both)

All the images and how-tos discribe to shorten a pin next to the cpu before plugging USB in. I tried that over and over again. But: That's not right! This does not work.

There are two tiny resistors nearby the ram. These resistors have to be shortend.

I've attached a better picture of this.

I hope that helps.

this worked for me as well

how long does it take for fastboot to write ?

 

[azaopung257]

Himax m20s

 

[thistof]

I had gotten to the "remove short" step a couple months ago, but didn't have time to work on it. Now that I'm trying it again, nothing happens at all. Could it be that the battery no longer has charge? Does the battery need to be charged to do this? If so, how can I charge it? I left it in to charge overnight but still no change

 

[mikewazowski1993]

Hello, I'm new here, I'm currently having an issue, I've made it past the first step, (option 2) and my device is currently black, and plugged in.

# ./bootrom-step.sh
[2021-09-29 09:32:12.933648] Waiting for bootrom
[2021-09-29 09:33:36.744600] Found port = /dev/ttyACM0
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 265, in open
    self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyACM0'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "main.py", line 156, in <module>
    main()
  File "main.py", line 72, in main
    dev.find_device()
  File "/home/mint/Desktop/amonet/modules/common.py", line 83, in find_device
    self.dev = serial.Serial(port, BAUD, timeout=TIMEOUT)
  File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in __init__
    self.open()
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, in open
    raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))
serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyACM0: [Errno 2] No such file or directory: '/dev/ttyACM0'

I'm not sure what this error is, or why it happened, but I would like to know where I can go from here. Is my device softbricked for now? Or is this worse than a softbrick, thank you.

 

[captain_nemodroid]

Hello, I'm new here, I'm currently having an issue, I've made it past the first step, (option 2) and my device is currently black, and plugged in.

# ./bootrom-step.sh
[2021-09-29 09:32:12.933648] Waiting for bootrom
[2021-09-29 09:33:36.744600] Found port = /dev/ttyACM0
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 265, in open
    self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyACM0'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "main.py", line 156, in <module>
    main()
  File "main.py", line 72, in main
    dev.find_device()
  File "/home/mint/Desktop/amonet/modules/common.py", line 83, in find_device
    self.dev = serial.Serial(port, BAUD, timeout=TIMEOUT)
  File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 240, in __init__
    self.open()
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 268, in open
    raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))
serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyACM0: [Errno 2] No such file or directory: '/dev/ttyACM0'

I'm not sure what this error is, or why it happened, but I would like to know where I can go from here. Is my device softbricked for now? Or is this worse than a softbrick, thank you.

I doubt it's bricked. first make sure everything is updated, including python 3. I had to try several times to get it to enter bootrom correctly. I ended up shorting out the vdd1 pin instead of com. here is the link that shows the pins.

 

[Kallaste]

I tried this on a 5th gen fire using the option to downgrade the firmware rather than the shorting option. After downgrading and bricking, I cannot get through the bootrom step. It is stuck on the handshake after plugging the device in.

 

[Kallaste]

I tried this on a 5th gen fire using the option to downgrade the firmware rather than the shorting option. After downgrading and bricking, I cannot get through the bootrom step. It is stuck on the handshake after plugging the device in.

I resolved this problem. I had this error for two hours, and I tried many times to get it to work, pressing volume and power buttons over and over again, and doing all kinds of things to try to unstick the device. I had a feeling it was stuck in some noncommunicable state, so what I did finally was open the device and disconnect the battery for 30 seconds, then reconnect it and hold down the power button for ten seconds. Then I went through the bootrom step again, and it completed perfectly.