For those of you that are interested in MMS, you can now enable MMS on AT&T via a simple carrier update. As I stated before, no firmware update is required. This works on 3.0 and 3.0.1. Here are instructions from hacker Gates. Reports from Gates indicate that tethering is still working, although no promises.

If you have 3.1:

- For jailbroken & Non-Jailbroken Phones:
- – Plug in your iPhone, if no prompt, click ‘check for upgrade’
- – Let upgrade happen (it is very fast)
- – Restart your iPhone [DONE!]

If you have 3.0(.1)

- Close iTunes

- – Windows:
- – - Click Start > Run > Type: cmd (and hit enter)
- – - Run this command: “C:\Program Files\iTunes\iTunes.exe” /setPrefInt carrier-testing 1

- – OSX:
- – - Open the Terminal Application
- – - Run this command: defaults write com.apple.iTunes carrier-testing -bool TRUE

- Download the newest AT&T Profile 5.5 (release 9.25.09) [Download Here / Mirror]
- – *Note* This will disable “cellular data network” to keep, see note at bottom (Advanced Only)

- Open iTune

- – Windows – Hold the shift key while clicking update under your iPhone in iTunes.
- – OSX – Hold the alt key while clicking update under your iPhone in iTunes.

- Navigate to the IPCC file (Windows* might need to change file type to IPCC)

- Let upgrade happen (it is very fast)

- Restart your iPhone [DONE!]

**Note** (Advanced Only)
If you use the 5.0 carrier file you can KEEP your “cellular data network” & tethering

In other words-
dtube: Basically 5.5 will give you instant mms with setting configured but will disable cellular data network. With 5.0, you have to configure mms parameter manually, but cellular data network is there thus tethering is

Follow the same directions but instead use this file:
http://rapidshare.com/files/279287091/ATT_US.ipcc

After updating to that file and restarting you must goto “cellular data network” (Settings > General > Network > Cellular Data Network)

And update some your configs
- Visual Voicemail change wap.cingular to acds.voicemail

- MMS settings (below the Visual Voicemail ) should match this (leave blank fields blank):

APN: wap.cingular
Username:
Password:
MMSC: mmsc.cingular.com
MMS Proxy: 066.209.011.32
MMS Max Message Size: 614400
MMS UA Prof URL:

Pwnage v3.1 for iPhone 2g / 3g and first generation ipod touch for osx is out. I updated my pwnage guide for this release. 3gs/ipod 2g still require RedSnow which is not out yet. Before you rush out and upgrade, I still recommend staying on any 3.0 firmware you are on for as long as possible. The 3.1 firmware is not worth the hassles of upgrading. But if you have one of the two devices above, you can upgrade if you want now.

From dev team blog:

1. GOLDEN RULE: If you are using a 3G iPhone with ultrasn0w and rely on ultrasn0w to obtain cellular service, then you should only upgrade to 3.1 with a PwnageTool created .ipsw. – Stay away from Apple’s direct updates as described here and here please get up to speed on the whole subject by reading the information contained in these posts.
2. If you have an original iPhone (1st generation) then 3.1 unlock works with this PwnageTool release. iPhone 3G users upgrading to 3.1 will need to continue using ultrasn0w with a PwnageTool created 3.1 .ipsw
3. Please read all parts of this post before downloading and using these tools.
4. Read items 1, 2 and 3 again and again.
5. At the bottom of this post are the bittorrent files for the 3.1 capable version of PwnageTool.
6. This app is suitable for the recent 3.1 release.
7. This version of PwnageTool will NOT work for the iPhone 3GS.
8. PwnageTool WILL work for Original iPhone (1st Generation), Original iPod touch (1st Generation) and the iPhone 3G.

Saurik solves the 3.1 downgrade problem for iPhone 3gs users, “the Chosen” few that saved their ECID SHSH.

If you were one of the 50,000 folks that let Cydia store your information for you, you can now downgrade your 3.1 3gs to 3.0 or restore your 3.0 3gs to 3.0 – or downgrade your 3.0.1 3gs to 3.0. Why is this important?

Lets say you are happily on 3.0 jailbroken and you do something to mess things up and need a restore? As I wrote previously, Apple is no longer allowing restore to 3.0. Well, now if you were one of the folks that had cydia store your ECID SHSH information, you can restore and jailbreak.

Saurik writes a great article explaining how to downgrade or restore your 3.0. He also goes into a very interesting discussion (that I totally agree with) about how Apple is mistreating us as a community. It’s a must-read in my opinion even if you don’t have a 3gs. If you do have a 3gs, you want to read this to understand how you can be able to jailbreak forever at least your 3.0 version.

The downgrade steps are at the bottom of his post. I won’t go into too much detail here, but in short here are the steps. (These only make sense after you read his post, which I encourage you to do).

3.0 to 3.0 restore: Add the hosts entry, restore in itunes, jailbreak, you’re done

3.1 to 3.0 or 3.0.1 to 3.0: To downgrade to 3.0, restore in itunes, get error, restore in itunes, get error, use irecovery to boot device, jailbreak.

One last time, read his post for details. Out of well-deserved respect for Saurik, I am not copying the data here.

If you were not one of the few that saved your ECID in Cydia, dont feel too bad. It sounds like there is an exploit for 3.1 and you will be able to save your 3.1 ECID. Just make sure you do it as soon as it is available to do so.

BossPaper v1.1.1 is going into Cydia now. It’s a bug-fix release only. I hope it solves all the issues that some people experienced on v1.0, although I cant be sure as I cannot reproduce any of the missing icon issues. In any event, the changes are:

1) Fixed background location to include statusbar again.

2) Fixed help screen to talk about how to use the new “Under Winterboard” feature. See Help, then Feature Description.

3) Made some changes internally to try to make things more like how 1.0 worked for those that were having problems with layering when using winterboard. I verified this fixed the problem for one person, (thank you Scott). I still cannot reproduce this issue so can only hope for the best.

4) The change to #3 above also impacted dimming if you had a winterboard theme behind the bosspaper. On v1.0 the winterboard theme was covered but on 1.1 the paper dimming let the theme show from behind it.

If anyone is still experiencing the missing icons issue, I need someone that is SSH savvy to help me debug it further or anyone that can give me enough details to reproduce it on my own (a complete list of your winterboard themes and which ones are applied and in what order for example, also disable all winterboard themes and test, etc).

BossPaper v1.1 is released. The main addition is the ability to select whether or not you want BossPaper to be on top of or underneath your winterboard background.

BossPaper v1.0 overlays over winterboard. This means if you have a javascript date / time widget you want to run, you cant it will be covered up by bosspaper. This also has some benefits though for example, you can run a theme with one image and icons then use bosspaper to rotate backgrounds.

BossPaper v1.1 defaults to the same mode as BossPaper 1.0 where the wallpaper image is on top of winterboard. But it has a new switch called “Under Winterboard” where when “ON” the BossPaper wallpaper will be rendered underneath winterboard backgrounds. This lets you have a date / time widget or some other interesting javascript widget in winterboard while using bosspaper to rotate images. (Some theme makers have requested this).

I have explained this in the apps help and covered various scenarios. Those that understand winterboard really well can also make a transparent 320×480 png image and move it to the top of winterboard. Then put bosspaper below winterboard and winterboard will always show the blank wallpaper but behind that you’ll see bosspaper running. This would allow you to run themes that have both icons and backgrounds but have the background be ignored. I did not include a transparent 320×480 theme but I may release one as an addon if it is required and does not confuse people.

RockYourPhone has released their v2 client. Now, I have not looked at this client yet. Let me state that I am not bashing rock your phone and have not made a determination yet whether or not it is great or terrible. What I can tell you is that if you are on a 3gs you should not install this until a 3.1 jailbreak is released.

As I already posted, the 3gs can no longer be restored to 3.0 or 3.0.1 anymore. If you update to 3.1 on your 3gs you may never be able to jailbreak again.

Rock your phone installs its own extensions and modifies a lot of system files. It is not installing just “an app”. They replace mobile substrate with their own version and the two may or may not work well side by side. Some thumb C function injection is likely to be broken. In normal cases, a simple restore would solve whatever issues you run into, but as things stand, you cant restore. So again, a very strong warning. If you are on a 3gs, do not install RYP2 at this time. If you want to test it, use a 2g, 3g, or wait for 3.1 jailbreak.

Note: this warning also applies to other software, but most stuff in cydia community sources can be repaired fairly easily without a restore using SSH.

Edit: I want to clarify. This is in no way a cut to RockYourPhone. This is only due to the nature of RockYourPhone install. It’s almost like its own jailbreak. How many of you have jailbroken and had the process not work and had to restore and repeat it? I know that’s happened to me many times. The problem here is that due to apple no longer signing 3.0 and 3.1 not being jailbroken, that on your 3gs if something went wrong installing RYP, you are left with two choices:

1) Restore to 3.1 and perhaps never be able to jailbreak again.

2) Do not restore, and use a razr until the 3.1 is jailbroken.

Who wants to risk that? If you have already installed rock your phone, you are probably fine. I wouldnt worry about it. The 3g and 2g can still be restored to 3.0 so I would not worry about those either.

This same philosophy applies to other software as well. If you are a 3gs user, I would strongly recommend being cautious about what you install until a 3.1 jailbreak comes out. The difference is that we know how to debug and trouble shoot most things. Mobile substrate supported extensions that misbehave can trigger safe mode so you can uninstall them. So it’s all a bit less of a risk.

So as of today, Apple has stopped signing 3.0 and 3.0.1 restore files. That means that if you have a 3GS iPhone you cannot restore any firmware other than 3.1. If you are happily jailbroken today and something goes wrong you are pretty much screwed. Here is a summary:

1) If you have an iPhone 3g or 2g, you are fine and should be able to restore.

2) If you have a 3gs, you can only restore 3.1 (and kiss your jailbreak good bye). If you did not get an IBSS/IBEC signature before now and you restore, you may never be able to jailbreak again.

3) If you have an iPhone 3GS and you used Cydia to save your TSS or did purplera1n or similar a while back and saved your IBEC, then you will be able to restore in the near future, but you must wait for someone smart to write a utility that will let you do it. Chances are good that such a utility will come out in a couple days. If you can be patient and wait, do so. No one wrote this utility prior to this because we were not sure if Apple would actually stop signing 3.0 – only that they *could*.

It looks like an exploit has already been found in 3.1 firmware so it sounds like a jailbreak will be possible, but again, hold out for a bit.

Apple is pushing v3.1 now. I strongly recommend you do not upgrade. If you have a 3gs, if you update now, you may never be able to jailbreak ever again. If for some reason you think you must upgrade, at the very least make sure that you get your ecid shsh done via the home page of cydia first by clicking the heart. If you didnt do this or dont understand, do not upgrade!

If you have a 3g or 2g, you will probably be ok but you should still wait a few days to see what happens with the jailbreak. 3.0 is plenty stable and there’s no rush to upgrade to 3.1. Also, whatever bug you think you have that it will fix it probably will not fix as is always the case.

As always, will keep updates here and a tutorial posted when jailbreak is released.

From apple, the 3.1 firmware changes are (notice there is nothing about battery or push, so if you have bugs in that area assume they are not fixed for 3.1). None of this seems urgent to me:

iPhone OS 3.1 also includes these features and updates:

A quick note on memory usage (and hopefully this is the last note on libhide for months to come). There have been some questions as to how much additional memory is used by moving libhide into mobile substrate. I would argue that the answer is none. Here is why. First, the dylib itself, only takes a few kbytes of memory while running. Whatever is required to load a dylib and it just makes a list of your apps so that would be an array of some strings. Literally less than 100k including the 15k to load the dylib into memory. The “old” method had some overhead also. Springboard, itself, had to keep a list of hidden apps. But since it was not just focused on hiding icons, it had to keep more information in this list. Restrictions block protocols so that had to be handled. The new dylib prevents springboard from having to keep track of these things freeing up that memory. It’s a pretty bold statement to say that with the new method you are using *less* memory, but I will say it is roughly the same.

Update: I have v2.0.3 done and released in the main repository for beta testing. Changes: apps should no longer all be unhidden after installing something from appstore or sync from iTunes. (Respring solved the problem on 2.0.2). I’ll probably release this publicly in a few hours After over a 1000 downloads and no complaints, I’m releasing it public now.

————

Bug Report: If you sync with iTunes or install an app or update from appstore, all hidden apps are unhidden. Solution: just respring and everything is back to normal. I’ll look into this for next version. This is due to my spotlight speed up code.

Update: I have v2.0.2 done and released in the main repository up for beta testing. Changes:

- You can now hide iPod app

- Further spotlight speed ups, in fact, I think spotlight is probably slightly faster with the extension than without because I bypass some logic. Recommend uninstall spotbright for better spotlight speed with this. It will work with spotbright, but both do much of the samething and libhide does it faster. In fact, I believe libhide’s spotlight is faster than spotlight without libhide because it cuts off some internal logic and makes everything visible.

- Added ability for an app to hide from spotlight search results or not. No app uses this yet.

————–

I believe I have solved the reported libhide issues and released v2.0.1 for beta testing. Please if you are capable of it update your libhide using this deb and then this command in SSH: dpkg -i libhide_2.0.1.deb.

Remember, as a beta tester you are expected to understand this may not be stable, although it does work for me tested on 3 devices. You must also be able to install this without help and report issues with a syslog if requested.

To use this, you will need bossprefs or sbsettings and simply hide some icons and unhide them. Note that mobile substrate safe mode should show all hidden icons, and a respring would hide them again.

Changes from 2.0:

1) Fixed speed issue of respring which was causing many older iphones to take forever respringing and in some cases, if enough hidden apps existed, go into an endless reboot loop.

2) Fixed major lag caused on spotlight

3) Added spotlight support for hidden apps. Spotbright is no longer needed. Your spotlight will be a bit faster if you uninstall spotbright if using libhide 2.0.1 or newer.

4) Fixed output bug in the update process and removed all the debug messages from the updater app (runs when you install from cydia only).

5) Added 2.x support. On 2.0 on 2.x firmware, you would have had no hidden icons.

For those of you worried about another mobile substrate addon for hiding apps, this also handles the hidden icons in spotlight so you may no longer need spotbright. That lets you remove one substrate in place of another.

Note: due to the all sources package adding my beta repository for users that were not capable of being beta testers, I have removed my beta repository and asked Saurik to update my main repository source that would force the beta repository to be uninstalled.

I put up a beta repository a month ago with the intent to have it host unstable packages for hacker level users that wanted to take an extra risk and were both willing and able to provide syslogs for debugging problems. This actually worked well for the BossPaper initial release.

It turns out that many users that did not fit the above description installed this repository anyway. In addition, all sources packages included it. Those “all sources” packages are dangerous and no one should ever install them.

The result of all this is that a bunch of end users have installed my latest beta updates intended for beta testers only. Due to that, I now have had Saurik release an update of the bigboss repository that conflicts with the beta repository. This will uninstall the beta repository from everyone when they upgrade the main source.

I will be posting the beta repository URL for users to manually type in for each beta test in the future and I will expect only users capable fo debugging problems (without complaining mind you) will install it.

Final Update: You can get v2.0.1 here.

Edit 2: Thanks to syslog provided by Cory Lustic and Rob Kreger, I have a fix for the springboard reload problem. Working on slow spotlight now. Should hopefully be all updated within the hour.

Edit: I am quite disappointed. This is crashing for a lot of you but not one person has offered a syslog output that can help me solve the problem. Not even one person says what firmware they are on or provides any data other than “it doesn’t work” that can be used to help solve this problem. This is in the beta repository. No one should be using that if they are not going to provide syslog output. No one should be using it if they are not familiar with SSH and know how to solve problems. Did this get tested well before posting ? No, of course not thats what the purpose of the beta repository is. It works fine for me on all 5 of my devices. With no additional information how is it ever going to be fixed?

Now because there are so many people that did not follow instructions and installed the beta repository but are incapable of using SSH or doing their part as beta testers, I am going to have to move the beta repository to a new location that requires users to type it in :(

Resolving this matter is relatively simple. Uninstall the beta repository, uninstall libhide and let it remove anything that it wants to remove. Exit Cydia and reload cydia. Refresh sources and reinstall whatever was uninstalled. It will use the old libhide and you won’t have any problems – as long as the beta repository is not present.

——–

I have rewritten LibHide and released an update to poof, categories for it. SBSettings and BossPrefs will use it instantly as soon as you install the updated libhide. Why do you care about this? Read on, I will try to be brief.

LibHide is the underlying library that lets you hide icons. SBSettings and BossPrefs use it. It works by modifying system files. In most cases, it uses restrictions to hide your application. The restrictions are backed up by iTunes and if you restore your iPhone and then restore the backup, the hidden icons are hidden still. The biggest issue with this method is that users often will hide apps and then restore the iPhone later and find that the icons are still hidden. I actually get multiple email messages a day from users that have had categories folders created, restored, then found all their icons are missing. They’re just hidden and the iTunes restoration of your backup caused it. Anyways, read on.

An alternative method to this is to use a key in the Info.plist that resides with each application. The downside here is that each time you update an app, the icon is unhidden. Not so great either.

I have managed to solve this all, I think. I have moved hiding of icons into a mobile substrate addon. That means no system files are modified. If you restore, you are back to unhidden icons as you would expect. Also, the added benefit is if you are in mobile substrate safe mode, the icons are back. This may be useful for getting to your apps in an emergency.

BossPrefs and SBSettings already used libhide so updating libhide means that the new method of icon hiding takes effect instantly. Categories and Poof, however, did not. These have been rewritten to use libhide.

Libhide is a library and is available for any developer that wants to write an app that needs to hide icon(s). You can view the example source code in /usr/lib folder after installing the library.

Finally, as a normal user, you normally don’t have to install libhide. It is installed automatically for you. In this case, libhide is an update so you should update it.

I have put it in the beta repository along with categories and poof updates. Please give me any feedback if there are specific problems. If not, I’ll move it to the “real” repository in a day or so.

For some reason, all the sudden, I have had a lot of email support questions on problem installing several packages on Icy. If you have jailbroken and installed only Icy, you need to search for “pwnage” in Icy, and install the Icy Pwnage Bundle Fix. This will solve many install issues. Very important, those of [...]

I released v0.95 with some help file updates as v1.0. It’s now officially out of beta and into major repo. Enjoy.  !function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?’http’:'https’;if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+’://platform.twitter.com/widgets.js’;fjs.parentNode.insertBefore(js,fjs);}}(document, ‘script’, ‘twitter-wjs’);lang: en_US

Edit (Aug 10): Added v0.99 into the beta repository as a 1.0 release candidate. I fixed a couple issues:

• Large camera roll images are too zoomed to see them
• Added solid color option (by request)
• Fixed broken longer time durations (like in hours) so that the image would change even though you lock the device and load apps in that time frame.

I have done some testing on 2.2.1 with BossPaper. It *mostly* works but there are a few problems: 1) The image doesn’t stop rotating because the springboard API to detect when an app is loaded changed. 2) Some settings app gui problems 3) My routine to copy dock is broken. I am not sure how much effort I am going to take to fix these things.

As it stands, I plan to release v1.0 as 3.0 only sometime later tonight baring any major issues with 0.99 reported. So far all issues seem minor.

————–

I have released a new BossPaper to the beta repository tonight. If there are no major issues, I will open this up by adding it to the main repository later this week. There are still a few things to be done, but the major feature is added: allowing to select individual images. Here are the changes for v0.95:

• Used better randomization algorithm. The images seemed to be repeating too often.
• When locked, image was switching one more time. Fixed this so that the image did not switch on lock.
• Added sequential ordering option to show images in order rather than randomize.
• Added Wallpapers folder to images to select folders.
• Added some explanation on dock replacement screen when winterboard is installed that winterboard will be used to replace the dock.
• Added single image(s) selection. You can select images by browsing the folders on the flash disk. If both images and folders are selected, all will be rotated. If you have folders selected, you must delete them if you wish to show only images. You can also preview the images.
• Made the prefs app switch paper when closed if a preference reload is required so the user “feels” like something is happening.
• Took some extra steps to make sure no timer is running if only 1 image is selected.
• Added a “delete all” button for image mode. (Note this button is intentionally difficult to press).

Here is the current status:

Bug Reports:

1) Icon labels are grey – Status: Investigating.This is default color of icons. Winterboard themes make this white. I have not yet decided if I want to touch this.

2) Lag introduced on springboard when not using fade transition – Status: Investigating. I cannot reproduce this at this point.

Feature Requests:

1) White icon label switch – Status: Investigating. Theoretically this could get into “let me choose the icon label color” which was out of scope for the project since it focuses on wallpapers, but I may do it anyway.

2) Lockscreen wallpaper – Status: Investigating.

3) Release for 2.2 – Status: Investigating.

4) Cube Transition – Status: Investigating. (I do not want to use any opengles in springboard).

5) Lock Screen Wallpaper With home button to change – Status Investigating. I like this idea and will probably get to it.

Issues reported closed out:
1) Cydia issue after installing BossPaper – Status: Closed. This is an unrelated issue. See other Cydia bug reports. The comments in this post (not the post itself) offer suggestions for resolving these issues.

2) Theme Icons – Status Closed. Icon theming is out of scope and makes bosspaper become a full winterboard replacement. I may, however, create something that allows for a pick-and-choose for various winterboard themes (this is on my todo list).

3) Image swaps while on lock screen – Status: Closed. This was not a battery issue. The image just changed one more time. I fixed it in the latest 0.95 anyway (mainly to avoid emails by concerned users). If this is a battery issue, I will consider it urgent for a fix.

4) Dock swap is confusing – Status: Closed. Added some text to the new version explaining that if winterboard is installed, winterboard handles the dock swap with a theme added by BossPaper.

5) Allow for sequential display not just random – Status: Closed. Implemented in v0.95.

6) Allow single image select – Status: Closed. Implemented in v0.95. In addition, you can pick and choose any number of images not just one. (Or just one if you want).

7) Import from stock wallpaper folder - Status: Closed. Implemented in v0.95.

iPhone OS v3.0.1 is out. So far jailbreaking works if you use dev team tools redsn0w and even ultrasn0w. Purplera1n fails. I would recommend holding off the update though. It will not offer you much, if anything, and the current jailbreak state will most likely result in a 3.0 kernel on 3.0.1. In a few days a real jailbreak tool will be released. For those of you that can’t resist, you can update and jailbreak using the guides on this site. Just point redsn0w to your 30 firmware. This works for 2g, 3g, and 3gs.

Not recommended at this time. Good news that Apple hasn’t cracked down on the 3gs hole yet.