hi all, i have seen some mention of this issue here in the fora but it hasn't gotten all that much attention from what i can see, so i am wondering whether this is really an issue that affects all installations or only some? i updated my 1.1.2 iphone to 1.1.3 using the dev release via terminal and sftp, and it seemed to install and run fine at first, aside from a few snafus, some of which have been addressed w/ patches and hacks. but today i started experiencing what i cannot think of as other than a show-stopping bug.

i was installing some apps via the installer and one required a reboot, the app in question is listed as 1.1.3 compatible so i figured there could be no harm... but instead of rebooting back to my springboard, i found myself in recovery mode. inDependence was easily able to kick it out of recovery but that really isn't the point... i found myself w/out a phone for a good part of the day since I DON'T CARRY A LAPTOP AROUND JUST TO KICK MY PHONE OUT OF RECOVERY MODE! i mean, that is a pretty serious bug if it is widespread, i did a clean reinstall this evening and did a regular hard reset just to see what would happen upon reboot... sure enough, back into recovery mode.

this seems really bad if you want to rely on your phone when out and about, and don't want to be saddled w/ 5+ lbs of hardware just to reboot a phone... is this not really a widespread issue, are all iphones updated via the official dev JB exhibiting this behavior or only some? i am sitting at yet another clean 1.1.2 install right now and wondering whether i should try the earlier 'Nate' JB instead this time, any input as to which direction to go here friends..?

Yeah sukatoro had the same problem as you so restored back to 1.1.2.
Anyone have the same issues? and what do you think are causing it?
Every reboot it enters recovery mode, i use independence to kick it out of recovery and freezes at the springboard and reboots again

Originally Posted by maidstonelad

Yeah sukatoro had the same problem as you so restored back to 1.1.2.
Anyone have the same issues? and what do you think are causing it?
Every reboot it enters recovery mode, i use independence to kick it out of recovery and freezes at the springboard and reboots again

Same here


Back to 1.1.2

Yup. Happened to me as well.
Now trying to go down to 1.1.1 again, to jailbreak. And at the moment that's not working either. Mood is very low.

Originally Posted by maidstonelad

Yeah sukatoro had the same problem as you so restored back to 1.1.2.
Anyone have the same issues? and what do you think are causing it?
Every reboot it enters recovery mode, i use independence to kick it out of recovery and freezes at the springboard and reboots again

actually while i have seen the issue you describe, thats not what i'm refering to... when my iphone is working "normally" at 1.1.3 if i reboot for any reason i will enter recovery mode and require Independence to get kicked back out, making the phone pretty unreliable w/out a computer handy to reset it... once i am kicked out things are back to normal until another reboot is required/desired.

what you describe w/ the crashing springboard that eventually leads to recovery mode after 3 crashes i have only seen after applying the 'syncfix.sh' patch which is supposed to correct syncing issues w/ iTunes... at this very moment i am finishing up the whole process of restoring to 1.1.1 to 1.1.2 so i can have a try at 1.1.3 *yet again*. if it all gets screwy again after this attempt i am giving up for now and going back to 1.1.2 for what its worth..

I had a similar experience today, although my iPhone hasn't gone back to recovery mode since this first and only experience.

After JB 1.1.3 DEV I had a 100% full system partition, Installer behaved strangely with crashes or installed applications not showing up in Springboard although they were installed in the file system. After moving /Applications to the media partition that problem disappeared, so I guess, there an issue with Installer when it doesn't have enough space on the system partition.

And now the bad story begins: I installed the NetServices App, hoping it would work on 1.1.3 to disable EDGE. But it didn't. Instead, after "disabling EDGE" and returning back to Springboard, the iPhone showed the spinning wheel for several minutes.
I put it to sleep, but as I could see, this did a complete shutdown (spinning wheel on black background).

When I switched the iPhone back on I was presented with the DFU screen

I tried iPhuc on OSX to get it out, didn't work.
I tried iTunes to ALT-Recover to 1.1.1, didn't work (stopped after about 5 seconds with ERROR 2003). At this point in time I started transpiring...
I tried iNdependence, it told me, that 1.1.3 is an unsupported firmware version.

Then I looked back at my iPhone's screen and guess what I saw! "slide to unlock"!
Since then I'm back in 1.1.3, don't know how to get back to 1.1.1 (as restoring with iTunes didn't work) and don't dare installing any 3rd party application anymore as probably most applications are just not 1.1.3-fit yet.

Well, at least I can watch the wiggly icons and make phone calls, after all, it's just a phone.

I'm sure all issues will be fixed at some point in time, but this is really an annoying situation for many of us.

Anyone willing to give me a hint on how to get the 1.1.3 -> 1.1.1 downgrade done?

Same problem here. Everytime i do a reboot the phone steps into the restore mode. I need to boot it with the old ibrickr tool 0.91 to get back to springboard etc.

That's really a annoying situation. Because if a application crashes and you need a reboot and there is no pc with ibrickr on it nearby. You are not available for incoming calls

Please help to get a fix for this BIG problem!

Thanks,
syK

Originally Posted by wsarahan

Same here


Back to 1.1.2

Same issue with me too

Same - have 2 unlocked 'phones on 1.1.3 here both with the same issue, upgraded using the official Dev Team mechanism. Would be interested to hear if the Nate True upgrade causes the same problem or if there's a solution to this other than to downgrade to 1.1.2 again.

same here..