I flashed a custom rom to an HTC ARIA. After working w/ it for a short period I realized it would work for the users needs. I odined back to stock then flashed Froyo 2.2. It works well except for one major issue. At the end of a phone call, the screen/phone seems to freeze. When the phone switches to "black screen mode" (during conversation) it doesn't switch back to screen on and the power button doesn't wake it up. The only way to wake the phone up is by removing the battery.
I've searched the web and XDA but I don't even know how to phrase this as a question!
tomween1 said:
I flashed a custom rom to an HTC ARIA. After working w/ it for a short period I realized it would work for the users needs. I odined back to stock then flashed Froyo 2.2. It works well except for one major issue. At the end of a phone call, the screen/phone seems to freeze. When the phone switches to "black screen mode" (during conversation) it doesn't switch back to screen on and the power button doesn't wake it up. The only way to wake the phone up is by removing the battery.
I've searched the web and XDA but I don't even know how to phrase this as a question!
Click to expand...
Click to collapse
So just to be clear, you now have a Aria that has the official HTC Froyo 2.2 ROM installed, correct? The symptom would point to faulty proximity sensor.
First thing I would try would be a hard reset. Here is a reference:
http://community.htc.com/na/htc-forums/android/f/96/t/3451.aspx
If the problem still exists, you may want to consider it a hardware problem and take it back to AT&T.
tpbklake said:
First thing I would try would be a hard reset. Here is a reference:
http://community.htc.com/na/htc-forums/android/f/96/t/3451.aspx
Click to expand...
Click to collapse
Yes it is the official HTC 2.2. This issue didn't exist prior to the install
tomween1 said:
Yes it is the official HTC 2.2. This issue didn't exist prior to the install
Click to expand...
Click to collapse
So have you tried a hard reset as suggested? If that didn't work, you might want to run the Froyo 2.2 RUU again and reflash the image.
Since it is an official AT&T update, you should be able to call AT&T and report the issue.
tpbklake said:
So have you tried a hard reset as suggested
Click to expand...
Click to collapse
No, sorry, could you run these steps by me?
tomween1 said:
No, sorry, could you run these steps by me?
Click to expand...
Click to collapse
I posted a link in my original response. Dude I'm trying to give you the benefit of the doubt, but I must admit some of the issues and questions you have been posting in the Aria forums almost sound like you are trolling...
tpbklake said:
I posted a link in my original response. Dude I'm trying to give you the benefit of the doubt, but I must admit some of the issues and questions you have been posting in the Aria forums almost sound like you are trolling...
Click to expand...
Click to collapse
Please stop w/ the "trolling" thing I am not! I am having legitimate issues. Thank you for the link, I did miss that.
I have completed the hard reset, this hasn't fixed the issue.
tomween1 said:
Please stop w/ the "trolling" thing I am not! I am having legitimate issues. Thank you for the link, I did miss that.
I have completed the hard reset, this hasn't fixed the issue.
Click to expand...
Click to collapse
OK, hard reset didn't work and since you are on the official AT&T Froyo update, you don't have a lot of options to try, since that version is unrootable at this time.
Option 1 is to re-run the Froyo 2.2 RUU update just to make sure you have a good flash.
Option 2 is to call AT&T and report the issue. Although the proximity sensor is hardware and it is acting like a hardware issue, it could well be a software issue with the new ROM.
tpbklake said:
OK, hard reset didn't work and since you are on the official AT&T Froyo update, you don't have a lot of options to try, since that version is unrootable at this time.
Option 1 is to re-run the Froyo 2.2 RUU update just to make sure you have a good flash.
Option 2 is to call AT&T and report the issue. Although the proximity sensor is hardware and it is acting like a hardware issue, it could well be a software issue with the new ROM.
Click to expand...
Click to collapse
OK before I go to AT&T w/ the problem, would I just run the HTC sync to upgrade to 2.2 again? Basically flashing 2.2 over itself?
tomween1 said:
OK before I go to AT&T w/ the problem, would I just run the HTC sync to upgrade to 2.2 again? Basically flashing 2.2 over itself?
Click to expand...
Click to collapse
Yes, you would be reflashing the 2.2 upgrade over itself.
tpbklake said:
Yes, you would be reflashing the 2.2 upgrade over itself.
Click to expand...
Click to collapse
I'll give that a try, thank you.
Related
Unlocked, flashed radio, DCD 2.1 (WM 6.1).
I've had complaints from people who said they sent me texts which I never received. Happening from Sprint users and other networks too. Estimating approx 40-50% loss. Could this be ROM related?
Also noticing the lack of voicemail notification when messages are left.
Any ideas? Did I miss something?
Derp....missed the release of 2.2.3.
Will try that now.
Ok, tried 2.2.4 and still verified lost messages.
ROM or Sprint? Any way to tell?
Mirlyn said:
Ok, tried 2.2.4 and still verified lost messages.
ROM or Sprint? Any way to tell?
Click to expand...
Click to collapse
Probably not. Best you can do is flash it back to a stock Sprint rom/radio, and see if the problem persists. And even then you can't be sure what it is. But it might give you an idea.
Got the stock rom now, but its not flashing. Says check your updater.
I'm guessing I have to downgrade the radio or something. Is there a howto on reverting?
Mirlyn said:
Got the stock rom now, but its not flashing. Says check your updater.
I'm guessing I have to downgrade the radio or something. Is there a howto on reverting?
Click to expand...
Click to collapse
It's been discussed before, but I don't know if you can easily find a how-to. I'm sure someone here knows better, since I've never actually done it myself. You'll need to downgrade both the ROM and the Radio for sure. You'll probably have to downgrade the bootloader as well, and might even need to re-lock it. Hopefully somebody with experience will chime in and set us straight.
I've had complaints from people who said they sent me texts which I never received.
Click to expand...
Click to collapse
Yup. Me too and I'm on Alltel. I blame the radio. Had to go back to dcd 1.6.10.
billcohen said:
Yup. Me too and I'm on Alltel. I blame the radio. Had to go back to dcd 1.6.10.
Click to expand...
Click to collapse
Did that fix it, or did you have to downgrade the radio too?
Tried 1.6.10, but it locks up on the boot screen. I got into the bootloader and am trying 2.2.3 now.
Running 2.2.3 now. Did a hard reset (##RTN#) and after re-provisioning, it seems to be better. All test messages have come through.
Just FYI.
Mirlyn said:
Did that fix it, or did you have to downgrade the radio too?
Click to expand...
Click to collapse
Since I blame the radio, I downgraded. I miss the threaded SMS but knowing I get all messages is more important to me.
So there are posts about the Verizon update. Install or don't?
There are posts about AGPS - Why is this important? I thought phones with true GPS didn't need aGPS?
There are posts about PRI's - I have no clue what that is even about!
And another post telling people to shut up..
I am so confused right now I have no clue what to do any more! LOL
Update to VZ's MR1? Or am I holding on for something better?
Do I use GPS? Ehh.. Id'e like to use GPSTracker, so far it's not working very well with out GPSGate installed. And I like to have Tomtom installed as a backup. It works OK.. Very slow to lock on though.
However, with my desire to keep GPS intact, my S2U2 has stopped working, so I uninstalled it. ThrottleLauncher started breaking (even though nothing changed) so that's gone. My phone feels icky right now... I thought maybe the Verizon update would help clean it up!
I am all ears
HI and welcome to XDA!
pragakhan said:
So there are posts about the Verizon update. Install or don't?
Click to expand...
Click to collapse
I would not suggest using the VZW update. Go with DCD ROM 3.2.6.
pragakhan said:
There are posts about AGPS - Why is this important? I thought phones with true GPS didn't need aGPS?
Click to expand...
Click to collapse
It is important so you'll have a GPS lock within seconds instead of minutes.
pragakhan said:
There are posts about PRI's - I have no clue what that is even about!
Click to expand...
Click to collapse
The VZW update installs a new PRI that seems to help lock down GPS so other 3rd party programs do not work unless you pay the $10/mo VZNav access.
pragakhan said:
And another post telling people to shut up..
I am so confused right now I have no clue what to do any more! LOL
Click to expand...
Click to collapse
Just ignore the hostile posts. They are counter productive.
pragakhan said:
Update to VZ's MR1? Or am I holding on for something better?
Do I use GPS? Ehh.. Id'e like to use GPSTracker, so far it's not working very well with out GPSGate installed. And I like to have Tomtom installed as a backup. It works OK.. Very slow to lock on though.
However, with my desire to keep GPS intact, my S2U2 has stopped working, so I uninstalled it. ThrottleLauncher started breaking (even though nothing changed) so that's gone. My phone feels icky right now... I thought maybe the Verizon update would help clean it up!
I am all ears
Click to expand...
Click to collapse
What are you currently running? I suggest looking into DCD 3.2.6 or investigating what you might have installed causing the problem. Sometimes starting from scratch by doing a hard reset is just easier to clear out any changes one might have made.
tbhall77 said:
HI and welcome to XDA!
I would not suggest using the VZW update. Go with DCD ROM 3.2.6.
Click to expand...
Click to collapse
Thanks!
tbhall77 said:
It is important so you'll have a GPS lock within seconds instead of minutes.
Click to expand...
Click to collapse
Ok, that makes sense!
tbhall77 said:
The VZW update installs a new PRI that seems to help lock down GPS so other 3rd party programs do not work unless you pay the $10/mo VZNav access.
Click to expand...
Click to collapse
Not going to do that then LOL
tbhall77 said:
Just ignore the hostile posts. They are counter productive.
What are you currently running? I suggest looking into DCD 3.2.6 or investigating what you might have installed causing the problem. Sometimes starting from scratch by doing a hard reset is just easier to clear out any changes one might have made.
Click to expand...
Click to collapse
Running DCD 3.2.5 right now. Is there a problem with .5?
So say I move to .6
Would it benefit me to use the newer Radio VZ has provided us?
Then work on getting aGPS working
Then move along from there?
I am not good with getting the roms installed via flash card, so I am stuck using USB, if that option exists.. Will going from .5 to .6 erase everything? Do I need to use the spl program first when ever I do an update like this?
I think those questions will help, the other answers already help as I now have no intention of using the verizon update
pragakhan said:
Running DCD 3.2.5 right now. Is there a problem with .5?
So say I move to .6
Would it benefit me to use the newer Radio VZ has provided us?
Then work on getting aGPS working
Then move along from there?
I am not good with getting the roms installed via flash card, so I am stuck using USB, if that option exists.. Will going from .5 to .6 erase everything? Do I need to use the spl program first when ever I do an update like this?
I think those questions will help, the other answers already help as I now have no intention of using the verizon update
Click to expand...
Click to collapse
You can stick with 3.2.5 if it works for you. When DCD releases a new ROM I usually wait 1-2 days to see if there are any reported issues and then I upgrade to his latest. Upgrading the ROM does erase all the data from your phone. i.e. saved txt messages, call history, contacts, etc. So, you'll want to back that info up. I personally use a utility called "PPC Backup Contacts" to backup my contacts and I don't care about the rest. Verizon's radio rom isn't the latest version as far as version numbers go. I haven't had any issues with the latest radio, so, I'd suggest you you just use it. For SPL, once you have it on there you don't need to mess with it unless a new version comes along.
Flashing... I've never been successful flashing the radio rom via USB unless it was built into an official package like VZW or Sprints office rom. I've flashed most of my radios via the minisd method. I kind of cheat by using my phone as the minisd reader. I hook my phone up to my computer and let activesync go. From there, my phone shows up inside Windows Explorer and I just copy the new ROM to the minisd. For flashing the actual rom, I've always stuck with DCD's precooked rom that has the installer built in and works over USB.
Hello, Im about to upgrade my x10a to 2.3 using the flashtool. And i was wondering if everything works correctly and if it works with the x10a U.S.
Thanks A lot
Yes it does. It is working for me.
But I saw a post that someone in New York area is having difficulty to get the radio working.
hasei said:
Yes it does. It is working for me.
But I saw a post that someone in New York area is having difficulty to get the radio working.
Click to expand...
Click to collapse
Thanks, and what do you mean radio? Like the fm/am radio, because if its that,then im gonoing to that since i wont be using that.
no... it means gettign the signal!
reboot while getting signal found to be a little common happened to x10a user
me included
oh alright. Does it happen to you? or does it happen to everyone?
Don't worry, you can always go back to where you were if it doesn't work out, which I doubt will occur.
thanks a lot. I will be doing this soon. this is the official update? and is everything else working smoothly, example: the transition between pages and the touch?
Yes this is the official update. You would be the only judge to make sure everything works smoothly.
I'm glad that I upgraded!
Yeah, I did it and everything seems to work correctly. Now im going to root it. I just need find a way.
As far as I know conventional ways to root don't work.
http://forum.xda-developers.com/showthread.php?t=1196421
You may want to take a look at it. Or flash prerooted one like I did.
Does your phone customization version has the update released? If yes, update it through SEUS or PC Companion. FlashTool is just used for backup, I will not recommend to use it to upgrade OS.
Brunop10 said:
Yeah, I did it and everything seems to work correctly. Now im going to root it. I just need find a way.
Click to expand...
Click to collapse
I've found a better thread that shows how to root the official 2.3.
http://forum.xda-developers.com/showthread.php?t=1196808
I have flashed to 2.33 and my biggest complaint is that the phone reboots after using google navigation after about 10 minutes, and poor bt profiles, making my older se stereo headset unrecognised.
Sent from my X10i using XDA Premium App
i have a problem and i seem to be the only one with this problems its so strange. no matter what rom i flash or who its made by if its 4.3 or 4.4 i get the same problems. when i try to make a phone call i cant hear a thing no dial tone nothing UNLESS the phone is on speaker phone then i hear normal but if i switch back to normal phone its silent again. the second problem is when i use speech to text in a text, when i hit the mic symbol the phone reboots itself, sometimes i have to hit the mic then keyboard then mic but eventually it will always reboot its self. any help will be greatly appreciated.
You have done a full wipe, correct?
What radio are you using?
Have you had this problem ever since you first rooted our did this issue develop later?
Sent from my LG Optimus G using XDA Premium 4 mobile app
What Radio are you using? What Carrier?
I've used the ATT Hybrid radio on ATT for the longest time, and I haven't had any of the issues you describe.
DraginMagik said:
You have done a full wipe, correct?
What radio are you using?
Have you had this problem ever since you first rooted our did this issue develop later?
Sent from my LG Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes ive done a full wipe everytime im using stock jellybean modem i got from houstonn i believe and i never had this problem before ive had the phone over a year rooted since day one and never had this problem until i tried to install pcexpresses 4.4 and now every 4.4 and 4.3 rom i try to install has the same issues.
OMGMatrix said:
What Radio are you using? What Carrier?
I've used the ATT Hybrid radio on ATT for the longest time, and I haven't had any of the issues you describe.
Click to expand...
Click to collapse
can you give me a link to your radio so i can try it? and my carrier is simplemobile
dragonash86 said:
can you give me a link to your radio so i can try it? and my carrier is simplemobile
Click to expand...
Click to collapse
You'll want the third one from this link.
If that doesn't work, try the other one labeled "Hybrid" in that folder.
3622 23529369
The radio worked thank god but im still having the same problem with the MIC as soon as i push it the phone restarts.
dragonash86 said:
The radio worked thank god but im still having the same problem with the MIC as soon as i push it the phone restarts.
Click to expand...
Click to collapse
Have you tried the other hybrid radio from that link?
reply
Not yet but I don't think the radio is the problem cause when I install cyanogenmod it works perfectly fine with the hybrid modem where pcexpresses 4.4 the calling issue is fixed but not the reboot issue also I didn't notice this till yesterday but I lost root as well only with pcexpresses.
dragonash86 said:
Not yet but I don't think the radio is the problem cause when I install cyanogenmod it works perfectly fine with the hybrid modem where pcexpresses 4.4 the calling issue is fixed but not the reboot issue also I didn't notice this till yesterday but I lost root as well only with pcexpresses.
Click to expand...
Click to collapse
If you read the thread,you would have known that root is disabled by default in SlimKat.
You have to go in Developer Settings and allow root.
However, Slim's root implementation is kind of ****ty, so I always end up having to flash supersu when using that rom.
sdgf
yeah i noticed it says that at the begining i dont know how i missed that but its good to know how to fix that but that doesnt fix my rebooting problem. any ideas on that?
I had CodeFire on my DNA for about a month. All was running well. I just installed whatever was current around 2/23 and never installed a nightly update. Last week, I started having problems texting. I thought the ROM was going belly up on me. So I flashed SlimKat. I still cannot text without cycling Airplane Mode in between each. Alternatively, I can wait about an hour to sent a subsequent test message after a successful one.
I just re-flashed the latest radio hoping that would fix it. I'm at a loss. Do I need to call VZW and have them do something on their end?
mdphoenix said:
I had CodeFire on my DNA for about a month. All was running well. I just installed whatever was current around 2/23 and never installed a nightly update. Last week, I started having problems texting. I thought the ROM was going belly up on me. So I flashed SlimKat. I still cannot text without cycling Airplane Mode in between each. Alternatively, I can wait about an hour to sent a subsequent test message after a successful one.
I just re-flashed the latest radio hoping that would fix it. I'm at a loss. Do I need to call VZW and have them do something on their end?
Click to expand...
Click to collapse
Nothing? Just flashed another ROM. Phone is dead. Am I beating a dead horse with this question? Someone point me in the right direction then, please. Everything I've read states that the SMS issues are related to showing double texts. I can't find this exact problem.
My phone is useless to me now.
mdphoenix said:
Nothing? Just flashed another ROM. Phone is dead. Am I beating a dead horse with this question? Someone point me in the right direction then, please. Everything I've read states that the SMS issues are related to showing double texts. I can't find this exact problem.
My phone is useless to me now.
Click to expand...
Click to collapse
The kit kat roms are ported. There are several issues with them that cannot be "fixed" until the source code is released. If the phone does not respond to any commands including trying to boot.... leave it on a factory charger for 24 hours. Then try to work with it
mdphoenix said:
Nothing? Just flashed another ROM. Phone is dead. Am I beating a dead horse with this question? Someone point me in the right direction then, please. Everything I've read states that the SMS issues are related to showing double texts. I can't find this exact problem.
My phone is useless to me now.
Click to expand...
Click to collapse
What do you mean by "phone is dead"? Completely non responsive or no signal. I've been on cfx since I ported it over with no issues besides the random signal drop here and there. But that's maybe a few times per week and happens to me on all ROMs. What do you wipe when flashing a new ROM? Have you tried a RUU?
Sent from my HTC6435LVW using xda app-developers app
danjull said:
What do you mean by "phone is dead"? Completely non responsive or no signal. I've been on cfx since I ported it over with no issues besides the random signal drop here and there. But that's maybe a few times per week and happens to me on all ROMs. What do you wipe when flashing a new ROM? Have you tried a RUU?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Dead as in Roaming again. My apologies for the exaggeration. I'm a bit frustrated here. I cannot seem to win with this thing. I hated my Thunderbolt at the end, but at least it worked. RUU brings back mobile data and texting. I've tried CM 10.2 several times. Each time, it gets stuck in roaming. I cannot change the NV setting. Changing it, then checking it again and it's right back. I've tried flashing with the SIM in. With it out. I've cycled Airplane mode a few times. Rebooted. Installed GApps. Rebooted. Cycled Airplane mode. I'm missing something. Apparently.
I just want a phone without Sense or the Verizon crap. CFX was awesome until this texting issue.
mdphoenix said:
Dead as in Roaming again. My apologies for the exaggeration. I'm a bit frustrated here. I cannot seem to win with this thing. I hated my Thunderbolt at the end, but at least it worked. RUU brings back mobile data and texting. I've tried CM 10.2 several times. Each time, it gets stuck in roaming. I cannot change the NV setting. Changing it, then checking it again and it's right back. I've tried flashing with the SIM in. With it out. I've cycled Airplane mode a few times. Rebooted. Installed GApps. Rebooted. Cycled Airplane mode. I'm missing something. Apparently.
I just want a phone without Sense or the Verizon crap. CFX was awesome until this texting issue.
Click to expand...
Click to collapse
EDIT: Just installed the latest CFX and AGAIN I have the god blessed SMS issue. I can't sent sequential texts. I have to turn on Airplane mode after each one before sending the next.
mdphoenix said:
EDIT: Just installed the latest CFX and AGAIN I have the god blessed SMS issue. I can't sent sequential texts. I have to turn on Airplane mode after each one before sending the next.
Click to expand...
Click to collapse
omfg. I just installed a stock Odexed, Rooted 3.06.605.4. SMS works but now I'm stuck in 3G. Is there a ROM out there that works so I can use my phone for work and play or should I Just suck it up and put it back to a full stock OTA ROM?
mdphoenix said:
omfg. I just installed a stock Odexed, Rooted 3.06.605.4. SMS works but now I'm stuck in 3G. Is there a ROM out there that works so I can use my phone for work and play or should I Just suck it up and put it back to a full stock OTA ROM?
Click to expand...
Click to collapse
Have you considered hardware issues? If it was a ROM issue it wouldn't be a one person issue. Or provide a log of what's happening when you send SMS. You're just not giving us much to go by, except what's not working. Are you doing full wipes between flashing roms, or just cache or factory resets?
Sent from my HTC6435LVW using xda app-developers app
danjull said:
Have you considered hardware issues? If it was a ROM issue it wouldn't be a one person issue. Or provide a log of what's happening when you send SMS. You're just not giving us much to go by, except what's not working. Are you doing full wipes between flashing roms, or just cache or factory resets?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Full Wipes between flashes.
I've had this phone for about two months. I initially had issues flashing CM and being stuck in roaming. No CM ROM I attempt to flash will work. They always end up stuck in roaming. I think the problem is that I can't switch from NV. When I change it, it always goes right back. Not sure what's up there.
I just flashed ★ ☆ [ROM/RADIO][4.2.2] Stock 3.06.605.4 | Rooted | Odex-Deodex | Sense5 And now SMS works, but I'm stuck in 3G.
I hadn't considered hardware only because with each ROM, the previously broken feature works, but then something new pops up.
With one, I can text, but am in 3G. With another, I've got 4G but can't text without cycling Airplane mode.
I sincerely apologies for coming off as a d!ck. I've nothing to contribute to the community but my bug reports and money. It's frustrating to see how quickly some phones are abandoned, though.
I've always been thankful for everyone's help and tried to offer bug reports and donations where applicable.
I just want my phone to work, with a plain vanilla OS and tethering. I don't need Sense. I don't need fancy mods. Just a phone that works.
Please accept my apology, and thanks again for the help.
mdphoenix said:
Full Wipes between flashes.
I've had this phone for about two months. I initially had issues flashing CM and being stuck in roaming. No CM ROM I attempt to flash will work. They always end up stuck in roaming. I think the problem is that I can't switch from NV. When I change it, it always goes right back. Not sure what's up there.
I just flashed ★ ☆ [ROM/RADIO][4.2.2] Stock 3.06.605.4 | Rooted | Odex-Deodex | Sense5 And now SMS works, but I'm stuck in 3G.
I hadn't considered hardware only because with each ROM, the previously broken feature works, but then something new pops up.
With one, I can text, but am in 3G. With another, I've got 4G but can't text without cycling Airplane mode.
I sincerely apologies for coming off as a d!ck. I've nothing to contribute to the community but my bug reports and money. It's frustrating to see how quickly some phones are abandoned, though.
I've always been thankful for everyone's help and tried to offer bug reports and donations where applicable.
I just want my phone to work, with a plain vanilla OS and tethering. I don't need Sense. I don't need fancy mods. Just a phone that works.
Please accept my apology, and thanks again for the help.
Click to expand...
Click to collapse
Verizon is sending me another phone. Stay tuned.
mdphoenix said:
Verizon is sending me another phone. Stay tuned.
Click to expand...
Click to collapse
Have you considered the fact that the recovery itself is causing your issues? I would give TWRP a try to see if there are differences. TWRP is a must to flash KitKat roms and the version used is critical.
RLGL said:
Have you considered the fact that the recovery itself is causing your issues? I would give TWRP a try to see if there are differences. TWRP is a must to flash KitKat roms and the version used is critical.
Click to expand...
Click to collapse
Nope. I didn't consider that. Because most of my problems were with CM 10.2.1. Which is JB, correct?
That being said, I've tried both CW and TWRP to no avail. After being stuck in 3G for two days across multiple ROMs, I'm convinced the hardware went belly-up.
New SIM?
HTC DNA
LG Optimus G
mdphoenix said:
Nope. I didn't consider that. Because most of my problems were with CM 10.2.1. Which is JB, correct?
That being said, I've tried both CW and TWRP to no avail. After being stuck in 3G for two days across multiple ROMs, I'm convinced the hardware went belly-up.
Click to expand...
Click to collapse
Santod has a process to recover the unit from the conditions you describe. It is fairly simple and doesn't appear to require much time.
I don't have time to search for it at the moment.
RLGL said:
Santod has a process to recover the unit from the conditions you describe. It is fairly simple and doesn't appear to require much time.
I don't have time to search for it at the moment.
Click to expand...
Click to collapse
I did lots of searching before asking. I try to do my due diligence before bothering you all.
The replacement phone did not resolve the problem. The replacement SIM did.
Now on to bigger and better things. Thanks for putting up with me.
And now I can't text without cycling Airplane mode again.
Sent from my HTC6435LVW using Tapatalk
RLGL said:
Santod has a process to recover the unit from the conditions you describe. It is fairly simple and doesn't appear to require much time.
I don't have time to search for it at the moment.
Click to expand...
Click to collapse
Are you certain it was Santod? He's only got 19 posts on this board and I don't see anything directly related to the SMS problem I'm having.
mdphoenix said:
Are you certain it was Santod? He's only got 19 posts on this board and I don't see anything directly related to the SMS problem I'm having.
Click to expand...
Click to collapse
Yes it is on This page
RLGL said:
Yes it is on This page
Click to expand...
Click to collapse
Since my last update, I've received a new DNA, and a new SIM card.
Check out the last few posts here: http://forum.xda-developers.com/showthread.php?p=51465109
This is bizarre. Either I'm doing something wrong, or... I don't know. SMS works on a stock ROM but not on a custom ROM, with a new phone, with a new SIM.
I think you are doing something wrong.
RUU the latest firmware, factory reset, wipe data, cache, and system, install a ROM and DO NOT restore anything.
I think youre not completely wiping and/or are restoring things.