iPhone MMS on t-mobile!

Ok here is how to make the above work on t-mobile! [note this may work for other providers however I have only tested it on t-mobile USA]

Once your iPhone is jailbroken and unlocked you will want to do the following

Goto Settings>General>Network

Make sure Data Roaming is turned on and 3G  is OFF then go into Cellular Data Network.

From here enter in the following

Cellular Data:
apn: internet2.voicestream.com
username:
password:
Visual Voicemail:
apn: wap.voicestream.com
username:
password:
MMS:
apn: wap.voicestream.com
username:
password:
MMSC: 216.155.174.84/servlets/mms
MMS Proxy 216.155.165.50:8080
MMS Max Message Size:
MMS UA Prof URL:

Now reboot your iPhone and you are good to go!!! You will now have a little camera icon next to your message window on the sms/mms application.

AS ALWAYS TRY THIS AT YOUR OWN RISK!! THE CHANCES OF SOMETHING GETTING MESSED UP WHILE DOING THIS ARE VERY VERY SLIM HOWEVER IF YOUR PHONE BREAKS ITS NOT OUR FAULT!

happy hacking

-Tracker

iPhone 3.0 will I be upgrading to it?

dscf2082

So with the release of the new firmware for the iPhone getting VERY VERY close one question on anyone who unlocks and or jailbreaks there phones are wondering the same thing. Well I am going to attempt to answer some questions.

First off for those of us unfortunate enough to be stuck with a 2.2.1 iPhone using a turbosim to unlock or just not using the phone because of the damn baseband update we are going to be in luck. A week or so ago I was reading the iPhone Dev Teams blog and they stated the following about yellowsn0w [the program used to unlock iphones with out using a turbosim. Don’t forget to save this iPhone back glass repair contact in case you need an affordable solution to the damage on your device.

YellowSn0w on 2.2.1 and beyond

We see many questions about whether yellowsn0w can ever be made to work on firmware versions past 2.2 (or equivalently, basebands past 02.28).  This is probably a good place to address those questions:

If there is a yellowsn0w update for firmware after 2.2 (or basebands after 02.28), there is no way it would ever be released before 3.0 is official. It just wouldn’t make any sense to release an exploit for something that only those who have beta 3.0’s (NDA signers) could use.  Most people in the world aren’t NDA signers.  Any yellowsn0w update for 3.0 would need to happen *after* 3.0 is officially available

Now I dont know if maybe I was just being optimistic but I figured they had gotten it to unlock on the 3.0 firmware just because of the way it was worded. Well I was correct. As of writing this and just a mere 4 hours ago the dev team posted this to there blog.

On Tuesday evening (just before the big Apple release) we’ll do a live demo of the yellowsn0w carrier unlock working on official 3.0 firmware. The actual link for the feed will be twittered by @MuscleNerd (see our twitter feeds to the right) and also placed here when the feed starts.  The demo should answer everything you need to know about the new yellowsn0w.  But it’s good news for iPhone 3G unlockers everywhere.

What does that mean? Well first it means I can drop this damn tubrosim and go software to unlock. Dont get me wrong the turbosim works great most of the time it just takes a while for it to kick in and do its job and having to type in “internet2.voicestream.com” every time I loose a signal is not a fun task. So that is great news for me and anyone else out there using it.

Lets move on shal we? The 3.0 firmware is going to be able to be jailbroken [did you have any doubt] and it will work with the new iTunes 8.2 that was released. So if things go as I think they are going to go by the end of the week I will be on the new itunes rocking 3.0 firmware on my iPhone with yellowsn0w unlocking it to use on t-mobile.

Lets summarize this up…

  • iPhone 3.0 firmware CAN be jailbroken
  • iPhone 3.0 firmware CAN be unlocked [pending the release of the new yellowsn0w]
  • Quickpwn/pwnagetool WILL work with iTunes 8.2
  • DarkWarrior is a n00b because he never posts anymore 😉

[Source: Dev-Team Blog]

-Tracker