Hi Torpie, I'm not 100% sure what I did to get it working, because I am not sure I gave it enough time to boot when trying to confirm the status of what I had done but I will place a list below.. I had actually done the exact thing you mentioned - running a restore from the phone... very bad idea as mine got mucked up as well and i ended up restoring from itunes to 3.1.. however I got a warrenty replacement for that one so it is irrelevant [stores still giving out 3.0.1 - so if you think your phone has a legit hardware issue you could gamble and flash 3.1 and take it in - tho i wouldn't recommend it as there is much gambling involved]

Anyway, what i did when my phone started the loop [which this second time i caused from the ssh prompt by running 'reboot']

First I tried rejailbreaking which as you noticed didn't complete.. and is how i found out this error to get to this thread - nonetheless i tried this a few times with redsnow... second I tried restoring 3.0.1 and prob 3.0 from itunes [which yes I pretty much knew wouldn't work but tried anyway... you tend to get a bit desperate /hopeful haha] then i decided to delve into irecovery which i ran that bootx command and possibly one other..i dont remember offhand and without seeing the options i know I tried a command for something relating to booting the kernal at a specified address and utilizing the above mentioned values that are needed (4,3) .. regardless in the middle of this all and both before and after were countless reboots going iinto dfu/restore mode, but i doubt those would have had impact... let me know of your process.. it is frustrating as it is only a single environment variable preventing the boot and your phone is intact otherwise.. Good luck!

Thanks folks for your answers.

I'm ready to keep my iPhone locked for some days. But, do you think/know if the Dev Team will release something in the next days ( I mean, is it in some days, weeks, or months ...) it's important to me evaluate the waiting to make a decision. And don't flame me please cause TBH I started using the iPhone only since 5 days, so I have no visions of hypes/delays/teams/habits ...

However I have some experience on Linux/Unix systems.

@nptn2k : can u please tell me how you did that ? : "I tried a command for something relating to booting the kernal at a specified address and utilizing the above mentioned values that are needed (4,3) .."

Cheers

BTW: does the dev team got a irc channel ?

Originally Posted by torpie13

Thanks folks for your answers.

I'm ready to keep my iPhone locked for some days. But, do you think/know if the Dev Team will release something in the next days ( I mean, is it in some days, weeks, or months ...) it's important to me evaluate the waiting to make a decision. And don't flame me please cause TBH I started using the iPhone only since 5 days, so I have no visions of hypes/delays/teams/habits ...

It will be ready when it is ready.
Dev Team does not give dates and hypes.
IMHO, the wait will be worth it.

I don't know what you are thinking. STOP tinkering with your device because Irecovery will not help you. I'm just trying to save you time and damage here. Feel free to give it a whirl if you want.

Originally Posted by dtube

It will be ready when it is ready.
Dev Team does not give dates and hypes.
IMHO, the wait will be worth it.

Thanks for the answer dtube.

I've got just a last question: I know what means Jailing application in a *nix OS as I m doing it for ssh connections and Bind servers that I administer. To break it (Chroot it out), you have to own an elevated priviledge ( root ) on the device system. This could be possible thanks to an bug (BufferOverflow ...) or an error from the owner of the system.

So my question: Is the known exploit still workable in the 3.1 FW ? or the team is still searching for a new exploit ?

I know that there is no more known flaws (exploit) available for the Radio part of the device. So, unlocking this part is not possible atm. But I'm not sure about the OS part.

Originally Posted by dtube

I don't know what you are thinking. STOP tinkering with your device because Irecovery will not help you. I'm just trying to save you time and damage here. Feel free to give it a whirl if you want.

Don't worry dude ! and that for the advise


Thanks for your help.

Originally Posted by torpie13

So my question: Is the known exploit still workable in the 3.1 FW ? or the team is still searching for a new exploit ?

These are the facts as of now.

The iphone dev team have not said anything publicly about having any more new exploits for jailbreak or baseband sitting around. This is their standard policy and and important part of playing cat and mouse with Apple regarding exploits.

The existing 3.0 iBoot exploit was found independently by the devteam and geohot. Both produced jailbreak tools based on this exploit (redsn0w and purplera1n respectively). This exploit was blocked in an updated iBoot that ships with firmware 3.1

ChronicDev (a different iPhone team, originally more focused on the iPod Touch) have revealed they had another exploit which they kept quiet about in the hope that apple would not fix it in 3.1. Subsequent testing has proven this exploit still exists in 3.1 and this team is working on a jailbreak tool that will be called greenpois0n. It will be similar to redsn0w requiring only recovery mode to use.

Geohot has confirmed that he has discovered the same exploit that will be used in greenpois0n but has not got the time to develop a jailbreak tool because he is back at college.

Originally Posted by torpie13

I know that there is no more known flaws (exploit) available for the Radio part of the device. So, unlocking this part is not possible atm. But I'm not sure about the OS part.

Very well explained above Olethros ... thanks
The BB is going to be tough ... but I think Dev Team is looking at the bootloader or other things now... they are going for a homerun I hope.

After installing something on cydia I had to reboot my iPhone and got this problem too. It won't boot... apple logo appears and then the screen goes black again.

If I restore and update my firmware on iTunes, I won't be able to jailbreak my device anymore?

or is it possible that when the developers release this greenpois0n it will jailbreak new iPhones 3GS with 3.1?

blackra1n will jailbreak 3.1.2 devices regardless of how they got there. Devices that were pwned prior will keep their tetherless jailbreak, devices that were 3.1.2 OOTB will be a tethered jailbreak. Should be no need to wait for greenp0ison. At this point there is little reason to be on any version of firmware other than 3.1.2 unless you're negatively impacted on a regular basis by the tethered jailbreak...

Originally Posted by intelinside

After installing something on cydia I had to reboot my iPhone and got this problem too. It won't boot... apple logo appears and then the screen goes black again.

If I restore and update my firmware on iTunes, I won't be able to jailbreak my device anymore?

or is it possible that when the developers release this greenpois0n it will jailbreak new iPhones 3GS with 3.1?

Once jailbroken, always jailbroken unless you restore with apple firmware.

Just make a custom ipsw with pwnagetool 3.1.4 (or if you are on windows google and download a pre-made custom ipsw for your model iPhone)

Be sure to pick the correct option (activated if you require unlock, otherwise not activated)

If you don't require unlock, then you can restore with apple firmeware and jailbreak with blackra1n. That will be slightly faster, but I recommend pwnagetool over blackra1n.

I found that iRecovery could be useful in my case, just need to rename one folder, but fs command always give Permission Denied reply. There is no clear explanation, why Permission Denied? I found success that some people can move files with fs mv, but why in my case iRecovery give Permission Denied on 3G 3.0FW? Can you or anybody explain shortly?