MobileRead Forums - View Single Post - Onyx Boox Kon-Tiki 2 (Nova3 platform)

Renate · 08-10-2021, 10:00 PM

The first thing is that the Sahara protocol (the initial protocol that runs out of the ROM) is stupid.
It's easy to get out of sync and have it stall.
That means, when you're experimenting and having problems it's best to do a hard reset then go to EDL mode fresh as an incomplete operation leaves it vegged.

The elf that I use (for Qualcomm 636) is this one:
https://github.com/bkerler/Loaders/b..._bqx2_peek.bin
The MD5 is 0f159e0b43ad95974e4ce507ee362aec

I remember there was another problem with a missing/incompatible DLL that wasn't error-messaged out very clearly.
Do you have something recent here:

Code:

Directory of C:\Windows\System32
12/11/2020  03:00           166,912 libusb-1.0.dll

08-10-2021, 10:00 PM	#18
Renate Onyx-maniac Posts: 3,992 Karma: 18026955 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	The first thing is that the Sahara protocol (the initial protocol that runs out of the ROM) is stupid. It's easy to get out of sync and have it stall. That means, when you're experimenting and having problems it's best to do a hard reset then go to EDL mode fresh as an incomplete operation leaves it vegged. The elf that I use (for Qualcomm 636) is this one: https://github.com/bkerler/Loaders/b..._bqx2_peek.bin The MD5 is 0f159e0b43ad95974e4ce507ee362aec I remember there was another problem with a missing/incompatible DLL that wasn't error-messaged out very clearly. Do you have something recent here: Code: Directory of C:\Windows\System32 12/11/2020 03:00 166,912 libusb-1.0.dll