Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader > Kobo Developer's Corner

Notices

Closed Thread
 
Thread Tools Search this Thread
Old 03-01-2017, 12:08 AM   #751
meeera
Grand Sorcerer
meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.meeera ought to be getting tired of karma fortunes by now.
 
meeera's Avatar
 
Posts: 5,815
Karma: 68407974
Join Date: Dec 2011
Location: Australia
Device: Kobo Libra 2, iPadMini4, iPad4, MBP; support other Kobo/Kindles
Quote:
Originally Posted by luke73 View Post
At the moment it's showing a book cover and a little windows that says it's OFF.
Quote:
Originally Posted by luke73 View Post
[photo very clearly showing a smashed screen]
You are going to be wasting a whole lot of your own time (and that of others trying to help you) by omitting information like this. So many people here open their devices and muck about with the SD cards and batteries and etc, when the screen is broken and no amount of technical fiddling will change that. I wonder why the screen artifacts are so often ignored or omitted from the troubleshooting info given - even when the person describes other aspects of what is showing on the screen? Not aimed at you specifically; this happens a lot, and I just can't figure out why, or how the process can be improved.
meeera is offline  
Old 03-01-2017, 01:04 AM   #752
luke73
Junior Member
luke73 began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Feb 2017
Device: kobo glo hd
I'm sorry but I didn't foresee a broken screen.
I'm new to e-paper screen and I was thinking of a sort of last memorized page that was degrading in time.

There is no external sign of impact on the screen or the case (take a look at the images). The owner didn't talked about an incident, only about a frozen reader.

I'will report on the logs, I imagine that the boot should appear standard but no reacting screen.

Thanks
Attached Thumbnails
Click image for larger version

Name:	IMG_7847.JPG
Views:	142
Size:	531.2 KB
ID:	155363   Click image for larger version

Name:	IMG_7846.JPG
Views:	192
Size:	962.1 KB
ID:	155364  
luke73 is offline  
Advert
Old 03-01-2017, 02:05 AM   #753
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 luke73 View Post
I'm sorry but I didn't foresee a broken screen.
I'm new to e-paper screen and I was thinking of a sort of last memorized page that was degrading in time.

There is no external sign of impact on the screen or the case (take a look at the images). The owner didn't talked about an incident, only about a frozen reader.

I'will report on the logs, I imagine that the boot should appear standard but no reacting screen.
Those images clearly show a broken substrate. If you do a search here or elsewhere, you will find many readers of all brands with broken screens looking the same.

How it was broken, I don't know, I'd be tempted to think something sharp hit it near the end of the light area going across the screen. But, it might have been something else. And it might have been gradual. If there was bad bump on the screen, it can start a crack you can't see and then twisting the device a bit while using can extend it. Until you get what you are seeing.
davidfor is offline  
Old 03-03-2017, 10:13 AM   #754
luke73
Junior Member
luke73 began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Feb 2017
Device: kobo glo hd
Here I am,
I finally got the serial converter and read the boot log from the console ...

The log is attached but here is the evidence:

#########

U-Boot 2009.08-00784-ge26a520-dirty-svn2940 ( 1æ 13 2015 - 14:27:41)

CPU: Freescale i.MX6 family TO0.0 at 792 MHz
Temperature: 29 C, calibration data 0x57c5015f

...(omitted)...

Starting kernel ...

drivers/misc/ntx-misc.c(msp430_i2c_probe): Can't allocate irq 395
[zForce_ir_touch_recv_data-259] command BootComplete (0)...
PMU: ricoh61x_battery_probe : version is RICOH61x_BATTERY_VERSION: 2014.02.21 V3.1.0.0-Solution1 2015/02/09
drivers/video/mxc/lk_tps65185.c(568):tps65185_int_func under-voltage on VEE charge pump detected !

#######

The last message is repeated continuously intervalled by a line like:

drivers/video/mxc/lk_tps65185.c(1380):wait power on timeout lpcnt=0!

in which lpcnt counts up each 36 messages til

cannot open /dev/nulldrivers/video/mxc/lk_tps65185.c(568):tps65185_int_func under-voltage on VEE charge pump detected !

then we got

dosfsck 3.0.6, 04 Oct 2009, FAT32drivers/video/mxc/lk_tps65185.c(568):tps65185_int_func under-voltage on VEE charge pump detected !
, LFN
There are differences between boodrivers/video/mxc/lk_tps65185.c(568):tps65185_int_func under-voltage on VEE charge pump detected !
t sector and its backup.
Differences: (offset: original/backup)
drivers/video/mxc/lk_tps65185.c(568):tps65185_int_func under-voltage on VEE charge pump detected !
489:8d/00, 490:ef/00, 491:02/00, 492:d2/00, 494:ff/00, 495:ff/0drivers/video/mxc/lk_tps65185.c(568):tps65185_int_func under-voltage on VEE charge pump detected !
0, 496:ff/00
, 497:ff/00, 498:ff/00, 499:ff/00, 500:ff/00, 501drivers/video/mxc/lk_tps65185.c(568):tps65185_int_func under-voltage on VEE charge pump detected !
:ff/00, 502:ff/00
, 503:ff/00, 504:ff/00, 505:ff/00, 506:ff/00drivers/video/mxc/lk_tps65185.c(568):tps65185_int_func under-voltage on VEE charge pump detected !
, 507:ff/00, 508:ff/00
, 509:ff/00
Not automatically fixingdrivers/video/mxc/lk_tps65185.c(568):tps65185_int_func under-voltage on VEE charge pump detected !
this.

So it clearly shows up an hardware error.
It seems a problem on the negative voltage (VEE) converter in the e-paper display power supply IC (TPS65185) not reaching the right level (-20V).

Attached Files
File Type: txt boot.txt (143.5 KB, 129 views)
luke73 is offline  
Old 03-03-2017, 04:31 PM   #755
luke73
Junior Member
luke73 began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Feb 2017
Device: kobo glo hd
And then,
removed the motherboard ...

found the broken display ....

OK, I leave.
...

Thanks to all of you for your time.
Bye
G
Attached Thumbnails
Click image for larger version

Name:	IMG_7861.JPG
Views:	160
Size:	413.0 KB
ID:	155434   Click image for larger version

Name:	IMG_7862.JPG
Views:	179
Size:	366.5 KB
ID:	155435  
luke73 is offline  
Advert
Old 03-24-2017, 02:29 AM   #756
Crashworthy
Junior Member
Crashworthy began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Mar 2017
Location: Canberra, AU
Device: Kobo Glo
Hi, Daughter powered down her Kobo during an update. Now bricked. Could I please request an image?
Crashworthy is offline  
Old 03-24-2017, 02:40 AM   #757
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
PM sent.

You should try a manual factory reset before opening the Glo. The time period where powering the device off would prevent a factory reset from working is pretty small. There's a good chance this will get the device going and you won't need to open the device.
davidfor is offline  
Old 03-25-2017, 12:24 PM   #758
knubo
Junior Member
knubo began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Mar 2017
Device: Kobo glo
Hi, my Kobo glo is bricked. Cuold I please request the image to ?
Thank´s in advice.
knubo is offline  
Old 03-25-2017, 08:09 PM   #759
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
PM sent.
davidfor is offline  
Old 03-28-2017, 06:10 PM   #760
sekenon
Junior Member
sekenon began at the beginning.
 
Posts: 2
Karma: 10
Join Date: Mar 2017
Location: Netherlands
Device: Kobo Aura HD
Hello, just spent hours trying to read the SD card from a Kobo Glo HD. My daughter too interrupted a firmware update and bricked it. Hopefully flashing a new image is easier than fiddling around with the SD card. Could you please provide one? Thanks in advance.
sekenon is offline  
Old 03-28-2017, 08:22 PM   #761
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
PM sent. But...

Have you tried a manual factory reset? You would have to be very unlucky to interrupt the install at a point that would break this.
davidfor is offline  
Old 03-28-2017, 08:46 PM   #762
AkiraReader
Connoisseur
AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.AkiraReader ought to be getting tired of karma fortunes by now.
 
Posts: 83
Karma: 1873672
Join Date: Feb 2015
Device: Boox, Kindles
51 pages of people needing the image? Is this device a piece of s*** or something?
AkiraReader is offline  
Old 03-28-2017, 09:31 PM   #763
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 AkiraReader View Post
51 pages of people needing the image? Is this device a piece of s*** or something?
51 pages over four years. That's 763 posts (including yours). As about half the posts are "PM sent", that's at most 382 requests. It's less because there is some discussion. And there are people who didn't need it, just didn't know how to reset the device properly. And some from people who deliberately did something that messed it up (such as install Android) But, if we stick to 763 requests, what percentage of Kobo Glo's do you think that represents?

No, it is not a piece of s***. It was an excellent ereader and easily outclassed the Kindles that were available when it was released. And, as an added bonus, it was constructed in a way that made it easy to recover from what would be a complete disaster for other devices.
davidfor is offline  
Old 03-28-2017, 09:38 PM   #764
kdog1975
Junior Member
kdog1975 began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Mar 2017
Device: Kobo Glo
My Kobo Glo is bricked. Can someone please send me the factory SD image?
kdog1975 is offline  
Old 03-28-2017, 10:14 PM   #765
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
PM sent.
davidfor is offline  
Closed Thread


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Vox Kobo Vox memory card image - Fix tablet upgrade error and more pcampbell Kobo Tablets 76 05-05-2020 12:11 PM
Glo Kobo Glo: how to replace boot image elpaso Kobo Developer's Corner 12 05-08-2013 11:09 AM
Glo Can kobo glo run android app such as nook glo? suspect Kobo Developer's Corner 1 12-28-2012 11:25 PM
Kobo Glo SD card support maxime Devices 2 12-16-2012 07:09 AM
Image remaining on Glo - help! Richard Moody Kobo Reader 4 12-04-2012 08:28 AM


All times are GMT -4. The time now is 03:21 PM.


MobileRead.com is a privately owned, operated and funded community.