yes u can...u can use blackra1n to JB ur phone...easy and fastest.

hi, means now any firmware, any baseband iphones also can jb without any problem?? don need to care about is it official unlock or sim unlock?

if i want to remove jailbreak i just do a restore in iTunes right.
wat happen to all my songs, apps etc..

the jailbreak apps will be remove auto or i need to remove first before restore

You mentioned you used redsn0w? if you did, it should have activated for you. Currently your phone is not only locked but still need activation. I am sorry to say but if redsn0w didn't work (i am sure you chose firwmare 3.0 right?) it could mean that your phone is no longer at firmware 3.0?. I suspect this because, in a previous post, you mentioned that you also used Itunes to update your phone?

he used iphone 2g 16gb...if he accidental upgrade using itunes...i think he can downgrade it back to 3.0 using itunes 8.2 or just restore use customs firmware created using pwnage (in DFU mode)

if i want to remove jailbreak i just do a restore in iTunes right.
wat happen to all my songs, apps etc..

the jailbreak apps will be remove auto or i need to remove first before restore

blackra1n is the easiest way to jailbreak so far. The previous methods are more complex so this is rather straight forward However sometimes it might not work in your machine due to OS compability, drivers, etc (I'm not sure of the actual cause). The best is to try with another PC if yours don't work.

i've noticed that using FW 3.1.2 is making ur 3gs smoother in using apps and less battery usage...

Hey guys, the problem lies with blackra1n removing support of afc2, you can fix it, there is a link to a  way on geohot's twitter but you will need to SSH into the unit.

What is the impact of removing support of afc2? What is that for?

What is the impact of removing support of afc2? What is that for?

if u use ifunbox or iphonebrowser or etc....software only detect raw contain of the iphone...and also detect as jailed phone...so for those who are always transfer files manual using those software...this support is quite important. backup ur iphone manual for example...

Apple Moves To Block Jailbreaking In New iPhones

Share
by Greg Kumparak on October 13, 2009

In the endless game of cat and mouse that is Apple vs. the jailbreak scene, the cat just put a pretty nasty gash in the mouse’s face.

For the past seven months, jailbreaking (opening an iPhone to applications not signed by Apple for installation) has relied on an exploit dubbed “24kPwn”. We’ll skip the technical voodoo for the sake of not putting you straight to sleep, but here’s the important bit: in the latest batch of iPhone 3GS units to hit the shelves, the exploit has been fixed. Unless a new exploit is discovered (and, with each patch, this is becoming less and less likely), any iPhone 3GS to ship after last week will not be jailbreakable.


If you want the full technical rundown of the exploit, you can find it here. In its simplest form: as with all computers, the iPhone requires something called a “Bootrom” to startup. During the startup process, one stretch of code in the Bootrom fails to ensure that the content being loaded is within a certain size limit. By throwing more instructions at that chunk of code than it’s intended to handle, exploiters are able to make the iPhone do damn near whatever they want; in this case, the jailbreaking process.

The first to notice that the 24kPwn exploit was no longer functioning was France’s Mathieu H.. A few hours later, others had confirmed the news. The latest Bootrom, iBoot-359.3.2, was no longer vulnerable to 24kPwn.

So, why would Apple do this? The exploit wasn’t really a security risk to the user; it wasn’t accessible without physical access to the handset, and the process was just intense enough that it couldn’t be done accidentally. Sure, it theoretically allowed malicious code to be run on the iPhone which might brick the handset – but that has by no means been an issue thus far. There’s only one other reason, then.

Even as Apple continues to open up APIs and (very) slowly loosen their restrictions on the App Store, there are many, many (legal) reasons why jailbreaking is fantastic; alas, there’s one why it’s not: piracy. While jailbreaking allows for countless wonderful (but otherwise disallowed) apps to run on the iPhone, it also allows cracked versions of paid applications to be installed. As a result, piracy is mind-blowingly, soul-crushingly rampant on the iPhone. Many iPhone developers – such as those behind the popular IM client, Beejive – are reporting that 80 percent of their users are pirates. Yep. For every 10 users on Beejive, 8 of them didn’t pay for it. I’m no saint myself, and all of us here fully understand that a download does not equal a lost sale – but when 80% of the people using your app (and in Beejive’s case, your servers) aren’t paying to keep the lights on, it’s likely seen as a big issue.

Will another exploit be found? Most likely. There is no such thing as perfect code – especially in something as complex as an operating system. It may be difficult, and it may require waiting through an update or two, but eventually someone will find a way back in.

do u mean 3.1,2? u can JB both of them depends on ur iphone whether it lock version or official unlock....for more info...please take time to read at the main page of this thread....david has been updated news regarding jailbreaking

---

Added on October 14, 2009, 3:57 amupgrade to 3.1.2 for my i3gs using pwnage tools....mine is lock version