Quote:
Originally Posted by Renate
Well, if that's all you get on a cold boot it's not going to help.
You need:
1) EDL cable (might not work if the abl is damaged)
2) Find the internal test points.
|
I think I'm connected to the test points ??? with my USB TTL gizmo. I'm connected (tx, rx, and gnd) and that is connected to my USB TTL converter and it shows up as COM3. That's been the ONLY way I can communicate with the Note 2. All the logs I've posted are from that internal connection. The USB-C port on the bottom of the device does nothing. I never hear windows ding-dong or see anything show up in Device Manager.
Or are test points something else to look for?
If abltest is meant to talk to the Note 2 via the USB-C port on a device that is operating more normally than mine, then I reckon it ain't going to work. I get nothing when plugging into the USB-C port on the bottom of the Note 2 connected to my PC. I have the Google provided USB drivers for the SDK/adb installed. Nothing shows up in Device Manager, no ding-dong from windows that a new device connected.
Test on my linux machine as well. With dmesg -w looking for any changes while plugging in, unplugging the Note 2 via its USB port. Through several bootloop cycles, never registers as "seen" by linux.
I don't have an EDL cable, but I can order one. Is this to force it into emergency mode?
Is this right? 9008 mode?
https://www.amazon.com/Mobile-Phone-...=sr_1_6?sr=8-6
https://cablematic.com/en/products/e...chipset-MH041/