Hi,
I'm on a Rooted (CWM) Nexus 5 running SlimKat 4.4.4.
I have used my viber account activated on a prepaid US number T-mobile (while living there last year ) for a long time. I now live in Sweden (since march 2015) and have changed the SIM to a swedish number +46 without any problem still using the same old US viber account. Recently I froze Viber (using SD Maid) for a month then when I unfroze it, it asks for activation and I cant receive an activation code to the old US number even though its active, inserted in phone and has sms credits. I have received refill smses for the US number just now which helps me conclude that the receiving function is ok.
I have backed up Viber with Titanium Backup, restored app+data even app or data separately. What happens is I get into my Viber account and I see all messages as usual, then it stops and the activation screen appears again.
Ive read all threads here on viber backup of messages and similar, many questions were exactly formulated in a way that would solve my problem, but they never got answered. A new question seemed to always hijack the original.
To conclude:
1. Can I alter any viber db file to just skip activation?
2. How can I get into my viber account again not loosing ANY data?
PLEASE help me...I dont wanna loose all my messages especially from my loved one.
Thanks!
Related
Starting about 3-4 weeks ago, I noticed I haven't been receiving any SMS messages (web-to-phone, phone-to-phone or voice mail). I can send messages, however I do not receive them.
I called T-Mobile and they "reset" the SMS account with no avail (still open ticket).
I checked the processes and "smsreceive.exe" is running as a process.
Any recommendations? :roll:
Thanks in advance!
JS
XDA I, T-Mobile USA
Pocket PC 2003, v4.20.1081
ROM 4.00.11 ENG, 6/23/03
Radio 6.24.00
Protocol 324.e4
Try another SIM on your device or try your SIM on a normal phone
It might be a barring problem on your SIM
make sure the country code is set correctly
There is a certain backup program that has this bug, it knackers your abil;ity to receive sms if you have backed up and restored your sms folder. Do a search on "sms backup".
Yeah, and the program is called Sprate Backup. There was a thread about it not long ago, just search for it.
It's supposed to be Sprite backup, not Sprate
I recently had a problem where my htc Evo 4G LTE on the Sprint network. I'm posting this here because the Service Rep told me they were seeing a lot of issues like this lately, and I couldn't find anywhere else where this problem had been solved online.
Symptoms:
Phone would not send or receive text messages
Phone would not receive MMS messages
Phone would not generate any error on sending MMS messages, but message would never be received
Calls and data would function as normal
If number is Google Voice integrated, Voice would not receive text messages either.
Solution:
Find an old phone
Write down the MEID of both phones
Find a third phone to use to call Sprint (since you'll be activating/deactivating the other phones throughout the call), and know your account PIN/be able to verify your account
Call Sprint Customer Support (888-211-4727), and punch the appropriate numbers until you are talking to someone
Have them switch your number to the old phone's MEID. Make sure the old phone is activated.
Have them switch your number back to the new phone's MEID. Make sure the new phone is activated.
Texting should be working on your new phone again.
Notes: The old phone may not be necessary. It may be enough for the Sprint Service Rep to deactivate your phone and then reactivate it. But I figured I would write out the EXACT method that solved the problem for me, since I am positive that this method has worked at least once. I have neither the means nor the desire to recreate the problem, so I will have to leave testing of other methods to the next person that experiences this problem.
More information (including a more detailed retelling of how my phone was fixed) can be found in This Thread. (Yes, parts of this post are copy/pasted from the linked thread. Sue me.)
Anyway, I hope this saves someone some trouble (and if it does, feel free to hit the thanks button).
My Galaxy Note II can receive and send phone calls, I can use data over the 3 network and I can receive texts, but I cannot SEND texts.
My Note II is rooted, unlocked and running Jelly beans rom V5 on the 3 network in Scotland on a pay as you go SIM card. The SIM card works in my other UK phone (unlocked Nexus S), i.e. I can send texts when it's in the Nexus.
I have never been able to send texts with the 3 SIM card in the Note II, (as in this isn't something that was working and stopped, it never worked). My note II was able to send texts when it was on the Verizon SIM in the states.
After I send a text, the "view message info" screen show it as sending to a +44 number and says sent. Several hours later (after the recipient in question never receives the text) I get a text from +441144 (then recipients number) with a message stating " Your text - to - speech message to 01144 (number of recipient) has been rejected by recipient phone."
Calling my +44 contacts works just fine.
I have no idea how to fix this issue. Does anyone have any ideas/ similar issues with their Verizon note II abroad ?
Thank you for your help and time
Using rooted Verizon phone to text on UK three network
I had the exact same problem, three network, using a Verizon S3 with synergy ROM and a hacked APN (as Verizon would not allow APN to be added), I guess you figured that bit out? Using APN Manager Pro running as a system app as set by Titanium Backup Pro.
You also have to make sure you have all the right APN settings, this was done to make DATA work on the phone.
Now the problem you describe is exactly what we had, it's the format of your phone numbers in your contact list, for UK numbers while in the UK, you DO NOT use the +44 or 44... just enter the number as normal 0745 xxx xxx etc... and that fixes the problem. Btw It's quicker to log into your gmail account and edit all of your phone numbers in there, presuming you use Gmail to sync your contacts and not verizon backup as that won't work over here when off their network.
This does cause another problem though, if you happen to use Viber, then viber will not see the contact, so what you do for that is add ANOTHER entry in the same contact, so I use the WORK field, and you enter +44 745 ... you must have the + in there and you must drop the zero, this way normal text works using the MOBILE entry in UK format, and Viber can see the contact in thge WORK entry... all appears to work doing this.
I know it's off topic and you may not use viber, but if you do, then your USA contacts would have to change your phone book entry to +44 745 xxxxxx again including the + and international country code and they can then see you as a viber contact. To see my USA contacts I changed my entries to +1 xxx xxx xxxx, so an orlando number might be +1 407-999-9999 then Viber can see the contact, just use multiple entries within the same contact, there are plenty of fields available.
Hope all of this helps, took some time to figure it all out
Mark
Melian06 said:
My Galaxy Note II can receive and send phone calls, I can use data over the 3 network and I can receive texts, but I cannot SEND texts.
My Note II is rooted, unlocked and running Jelly beans rom V5 on the 3 network in Scotland on a pay as you go SIM card. The SIM card works in my other UK phone (unlocked Nexus S), i.e. I can send texts when it's in the Nexus.
I have never been able to send texts with the 3 SIM card in the Note II, (as in this isn't something that was working and stopped, it never worked). My note II was able to send texts when it was on the Verizon SIM in the states.
After I send a text, the "view message info" screen show it as sending to a +44 number and says sent. Several hours later (after the recipient in question never receives the text) I get a text from +441144 (then recipients number) with a message stating " Your text - to - speech message to 01144 (number of recipient) has been rejected by recipient phone."
Calling my +44 contacts works just fine.
I have no idea how to fix this issue. Does anyone have any ideas/ similar issues with their Verizon note II abroad ?
Thank you for your help and time
Click to expand...
Click to collapse
I'm having this problem too, on a Samsung Galaxy Stratosphere 2 that I imported from America (it's got a slide-out keyboard, we don't have them over here), also rooted and running on the three network.
I've changed all my +447 contacts to 07 but texts only send successfully when I start a new conversation and pick the 07 recipient. When they text me back the number at the top changes to +447 again and I can't reply without starting a new conversation.
Any tips?
possible workaround
I've installed Handcent to replace the stock sms app and it seems to be working well so far. As far as I can tell, replies are successful and the number doesn't default to +44
Hello everyone,
I am rooted and locked runinng MOF 2.3.5 ish v2.0.
Yesterday AM I started receiving an error (unable to send text) when trying to send texts through GO SMS. I also received the same error when using the stock messaging app. Then I discovered I was also not receiving texts. I can send and receive texts through Google Voice. I integrated my Google number with Sprint several months ago. I had made no changes to Google voice settings, or my text settings in several months. This just came out of the blue.
I tried restoring a backup from Titanium, that did not work. I tried de-linking Google voice from my phone and that did not work. I uninstalled GO SMS- still nothing. I have since re-linked Google voice to my Sprint # as it is the only way I have of receiving my messages.
Today I called Sprint. After a few tests with no luck, they instructed me to accept the OTA 2.3.5 update. They claim that one of the issues fixed in this OTA update was a fix of this "known issue with SMS". I told them I did not want to do that because it would perma lock my boot loader. They also suggested having them de-link Google Voice from my Sprint #. They said that if they de-linked Google Voice, I would not be able to re-link Google voice to my number later and that was a "known issue" with Google.
So, I have 3 options...
1) Keep it as is until upgrade time, but of course Google Voice does not have MMS support. And Google Voice leaves a lot to be desired with SMS threading and customization.
2) Take the OTA upgrade and "hope" it solves my texting issue, but of course that opens another can of worms with the bootloader.
3) Have them de-link Google Voice and hope that works. However, I enjoy having one number when I travel, etc. And if it doesn't work, according to them I wont be able to re-sync and then I will not have any access to my texts.
Has anyone else ran into this issue? I didnt see the exact issue in a Google search.
Thanks in advance
I also use Google voice to manage/backup my voicemails and texts remotely. I hate the google voice app. I only use it in it rare situations where I have no signal and no roaming available, but have wifi.
This has happened to me a couple times, I'll notice my gvoice has texts that my phone never received via SMS.
What is your preffered network set to? I've noticed my prefered network mode changes mysteriously on this phone. I'll just set it back normal and all my missed sms come flooding in.
Sent from my MB855 using xda app-developers app
Thanks for the reply. I normally set to automatic. I just checked and it was changed to any cmda. I will play with the options and see if that helps. Thanks again.
type in *#*#4636#*#* on the phone dialer
Sent from my MB855 using xda app-developers app
Hello, it was on CDMA Auto (prl). What do you generally set yours on for domestic use?
Your answer got me thinking. Saturday afternoon I removed a sim card from another country because I was here in the us and didn't need it. So when I got home I put the sim card back in and switched network to automatic and then all my texts arrived. Thanks again :thumbup:
Hi all,
I recently lost or had stolen my S3. Its on t-mobile uk. Its been reported and blacklisted. Unfortunately due to the battery nearly dead and having it blacklisted and maybe the sim removed i could not track and wipe via Samsungdive. Could anyone please advise what will be visible on the screen etc. T-mobile have said only the phone connection, mobile internet and sms are essentially blocked. Im concerned about other data such as already downloaded emails, texts ect being visible and navigation around the phones file system being possible. Would someone be able to look at email apps(system default, gmail and yahoo) or the text app on the phone? Also if a new sim is inserted, would that by any chance effectively create a new profile thus preventing anyone from viewing my old emails and texts etc. I have changed all my passwords. However im thinking of transferring all my emails to new email accounts, deleting the emails from the old accounts and setting the passwords for the old email accounts back to the same as on the phone. Then if the phone connects by wifi the email apps should hopefully update and delete the emails on the phone. Of course hindsight is great and I know I should have had a phone lock in place.
Cheers
A
If you didn't have any lock at all then everything on the phone will be available, IMEI locking will only prevent the phone connecting to mobile data, making calls or sending texts. Inserting a new SIM won't remove anything.
If you had set the email client to leave emails on the server then you can download them to your pc, delete them from the server, which would delete them on the phone if wifi connection is ever made.
Unless you had your visa card details on speed dial I wouldn't worry too much, it's probably already been factory reset and sold to a mug in a pub.
Thanks for the reply. Ive just noticed....... I changed my google password as a precaution. Ive just switched on my nexus7 and of course it asked for the new password. Therefore I guess if the lost S3 makes a wifi connection it will also ask for a password.
Edit** Sorry it asked for the password because I was connecting to the play store not upon switching on the nexus