yashsingh1/xdaforums huggingface dataset:
[Fire General] saupe2005:
Used linux mint instead worked but now get waiting for bootroom so looks good

type reboot in the othe terminal window tablet reboots but i get this.

[2019-12-19 00:31:36.007960] Waiting for bootrom

[2019-12-19 00:31:49.889921] Found port = /dev/ttyACM0

[2019-12-19 00:31:49.898823] Handshake

Traceback (most recent call last):

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read

'device reports readiness to read but returned no data '

serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

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

main()

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

handshake(dev)

File "/home/mint/Downloads/amonet-mustang/modules/handshake.py", line 9, in handshake

dev.handshake()

File "/home/mint/Downloads/amonet-mustang/modules/common.py", line 97, in handshake

c = self._writeb(b'\xa0')

File "/home/mint/Downloads/amonet-mustang/modules/common.py", line 92, in _writeb

return self.dev.read()

File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 509, in read

raise SerialException('read failed: {}'.format(e))

serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

Did you come across this issue?
[Fire General] Youdoofus:
this is the error i get

https://xdaforums.com/amazon-fire/o...-downgrade-t3944365/post81228897#post81228897

i did uninstall and reinstall pyserial too.
[Fire General] slacka123:
Team Win Recovery Project 3.3.1

@xyz`

Can you please update the instructions to add a link to

twrp-mustang-3.3.1-0.zip

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

This gives backup and recovery options that I've found to be useful. Thanks for making this possible.

Happy Holidays!
[Fire General] Rortiz2:
What command did you used to install pyserial?

Regards.
[Fire General] Youdoofus:
sudo apt install pyserial

then the downloading confirmation and installation confirm codes flew by in terminal, as it looked like it should

tried it again, failed with the same error

then issued the following "sudo apt uninstall pyserial", confirmation code flew by, resulted in something along the lines of "successfully uninstalled pyserial" yada yada

reinstalled using previous code

tried it again with same result

because im an idiot, i then typed something in shell that bricked it :D

tried shorting the wires, but what do i connect the other end of the wire to? Ground on the battery terminal? positive? I havent tried any of the battery posts yet as i didnt want to fry it
[Fire General] Rortiz2:
You should install pyserial for python3 not for python2 ;)

sudo apt install python3-serial

About the tab, I pressume that thing that you typed to brick it is what OP says to brick the Preloader. Can you connect the tablet without short anything and type

lsusb

?

Regards.
[Fire General] Youdoofus:
ok, on Ubuntu now. ran the python3 install code and resulted in this

joe@joemama:~$ sudo apt install python3-serial

[sudo] password for joe:

Reading package lists... Done

Building dependency tree

Reading state information... Done

Suggested packages:

python3-wxgtk3.0 | python3-wxgtk

The following NEW packages will be installed:

python3-serial

0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded.

Need to get 56.5 kB of archives.

After this operation, 376 kB of additional disk space will be used.

Get:1 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 python3-serial all 3.4-2 [56.5 kB]

Fetched 56.5 kB in 0s (220 kB/s)

Selecting previously unselected package python3-serial.

(Reading database ... 168419 files and directories currently installed.)

Preparing to unpack .../python3-serial_3.4-2_all.deb ...

Unpacking python3-serial (3.4-2) ...

Setting up python3-serial (3.4-2) ...

lsusb with tablet connected via usb results in this

joe@joemama:~$ lsusb

Bus 001 Device 002: ID 8087:8000 Intel Corp.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 002 Device 004: ID 8087:07dc Intel Corp.

Bus 002 Device 003: ID 04f3:2013 Elan Microelectronics Corp.

Bus 002 Device 002: ID 0bda:5754 Realtek Semiconductor Corp.

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

unplugged the usb and lsusb results in the same

joe@joemama:~$ lsusb

Bus 001 Device 002: ID 8087:8000 Intel Corp.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 002 Device 004: ID 8087:07dc Intel Corp.

Bus 002 Device 003: ID 04f3:2013 Elan Microelectronics Corp.

Bus 002 Device 002: ID 0bda:5754 Realtek Semiconductor Corp.

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Fire General] Rortiz2:
Ok not sure how you exactly "bricked" the tablet but isn't in bootROM mode neither Preloader Mode, so you will need to use hw method.

The amonet script should work now.

Regards.
[Fire General] Youdoofus:
thank you for the help btw. its appreciated. also, im still unclear on how to get it out of the brick state with the wire shorting methods. i have tons of different sizes of wire at my disposal, so thats not an issue in the slightest, i just dont know where to touch the other end to. The diagram shows what spot on the pcb to touch one end to, but not the other. I could be missing something small, obvious and stupid too.

i bricked it by typing something in shell. i cant recall what it was at the moment, but i figured i was just relegated to the hardware method now. Just cant figure out what the wire needs to connect to. Thsi reminds me of the HTC Rezound root method from waaaaay back lol never got that one to work either fwiw
[Fire General] Kramar111:
[MENTION=3695297]Youdoofus[/MENTION]
[Fire General] Youdoofus:
yeah, i looked for spots with those labels, but wasnt able to find them. i can post a pic of the tablets guts if that would help
[Fire General] Kramar111:
[MENTION=3695297]Youdoofus[/MENTION]

Metallic shield/edging = ground = second point you looking for
[Fire General] Youdoofus:
will a successful short cause the screen to do anything, or will it only be noticeable in terminal?
[Fire General] Kramar111:
[MENTION=3695297]Youdoofus[/MENTION]

Terminal

Or dmesg

Did you read OP? Hardware method, item 7
[Fire General] spatchy:
Hey, I'm having the same issue, did you find out how to do this?
[Fire General] Danksh:
I'm trying to root my second Fire 7 Mustang (first one was a success). Both time I used the software method, but on the second one the screen turned off when I ran ./bootrom-step.sh, and I can't get it to trun back on.

It's been over an hour. I tried holding the power button for over a 60 seconds to force a shutdown in case it was stuck on, but I can't seem to get it to turn back on. I've got it sitting unplugged right now, wondering if killing the battery and plugging it back in may solve anything. Any other suggestions?
[Fire General] BuckNut82:
Been working at this for 2 days I hope someone can help

steve@steve-OptiPlex-790:~$ adb devices

List of devices attached

G0W0X8089445FTGX	device

steve@steve-OptiPlex-790:~$ adb push /home/steve/Desktop/arm/mtk-su /data/local/tmp

/home/steve/Desktop/arm/mtk-su: 1 file...shed. 7.2 MB/s (34312 bytes in 0.005s)

steve@steve-OptiPlex-790:~$ adb shell

mustang:/ $ cd /data/local/tmp

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

[Failed critical init step 4

This platform is not supported

1|mustang:/data/local/tmp $
[Fire General] delgada89:
Actually didn't end up doing that. I just unplugged it from the battery and then it worked. So removing the heatshield and grounding it wasn't necessary. Hope that helps.
[Fire General] Youdoofus:
the heat shield is pinched in over a dozen places along the base of where the pcb and the shield itself meet. Youll notice tiny indents along that line. The Shield is quite flexible too, so use caution when prying it up.
[Fire General] Youdoofus:
at wok now. ill have the tablet and one of my lappys when i get home and ill be off for the next 2 days for Christmas break, so ill have some time to fiddle with it

also, do you need to keep the wire on the posts during this process? or is it just a tap and done? if one must keep it attached, should i use tape or bluetac to secure it? i only have 2 arms (the others are on backorder from amazon. ill be Doc Oc soon tho ;) )
[Fire General] kylegordon:
Hi all,

Big thanks to the OP for developing this rooting method. The software route seems to have worked well on a new Fire 7 I got a few weeks ago. I do however have one issue to ask the community...

Has anyone experienced situations where the device goes to sleep and absolutely refuses to waken up again? Single button press, multiple presses, long presses (up to a minute long), etc all fail to waken it. A few times I've resorted to disconnecting the battery or just letting it drain entirely.

Next step would be for me to wipe it completely and start afresh, but just thought I'd ask around first.
[Fire General] Michajin:
Are you on the stock rom? Next time it does it, see if you are in the bootrom or preloader (plug in a linux system then lsusb). I had this happen once and found it to be stuck in the preloader (i caused it with amonet though). I have been using Los 14.1 without issues....
[Fire General] claustrox:
mustang:/data/local/tmp $ adb shell

/system/bin/sh: adb: not found

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

Failed critical init step 4: Bad address

setns failed:: Permission denied

New UID/GID: 2000/2000

Kindle fire 7 9th

002517057668

Any idea? Patched?
[Fire General] avengerpro:
bad

after run mtk script via software mode

shows same screen to this first post and after that my tablet wont start anymore

stuck on black screen, dont charge, dont turn on, dont nothing
[Fire General] kylegordon:
Not on the stock ROM. LOS14.1 as well. Did the rooting process and then pivoted to directly installing LOS 14.1, so am wondering if it's related to that.

Nothing relevant appears on lsusb, and dmesg stays silent too. It's as if nothing has been plugged in. It's actually in this state just now, after working just fine this morning! :)

---------- Post added at 12:34 AM ---------- Previous post was at 12:09 AM ----------

In saying that, it sounds awfully like it would be fixed by flashing the 'SOD Fix', from https://xdaforums.com/showpost.php?p=80621157&postcount=253

Have just done so... will report back in a day or two :)
[Fire General] Danksh:
I'm having the same issue. I ran lsusb and see "MediaTek Inc. MT6227 phone" when my tablet is plugged in. How can I get out of bootrom/preloader? Should I run the bootrom script again?
[Fire General] Michajin:
What were you doing prior to getting stuck in this? You should be able to hold the power button for 10-15 seconds for forced reset, but sometimes you have to disconnect the battery. Any idea what you were doing right before it went into this state?
[Fire General] Danksh:
I ran the bootstep script again and all seems to be working well.
[Fire General] jcruz942:
Has anyone tried this with the new Fire OS 6.3.1.4 update
[Fire General] kylegordon:
Well, it's day 2, and the Fire 7 has been seemingly solid after flashing the SOD fix. Fingers crossed.
[Fire General] Youdoofus:
thank you very much. as it happens, i was an idiot. to my credit, i was a really frustrated idiot, but an idiot nonetheless. Got it unbricked, booted, TWRP installed and magisk installed. Thanks again man!!
[Fire General] Youdoofus:
i accidentally updated mine just before attempting any of this to the latest version. cant recall what version it is, but it was what the stock recovery wanted to install, so i assume its the one youre referring to
[Fire General] jcruz942:
Got it, did you use mtk-su_r19?
[Fire General] Youdoofus:
yep. and once i stopped being a moron with it, it worked like a charm. i found it to be the easiest by booting directly into Ubuntu and using the terminal
[Fire General] rburtch3:
Touchscreen not working

I did everything in the guide. I got TWRP on there. I unlocked the bootloader, but now the touch screen won't work at all...Not in TWRP or in FireOS. Thoughts?
[Fire General] mauro78:
mtk-su not working anymore

Hello,

Thanks for your work,much appreciated!

I tried to run mtk-su on my fire 7,

running fire OS 6.3.1.2,

and I get:

1|mustang:/data/local/tmp $ ./mtk-su -v
armv7l machine
Failed critical init step 4
This platform is not supported

On the mtk-su page you linked:

https://xdaforums.com/android/development/amazing-temp-root-mediatek-armv8-t3922213

I read:

Does that mean that I can't proceed with the software method?

Thanks
[Fire General] jumpygecko20:
Had to root/unlock using hardware method, software method did not work for me.

I did not run the finalize.zip file, instead I used the PM disable command as needed to disable various packages, example:

pm disable com.android.contacts

Once finished rooting I also performed the following actions:

- Disabled OTA updates by running:

o pm disable com.amazon.device.software.ota

o pm disable com.amazon.kindle.otter.oobe.forced.ota​

- Updated TWRP to newer version.

- Installed OpenGApps, version 7.1 Nano (clear dalvik and cache after install)

- Disabled auto-updating inside Magisk Manager to help avoid bricking

- Disabled special offers

- Switched launcher to Nova (after installing and initializing Nova)

- Installed "magiskhide props config" module in order to pass Google SafetyNet
[Fire General] amostfy:
Does this work on amazon 10 2019?
[Fire General] zolotiyeruki:
Thanks, OP, and to all the other developers who have worked on this! I've run into a problem/question that I could use some help with. After I follow all the steps, almost everything is fine. However, if I go to Settings->My Account, the app crashes. If I then reboot, it appears that the tablet then tries to run the setup app, which repeatedly crashes. The only (easy) way to fix it is to reinstall fw.zip.

If I do not run finalize.zip, the My Account setup starts just fine. I'm not a developer, but my guess is that the tablet is trying to run /system/priv-app/com.amazon.kindle.otter.oobe.forced.ota, which is removed by finalize.zip

Is there a way to disable OTA updates, but still allow the device to be registered with Amazon?
[Fire General] theholmboy:
Would mustang No-Ads version cause serial mismatch error?

Background: I have successfully rooted many devices, with ford & karnak tablets being the most recent. I am using the same Ubuntu setup and and trying to do the hardware method on a mustang tablet, but it keeps stopping with the serial mismatch error (see typical error message below). I have tried all of the suggestions here (including trying it with the battery disconnected, restarting the computer, different USB ports/cables) but always with the same basic error.

My mustang tablet is the No-Ads version - Could that be the reason and, if so, is there a work-around? It currently has Fire OS 6.3.1.2. Thanks!

rob@TX1000-Ubuntu:~/Downloads/mustang/amonet$ sudo systemctl stop ModemManager

[sudo] password for rob:

rob@TX1000-Ubuntu:~/Downloads/mustang/amonet$ sudo systemctl disable ModemManager

rob@TX1000-Ubuntu:~/Downloads/mustang/amonet$ sudo ./bootrom-step.sh

[2019-12-29 15:31:19.509651] Waiting for bootrom

[2019-12-29 15:31:31.894169] Found port = /dev/ttyACM0

[2019-12-29 15:31:31.915424] 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/rob/Downloads/mustang/amonet/modules/load_payload.py", line 99, in load_payload

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

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

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

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

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch

rob@TX1000-Ubuntu:~/Downloads/mustang/amonet$
[Fire General] rburtch3:
Touchscreen still not working. Anyone???
[Fire General] Sideswip3:
Stucked in the same place, if you find a soluion please let me know, i've applied this method succesfully for other 2 tablets, but this one is the only one that popped up with this.

---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------

If you applied the hw method, i suggest you to check if you accidentaly plugged out the digitalizer connection from the motherboard.
[Fire General] rburtch3:
Can you tell me how you disabled special offers and ads after rooting?
[Fire General] da_anton:
I had the same problem. After some research I found out that the tablet is connected only in preloader mode and the pin short circuit I used did not work. dmesg showed that. I did the following then:

- removed the heat spreader

- shorted the small recommended pin as mentioned here https://xdaforums.com/showpost.php?p=79683131&postcount=22 with a paper clip to the metal case where the heat spreader is mounted

After doing so the script ran successfully and I could install lineageos. Hope that helps.
[Fire General] komandantemario:
WOW I did it!

Just wanted to say a big thank you! I tried first with the software option and I couldn't make it because it's a new version of the Fire 7. So I tried with the hardware option and, after trying by a couple of hours I could make it. My problem was that I was not doing well the shorting between the indicated point and the ground. I got confused, thought that it was another stuff but finally I could make it. Big hooray for you guys. So far I have my fire 7 with the TWRP installed and working. Next step is to choose if I install a stock ROM or another one that has been created by some dev in this great forum.

Thanks!!!

Cheers.

Mariano from Argentina.
[Fire General] wolf45801:
anyone have an idea on why the screen would flash orange off and on? you can see the time up at the top of the screen but nothing else
[Fire General] DB126:
Most likely a hardware failure if it happened spontaneously. Try long pressing power for 20-30 sec to force a shutdown. Alternatively, pop off the back and disconnect/reconnect the battery. If unsuccessful reach out to Amazon for a replacement if under warranty.
[Fire General] wolf45801:
I got it working turns out the software was corrupted it booted fine and I could access the settings but only half of the settings was available
[Fire General] leviathany2k:
Can I use FWUL?

Can I use the Forget Windows Use Linux app from here or just Ubuntu will do the job?
[Fire General] elshaera:
Windows support

Why isn't windows supported !!?
[Fire General] DB126:
If it were easy it would have been done.

With that said, there are several alternatives (all Linux based) that are not terribly difficult to work through depending on your background.
[Fire General] Sideswip3:
This worked like a charm! turns out that i was shorting the pin on the image with the one next to it, shorting only that pin with the metal case solved it, thank you!

btw the admin should link this to the original post, a lot of people were having the same problem.
[Fire General] remghoost:
Hello all

The download for amonet-mustang.zip seems to be broken.

Anyone have a copy of it....?
[Fire General] leviathany2k:
this works very easy the first time.

sudo systemctl stop ModemManager

$ sudo systemctl disable ModemManager

$ sudo ./bootrom-step.sh

[2019-12-29 15:31:19.509651] Waiting for bootrom

Make sure you are shorting the right pins and places and youll be set. Installing via ADB lineage and the patch after to fix the not waking up issue and everything is running.

if you get an error is because the right pin is not shorted.
[Fire General] milfriez:
Need a bit of help here. Trying HW method running on Ubuntu 18.04 Live USB. On first try I was able to short the pin, and it copied code everything went as planned. Made it to the reboot message, it indicates to proceed? What does that mean? I rebooted the device nothing just black screen. I tried once again to short the pin, it copied the code, and it go to the confirmation reboot to unlocked fastboot. Device shows in fastboot, but I cannot start ADB shell to reboot. What do I do? I eventually got to the Amazon screen, shut back off and tried again. Now i'm getting consistent protocol mismatch errors when trying to short. I have disconnected the battery, modemmanager has been disabled since the start, but it seems like I'm going backwards now.

Can anyone help at least get me past serial protocol mismatch. And then if I am able to flash again, what do I do once it gets to the reboot to unlocked fastboot? Unplugging via USB and replugging back in does nothing for me.
[Fire General] cyborggold:
I can't for the life of me get this to work. When I enter adb shell and try to run mtk-su I get the message 'Failed critical init step 4, this platform cannot be supported." With the hardware bootloader unlock I have only found directions that say 'temporarily connect a point on the back of the board to ground" without anything saying how long the connection needs to be made, what do do once it is connected, etc. I would really like to get a non-amazon OS on this before giving it to my daughter. I have tried several versions of mtk-su with the same results each time.
[Fire General] milfriez:
After starting bootrom, hold the pin and the case to ground. Watch the screen, it will instruct you when to remove and press enter. It should only take a few seconds.

Past this point good luck, I have completed all steps, and still have been unable to get it to recovery mode. I was able to complete both bootrom and fastboot, but it never came back up to the recovery console. When I reboot, I am just presented with a battery logo. I am currently charging the device to see if that will help at all. I had to disconnect the battery multiple times throughout this endeavor to get it to work properly, and still have not completed it yet. Going on Day 3

---------- Post added at 09:10 PM ---------- Previous post was at 08:52 PM ----------

Happy to report that I believe my issue was just due to having it connected to the computer and poor charging capabilities. I put it onto a wall charger, and it has booted into recovery mode. So I believe from this point on out I should be good.

One word of advice. At the point after running bootrom it says to reboot. I had a heck of a time getting mine to reboot. I suspect this may have been due to again poor charging capabilities on the laptop USB ports to provide adequate power. But I had to remove the battery clip to get it to fully shutdown, and then it would not come back up to the amazon screen as instructed, again I blame power. Word to the wise, make sure you're charged up before starting this. I think it could have saved numerous headaches for myself.
[Fire General] Michajin:
"Fire 7 9th gen (2019) (thanks [MENTION=4914529]Michajin[/MENTION]) -- up to Fire OS 6.3.1.2 build 0002517050244 only"

You have an updated device, you must do the hardware way.