Anyone willing to "repair" an Onyx Note 2?

[tatteredscroll]

Anyone willing to "repair" an Onyx Note 2? I have some old posts scattered around MobileRead forums with attempts by me to fix what I think was me smashing the loader part of the system during a factory reset.

https://www.mobileread.com/forums/sh...d.php?t=354304

I've connected a USB to TTL Serial Converter to the bits on the board and watch the world scroll by over and over. Have tried power and front panel button combos, etc.

If there's not a reasonable way to fix this (or at least check if it's actually fixable), I'll chalk it up as a loss. But if someone with more skills and experience than me could look at it, restore it to the original (or newest supported firmware, wiped is fine) somehow, I'd like to entertain shipping it to you for repair.

Not sure if @Renate does this, but would trust you with the device. Anyone else?

[Renate]

Mmm, I could probably fix it quicker if it were in my hot little hands, but that may not be practical.
I do have all the equipment here that makes it easier.

But of course we can try it the old way in cyberspace.

[tatteredscroll]

Renate, I'm in the US, I didn't realize you were not "local".

I'm basically back to where I was in the thread linked in my post. USB TTL Serial connected, saving logs in Putty.

I've tried going from powered off state to power on, see blue power light, press and hold Backspace in my Putty session (I see the orange light TX on my converter go orange) and it just loops and reboots.

Rinse and repeat from off state to on and trying different keyboard keys.

[Renate]

Run abltest.exe then reset with a long power press.

[tatteredscroll]

Can't get to EDL with adb reboot edl. Plugging into windows desktop, it never seems to get recognized by the OS.

ADB never sees anything plugged in. I've tried different ports/cables on the desktop. This is with a standard USB cable to USB port, not with my USB serial plug.

[tatteredscroll]

Originally Posted by Renate

Run abltest.exe then reset with a long power press.

abltest output looks a lot like the output I get with my putty session. Should I be looking for something or do we just want to see if it talks?

[tatteredscroll]

link to screenshot upload

https://ibb.co/3nd2hgn

I've taken a lot of screenshots of the scrolling if items like hardware info or bootup info might help, but I never see it go into EDL mode as referenced here. It's pretty much the same as my putty.

https://www.mobileread.com/forums/sh...48&postcount=9

[Renate]

If you run it without the /v it doesn't say the Putty-like stuff, only what you linked.
The screenshot you posted shows that you started abltest too late.
Start abltest, then reset.

Your problem is probably that you just don't have the Windows driver for EDL mode loaded.
Use Zadig or Device Manager and "Show all devices".

[tatteredscroll]

Originally Posted by Renate

If you run it without the /v it doesn't say the Putty-like stuff, only what you linked.
The screenshot you posted shows that you started abltest too late.
Start abltest, then reset.

I thought I tried this. I've gone from powered off state, start abltest, then power on. I've also tried with the light on and scrolling just pressing and holding the button for a looong time. Light goes off, but it just stays off. I'm probably not getting the sequence or timing right.

Your problem is probably that you just don't have the Windows driver for EDL mode loaded.
Use Zadig or Device Manager and "Show all devices".

I installed a driver after plugging in the usb-serial device. Device Manager showed a yellow triangle on the device. So I ran Windows Update, asked to search for driver, it found a driver and installed it at COM3 and appears to be in a normal state.

But what you're saying is a driver that supports EDL mode?? Let me check details on the driver.

FT232R USB UART with the FTDIBUS (v2.12.36.4) that Zadig downloaded and replaced my previous driver.