yashsingh1/xdaforums huggingface dataset:
[Fire General] Rortiz2:
WTF no. 7th gen can be unlocked and rooted. (Also there are ROMS for it: LOS 12.1, AOSP FIRE NEXUS, etc).

https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860
[Fire General] DB126:
Neither are pure hardware. Long pressing the power button on most gizmos engages low level processes that initialize and validate various hardware and software components (eg: signature checks) before handing control off to the operating system (ROM). PCs typically have a hardware chip that is isolated/protected from firmware changes targeting the operating system and kernel (bootloader). Consumer grade mobile devices lack such protection. In most cases the device can be revived by shorting pins on the mainboard followed by a reload of low level firmware. The above is an abstraction of what actually happens ... tech purists will be quick with the red pen ... but good enough to address the question.
[Fire General] donk165:
Aha ! Yeah I did the hardware method just to be sure, but its working, I have lineage 14.1 running on the tablet! OMG!

Thank you for your help, and thank you to the dev for this work!
[Fire General] TheFifthOneToBe:
When I enter ‘sudo ./bootrom-step.sh’ I get an error that says ‘command not found’

I know it’s something simple and I’m an idiot

Edit:

adb appears to be working fine. I disabled ModemManager successfully.

ButI keep getting, error: line 5: cd: modules: No such file or directory

Edit 2: Fixed typo caused by autocorrect
[Fire General] Rortiz2:
It's not "bottom";)

It's

sudo ./bootrom-step.sh
[Fire General] TheFifthOneToBe:
Sorry typo, I was typing in ‘bootrom-step.sh’ Into the console. I posted the comment from mobile so auto correct kicked my ass there
[Fire General] Rortiz2:
Alright so it fails when it tries to go in the modules.

Did you downloaded and extracted ALL the zip?

Regards.
[Fire General] TheFifthOneToBe:
I’ll have to double check once i get out of work but that’s not for another 10 or so hours. Is it alright if I PM you at that time so we don’t bloat up the post?
[Fire General] Rortiz2:
Sure. When you get off PM me if you want;)

Regards.
[Fire General] Nurlan57:
i have a problem in software method :do you have suggestions? os 6.3.1.2

mustang:/ $ cd /data/local/tmp

mustang:/data/local/tmp $ ls

Kinguser.apk encrypt mtk-su su

mustang:/data/local/tmp $ ./mtk-su

Failed critical init step 4

UID: 2000 cap: 0000000000 selinux: enforcing

mustang:/data/local/tmp $ chmod 750 mtk-su

mustang:/data/local/tmp $ ./mtk-su

Failed critical init step 4

UID: 2000 cap: 0000000000 selinux: enforcing

mustang:/data/local/tmp $

give this error
[Fire General] Rortiz2:
Please, don't quote the entire OP..

That error means that mtk-su has been patched on your firmware version.

The only thing that you can do is use the hardware method.

Cheers.
[Fire General] jasonmerc:
I'm new to this tablet here (so pardon the noob question) but I did a bit of reading and I'm halfway convinced I want to get one of these 2019 7 inch fire tablets. It looks like mtk-su has been patched out of the latest software revision, but from what I read, I assume the hardware method is indeed a hardware problem and will work on ANY firmware? If I'm running the latest update when I get mine I want to make sure I'll be able to somehow unlock it and flash AOSP custom ROMs.

Also, one more thing to, are there any custom ROMs for the 2019 variant? The OP mentions them but this is in the OG Fire tablet forum so I'm not sure if they're cross compatible or not.

Thanks in advance!
[Fire General] Rortiz2:
Yes, you will be able to unlock with with hardware method in any sw version.

There's LineageOS 14.1 (Pretty same as AOSP ROM): https://xdaforums.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329

Cheers!
[Fire General] DB126:
You will be much happier with the HD 8, or better yet, Onn 8, for just a few $$ more. Check specs and capabilities before investing hard earned coin.
[Fire General] LastMile:
I've succeded with the hardware method, after my initial attempts at the software method failed.

To update Magisk can I just flash the latest version from topjohnwu/Magisk/releases via TWRP? (sorry, can't post links yet)

Edit: Yes, turns out flashing the latest zip from the topjohnwu's githuib repository works. Now running 20.1
[Fire General] V3N0M_90:
Newbie question.... I've rooted plenty of other devices but only through Windows. I've never used Linux before, in my entire life, so maybe there is just I'm missing.

When I enter the "./mtk-su" command in the shell, I recieve this error message.

"Failed critical init step 4

This platform is not supported"

I'm running Linux Mint 19 from a live USB stick.
[Fire General] angry_goldfish:
Thanks for the info about your experience level and environment. That's helpful!

I suspect maybe you are mistakenly executing mtk-su on your linux system instead of the android device? You should be sending mtk-su to the android device and running it there via and adb shell. A full shell log would be helpful. More info in = more help out.
[Fire General] benmayim:
A one-click rooting app for fire 7 9th gen. OS 6.3.12

I have looked for a rooting app specific to this brand new tablet, found none that work after trying all of them I could find.

I don't want to learn linux, or how to use it's terminal, or use a pc running windows or linux. 1-click Root Techs and support say it doesn't exist yet. I hope someone will make such an app or say in a post here why it's not possible in terms I can understand. Maybe such an app does already exist, and I just haven't found it. If someone knows of such, please post here where the app for the device can be downloaded. I can install a .apk file on my fire, and know enough to enable installation from unknown sources. So, I can run and install any .apk file. Someone pls make one for this device if possible. :good::fingers-crossed::good: Pls also post how I can find any and all replies to this post. I'm not sure how to in this forum.
[Fire General] DB126:
- a self contained 1-click solution does not exist for the device in question (and probably never will)

- securing root is possible but you have to do your homework and use tools that fall outside your comfort zone

- if you don't care for the above best find another device
[Fire General] SumoCat:
Ran into the same problem

1|mustang:/data/local/tmp $ ls
mtk-su
mustang:/data/local/tmp $ chmod 755 mtk-su
mustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform is not supported
[Fire General] AdrianSR20.240SX:
Platform not supported issue?

Also having the same issue.

New to Linux too. Have rooted my G5 and PH-1 on Windows before this.

Using the latest Linux Mint.

terminal reads:

mustang:/ $ cd /data/lcoal/tmp
mustang:/data/local/tmp $ mtk-su
Failed critical init step 4
This platform is not supported
[Fire General] SumoCat:
I ended up doing the hardware setup instead.
[Fire General] AdrianSR20.240SX:
So my understanding is I need to ground that pin to the back board, correct?
[Fire General] SumoCat:
Yea, there is actually a giant spot marked GND near the edge of the board which I used.
[Fire General] timohim:
Thanks for the many advices, but i have one question to the hardware solution:

The process is a little bit unclear to me. I switched the tablet of and bridged for a short time the given point and the big GND point and switched the tablet back on. When can I see, if the bridging of the two points worked?

Maybe somone can write a step-by-step guide to the hardware solution?
[Fire General] YodaDude2011:
You tried executing the mtk-su on your local device instead of going into the device, transferring the script to ut, and executing it from there
[Fire General] diplomatic:
No, he hasn't. That was the correct error message for firmware that is not supported (anymore) by mtk-su. No way would mtk-su even load on your PC. See the Rapid Temporary Root thread for the supported OS versions...
[Fire General] SumoCat:
There is step by step for hardware unlock in the first post. When shorted you should be seeing status messages in the terminal windows specified in the tutorial steps.
[Fire General] Doomwake:
Everything from amazon is blocked. I have a fire recast and amazon prime video

I tired getting play store version and still did not work. is there a way to just unblock these two?

also

https://xdaforums.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329

Lineage rom does not flash for some reason I get a error 7 inb twrp.

If anybody could help out that would be great!

Thanks for all your work. Works great other than what is stated above.
[Fire General] Doomwake:
Lineage is working fine for me. Got it to work have to wipe the whole thing first then push and flash it in twrp
[Fire General] wodgey:
I'm really surpassed that there aren't more custom ROM's on development. It's currently on black Friday sale in the UK for£30.
[Fire General] DB126:
Lineage works fine as an alternative to FireOS. At some point having 2 dozen custom ROMs, often with their own bugs and limited maintainer support, that largely do the same thing is a fool's errand. Yesterday's world is changing.
[Fire General] adamc77:
[deleted cause I'm an idiot and missed the commands after "./mtk-su"]
[Fire General] adamc77:
Since this unlocks the bootloader, does that mean it's possible to change the amazon logo that shows first thing on boot?
[Fire General] ghostdogg49504:
is there another way of doing this on windows 10 it seems complicated and i don't wanna tear it apart i don't like tedious tasks all i want to do is install magisk not go to the moon no offense but i'm a kingoroot type of guy
[Fire General] Michajin:
Taking it apart is easy, It really isn't as tedious as the instructions look, they are just very thorough instructions. There is a live disk here that should make it even easier.... The software is locked up and access to root is in the bootrom so kingo or one click root stuff will not work. Months ago there was a exploit to get temp root, but amazon blocked it.

https://github.com/amonet-kamakiri/fireiso/releases
[Fire General] mcbeat257:
Software Method Fix!

[MENTION=9667509]xyz`[/MENTION] should add this to the post:

As of the time of writing, you can still use the software method on the Fire 7 9th Gen, you just have to downgrade your firmware in order to do it. mtk-su only supports the build number of 0002517050244 -- this is why people are getting the not supported error. Amazon doesn't sign it's build revisions at this time so it is possible to downgrade.

This method will wipe your data. Backups are a must.

Steps to downgrade to get the Software Method to work:

Download the 0002517050244 build revision here: https://fireos-tablet-src.s3.amazonaws.com/.../update-kindle-NS6312_user_1827_0002517050244.bin

Enable USB debugging on your device and developer options

Plug in your device to your PC. Type in "adb reboot recovery" on your PC to go to the recovery screen.

Use the volume up and down icons to scroll to flash a recovery image from the ADB

While in the directory of where the ".bin" file is stored on your PC, type in on your PC "adb sideload update-kindle-NS6312_user_1827_0002517050244.bin"

Wait for the action to finish. DO NOT TURN OFF OR UNPLUG YOUR DEVICE OR IT WILL BRICK.

Once finished, use the volume up/down buttons to go to the factory reset button. Press the power button to select factory reset and confirm to do so.

Once finished, use the volume up/down buttons to reboot the device.

At the Fire setup screen, select your language. On the next screen, Wifi setup, select any password-protected network, then instead of entering the password press "cancel". Now, back at the wifi setup screen, press "Skip setup" and "Skip" in the dialog pop-up again

Wait for the update to finish (wait until the updating fire notification disappears)

Follow the instructions to use the mtk-su software method
[Fire General] Flixie:
Hardbricked?!

Hallo first of all Thank you for this Guide.

SW Methode worked for me on one device.

The second one i tried with hw method. I was Anke to Flash and use Lineage for Dome Minutes. But Fire randomly Shuts down.
[Fire General] RBThompsonV:
So, it looks like they may have patched the ability to reboot into recovery (or im an idiot and im doing something wrong)...

With Developer mode activated, and USB debugging enabled, I get:

adb reboot recovery

error: insufficient permissions for device: user in plugdev group; are your udev rules wrong?

See [http://developer.android.com/tools/device.html] for more information

When trying to reboot to recovery... Any suggestions?

FYI: wife opened the kindle and set it up and took an update to 6.3.1.2 (Build date October 5, 2019 1:31AM)

Which seems like a weird date for an update if yesterday you were saying this downgrade method still works...

Additional Info: I am on Ubuntu 19.10, Kindle was just ordered from amazon... it is the 32GB version and is listed as Fire 7 (Mustang)

---------- Post added at 11:12 AM ---------- Previous post was at 11:07 AM ----------

EDIT: Disregard...

But note: you need to select your USB to transfer files and not just charge to prompt for ADB authorization/trust and then follow the instructions.
[Fire General] Nuggets321:
What custom ROMs are available for this??
[Fire General] youngdaddytc:
had this same problem where all i was getting was 'permission denied' at this same step. left it as is, all plugged in, terminals up, and came back after an hour. decided at that time 'oh why not? i'll go ahead and try to run the commands again.' this time it worked!

so long story short, dont give up just because you see this message at first. trying again after a short waiting period worked for me. currently on Fire 7 2019, 9th generation.

UPDATE: so using these steps I've verified root, used titanium backup to remove every bit of bloatware I can identify, installed nova launcher as the default, and just need to find a good alternative to setcpu which freezes every time I try to use it.

Also, question: is there a good list of which apps can be removed and/or which are essential? The goal of this tablet is to serve as a simple learning device for a 7 year old with maybe a few games if he's good lol.
[Fire General] kn4thx:
Procedure Was Successful But Not Rooted?

Excuse me if I am missing something simple, but I went through the process and everything seemed successful. The problem is I still cannot uninstall any Amazon apps. Do I need a special app or did I miss a step which gives me full privileges?

EDIT: I do have root. Is there a safe list of apps which can be disabled or an app that can be recommended? Any services that can be safely disabled to speed up the tablet?

Thank you
[Fire General] ghostdogg49504:
mtk-su r16 link is dead

tried to download mtk-su r16 but link is dead the only one i found was mtk-su r17

taking it apart is not easy for me and it is hard for me to understand or follow i'm just gonna leave it alone until i got a one click root method or i'll just sell it get my money back and buy a raspberry pi 4 :confused:
[Fire General] mrmazak:
???????

Really strange comments.

Too hard for you to do mods with step by step guide. So you will get a development board, where everything you do you need to come up with the process on your own.
[Fire General] ghostdogg49504:
its easier all i have to do is flash a sdcard with etcher im somewhat computer illiterate and have a hard time following instructions my fragile mind can barely do times tables without a calculator my adhd doesn't help the last grade i completed in school was the 9th grade i kind of wish i could just flash a rom like lineage and erase fire os without root and then root it
[Fire General] garnet2k:
Hi all,

How can I overwrite hosts file?

I run lineage OS with magisk, but it seems it is mounted read only.

Where is it in the first place? /etc/ or /system/etc?
[Fire General] moccor:
Edit: Nvm I am finishing up with making mine work. Some notes though -

If using a virtual machine, make sure to often check the devices to make sure its connected. Alternatively, go with the hardware method to save time if you have to use a virtual machine lol. I ended up having to open mine up anyway to unplug the battery.

Unplugging the battery and connecting it to my PC resulted in Windows recognizing it when stuck at the black screen, but it still wouldn't work in the VM. I unplugged it from my PC, plugged the battery back in and then plugged it back into the PC and the -`sudo ./bootrom-step.sh`. It should print "Waiting for the bootrom". - continued no problem.
[Fire General] Crigges:
So I bought 2 Fire 7. The first one went like a charm with the Hardware method. The second one is stuck in step 11. I can't get it to fastboot. I ran the bootrom-step.sh twice, and both time it there were not errors see the output:

[2019-12-06 08:56:33.741449] Waiting for bootrom
[2019-12-06 08:57:27.993163] Found port = /dev/ttyACM0
[2019-12-06 08:57:27.996709] Handshake

* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *

[2019-12-06 08:57:33.023515] Init crypto engine
[2019-12-06 08:57:33.154909] Disable caches
[2019-12-06 08:57:33.156938] Disable bootrom range checks
[2019-12-06 08:57:33.244496] Load payload from ../brom-payload/build/payload.bin = 0x46B8 bytes
[2019-12-06 08:57:33.246772] Send payload
[2019-12-06 08:57:37.776370] Let's rock
[2019-12-06 08:57:37.779791] Wait for the payload to come online...
[2019-12-06 08:57:38.512340] all good
[2019-12-06 08:57:38.512882] Check GPT
[2019-12-06 08:57:38.861484] gpt_parsed = {'proinfo': (1024, 6144), 'PMT': (7168, 9216), 'kb': (16384, 2048), 'dkb': (18432, 2048), 'lk': (20480, 2048), 'tee1': (22528, 10240), 'tee2': (32768, 10240), 'metadata': (43008, 80896), 'MISC': (123904, 1024), 'reserved': (124928, 16384), 'boot': (141312, 32768), 'recovery': (174080, 40960), 'system': (215040, 6354944), 'vendor': (6569984, 460800), 'cache': (7030784, 1024000), 'userdata': (8054784, 22480863)}
[2019-12-06 08:57:38.861592] Check boot0
[2019-12-06 08:57:39.108925] Check rpmb
[2019-12-06 08:57:39.320607] Downgrade rpmb
[2019-12-06 08:57:39.322688] Recheck rpmb
[2019-12-06 08:57:40.221143] rpmb downgrade ok
[2019-12-06 08:57:40.472052] Clear preloader 1
[1 / 1]
[2019-12-06 08:57:40.495718] Clear preloader 2
[1 / 1]
[2019-12-06 08:57:40.519149] Flash lk-payload
[4 / 4]
[2019-12-06 08:57:40.858407] Flash tz
[5547 / 5547]
[2019-12-06 08:59:45.031114] Flash lk
[651 / 651]
[2019-12-06 08:59:59.838813] Inject microloader
[4 / 4]
[2019-12-06 09:00:00.178224] Flash preloader
[271 / 271]
[2019-12-06 09:00:06.487188] Restore preloader
[8 / 8]
[2019-12-06 09:00:06.668373] Reboot to unlocked fastboot

But the screen stays black, sometimes the amazon logo flashes for like 0.5sec but that happens totally random. Using the fastboot devices command shows no devices. I also tryed pressing and holding buttons, and to remove the battery but no success.
[Fire General] slacka123:
Magisk-v19.3 update?

A warning to others: Magisk has been nagging me to update for awhile now. After giving in, and updating it to 20.1, my device was (soft) bricked. When I rebooted is only displayed the Amazon logo.

I fixed this by booting to TWRP and following the instructions from step 15.

This raises a few questions. Can Magisk 20.1 be used, is there a bug with 20.1 + Kindle 7, or did I do something wrong in my update procedure?

Finally, BIG thanks to [MENTION=9667509]xyz`[/MENTION] [MENTION=8132642]diplomatic[/MENTION] and [MENTION=5854796]mcbeat257[/MENTION] for making this possible!!!!
[Fire General] xyz`:
You cannot install updates from the Magisk app - see in the first post under "VERY IMPORTANT STUFF".
[Fire General] Madmansdeath:
Completed all the steps, everything working etc.

Was just wondering if there was any way to use the kindle app on the device now (fire 7) with it connecting to the amazon account (currently won't let me register the account assumedly to block updates). Would removing all amazon apps and getting them from the play store fix this ?

Edit: Got it working, used fire toolbox to Remove everything amazon, then went to kindle app on playstore clicked enable, then when the register button popped up on the app it actually let me login.

Only app i can't get to work is the docs app, anyone have any ideas ?
[Fire General] leslieliang:
I get a serial protocol mismatch error after the remove short and press enter step. I am using Ubuntu and am using the hardware method, shorting out the location suggested in the first post. I have ensured modem manager is uninstalled.

Is the correct steps to run bootrom-step.sh, turn off Fire 7, short the pin, plug in usb, remove short after prompt, and press enter?
[Fire General] mcbeat257:
You have to download the latest version to get my method to work, which is mtk-su_r19.

Link to my post here
[Fire General] slacka123:
ssh server / bloatware removal

What are the cool kids using for a ssh server these days? Previously, I used dropbear that came with CyanogenMod. I liked that, but I'm not seeing it as a standalone.

Also what are people using to debloat? Amazon Fire Toolbox V6.4 or manually adb shell pm disable/uninstall ?
[Fire General] bardell3600:
Play Store

Rather that the link above for Google Apps, which will lead you to wrong file versions, it is better you get the download links from this YouTube Post. The links he provides get you to the correct Account Manager and Framework:

Google Play Store on Kindle Fire 7" 9th Generation
[Fire General] mundre:
I followed the hardware method since my build number seem to exceed what's supported by mtk-su.

Anyway, I ran sudo ./bootrom-step.sh, shorted my pin, connected to USB and then I got this error, which looks like some serial connection error:

[2019-12-16 21:19:26.575777] Waiting for bootrom
[2019-12-16 21:20:52.559444] Found port = /dev/ttyACM0
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 291, 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 161, in <module>

And, now the device doesn't respond at all. It doesn't charge or start. Did I just brick my fire ? I would appreciate any help.
[Fire General] saupe2005:
Cant get past step 5

Help im at stuck at this stage

5. Now, open another terminal on your PC, extract amonet-mustang.zip, navigate to it, and run `sudo ./bootrom-step.sh`. It should print "Waiting for the bootrom".

All i get is this

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

Traceback (most recent call last):

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

from common import Device

File "/home/xubuntu/Downloads/amonet-mustang/modules/common.py", line 6, in <module>

import serial

ModuleNotFoundError: No module named 'serial'

Been trying for hours

Gather it is a problem with pyserial supposedly installed but not working using xubuntu live usb

Any ideas??
[Fire General] parkskier426:
Yeah, I got that issue. I removed and reinstalled pyserial and it worked, so I'd suggest trying that.