yashsingh1/xdaforums huggingface dataset:
[Fire General] MarcLmao:
hey guys, i want to know if my fire 7 2019 is compatible with this, ive heard alot of talk about it not being supported on units bought >2020

I bought mine on Sept 8 2019. but ive been trying to get it into bootrom mode for a while with the hardware method, with a piece of alluminium foil. but nothing is working, what should i do?

edit:

i got into it but the script returns this

[marcus@fedora amonet-mustang]$ sudo ./bootrom-step.sh

[2022-12-11 18:38:53.643964] Waiting for bootrom

[2022-12-11 18:38:59.200003] Found port = /dev/ttyACM0

[2022-12-11 18:38:59.253676] Handshake

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

* * * Press Enter to continue * * *

Traceback (most recent call last):

File "/home/marcus/Downloads/amonet-mustang/modules/main.py", line 161, in <module>

main()

File "/home/marcus/Downloads/amonet-mustang/modules/main.py", line 82, in main

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

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

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

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

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

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch
[Fire General] Michajin:
That is only the preloader. You are looking for bootrom. if you run lsusb in linux it should show up as a MediaTek Inc. MT6227 phone if you are in the bootrom. What OS are you on? Something that might work, on the hd10 i had to disconnect the battery to get it to go into bootrom, then plug it in to run the exploit.
[Fire General] fleisch80:
to be honest , the fire 7 gen 9 is extremely picky even in the models that were pre 2020 ,

and were able to be flashed .

i reccomend you get a fire 7 5th gen , or fire 7 , 7 gen .

the fire 7 gen 7 , runs absolutely fast once its unlocked , flashed , and custom rom

installed.

best part is most people sell those on ebay for only 15.00 many times including

shipping.

i know its fustrating , millions of people bought the 2019 models , or even worse

thought they were the same exact 2019 models only to find out they were

the same model number but locked down in hardware.

amazon feels that they have that right to be deceptive when it comes to right of

modifications and terms of ownership ,

the worst thing is at any time while you are using their tablets ,

if your not already unlocked and flashed off of their software they

are constantly looking for new ways to send out new firmware and software updates that

in theory have the potential to fully lock your device so you can not unlock it or flash it.

idk , in my book that constitutes legal action against amazon .

if i buy a device and it works one way yesterday , i want it to be able to

have those exact same functions in a year from now .
[Fire General] fleisch80:
its even worse than that. if it was made after the 2019 models ,

its hardware locked on the chip level even besides the nastiness of what they did on the

software side. amazon just isnt fair .
[Fire General] MarcLmao:
On FireOS 7.xx and ubuntu 2204, its showing as the preloader, even with the battery disabled,

EDIT: It shows as the "phone" on lsusb now using the point on the back, but te script wont detect it
[Fire General] Michajin:
Try using fire iso, for setup. If you see phone you can totally unlock it. It's all set up

Releases · amonet-kamakiri/fireiso

ISO with patched kernel for kamakiri and amonet. Contribute to amonet-kamakiri/fireiso development by creating an account on GitHub.

github.com
[Fire General] fleisch80:
Your not alone in the last few Ubuntu releases not playing well with the

Linux files for the flashing .

I've also had sporattic issues too with the last 2 main releases of Ubuntu .

I can't remember exactly how many versions back didn't give me issues.

To be honest though its been a few months since I unlocked and flashed

so for all I know , most errors could be ok now .

I know the versions that coinsided , that were Linux mint usually gave me

less trouble though .
[Fire General] ForForkSake:
Hardware method Worked perfectly in latest Kububtu 22.04

I've managed to boot into twrp. But have 1% battery so better give it some juice before I get flashing :LOL:

The firmware link is working - tried once or twice before and it failed.

As soon as it downloaded this time I got into action.

The short it really easy and only took me a few attempts

Thank you!!

Edit: enough battery to downgrade succesfully.

install latest magisk canary & finalize.zip

woop
[Fire General] ForForkSake:
This happened to me.. It was when I had incorrectly install pyserial when you actually need pytbon3-serial

I then changed USB port and voila.
[Fire General] ForForkSake:
Yes. Easy to follow guide.
[Fire General] Ch Tech:
when i execute mtk-su i have this output : "failed critical init step 3" how i can solve this?
[Fire General] Michajin:
you cant unless yours was pre 2020.
[Fire General] muzicman82:
I've been on Lineage 16 (whatever the latest is) and WiFI keeps crapping out constantly. I've heard this is a common issue.

Is there a flashable stock ROM with root so I don't lose root?
[Fire General] coolst3r:
when i try to run boot tom sh on original austin it also stuck at handshake

b''

b'\x00\x01'

Traceback (most recent call last):

File "/home/cunny/Downloads/amonet/modules/main.py", line 130, in <module>

main()

File "/home/cunny/Downloads/amonet/modules/main.py", line 64, in main

handshake(dev)

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

dev.write32(0x10007000, 0x22000000)

File "/home/cunny/Downloads/amonet/modules/common.py", line 152, in write32

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

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/home/cunny/Downloads/amonet/modules/common.py", line 89, in check

raise RuntimeError("ERROR: Serial protocol mismatch")
[Fire General] Michajin:
you are in preloader not bootrom
[Fire General] turboTermite:
was it hard opening it up?
[Fire General] turboTermite:
nvm it's super easy to pop off :P
[Fire General] MarvinMod:
when i try the hardware, it stays on waiting for bootrom while i have the pin grounded. nothing else happens, what am i doing wrong? @ggow
[Fire General] turboTermite:
lol i combed this thread a lot over the years before i flashed mine, because i was chicken opening up.

From what I read you need a one from the early batches, because Amazon locked it down late 2019. Probably hard to tell which one you got other than going off by purchase date. I remember when I got mine I prob could of done the software flash, but I was dumb and didn't know how to go past the first boot up screen and connected it to the internet and it updated it self.....

Are you getting a good connection when you are grounding the pin? Mine was like way tiny compared to the picture, like there's nothing sticking out like that one picture that shows you how to do it. Are you grounding it to the leftover shield piece that surrounds it?

Anyways hope it works for you, it would be kinda nice to have more people interested in this.
[Fire General] MarvinMod:
Mine was purchased new in 2021 and has fire 7. Something on it. The pin is very small yes and if i keep it grounded, it stay at waiting for bootrom but as soon as i realease the short, it starts to go but ends with port protocal mismatch or something like that. I disconnect battery and try again with same results. Ive been reading alot of threds talking about the patch being fixed on newer devices but no ones actually confirmed it as you are right, theres no way to tell if you have a pre 2019 or not or at least i haven't been able to confirm that from the tablet but again, i did get it in 2021. I have several tablets, this ones not important to me so ill keep tinkering till i find a way to unlock it or break it lol. Thanks for the reply. 🖖
[Fire General] Michajin:
In Jan 2020 the bootrom was disabled, you can also tell by the serial number. Anything that was purchased from amazon after march of 2020 had the bootrom disabled. You can only get into the preloader. There may be a rooting option with it having a mali GPU, but i cant confirm anyone is working on it or it will work on this, and this will likely be root only.
[Fire General] Crazycat070:
Tried the hardware method on mine and it said something like incorrect serial and now it wont power on anymore. Anybody know how to fix this issue or can i not use it anymore?

Edit: I just shorted it again and it turned on
[Fire General] cyb222:
I have tried on many distros and i keep getting to preloader instead of bootrom. Can anybody help
[Fire General] klamation:
You'll need to provide more information on what's going on. First, there's not a lot of distros for this device - only one by ggow, that I've seen. Second, only specific Mustang Kindle Fire's can be modified. When did you buy yours and what OS is currently on it?
[Fire General] fleisch80:
i have some info for many wanting to know specifically why the unlocking thing is such a big issue .

Most of the amazon devices have a MediaTek chip , and also many ,many cell phones use these similar chips which are also MediaTek .

the way the device unlocking worked was by an exploit that was developed not only used to unlock MediaTek devices, but it was well known that similar methods were compromising the security of millions of cell phones by hackers who also knew how to exploit the same code in secret to take control over unsuspected people and their devices , those who had MediTek chip run cell phones.

this became the elephant in the room because the government put pressure on all device manufacturers to secure and close the security loophole in which the MediTek exploit worked ,

however the more it was talked about in the media and internet , the more people were even more interested in finding ways to do such unlocking and device exploits.

this is why "A" now hard locks most of its devices now.

the last 2 years the Government had a mandate requiring almost all device makers to secure the MediaTek exploit .

its less an issue of why are they purposely doing this to our device modding groups ,

it was found to be a national security high level threat to allow MediaTek devices

to continue to keep that vulnerability exploit open.

it works both ways , yes its great for flashing and unlocking , however

very similar exploits using hacker code based on the MediaTek exploit, and vulnerabilities

were used almost without anyone knowing that millions and millions were '

unknowingly getting hacked , surveilled , and more by this

exploit vulnerability.

Nobody within this device community wants anybody to be harmed due to any

remaining loopholes in a S.O.C. , system on a chip or its flaws in security .

companies had no choice but to hardware lock and patch the vulnerability that allowed unlocking and flashing.

Do i agree 100 percent with this , no ,

however i also don't want anyone to inadvertently be harmed due to the MediaTek exploit that allowed many unwanted things to occur ( outside and aside from just unlocking and flashing )
[Fire General] cyb222:
bought mine december 2019, i tried the contacts on the board but it keeps going to mtk preloader

It looks like it didnt ship with the contacts but they did short but it was just to the preloader
[Fire General] cyb222:
I'll make a tool for it that doesnt root it if anyboady wants the customizations without root, i know Fire Toolbox exists but i want to make my own tool
[Fire General] klamation:
So what version of FireOS is it currently running?
[Fire General] fleisch80:
on the mustangs ?

I think all of them have been force updated to ver 9 os .

Another thing I don't like about it ,

forced updates could put someone on the newest os firmware and os ,

what if you just don't want that , you really have no choice.

basically our devices aren't our devices .
[Fire General] klamation:
I think most people in the XDA community would agree with your complaint, which is why we're here. Sadly, it's a direction that Apple has been heading, and now Microsoft is heading that way as well.

There's some talk in this forum thread about downgrading, but I don't know if the current OS9 can handle that. It sounds like you tried and it doesn't work, so unfortunately I suspect you're stuck. Maybe you can sideload the Google Play store onto the device, but that's probably it.
[Fire General] fleisch80:
Yea . I even noticed lately some of the fire tools can't completely disable system

components like prime video app , etc .

After a few days now its right back on the home screen .

In the past I've used no root VPN to block them from update access , but

the whole thing gets played out .

I'm just glad that mostly , I don't need any x64 arm based tablets.

mostly any older 32 arm like fire 7 , gen 5 or 7 is usually ok for me still ,

especially since their flashed and unlocked .

Even the mustang gen 9 has hardware limitations within x64 arm .

why they chose to make it like that. i.d.k.
[Fire General] cyb222:
Latest, the lastest has probably bricked it because it won't come one

It gets warm but then it won't turn on
[Fire General] cyb222:
With fireOS 9 i think it installed on mine and i think it bricked it : 0
[Fire General] klamation:
According to Amazon, the latest FireOS release for the 2019 Fire7 tablet was FireOS7, not 9: https://developer.amazon.com/docs/f...pecifications-fire-models.html?v=firehd7_2019

If your device was somehow bricked through installing Amazon's updates, I would suggest contacting Amazon support. They might be able to help with it. Otherwise, you could always do the trade-in to get credit towards a new device, if you wanted to stay with their systems.
[Fire General] fleisch80:
this is another reason why companies should have no right to send intrusive updates , to device owners who dont want to allow the updates.

even worse , they dont want to mention exactly what revision or changes the updates are

doing to the device.
[Fire General] fleisch80:
the united states seems only to protect rich big companies rights ,and not

individual rights with respect to ownership and freedom of choice of what we buy

and how we choose to use it , or not allow certain code to be manipulated into it .
[Fire General] fleisch80:
this subjuct is a dead horse though .

companies know it takes money to fight .
[Fire General] fleisch80:
I have to reiterate a statement that I posted about fire tab updates.

I didn't mean to imply that what's going on for one specific model of fire tabs is the holy grail for every single one.

I mis spoke and I thank the other fellow senior member for pointing that out .

everyone have a great day.
[Fire General] ForForkSake:
Can confirm this isn't the case for fire hd 7 12th Gen

successfully have google play and everything amazon removed, no forced updates, never had root either...

there must be something you are missing
[Fire General] fleisch80:
Im not denying that your 100 about your device model.

I think they have different variations of the updates depending on how old the device is , when the

update will specifically change that device characteristics and other factors.

I know the updates for the gen 9 have been doing some malicious changes but no im not trying to say thats for every device.

your right on pointing that out .
[Fire General] ForForkSake:
had no end of problems after installing magisk canary 26104.

Was working fine on 26102 aswell.

amonet to the rescue again :love:
[Fire General] itsjake100:
I got this error. Im running the latest version of Linux Mint

[2023-07-25 04:12:14.548926] Waiting for bootrom

[2023-07-25 04:12:56.202743] Found port = /dev/ttyACM0

[2023-07-25 04:12:56.241493] Handshake

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

* * * Press Enter to continue * * *

Traceback (most recent call last):

File "/home/faggyboi/Downloads/amonet-mustang/modules/main.py", line 161, in <module>

main()

File "/home/faggyboi/Downloads/amonet-mustang/modules/main.py", line 82, in main

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

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

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

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

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

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

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch

What should I do about this. Note: I'm a noobie at this stuff
[Fire General] nihiLichen:
RIP, this completely killed my tablet. Kept throwing the "Serial protocol mismatch" errors so I chose to keep trying and now the device simply doesn't do anything. Heard a weird click and that was the end of it, I suppose that's Amazon fighting back + I only just realised this never would work since I have a newer revision with the nanya chips. :/
[Fire General] krazy006:
Does this also hold true for a Fire HDX 7" prior 2019 (3rd gen)
[Fire General] Watever44:
My fire 7 was purchased in 2021, meaning it's an updated version.

I understand the software way won't work. But does the hardware way still works ?
[Fire General] seansean23:
I bought a bunch of these for my business but ended up going a different route. I'm currently trying to sell them on Marketplace but no one seems interested. And I don't want to just throw them away. If anybody here could use them send me a message, I'd let them go for whatever shipping costs to your place are. I'd rather get rid of all 14 at once. Send me a message.

I have:

13 x 2019 version, Mustang

1 x 2019 version, Austin
[Fire General] ergonomical69:
Mine is having trouble executing mtk-su. When I execute it, I get "Failed critical init step 3"
[Fire General] dd8zc:
I'm still using LineageOS 14.1-20190827-UNOFFICIAL-mustang

Can someone recommend a better / newer rom?
[Fire General] fleisch80:
your lucky . your mustang must be the very first production run . after the very first production run, they were manufactured locked down .
[Fire General] israel659:
Hello, I have a question, is Linux necessary?

You can't do it with Windows?
[Fire General] fleisch80:
usually these things are only written for linux.

i will say that for the 2019 mustang model, keep in mind that

if you have one and it was any production run made after the first initial 2019 release , its hardware locked 100 percent, and you cant do anything with it .
[Fire General] fleisch80:
that means only the first released units shipped beginning of 2019 can be unlocked and flashed for mustang.
[Fire General] burkettc:
I was given a Fire HD 7 (9th gen) that was flashed with TWRP at some point in time, but then upgraded to 7.x os. It just boot-loops at Amazon logo. Is there a way to recover this thing? I've tried vol up/down + power, nothing. Only disconnecting the battery helps stop it from insanity.

Searched the threads but haven't see a way to recover from this bricked scenario.
[Fire General] Tropics09:
at the waiting for bootrom step, (i went with the short method, shorting clk to a ground point) i get this
[Fire General] uig200:
How can I know whether my kindle fire 7 9. gen was made pre 2020 and check if the hardware method does actually work?

I have heard that somehow it is possible to extract that information from the serial number.

Thanx.
[Fire General] fleisch80:
The simplest way to know is when you attempt the unlock and flash ,

no matter what you do it will not go into flash mode when shorting the wires and running the scripts.

It won't allow anything to be changed.

A more in depth look would be to use Android debugging protocol ,

and at the command prompt there's specific commands to enter that would show you

if your device is hardware locked. It actually will say hardware locked at certain command promps.

I apologize for not giving more in depth details ,

its been a while since I flashed and unlocked fire devices.
[Fire General] uig200:
Hmm, will it not brick my device if the attempt to unlock it fails?
[Fire General] fleisch80:
Absolutely not . if your device is hardware locked , the chip prevents any code from even

being executed. It won't even allow the process to begin.
[Fire General] uig200:
Thank you. I will give it a try

EDIT: Unfortunately, it seems not to be working:

I get low-level watchdog kick at writing payload.bin and

RuntimeError: ERROR: Serial protocol mismatch.

That sucks!
[Fire General] Tropics09:
yep ive tried so many times. must be unlucky and we all have post 2020
[Fire General] Gumann:
So do everything in the script except for DeviceSoftwareContracts?

---------- Post added at 09:50 PM ---------- Previous post was at 09:15 PM ----------

So. I messed around a b

Holy frick. WTF?

---------- Post added at 10:02 PM ---------- Previous post was at 09:50 PM ----------

So apparently something I did worked, because the Play Store and every other Google app works.

So basically I didn't flash the Finalize.zip and did it manually and skipped DeviceContracts.

At first I was stuck in the Google login loop, so I looked it the settings, and I think with Gapps on the device the usual Google option was available. After opening that I was surprised when I was apparently logged into my account, so I switched back to YouTube, Play Store etc. and wouldn't you know it, they run. A bit slow, but they run.
[Fire General] Dan_firehd:
Disable OTA

I find out that just by disabling/removing/renaming the following two files seems sufficient to disable OTA (similar to Amazon OS 5.xxx tablets) :

/system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk

/system/priv-app/com.amazon.kindle.otter.oobe.forced.ota/com.amazon.kindle.otter.oobe.forced.ota.apk

I am not sure about the purpose of these two :

/system/priv-app/DeviceSoftwareOTAContracts

/system/priv-app/DeviceSoftwareOTAIdleOverride

I verify that OTA "seems" disabled by going to

Settings --> Device Options --> System Updates and tapping "CHECK NOW" buttons. The displayed result is : Check for updates failed.
[Fire General] DB126:
Only one file needs to be renamed: DeviceSoftwareOTA.apk
[Fire General] Dan_firehd:
ZRAM=256mb & RAM=902mb

This tablet has ZRAM=256MB & RAM=902MB.

It is faster than Fire7 7th-Gen.

Fire7 7th-Gen has: ZRAM=64MB & RAM=890MB.
[Fire General] DB126:
The ZRAM setting your reference reflects a max value. Whatever amount of ZRAM is in use reduces the amount of available RAM. While there may be subtle reporting differences Ford/Austin/Mustang are all equiped with appx the same amount of physical RAM.
[Fire General] wodgey:
Yeah I'd also thought of doing it this way (I have purchased the licence for Titanium backup in the past, so I know that I could use this to achieve exactly that) but I don't know the name of the Amazon launcher.

I'll try googling "fireos debloat" now and see what I can see
[Fire General] brmpfgl:
Awesome! Thanks, very nice work!

Can anyone recommend a custom rom?
[Fire General] Dan_firehd:
The name of the Amazon launcher is: Home Pages
[Fire General] Michajin:
I use

Package Disabler Pro ( Owner APP) All Android

com.amazon.firelauncher

You can also disable from a shell

adb shell

$ su

# pm disable com.amazon.firelauncher
[Fire General] MontysEvilTwin:
Renaming DeviceSoftwareOTA.apk on its own is enough to prevent OTA updates. On the HD8 (8th gen. Karnak) renaming or deleting DeviceSoftwareOTAContracts.apk prevented Prime Video from working. I've not checked it this is the case with the Mustang.