yashsingh1/xdaforums huggingface dataset:
[Fire General] Michajin:
I haven't heard of anything. The bootrom got disabled pretty early after it's release.
[Fire General] zefme:
Hi,

I have some Fire 7 9th gen (mustang) tablets here.

They have fireOS 6.3.1.5

That version theoretically can be downgraded to 6..3.1.2 where the software method of installing twrp via mtk-su should be possible, right?

But when I reboot to recovery, there is no option "flash a recovery image from the ADB"

Is that loophole closed on that device, or am I doing something wrong?

Thank you for any advice!
[Fire General] PRInCEI7:
Downgrade succeeded

Fire 7 (9th Generation)​

FireOS 7 | FireOS 7.3.2.2

and activated the test point, the method works on some devices, not everyone, by the way, I used a tool UFI BOX
[Fire General] zefme:
Wow, sounds exciting !

What exactly has to be done?

Thanks!
[Fire General] darlynmr:
I have tried the hardware method and followed the steps to the letter but I think I have damaged the tablet instead of entering bootrom mode, has it ever happened? I leave image for reference:
[Fire General] burgerdood:
In the initial instructions the following is included

1. Back up whatever important data you have on the device and perform a complete factory reset of the tablet. When going through the initial setup, don't connect to a network (see below on how to do that).

I have read through this and have not seen where this is addressed. I have done factory reset, it asks for language and now to connect to a network - how do I proceed to enable developer mode etc to continue with the software option?

Thanks
[Fire General] zefme:
Just select any network which is available for you, and enter some random (wrong) password.

After that there should be a [Skip] button available.
[Fire General] fleisch80:
Hi everyone.

I just wanted to help everyone whos having problems with this tablet when trying to unlock and flash .

If you purchased the fire 7 gen 9 model after 2021 , your hardware is locked down and you can't do anything with it .

I have found complete evidence to this effect .

While in adb fastboot , I executed the adb boot loader unlock command and it spit out this

statement .

Cannot unlock boot loader on this device , it is hardware locked .

Also , I used some other adb windows tools and in fact it told me my unit was

produced in 2022 .

There you have it folks .

This device is not the same device that was being made 2 years ago .

Its only the same in name . every thing is hardware locked down tighter than

a seventeen year old nymph on prom night .

It's more than them just disabling the hardware , they changed the production of

how it was being made .

C.f.
[Fire General] fleisch80:
YOU OWE ME SOME MONEY AMAZON !
[Fire General] fleisch80:
I just wanted to post this .

I think its extremely underhanded and nasty as to what Amazon is now doing .

There taking the same product that went out in production , like the fire tablet 7 gen 9 ,

and changing all newly produced units to have the hardware and bootloader locked .

What this means is if you bought the same model in 2019 , it wasn't hardware locked .

If you bought it in 2021 , 2022 , the hardware is locked .

There pulling a bait and switch and its not right .

Until someone can find out a trick to get around that , were toast .
[Fire General] Michajin:
It was actually a mediatek exploit that got it unlocked. This device was released with the mtk-su working as it worked on most devices at the time (also a mediatek exploit). The SoC was changed to have the bootrom access blocked on the chip. Amazon couldn't fix the problem. This was actually locked out the same time as every other amazon device (early jan 2020 like the HD8, HD10, and i think the 4k). Amazon has no agenda to ever release a unlockable device and usually patches root exploits pretty fast. You can check out the Karnak (HD8) unlock about march of 2020 and see that it was being identified that mediatek fixed the bootrom access exploit.
[Fire General] fleisch80:
Hi friend .

I was wondering , for the older model 7 gen 9 units made in 2019 that weren't

boot loader locked down , if Amazon was to hit it with an update can they in fact

lock the unit down just by an update .

Do you think its possible that another exploit can undo their hardware lock some day or

is there more to it than that .
[Fire General] Michajin:
It wasn't a update that blocked the bootrom access. The shorting method would still work on any of those 2019 mustangs. The software update just blocked root access (mtk-su) which made getting to the bootrom easier. I see the fire stick 3 was recently unlocked, so exploits are still be found. The mustang wasn't a big seller, I would be surprised if this gets anywhere further now.
[Fire General] fleisch80:
Why they call the 2019 model now made differently , the same model

When its a different locked down version .

Sounds like bait and switch to me 😑
[Fire General] fleisch80:
Is it at all possible to regain bootloader access to unlock now,

or is it curtains as long as its hardware locked with flags .
[Fire General] zippzYT:
probably broke a cable
[Fire General] zippzYT:
can anything be done with a fire tablet updated to fireOS 7.3.2.2
[Fire General] stupid_questions:
Lineage OS or Nexus OS

I would like to install a custom rom to a 2019 fire 7 tablet. Amazon can not be trusted and I would prefer to use open source software like lineage os. Is there a custom OS avaible like the ones for the fire 7 2017 tablets?
[Fire General] k4y0z:
New TWRP for mustang (with backup-support) is now available: https://xdaforums.com/amazon-fire/orig-development/recovery-twrp-touch-recovery-fire-7-t3949114
[Fire General] wodgey:
I'm here looking for exactly the same thing.

My guess is that currently the answer is "no custom ROM is available currently"

I'll keep my fingers crossed
[Fire General] Gumann:
Completely utterly hard-bricked?

So....

I tried the software methode, but the screen went black on "Waiting for the bootrom"

Then I opened the tablet and shorted the point mentioned in the thread. My PC doesn't show anything connected at all.

Then I dis- and reconnected the battery but still nothing.

Did I brick my device? Was only 35 € but still a bummer
[Fire General] Dan_firehd:
No, you did not brick your device.

The screen went black after issuing the "reboot" command in step 6(a) of OP.

Since the script is stuck at "Waiting for the bootrom..", one should disconnect the tablet from the PC and proceed to remove the back-cover, followed by disconnecting the battery.

With the battery disconnected, one then plugs the tablet back into PC. One should hear the USB-device-connecting-to-PC sound. Then the "Waiting for the bootrom ..." script should continue onward.

At this stage, with the battery disconnected, the tablet is getting its power from PC via USB port.
[Fire General] robojerk:
In a thread for LineageOS 14.1 for the Fire HD 8, 8th gen [Karnak] the dev says he'll work on a ROM for the Fire 7, 9th Gen [Mustang] as the hardware is very, very similar. I believe he said that on July 16th (a whole 2 days ago) so fingers crossed.
[Fire General] wodgey:
I knew it wouldn't take long. I'll have a read of that thread you mention
[Fire General] delgada89:
Please explain how to pop the heatshield. Not immediately obvious. Thanks!
[Fire General] wodgey:
I've followed the procedure and I sucessfully have a rooted mustang! YAY!!!

I have installed the google play store, framework and libraries etc and have installed Nova Launcher.

My question ---- How do I set Nova Launcher to be the default launcher? The releavent section in the settings app will only allow me to see default browser (currently Silk) and "links" (which is empty)???

edit2add

Nevermind. I have found the LauncherHijack app and that has allowed me to acchieve my needs
[Fire General] AmznUser444 Dev:
Where's the source code of amonet-mustang exploit file?
[Fire General] Dan_firehd:
Sorry for the following dumb question:

I have successfully installed the TWRP recovery and updated TWRP to version 3.3.1-0 by following the link below :

https://xdaforums.com/amazon-fire/orig-development/recovery-twrp-touch-recovery-fire-7-t3949114

Every time after I wipe the system+data+cache clean and perform a complete fresh re-install of Amazon OS 6.3.1.2 (per steps 14 ~ 20 of the OP, as shown in the quote above), do I have to repeat Step 21 ?

What is the purpose of flashing the "finalize.zip"?
[Fire General] k4y0z:
It removes some amazon apps, like OTA and recovery-from-boot:

ui_print "Remove OTA apps"
rm -rf /system/priv-app/DeviceSoftwareOTA
rm -rf /system/priv-app/DeviceSoftwareOTAContracts
rm -rf /system/priv-app/DeviceSoftwareOTAIdleOverride
rm -rf /system/priv-app/com.amazon.kindle.otter.oobe.forced.ota
# Not sure what this does but it spams logcat with errors so off it goes
rm -rf /system/priv-app/com.amazon.precog

ui_print "Remove recovery-from-boot.p"
rm -f /system/recovery-from-boot.p

You could also do that manually.
[Fire General] Dan_firehd:
recovery-from-boot.p

Thank you for the reply.

May I ask, where does the file "recovery-from-boot.p" come from and what is it for ?

Thank you again for all your efforts to help everyone here.
[Fire General] Gumann:
Worked! Yay!

But when do I reconnect the battery?
[Fire General] k4y0z:
it is used by install-recovery.sh to flash recovery.

It is removed here to prevent TWRP from being overwritten, although this is actually not necessary, since install-recovery.sh will fail anyway because of the patched boot.img

As soon as bootrom-step.sh has completed you can reconnect the battery.
[Fire General] Gumann:
fastboot not found

+++UPDATE+++

Me dumbass didn't install fastboot.

bootrom completed, device shows amazon logo.

Now ive opened a terminal at amonet-mustang, but as soon as try running the fastboot script, the terminal immediately returns

line 5: fastboot: command not found

---------- Post added at 05:42 PM ---------- Previous post was at 05:03 PM ----------

How do I get Google apps onto it?
[Fire General] Dan_firehd:
In order to install Google apps, follow the instruction in this link:

https://xdaforums.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603

---------- Post added at 07:30 PM ---------- Previous post was at 07:23 PM ----------

Removing /system/priv-app/DeviceSoftwareContracts seems to cause the following problems:

(1). Amazon app "Docs" will not launch -- screen just flashes and returns back to prior.

(2). Settings --> Device Options --> System Updates will show blank and closes back to prior screen

(3). Settings --> Device Options --> Date & time will not allow the selection of "Select time zone" -- screen just flashes and returns back to prior.
[Fire General] Gumann:
It's stuck in an infinite loop

Basically whenever I try to log into my Google account it reverts right back onto the Google login screen. I've also tried flashing gapps. Same thing

Any fix?
[Fire General] Dan_firehd:
I created a new Google account and I did not encounter any problem at all. Not sure what causes your problem.

I wonder whether it has anything to do with the removal of /system/priv-app/DeviceSoftwareContracts . I did not flash "finalize.zip". Instead, I performed the task manually and skipped the removal of "DeviceSoftwareContracts".
[Fire General] Michajin:
A better one is to disable the stock amazon launcher. install a package disabler, you can remove bloat too. Search what is safe to disable beyond that, but if you have another launcher installed you are safe to remove the amazon launcher.
[Fire General] fleisch80:
Everyone is still wondering if older units that are now on firmware 7.3.2 could in theory

be patched by updates and become hardware locked . what is known is that

if you purchased yours new after 2021 , most likely your bootloader hardware locked .

I think they do have that capability ,

To take an older bootloader unlocked unit running stock ,and send new updates to it to lock it down. As long as it still was not unlocked yet or the os changed .

I just talked to an Amazon tech manager and according to them ,

Amazon does not feel that the customer should have the final say on what their own

property can and can't do . or even that the customer should have the right to block

updates that are intrusive and evasive .

when I test commands for mustang 2021 version , in adb fast boot I use the flash and

unlock commands , it actually returns a message saying this bootloader is hardware locked

and you cannot unlock this unit .

If you also try to sneakily send twrp recovery with using the fast boot method ,

It also says forbidden and blocked on locked hardware .

seems to me while looking in fast boot mode ,

They locked it down now tighter than a 17 year old girl on prom night .

Were screwed
[Fire General] fleisch80:
My advise is if your tab was made or bought before 2021 , its worth trying .

Before having to open it up ,

Try using adb fastboot mode ,

Use the fastboot bootloader unlock command ,

If you don't get a message saying unit is hardware locked , usually its a sign that the

hardware unlock will work . if you get message saying device is hardware locked , you can't

unlock , then your screwed .

while searching on Google , search adb fastboot .

you need the fast boot drivers , the command to boot into adb fast boot mode on your device , and the commands to show status of bootloader lock .
[Fire General] fleisch80:
Basically , yea .if you bought yours after 2021 , your screwed because it shipped hardware locked . unless your the CIA , there's usually no civilian method to undo hardware lock.

Its different from older units being made and shipped with just bootloader status

not modified .
[Fire General] fleisch80:
It's possible . remember for all units made after 2021 , there's no access to bootloader mode. I also think this means they changed the units circuitry .

I blew out one myself before I read up on mustangs being locked after 2021

production.

Only thing you can try is to open up again and pull the battery connector .

Put it back , see if it restarts.

If it don't , its done for .
[Fire General] Tommo1992:
Fire 7 (9TH Gen)

Fire OS: 7.3.2.2

Build Number: 0022247240580

Tried to Sideload the older build but guessing thats no longer an option?

C:\Users\Thomas\Downloads>adb sideload update-kindle-NS6312_user_1827_0002517050244.bin
adb: sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
[Fire General] fleisch80:
Your right . the adb method will also fail for flashing and unlocking if

the unit is under full hardware lock .

Just like the other method to unlock .

What I wonder friend is what exactly is the hardware lock made of.

Is it a removed or unfinished resister lead that would originally go to the

Chip , or is it a completely redesigned chip with just a package

made without any flash capabilities .
[Fire General] 789mod:
In 7.3.2 .2

At recovery not available ( able update from adb )

How you do that ??
[Fire General] fleisch80:
You probably have a unit made after original 2019 production run.

These units were still mustang 2019 model , but were made with a locked

Bootloader.

Any unit made after 2021 has a locked bootloader.
[Fire General] 789mod:
Have you any way to root it ?
[Fire General] fleisch80:
No. Its locked down and heavily protected specifically to not allow it , if in fact

You have the 2021 or newer mustang version. That's why so many people are vowing to never buy a new Amazon product again, because their business practices are becoming

extremely nasty and anti customer/ user. Amazon stated they will no longer sell

a product that can be rooted or modded. Makes you wonder what other spying software is

on these tablets now , that Amazon builts into it.
[Fire General] fleisch80:
It watches what you install on the device .
[Fire General] 789mod:
What is the source of your statement?
[Fire General] fleisch80:
If you attempt to install custom launch menu , it will block it.

It can only do that if it also knows what you are doing .
[Fire General] fleisch80:
How much it watches is unknown , but it certainly is doing intrusive things .
[Fire General] perez6991:
I wish I would've read the last few pages of this thread before attempting the guide. Spent hours trying to get around the "Serial Protocol Mismatch" only to read the last posts saying any Fire 7 from ~2021 onwards is bootloader locked. This kinda makes me want to return the tablet, FireOS is an abomination.
[Fire General] klamation:
I doubt it's any worse than what Google includes on their devices, tracks when you use their sites, or drops on your computer when you install the Chrome browser.

Every company does it. It's just a matter of, whom do you want to give your information to?
[Fire General] klamation:
FireOS isn't terrible, if you recognise it for what it is - a platform for consuming Amazon's media. However, if you want a generic Android experience, it leaves much to be desired.

It's still possible to sideload apps on a locked down device, but if you really want a pure Android experience, you'll want to look elsewhere. It's hard to find decent entry-level tablets these days without looking to Samsung or other third party companies with limited support.
[Fire General] k8500:
Is there some definite way to tell this will not or will work on my device? I recently got one cheap, according to the seller it was originally purchased in April 2020 so I figured there may be hope.

Now, if I get the correct point via the hw method (at least I assume I do), the device is simply not recognized at all (as confirmed by dmesg and lsusb), and the bootrom-step.sh script doesn't do anything either (without the point shorted, I get an exception).

Mainboard also looks a bit different from what I saw in the photo provided by @ggow , so this may be, in fact, the later hw revision :/.
[Fire General] klamation:
I never had to disassemble mine, as it was old enough that it took the ROM through a software install. Does yours boot up? What does its settings/status page say the device and FireOS versions are?
[Fire General] k8500:
I can properly check tomorrow, but Fire OS version is > 7, meaning mtk-su won't work (even the download site says so). The hw way is the only option. And the mainboard has different chips than the unit posted by ggow, so...
[Fire General] klamation:
Yeah, it sounds like yours is the newer model that won't support a custom ROM.
[Fire General] User8395:
What does "Failed critical init step 3" mean?
[Fire General] teetee1:
It probably means your Fire HD 7 currently has OS version v7.3.xx which is not supported by mtk-su. I am on the same boat. Got the table for $15 just for converting to android but I can't even disable the bloatware because becoming root is the first step.

Has anyone with v7.3.xx tried the hardware jumper method and gain root?
[Fire General] 789mod:
Hi friend I buy the method from you 50$ to convert to android
[Fire General] SPanza:
I really want to give these instructions a shot. I know this is an old thread, I have had this fire 7 9th generation sitting around for 3 years waiting to be turned on. What I can't figure out despite really trying and searching xda and beyond is where this "Mustang" designation comes from. I feel confident that's what my fire 7 is or has, but I can't find an explanation from XDA or beyond or an indicator on the device that shows this "Mustang". a link or a short explanation will be much appreciated
[Fire General] thepeck:
Apologies if this is an inappropriate question for this thread but the other seems dead.

I recently rooted a fire 7 2017 and installed lineage os as per instructions on thread (https://xdaforums.com/t/rom-unlocked-ford-austin-lineage-14-1-05-feb-2022.3962457).

Can anyone advise me on how to correctly use forcedoze and kernel auditor (to prevent battery drain when asleep). Unfortunately there is no help on the other thread.

I noticed a battery drain issue and within the thread found further info. I've installed forcedoze. I then found further instructions (though here not very clear) to install Kernel Auditor and run the installed scripts after start up. It's not fixed my battery drain issue. Had anyone here encountered and solved this issue?

Also performance is poor with the os regurally very slow of freezing. Advise on that would to be appreciated.

Thanks
[Fire General] thepeck:
Wrong thread, can't delete, sorry
[Fire General] Kamian.Fire:
I want to unlock my bootloader. I own a amazon fire 7 2019. There is no OEM unlocking feature in developer option. What should i do ?
[Fire General] fleisch80:
Hello.

When did you purchase your fire 7 2019 model ?

I ask because the only 2019 aka mustang versions that can be rooted , unlocked , and flashed are the first production runs sold around 2019.

After that first batch sold , starting in early 2020 and on ,

The BOOTLOADER AND CHIP are HARDWARE locked .

Theres nothing you can do at all to modify anything on it if yours was bought after

2019.

I know they say its the same model , and technically it is ,

Its just that they secretly modified the hardware and started selling it with everything locked down after the initial 2019 models .

as for modding it by opening it ,

That won't work either if its made starting in 2020. Nothing will.

Sorry for the news .

I actually have 2 of those models also and its sucks.

With that model , your only chance is if its absolutely , 100 percent made beginning of 2019 .no later . if it is one of those , follow the forum guide for that model.

Look for the fire tool , its called fire debloat tool,

Will make that model run slightly faster however Amazon still has most of its control over it

and from time to time updates will force you to run the debloat tool again .

For fire tablets to unlock , mod , and flash ,

I would say you can't go wrong with a fire 7 GEN 5 , or GEN 7 .

Their dirt cheap used , but really run pretty fast after you unlock and flash them.

Even better than the crappy newer model 7 , gen 9 .

Dont give up , get another fire and you'll be able to mod it .

Peace.
[Fire General] Kamian.Fire:
I don't remember it clearly. But it was like the starting of 2021. 🙏🏻
[Fire General] fleisch80:
sorry friend . for the fire tablet 7 gen 9 , aka mustang ,

a unit made in 2021 is 100 percent locked.

i know it sucks and i even had multiple fights on the phone with amazon

reps . they have a really nasty attitude and feel that they can change

the firmware and hardware anytime they want , lock it down ,

and lie about it while still try to say its the same exact model.

in my book they should be sued big time for

misrepresenting their products , and performing a bait and switch on people. in the past when you bought a fire tablet you knew

it was worth so much and capable of an equal amount.

now they are purposely giving the customer a unit that is far more

inferior and they are saying that it is still the same model as before.

its just not right .
[Fire General] fleisch80:
1 more thing , its 100 percent locked in hardware and the chip too ,

not only in firmware . for those units made after 2019 , for that model .