Posts tagged Dev-Team

iPhone Dev-Team Offers Tips to Fix Unlock Issues



The iPhone Dev-Team has posted some tips to help those experiencing problems with the UltraSn0w unlock

—–
It looks like version 0.9 of ultrasn0w fixed up the vast majority of any problems people were seeing with the 3G/3GS carrier unlock. But here’s a brief list of fixes for anyone still seeing problems:

* Unusual battery depletion is almost always caused by people choosing to “Restore from backup” instead of “Setup as new iPhone” when iTunes asks you. This isn’t caused by either the jailbreak or the unlock, but it’s a common 3.0 snafu. The fix is to just re-run the official 3.0 restore and choose “Setup as new” this time. Your music and apps and all that will still be synced, but you’ll get rid of any conflicting wifi, bluetooth, or carrier settings. Then just re-run redsn0w and install ultrasn0w.
* Remember, ultrasn0w works with hacktivated phones too, but don’t outsmart redsn0w into thinking you don’t need hacktivation! If you don’t plan on using an official sim, don’t activate via iTunes with such a sim. Just keep your unofficial sim at all times and let redsn0w and ultrasn0w handle hacktivation :)
* T-Mobile in the USA doesn’t use the 3G frequencies that the iPhones support, so turn off 3G in Settings->General->Network. (Some T-Mobile territories gracefully hand down to Edge mode, but most do not).
* Certain unofficial plans have limitations on whether you can make calls and use data at the same time. That’s not unlock-related.
* Some people have installed previous versions of ultrasn0w using non-standard techniques. While the ultrasn0w 0.9 update should have removed all previous versions of ultrasn0w, these users may have outsmarted our removal. So make sure you don’t still see /usr/bin/ultrasn0w present if you’re at ultrasn0w 0.9 (which doesn’t have such a binary anymore).
* If you don’t need or plan to update to ultrasn0w 0.9 from a previous version, you can avoid having that red badge over Cydia by removing repo666 as a Cydia source. Don’t worry, you can always add it back later :) If you follow us on twitter you’ll be advised of any new updates anyway.
—–

Read More


iPhone Dev-Team Updates UltraSn0w Unlock, Discusses PurpleSn0w


The iPhone Dev-Team has updated the UltraSn0w unlock to use some of the good ideas from PurpleSn0w. They have also provided a very detailed explanation of how PurpleSn0w and UltraSn0w work.

—–
The day before yesterday, some fellow named geohot released a program called “purplesn0w” which claims to be a better unlock than our ultrasn0w solution. He was kind enough to provide source, which we naturally took apart to try to validate his claims. ;) We’ve found he had come up with some pretty neat ideas, including patching the actual text of the baseband code by copying it over to RAM and then using the MMU and page tables to have the baseband pretend it is part of the original bootrom. Of course, like yellowsn0w and ultrasn0w, this code has to be reloaded with every reboot of the baseband. However, the advantage of this is that developing unlocking payloads is a lot simpler… in fact, geohot used the same payload in AnySim and BootNeuter. We kicked around this idea ourselves before, but eventually found a work-around for the same problem with the yellowsn0w/ultrasn0w payload. The two pieces of code have the exact same effect on the baseband… with the difference that geohot’s exploit overwrites an arbitrary block of memory one megabyte in size. The baseband has a total of eight megabytes of memory and every bit of it is earmarked for use (except for 485212 bytes of it which we haven’t accounted for yet, but that’s still less than 1 MB). This means that eventually the area of memory geohot is using will be corrupted and 1 MB of baseband code will be corrupted (until the next reboot). How soon will this happen? Will it even matter in day-to-day use? We don’t know, because we haven’t spent much time looking. However, why take the risk when the yellowsn0w/ultrasn0w payload accomplishes the same job with no corruption?

The second new idea he had was to patch CommCenter rather than use a daemon. At first, this idea seemed pretty distasteful to us. Binary patches are messy and difficult to maintain (we figure it’s partly why he only made a version for 3G S and not 3G as well). In addition, the stated reason of reduced battery life with a daemon is factually incorrect, since any computer science student who’s taken a course in operating systems will tell you that a sleeping task takes up exactly NO CPU resources and NO power (it’s merely skipped over during context switches). That’s right: not “only a little” power, but absolutely NO power. However, ultrasn0w 0.6 did have a problem where the STK refresh command it used crashed the baseband in 3G S. This caused the baseband to continually come up and then restart. That DOES take power and so may explain the issues that people have been seeing. ultrasn0w 0.8 was supposed to have fixed this issue, but perhaps not completely. This is because the STK refreshes we used are inherently unreliable… but we thought they were necessary to avoid people having to reinsert their SIM. Turns out we were wrong on that score. geohot’s method shows that we can perform the unlock before CommCenter polls for lock state. When we do it before (instead of after), the STK refreshs are no longer necessary! The only way to do it before the polling, however, is to modify CommCenter. We’ve tried to make the best of a bad situation by using MobileSubstrate to perform the modification. This lets us modify the behavior of CommCenter without touching the actual binary. We also used a method to dynamically locate the patch location so that it should work on both 3G and 3G S (and should need to be updated less frequently). We also do it in a different way so that hactivated phones will work with the unlock (unlike purplesn0w). You’ll find that this update is now available through Cydia as ultrasn0w 0.9 We thank geohot for contributing to the scene once again. We don’t think purplesn0w is the right path, but it has certainly helped us improve ultrasn0w!

P.S. geohot, seriously, stop dicking around and look at the bootrom instead kthx. =P
—–

You can find instructions on how to unlock your iPhone using UltraSn0w here.

Read More

How to Unlock the iPhone 3GS Using PurpleSn0w


These are instructions on how to unlock the iPhone 3GS for use with any GSM cellphone carrier using PurpleSn0w. Geohot has posted stating that the purplesn0w unlock should improve issues with wifi, battery, and the unlock itself. If you would prefer to use the iPhone Dev-Teams UltraSn0w unlock you can find those instructions here

Before you can follow these instructions you must have a jailbroken iPhone and you must be on the 04.26.08 baseband(modem firmware). This means that you must be running the 3.0 firmware and have used PwnageTool, RedSn0w, or PurpleRa1n to jailbreak. YOU MUST ALSO (FOR THE TIME BEING) HAVE ACTIVATED YOUR IPHONE WITH AN OFFICIAL APPLE CARRIER. NO HACTIVATION SUPPORT YET.

To find your firmware and modem firmware(baseband) versions you can follow this tutorial. If you are not on baseband version 04.26.08 then you need to follow one of these tutorials before unlocking: Mac, Windows

If you are on T-Mobile or any carrier without 3G remember to turn it off before starting…



Step One
Press to launch Cydia Installer from your SpringBoard.

Step Two
Press to select the Manage tab at the bottom of the screen.

Step Three
Press to select the large Sources button

Step Four
Press the Edit button at the top right of the screen.

Step Five
Press the Add button at the top left of the screen.

Step Six
Enter http://apt.geohot.com/ as the source url and press the Add Source button.

Step Seven
Once the source has been added press the large Return to Cydia button.

Step Eight
Press the Done button at the top right of the screen.

Step Nine
Press to select apt.geohot.com from the list of user entered sources.

Step Ten
Press to select com.geohot.purplesn0w from the list of packages

Step Eleven
Press the Install button at the top right of the screen.

Step Twelve
Press the Confirm button at the top right of the screen.

Step Thirteen
After installation completes successfully press the large Return to Cydia button.

Step Fourteen
Now press the Home button then power off and power on the iPhone. You do this by holding down the power button for 3 seconds then moving the power slider that appears to the right. Press the power button again to turn on the phone.

You should now be able to insert the SIM of your choice!

Fuzzyband 3.1b1 Now Supports iPhone OS 3.0


The Fuzzyband Baseband downgrader has been updated to 3.1b1 and now supports iPhone OS 3.0. It also adds an upgrade feature for those looking to use the ultrasn0w unlock.

FEATURES:
Upgrades / Downgrades baseband to 4.26.08 for unlocking with the ultrasn0w tool released by the iPhone Dev-Team

UPGRADING:
Upgrading is for users that wish to remain on 2.2.1 but also unlock. Upgrading will put the 4.26.08 baseband from 3.0 on the modem so that ultrasn0w may be installed from cydia

DOWNGRADING:
Downgrading works from any version greater than 4.26.08 (currently 5.08.01 is the newest version available, found in 3.1 beta 1). It will put your baseband back at version 4.26.08 which is the current unlockable version by ultrasn0w.

Downgrading only works on phones that have the 05.08 (5.8) Bootloader from the factory. This is a very limited number of phones that were released in the first few weeks of the 3G production cycle.

If you do not know your bootloader then you can run Fuzzyband and it will report the version number for you.

Read More

WSJ Profiles the Chronic Dev Team


The WSJ has published an article on AriX, Chronic, Geohot and the Chronic Dev Team.

The article focuses on Ari, the 15 year old hacker who originally wrote iJailbreak. It tells the story of how he became interested in hacking the iPhone and how he joined up with Chronic and others to form the Chronic Dev Team.

Earlier this year, Ari and his team tried to hack more efficiently by working with another group — iPhone Dev Team, an invitation-only bunch in their 20s and 30s who have typically been the first to roll out iPhone hacks.

Members of the iPhone Dev Team worried about working in a large group. In part, they were concerned that if information leaked out about the security holes they were probing, others could exploit them first. Or, Apple could plug the holes. In March, the two groups stopped communicating.

The article also notes that GeoHot has been helping the Chronic Dev Team and that they have released the purplera1n jailbreak in spite of the iPhone Dev-Team’s desire to wait for firmware 3.1.

Mr. Hotz, who took a paid internship with Google Inc. in April, joined the hackers in early June. In emails, he says he has done the project on his own time and was happy to help “a bunch of cool guys with a good attitude.”

More than a week ago, both Chronic Dev and iPhone Dev said they figured out how to jailbreak Apple’s new phone. The iPhone Dev Team wanted to wait to release its software so Apple can’t plug the security hole in the device immediately.

But Chronic Dev and Mr. Hotz released theirs as soon as it was ready. “A lot of people bought their phones expecting to jailbreak their phones, and now that we have the capability to do it, we should let them,” Ari says. “A lot of people have thanked us.”

Much more in the article linked below…

Read More [via TheiPhoneBlog]

RedSnow 0.8 and UltraSnow 0.8 released (support for 3GS devices)

The Dev-Team released RedSnow 0.8 that jailbreak all devices(incl. 3GS) on OS3.0 and RedSnow 0.8 to include support for 3GS devices

redsnow 0.8 torrent: http://thepiratebay.org/user/iphonedev/

Click the image to open in full size.

Click the image to open in full size.

iPhone Dev-Team Releases RedSn0w Jailbreak for iPhone 3GS


The iPhone Dev-Team jailbreak has been released for the iPhone 3GS, according to a BigBoss report.

The jailbreak can be performed using RedSn0w 0.8 for Windows and Mac. BigBoss is hosting the files here: Windows, Mac

Features:
1) Stable jailbreak tested by dev-team
2) Icy + Cydia problem solved (we think).
3) Ultrasn0w tested and working on 3gs
4) Proper kernel patches which will enable logome (after it’s updated for 3.0).
5) Mobile Substrate + Winterboard now working on 3gs.

The guides are very similar to the iPhone 3G but we have created specific ones for the 3GS since future jailbreaks will likely get more complicated. You can find them here: (Windows, Mac).

Read More

How to Fix Push Notifications on Your 3.0 iPhone 2G


These are instructions on how to fix push notifications on your jailbroken 3.0 iPhone 2G. Please note that this is a preliminary fix by the iPhone Dev-Team and thus may need some improvements before it is finalized.

Step One
Press to launch Cydia from your SpringBoard.

Step Two
Press to select the Manage tab at the bottom of the screen.

Step Three
Press the large Sources button.

Step Four
Press the Edit button at the top right of the screen.

Step Five
Press the Add button at the top left of the screen.

Step Six
Enter http://cydia.iphoneil.net as the new source address and tap the Add Source button.

Step Seven
Once the source has been successfully added press the large Return to Cydia button.

Step Eight
Press the Done button to exit Edit mode.

Step Nine
Press to select the newly added cydia.iphoneil.net repository.

Step Ten
Press to choose Push Fix from the list of Packages

Step Eleven
Press the Install button at the top right of the screen.

Step Twelve
Then press the Confirm button to beginning installation

Step Thirteen
Once installation has completed successfully press the large Reboot Device button to reboot your iPhone.

Once rebooted verify that YouTube works. If not try reinstalling the patch.

You will also need to remove then reinstall all your applications which use Push Notifications before they will work.

THANKS***: A big thanks to the iPhone Dev-Team for providing this fix. Also thanks to iPhoneIL for packaging it up nicely. Thanks to iSpazio for bringing this package to our attention.

Apple Tutorials How to Jailbreak Your iPhone 3GS Using PurpleRa1n (Mac)

Apple Tutorials
These are instructions on how to jailbreak your iPhone 3GS using PurpleRa1n for Mac OS X. Once you have completed this tutorial you will be able to unlock your iPhone 3GS using this tutorial.

This is a preliminary jailbreak and thus some apps such as Winterboard will not work. You may want to consider waiting for the jailbreak release from the iPhone Dev-Team if this is important to you.

You can find a Windows version of this tutorial here.

Step One
Open your web browser of choice and navigate to http://www.purplera1n.com. Click the Apple logo at the bottom of the screen.

Step Two
When prompted save the download to your desktop

Step Three
Double click the purplera1n archive to extract the application. Then double click the purplera1n application file from the desktop to launch the program

Step Four
Click the large make it ra1n button

Step Five
You iPhone will now be placed in recovery mode. You will see a picture of GeoHot that replaces the regular recovery mode screen on your device.

purplera1n will run and then your device will reboot.

Step Six
Once your device reboots you will see a new icon on the SpringBoard entitled Freeze. Press it to continue.

Step Seven
Once Freeze opens tap Install Cydia.

Step Eight
Once the Cydia installation has completed you must reboot your iPhone.

Step Nine
When you iPhone has rebooted you can run Cydia. Let it do all the necessary updates then follow our Unlock tutorial to finally unlock your iPhone 3GS.

NOTE*: To remove the Freeze icon from your desktop you can install CyDelete from Cydia then use it to delete the application. We will post a tutorial on this shortly.

THANKS*: A big thanks goes to GeoHot for his work in making this jailbreak possible. Also thanks to others who contributed such as chronic and the dev-team.

iPhone Dev-Team Releases Trial Fix for Push Notifications


The iPhone Dev-Team has released a trial fix for push notification on hacktivated iPhones. The team is requesting feedback from testers and will make changes and polish up the fix accordingly.

You can download the fix from here.

The installation is bit complicated and thus only advanced testers should attempt this for now.

Read More

——————————————-