Thanx a lot, just what i was looking for.
I think (but can't recall the exact version numbers) that v18.104.22.168 = v22.214.171.124. Amazon screwed up the version numbers at some point and caused massive confusion about which version was which & which version was the latest.
Ah, ok. Mine is on 126.96.36.199, with 659662020. That's exactly the number of that one linked by you to amazon website (v188.8.131.52).
I tried Zip in TWRP & apk which all seemed to work, but when I then launched Magisk app, I think it told me Magisk wasn't installed & when I chose to install Magisk from within the Magisk app, the only method presented was to patch the boot.img
I'm not sure upgrading TWRP to the very latest version is a good idea, I'm sure I've read that it causes problems. I recommend sticking with a working version (I can't recall what version mine is, but 3.6.9_1.2 seems familiar, or is it 3.6.1_9.2? sorry, can't recall the right version number).
I flashed Magisk zip in Twrp, then renamed it with twrp file manager to apk and copied it to /system. After system boot Magisk Manager App was not installed completely, but starting it downloaded some missing files. Afterwards it runs without probs.
sudo ./bootrom-step-minimal.sh [2023-07-09 22:36:36.674250] Waiting for bootrom [2023-07-09 22:36:47.738967] Found port = /dev/ttyACM0 [2023-07-09 22:36:47.776022] Handshake [2023-07-09 22:36:47.796982] Disable watchdog b'' b'\x00\x01' Traceback (most recent call last): File "/home/laurens/Dokumente/suez/amonet/modules/main.py", line 192, in <module> main() File "/home/laurens/Dokumente/suez/amonet/modules/main.py", line 82, in main handshake(dev) File "/home/laurens/Dokumente/suez/amonet/modules/handshake.py", line 11, in handshake dev.write32(0x10007000, 0x22000000) File "/home/laurens/Dokumente/suez/amonet/modules/common.py", line 163, in write32 self.check(self.dev.read(2), b'\x00\x01') # arg check ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/laurens/Dokumente/suez/amonet/modules/common.py", line 90, in check raise RuntimeError("ERROR: Serial protocol mismatch") RuntimeError: ERROR: Serial protocol mismatch
Could simply mean the short was not applied correctly, you will have to keep pressing the power button to turn on then turn off the tablet and start again.
Bit late answering, but my post #1622 should answer your question.
I guess i'd install adb and fastboot on a pc if you already haven't, connect the device with usb, then flash the recovery of the tablet with twrp by entering these commands in a command prompt:Hello,
Revisiting hacking my Fire HD 10 after giving up in 2020 (I thought I killed it during the downgrade brick). Turns out I didn't and the tablet now displays the Amazon logo and the text "=> HACKED FASTBOOT mode: (0) - xyz, k40z" on screen. Where should I go from here?
Gonna add some important info I forgot. I remeber the last thing I did years ago was being able to root, then perform the brick. My VM lost connection with the device, which lead me into thinking I killed it. Decided to try it out again, starting at the step where you type "sudo ./bootrom-step-minimal.sh." and the following step.
So I've installed adb and fastboot, and i tried this command but it just says "waiting for device." Using lsusb does see a device called "Device 007: (ID no.) MediaTek Inc. Wireless_Device. I'm now out of the brick but if I recall I had to go that route because my OS version was too new. I don't recall ever completing the downgrade or installing twrp either.I guess i'd install adb and fastboot on a pc if you already haven't, connect the device with usb, then flash the recovery of the tablet with twrp by entering these commands in a command prompt:
fastboot flash recovery /path/to/twrp.img
You can get twrp for suez from ggow's lineageos 16 thread.
If you manage to flash twrp then you can go on with installing LOS 12/14/16 by booting into twrp. To boot into twrp recovery turn the tablet on, and keep holding the power button + the Volume key next to the headphone jack until it boots into recovery.
seems the tablet isn't connected in fastboot mode then. You can check with "fastboot devices" command too. Or try "adb devices" and if it shows up there use "adb reboot bootloader".So I've installed adb and fastboot, and i tried this command but it just says "waiting for device." Using lsusb does see a device called "Device 007: (ID no.) MediaTek Inc. Wireless_Device. I'm now out of the brick but if I recall I had to go that route because my OS version was too new. I don't recall ever completing the downgrade or installing twrp either.
sudo apt update sudo add-apt-repository universe sudo apt install python3 python3-serial adb fastboot dos2unix
sudo systemctl stop ModemManager sudo systemctl disable ModemManager
fastboot flash recovery bin/recovery.img
Bus 002 Device 013: ID [b]0e8d:0003[/b] MediaTek Inc. MT6227 phone
Bus 002 Device 014: ID [b]0e8d:2000[/b] MediaTek Inc. MT65xx Preloader
[ 6383.962057] usb 2-2: New USB device found, idVendor=[b]0e8d[/b], idProduct=[b]0003[/b], bcdDevice= 1.00
You'll need a linux distrubution to work from, a live boot cd/usb will work fine.