You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Be aware, Apple has banned my iPhone 6s after running beepserv for about a week.
Initially, I have beepserv disconnecting after some time and I have to manually open the iMessage settings on my iPhone 6s to get it to send and receive using Beeper Mini on my Pixel 8. To solve this, I put the screen time out setting on the iPhone to "never" and had the screen brightness set to the lowest setting and left the iMessage setting page open. It was working fine for 5 days without any issue then suddenly it stopped working.
I tried to restore the iPhone, re-do jailbreak from the beginning and whatever I tried no registration code is provided. I tried to put a sim card in the iPhone after restoring it to factory setting and to my surprise I was unable to use iMessage on the iPhone at all! It can only send SMS but no iMessage.
I tried to connect to Apple support and the rep. asked me to perform some troubleshooting and asked to share the SN and phone number. Then she started to ask me some weird questions about my usage of the phone, like are you trying to connect the phone with a kind of virtual services, emulator, etc.. and informed me that my iPhone SN is blocked on Appel servers.
Apparently, Apple found a way to identify Beeper traffic and now they are blocking their own hardware!
UPDATE: After back and forth with the Apple rep. they agreed to unlock my iPhone "this time only" and it should be able to reactivate after a day or so. I actually have this phone for long time sitting in the drawer and I don't mind risking it for more trials, hope the Beeper team can find a way to prevent Apple from tracking their app. traffic. I will create a new Apple ID just in case they decided to deactivate my Apple ID next!
The text was updated successfully, but these errors were encountered:
They can't and won't fix anything because this crap is utterly broken and was even removed from the Google Play Store as of very recent (can't say for sure but either since yesterday or today). Sad that Apple has to be this way and keeps on being a shitshow of a company with Chinese sweatshops, but it's dead, Jim.
#22
Be aware, Apple has banned my iPhone 6s after running beepserv for about a week.
Initially, I have beepserv disconnecting after some time and I have to manually open the iMessage settings on my iPhone 6s to get it to send and receive using Beeper Mini on my Pixel 8. To solve this, I put the screen time out setting on the iPhone to "never" and had the screen brightness set to the lowest setting and left the iMessage setting page open. It was working fine for 5 days without any issue then suddenly it stopped working.
I tried to restore the iPhone, re-do jailbreak from the beginning and whatever I tried no registration code is provided. I tried to put a sim card in the iPhone after restoring it to factory setting and to my surprise I was unable to use iMessage on the iPhone at all! It can only send SMS but no iMessage.
I tried to connect to Apple support and the rep. asked me to perform some troubleshooting and asked to share the SN and phone number. Then she started to ask me some weird questions about my usage of the phone, like are you trying to connect the phone with a kind of virtual services, emulator, etc.. and informed me that my iPhone SN is blocked on Appel servers.
Apparently, Apple found a way to identify Beeper traffic and now they are blocking their own hardware!
UPDATE: After back and forth with the Apple rep. they agreed to unlock my iPhone "this time only" and it should be able to reactivate after a day or so. I actually have this phone for long time sitting in the drawer and I don't mind risking it for more trials, hope the Beeper team can find a way to prevent Apple from tracking their app. traffic. I will create a new Apple ID just in case they decided to deactivate my Apple ID next!
The text was updated successfully, but these errors were encountered: