How to Fix iOS 5 iMessage and Push Notifications on Unlocked iPhones
- Why iMessage and Push Fail on Unlocked iPhones
- Common Symptoms to Look For
- Who This Jailbreak Method Suits
- Back Up Your Device First
- Risks and Proceeding at Your Own Risk
- Installing the SAM Tweak from Cydia
- Adjusting Settings in SAMpref
- Reverting lockdownd to Its Original State
- Deactivating and Restoring Activation
- Testing Push Notifications with iPusher
- Toggling iMessage After a Reboot
- Results Across iOS 4.x, 5.0.1, 5.1, 5.1.1
Why iMessage and Push Fail on Unlocked iPhones
iMessage and push notifications look like two separate features, but on an iPhone they depend on the same plumbing. Both rely on Apple's push service, and both lean on the device identifying itself correctly to Apple's activation servers. On a stock, carrier-supported iPhone, that identification happens quietly in the background: the phone presents its serial number, its IMEI and the details of its SIM, and Apple's servers decide that this is a legitimate, activated device. Once that handshake succeeds, a persistent connection to the push service is opened, and everything from iMessage registration to alerts from third-party apps flows through it.
On an unlocked or hacktivated iPhone 3GS or iPhone 4, that handshake is where things go wrong. A hacktivated phone has been taken through a workaround that convinces the operating system it is activated without the usual blessing from Apple's servers, or that it is running on a carrier it was never officially tied to. The baseband and the activation record no longer tell the story the servers expect. In practice the phone may carry modified activation data, a patched lockdownd, or a SIM identity that does not match what the activation ticket claims. When iOS 5 then tries to register with the push service or with iMessage, the request is either rejected outright or never completes.
The visible symptoms are fairly consistent. The most common is an iMessage toggle that spins indefinitely or flips back to off, sometimes accompanied by the message Waiting for activation or a plain iMessage could not be activated error. The other is silent: push notifications simply never arrive. Mail does not alert until you open the app, messaging apps deliver nothing in the background, and badges only update on launch. Many users noticed this right after upgrading to iOS 5 or after restoring an unlocked phone, because iOS 5 introduced iMessage and leaned much harder on push than the 4.x releases did.
The reason the problem is so stubborn is that the system daemon responsible for activation, lockdownd, is the same component that unlock and hacktivation methods usually patch. To make the phone behave on an unsupported carrier or without an official activation, the patched version reports a different state than the real one would. That is fine for making calls and using data, but the push service and iMessage perform their own checks, and they expect a clean, verifiable device identity. A patched lockdownd can feed them inconsistent information, so the registration fails even though the phone appears to work normally in every other respect.
Another layer of confusion comes from the fact that behavior was not uniform across firmware versions. Reports of this problem and of successful fixes span iOS 4.x, 5.0.1, 5.1 and 5.1.1, and what worked on one release did not always work on the next. Some users found that iMessage activated on the first attempt after a tweak was applied, while others on a slightly different build needed several rounds of deactivating and reactivating. That unevenness is typical of workarounds that depend on how a particular jailbreak and unlock combination interacts with a specific version of the system software, and it is why no single recipe can be guaranteed for every device.
It is also worth understanding that this is a jailbreak-level problem with a jailbreak-level solution. The approaches discussed in the rest of this guide assume a device that is already jailbroken and has Cydia installed, because they involve replacing or reverting system files and changing how the phone reports its identity. They are not options for an unmodified iPhone, and they carry real risk. Anyone planning to try them should make a full backup first, ideally through iTunes, and accept that changing activation-related files can leave a device needing a restore. Proceed at your own risk, and treat the steps that follow as a record of what worked for other users rather than a promise of the same result on your phone.
Common Symptoms to Look For
The first thing most people notice is that iMessage simply refuses to switch on. You open Settings, go to Messages, flip the iMessage toggle, and instead of the usual brief spinner followed by a confirmation, you get a message saying that iMessage is waiting for activation, or that it could not be activated, or that you should try again later. On a device that was never officially activated through a carrier, this is by far the most common complaint. The switch may bounce back to the off position on its own, or it may stay on while the text underneath keeps saying Waiting for activation for hours, even days. An iMessage toggle that never completes activation is the clearest sign that the device's activation state does not match what Apple's servers expect.
A second, closely related symptom is a mismatch in how your messages are delivered. You send a text to a friend who also uses an iPhone, and the bubble stays green instead of turning blue. Occasionally the bubble starts out blue and then falls back to a regular SMS after a failed attempt. If everything is working properly, conversations between iOS 5 devices should travel over data and show up in blue, with a Delivered status beneath the last message. When that status never appears, or when you can only reach other iPhone users by plain SMS, iMessage is not registered properly, even if the toggle looks fine.
The third group of symptoms involves push notifications more broadly. On an unlocked or hacktivated iPhone 3GS or iPhone 4, push can fail silently without any error on screen. Mail does not arrive until you open the app and pull down to refresh. Third-party apps that rely on Apple's push service, such as instant messengers, social networks and game alerts, stop producing banners, badges and sounds. You may see the badge count update only when you launch the app manually. In some cases notifications arrive late, in bursts, or only while the phone is plugged in and on Wi-Fi. Because nothing crashes and nothing is labelled as broken, many people assume the apps themselves are at fault and waste time reinstalling them.
There are also subtler signs worth paying attention to. The Notifications section in Settings may list your apps normally, yet the option to enable alerts for some of them is missing or does nothing. After a reboot, iMessage may work for a short while and then quietly stop. Some users report that everything functioned on one firmware, then broke after an update or restore, which is why the iOS version you are running matters. Reports of this behaviour have come from devices on 4.x, 5.0.1, 5.1 and 5.1.1, and the exact pattern differs slightly from one version to the next. A phone that survived a downgrade, a baseband workaround or a re-jailbreak is especially likely to show it, since those procedures often alter the activation files that the system consults when it talks to Apple's servers.
Finally, look at what happens when you try to sign in with your Apple ID under Messages, FaceTime or the Notifications settings. If the sign-in hangs, returns a vague verification error, or succeeds but changes nothing, that points toward the same underlying cause. None of these signs prove the problem on their own, but when two or three appear together on a jailbroken, unlocked handset, you are almost certainly dealing with the activation and push registration fault that the rest of this guide is meant to address. Before changing anything, take note of exactly which symptoms you see and on which firmware, because that information will tell you which fix to try first and help you judge whether it worked afterwards.
Back up the device before touching any activation tweak, and test notifications only after a clean reboot so you know which change actually helped.
Experienced mobile repair technician
Who This Jailbreak Method Suits
This approach is aimed at a fairly narrow group of people, and it helps to be honest about who that is before anyone starts tapping through Cydia. The fix revolves around the SAM tweak and its SAMpref settings, which only exist on jailbroken devices. If your iPhone is running stock firmware with no jailbreak, none of the steps described here apply, and you would be better off using Apple's own restore tools or contacting your carrier. The same goes for anyone who bought a locked phone, never touched the baseband, and simply has a flaky data connection. SAM exists to solve a very specific problem, and applying it to an unrelated one will not accomplish much.
The people this method suits best are owners of an iPhone 3GS or iPhone 4 that has been unlocked or hacktivated. Those are the handsets where activation is faked or bypassed at the baseband level so that the phone can work on a carrier it was never meant to use. The side effect, as many owners discovered, is that Apple's activation servers never properly recognise the device, which leaves iMessage stuck on Waiting for activation and push notifications silent. If you rely on a hacktivated phone every day and have noticed that messages arrive late, arrive only when you open the app, or never arrive at all, you are exactly the audience this guide was written for.
It also suits people who are comfortable working inside a jailbroken environment and don't mind a little trial and error. Reports from users covered a surprisingly wide spread of firmware: iOS 4.x, 5.0.1, 5.1 and 5.1.1 all show up in the accounts of people who got something working. That spread is useful, but it comes with a warning. Results were not consistent from one version to the next. Someone on 5.0.1 might get iMessage activating after a single reboot, while another person on 5.1.1 needed to deactivate, restore the activation state, revert lockdownd and test again before anything changed. Treat any success story as a data point rather than a promise, and expect to experiment a bit with the SAMpref options for your own firmware.
You should be willing to work through several small steps rather than hoping for a one-tap fix. Testing push delivery with an app like iPusher, rebooting, and then toggling iMessage off and on again is a patient, iterative routine. If you want something that works instantly and permanently, this is probably not the right path, because activation workarounds can break after an update, a restore or even an unexpected crash.
This method is also a reasonable fit if you are cautious by nature, because the sensible way to approach it is slowly. Back up your device before changing anything, since tweaking lockdownd or activation data can leave a phone in a state that is awkward to recover from. A fresh backup, plus a note of your current firmware version and baseband, means you can return to a known starting point if something goes wrong.
Finally, it suits people who accept the trade-offs. Modifying system files and activation records is done entirely at your own risk. There is no official support for any of it, no guarantee it will work on your particular combination of device and firmware, and a small chance it will make matters worse before they improve. If you can live with that, and you simply want your old iPhone to behave like a normal one again, this method deserves a try. If the phone is your only line of communication and you cannot afford downtime, consider waiting until you have a spare device or a quiet weekend to experiment.
Back Up Your Device First
Before you touch a single setting, file or package, make a complete copy of everything on the device. The methods used to get iMessage and push notifications working on an unlocked or hacktivated iPhone 3GS or iPhone 4 running iOS 5 involve changing system-level components, most notably the lockdownd service, which is the background process that handles activation and communication between the phone and its servers. Even small mistakes here can leave a phone stuck at the activation screen, unable to make calls, or caught in a restore loop. A backup is the only thing that reliably lets you return to a working state, so treat this step as part of the fix rather than a formality.
The most dependable approach is to back up through iTunes on a computer you trust. Connect the iPhone with its USB cable, select the device in the sidebar, and run a full backup to the computer rather than relying on any cloud copy alone. Because these devices are old and the cloud services of that era were limited in what they stored, a local backup is the safer bet. If you want extra protection for things like saved passwords and health or keychain data, choose the option to encrypt the local backup and write down the password somewhere safe. An encrypted backup you cannot unlock is no better than no backup at all, so do not lose that password.
It is also wise to copy the backup folder itself to a second location, such as an external drive. iTunes stores its backups in a default folder inside the user profile, and a copy of that folder means a single disk failure or an accidental overwrite will not wipe out your only safety net. Keep in mind that every new backup can replace the previous one for the same device, so if you already have a good backup from before you started experimenting, duplicate it first and label it clearly with the date and the iOS version it came from.
Because the device is jailbroken, there are a few extras worth saving that a normal iTunes backup may not capture well. Make a note of the list of tweaks and repositories you have installed in Cydia, since a restore will remove them and you will want to reinstall only what you actually need. If you use any custom themes, tweaks with their own settings, or SSH-accessible configuration files, copy those over to your computer as well. Many people also keep a record of their SHSH blobs for the firmware they are running, because saved blobs may be the only way to return to a specific iOS version later, particularly on the versions mentioned in user reports such as 5.0.1, 5.1 and 5.1.1. Whether this is possible depends on the tools and the firmware in question, so check the current situation for your exact model before assuming it will work.
Note your baseband and bootloader details as well. Unlocked phones depend on a particular baseband version to keep working with a different carrier, and updating or restoring through the official route can overwrite it. If you do not know what baseband your phone is on, look it up under the general settings and the About section and keep a written record. Losing the unlock because of a careless restore is one of the most common ways people end up worse off than where they started.
Finally, understand the risk you are accepting. This process is intended for jailbroken devices only, and it is not endorsed by the manufacturer. Results have been inconsistent across iOS 4.x, 5.0.1, 5.1 and 5.1.1, meaning a procedure that worked flawlessly for one person on one version may fail or cause side effects on another. Proceed at your own risk, work slowly, and change one thing at a time so that if something breaks, you know exactly which step caused it. With a verified backup in hand, you can experiment with confidence, because the worst outcome becomes an inconvenience rather than a loss of your data.
Risks and Proceeding at Your Own Risk
Anyone who follows a fix like this should understand up front that it works by altering parts of the operating system that Apple never intended users to touch. Jailbreaking itself changes how the device boots and what code it is allowed to run, and the SAM tweak goes a step further by tampering with the way the phone identifies itself to Apple's activation and push services. That is the core of the risk: you are asking a modified system to behave like an unmodified one, and sometimes it simply refuses. A device that was working acceptably as a basic unlocked phone can end up worse off after a few careless steps, with iMessage dead, notifications still silent, or, in the unlucky cases, the phone stuck on an activation screen that will not go away.
The most important precaution, and the one people skip most often, is a complete backup before anything else is changed. Back up the device in iTunes and, if you can, keep a second copy of that backup on a different drive. Copying the backup folder somewhere safe takes a couple of minutes and can save you from an overwritten or corrupted file. A backup protects your contacts, messages, photos and settings, but it does not protect your unlock. If you restore the firmware through iTunes at the wrong moment, the baseband or activation state that made your carrier-unlocked setup work may be gone, and on some models that cannot be undone. This is why anyone relying on a hacktivated iPhone 3GS or iPhone 4 should note down exactly which iOS version and baseband they are running before touching lockdownd or deactivating the phone. The step of reverting lockdownd and then deactivating and restoring activation is the point where most people get into trouble, because it deliberately resets the state the phone uses to prove it is legitimate.
Results with this method were never uniform. Reports from users covered iOS 4.x, 5.0.1, 5.1 and 5.1.1, and the same sequence of steps that cleanly revived iMessage on one phone did nothing on another running a slightly different build. Differences in the baseband, in how the device was originally unlocked, and in which version of the SAM package and its preference settings were installed all seem to have played a part. It is entirely possible to follow every instruction correctly and still see no change, so a failed attempt does not necessarily mean you made a mistake. Equally, a success report from someone else does not guarantee the same outcome on your handset. Treat any forum post describing a working recipe as an anecdote about one device, not a promise.
There are smaller, practical risks as well. Testing with an app such as iPusher means granting a third-party tool access to push registration, and the push token it displays should be treated as semi-private rather than pasted into a public thread. Toggling iMessage off and on after a reboot is harmless in itself, but repeated failed activation attempts can leave the phone in a confused state where the setting greys out, and a full restart cycle may be needed before it responds again. Using a device on a mobile network while its identity is partly spoofed can also lead to odd behaviour with your SIM, such as messages falling back to ordinary text unexpectedly, so keep an eye on what is actually being sent and charged.
Finally, remember that this approach is intended only for jailbroken devices. If your phone is not jailbroken, or you are not comfortable with Cydia, SSH access and editing system files, the sensible choice is to stop here. Jailbreaking may affect warranty coverage, and iOS 5 itself is long out of support, so you should not expect any help from Apple if something breaks. Proceed only if you accept that you alone are responsible for the result, that data loss and a non-functioning phone are real possibilities, and that the safest fix is sometimes to leave a working device exactly as it is. If the phone holds anything you cannot replace, copy it elsewhere first, and consider testing the whole procedure on a spare device before trusting it on your main one.
Installing the SAM Tweak from Cydia
Before touching Cydia, make sure the device is in the right state for the tweak to do its job. SAM only makes sense on a jailbroken iPhone 3GS or iPhone 4 that has been unlocked or hacktivated, so if your phone is running stock firmware with an official activation, there is nothing here for you to fix. Plug the device into a computer first and make a full backup through iTunes, because the steps that follow touch system files, and a mistake with lockdownd or the activation records can leave the phone in a state that only a restore will repair. Back up before you do anything else, and understand that everything described here is done at your own risk.
| Method | What it does | Tools needed | Best used when | Pros | Cons and cautions |
|---|---|---|---|---|---|
| Install SAM and open SAMpref | Adds the Subscribers Artificial Module, which spoofs the subscriber data the device expects so that iMessage activation and push services can work on an unlocked or hacktivated phone | Cydia, repo.bingner.com source, SAM (Subscribers Artificial Module), SAMpref under Settings > SAM | iMessage will not activate and push notifications never arrive on an iPhone 3GS or iPhone 4 running iOS 5 | Addresses the root cause rather than a single symptom; free to install from Cydia | Only for jailbroken devices; results varied between iOS 5.0.1, 5.1 and 5.1.1; back up first and proceed at your own risk |
| Revert Lockdownd to Stock | Restores the original lockdownd service through the SAM settings so the device can talk to Apple's activation and push servers normally | SAM settings (Settings > SAM) | A previously modified lockdownd is blocking activation or push registration | Simple switch inside the SAM menu; undoes earlier tweaks that may conflict | Changes a core system service, so a backup beforehand is essential; may not be enough on its own |
| De-activate, then re-activate via iTunes | Uses the De-Activate iPhone option, then connects the device to iTunes to activate it again, giving a fresh activation record | SAM settings, iTunes on a computer | The existing activation record seems corrupted or stale | Clears out a bad activation state; uses the standard iTunes activation route | The phone is temporarily deactivated, so keep the computer and cable at hand; the unlock or hacktivation status can be affected |
| Backup Activation and Restore Activation | Saves the working activation data and puts it back later, found under Settings > SAM > Utilities | SAM Utilities menu | Before experimenting, or after a restore that wiped the activation | Gives a safety net so a failed attempt does not leave the phone unactivated | Only helps if the backup was taken while activation was in a good state |
| Test with the iPusher app | A free app whose Test Push Notifications button checks whether push delivery works; a pop-up reading "Yay, push notifications work fine!" confirms success | iPusher (free), Wi-Fi with active internet | You need to verify push status after each change instead of guessing | Clear pass or fail result; free; quick to repeat | Requires a working Wi-Fi connection during the test; a failed test does not say which step is at fault |
| Toggle iMessage after a reboot | Turn iMessage off, reboot the device, then turn iMessage on again so it registers with the refreshed settings | Built-in iMessage setting, device restart | As the final step once SAM settings and activation are sorted out | No extra software; often completes the fix after the other steps; also worth syncing with iTunes after the reboot | Rarely works alone; one reader on iOS 5.0.1 still got no push notifications after reboots and a sync |
Open Cydia and let it finish refreshing its sources. If it asks whether you are a user, hacker or developer, choose hacker or developer, since the default user view hides some of the packages you will need. Tap the Search tab and type SAM. The package you are looking for is usually listed as SAM, short for Subscribers Artificial Module, and it normally comes from the repository maintained by its author rather than from the default Cydia sources. If a search returns nothing, the repository is most likely missing from your source list, so go to Manage, then Sources, tap Edit, then Add, and enter the repository address given in the original tweak announcement. Wait for Cydia to reload the sources and search again.
Once the package appears, open its page and read the description and the version note before installing. This matters more than it sounds, because results varied noticeably between firmware versions. People reported the tweak working on 4.x, 5.0.1, 5.1 and 5.1.1, but not always in the same way, and an older build of SAM could behave differently from a newer one on the same iOS release. If the page lists a dependency or a note about a specific firmware, take it seriously. Tap Install, then Confirm, and let Cydia download and unpack the files. Do not interrupt it, and keep the device connected to power and to a stable Wi-Fi network while it works.
When the installation finishes, Cydia offers a button to restart SpringBoard or to reboot, depending on the package. Choose the option it presents, and if you are given a choice, a full reboot is the safer one, because the tweak hooks into services that start at boot. After the device comes back up, go to the Settings app and scroll down. A new entry called SAMpref, sometimes shown simply as SAM, should have appeared in the list. If that entry is missing, the tweak did not install correctly, and you should go back to Cydia, check the Installed tab to confirm the package is present, and reinstall it before continuing.
Do not change any SAMpref options at this point. The installation step only puts the module on the phone. The behavior that actually repairs iMessage and push delivery comes from how the settings are configured afterward, in combination with reverting lockdownd, deactivating and restoring activation, and testing with iPusher. Treat a clean, confirmed installation as the foundation, and move on to the configuration only after the Settings entry is visible and the phone has restarted without trouble.
Adjusting Settings in SAMpref
Once SAM is installed from Cydia, the real work happens in SAMpref, the small preference pane that appears in the Settings app (or as its own icon, depending on the version you installed). Open it and you will see a handful of options that control how the module presents your device to the carrier and to Apple's activation and push servers. The names can differ slightly between releases, but the logic stays the same: SAM tricks the phone into behaving as though it holds a legitimately activated SIM, and SAMpref is where you tell it how far to go with that trick.
The first thing to check is whether the main toggle for the module is switched on. It sounds obvious, yet a surprising number of failed attempts come down to a tweak that was installed but never enabled. After flipping it, do not assume the change has taken effect. SAMpref writes its values to a configuration file, and the system daemons only read that file when they start. Respring the device at the very least, and preferably perform a full reboot, so that the new values are picked up by the services that handle iMessage and push.
Next, look at the options that deal with the activation state. Some builds of SAMpref offer an entry that lets you reset or refresh the stored activation information. If your iMessage setting hangs on Waiting for activation or returns an error that the service could not be activated, use this option before anything else. Clearing a stale activation record often does more than any other single change, because a half-completed earlier attempt can leave the phone holding data that conflicts with the fresh request. If the entry is not present on your version, the same result can be reached manually by deactivating and then restoring the activation, which is covered in the surrounding steps of the process.
Pay attention to any field that lets you specify a carrier or network identifier. The aim here is to have the device report values that Apple's servers accept. Leaving a field blank, or filling it with data that does not match your SIM, is a common reason why iMessage refuses to register even though everything else looks correct. If you are unsure what to enter, use the defaults the tweak ships with before experimenting, and only change one value at a time so you can tell which adjustment made the difference. Changing several settings at once makes it nearly impossible to work out what helped and what hurt.
Results here varied considerably with the firmware. Reports exist for iOS 4.x, 5.0.1, 5.1 and 5.1.1, and the same SAMpref configuration did not behave identically across them. On one version a simple enable-and-reboot was enough, while on another the user had to revert lockdownd and re-run the activation sequence before push notifications began to arrive. Treat any settings you find in old forum posts as a starting point rather than a recipe, and match your approach to the iOS build actually installed on your iPhone 3GS or iPhone 4.
After saving your changes and rebooting, return to Settings, open Messages, and switch iMessage off and then on again. Give it a minute or two to contact the server. If the status changes to activated, you can verify push delivery with the iPusher app, sending yourself a test notification and confirming that it lands on the lock screen. If it stays stuck, go back into SAMpref, reconfirm that the module is enabled, and repeat the reboot and toggle cycle once more before trying a different configuration.
Because this whole procedure targets jailbroken devices and alters low-level system behavior, back up your device before touching any of these settings. A wrong value in the wrong place can leave the phone without a working activation state, and a backup is the only reliable way to return to where you started. Proceed at your own risk, and change things slowly and deliberately rather than all at once.
Reverting lockdownd to Its Original State
Before touching anything else, it helps to understand why lockdownd matters in the first place. On an iOS device, lockdownd is the system daemon that handles pairing with iTunes, stores activation state, and hands out the credentials that services such as iMessage, FaceTime and push notifications depend on. When a phone has been hacktivated, the usual trick is to patch or replace this file so that the device believes it has been activated by a legitimate carrier. That patch is exactly what can break Apple's activation servers' conversation with the phone, which is why iMessage hangs on Waiting for activation and why push notifications silently stop arriving. Reverting lockdownd to its original state is the step that removes the patched version and lets the device talk to Apple's servers as a stock iPhone would.
The most common way to do this on a jailbroken iPhone 3GS or iPhone 4 is through the SAM tweak. SAM, short for Subscribers Artificial Module, works by simulating a valid SIM for the parts of the system that check for one, and it comes with a companion settings panel called SAMpref, installed from Cydia. Inside SAMpref there is a toggle that lets you switch between the patched lockdownd and the original one. The usual sequence is to open SAMpref, disable the option that keeps the modified lockdownd active, and then respring or reboot so the stock file is put back in place. Do not skip the reboot; the daemon is loaded at startup, and changing the setting without restarting leaves the old version running in memory.
Once the original lockdownd is back, the phone will usually drop its activation status, and that is expected rather than a sign that something went wrong. At this point many people report that iMessage can finally be switched on, because the device is now presenting honest credentials to Apple. If the toggle still refuses to stick, go to Settings, then Messages, turn iMessage off, restart the phone completely, and turn it on again afterwards. This off, reboot, on rhythm is the single most repeated piece of advice across user reports, and it seems to work because the first toggle clears a stale registration attempt that would otherwise keep failing.
Results were not uniform across firmware versions, and anyone following this approach should keep that in mind. Reports exist for iOS 4.x devices that needed the lockdownd reversion for push to function, as well as for 5.0.1, 5.1 and 5.1.1, but the exact behavior differed. Some users on 5.0.1 found that reverting was enough on its own, while others on 5.1 and 5.1.1 had to deactivate and then restore activation through the SAM settings before iMessage would register. There is no single sequence that is guaranteed to work on every build, so treat the steps described here as a starting point and be prepared to repeat a stage if the first attempt does nothing.
When the original lockdownd is in place and the phone has been rebooted, you can verify push delivery with a small utility such as iPusher, which sends a test notification to the device and shows whether the push connection is alive. If the test arrives, the daemon is behaving properly and iMessage should follow. If it does not, go back to SAMpref, confirm that the settings were saved, and repeat the revert and reboot cycle once more before trying anything more drastic.
A few cautions belong here. This whole method only applies to jailbroken devices, since SAMpref and the file changes require root access that a stock phone does not have. Make a full backup before you start, ideally through iTunes and, if you are comfortable with it, a copy of the original activation files as well, because a mistake with lockdownd can leave a phone stuck in an unactivated state. And as with any modification of this kind, you proceed at your own risk: the process is unofficial, firmware-specific, and not supported by Apple, so there is no guarantee that a particular device will respond as described.
Deactivating and Restoring Activation
When iMessage refuses to activate or push notifications stay silent on an unlocked iPhone, the root cause is usually the activation state stored on the device rather than anything wrong with the apps themselves. Hacktivated phones carry a patched activation record, and that record can drift out of step with what Apple's servers expect, especially after an update or a restore. For that reason, the step of deactivating and then restoring activation tends to sit at the heart of every working repair, because it forces the phone to rebuild the very thing that went wrong. This approach applies to jailbroken devices only, and it is worth saying plainly that you should back up the device before touching anything and accept that you are proceeding at your own risk. A full backup in iTunes, plus a copy of any important tweaks or settings, takes a few minutes and can save an afternoon of frustration.
Begin by making sure the SAM tweak is installed from Cydia and that its preference pane, usually called SAMpref, is available in the Settings app. SAM stands for Subscribers Artificial Module, and its job is to present the phone to the system as if a valid, activated SIM were present, which is what iMessage and push services check for. Open SAMpref and look at the options it offers. Reports from users on iOS 4.x, 5.0.1, 5.1 and 5.1.1 all point to the same lesson: the right combination of settings differs from one firmware version and one device to the next, so treat any configuration you read about as a starting point and not a guarantee. If SAM is currently set to run in a mode that does not suit your firmware, switching it before you deactivate can make the difference between a clean result and a repeat of the same failure.
Next comes the deactivation itself. With SAM enabled and your settings noted down, you remove the existing activation by reverting lockdownd to its original state, since the patched copy is what keeps presenting the wrong credentials. Many guides handle this by using the tweak's own option to restore the stock lockdownd file, or by swapping in the untouched original through a file manager. Either way, the point is to return the system daemon to a factory condition so the phone can negotiate activation afresh. Once lockdownd is reverted, the device will usually report that it is not activated, and the familiar activation screen may appear. That is expected, and it does not mean something has broken.
Restoring activation is the part that makes people nervous, but it is mostly a matter of patience. Reapply the activation using the same method you originally used to hacktivate the phone, or the one supplied with your SAM setup, and then let the device settle. Do not launch Messages or any push-dependent app in the middle of this process. Reboot the phone once activation has been restored, and wait until the springboard is fully loaded and the signal indicator has stabilised. Rushing this stage is one of the most common reasons people end up repeating the whole procedure.
After the restart, open Settings, go to Messages and toggle iMessage off, wait a few seconds, then switch it back on. The phone should attempt to register, and in successful cases the status changes from a spinning activation message to the green, ready state. If it hangs, turn iMessage off again, reboot once more, and repeat the toggle. Some devices needed two or three cycles before the registration went through, and that stubbornness is normal for unlocked hardware on newer firmware.
To confirm that push notifications are really working and not just appearing to, use a test app such as iPusher, which lets you send yourself a notification and see whether it arrives. A successful test tells you the push channel is healthy, and any remaining trouble then lies with an individual app's own settings. If nothing arrives, go back to SAMpref, adjust the configuration, and run the deactivation and restoration sequence again, keeping notes on what you changed each time so you can tell which adjustment helped.
Testing Push Notifications with iPusher
Once the SAM tweak is installed and configured, the most reliable way to find out whether your fix actually worked is to stop guessing and send a real push notification to the device. This is where iPusher comes in. The app is a small utility that was popular in the jailbreak community for exactly this purpose: it lets you fire a test notification at your own device so you can see, in a few seconds, whether the connection to Apple's push service is alive. Because it is a Cydia-era tool, it is only relevant for jailbroken iPhone 3GS and iPhone 4 units still running iOS 5 or thereabouts, and it should be treated as a diagnostic aid rather than a permanent part of your setup.
Start by installing iPusher from Cydia, using the same repository habits you applied when you added SAM. Search for the name, check that the package matches your firmware branch, and install it. Depending on the build you find, it may ask for a respring or even a reboot afterward. Do that, and then open the app from the home screen. Do not run the test immediately after changing SAMpref settings or reverting lockdownd. Give the device a clean restart first, because the push daemon only reads the new activation state during boot, and a test performed too early will almost always report a failure that is not real.
When iPusher opens, you will see that it works in a straightforward way. It tries to register the device with Apple's notification service and then sends a message back to itself. If the registration step succeeds, you should see a banner or hear an alert tone within moments. If nothing appears, the problem is almost certainly still in the activation or token layer, not in the app. A missing banner combined with a clean registration message usually points to notification settings, so open the Settings app, go to Notifications, and confirm that iPusher is allowed to show alerts, badges and sounds. Without that permission, even a perfectly working push connection will look dead.
If the test fails outright, resist the urge to reinstall everything at once. A more patient sequence tends to work better. First, confirm that the device has a working data connection, preferably Wi-Fi, since push traffic depends on stable network access and many carrier-unlocked phones have unreliable cellular data settings. Second, open SAMpref again and verify that the toggle for the tweak is actually enabled for the services you need, because it is surprisingly easy to leave a switch in the wrong position after a restore. Third, if you earlier reverted lockdownd, check that the replacement was applied cleanly, since a half-completed revert can leave the device in a state where activation looks fine but push tokens are never issued. Reports from users varied here depending on the firmware: those on 4.x often had an easier time than those on 5.0.1, while 5.1 and 5.1.1 owners more frequently needed to repeat the deactivate-and-restore step before the test would pass.
Once iPusher confirms that a notification arrives, the next move is the one that trips up many people: toggle iMessage off and back on after a reboot. Go to Settings, then Messages, switch iMessage off, wait a few seconds, and switch it on again. The device should attempt activation and, if the push layer is healthy, complete it without the endless spinning indicator. Doing this before the reboot, or without having verified push first, is a common reason the activation keeps hanging. Sending a test message to another iOS device afterward, and watching whether the bubble turns blue, gives you a practical final confirmation.
Keep in mind that results were inconsistent across the community, and no single recipe worked for everyone. Before you experiment further, make sure you have a current backup, and accept that you are proceeding at your own risk. If iPusher keeps failing after several clean attempts, restoring the firmware and starting the process again from a fresh state is often quicker than chasing a corrupted configuration one setting at a time.
Toggling iMessage After a Reboot
Once the tweak is installed, the settings are configured and the device has been restarted, the last stage of the repair is the one people most often skip: switching iMessage off and back on after the reboot. It sounds trivial, yet on iOS 5 devices that have been unlocked or hacktivated it is frequently the step that decides whether the service registers or keeps spinning forever. The reason is fairly simple. iMessage performs its registration handshake with Apple's servers at the moment you flip the toggle, and it reads the identity values that the activation daemon presents at that moment. If you flipped the switch before the reboot, the handshake may have been made with the old, unpatched values, and the device carries on using that stale result until you force a fresh attempt.
Start by letting the phone finish booting completely. Wait until the home screen is fully loaded and the signal bars or Wi-Fi icon have settled, because toggling too early can cause the registration request to fail silently. If the device was jailbroken with a tethered method, boot it through the usual tethered procedure first, otherwise the tweak will not be loaded and nothing you do afterwards will matter. Make sure a working internet connection is available, ideally Wi-Fi, since cellular data on an unlocked handset with a foreign SIM can be unreliable during activation.
Now open Settings, tap Messages and switch iMessage to the off position. Leave it off for a few seconds, then go back to the Home screen, wait a moment, and return to switch it on again. Give the phone at least half a minute after turning it on. You will usually see a message such as Waiting for activation, and on a successful run it clears by itself and the toggle stays green. Some users reported that the spinner lingered for a minute or two before resolving, so patience is worth more than repeated tapping. If an error appears instead, do not keep flipping the switch over and over; each failed attempt can make the server less willing to respond for a while.
When the first attempt fails, a short sequence often helps. Turn iMessage off, then toggle Airplane Mode on and off to reset the radios, and try again. If that still produces nothing, reboot once more and repeat the toggle from the beginning. Several people found that it took two or three full cycles of reboot and toggle before the registration finally stuck, particularly on iOS 5.1 and 5.1.1, while others on 5.0.1 had it working on the first pass. Reports from devices still on 4.x were more mixed, mostly because the iMessage feature itself only exists from iOS 5 onward, so the push part was the only thing being repaired there.
To confirm the result, send a message to another iMessage user and check that the bubble is blue rather than green, and that the text appears in the conversation as Delivered instead of falling back to SMS. After that, use the iPusher test again to verify that push notifications arrive while the app is closed. If both work, leave the settings alone. Avoid toggling iMessage unnecessarily from this point on, because every new registration is another chance for the values to be overwritten, and avoid restoring or updating the firmware without first noting your working configuration.
Keep in mind that this whole approach is meant for jailbroken devices only, that outcomes differed noticeably between iOS versions, and that a current backup should exist before you touch anything. Proceed at your own risk, and if the toggle still refuses to hold after several clean cycles, restoring the activation state and starting the process over is usually more productive than forcing the same step again.
Results Across iOS 4.x, 5.0.1, 5.1, 5.1.1
Reports on the SAM approach came in from a wide spread of firmware versions, and it is worth understanding that the outcome was never uniform. The method was first discussed in the context of iOS 5.0.1, which is where most of the early success stories originated. Users on that release described a fairly clean sequence: install SAM from Cydia, adjust the settings in SAMpref, restore the original lockdownd, deactivate and reactivate the device, then reboot and toggle iMessage. For a large share of those people the green light appeared within a few minutes, and push notifications for third-party apps started to behave again shortly afterward.
On iOS 5.1 and 5.1.1, the picture was more mixed. Many users confirmed that the same steps worked without any changes, particularly on iPhone 4 units that had been unlocked with a standard baseband workaround. Others found that the process needed to be repeated two or three times before iMessage finally accepted the activation. A common pattern was that the first attempt failed with the familiar waiting for activation message, while a second attempt after a full power cycle succeeded. This is why patience matters more than any single setting. If the iMessage toggle hangs, switching it off, rebooting and trying again is a legitimate part of the procedure rather than a sign that something has gone permanently wrong.
The iPhone 3GS tended to be slower to respond than the iPhone 4. Several reports mention that activation on the older hardware could take noticeably longer, and that push notifications sometimes arrived only after the device had been left connected to Wi-Fi for a while. That delay is not necessarily a failure. Before assuming the fix did not work, give the device some time on a stable wireless connection and send a test push through iPusher, since that app gives a clear answer about whether the push channel is alive.
The 4.x reports deserve a separate note. iMessage itself does not exist on iOS 4, so for those devices the relevant problem was almost always push notifications rather than messaging. Users on 4.x who had hacktivated their phones sometimes lost push delivery after restoring or changing activation state, and the same SAM and lockdownd steps were reported to bring it back. Since the messaging side was irrelevant there, success on 4.x was judged purely by whether iPusher received its test notification and whether apps such as mail clients and chat tools alerted normally again.
It is also fair to say that some users never got a result at all. Reasons mentioned in discussions include an incorrectly restored lockdownd file, a SIM or baseband state that conflicted with the activation request, and leftover tweaks from earlier unlock attempts. If the procedure fails repeatedly, the most reliable course is to check the lockdownd step first, because an incomplete restore was the single most frequently cited cause of a stubborn failure. Confirming that the original file is truly back in place before deactivating saves a lot of wasted attempts.
Whatever firmware you are running, treat every report as anecdotal rather than guaranteed. Results depended on the exact hardware, the unlock method used, the Cydia packages installed and even the timing of each step. Make a full backup before you start, accept that you are modifying system files on a jailbroken device, and proceed at your own risk. Used carefully, the approach restored iMessage and push for many people across iOS 4.x, 5.0.1, 5.1 and 5.1.1, but it was never a one-size-fits-all cure, and a little experimentation with repetition and reboots was frequently part of getting it to stick.
Published: 19. 11. 2026
Category: lifestyle