[decros]

hi guys,
first of all I would let you know that I am a rookie regarding moding the iphones and if it happens to get some answers please be patient ant take the time to provide me with detailed answers.
So. I have an Iphone 2g firmware version 2.1 unlocked and jailbroken.Everything was just fine till last night when I tried to install some new sources using installer.app. Some of the sources couldn't be installed the message I got being: can not decompress (?) the source data or something like that. Some other worked just fine.
The first symptom occurred when I tried to open something on the springboard. It seemed that the application is going to start (i mean it shows up on the screen) but after a second is gone and phone returns on the home screen (the icons interface). I said Ok maybe it wants a reboot so I did it. And this is when it happened. Phone restarts itself and get stuck on the screen with apple logo and nothing happens no matter what; and is stays like that forever. The only way to switch it off is by pressing the home and power button. When I try to start it using home and power buttons exactly the same thing happens (the apple logo screen).
What is funny is that once connected to PC (Windows OS) the computer is able to see the device and Itunes pops up and syncronize the phone and pc.

So that would be the story of my phone. I would really appreciate if you guys can provide some useful info about recovering the phone as I love it and don't wanna just look at it as a piece of furniture or a toy.

Thanks in advance.
Yours,

Dec

[Chefanim]

Learnin the hard way, Installer has done this to me too.

Do you have SSH installed?

This info is from here:
Apple Logo of Death solution! (SWOD) - iPhone Tips& tricks - iPhoneFreakz



If you don’t have OpenSSH already installed then sorry, it’s restore time…

As the device is trying to boot up but still at the apple logo, try to log in as root using ssh. You should find you are able to log in soon after the device is pingable on your wifi network, and you have a few minutes to complete the following steps in time.

For example from a mac, log in with:

ssh -l root 192.168.1.103 (your iPhone iP address)

Where your iphone/ipods own ip address is substituted.

First we will disable the watchdog timer (by temporarily moving its files elsewhere) and then reboot:

mv /System/Library/SystemConfiguration/mobilewatchdog.bundle/ /
reboot

After a few seconds the device will start to reboot, and after approximately 3-6 minutes (depending on how many apps you have installed) you will reach the lock screen as normal, when that happens we now have to re-enable the watchdog timer, and reboot again, so again log in with ssh, and type:

mv /mobilewatchdog.bundle /System/Library/SystemConfiguration/
reboot

You should find your iphone / ipod touch will reboot normally a second time.

The reason this is a workaround is because you CAN’T leave the watchdog disabled, because as well as monitoring Springboard and killing/restarting it, the watchdog also has to periodically reset the HARDWARE watchdog, if this doesn’t happen the device will spontaneously reboot. The hardware watchdog is 10 and a bit minutes, so without the watchdog installed and working your device will reboot itself every 10 minutes.

If anyone knows how to contact or draw this message to the attention of the dev team I have an idea for a simple patch that they could apply to the watchdog as part of the Pwning process (or as a Cydia package) that would for all intents and purposes solve this problem until Apple gets around to fixing it properly. Please send me a PM.

Note: This same issue is the reason why after installing apps with Cydia the system will sometimes freeze. As far as I can tell Cydia is NOT to blame - what Cydia does is tells Springboard to regenerate the application map, and it is that application map regeneration that triggers the problem - Springboard becomes unresponsive for extended periods of time, the watchdog process starts trying to kill Springboard, and all hell breaks loose…this procedure will also recover from that situation.

The reason Installer.app doesn’t trigger this problem is it doesn’t tell Springboard to regenerate the application map - it just kills Springboard and allows it to launch again.