At this point, I have to consider I have a hardware issue.
I am S-off and i have been on every RUU from Gingerbread to latest OTA ICS. I have tried MANY kernels with updated or modified radios and have the same problem through and through:
My bluetooth will not turn on and my wifi (depending on the ROM and or Firmware) will either stay on and intermittently say its scanning for networks or will toggle quickly back and forth from on to off by itself or get stuck at "turning on".
I have had no luck with BT or WIFI. I have spent hours searching forums for anyone in this same predicament and everyone else seems to get relief from updating Kernels or firmware, etc.
I was on CleanROM for the longest time with no issues (S-on at that time). Then the latest RUU came out and I flashed to VipreRez, since then, no wifi. Downgraded back to 3.xxx and back to CleanROM with no luck. I've tried updating kernels and manually pushing WIFI module files. Currently S-off to see if that was my issue but even going to the original GB RUU (1.xxx) and upgrading, I never had wifi or BT.
Im starting to think this is now a hardware issue. However, the wifi BT problem only happened after I upgraded to latest OTA.
I've been following directions on every flash for every rom, kernel, RUU, etc to no avail. Not a single one of them has allowed me to get wifi BT back.
Can anyone out there in their infinite wisdom give me a suggestion or perhaps something I'm over looking? THANK YOU SO MUCH
U aren't missing any of the contacts that make connection with the battery cover are you ?
Also, when you wipe before flashing are you making sure you flash boot ?
Sent from my Nexus 7 using Tapatalk 2
dottat said:
U aren't missing any of the contacts that make connection with the battery cover are you ?
Also, when you wipe before flashing are you making sure you flash boot ?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for replying. I'm S-off now so I didn't think it would be necessary to manually flash the boot.img. However, when I was S-on and first started having the problem, I would always flash the boot manually to no avail.
Also, I checked the backplate and everything is fine there. I've even gone as far as to place the phone directly on the wifi router to make sure it wasnt an issue with that. When the wifi starts glitching out and sliding itself off and on, it makes me think i can rule out backplate connections.
update
Update:
just flashed Rezound.Cubed.ICS.Kernel.1.0.7.Sense4 after wiping cache and delvik and WIFI now says "error". *shrug*
That typically happens when your WiFi libs don't match your kernel. S-off or not did you actually wipe boot and system before flashing? You symptoms sound very indicative of a dirty flash as you are ending up with mismatched components.
Sent from my Nexus 7 using Tapatalk 2
dottat said:
That typically happens when your WiFi libs don't match your kernel. S-off or not did you actually wipe boot and system before flashing? You symptoms sound very indicative of a dirty flash as you are ending up with mismatched components.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
just went into recovery and wiped dalvik/cache/boot. Flashed kernel. wifi stuck on "turning on".
Thanks for your thoughts and ideas to help fix
Wipe system/boot/data/cache and reflash viper again. Tell me if your WiFi works after that.
Sent from my Nexus 7 using Tapatalk 2
dottat said:
Wipe system/boot/data/cache and reflash viper again. Tell me if your WiFi works after that.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
just did that and am stuck in boot loop... standby...
dottat said:
Wipe system/boot/data/cache and reflash viper again. Tell me if your WiFi works after that.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
was stuck in boot loop hell last night. Coudlnt even get out of it by flashing 3.14 RUU. Had to use the RUU for 1.xxx gingerbread. When that finally came back up - still no wifi. Kept getting error message: "Settings has stopped working". No wifi still, no BT.
Left my phone on gingerbread last night, it OTA'd ICS and still, no wifi, no BT, same error. I'm beyond baffled. *shrug*
MicahJamesNRCAL said:
was stuck in boot loop hell last night. Coudlnt even get out of it by flashing 3.14 RUU. Had to use the RUU for 1.xxx gingerbread. When that finally came back up - still no wifi. Kept getting error message: "Settings has stopped working". No wifi still, no BT.
Left my phone on gingerbread last night, it OTA'd ICS and still, no wifi, no BT, same error. I'm beyond baffled. *shrug*
Click to expand...
Click to collapse
If you're completely wiping your phone and installing the current OTA RUU and your wifi still errors, exchange it for a new phone.
A RUU should have fixed all your problems all together. Sounds like a hardware issue. Call Verizon, replacement should be sent within a 5 minute phone call.
HTC Rezound
luis86dr said:
A RUU should have fixed all your problems all together. Sounds like a hardware issue. Call Verizon, replacement should be sent within a 5 minute phone call.
HTC Rezound
Click to expand...
Click to collapse
wont they know that im s-off and modded ? ive never had to call verizon for an RMA issue. im not even sure if im within a warranty period
No they won't. They asked me a series of questions. (Did I factory reset, blah blah blah...) Told them I did, in which he then decided to ship me a replacement. Once I got replacement in mail, then I restored my Rezound to S-On and Locked. Simple as that.
HTC Rezound
What firmware is this phone on?
Sent from my Nexus 7 using Tapatalk 2
on latest OTA. should i bring it to my local Verizon store or call only?
thanks guys. looks like on my receipt i bought the phone on 9/18/2011
luis86dr said:
No they won't. They asked me a series of questions. (Did I factory reset, blah blah blah...) Told them I did, in which he then decided to ship me a replacement. Once I got replacement in mail, then I restored my Rezound to S-On and Locked. Simple as that.
HTC Rezound
Click to expand...
Click to collapse
dottat said:
What firmware is this phone on?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Just got off the phone with Verizon - theyre sending me a replacement Rezound refurbished.
Sadly, I think the hardware is nuked on this. Thanks for everyone's help
MicahJamesNRCAL said:
Just got off the phone with Verizon - theyre sending me a replacement Rezound refurbished.
Sadly, I think the hardware is nuked on this. Thanks for everyone's help
Click to expand...
Click to collapse
Make sure you check it fully once received. Verizon is know to send you devices with problems.
HTC Rezound
luis86dr said:
Make sure you check it fully once received. Verizon is know to send you devices with problems.
HTC Rezound
Click to expand...
Click to collapse
will do, thanks
luis86dr said:
Make sure you check it fully once received. Verizon is know to send you devices with problems.
HTC Rezound
Click to expand...
Click to collapse
hey so, do i just need to relock the Bootloader and S-on?
im paranoid they are going to tell me this is something I did.
I did. It's honestly up to you.
HTC Rezound
Related
So, long story short, took the Phone into Sprint so they could look at my headphone jack (was cracked and left ear bud would constantly cut in and out) because its acting up.
Gave the Tech the phone without the battery in it (since he didn’t need to power up the device to clearly see the headphone jack has a huge crack in it) but I left my SD card installed. As he was walking away, I asked him if I could remove my SD card and he let me, then seen that I gave him the phone without a battery. So, I ended up giving it to him (praying he didn’t turn it on and see ViperBoys sick ass ROM booting up) and he accidently pressed the power button turning the phone on. Promptly short after, he removed the battery when the phone was on the HTC screen, didn’t even get the boot animation. I was like OHH $h!t, that gonna mess up my phone & sure as $h!t, it did… Just loops in and out of that screen resetting each time with a little vibrate then looping.
I can get into Fastboot and use ADB, I’ve flashed RUU’s, put Stock image on root of SD and let recovery restore (losing my CWM & my HBOOT 1.400), unlocked, relocked, wiped, thrown, and screamed at it with no luck.
I did do a CWM backup before even setting foot in the Store, so I do have a backup. The 1st thing I tried was restoring it through CWM recovery and that didn’t stop the looping. I can still get into fastboot via power + vol down and adb functionality is still there.
HBOOT is 1.50 and s-on is enabled..
Been reading through threads since lunch and tried many different solutions without success. It seems once a phone is this far gone, people stop responding.
Anyone have any ideas?
New phone will be here tomorrow (free of coarse courtesy of Sprint insurance) but I’ve been without a phone all day and most of yesterday. I’d like to get this one back to stock and booting before I trade it in for the replacement tomorrow
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
yousefak said:
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
Click to expand...
Click to collapse
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
lessegr said:
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
Click to expand...
Click to collapse
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
yousefak said:
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
Click to expand...
Click to collapse
BUMMER! In case the question comes up I ran "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed" and it ran just fine.
Hmm, hardware issue. Dont see how I can check for that if it doesnt boot.
Guess I'll just have to wait for the new Phone
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
jdeoxys said:
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Click to expand...
Click to collapse
The HTC unlock went as expected. Followed the directions to the "T", then relocked, checked in fastboot (not that I could check anywhere else, LOL) and the phone says "*** RELOCKED***". Ran 2.17.651.5 RUU successfully to the finish. Still looping
WEIRD!
DarkManX4lf said:
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
Click to expand...
Click to collapse
Because I just want to know WTF happened!!! Had this Phone since release, abused\used the hell out of it by flashing ROMs constantly, restoring backups, tethering like crazy, emailing, texting, FBing...
No reason for it to crap out on me from a simple mistake, not even of my responsibility, lol!
The only issue I've had with this Phone is that damn headphone jack 1/2 way failing..
Got new phone, terrified to even think about trying to flash new ROM though
lessegr said:
Got new phone, terrified to even think about trying to flash new ROM though
Click to expand...
Click to collapse
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Threevo said:
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
DONT TEMPT ME DAMMIT! lol! Just been without a phone for almost 3 days. I'm also seeing a lot of new threads about people experiencing what I've gone through.
Woops, sprint\HTC! once again rooted, and running viperROM.... SWWWWWET!
HBOOT 1.5 and s-on is a *****!
Not to mention... But in Linux, I never got revo recovery to flash... You can do it in windows just do it via fastboot.
Took my Orig cwm bsckup "recovery" & "boot" .img and threw them @ the phone via command prompt.
After cwm was restored, I restored my 4\29\2012 backup that I made before I entered the Sprint store, now my phone is back to the exact same way
It was. Pretty Damn sweet!
So much info here!! I'm truly thankful!!!
Sent from my PG86100 using xda premium
I don't know what happened. All of a sudden, my phone's WiFi functionality is totally shot.
No access points are detected, and when I try to switch WiFi on and off again, the phone locks up and reboots.
The last time I had flashed something was a week ago. I haven't even downloaded any new apps recently.
I was on jokersax's CM9 0.6.9.2 and 1.0 GHz kernel. After wiping data/cache, re-flashing joker's CM9, upgrading joker's CM9 to 0.6.9.3, and switching to faux's latest 1.0 GHz kernel, the problem persists.
Could I possibly have fried the WiFi chip on this thing somehow? It sounds crazy, but there were virtually no software changes made to the device prior to the incident.
Have you a nandroid backup of a rom with working wifi? I had same problem several times and restoring a backup with it working has always fixed mine.
Sent from my MB860 using XDA
I had the same. Mine just kept getting worse, until the phone kept rebooting at every phone call, and eventually every few minutes. Called warranty, and the said it is well documented problem and replaced both of my atrix phones. They said it was a hardware issue.
chrism.brunner said:
I had the same. Mine just kept getting worse, until the phone kept rebooting at every phone call, and eventually every few minutes. Called warranty, and the said it is well documented problem and replaced both of my atrix phones. They said it was a hardware issue.
Click to expand...
Click to collapse
That's unfortunate. Well, at least I know I'm not an isolated case.
So after charging overnight, WiFi worked for like 5 minutes, then proceeded to cut out again and continually reboot the phone until I turned off WiFi.
I would just send it to Moto, but of course their refurb/replacement units are bootloader locked... I doubt they'll even replace an unlocked device.
Looks like I'm screwed.
JPBeard21 said:
Have you a nandroid backup of a rom with working wifi? I had same problem several times and restoring a backup with it working has always fixed mine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I mean, the problem just started randomly; I was running that version of CM9 for a week already, so I doubt the ROM is the issue. I suppose I can try, though (if I even have a recent nandroid backup...heh)
Mine was unlocked and rooted. Just flash the latest sbf, and send it in. That returns it to locked stock.
chrism.brunner said:
Mine was unlocked and rooted. Just flash the latest sbf, and send it in. That returns it to locked stock.
Click to expand...
Click to collapse
He's saying he doesn't want to get a replacement back that has a locked un-unlockable bootloader. That's been happening lately.
stewartsoda said:
He's saying he doesn't want to get a replacement back that has a locked un-unlockable bootloader. That's been happening lately.
Click to expand...
Click to collapse
Yeah, that's the main reason.
So it seems Wi-Fi isn't 100% toasted. After a few cycles of toggle on, toggle off, toggle on, toggle off, lockup and reboot, toggle off, toggle on, lockup and reboot, toggle on, etc., I can end up connecting to Wi-Fi. It works, but then locks up and reboots after some amount of time (5-10 minutes usually) and then it doesn't connect anymore.
I don't know how, but maybe this could be a software issue? Could some system file that governs Wi-Fi have gotten corrupted somehow by some random process? Is there some system file I should check? Maybe flash a radio? I don't know.
All I know is that I'm gonna easily blow through my 2GB cap if I don't remedy this somehow.
(EDIT: My Smart Keyboard Pro settings got randomly wiped about the same time this started happening, but I have no idea how that could relate...)
EDIT2: Well, never mind, I found the thread in the Dev forum that has a bunch of people talking about this issue. Case closed, I guess, to some extent.
I unlocked the bootloader of the new phone. So, seems to me it is the way to go. Let them send you the new phone. Had to combine a few of the unlock methods, but everything is fine.
stewartsoda said:
He's saying he doesn't want to get a replacement back that has a locked un-unlockable bootloader. That's been happening lately.
Click to expand...
Click to collapse
I just unlocked a warranty replacement atrix with the newest att firmware... What are you talking about...
Sent from my MB860 using Tapatalk 2
hoodlikegaza said:
I just unlocked a warranty replacement atrix with the newest att firmware... What are you talking about...
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Well, since you are not everybody....
SBF/Bootloader Unlocking Blocked on New Atrix (forum.xda-developers.com)
Perhaps you got lucky when you got your phone back.
stewartsoda said:
Well, since you are not everybody....
SBF/Bootloader Unlocking Blocked on New Atrix (forum.xda-developers.com)
Perhaps you got lucky when you got your phone back.
Click to expand...
Click to collapse
That makes two of us then. Its still worth a try, because you can't hardly use the phone the way it is. At least with warranty you get a new one. If you are worried about bricking it leave it alone. At least it is useable.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
stewartsoda said:
Well, since you are not everybody....
SBF/Bootloader Unlocking Blocked on New Atrix (forum.xda-developers.com)
Perhaps you got lucky when you got your phone back.
Click to expand...
Click to collapse
Classic user error. The solution is right there in the very thread you posted...
Non-issue ftw.
Sent from my MB860 using Tapatalk 2
hoodlikegaza said:
Classic user error. The solution is right there in the very thread you posted...
Non-issue ftw.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Very well, I stand corrected. I read the posts when they were first posted but didn't follow them to the point that there was a resolution.
My DNA has just started popping up the message "com.android.phone has stopped" and crashing the dialer every time I try to make a call. It worked fine for the first couple weeks I had it, and still works fine apart from making calls. 4G works and I get data. I've tried re-inserting the SIM, doing a factory reset, flashing RUU, and I just got back from the Verizon store where the swapped out the SIM. Nothing has fixed it.
Before I call the VZ warranty department I thought I'd post here and see if anyone had an idea. I'm a little worried they'll see my "Relocked/Tampered" bootloader and tell me I'm SOL. :/
Hmm...that didn't work I think there's a tread about this issues somewhere around here
sent from my beastly powered viper DNA using Tapatalk 2
holla420 said:
Hmm...that didn't work I think there's a tread about this issues somewhere around here
sent from my beastly powered viper DNA using Tapatalk 2
Click to expand...
Click to collapse
Hmm, I didn't find anything in my (admittedly brief) search. Either way, I gave up and called Verizon warranty service. The rep was very helpful and agreed to send me a new phone.
neo_1221 said:
Hmm, I didn't find anything in my (admittedly brief) search. Either way, I gave up and called Verizon warranty service. The rep was very helpful and agreed to send me a new phone.
Click to expand...
Click to collapse
Wow, it would never be that easy to get a replacement in Australia
uppon2 said:
Wow, it would never be that easy to get a replacement in Australia
Click to expand...
Click to collapse
Just to be clear, my "new" phone is actually "recertified like-new". And I have to send the old one back or pay full price for it. And if they find evidence of damage or tampering on the old phone I'll get charged $300. But yeah, aside from that it was pretty easy.
Guys, i am having the same problem! On every call i get com.android.phone has stopped ! Does anyone had the same and found a solution?!
I tried 3 custom roms(viper hatka and another one) no work, reflashed back to stock, problem remains!
I am also living overseas! Is this a problem?
Just out of curiosity, do you still have the little flap covering your microUSB port? I got annoyed with mine and yanked it out...now I'm wondering if it damaged the antenna.
I have removed it too, no way this thing can affect the operation!
It has to do with someone on you facebook or contacts has a birthday on Feb 29 find out which one it is delete the contact sync for that person or change the birthday
Thanks for the reply, have you experienced the same problem in htc DNA?
The solution you are giving is kinda strange, as i haven't passed any contacts or fb account to my mobile and the problem persists. Of course, i had done this one in the past, lets check what you just said, thanks!
ergotelis said:
Thanks for the reply, have you experienced the same problem in htc DNA?
The solution you are giving is kinda strange, as i haven't passed any contacts or fb account to my mobile and the problem persists. Of course, i had done this one in the past, lets check what you just said, thanks!
Click to expand...
Click to collapse
sorry wrong on the one I thought it was is http://forum.xda-developers.com/showthread.php?t=2076784
android.phone.acore .. again I am sorry
I also am having this problem.
I completely wiped everything and stuff as well.
Any solutions?
any resolutions?
has anyone been able to resolve this? after S-OFF, i'd hoped that flashing the new radio may work, but it didn't. i've formatted every partition and then resintalled every rom i can think of, to no avail. sucks!!
I had stock rom, unlocked, rooted, flashed viper and had the problem. Flashed different roms, the same. Returned to stock RUU, the same. Reflashed, the same. Unlocked, rooted again, and flashed viper again, and voila, the problem solved!:laugh:
ergotelis said:
I had stock rom, unlocked, rooted, flashed viper and had the problem. Flashed different roms, the same. Returned to stock RUU, the same. Reflashed, the same. Unlocked, rooted again, and flashed viper again, and voila, the problem solved!:laugh:
Click to expand...
Click to collapse
I tried this hoping it would fix com.android.phone, no luck
If RUUing doesnt help it then it might be a hardware related issue and its getting that error because the software can not communicate with the hardware... possibly? maybe? just an idea
.torrented said:
If RUUing doesnt help it then it might be a hardware related issue and its getting that error because the software can not communicate with the hardware... possibly? maybe? just an idea
Click to expand...
Click to collapse
It's not like I'm not getting a signal, I still receive txt sms. The signal cuts as soon as I try using dialer.
ergotelis said:
I had stock rom, unlocked, rooted, flashed viper and had the problem. Flashed different roms, the same. Returned to stock RUU, the same. Reflashed, the same. Unlocked, rooted again, and flashed viper again, and voila, the problem solved!:laugh:
Click to expand...
Click to collapse
I tried following what you mentioned flashed ruu and then flashed back to viper rom. So can you please tell me what I'm doing wrong?
thanks
Have you checked md5 files for your files to be sure that you have the right ones?What recovery are you using? Are you locking-unlocking etc as you have to on every step?Try it once more but be sure for all these! I personally used cwm recovery!
ergotelis said:
Have you checked md5 files for your files to be sure that you have the right ones?What recovery are you using? Are you locking-unlocking etc as you have to on every step?Try it once more but be sure for all these! I personally used cwm recovery!
Click to expand...
Click to collapse
I am using cwm and followed step-by-step. I think it maybe a hardware issue or partitions are corrupt
My phone is rooted and S-ON and whenever it goes into sleep mode, I am unable to wake the device (it'll sometimes show the flashing green light if there's a notification waiting) and have to Soft-Reset (simulating battery pull) to get it to become responsive again. Do I need to go back to stock and re-root or is there something else that may resolve the issue?
What ROM are you on?
Sent from my HTC EVO 4G LTE
What Rom are you running?
^^^
I am still on stock build with latest software.
I would do a full wipe in TWRP (Dalvik, cache, data & system), flash a ROM and go from there to see if that resolves the issue.
Sent from my HTC EVO 4G LTE
FinZ28 said:
I would do a full wipe in TWRP (Dalvik, cache, data & system), flash a ROM and go from there to see if that resolves the issue.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I gave this a try... wiped it, installed a ROM (meanbean) and discovered the problem persists. I am using a warranty replaced device from Asurion btw (got it last week). Any other thoughts on this? I'm feel like ill need to RUU it and get another replacement.
Hybrid0NE said:
I gave this a try... wiped it, installed a ROM (meanbean) and discovered the problem persists. I am using a warranty replaced device from Asurion btw (got it last week). Any other thoughts on this? I'm feel like ill need to RUU it and get another replacement.
Click to expand...
Click to collapse
That might be your best bet. Did you have issues with the phone prior to rooting it? If so, then it sounds like you have a hardware issue. I would RUU and see if the problem persists and, if so, get another replacement.
Sent from my HTC EVO 4G LTE
FinZ28 said:
That might be your best bet. Did you have issues with the phone prior to rooting it? If so, then it sounds like you have a hardware issue. I would RUU and see if the problem persists and, if so, get another replacement.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I rooted my replacement the same day, didn't notice anything odd during that timeframe.
I've noticed that since I activated my replacement phone, the old device no longer appears to have this issue. Is it possible that the SIM card or some other element/component that works while the device is in an active state was triggering the issue?
right in the middle of a call my phone cut off and since then i have not been able to make any calls or send texts, my signal bars show a X
i was on insertcoin but have since done the original RUU back to stock 1.15 but no change
i have never flashed the modem other than through the RUU, no ENG hboot or anyhting
my phone is s-off but like i mentioned this happened after being in a call for a minute
happen to anyone else? any clues? thanks in advance!
hyphydragon said:
right in the middle of a call my phone cut off and since then i have not been able to make any calls or send texts, my signal bars show a X
i was on insertcoin but have since done the original RUU back to stock 1.15 but no change
i have never flashed the modem other than through the RUU, no ENG hboot or anyhting
my phone is s-off but like i mentioned this happened after being in a call for a minute
happen to anyone else? any clues? thanks in advance!
Click to expand...
Click to collapse
Re-seat your simcard, might help
Yeah or you fried your SIM card. You could also go into settings > mobile network, and make sure your phone is looking for a CDMA/LTE network instead of GSM or WCDMA or whatever.
Sent from my HTC6435LVW using Tapatalk
thank you for the replies, i tried everything and nothing works, i emailed htc and got no response, so im sending a second email, next step is the trash can, i already got a S5 and i hate it! except the battery life is ungodly amazing, cannot kill it in a day no matter what i do
hyphydragon said:
thank you for the replies, i tried everything and nothing works, i emailed htc and got no response, so im sending a second email, next step is the trash can, i already got a S5 and i hate it! except the battery life is ungodly amazing, cannot kill it in a day no matter what i do
Click to expand...
Click to collapse
Try using their I've chat or calling them. They will usually request you send it in for repair. If your not under warranty they will charge you.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
so just an update in case anyone else ever has this problem, dont give up!
although i had flashed the original RUU many time in attempts to fix my dna's dead radio it had not worked but this time for some reason it did.
the steps i took were.
1, leave the dna in the closet for 2 months
2, get mad and hit it on the table
3, flash the original hboot and RUU from torrented's post
hope no one else has this problem
hyphydragon said:
so just an update in case anyone else ever has this problem, dont give up!
although i had flashed the original RUU many time in attempts to fix my dna's dead radio it had not worked but this time for some reason it did.
the steps i took were.
1, leave the dna in the closet for 2 months
2, get mad and hit it on the table
3, flash the original hboot and RUU from torrented's post
hope no one else has this problem
Click to expand...
Click to collapse
It's mandatory to do a Factory Reset from stock recovery after RUU
I thought I was in the trash can once too, turned out to be the "Mobile network settings".