If you are decided that you want to try setting up your phone as a new phone after jailbreaking but want to keep all your SMS, notes, bookmarks, calendars, and mail accounts, please read and follow BigBoss’ 3.0 Preparation Guide prior to setting up as a new phone.
Update 4 (6/25/09 8PM EST): My battery drainage problems seems to originate from bluetooth. I LOSE battery charge even when plugged in when bluetooth is enabled. When I shut it off, I no longer have that problem. This is a pretty big bug to have missed the beta testing, so it is either a) personal phone problem, b) jailbreaking problem, or c) SBSettings toggle bug. I’ll do more tests and update later.
Edit: I think I may have found a cause for the insane battery drainage: bluetooth A2DP. Right before I noticed the battery drainage, I tested out A2DP on my car stereo system with streaming music. I believe that before I noticed drainage the first time (2 days ago), I also tested the A2DP streaming. Another user commented that he also noticed high drainage after using A2DP.
Update 3 (6/24/09 6PM EST): I was still having a plethora of problems with my jailbroken 3.0 phone on T-mobile. The battery drainage was above the roof, it would lose a percentage every minute or so – basically draining the battery within two hours. I did everything to try to diagnose the problem, and it seemed that a full restore did the trick. So many problems seem to originate from restoring your old phone backup, ESPECIALLY if it was jailbroken before. If you are having any troubles, whether poor battery life, unstable connection, etc; I suggest doing a full restore and setting it up as a new phone.
Another problem some users faced is the unstable T-mobile signal with ultrasn0w, which seemed to originate from MMS settings in conjunction with a backup restore.
So here is what I’ve learned over the past few days about 3.0, jailbreaking, and unlocking:
- Push is broken if you hacktivated your phone (2G or 3G)
- To get push working on your iPhone 3G, you must activate with any AT&T Sim
- No known push fix for the iPhone 2G
- Some users are reporting that you cannot have Push and MMS setup at the same time using ultrasn0w. Either Push stops working or your signal becomes unstable once you enter the MMS settings in.
- In many cases, restoring your old iTunes iPhone backup will cause problems – especially if the backup was made from jailbroken phones
- Old 2.x backups seem to cause some or all of the following: Poor battery life, unstable ultrasn0w connection, and unable to launch apps
- If you have ANY problems after upgrading: restore and setup as a new phone, this will fix 90% of the problems
- Apple is a bitch
Update 2 (6/24/09): If you have an AT&T sim lying around (activated or not), you can try this method to get push working on iPhone 3G’s (from user “l1ceo1l” on macrumor’s forums):
Tip: if you SSH to /var/root/Library/Lockdown/activation_records and delete wildcard_record.plist, the next time you reboot your phone, it will ask for activation again, thus allowing you to easily put in an AT&T sim and activate with iTunes open – this should allow you to skip the restore and re-jailbreaking steps if you already are in that state.
- You need a Unactivated or Activated ATT Sim
- Take out your T-Mobile SIM and Pop in your Unactivated ATT Sim card (Just found out any ATT Sim is ok).
- Restore and Jailbreak with redsn0w
- Go to settings and turn off your 3G!
- Let iTunes activate the phone – you should get a “Waiting for activation.” message, dismiss it and Open cydia.
- Add the Ultrasn0w source repo666.ultrasn0w.com
- Install Ultrasn0w and turn off your phone
- Remove the unactivated ATT sim and insert your T-Mobile sim
- Turn on the phone, once you receive service you should get the message. “iPhone has been activated”
(If you deleted wildcard_record.plist, you can skip this step)
Update 1 (6/23/09): It seems that I did something else on top of replacing my lockdownd. Users on howardforums found out that to get push working with jailbroken phones, you MUST activate it with an active AT&T sim (sim that currently has service). I asked my friend with a legit AT&T service to send over his lockdownd and replaced mine – and it worked.
A few results have come back from both 2G and 3G users and apparently the lockdownd method does not work – after rebooting it has them activate again. Currently, the only sure way to enable push and stable ultrasn0w is to activate your phone (before redsn0w or after pwnage) with a legit, working AT&T sim.
It might have been a fluke on my part, but I apologize for suggesting a method that does not work. I will keep looking into this. The Dev Team does recognize this problem and are currently working on the push problem.
I will keep the original post intact, as it has good information to those who don’t know whats going on.
This is a notice to everyone that hacktivated your phone (either had pwnage tool activate for you or did NOT activate the phone with an active Sim before running redsn0w), your push notifications will not work – This is a known bug. You can easily test push by downloading the Free AIM app from the appstore and messaging yourself from a computer – it should work on wifi and edge\3g.
Also, if you used an inactive ATT sim (no current service) to activate your iPhone and attempted to use ultrasn0w afterwards, you might have had signal dropping problems (have full bars + data, then randomly drop signal + data every 20 seconds).
The only current solution is to activate your phone with a legit, ACTIVE AT&T sim (or whatever carrier your iphone is originally locked to). Push (and youtube) will work and you will not drop signal.
Activation remained the same since 1.x to 2.x, and you can just replace the lockdownd file located in /usr/libexec/ and chmod it 755 lockdownd is the main (and only) activation file:
Here is a working, 3.0 active-ATT lockdownd (3G iPhones ONLY):
SSH into your phone (doesn’t matter if it was hacktivated or activated with a deactivated sim) and browse to /usr/libexec/. Rename your current lockdownd file to lockdownd.old Upload the new lockdownd and chmod it to 755 Reboot your phone This *should* fix all your push or signal problems. This lockdownd is from ATT US, so it may not work with other carrier locked phones. The current lockdownd is from an iPhone 3G, so it will not work on 2G iPhones until someone sends me a lockdownd from an active-ATT activated iphone 2G. Install SBSettings so if it does not work or your phone has an endless reboot, you can SSH back in and restore your lockdownd. (sbsettings turns on openSSH after a reboot).
I have only tested this myself on an iPhone 3G and T-Mobile Sim, so please let me know if this works for you. Please note that this should only be a temporary solution until the Dev Team fixes their activation methods with jailbreaks. If push already works for your jailbroken phone and having no problems with ultrasn0w, do not bother replacing lockdownd.BigBoss Authors: Mark Bruce & Kory Lee