yashsingh1/xdaforums huggingface dataset:
[Fire General] cyborggold:
Okay, I got it to short once, and the script froze. Now when I try I get the following:

ubuntu@ubuntu:~/Downloads/amonet$ sudo ./bootrom-step.sh

[2020-02-16 21:19:06.178553] Waiting for bootrom

[2020-02-16 21:19:52.950013] Found port = /dev/ttyACM0

[2020-02-16 21:19:52.989056] Handshake

[2020-02-16 21:19:53.009899] Disable watchdog

Traceback (most recent call last):

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

main()

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

handshake(dev)

File "/home/ubuntu/Downloads/amonet/modules/handshake.py", line 11, in handshake

dev.write32(0x10007000, 0x22000000)

File "/home/ubuntu/Downloads/amonet/modules/common.py", line 160, in write32

self.check(self.dev.read(2), b'\x00\x01') # arg check

File "/home/ubuntu/Downloads/amonet/modules/common.py", line 87, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch
[Fire General] Sonicfann:
can someone help me it says permission denied when i run ./mtk-su
[Fire General] mchipser:
I have done 5 of these and all are showing the same issue.. if the battery is drained the device wont power back on unless i remove the battery plug it in, wait for the amazon logo, then plug the battery back in.. then the device will charge.. I am not sure if i missed a step, but all of them are doing it.. I updated TWRP to 3.3.1-0 and flashed lineageOS on all of them.. any advice?

EDIT: it looks like I need to flash the zip from here.. https://xdaforums.com/showpost.php?p=80621157&postcount=253
[Fire General] pesadilla1973:
lock at Step 16

Hi guys

I was able to follow the HW method up to 16

Go to "Wipe" and do the default wipe, then reboot

Basically the fire Smiley with 3 dots moving... I'd wait up to 1 hour.
[Fire General] pesadilla1973:
Answer to myself,

this is a Stupid question, just follow the steps. {16. Go to "Wipe" } means go to home and press WIPE

regards
[Fire General] Michajin:
Try...

sudo systemctl stop ModemManager

$ sudo systemctl disable ModemManager

$ sudo ./bootrom-step.sh

---------- Post added at 04:17 PM ---------- Previous post was at 04:15 PM ----------

What version are you on?

"Fire 7 9th gen (2019) (thanks [MENTION=4914529]Michajin[/MENTION]) -- up to Fire OS 6.3.1.2 build 0002517050244 only"

If You have an updated device, you must do the hardware way.
[Fire General] Michajin:
Just curious, open another terminal. Lsusb- Are you in bootloader or preloader?
[Fire General] ghostdogg49504:
i'm a noob

what on earth is an ssh server
[Fire General] ghostdogg49504:
no flash option in recovery

not sure i have the right device but my recovery doesn't have a flash option but it's an amazon fire 7 tablet i bought from walmart on black friday
[Fire General] Michajin:
You have to do the hardware method.... Amazon has removed adb sideload from recovery.
[Fire General] mkjhwvsrb:
My build number is 0003188263812

Is it impossible to root my device?

[MENTION=4914529]Michajin[/MENTION] I have tried hardware method, unplugged and turned off(waiting for bootrom) and then plugged the device but no results, only "fail"

I guess there is no way to root or install twrp recovery....
[Fire General] Michajin:
You would be the first. What else does it say besides fail? Does it fail on bootrom.sh? It might be the live disk you are using, a driver problem, or a bad set up. You need to post what the script is saying besides "fail". It sounds like you are not going into the bootrom, but the instead the preloader. Do a lsusb and see if it says preloader or phone. Phone would be bootrom...

From my expierience it seems like i fireOS works best for the bootrom.sh, and standard linux works best for fastboot.sh.

Here us the link for the live disk i used for most of mine..

https://github.com/amonet-kamakiri/fireiso/releases

This has modem manager disabled and drivers. Some had had issues with fastboot drivers though on it (if so use the ubuntu? or what you have been?)

The failure.... I am assuming you followed EVERY step closely from the directions? Just to be clear...
[Fire General] ghostdogg49504:
how do i do that i just wanna change the rom to regular android
[Fire General] Michajin:
Read the first post in this thread (hardware option). You have to unlock. Once unlocked and TWRP is installed you can flash lineage...
[Fire General] ghostdogg49504:
i did read it but i don't understand his instructions or where ground is and my eyesight isn't that good :(
[Fire General] Michajin:
Run the bootrom script. The shield cover would work for a ground. I piece of aluminum foil rolled up would work. Touch the red dot pit to the shield cover retainer (about 1/8" away from it?) and power it on while the script is saying waiting for device.

https://xdaforums.com/showpost.php?p=79683131&postcount=22

maybe a magnifying glass would help?
[Fire General] champs777:
I tried the Software Install. These instructions are for that. Not for the Hardware side.

Boot up fire tablet.

Login to Amazon

It will download update but don't install it.

Enable Developer Option

Device options -> About Fire Tablet -> Keep clicking on serial number

Settings -> Device Options -> Developer Options -> Turn On

Enable USB Debugging

Settings-> Developer Options -> Enable USB Debugging

I installed Ubunu v18.04.4

Get Live CD for Ubuntu and install to flash drive.

Boot to flash drive

On all installs you will be prompted to continue, say yes.

Control + Alt + T for a terminal window

Install python

sudo apt install python3 python3-serial

To install fastboot and adb

sudo add-apt-repository universe && sudo apt-get update && sudo apt-get install android-tools-adb android-tools-fastboot

Remove ModemManager

sudo apt-get remove modemmanager

Plug tablet into PC.

Make sure when you plug into computer you allow usb debugging.

In terminal window type adb devices.

If you see a number and unathorized, unplug tablet and plub back in. Then I got a prompt to allow the USB degugging connection. Make sure you see a number and the word device...not unauthorized.

Download mtk-su (I downloaded version 20) from https://xdaforums.com/and...armv8-t3922213

Download 2 files from this post. They are at the bottom

amonet-mustang.zip

Finalize.zip

It will download to /home/downloads

Navigate via the Files icon on the desktop.

Right click on file and extract here.

Double click folder.

Right click on folder and click on open in terminal

Paste this in terminal window "adb push arm/mtk-su /data/local/tmp"

Once done type ADB Shell. Keep this ADB shell window, you will need it.

Run code block at step #6

Keep the Files window Open

Extract this file from /home/downloads

amonet-mustang

Open the folder. Right click and open terminal window.

Type this sudo ./bootrom-step.sh

Verify that you see this message "Waiting for the bootrom"

Open the ADB Shell Terminal window.

Type reboot and the the "Waiting for the bootrom" will change to a message and Press Enter to Continue.

Press Enter

It will process for about 4 minutes.

If you see this message "Reboot to unlocked fastboot" you are golden.

Type fastboot devices on the non-ADB shell window

You should see your device ID and fast boot.

If you do, run this. sudo ./fastboot-step.sh

Your device will now boot into recovery! Press the power button twice if you screen is black.
[Fire General] LocoMexican:
My Fire 7 9th gen. has already updated to latest so software rooting is not available. I want to try the hardware method, but I'm having a problem getting ADB enabled. I have "Developer Options" turned on, but there is no option to "Enable ADB" as the "how to" instructs.

Settings-> Developer Options -> Enable ADB

Is there any other way to "Enable ADB"? Without enabled ADB, is there another way to push files and folders to the device sd card?? Any suggestions are appreciated. Thanks.
[Fire General] Michajin:
It is there, i think it is call usb debugging
[Fire General] LocoMexican:
Yes, I've turned on developer options, and then adb debugging and unknown sources, but there is no option visible anywhere on the screen to enable adb. When I try to adb connect (device ip) it does not connect or push or install or anything else that requires a adb connection. In other words, it will not enable adb connections. However, this device does have an sd card slot. So, can I copy the necessary "push" file to the sd card and then flash the files from the external sd card in TWRP? Thanks for your response.
[Fire General] DB126:
Possibilities:

- bad port or cable (data pins/wires); try different USB ports on host, different host, different cable, etc

- adb is stuck in 'charging mode' which can suppress notification with options to select/switch modes when first tethered. Google for a solution; not easy to find
[Fire General] CompuGenius Programs:
Custom ROMs

Does anyone know of custom ROMs that are compatible with Mustang besides Lineage OS 14.1? It keeps powering off randomly, and i need to pull the battery out to fix it.
[Fire General] baconphonics:
Thanks a lot for this post. I got pretty far but I got stuck at step 11.

At step 10, I got the successful feedback, and the device rebooted. The amazon logo came up and stayed on the screen. Now I am stuck in a position, though, where it seems that adb can't connect to the device, so I can't move on to the next step.

[2020-03-20 14:41:24.930600] Reboot to unlocked fastboot
demo@mx1:~/amonet-mustang
$ fastboot devices
no permissions (user in plugdev group; are your udev rules wrong?); [snipped for url, forum rules]
demo@mx1:~/amonet-mustang
$ adb shell
error: no devices/emulators found

Any idea why, or what I might do to fix it? From the post it sounds like the logo should have appeared briefly and then disappeared. This is using the software method.

----

Update:

I ended up restoring the stock image and trying again, and things went smoothly on the second try. Not sure what changed, but try again is my suggestion.
[Fire General] Michajin:
Not really sure why you have to pull the battery. Have you tried holding the power button down for ~10 seconds to force reboot? Mine will crash occasionally not often.
[Fire General] kg_jettaIV:
I got a new Fire and followed the software root method and overall everything seems to be working pretty well except for the Battery section in Settings. When I go to Settings and select Battery it just crashes back to the home screen. I need to try and disable batter optimization for Tasker but can't get to it. Any thoughts or anyone else with this issue.

Also, anyone know if OTG and charging simultaneously is possible?

Thanks
[Fire General] Michajin:
i was just reading this again... why do you need ADB if you are doing the hardware method?
[Fire General] Bandor:
Is there another way to get the file "update-kindle-NS6312_user_1827_0002517050244.bin"?

With the link (from amazon; from page 1) i need to download the file for about 12 days?!?
[Fire General] AntJWebb:
Please help! :(

So, I have three Fires here, I've been using the hardware method (as annoyingly they were all updated to FireOS 6.3.1.5) and have successfully got two out of three running LineageOS with no issues at all.

Unfortunately, the third now seems to be semi-bricked, or possibly worse - I don't give up easily, but I think I've now read every message in the thread and tried all sorts with no joy..

I am able to short the point on the PCB and when I plug in the USB cable bootrom-step.sh picks it up as expected and seems to complete successfully, with

[8 / 8]
[2020-03-31 20:49:44.294080] Reboot to unlocked fastboot

however, the screen then remains blank - on the other two at this point they rebooted, the Amazon logo came up, and running fastboot devices showed a device, and I could proceed with fastboot-step.sh, but with this one nothing seems to be able to get it going again. I've tried holding various button combinations, leaving the battery unplugged for a long period several times, then after plugging battery back in I've tried either plugging in USB, or holding button combos, or putting it back in mains charger, whatever I do it just stays blank, and whatever the state, whenever I plug in to USB nothing seems to be picked up at all,

EXCEPT -

I know it's not completely dead, because I can still short the contact on the PCB and when I plug in USB then with bootrom-step.sh running, it picks it up straight away and can complete that whole process successfully, which I have now done quite a few times, but with the same result - blank screen and no fastboot :(

What do you all think, any chance I can recover from this?
[Fire General] Michajin:
Unplug and Try holding the power button for about 20 seconds, then tap it again. If nothing happens, trying holding the power for 20seconds (again) try holding volume down and power. Might get you into recovery... and give the option to boot into fastboot..
[Fire General] AntJWebb:
Not even a flicker :(
[Fire General] Michajin:
Have you tried pulling the battery? You might need to run the script again....
[Fire General] AntJWebb:
Yep, I have pulled the battery overnight, I have successfully re-shorted the contact and re-run the bootrom-step.sh script multiple times, both with and without the battery connected, each time it finishes successfully and says "Reboot to unlocked fastboot" but never comes back up in fastboot mode.

Looking at it I would definitely think that tablet was 100% bricked if it wasn't for the fact that shorting the contact definitely does get it back into the mode that bootrom-step.sh detects, and that whole script seems to work fine - it just won't come back up in fastboot mode afterwards, I really can't figure it out!

Thanks for your help, am very close to just giving up on this one, prob not even worth anything in parts is it
[Fire General] Michajin:
when you do a lsusb, does it just say phone always? have you tried holding volume down while plugging in? it might get you into recovery....
[Fire General] morgiee:
Thanks for this thread really informed but I only have a couple of questions.

1. The fire HD 7 is currently on stock version 6.3.1.5 will these steps still work?

2. I don't have a Linux pc but do have a raspberry pi version 3 b+ with USB ports on it. Will this still work if I use the pi as my Linux pc?

3. Once the recovery is installed and is unlocked I'm looking to remove fire OS completely and either install a custom rom or standard android OS. Is this possible and which custom rom is best to use?

Many thanks
[Fire General] Michajin:
1. Yes, the hardware unlock should still work, the software method will NOT (up to Fire OS 6.3.1.2 build 0002517050244 only)

2. Yes the rpi3 should work, i have used it on some of mine...

3. There is only one custom rom, it is fairly stable, OP for it is taking a break (last i read he said sometime this quarter he will continue it) - Here is the link:

[ROM][unlocked][mustang] Lineage-14.1 [27 AUG 2019]

https://xdaforums.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329
[Fire General] crankycowboy:
Newb in need of help

So I have a have one of these tablets that I just got. It is at FW 6.3.1.5 (I actually didn't realize that there was a cutoff for the software option. I started there and when I got to mtk.su I was getting a permissions error. I then did some more reading and realized that it was related to my FW version. So then I decided to give the hw option a try. I have it opened up and ready to short; however, when I navigate to the directory where I have the amonet-mustang folder and execute : "sudo ./bootrom-step.sh" I get a "command not found" error. If I go "ls", it lists the files in that folder (folders: bin, brom-payload, lk-payload, modules) and then (files: bootrom-step.sh and fastboot-step.sh). So the file is there, but it's saying command not found. Any idea what could be wrong? Thanks in advance.
[Fire General] Michajin:
Try without sudo, you might have to do a chmod for all files...
[Fire General] lucas.lop:
Is there another point of short? The one in post # 22 is not working for me.
[Fire General] Ozed20:
Device offline MTP Error

I follow everything flawlessly until step 7. None of my SD cards are recognized. So I follow the steps posted in Step 7. In my device list I see "omni mustang" then it says I cant access this drive. I do step 7 then go to push lineage onto the system it says device offline.

I have rebooted the tablet many times Disable MTP and Enabled MTP countless times.

Sorry this is all jumbled up. Hopefully you understand what I am trying to say.
[Fire General] jcruz942:
I ran into this issue as well. The only way I could even boot the device past recovery was to use "adb sideload lineage.zip"
[Fire General] Bandor:
Hello,

my problem is, that i cant find the files which i copy (adb push Magisk-v19.3.zip /sdcard) to the sdcard.

At first i root the fire 7 (i think) like it is explain in post Nr.1.

The first time i can copy the files with the command adb push... to the sdcard like it is explaint. Then i found this file in TWRP and flash the 3 files (fw.zip, Magisk-v19.3.zip, finalize.zip).

There are no error displayed so i think the root was ok.

Now see that there is a new version of Magisk-20. So i copy the new downloadet file to the sdcard with adb push...

The same i do with the GApps file

But now i cant find the new files on the sdcard in TWRP to flash them. There are just the 3 files from the first time.

If i start the fire 7 i can see that Android OS i can see all the files (form the first time and the second time) on the sdcard. (Settings, Storage, SD-Card,)

Perhabs it has something to do with, that after i root and boot the first time i was ask something how i want to use the SD-Card (i thought it was mean the extern SD Card). I do not know anymore what i chose.

what am I doing wrong
[Fire General] pitak-x:
Thanks for the instruction.

But I'm in a bootloop after the 16th step. I tried to reinstall the update (fw.zip) twice without any effect.

Best regards,

Pitak
[Fire General] firetesting:
Still Lost

I got past this screen. Ignore my post below... Had to make sure i was shorting correct pin.. Thats they key if the below error comes up.

Hi guys,

I tried everything but still no joy.

Please can anyone help me with this error :

xubuntu@xubuntu:~/amonet-mustang$ sudo ./bootrom-step.sh

[2020-05-08 13:52:08.193860] Waiting for bootrom

[2020-05-08 13:52:19.543158] Found port = /dev/ttyACM0

[2020-05-08 13:52:19.598260] Handshake

* * * If you have a short attached, remove it now * * *

* * * Press Enter to continue * * *

Traceback (most recent call last):

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

main()

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

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

File "/home/xubuntu/amonet-mustang/modules/load_payload.py", line 99, in load_payload

dev.write32(0x10007008, 0x1971) # low-level watchdog kick

File "/home/xubuntu/amonet-mustang/modules/common.py", line 147, in write32

self.check(self.dev.read(2), b'\x00\x01') # arg check

File "/home/xubuntu/amonet-mustang/modules/common.py", line 84, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch

^CException ignored in: <module 'threading' from '/usr/lib/python3.8/threading.py'>

Traceback (most recent call last):

File "/usr/lib/python3.8/threading.py", line 1388, in _shutdown

lock.acquire()

KeyboardInterrupt:

xubuntu@xubuntu:~/amonet-mustang$ ^C

xubuntu@xubuntu:~/amonet-mustang$

AND:

xubuntu@xubuntu:~/amonet-mustang$ sudo ./bootrom-step.sh

[2020-05-08 13:52:08.193860] Waiting for bootrom

[2020-05-08 13:52:19.543158] Found port = /dev/ttyACM0

[2020-05-08 13:52:19.598260] Handshake

* * * If you have a short attached, remove it now * * *

* * * Press Enter to continue * * *

Traceback (most recent call last):

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

main()

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

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

File "/home/xubuntu/amonet-mustang/modules/load_payload.py", line 99, in load_payload

dev.write32(0x10007008, 0x1971) # low-level watchdog kick

File "/home/xubuntu/amonet-mustang/modules/common.py", line 147, in write32

self.check(self.dev.read(2), b'\x00\x01') # arg check

File "/home/xubuntu/amonet-mustang/modules/common.py", line 84, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch

^CException ignored in: <module 'threading' from '/usr/lib/python3.8/threading.py'>

Traceback (most recent call last):

File "/usr/lib/python3.8/threading.py", line 1388, in _shutdown

lock.acquire()

KeyboardInterrupt:

xubuntu@xubuntu:~/amonet-mustang$ ^C

xubuntu@xubuntu:~/amonet-mustang$

Regards
[Fire General] Klerrtery:
Does the short method still work?

I tried for 2.5 hours to enter the bootrom mode without luck.

I tried different wires, aluminium foil, different ground points, usb cables etc.

I'm sure that I'm using the right pin, pointed out in post #22.

As long as the short is applied, it wont show any new USB devices in dmesg.

When I remove the short while the USB cable is plugged in, it immediately shows up as "Preloader".

Is it posssible that my fire tablet is from a newer batch where this exploit was fixed? Where do I find the batch number from my fire tablet?
[Fire General] xdauser1101:
I reinstalled the rom and did not run the finalize.zip. It removes the ota software. Instead i used sdmaid to disable the ota software. I was able to register without issues and keep root. The docs app is also working.
[Fire General] JokkerUCF:
recovery bootloop

i have this tablet, the problem is when power on, go to recovery and it is constantly restarted towards the recovery and from there it does not come out
[Fire General] JokkerUCF:
tengo problemas mi tablet me lanza a el recovery siempre alguna solucion ??
[Fire General] wodgey:
English please
[Fire General] DB126:
Use/retry the procedure in the first post to revive your tablet
[Fire General] JokkerUCF:
the problem

I really have not put the TWRP on my device what happened was that it turned off and then performs a bootloop to the recovery directly, I do not know what to do I will put a shared photo in mega.

https://mega.nz/file/PgNykS4R#wjPPduwp52kXX7eB4N_pMdWz84B2BLI8-R3HorVSLyE
[Fire General] dmfranco:
error in step 8

I am getting this error when i run the sudo ./bootrom-step.sh

Waiting for bootrom

[2020-05-17 05:24:44.169459] Found port = /dev/ttyACM0

[2020-05-17 05:24:44.169924] Handshake

* * * If you have a short attached, remove it now * * *

* * * Press Enter to continue * * *

[2020-05-17 05:24:54.189423] Init crypto engine

[2020-05-17 05:24:54.204365] Disable caches

[2020-05-17 05:24:54.204887] Disable bootrom range checks

[2020-05-17 05:24:54.219459] Load payload from ../brom-payload/build/payload.bin = 0x46B8 bytes

[2020-05-17 05:24:54.225285] Send payload

[2020-05-17 05:24:54.826115] Let's rock

[2020-05-17 05:24:54.826787] Wait for the payload to come online...

[2020-05-17 05:24:55.558720] all good

[2020-05-17 05:24:55.559356] Check GPT

Traceback (most recent call last):

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

main()

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

switch_user(dev)

File "main.py", line 54, in switch_user

block = dev.emmc_read(0)

File "/home/lubuntu/Downloads/amonet-mustang/modules/common.py", line 180, in emmc_read

raise RuntimeError("read fail")

RuntimeError: read fail

someone can help me on this issue?
[Fire General] dmfranco:
hardware method

Could someone make a video explaining how I need to do the hardaware method? I am not knowing how to run it.