Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need help with connecting the device, thanks! #614

Open
thememika opened this issue Jan 4, 2025 · 0 comments
Open

Need help with connecting the device, thanks! #614

thememika opened this issue Jan 4, 2025 · 0 comments

Comments

@thememika
Copy link

Hello!
I have a Xiaomi device with Snapdragon 680 4G, that I've bricked in a tricky way when I needed to alter the partition table, it was out of free GPT entries and I thought it is fine to delete some _b partitions since I only use the A slot. But after I deleted vbmeta_system_b it will always freeze on boot, with screen lighted up (not black), but no Logo and no Fastboot.
When I just connect it to an x86 host (linux), there is no reaction (regardless of pressed buttons, power button hard reboot, etc).
I cut a charging cable open and cleaned Green and Black wires from protection. Then I've shorted them together and plugged the cable to host. Immediately when the screen went black (from power button press, in reboot phase), I would release the wires from each other.
At first nothing happens, but when I retried it dozens of times, I suddenly got a reaction on the host's console!

[616698.854580] [T11042] usb 2-1.6.1.1: new full-speed USB device number 114 using ehci-pci
[616698.919566] [T11042] usb 2-1.6.1.1: device descriptor read/64, error -32
[616699.088559] [T11042] usb 2-1.6.1.1: device descriptor read/64, error -32
[616699.192748] [T11042] usb 2-1.6.1-port1: attempt power cycle
[616699.771551] [T11042] usb 2-1.6.1.1: new full-speed USB device number 115 using ehci-pci
[616700.184567] [T11042] usb 2-1.6.1.1: device not accepting address 115, error -32
[616700.184689] [T11042] usb 2-1.6.1-port1: unable to enumerate USB device

But unfortunately it always fails to enumerate device. I was able to get this few more times, and the behavior is always the same. new device -> error -> power cycle -> new device -> not accepting address.
Device quickly starts again and freezes with the screen on.
I know unix Error 32 is EPIPE/Broken pipe, and this is from my host kernel Docs about its meaning for USB:

-EPIPE [2] Endpoint stalled.
This is also one of several
codes that different kinds of host controller use to indicate a transfer has failed because of device
disconnect. In the interval
before the hub driver starts disconnect processing, devices may receive such fault reports for every request.

Yet I don't know what is happening besides the device disconnecting immediately.

Do you know some different way to connect the device, or what could I be doing wrong (I know testpoint but I don't want to disassemble).

Thank you for any help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant