Novice Question 3G Jailbrake & Unlock

I have two iPhone 3G’s, one has IOS 4.01 (modem firmware 5.13.04) while the other has 3.1.3 (modem firmware 5.12.01). Both have already been jailbroken using JailbreakMe.com and then unlocked using ultrasn0w. I would like to update both to IOS 4.1 but want to make sure that I can also unlock them. Can I do that using the latest version of PwnageTool, should I install IOS 4.1 (thus removing the jailbrake) and then use PwnageTool to jailbrake the phone? After jailbraking with PwnageTool do I run ultrasn0w or should I use some other app to unlock both phones?
Thanks

Quote:

---

Originally Posted by DunderMifflin

I have two iPhone 3G’s, one has IOS 4.01 (modem firmware 5.13.04) while the other has 3.1.3 (modem firmware 5.12.01). Both have already been jailbroken using JailbreakMe.com and then unlocked using ultrasn0w. I would like to update both to IOS 4.1 but want to make sure that I can also unlock them. Can I do that using the latest version of PwnageTool, should I install IOS 4.1 (thus removing the jailbrake) and then use PwnageTool to jailbrake the phone? After jailbraking with PwnageTool do I run ultrasn0w or should I use some other app to unlock both phones?
Thanks

---

This question gets asked at least once a day here right now... Did you search before posting?

Answer is no. This is not possible right now. If you update to 4.1 you will lose unlock, maybe for ever (definitely for a few months or more)

Jailbreakme.com is not a low level jailbreak, so you cannot go from jailbreakme to pwnagetool without a SHSH for iOS 3.1.2 and only on an old bootrom 3GS.

Wait for SHAtter jailbreak coming soon. Do not allow your iPhones to update to 4.1.

Use TinyUmbrella to get SHSH for 4.1 while you can.

I updated my 3G to 4.1 retaining my 5.13 baseband using Snowbreeze.

Jailbreak iOS 4.1 on iPhone 3GS New Bootrom with Sn0wbreeze 2.0.1 [Custom Firmware Windows] | Redmond Pie

Quote:

---

Originally Posted by totono8

I updated my 3G to 4.1 retaining my 5.13 baseband using Snowbreeze.

Jailbreak iOS 4.1 on iPhone 3GS New Bootrom with Sn0wbreeze 2.0.1 [Custom Firmware Windows] | Redmond Pie

---

Apologies, I think I saw 3G's and read 3GS

Still.. there is no "official" jailbreak for the 3G that can retain the ability to unlock.

We have been very clear in stating that sn0wbreeze is not a supported jailbreak tool on this forum. While it works for many (and appears to have stabilised since the early days when it bricked some phones) it still has conflicts with some cydia apps

I was unaware it wasn't a supported tool here. Since i read about it in redmond pie, commonly regarded as a good source, I thought I would give it a shot. Must say that custom firmware restored only after running iREB first.

Quote:

---

Originally Posted by totono8

I was unaware it wasn't a supported tool here. Since i read about it in redmond pie, commonly regarded as a good source, I thought I would give it a shot. Must say that custom firmware restored only after running iREB first.

---

Well.. if you consider a site that reports on piracy tools a good source, you might be on the wrong forum.

We don't tolerate warez/piracy here at all. That is one of the reasons sn0wbreeze is not supported here (early versions of sn0wbreeze illegally distributed copyrighted Apple files).

The original reasons for refusing to support sn0wbreeze have mostly been fixed now. However I doubt the decision to refuse to support sn0wbreeze and other ih8sn0w tools will be reviewed any time soon.

By "good source" I mean it won't advertise fake tools floating around the net, viruses, or scam sites for hacking the iPhone. It's ironic how you frown upon content talked about there when you are a moderator of a HACKING forum, I don't think you have too much room to talk. I don't come to HACKint0sh for morality lessons.

I agree with tonono8. It seems alittle hypocritical to refuse to "support" sn0wbreeze because in the past it's had some issues. Jailbreaking the original iPhone with redsn0w requires downloading the bootloader binaries. Even though the dev-team doesn't bundle those files, you still have to engage in piracy in order to make the jailbreak work.

I use this forum, as I'm sure many do, as a source for information regarding jailbreak. I kinda look at hackint0sh and being THE source for jailbreak discussion, as I'm sure many do. Simply refusing to discuss the issues that a jailbreak might have doesn't exact seem conducive to the community. If there are known issues with a jailbreak it might be helpful to discuss them instead of simply saying "we don't discuss that here."

I used sn0wbreeze to jailbreak 4.1 on my iPhone 3GS and have experienced some issues, I don't know if those are issues specific to sn0wbreeze or issues with 4.1. Because nobody discusses it here.

I'm with Olethros here. This is extremely similar to the situation we encounter when we discussed Rock previously (as it was not a supported package manager). It was an insecure, unsafe package manager that many people liked because of one or two features, and because of how fast it was. What most people didn't know was that the reason it was faster than Cydia was because of shortcuts that the developers took that ended up causing a lot of grief for Rock users when an update was made that effectively bricked users phones who were using it. Hackint0sh forum mods did not support Rock, and users made similar comments as yours until the day that Rock bricked thousands of people's phones due to their shortcuts.

The same is true of sn0wbreeze. When it came out, it contained copyrighted Apple code -- that alone banned it from these forums immediately until such time as the copyrighted material was removed. Once that issue was resolved, the software itself was buggy and caused many problems with the devices that it was used on, some that were extremely difficult to pinpoint or resolve. This is because the sn0wbreeze developers took many shortcuts to provide the jailbreak to the community. While it's true that many users may be able to use sn0wbreeze these days and that the software may have matured to the point that it no longer habitually bricks phones, you'd be just as upset if we recommended using it and you bricked your phone because of it.

No one is trying to teach you morality here (though there is nothing immoral about hacking at all, and stealing someone's work by pirating their copyrighted material can easily be argued as immoral), we're just trying to educate you on the things we know about this software that you may not yet be aware of - which is ultimately what you were asking us to do. If a software package has habitually caused problems in the past, I'd feel we would be more remiss for supporting it and recommending the use of it than we are informing users of the issues associated.

In either case, this has rapidly gone from topic to off-topic to flamebait, I'm closing the thread to nip this in the bud as the initial question has been answered.