View Single Post
Old 06-25-2017, 04:00 PM   #16
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
I did not try to match systematically the PCB values with models, but my list for code names, model identification numbers (as used for determining the FW update file) and product ids is as follows:

trilogy 310 Kobo Touch 0x4163
trilogy 320 Kobo TouchC 0x4163
kraken 330 Kobo Glo 0x4173
pixie 340 Kobo Mini 0x4183
dragon 350 AuraHD 0x4193
phoenix 360 Aura 6" 0x4203
dahlia 370 AuraH2O 0x4213
alyssum 371 GloHD 0x4223
pika 372 Touch 2 0x4224
daylight 373 Aura One 0x4225
snow 374 Aura H2O 2 0x4227
star 375 Aura Edition 2 0x4226

Sure, I might be wrong.

Last edited by tshering; 06-25-2017 at 04:03 PM.
tshering is offline   Reply With Quote