View Single Post
Old 01-19-2022, 07:24 PM   #3
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
@BatteryPowered: The images I have are all taken after a factory reset. That means that the one I have for the Aura HD would be at firmware 2.5 like your devices.

The WiFi connectivity issue is because in early 2019 Kobo had to remove older security protocols from their servers as they were no longer considered to be secure. You could still setup the older devices using the Kobo desktop application or by manually installing newer firmware.

But, if the USB connection is not working, you cannot do either of these. And it is very unlikely that an image will fix anything. If the device is booting to the point were you can tell that WiFi is not connecting, then the device is probably OK from that side. The issue is probably the USB hardware (port or cable) or an issue on the PC. Does the device or PC react at all when you plug it in? Does the battery charge?

Something you could try is to take the SD card out and copy the firmware update files directly to the card. You need to put them in the ".kobo" directory of the books partition. These are normally handled when the device is disconnected from the PC. They don't normally get processed when the device is booted, but, if it is in the setup state, it might happen. Or if there is some connectivity when plugging in to the USB port, it might happen when the device is disconnected.

I can supply the image if you want, but, at this point, I don't think it will help.
davidfor is offline   Reply With Quote