yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Android Development] NerdFire:
Is there a circumstance where Linux (or by extension any other OS) would refuse to recognize the existence of a tablet?

Here's the deal: The other day I found a suez-class Fire HD 10 in my junkbox drawer. (Yeah, my life is kind of like that.) I vaguely remember packing it away over a year ago, maybe closer to two, but I don't remember at all why I packed it away in favor of another Fire HD 10 that's currently one of my main tablets. I probably screwed up an update sideload or something.

At any rate I pulled off the cover and prepped it for unbricking, but my unbricking setup -- a Victualbox instance running Linux Mint 19.2 on a Mac OS host that has successfully resuscitated several other tablets -- doesn't recognize the tablet when I plug it in. I think I should get an indication that there's a Mediatek device attached to a USB port when I hook the tablet up to my Mac, but there's no reaction from the Mac -- and if the Mac can't tell the tablet is there, the guest OS certainly won't be able to.

Using a different cable made no difference. (Both cables are known good.) If I plug the tablet into my USB hub instead of directly into a port on my Mac, the "I'm connected to something" light doesn't light up.

I haven't tried using a Linux machine and probably won't be able to for a few days.,

I wasn't able to disconnect the battery. It's seated pretty firmly and I don't want to pull on the wrong thing and have the wires come off, leaving the connector firmly in place. (Yeah, my life is kind of like that too.) But as I understand it the presence or absence of the battery shouldn't make any difference as far as flashing the memory or detecting the existence of the tablet is concerned.

Any ideas? Or do I put the screws back in, put the cover back on and wait to see what they'll give me in trade for one of the 2019 models on Black Friday?

Thanks.
[Fire HD 8 and HD 10 Android Development] DB126:
Sounds like a great idea assuming you can score a 'good' deal on trade. One can assume the Black Friday price will be $100 USD like always; take it from there.
[Fire HD 8 and HD 10 Android Development] NerdFire:
True, and unless a solution presents itself pretty quickly, that's probably what I'll do. I know I'm going to want one of those; I know payday falls on Black Friday this year; and while I was hoping I could get it going so I could experiment with it, I'm about at the limit of the amount of time I want to put into the project. Thanks for the reply.

UPDATE: If I read it right, I should be able to get a $5 gift card for my bricked suez, plus 20% off when I upgrade to the Maverick-class HD 10. If it really does go down to $100 for Black Friday, that sounds like a sweet deal.
[Fire HD 8 and HD 10 Android Development] MarkAG:
I am running Debian and when I get to Disable Watchdog, it responds with RunTime Error Serial Protocol mismatch
[Fire HD 8 and HD 10 Android Development] wings516:
[MENTION=3497316]retyre[/MENTION] Can this be done running Ubuntu on Windows10? I run it EXACTLY as directed in the guide and it just hangs on "Waiting for bootrom"

any advice?

I am using stranded copper tied into the SD card housing and the other end touching the blue marked point on the back.
[Fire HD 8 and HD 10 Android Development] Rortiz2:
Ubuntu should work. If it gets stuck at that point you're probably not running the script as sudo.

sudo ./bootrom-step.sh
[Fire HD 8 and HD 10 Android Development] wings516:
Still hangs.
[Fire HD 8 and HD 10 Android Development] Rortiz2:
You're using WSL. You need to use VirtualBox or live USB with ubutnu;)

Regards.
[Fire HD 8 and HD 10 Android Development] wings516:
Done and running, but now I'm getting serial protocol mismatch, line 87. I ran all the commands on root to disable modem manager.
[Fire HD 8 and HD 10 Android Development] Rortiz2:
Sounds like it's detecting the Fire in Preloader Mode instead of bootrom.

You can try running the script without the battery connected and only shorting the marked points by the OP.

Regards.
[Fire HD 8 and HD 10 Android Development] wings516:
This was done with the battery disconnected. Only the shorted pin, USB and speaker cables are connected.
[Fire HD 8 and HD 10 Android Development] Tired & Frustrated:
Don't know if this is the right place for this but here we go!

The definition of insanity: doing something over and over again expecting different results. I need help. I'm tired of wasting my time on trying to fix something that can't be fixed. You'll say there is no tablet that can not be unbricked. Well, I beg to differ. My 2017 Amazon fire HD 10 sits now in front of me a giant useless hunk of junk that at this point deserves to be thrown in the trash. I'm just sick and tired of being frustrated at how long it has taken to find out it can't be done. Can you believe I've been trying to get this thing working since September of last year. I mean, It really shouldn't be this hard to unbrick a $189.00 64gb black tablet. And can you believe the reason for it being bricked was the result of me stupidly listening to the amazon agent on the phone telling me to press the power button in the middle of it performing a factory reset! How dumb was that?! Before that it was stuck in a bootloop. It wouldn't go past the fire label. I wish I had found this site before calling them but that's neither here or there. I mean come on! I've tried everything on here and then some, following it to a T yet no results. Go figure! Every time I felt like I was going to make progress an error pops up on the screen like it's giving me the finger and laughing in my face saying "ha! you really thought It was going to work you moron!" I even went out of my way to go buy a special tool just so I can unscrew the back to perform the short. I also purchased a so called 'factory cable' which ended up being a complete and utter waste of money. I'm running linux off of a live usb version ubuntu-mate on a HP pavilion zv5000 built for 32bit windows xp but currently running win 7. Slow as molasses though. I've tried other linux distros as well thinking that was the issue. I've used versus paper clips and jumper wire from a beard board kit to do the short. I've followed the guide spending countless hours reading and researching through the forums and the internet for possible solutions even tried that battery trick from Dragonfire1024 but, no go. Even though I didn't have the correct error message the gpt-fix was made from a 32gb tablet I tired anyway and that ended in failure. The Runtime Errors I've got ranged from serial protocol, read fail, and device failure. I feel like a post should be added detailing the common errors one might in encounter and the possible solutions. Cause I'm sure either people are having the same issues. Just my suggestion. I spent hours last night trying to figure this out with no sleep might I add. At this juncture I'm about ready to toss in the towel and go purchase the latest and greatest for whatever price even though it doesn't seem that much different from this one I hear it's good. I'd like to thank you for the privilege of your time in reading this and I hope someone out there with the knowledge and experience can lend a helping hand to get my baby out of the emergency room and back to normal.

That is all. Good day to you all.
[Fire HD 8 and HD 10 Android Development] DB126:
- Amazon techs are just script readers

- factory cables are useless on Amazon devices

- possible your device suffered a secondary hardware failure sometime after the initial issue began or it became damaged during all the tinkering

- that said...probably a procedural error w/pin short method or some subtlety escaping attention

- tighten up the posts; wall-of-text rarely gains attention

Contact Amazon, tell them your story (briefly). Most likely get a discount on a 2019 model which has some nice improvements. Or, head on down Wally's and grab one of their tabs at a lower price point. Then sell your Amazon brick on an auction site or save it for a future project.

Life sucks sometimes - but there is always another sunrise (until there isn't). Make the best of your gizmo situation; there are bigger fish to fry.
[Fire HD 8 and HD 10 Android Development] coliny59:
I bricked my tablet. I am able to start the script and it looks like it's doing things, but it fails saying that it can't read rpmb. What can I do next?

I commented out all the lines that reads rpmb. Looks like it works now.
[Fire HD 8 and HD 10 Android Development] martinbrecko:
I am trying to carry out the instructions with VirtualBox. Unfortunately, the script always stops at waiting for Bootrom. Can this be due to the virtual machine?
[Fire HD 8 and HD 10 Android Development] chjohnso:
Still getting Serial protocol mismatch

I have everything disassembled and have been trying to short my fire hd 10. Here is what I get every time:

[2020-03-24 15:30:59.801978] Waiting for bootrom
[2020-03-24 15:31:21.396052] Found port = /dev/ttyACM0
[2020-03-24 15:31:21.435498] Handshake
[2020-03-24 15:31:21.456238] Disable watchdog
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 92, in <module>
main()
File "main.py", line 54, in main
handshake(dev)
File "/home/XXXXXXX/Documents/HD 10/unbrick_suez/modules/handshake.py", line 11, in handshake
dev.write32(0x10007000, 0x22000000)
File "/home/XXXXXXX/Documents/HD 10/unbrick_suez/modules/common.py", line 150, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/XXXXXXX/Documents/HD 10/unbrick_suez/modules/common.py", line 87, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch

Battery is disconnected, ModemManager is disabled, and I have tried both USB ports. Not sure what to try next.

Does anyone have any ideas as to how to fix this?

Thank you!
[Fire HD 8 and HD 10 Android Development] flaming_lemons:
serial protocol mismatch here, too

similar problem (same?) here on Ubuntu 19.10, adb and fastboot enabled, modemmanager removed and disabled...

I have the fire hd10 open and shorted but the script throws:

[2020-04-05 22:42:37.014509] Waiting for bootrom
[2020-04-05 22:42:45.335053] Found port = /dev/ttyACM0
[2020-04-05 22:42:45.374266] Handshake
[2020-04-05 22:42:45.396024] Disable watchdog
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 92, in <module>
main()
File "main.py", line 54, in main
handshake(dev)
File "/home/xxx/Downloads/unbrick/modules/handshake.py", line 11, in handshake
dev.write32(0x10007000, 0x22000000)
File "/home/xxx/Downloads/unbrick/modules/common.py", line 150, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/xxx/Downloads/unbrick/modules/common.py", line 87, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch

so I went to line 87 and commended out the in common.py but I don't think I know what I am doing at this point :)

def check(self, test, gold):
if test != gold:
print(test)
print(gold)
print("ERROR: Serial protocol mismatch") <--- uncommented
#raise RuntimeError("ERROR: Serial protocol mismatch") <---- commented out

and now it stops here:

[2020-04-05 22:22:58.368021] Waiting for bootrom

[2020-04-05 22:23:40.592908] Found port = /dev/ttyACM0
[2020-04-05 22:23:40.631312] Handshake
[2020-04-05 22:23:40.652038] Disable watchdog
b''
b'\x00\x01'
ERROR: Serial protocol mismatch
b''
b'\x00\x01'
ERROR: Serial protocol mismatch

* * * Remove the short and press Enter * * *

[2020-04-05 22:24:00.674653] Init crypto engine

b''
b'\x00\x01'
ERROR: Serial protocol mismatch
b''

[SNIP - removed ~30 iterations of this]

b'\x00\x01'
ERROR: Serial protocol mismatch
b''
b'\x00\x00'
ERROR: Serial protocol mismatch
Traceback (most recent call last):
File "main.py", line 92, in <module>
main()
File "main.py", line 57, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/xxx/Downloads/unbrick/modules/load_payload.py", line 113, in load_payload
hw_acquire(dev)
File "/home/xxx/Downloads/unbrick/modules/load_payload.py", line 25, in hw_acquire
dev.write32(CRYPTO_BASE, dev.read32(CRYPTO_BASE) & 0xFFFFFFF0)
File "/home/xxx/Downloads/unbrick/modules/common.py", line 125, in read32
data = struct.unpack('>I', self.dev.read(4))[0]
struct.error: unpack requires a buffer of 4 bytes

anyone can point in the right direction?

I tried using bootable USB of ubuntu 18.04LTS and 16..04LTS - same same. so back on 19.10 now. did something change to cause this to fail?

Can I run the script in verbose to help // troubleshoot?

thanks

Andreas
[Fire HD 8 and HD 10 Android Development] flaming_lemons:
USB2 ports?

Are you using USB2 ports?

I am looking for an old laptop to prove this... only USB3 ports here...

good luck
[Fire HD 8 and HD 10 Android Development] flaming_lemons:
tried a different laptop - no joy

it was not the laptop. can someone tell me what the script is checking at line 87 (when it throws the error?)

Apparently it expects \x00\x01 but gets .. nothing? but this is where my code skill stops :/

also I seem to be stuck in preloader... any clues?

[2020-04-10 07:34:52.475445] Waiting for bootrom
[2020-04-10 07:35:10.082899] Found port = /dev/ttyACM0
[2020-04-10 07:35:10.121918] Handshake
[2020-04-10 07:35:10.142719] Disable watchdog
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 92, in <module>
main()
File "main.py", line 54, in main
handshake(dev)
File "/home/xxx/Downloads/modules/handshake.py", line 11, in handshake
dev.write32(0x10007000, 0x22000000)
File "/home/xxx/Downloads/modules/common.py", line 150, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/xxx/Downloads/modules/common.py", line 87, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch
root@snowflake:/home/xxx/Downloads#

connecting usb cable (tried 3 now) and applying a short the device starts, when I have the script running

but I immediately get to

Bus 003 Device 006: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

checked/used updated udev rules

https://github.com/M0Rf30/android-udev-rules

but still cant' get the device further than bootloader (disconnected from battery, disassembled)

tried the amonet scripts (bootrom-minimal, etc..)

but they all drop at this

[2020-04-10 08:49:34.458825] Found port = /dev/ttyACM0
[2020-04-10 08:49:34.498194] Handshake
[2020-04-10 08:49:34.518900] Disable watchdog
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 192, in <module>
main()
[Fire HD 8 and HD 10 Android Development] flaming_lemons:
[MENTION=3497316]retyre[/MENTION] could you lend me a hand and help me debug the script? i really can't read it with my meager skills :/

and I am stuck in preloader

amazon offered me a 15 bucks discount for a new hd10 as a workaround as it is just out of warranty :P
[Fire HD 8 and HD 10 Android Development] kudiska:
hd 8

does anyone know if this will work with the HD 8 2017? what pin would be needed?
[Fire HD 8 and HD 10 Android Development] Michajin:
There is a unlock thread for hd8 (2017) Douglas. Search for it...

---------- Post added at 08:58 PM ---------- Previous post was at 08:07 PM ----------

I can try and help you. There is a lot of useful info in the hd10 Suez unlock thread. Look through that. Most the answers you search for are there. If you would like more assistance send me a message and I see I can do. I'm no expert, but have some experience with unlocking/ bricking these.

---------- Post added at 09:07 PM ---------- Previous post was at 08:58 PM ----------

I can try and help you. There is a lot of useful info in the hd10 Suez unlock thread. Look through that. Most the answers you search for are there. If you would like more assistance send me a message and I see I can do. I'm no expert, but have some experience with unlocking/ bricking these.
[Fire HD 8 and HD 10 Android Development] flaming_lemons:
hd10 unlock follow-up

yeah.. so.,. that's how I ended up here :)

after I had installed TWRP I rebooted and since then I don't get any further than preloader

also took the tablet apart and tried to use the scripts used here (amonet bootrom and bootrom-step scripts)

tried with an old laptop, too. (USB2 ports) no joy

that's how I ended up here, that script is the only one that does _anything_ :P

but my skills are not good enough to unravel what this means:

File "/home/xxx/Downloads/modules/handshake.py", line 11, in handshake
dev.write32(0x10007000, 0x22000000)
File "/home/xxx/Downloads/modules/common.py", line 150, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/xxx/Downloads/modules/common.py", line 87, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
[Fire HD 8 and HD 10 Android Development] Michajin:
Yes, you are in preloader to run the script, i would suggest you go over to the most current files from the unlock thread.

Try unbricking from there and see if you have the same result. Can you short the device and force bootrom?

https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
[Fire HD 8 and HD 10 Android Development] flaming_lemons:
SUCCESS

the problem was not the procedure or the script, it was the short :/

silly me used a crocodile clamp to attach to the MicroSD cage.. and because it seemed convenient I soldered the needle for the short to the attached cable (an anti-static wristband)

now those have a resistance of 1,5M Ohms.. not suitable for a short, I guess

soldered it to a common cable > works instantly

[2020-05-09 07:35:05.401969] Waiting for bootrom
[2020-05-09 07:35:42.807252] Found port = /dev/ttyACM0
[2020-05-09 07:35:42.807947] Handshake
[2020-05-09 07:35:42.808590] Disable watchdog

* * * Remove the short and press Enter * * *

[2020-05-09 07:35:46.735715] Init crypto engine
[2020-05-09 07:35:46.766793] Disable caches
[2020-05-09 07:35:46.767285] Disable bootrom range checks
[2020-05-09 07:35:46.784772] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes
[2020-05-09 07:35:46.786846] Send payload
[2020-05-09 07:35:47.512935] Let's rock
[2020-05-09 07:35:47.513816] Wait for the payload to come online...
[2020-05-09 07:35:52.265234] all good
[2020-05-09 07:35:52.265655] Check GPT
[2020-05-09 07:35:53.548315] 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, 34816), 'system': (208896, 3306496), 'cache': (3515392, 868352), 'userdata': (4383744, 56687583), '': (0, 1)}
[2020-05-09 07:35:53.548474] Check boot0
[2020-05-09 07:35:54.749738] Check rpmb
[2020-05-09 07:35:54.956222] Downgrade rpmb
[2020-05-09 07:35:54.958394] Recheck rpmb
[2020-05-09 07:35:55.855508] rpmb downgrade ok

sooo... thinking helps! Thank you for helping me out. now.. where was I? rooting.. yes!
[Fire HD 8 and HD 10 Android Development] BrainlessDude:
Hey guys. I bought a not working Fire HD 10 2017 because I thought it might be just a bad battery.

After trying a known working battery I tried plugging it into my PC and it seems like the PreLoader is connecting but is disconnecting right away after 1-2 seconds. Since I dont know what happened to this device is it worth trying this script on it? Or is this behavior a sign of a hardware failure?

When it is fixable I will setup a virtualbox right now :D

EDIT

I made a Ubuntu Live USB Stick and tried my luck. This is the outcome for now:

Im clueless what to do next...

Seems like the payload isnt going online as expected. lsusb shows the Mediatek Phone and not PreLoader
[Fire HD 8 and HD 10 Android Development] Michajin:
I believe that it the error related to modem manager...

sudo apt-get remove modemmanager

sudo apt-get remove --auto-remove modemmanager

sudo systemctl stop ModemManager.service
[Fire HD 8 and HD 10 Android Development] BrainlessDude:
I did all the commands. I can try it again but I am pretty sure.
[Fire HD 8 and HD 10 Android Development] Michajin:
You are better off using this thread and its files.....

https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
[Fire HD 8 and HD 10 Android Development] BrainlessDude:
Tried it but its still not fixed. Might really be a hardware failure.
[Fire HD 8 and HD 10 Android Development] kindle-user:
question

Hello

my problem is that after a successful unbrick the tablet still won't start. I plugged the battery in and out.

jorg@jorg-ThinkPad-X250:~/Schreibtisch/boot$ sudo ./bootrom.sh

[sudo] Passwort für jorg:

[2020-06-17 22:20:30.197994] Waiting for bootrom

[2020-06-17 22:20:55.321570] Found port = /dev/ttyACM0

[2020-06-17 22:20:55.322073] Handshake

[2020-06-17 22:20:55.322675] Disable watchdog

* * * Remove the short and press Enter * * *

[2020-06-17 22:21:05.042216] Init crypto engine

[2020-06-17 22:21:05.066640] Disable caches

[2020-06-17 22:21:05.067332] Disable bootrom range checks

[2020-06-17 22:21:05.083522] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes

[2020-06-17 22:21:05.085466] Send payload

[2020-06-17 22:21:05.634210] Let's rock

[2020-06-17 22:21:05.636187] Wait for the payload to come online...

[2020-06-17 22:21:09.240955] all good

[2020-06-17 22:21:09.241475] Check GPT

[2020-06-17 22:21:10.530568] 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, 34816), 'system': (208896, 3306496), 'cache': (3515392, 868352), 'userdata': (4383744, 56687583), '': (0, 1)}

[2020-06-17 22:21:10.530913] Check boot0

[2020-06-17 22:21:11.733233] Check rpmb

[2020-06-17 22:21:11.940314] rpmb looks broken; if this is expected (i.e. you're retrying the exploit) press enter, otherwise terminate with Ctrl+C

[2020-06-17 22:21:17.995600] Downgrade rpmb

[2020-06-17 22:21:17.997851] Recheck rpmb

[2020-06-17 22:21:18.888288] rpmb downgrade ok

jorg@jorg-ThinkPad-X250:~/Schreibtisch/boot$ ^C

lsusb shows:

jorg@jorg-ThinkPad-X250:~$ lsusb

Bus 001 Device 002: ID 8087:8001 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 003: ID 04ca:703c Lite-On Technology Corp. Integrated Camera

Bus 002 Device 002: ID 8087:0a2a Intel Corp.

Bus 002 Device 098: ID 0e8d:0003 MediaTek Inc. MT6227 phone

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

jorg@jorg-ThinkPad-X250:~$ ^C
[Fire HD 8 and HD 10 Android Development] Michajin:
I would suggest going to the newer unbrick and unlock thread. Use it to unlock it, since you are booting into the bootrom (that is "MediaTek Inc. MT6227 phone") you should be able the install twrp and flash a clean fireOS.

https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
[Fire HD 8 and HD 10 Android Development] kindle-user:
thank you

but I have to start it first. But nothing reacts either.
[Fire HD 8 and HD 10 Android Development] kojam:
Took mine apart. Why doesn't it look like this? (Comparing my attached pic vs the one in the OP)

11 screws? Where? Are they under this twin battery setup? I don't see one screw otherwise. Is mine not a 2017? I got it from the local drug store last year. They only ever get older stock electronics so I assumed it's gotta be 2017.

Do I have to remove these 2 monster batteries? ( By the way, how can this have two bigger batteries than the space shuttle, yet have such terrible battery life?! They drain like Crazy!!!)

I'm trying this process on Kali Linux. Is that a problem? Is that why it fails with the "serial protocol mismatch" error all the time?

Hopefully someone can help me.

Thanks
[Fire HD 8 and HD 10 Android Development] kojam:
Uploading the pic again. Used the xda app on previous post but it didn't upload the pic.
[Fire HD 8 and HD 10 Android Development] kojam:
Still didn't work.

Here's the image :

https://imgur.com/a/VOVGGSb