Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader

Notices

Reply
 
Thread Tools Search this Thread
Old 09-22-2015, 12:52 AM   #1
PamNawi
Junior Member
PamNawi began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Sep 2015
Device: Kobo Glo N613
Question Kobo glo reboot loop

Hi people ,

My kobo glo is on a infinite loop and I really don't know what to do. After some months without using my kobo I put him on a charger and turn it on. Some downloads later (.epub and some .pdfs, nothing especial) he asked if I wanted to make a update of the firmware (I don't know what version, but probably will be the last?), I accepted, and then I put in the side. On the other day he was in the infinity loop. He asks to be connected with PC and then he start a restoration routine, then after the restoration he asks again to be connected with PC...

He just make the loop with this 2 screens:
Spoiler:





I made some manual factory reset, I pushed the bottom button and nothing happens. I called the kobo on fb, but this guy is to old for warranty so they said to wait to the battery drain. He was almost full charge when this started, and probably has recover some battery while I tryed to connect him to my PC so that would take too long. I can't do anything, no menus, no connection with PC, no detection from my PC (on win7 or win10), so no access in a friendly mode to the files.

I opened his back and take off his internal microSD card, put on my computer but I can't read what is inside and I'm too afraid to make something wrong with that. I read some about exchange the image from the microSD for a new one. Is this a case of that?

Thank you and sorry about my bad english, is not my mother language.

Last edited by Dr. Drib; 09-23-2015 at 05:33 AM.
PamNawi is offline   Reply With Quote
Old 09-22-2015, 06:25 AM   #2
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
You could check the SD card for defects (read errors) maybe you just need a new one.

If you have it open anyway you could disconnect the battery to simulate a hard power off without waiting for the battery to actually run out entirely. Although I'm not sure how/why that would fix things.

The only thing I can think of that would cause reboots is sickel, but that should be gone after a factory reset so ... unless performing firmware update is part of the loop, i.e. you're registering with Kobo every time ... not really sure what's going on with your device. Good luck.
frostschutz is offline   Reply With Quote
Advert
Old 09-22-2015, 11:55 AM   #3
PamNawi
Junior Member
PamNawi began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Sep 2015
Device: Kobo Glo N613
Quote:
You could check the SD card for defects (read errors) maybe you just need a new one.

If you have it open anyway you could disconnect the battery to simulate a hard power off without waiting for the battery to actually run out entirely. Although I'm not sure how/why that would fix things.

The only thing I can think of that would cause reboots is sickel, but that should be gone after a factory reset so ... unless performing firmware update is part of the loop, i.e. you're registering with Kobo every time ... not really sure what's going on with your device. Good luck.
Thank you, I'm too afraid to simulate a hard power off, so I removed the microSD card and put the device on the side. My theory is that a problem of software, not hardware, so it's better I don't mess with hardware device.

I have some news, but I really don't know the consequences of what I found. I mounted a virtual machine with ubuntu on my notebook and plugged the microSD. The ubuntu see the 3 partitions (KOBOeReader, recoveryfs and rootfs). The KOBOeReader partition seems to be empty. While the recoveryfs and rootfs has some files. I'm posting the terminal images.

[Images violate Posting Guidelines for size - MODERATOR]

My conclusion is the microSD is not corrupt, probably the files on him is. I tryed to make some operations (I have a backup made with USB Image Tool) but I have no permissions. Anyone has a ideia? I'm not really familiar with linux maybe I'm missing something

Ah! I tryed to make a factory reset without the microSD. He just don't respond. When I put the microSD back he still continues the loop.

Last edited by Dr. Drib; 09-23-2015 at 05:34 AM.
PamNawi is offline   Reply With Quote
Old 09-22-2015, 12:54 PM   #4
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
It's normal for KOBOeReader to be empty after a factory reset. These files will be created on the first boot.

You should not touch the recoveryfs, if you modify that factory resets will no longer work.

As for the rootfs you could check if there is a file usr/local/Kobo/sickel - if the factory reset worked it should not be there.

If nothing else works you might need a Kobo Glo SD card image from someone else.

Did you install firmware manually and picked the wrong markX?
frostschutz is offline   Reply With Quote
Old 09-22-2015, 02:34 PM   #5
PamNawi
Junior Member
PamNawi began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Sep 2015
Device: Kobo Glo N613
Quote:
Originally Posted by frostschutz View Post
It's normal for KOBOeReader to be empty after a factory reset. These files will be created on the first boot.

You should not touch the recoveryfs, if you modify that factory resets will no longer work.

As for the rootfs you could check if there is a file usr/local/Kobo/sickel - if the factory reset worked it should not be there.

If nothing else works you might need a Kobo Glo SD card image from someone else.

Did you install firmware manually and picked the wrong markX?
The firmware install was call and made automatically from wifi, so I don't have any idea what happened to him while I was sleeping =/. Maybe the wifi was gonne down??? I don't know..

I see this post : http://www.mobileread.mobi/forums/sh...=194206&page=2

And executed this commands:
Code:
rm -rf /media/rootfs/*
cd /media/rootfs/
tar xvzf /media/recoveryfs/upgrade/fs.tgz
So I ejected the microSD, put back in the device and restart everything. It works!!!!

Now I have a new problem . I configurate the device connecting him to my PC and using Kobo desktop. Everything on the screen seems to be less black. Has more ghosts too. Maybe I messed up with the hardware while I was trying to get the microSD working??? Or maybe something weird about the files exchange on the microSD????

I got the firmware version now: 3.17.3
PamNawi is offline   Reply With Quote
Advert
Old 09-23-2015, 02:49 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 PamNawi View Post
The firmware install was call and made automatically from wifi, so I don't have any idea what happened to him while I was sleeping =/. Maybe the wifi was gonne down??? I don't know..

I see this post : http://www.mobileread.mobi/forums/sh...=194206&page=2

And executed this commands:
Code:
rm -rf /media/rootfs/*
cd /media/rootfs/
tar xvzf /media/recoveryfs/upgrade/fs.tgz
So I ejected the microSD, put back in the device and restart everything. It works!!!!
You were lucky that it was something on the rootfs that was messed up and not the kernel. You can restore this with a dd command, but I think restoring an image is easier.
Quote:
Now I have a new problem . I configurate the device connecting him to my PC and using Kobo desktop. Everything on the screen seems to be less black. Has more ghosts too. Maybe I messed up with the hardware while I was trying to get the microSD working??? Or maybe something weird about the files exchange on the microSD????

I got the firmware version now: 3.17.3
One of the complaints about the recent firmware on the Glo is that there is more ghosting than before. I think this started with 3.15.0 (or maybe that's the last "good" one) with more ghosting behind the pop-ups when reading. I think this has improved with the later firmware, but I don't use my Glo enough to be sure.
davidfor is offline   Reply With Quote
Old 09-23-2015, 05:36 AM   #7
Dr. Drib
Grand Sorcerer
Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.Dr. Drib ought to be getting tired of karma fortunes by now.
 
Dr. Drib's Avatar
 
Posts: 45,309
Karma: 59447733
Join Date: Jan 2007
Location: Peru
Device: KINDLE: Oasis 3, Scribe (1st), Matcha; KOBO: Libra 2, Libra Colour
Moderator Notice

PamNawi
Please take a few moments to read our Posting Guidelines, in particular the part about the maximum image size allowed (600x600 pixels). Images that violate those guidelines will be deleted.

It is every member's responsibility to read our Posting Guidelines and follow them.

Thanks.
Dr. Drib is offline   Reply With Quote
Reply

Tags
firmware backup, firmware update, infinite loop, kobo glo freezes


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
PRS-T1 Help? Endless reboot loop with spinning arrows bookEmonster Sony Reader 0 03-25-2015 04:18 PM
Aura HD infinite loop reboot tuxpeppe Kobo Reader 1 09-01-2013 01:36 PM
Glo KOBO GLO SPONTANEOUS REBOOT jackastor Kobo Reader 89 10-20-2012 12:35 AM
Stuck in wierd reboot loop aditya3098 Kindle Developer's Corner 6 09-12-2012 06:54 AM
Edge Reboot Loop nikkie enTourage eDGe 22 10-08-2011 07:12 PM


All times are GMT -4. The time now is 11:21 AM.


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