search

Dragon863 / EchoCLI

A python command line tool for rooting your Amazon Echo dot 2nd generation
94 stars 12 forks source link

Missing Green Ring After Running MTKClient #17

Closed samsieber closed 1 year ago

samsieber commented 1 year ago

I thought I had fastboot on my path but didn't when going to run the step 1.2 of setting the fos_flags, but I didn't. I ran the mtkclient command in a different terminal, and then came back to continue the step 1.2 of main.py (where fastboot is run) and it crashed. I'm not sure if the green light ring came on, but I think it did?

Am I hosed? Retrying the mtkclient command doesn't trigger a green ring of light for me. Here's the output from running that mtclient command while holding the uber button:

MTK Flash/Exploit Client V1.6.3 (c) B.Kerler 2018-2023

Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Port - Device detected :)
Preloader -     CPU:                    MT8163()
Preloader -     HW version:             0x0
Preloader -     WDT:                    0x10007000
Preloader -     Uart:                   0x11002000
Preloader -     Brom payload addr:      0x100a00
Preloader -     DA payload addr:        0x201000
Preloader -     CQ_DMA addr:            0x10212c00
Preloader -     Var1:                   0xb1
Preloader - Disabling Watchdog...
Preloader - HW code:                    0x8163
Preloader - Target config:              0x5
Preloader -     SBC enabled:            True
Preloader -     SLA enabled:            False
Preloader -     DAA enabled:            True
Preloader -     SWJTAG enabled:         True
Preloader -     EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT:  False
Preloader -     Root cert required:     False
Preloader -     Mem read auth:          False
Preloader -     Mem write auth:         False
Preloader -     Cmd 0xC8 blocked:       False
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader -     HW subcode:             0x8a00
Preloader -     HW Ver:                 0xcb00
Preloader -     SW Ver:                 0x1
Preloader - ME_ID:                      D0AD8B8E4D11EDFA60C923007B9699A2
PLTools - Loading payload from mt8163_payload.bin, 0x258 bytes
Exploitation - Kamakiri Run
Exploitation - Done sending payload...
PLTools - Successfully sent payload: /home/sam/dev/capture-echo-dot-2/mtkclient/mtkclient/payloads/mt8163_payload.bin
Port - Device detected :)
Main - Connected to device, loading
Main - Using custom preloader : preloader_no_hdr.bin
Mtk - Valid preloader detected.
Mtk - Patched "Patched loader msg" in preloader
Main - Sent preloader to 0x201000, length 0x22408
Preloader - Jumping to 0x201000
Preloader - Jumping to 0x201000: ok.
Main - PL Jumped to daaddr 0x201000.
Main - Keep pressed power button to boot.

Trouble shooting steps I've taken so far:

samsieber commented 1 year ago

Part of me thinks that I broke the ribbon cable between the top button/microphone section or something because I get absolutely zero lights ever, and I get the same behavior output from mtkclient even when I don't hold down the button. But if someone wanted to / could confirm if there's a visible behavior difference between holding down the uber button and not (in terms of the mtkclient output) that would be great.

Dragon863 commented 1 year ago

Hello! This seems to be common behaviour from firmware 5.x devices which it seems are not patched correctly. The ribbon cable is most likely fine (I should know, I've knocked my echo from my desk twice without the case on!). I'd recommend that you use the restore option of EchoCLI to reflash the original software, then ask Alexa to update. Once it has upgraded to FireOS 6, try again and it should be good to go

samsieber commented 1 year ago

That's wonderful news! Thank you so much!!! I do see now a similar issue at https://github.com/Dragon863/EchoCLI/issues/16; I only realized there were other closed issues after you replied. Thanks again, I'll close this :)