[Q] Help needed - no sms after rooting on DZ - G2 and Desire Z Q&A, Help & Troubleshooting

OK sooo, while making some last-minute checks before posting this thread, I finally found the solution to my problem. It was actually quite obvious if you think about it for a second, but I'll post this anyway just in case someone runs into this problem, as I spent hours figuring this one out.
Just as a reminder of my shame and stupidity, I'll just say that even with years of experience on most PC OS, and as many years troubleshouting on any of those, it didn't occur to me that I should just google the exact error message. Instead, I spent countless hours scouring forums, guides, wikis and whatnot to no avail. Also did countless google searches, just not with the exact error message. So if you're stuck anywhere on any operating system, and have an error message, just remember : GOOGLE THE DAMN ERROR MESSAGE !
So, first and foremost, the solution : go into sms app>settings and search for service center number. Then google your provider's service center number. If they're different, that's probably your problem right here. Write down the one you have just in case, and put in the one you found. Problem solved !
What happened is that while trying to resolve the APN problem and before using the info from another rom, I found some bad informations regarding my operator. I used it, including something that I thought was unrelated to sms. Well it was, and it broke the functionality.
But wait, I still have a question !
Now I'm back on stock 1.82.405.1 with S-OFF and plan to root again tonight or tomorrow following instructions in that thread : http://forum.xda-developers.com/showthread.php?t=1107911.
I plan on backing up everything (including APNs) and do it all over again. Anything I should worry about (like, not doing some specific part because I already have S-OFF) or will it be just fine ?
Here is my unfinished original message, just in case someone searches for a similar problem :
Hi,
So, I always wanted to root my Desire Z to have more control/apps/etc, and finally decided to do it yesterday. Now I have a problem, SMS won't work any more. I tested with the rooted 1.34, CM7.0.3, go sms pro, the stock app, handcent, and any combination of those. Not working.
Everything else went perfectly fine, except the sms. I had issues regarding APNs (no internet, mms), but found the info and all was working nice in cm7. Except sms.
I also tried to go unroot and go back to stock rom, no luck.
Now, I'm not sure at which point this happened between being stock and being on CM7. Here are the steps I followed :
Base situation was : stock rom 1.82.xxx (last OTA update), INFOCID was htc_102
The phone itself is a Desire Z with german keyboard (QWERTZ physical keybord)
So, I Rooted using this guide : http://forum.xda-developers.com/showthread.php?t=1107911.
Everything worked nice, nothing to report. Didn't test sms at that point though.
Backed up with ROM manager.
Then, I installed CM7.0.3 and google apps using their wiki (http://wiki.cyanogenmod.com/wiki/HTC_Vision:_Radio_and_CyanogenMod). Backed up with rom manager.
At that point, internet and mms didn't work because of a lack of APNs, so I found suitable info (restored my 1.34 save, exported apns, re-restored CM7, import apns) and everything was working like a charm.
I noticed that the phone seemed to lose data connexion quite often, but not sure if I was just unlucky or if there was a problem.
Still, everything worked nicely, except sms.
Now, that's a problem obviously, so after reading countless threads vaguely related to my problem, the consensus seemed to be "flash again". Well I did it, it didn't help.
So I thought screw that, I'll return to stock. Which is what I did. I used this guide : http://forum.xda-developers.com/showthread.php?t=835971 .
I used the 1.34 rooted rom, and the factory 1.72 from the RUU found here : http://forum.xda-developers.com/showthread.php?t=971109&highlight=vanilla+rom
I took extra care of the versions number, and didn't have to change the misc.img as in the guide, everything went smooth. Well, except it didn't turn S-ON back when I flashed the factory, so i'm still S-OFF.
I updated up to 1.82.405.1
I figured I could restore S-ON using this : http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#radio_S-ON_and_original_CID
But that doesn't seem to address my sms problem.
So, I am back on stock but with S-OFF, got a part7 and part17 backups (no idea what part17 is for, but it looks like it was created before rooting attempt).
Ideally, I'd like to re-root and go to whatever nice rom is out there, but what I want right now is sms working. Sending gives me a message after a while saying "Couldn't send text message after multiple tries". Can't send to myself or other people. Not sure if I can recieve (but I think I can't). MMS/internet works fine which is why I think it's not APN-related.
Click to expand...
Click to collapse

Related

[Q] No reception, bricked?

I´ve been searching trough internet the whole afternoon before posting, didnt find any similar.
I rooted and installed some custom roms some weeks ago. I made all the steps correctly and i got my customs roms always functional and with no problems at all.
Been using NextSense rom this last 3 weeks, all all went great. Today i decide to install the new update, 5.0 to 5.3. I did nothing special, wipe data,ext,dalvik etc and flash. As always it worked perfectly, made some calls etc. But during the afternoon i´ve lost my reception. I had all bars but seems people couldnt contact me.
Since I`ve noticed it been doing many experiments. Reflash again, reflash the radio, tried another rom (leedroid), but i cant get rid of the problem, it have different symptoms.
- After a full wipe + re flash radio (last one) + rom:
- I get bars, but cant call or receive calls nor SMS.
- I don't get bars at all
- Data connection sometimes work, some others no.
- Sometimes, after a reinstall, i get SMS of my prior lost calls, then I can make a call, only one, after that, even the bars are there, i can´t call anymore.
I´ve thought it was some kind of problem derived of Titanium Backup, but not restoring with titanium didn't help at all.
Only thing I did today, different to other days was:
adb shell
mount /system
mv /system/app/HtcLockScreen.apk /system/app/HtcLockScreen.bak
exit
To remove some lock screen i didn't want, don't think this have nothing to do, but i want to write down as much details as i remember.
Any ideas to bring back to life my little phone?
Same thing happened to me with nextsense 5.3, I am going try another ROM

[NEED HELP] WLAN/WIFI Problem at DESIRE Z

Hi guys,
maybe somebody may help me with the problem.
I am a owner of the Desire Z.
Done a Update to 2.2.1.
Used this faq for downgrade and rooting.
http://forum.xda-developers.com/showthread.php?t=905261
Afterwards i ve installed the recovery of http://www.klutsh.com/ .
First everything worked fine (WLAN etc.)
Cause i installed different Apps (Titan Backup, SMS blocker etc.) through WLAN.
Cant tell what happened but now i am having the following problem:
- Does not connect to my WIFI AP even if it worked quite well before.
- When i turn on WLAN through option menu the icon/symbol does not appear at the upper Part of the phone.
- Even closed APs (not mine) aren´t shown at the menu for the WLAN configuration.
- It is still possible to establish the internet connection to my provider and this one still works proper.
What am i doeing wrong?
Which further Infos do you need to help me with this problem?
Greetz
Jake555
Sounds like something you have installed has broke the WiFi as it was working when you first installed the ROM.
My advise would be to back everything up, do a factory wipe & then start again. This time after installing each app & its backup checking the WiFi.
This way you will find the app which is to blame & can get rid of it
Delivered by Western Union in the rain after 70 Years
You are wright with your solution of the problem.
I think this would help.
But i thought that there would be a easier and less time intensive solution like.
updating kernel, radio or something else.
Or am i wrong?
Because your solution looks more like trial and error which would takes a lot of time again.
The issue is that something is broken in your phone and it's not a common problem (you may be the only one who is experiencing it), so there isn't an accepted solution for it yet.
If you nandroid back up your phone as it is now, then wipe, you should be able to identify what app you installed or what you changed to break WiFi, from there if you wished you could restore the nandroid backup and work on fixing the problem. If you share what you learn it might be of help to anyone who runs into a similar issue in the future.
Edit - never mind, misunderstood the question.
actually i am sorry i can t tell to 100 % what changed the seetings.
have done a wipe and tryed some ealier backups which i have done before.
In one Backup the Functionality was still given and i hadn t to install from the beginning again.
If i will have again the problem i will write here a report.
greetz
jake555

[Q] Generic network failure... HELP!

Let me start by saying, I have searched all of the treads for my phone, and the ones suggested before posting a new one, with no luck. I also searched all over other sites for an answer, about 3 hours now, and still nothing that quite fits my problem..
I have a Verizon HTC Inc2
-running 2.3.4
-Virtuous Unity v2.39.0
The problem I keep running into is that whenever I flash a new rom, or do a factory reset with clockworkmod, I can never get my phone to send or recieve MMS. It always says, generic network failure. I have tried with the HTC messages app and handsent app, both failed. The data icon in the notification area usually does not even show activity. I tried wiping the cache several times, restarts, changing data and wifi settings but to no avail. Funny thing is, I can restore my phone to the first backup I made, Gingerbread 2.3.3, and then MMS works.
Any ideas as to what may be happening? I can give you any additional info you need or ask as well. I'm not a total noob, but I feel like one right now. I just can't figure this one out on my own. Thanks!
my3kgt said:
Let me start by saying, I have searched all of the treads for my phone, and the ones suggested before posting a new one, with no luck. I also searched all over other sites for an answer, about 3 hours now, and still nothing that quite fits my problem..
I have a Verizon HTC Inc2
-running 2.3.4
-Virtuous Unity v2.39.0
The problem I keep running into is that whenever I flash a new rom, or do a factory reset with clockworkmod, I can never get my phone to send or recieve MMS. It always says, generic network failure. I have tried with the HTC messages app and handsent app, both failed. The data icon in the notification area usually does not even show activity. I tried wiping the cache several times, restarts, changing data and wifi settings but to no avail. Funny thing is, I can restore my phone to the first backup I made, Gingerbread 2.3.3, and then MMS works.
Any ideas as to what may be happening? I can give you any additional info you need or ask as well. I'm not a total noob, but I feel like one right now. I just can't figure this one out on my own. Thanks!
Click to expand...
Click to collapse
General Network Error is when the system returns an error stating that you have no connectivity to send a message or an MMS (at least from my experience w/ it). I have this issue a lot with any messaging on my end because of shoddy reception. Which other ROMs besides Virtuous are you flashing that are giving this error? I know for a fact the CM7 has been having a LOT of issues with data connectivity. The last ones I remember hearing about with working data is #79 (or was it #80, I can't remember) and #85 and for a few people, #92.
I do have plenty of reception, always around 2 to 3 bars. Sorry I worded that wrong in my post, Virtuous is the only and first rom I flashed. I did it because Verizon OTA updates kept freezing my phone and I would get the blue android with the !. What I meant was, even when I did a factory reset, my MMS wouldnt work. First time I got that error, I was able to use bootloader and make a backup of eberything, then did a factory reset/wipe data and thats when I first noticed MMS was not working. So I copied the backup to my laptop, did another factory reset and format SD card, then I copied the backup to my card again, and did a restore with that backup. I restored data, cache, system, and boot I believe, and everything was back to normal and MMS was working. Unfortunetly I kept getting the OTA updates and each time, same problem, so this morning I read on a forum that a custom rom would prevent OTA updates, so I flashed Virtuous. I just found it odd that a normal factory reset, with no custom rom, would prevent MMS.
One more thing, not sure if its related, but I keep recieving messages from #6250 that say "VZWNMN: 1." Google searched that, most responses in forums are people saying they get the same thing and that Verizon told them they know nothing about it..
Have you tried a different radio?
Sent from my Incredible 2 using xda premium
my3kgt said:
I do have plenty of reception, always around 2 to 3 bars. Sorry I worded that wrong in my post, Virtuous is the only and first rom I flashed. I did it because Verizon OTA updates kept freezing my phone and I would get the blue android with the !. What I meant was, even when I did a factory reset, my MMS wouldnt work. First time I got that error, I was able to use bootloader and make a backup of eberything, then did a factory reset/wipe data and thats when I first noticed MMS was not working. So I copied the backup to my laptop, did another factory reset and format SD card, then I copied the backup to my card again, and did a restore with that backup. I restored data, cache, system, and boot I believe, and everything was back to normal and MMS was working. Unfortunetly I kept getting the OTA updates and each time, same problem, so this morning I read on a forum that a custom rom would prevent OTA updates, so I flashed Virtuous. I just found it odd that a normal factory reset, with no custom rom, would prevent MMS.
One more thing, not sure if its related, but I keep recieving messages from #6250 that say "VZWNMN: 1." Google searched that, most responses in forums are people saying they get the same thing and that Verizon told them they know nothing about it..
Click to expand...
Click to collapse
People on CM were complaining of the same exact issue. They'd get bars of reception but MMS was just broken. I was just stating that when I try to send a message thru verizon and not google voice, I often get the same error message you're getting, which means that the data is being prevented from going out. I probably should've clarified that a little better lol. When you installed Virtuous, did you do a wipe data/cache and a wipe dalvik cache?
Also, if you restore back to your Gingerbread 2.3.3 that's rooted and your MMS is working fine there, then I don't believe it could be your radio. A possibility would be the kernel, but I doubt that Virtuous would package a kernel that would crash the MMS function. And since it's any SMS/MMS app, that knocks out the possibility of it being application based. The only thing I can suggest, would be to test out another ROM. If you're looking for sense based roms, go for BAMF's (http://www.teambamf.net) or Newt's Incredible 2 HD (http://www.themikmik.com). If you're looking for an AOSP based rom, go for CM7 (found on ROM Manager or at http://www.cyanogenmod.com) or MIUI (ROM Manager again, or http://www.miuiandroid.com). If you want a hybrid, I would suggest Skyraider Zeus (http://www.teambamf.net) or Gingersense (it can be found in the development portion of XDA). Remember when you flash a rom for the very first time, I'm sure you know this already, but you need to backup your rom first and then wipe data/cache and wipe your dalvik cache. Not doing either wipe before installing a brand new rom for the first time can cause unforseen errors.
Ok I found the answer while actually looking for new radios, so thanks for the post! haha
For all you out there who might run into the same problem, this is the solution I found..
Instructions to fix MMS (by xelsewherex)
1.Go to the market and download apn backup and restore (Market Link APN B&R).
2.Create a folder on your sdcard named APNBackupRestore if it doesn't exist already.
3.Copy this file, ht tp://db.tt/9Ao5ErR, to APNBackupRestore folder (If you aren't doing this on desktop, hit menu now in xda and choose browser. File is an xml and your phone will not know what to do with it. Long press the link and use 'save link'). This is an XML doc, sorry but since I'm new I can't just post a link, just remove the spaces between ht and tp.
4.Run APN Backup Restore and press Delete Apns and then Restore from the downloaded file.
5.You should be good to go from there. MMS should now work and the softkey lights do as well.

Signal problems after update

Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.

Problems Updating OTA - Stock Non-Rooted

I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
robertlewisca said:
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
Click to expand...
Click to collapse
I was having the same exact problem. I even changed phones thru warranty. The new phone did the same thing. New SIM card didn't help. I had a guy at tech support to push the update to me.
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
IDK, co-worker with a Skyrocket has had the same issue, but he doesn't care about the update, so he hasn't bothered to get it resolved.
If I didn't have a red GS3, I could goof around and tell you that is what the problem is...
Actually, if it were me having the issue, I'd walk into AT&T and have their guys mess around with it. No telling why some have more issues than others.
robertlewisca said:
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
Click to expand...
Click to collapse
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Not really a solution but you could install this http://forum.xda-developers.com/showthread.php?t=1902178 to be fully stock LH9 with Root. Or use the OTA zip from here http://forum.xda-developers.com/showthread.php?t=1896773.
aboveusonlysky said:
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Click to expand...
Click to collapse
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
78c10 said:
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
Click to expand...
Click to collapse
You mention in your signature that your phone is rooted. So, did you update OTA then root, or did you update after rooting through some other method? The challenge some of us are having is that we are not rooted, and cannot update OTA because of the 'server error' it gives us everytime we try.
Problem Solved - for me at least
Well, the problem is solved for me, and I thought I would share what I found out here in hopes it helps someone else.
First, I had the phone replaced under warranty. It appears to be a brand new phone. When I received the new phone, I started it up, went through the normal startup stuff - entered my Google account information, it backed up my info and settings. Before I loaded any apps, I went straight to the update screen, and tried to check for an update. I again got the 'communication failed' error. Bummer.
So, then, I did a factory reset on the new phone, but this time instead of entering the initial Google account info on the startup screens, I skipped through all of the initial screens, got to the home screen, then went straight to the update screen - and this time it worked! So, it must be something to do with the initial screens, and entering Google account information that caused the problem.
Then, I got to thinking - perhaps this might work on my old phone too. Since I just got the warranty phone today, I still had my old phone (which needs to be sent back). So, I did a factory reset on it, skipped all of the initial screens where it asks for Google account information, and it still didn't work on the old phone. So, I'm not sure what the original issue was.
By the way, after the update installed on the new phone, and I went through and entered all of the Google account settings, and then checked for the update again, and there was no error.
So, perhaps this might be helpful for others?

Categories

Resources