I had got iphone 3GS Beta with 3.1 modem firmware. My friend did update to 4.2 and also teether jailbreak. Now as soon as he finished jailbreak it. It went to recovery mode and always give USB+itune logo, looks it needs kick from recovery to operation mode. He now said he is waiting for small softwares for 4.2 which can help it in few days! Also itune reuiqres it restore but since it is jailbroken and i don't want to restore it.

Originally Posted by lalipa

I had got iphone 3GS Beta with 3.1 modem firmware. My friend did update to 4.2 and also teether jailbreak. Now as soon as he finished jailbreak it. It went to recovery mode and always give USB+itune logo, looks it needs kick from recovery to operation mode. He now said he is waiting for small softwares for 4.2 which can help it in few days! Also itune reuiqres it restore but since it is jailbroken and i don't want to restore it.

Do NOT restore the phone in iTunes. That will make things much worse.

I'm not sure why your friend updated to 4.2 in the first place, but.. now you are there..

You have what is called a "tethered jailbreak" - you will need to live with this until a solution becomes available. I don't know when that will happen.

Just keep on using redsn0w to "just boot tethered for now" each time you power on the phone.

Google a program called RecBoot.

It's a known issue that the phone becomes stuck in recovery mode. RecBoot lets you jump your iphone in and out of recovery aslong as you have it tethered to the pc.

I came across the same issue, used RecBoot to jump out of recovery once, and have since had no problem.

Hope this helps.

Originally Posted by KritikSS

It's a known issue that the phone becomes stuck in recovery mode. RecBoot lets you jump your iphone in and out of recovery aslong as you have it tethered to the pc.

I came across the same issue, used RecBoot to jump out of recovery once, and have since had no problem.

Your advice is not correct for this particular problem (although it does work for many other similar problems)

Originally Posted by Olethros

Your advice is not correct for this particular problem (although it does work for many other similar problems)

Appreciate your correction. Concerning that, once the iphone is booted to recovery mode, if one was to use RecBoot to jump it out of recovery mode would that not allow it to fully boot? or does it continue in a repetitious cycle?

Originally Posted by KritikSS

Appreciate your correction. Concerning that, once the iphone is booted to recovery mode, if one was to use RecBoot to jump it out of recovery mode would that not allow it to fully boot? or does it continue in a repetitious cycle?

Nope - there is a check in the restore ramdisk - it checks for the baseband and fails.

While the iPhone is controlled by the restore ramdisk - at that specific point nothing you do via irecovery or recboot will fix this specific problem.

The only way I know is to restore to iOS 4.1 - which doesn't have this baseband check. Of course, that only works if you have a SHSH for 4.1

Originally Posted by Olethros

Nope - there is a check in the restore ramdisk - it checks for the baseband and fails.

While the iPhone is controlled by the restore ramdisk - at that specific point nothing you do via irecovery or recboot will fix this specific problem.

The only way I know is to restore to iOS 4.1 - which doesn't have this baseband check. Of course, that only works if you have a SHSH for 4.1

understood, i appreciate the clarification.