My joggler reboots at 5-minute intervals

[rockuad]

My joggler reboot at 5-minute intervals when it connects the wireless.
It's OK without the wireless connection.

Joggler is working on origin system S3.

This issue won't occur when joggler is working on ubuntu or android.

My friend has 4 jogglers.One of them has the same issue!

The others is working well.

Who can help us?

[danjog2]

Hi

I've got a similar problem, roobarb! is helping out on the reflashing joggler thread

[rockuad]

Hi

I've got a similar problem, roobarb! is helping out on the reflashing joggler thread

Excuse me. I can't understand.
Can you help me?
You will be appreciated very much if you help me to solve my issue.

[roobarb!]

I think we should make this the home thread for this issue. I've not got any progress to report at the moment, but it makes sense to concentrate the work here.

[rockuad]

My issue is solved!!!!!

The reason of joggler reboot is the joggler update firewarm automaticly in backstage.

The joggler will reboot when the it connect internet via the wireless and update the firewarm completely.

Many friends have the same issue.

If you flash the joggler the new firewarm version without updating automatic from the old firewarm version, the issue will occur.

So the solving way is back to the old firewarm version , then let the joggler update firewarm automaticly.

If your joggler is failed to update automaticly, you can update the firewarm manually.

Remember , you must update instead of flash others img or system.

You can flash Ubuntu ,android or orgin system etc when you complete updating.

Good lucky!

[danjog2]

Hi

Thanks for this, I guess you mean that we are trying to flash memory with a firmware version that is too new for the joggler. Your solution is to flash the joggler with older or original firmware then allow the joggler to update itself. If the joggler doesn't update the firmware automatically (say after 24 hours) then we should apply a manual update (possibly via telnet?)

Roobarb! Can you comment on this please?

Thanks

[roobarb!]

So, the 5 minute reboot problem has occurred after reflashing? I'm presuming you mean using my reflashing tool, or do you mean using some other method?

What process do you use to reflash manually?

@danjog2 Was your Joggler at the latest firmware revision before you tried reflashing it with my reflash tool for the first time?

[danjog2]

Hi

The last successful update I got from o2 was the one that gave us the official App Shop for the first time. I'm sorry I don't know what revision that was. I then put PMJ on it, installed some games etc. It's possible that it received one more update which is what triggered the booting problem, but it was probably about 8 months ago at a guess.

[roobarb!]

The last successful update I got from o2 was the one that gave us the official App Shop for the first time. I'm sorry I don't know what revision that was. I then put PMJ on it, installed some games etc. It's possible that it received one more update which is what triggered the booting problem, but it was probably about 8 months ago at a guess.

I'm not sure, but I think 26635.S3 brought with it the App Shop. Sorry if you've already told me this, but did the rebooting problem begin after reflashing with my reflash tool, or was it present beforehand? Just trying to rule things out.

Okay, let's try another couple of things. Log back in to your Joggler and post the output of these two again, just to check.

Code: Select all

cat /etc/firmware.ver 
cat /etc/software.ver

They should be 8686.S3 and 26635.S3 respectively. Then try this:

Code: Select all

mount -o ro /dev/mmcblk0p1 /efi
ls /efi
cat /efi/action
cat /efi/sum0
cat /efi/sum1

Let me know what the output of all of that is.

And while you're there, could you also post the output of:

Code: Select all

cat /openpeak/tango/xinit.sh

There'll be a fair bit to that one. It's the script you modified a while back, but it would be interesting to see if the changes stuck. It's also the only file I know of that definitely runs after 5 minutes of uptime, so it's a prime candidate for tweaking at the moment.

[Mozza]

What if my Joggler reboots instantly when fully loaded and doesn't give you time to telnet?

Cheers

Mozza

[roobarb!]

What if my Joggler reboots instantly when fully loaded and doesn't give you time to telnet?

Is it connected to a network with an ethernet cable? Does it give you a message before it reboots?

Disconnect it from the network and turn it on - see if it still reboots. If it does, it's a different problem. If it doesn't, it's grabbing something from the internet that is causing the reboot and you'll need to disconnect from the 'net to enable SSH and get in there to look around.

[danjog2]

The last successful update I got from o2 was the one that gave us the official App Shop for the first time. I'm sorry I don't know what revision that was. I then put PMJ on it, installed some games etc. It's possible that it received one more update which is what triggered the booting problem, but it was probably about 8 months ago at a guess.

I'm not sure, but I think 26635.S3 brought with it the App Shop. Sorry if you've already told me this, but did the rebooting problem begin after reflashing with my reflash tool, or was it present beforehand? Just trying to rule things out.

Okay, let's try another couple of things. Log back in to your Joggler and post the output of these two again, just to check.

Code: Select all

cat /etc/firmware.ver 
cat /etc/software.ver

They should be 8686.S3 and 26635.S3 respectively. Then try this:

Code: Select all

mount -o ro /dev/mmcblk0p1 /efi
ls /efi
cat /efi/action
cat /efi/sum0
cat /efi/sum1

Let me know what the output of all of that is.

And while you're there, could you also post the output of:

Code: Select all

cat /openpeak/tango/xinit.sh

There'll be a fair bit to that one. It's the script you modified a while back, but it would be interesting to see if the changes stuck. It's also the only file I know of that definitely runs after 5 minutes of uptime, so it's a prime candidate for tweaking at the moment.

Thanks for this, my telnet connection seems very unstable, is there a way to run this code in a terminal window in ubuntu on the joggler?

[roobarb!]

Thanks for this, my telnet connection seems very unstable, is there a way to run this code in a terminal window in ubuntu on the joggler?

Yup. You need to mount each partition individually under Ubuntu:

Code: Select all

sudo mount /dev/mmcblk0p2 /mnt
cat /mnt/etc/firmware.ver 
cat /mnt/etc/software.ver
cat /openpeak/tango/xinit.sh
sudo umount /mnt

Then the same for the backup:

Code: Select all

sudo mount /dev/mmcblk0p3 /mnt
cat /mnt/etc/firmware.ver 
cat /mnt/etc/software.ver
cat /openpeak/tango/xinit.sh
sudo umount /mnt

Then the boot partition:

Code: Select all

mount -o ro /dev/mmcblk0p1 /mnt
ls /efi
cat /efi/action
cat /efi/sum0
cat /efi/sum1
sudo umount /mnt

[danjog2]

Brilliant, I'll get onto that soon!

[danjog2]

Sorry for the delay, been a bit ill...

Here's the output, either I'm doing stuff wrong or my joggler is screwed.

joggler@joggler:~$ sudo mount /dev/mmcblk0p2 /mnt
joggler@joggler:~$ cat /mnt/etc/firmware.ver
8686.S3
joggler@joggler:~$ cat /mnt/etc/software.ver
26635.S3
joggler@joggler:~$ cat /openpeak/tango/xinit.sh
cat: /openpeak/tango/xinit.sh: No such file or directory

joggler@joggler:~$ sudo umount /mnt
joggler@joggler:~$ sudo mount /dev/mmcblk0p3 /mnt
joggler@joggler:~$ cat /mnt/etc/firmware.ver
8686.S3
joggler@joggler:~$ cat /mnt/etc/software.ver
26635.S3
joggler@joggler:~$ cat /openpeak/tango/xinit.sh
cat: /openpeak/tango/xinit.sh: No such file or directory
joggler@joggler:~$ sudo umount /mnt

joggler@joggler:~$ sudo mount -o ro /dev/mmcblk0p1 /mnt
joggler@joggler:~$ ls /efi
ls: cannot access /efi: No such file or directory
joggler@joggler:~$ cat /efi/action
cat: /efi/action: No such file or directory
joggler@joggler:~$ cat /efi/sum0
cat: /efi/sum0: No such file or directory
joggler@joggler:~$ cat /efi/sum1
cat: /efi/sum1: No such file or directory
joggler@joggler:~$ sudo umount /mnt

I hope this helps a bit - I added a sudo to the last code, as it seemed to be missing.

[danjog2]

I've realised my Joggler is still under warranty so I've requested a fix from o2.

[roobarb!]

Sorry for the delay, been a bit ill...

Here's the output, either I'm doing stuff wrong or my joggler is screwed.

joggler@joggler:~$ sudo mount /dev/mmcblk0p2 /mnt
joggler@joggler:~$ cat /mnt/etc/firmware.ver
8686.S3
joggler@joggler:~$ cat /mnt/etc/software.ver
26635.S3
joggler@joggler:~$ cat /openpeak/tango/xinit.sh
cat: /openpeak/tango/xinit.sh: No such file or directory

joggler@joggler:~$ sudo umount /mnt
joggler@joggler:~$ sudo mount /dev/mmcblk0p3 /mnt
joggler@joggler:~$ cat /mnt/etc/firmware.ver
8686.S3
joggler@joggler:~$ cat /mnt/etc/software.ver
26635.S3
joggler@joggler:~$ cat /openpeak/tango/xinit.sh
cat: /openpeak/tango/xinit.sh: No such file or directory
joggler@joggler:~$ sudo umount /mnt

joggler@joggler:~$ sudo mount -o ro /dev/mmcblk0p1 /mnt
joggler@joggler:~$ ls /efi
ls: cannot access /efi: No such file or directory
joggler@joggler:~$ cat /efi/action
cat: /efi/action: No such file or directory
joggler@joggler:~$ cat /efi/sum0
cat: /efi/sum0: No such file or directory
joggler@joggler:~$ cat /efi/sum1
cat: /efi/sum1: No such file or directory
joggler@joggler:~$ sudo umount /mnt

I hope this helps a bit - I added a sudo to the last code, as it seemed to be missing.

Well, something's definitely wrong with those 'no such file or directory' reports. Let us know how you get on with O2 - I'd be interested to know what level of support they give you!

[dwl99]

I've returned 2 dead Jogglers and was posted replacement units within a few days.

[danjog2]

I've returned 2 dead Jogglers and was posted replacement units within a few days.

Thanks, hope they do the same for me.

[Mr_Dave]

Hi guys,

Did anyone ever get to the bottom of this rebooting after update loop issue....? Its driving me mad!

Cheers,
Dave