View Single Post
Old 05-11-2017, 10:18 AM   #6
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
Quote:
Originally Posted by greshnik View Post
Thanks, got the link. Will try it tonight. When you say 'a while' how long should it be? I was waiting for several minutes, should I wait longer?
Several minutes should be enough. But, this is the sort of thing I would leave as long as possible to see if something happens.
Quote:
Yeah, PC sees it, and I am not sure what to make out of the wrong device type.
I tried all resets already, neither worked. I guess, it might be a hardware malfunction after all, just not visible to naked eye. I will try the image just in case and I will let you know if it did anything at all.
Btw, I certainly appreciate your help, even if it doesn't fix my reader, I am still very grateful for your efforts.
It could be a damaged substrate in the screen. Usually you can see the problem, but sometimes it isn't obvious from the front. Looking at the back of the screen can show the damage. But, the other symptoms don't really suggest this.
davidfor is offline   Reply With Quote