Chromebook ID List Outdated - GSM-Forum

JEF1056 · 07-06-2020, 15:58

HDBox is quite a great product, and I've been using it to unlock quite a few chromebooks (particularly the Samsung XE303 variant(s))

However, I encountered a major issue; the chromebook unlocking software checks the chip id before reading or writing, but does not have a proper or complete list of flashchips used by manufacturers, found in google's flashchips.h.

As such, the chromebooks with winbond chips (again, specifically of the XE303 variant) work with HDBox, while the same model of chromebooks with chips from gigadevice fail to be recognized.

The winbond chips show up as

Code:

00 EF 60 16 (W25Q32DV - 4 MB)

, shown on line 966 of flashchips.h but gigadevice chips show up as

Code:

00 C8 60 16  (UNKNOWN ID)

when it exists on line 398 of flashchips.h

It would be immensely helpful to create a way where users can upload/use their own lists of recognized IDs for chips so that this issue wouldn't occur. As seen above, even their architectures and sizes

Code:

60 16

are the same; in theory, even if the image from the winbond chip were directly copied to the gigadevice chip, the functionality of the chromebook would be fine.

Please consider removing the ID check or just checking if it's

Code:

00 00 00 00

(disconnected) or the ids in line 33-37 of flashchips.h (dummy chips and null ids).

Note: I was unable to include links in this post due to the unnecessary restrictions; please ask if you need to see the link to flashchips.h

07-06-2020, 15:58	#1 (permalink)
JEF1056 Junior Member Join Date: Jun 2020 Location: San Martin Posts: 1 Member: 2960843 Status: Offline Thanks Meter: 0	Chromebook ID List Outdated HDBox is quite a great product, and I've been using it to unlock quite a few chromebooks (particularly the Samsung XE303 variant(s)) However, I encountered a major issue; the chromebook unlocking software checks the chip id before reading or writing, but does not have a proper or complete list of flashchips used by manufacturers, found in google's flashchips.h. As such, the chromebooks with winbond chips (again, specifically of the XE303 variant) work with HDBox, while the same model of chromebooks with chips from gigadevice fail to be recognized. The winbond chips show up as Code: 00 EF 60 16 (W25Q32DV - 4 MB) , shown on line 966 of flashchips.h but gigadevice chips show up as Code: 00 C8 60 16 (UNKNOWN ID) when it exists on line 398 of flashchips.h It would be immensely helpful to create a way where users can upload/use their own lists of recognized IDs for chips so that this issue wouldn't occur. As seen above, even their architectures and sizes Code: 60 16 are the same; in theory, even if the image from the winbond chip were directly copied to the gigadevice chip, the functionality of the chromebook would be fine. Please consider removing the ID check or just checking if it's Code: 00 00 00 00 (disconnected) or the ids in line 33-37 of flashchips.h (dummy chips and null ids). Note: I was unable to include links in this post due to the unnecessary restrictions; please ask if you need to see the link to flashchips.h