MobileRead Forums - View Single Post - Help to replace broken screen Glo HD 2015

davidfor · 10-19-2017, 06:47 AM

My first reaction is that using another image isn't going to work. But, if any worked, it will be from the Touch 2. They appear to be identical except for the screen. Unfortunately, that would probably only use 800x600 pixels on the screen you have.

And I think the Aura Edition 2 is more likely to work than the Glo. It is the same resolution and it is in the same mark family as the Glo HD.

And you might get away with just writing the u-boot from the appropriate device. The firmware does detect the hardware, but it also reads the start of the SD card. etc/init.d/rc5 has:

Code:

if [ `dd if=/dev/mmcblk0 bs=512 skip=1024 count=1 | grep -c "HW CONFIG"` == 1 ]; then
	CPU=`ntx_hwconfig -s -p /dev/mmcblk0 CPU`
	PLATFORM=$CPU-ntx
	WIFI=`ntx_hwconfig -s -p /dev/mmcblk0 Wifi`
fi

Which, if I read it right, is reading near the start of the SD to get hardware information the hardware information. I can see "HW CONFIG" in the u-boot files. It might be enough to restore the u-boot image. Using the matching kernel might be needed as well, but I don't know.

And if it is using the hardware resolution from the u-boot file, it might be possible to change the resolution in the u-boot file for the Glo HD, and use that.

10-19-2017, 06:47 AM	#12
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	My first reaction is that using another image isn't going to work. But, if any worked, it will be from the Touch 2. They appear to be identical except for the screen. Unfortunately, that would probably only use 800x600 pixels on the screen you have. And I think the Aura Edition 2 is more likely to work than the Glo. It is the same resolution and it is in the same mark family as the Glo HD. And you might get away with just writing the u-boot from the appropriate device. The firmware does detect the hardware, but it also reads the start of the SD card. etc/init.d/rc5 has: Code: if [ `dd if=/dev/mmcblk0 bs=512 skip=1024 count=1 \| grep -c "HW CONFIG"` == 1 ]; then CPU=`ntx_hwconfig -s -p /dev/mmcblk0 CPU` PLATFORM=$CPU-ntx WIFI=`ntx_hwconfig -s -p /dev/mmcblk0 Wifi` fi Which, if I read it right, is reading near the start of the SD to get hardware information the hardware information. I can see "HW CONFIG" in the u-boot files. It might be enough to restore the u-boot image. Using the matching kernel might be needed as well, but I don't know. And if it is using the hardware resolution from the u-boot file, it might be possible to change the resolution in the u-boot file for the Glo HD, and use that.