Related
Ok, I've tried my best to figure this out on my own and now I need some help.
Had my CDMA Hero flashed to Cricket a few weeks ago on talk and text. Just found out that I can get Sprint service, so I want to activate on Sprint instead of Cricket.
Here's what I've tried so far...
1. Latest RUU (1.56) installed successfully. Data in ##3282# seems to have stayed the same.
2. Manually changed my MSID and MDN to the correct Sprint settings given to me by tech support. Still won't activate or Update Profile.
3. Executed ##786#. Still won't activate or Update.
4. Reset User Name in ##3282# and committed. Still won't activate.
5. Called and double checked that my ESN is free and clear. It is. Tried all above procedures, still no luck.
6. Wiped Dalvik, and caches through Recovery 1.5.2. Also wiped phone through the white screen boot up procedure with the volume key. Still no luck.
From what I've been told by tech support, if none of these things gets my phone to activate on Sprint, then I need to get my phone flashed back to Sprint since it's currently flashed to Cricket.
Can anyone give me any advice? Is anyone else on Sprint, maybe even in the Eastern NC area, who wouldn't mind giving me some edittable settings from ##3282# or other things to check?
Getting a little frustrated but not giving up yet. I can't afford or have the time to wait until I can afford to take this phone somewhere and get someone else to do it for me. If anyone can help me out, I'll be happy to write a fully detailed guide on this whole thing for anyone else who has this problem in the future!!
Another bit of info. I just tried flashing the RUU again, since my phone wouldn't even boot on the last ##786# I tried. To get it ready to use RUU again, I loaded my Fresh 1.1 nandroid, ran rhe RUU again, and now there's a change.
My passwords for ##3282#, etc. are no longer "000000", and they're back to the default "190320". Does this mean that I'm no longer unlocked? Am I making progress now?
Grr.
LMAO man... I was in the same position as you ... but I was in Metropcs...so first of all to flash it to metropcs I went to a store called WirelessToyz and they did it for me, I got tired of metropc's slowness and I wanted to go to Sprint, so I had a hard time doing it until I went back to WirelessToyz and they flashed it back to sprint, even tough you flash the RUU that does not make it run on Sprint , when they "flash it" they do something else, long story short go to wherever you did that and flash it back to sprint, you might need to pay money.
To make a long story short, I recently purchased a used HTC Hero (sprint). After purchasing I played with the phone for a day or two to see what it can do (my first android phone, after being a Windows phone user) and in the process noticed that my esn was correct but my meid was all zeroes.
Now to skip thru all of the unnecessary stuff, I've been trying to change the meid back to what it should be, the number shown on the sticker below the battery. I've read every guide I can find on the internet. I've googled a hundred different times, I've done everything I can think of but I can't get qxdm to allow me to write the meid to the phone! After I zero out all esn locations, I attempt to write my meid. Everytime I get the same answer: Error response received from target.
Let me recap... I've tried downgrading the radio to stock (and tried other radios as well), downgrading to android 1.5, it's been rooted, I've scanned and scanned and scanned in cdma workshop to be sure I have all esn locations, with airplane mode on and off, I've done memory dumps then went thru them with a hex editor to be sure I haven't missed any esn locations, etc, etc.
After more than a week of trying to get this phone usable again, I don't know what to try next. I've reached the end of my known options with this phone, and could really use some help!!!
did you ever figure out the problem?
No, not yet. This seems to be a nearly dead topic around here, but hopefully someone can help me out.
I might have something that could work for you. Pm me if you want to give it a shot.
Locked & Loaded
""shooter on Deck""
budgreen did you send spc/msl before using the meid write command? example: spc 000000 (your msl/spc)
and please keep us updated if you get it fixed, hopefully between myself and laie1472 we can get you back up and running
message me if you need any more help
whoshotjr2006 said:
budgreen did you send spc/msl before using the meid write command? example: spc 000000 (your msl/spc)
and please keep us updated if you get it fixed, hopefully between myself and laie1472 we can get you back up and running
message me if you need any more help
Click to expand...
Click to collapse
Yep, I did all that every time. And still no go. But, exploring some other options...I DID manage to finally get it. Thanks to help from you and from Klown80. I appreciate it big time.
woot awesome enjoy your repaired hero
Hi, quickly - apologies for the grovelling "plz help m3" thread, but i'm trying to sort out the logistics of moving house on a deadline for today from work using my now non-functional mobile and i'm in a bit of a panic! I normally hate these threads.
So, for some reason my phone has stopped sending or receiving calls and texts. Data is completely unaffected. This just happened out the blue this morning and nothing i've tried has been able to fix this. I'm running ARHD 31, with no custom kernel. 4A.21.3263 radio and i'm on 3UK. S-off with bootloader 1.44.
I've tried installing a different radio, the same radio, reflashing ROM, clearing cache/dalvik/data several times. Restoring nandroid. Everything I can think of, but when I make a call I just get a loud tone and my phone returns to the dialpad. When people call me they get the same thing.
Any ideas?
Forsh said:
Hi, quickly - apologies for the grovelling "plz help m3" thread, but i'm trying to sort out the logistics of moving house on a deadline for today from work using my now non-functional mobile and i'm in a bit of a panic! I normally hate these threads.
So, for some reason my phone has stopped sending or receiving calls and texts. Data is completely unaffected. This just happened out the blue this morning and nothing i've tried has been able to fix this. I'm running ARHD 31, with no custom kernel. 4A.21.3263 radio and i'm on 3UK. S-off with bootloader 1.44.
I've tried installing a different radio, the same radio, reflashing ROM, clearing cache/dalvik/data several times. Restoring nandroid. Everything I can think of, but when I make a call I just get a loud tone and my phone returns to the dialpad. When people call me they get the same thing.
Any ideas?
Click to expand...
Click to collapse
Are you on SuperCID by any chance? Some carriers seem to be blocking SuperCID, if you are, try changing it back to your carriers CID.
Used phone? Could be IMEI banned, happened me on a Galaxy S3 used sold by a thief.
This happened to me...here's your fix
-----------------------
Alright so this is what reenable voice calls. I downloaded omjs ROM from august ( really any stock ROM should do) so I would have the ability to use all the programming codes and update the profile. Obviously do a full wipe( system,data,cache,dalvik cache) loaded the ROM once it got settled and I went past the initial startup stuff I did what's called an "SCRTN" (that's ##72786# on your phones dialer) then hit the three dots and confirmed I wanted to reset the network settings. Also an "RTN" (##786#) won't work because of the custom recovery in case anyone was gonna do that instead. Let the device come back up it should auto activate and go through the hands free activation on its own if it doesn't just go to settings and update the profile you can do the prl too while your doing it just to make sure everything is working fine. Then reload this rom and toggle airplane mode on and then off and there you go. Now this worked for me it may not work for you just keep that in mind but hopefully this helps until they find out what may cause that issue.
Hi guys, thanks for the ideas! The phone is definitely not IMEI blocked as I bought it new and its not superCID. I'll try the fix with the codes and see if that works. I get an 'unrecognised code' error when typing in the codes on ARHD, i'll try and stock rom and see if they work there.
EDIT - No luck. Those code aren't recognised.
Forsh said:
Hi guys, thanks for the ideas! The phone is definitely not IMEI blocked as I bought it new and its not superCID. I'll try the fix with the codes and see if that works. I get an 'unrecognised code' error when typing in the codes on ARHD, i'll try and stock rom and see if they work there.
EDIT - No luck. Those code aren't recognised.
Click to expand...
Click to collapse
OK, so I played around in the settings a bit and noticed that my number was showing up as something different - from memory it looks like the number my SIM had before my old number was ported over. So I rang my carrier and told them, guy did a 'backline check' and turns out my hunch was right! My number was somehow mismatched, they're sorting it out now. Thanks for your ideas guys.
This can be closed by a mod if they wish
Forsh said:
OK, so I played around in the settings a bit and noticed that my number was showing up as something different - from memory it looks like the number my SIM had before my old number was ported over. So I rang my carrier and told them, guy did a 'backline check' and turns out my hunch was right! My number was somehow mismatched, they're sorting it out now. Thanks for your ideas guys.
This can be closed by a mod if they wish
Click to expand...
Click to collapse
Just add [SOLVED] or [CLOSED] to the main thread title
Ok, so I got everything done as per instruction on the bog thread about putting the XT883 radio on an XT862. Done. Every step done. exactly as stated. I have my straighttalk Sim in, and my phone doesn't do anything. got the red no smoking sign in the bars. no service. no phone calls.when I go to search networks. Networks unavailable.
When I go to *#*#4636#*#* set preferred network is set to unknown, and will not change and when I go to select radio band, USA in unsuccessful. well, they all are.
I flashed the radio, moved the build.prop and everything that is to be done. My phone reads as an 883 on my google play account, and all should be fine. Is there a reason the preferred network can't be set? I need to get my phone working because my job is an on call job, and if something happens to my work phone, my personal is kind of important. However, it currently does run N64 quite well, lol. Any help will be greatly appreciated. Thank you and thanks for all your guys' work om getting this whole Droid 3 on ST as smooth of a process as it is.
CPLSeraphim said:
Ok, so I got everything done as per instruction on the bog thread about putting the XT883 radio on an XT862. Done. Every step done. exactly as stated. I have my straighttalk Sim in, and my phone doesn't do anything. got the red no smoking sign in the bars. no service. no phone calls.when I go to search networks. Networks unavailable.
When I go to *#*#4636#*#* set preferred network is set to unknown, and will not change and when I go to select radio band, USA in unsuccessful. well, they all are.
I flashed the radio, moved the build.prop and everything that is to be done. My phone reads as an 883 on my google play account, and all should be fine. Is there a reason the preferred network can't be set? I need to get my phone working because my job is an on call job, and if something happens to my work phone, my personal is kind of important. However, it currently does run N64 quite well, lol. Any help will be greatly appreciated. Thank you and thanks for all your guys' work om getting this whole Droid 3 on ST as smooth of a process as it is.
Click to expand...
Click to collapse
did you get the unlock code and unlock it?
PassingThruLife said:
did you get the unlock code and unlock it?
Click to expand...
Click to collapse
Yes, phone is unlocked and everything should be right. I have it set to GSM/UMTS but I was a little confused on my unability to change it from unknown to GSM...
Redownload build prop, and replace, and/or fix permissions
Sent from my Amazon Kindle Fire using Tapatalk
I tried the build.prop again. nothing. same thing. However, something completely stupid just crossed my mind. We live in a basement Apt out of town a ways. I'm going to check if, when we go to town tonight, I get service. May just be something that silly. I'm going in to look at my radio to ensure the flash was succesful considering I am having an issue with it all together. However my phone reads as an 883 on Google Play, when I hook up to PC, it says something about XT862 drivers are working correctly
Motorola Phones can be sim card sensitive/picky may need a new sim card. even if it works in another phone.
Did you check build prop permissions?
---------- Post added at 02:50 PM ---------- Previous post was at 02:46 PM ----------
rw-r--r--
or
.......... Read Write Execute
Owner .....x ...... x
Group .....x
Others ....x
or
0644
I don't know how to do that, or what you mean. I am looking at the build prop now, but can you tel me where to look, SD Shadow?
Also, when hooked to PC, it reads as an XT883, just so it is known the radio was flashed.
Got permissions. However it just says
Owner, Group and Others, which I checked off the way you said. None of the other things. but the checks were way differant.Is there anything differant for the special permissions? none are checked.
I checked what was stated above. all is still the same. no service available.
which root explorer are you using?
I am using root explorer from Speed software. the one that cost 3.99
I also did a factory reset. kept the build.prop and all. Kind of debating to try the whole thing over. Or is there maybe a couple places to look to ensure everything is in its proper place?
CPLSeraphim said:
I am using root explorer from Speed software. the one that cost 3.99
Click to expand...
Click to collapse
long press on build prop>Permissions
sd_shadow said:
long press on build prop>Permissions
Click to expand...
Click to collapse
got that done. stilll the same.
I guess tomorrow I will buy another $60 kit from walmart with the straighttalk Sim and $45 monthly plan. A little discouraging since the last time I did, the $45 card didn't work because they checked it out wrong. What sucks is I got this new SIM from Straight talk CS because mine messed up, and now I get to blow more money and hope walmart doesn't mess it up this time. I guess I will see tomorrow if it was the Sim Card.
I am getting frustrated, moreso because this phone is pretty awesome, and does some amazing things. Never thought I could play N64 and PS1 on a phone. I just need to make calls. I'm not tech savvy, but these directions are right on the mark, and I know everything was done right, so it's gotta be the SIM. If it is not the SIM, I guess I will be back at square 1 tomorrow.
I did some testing, I think the radio is not getting changed.
Baseband should be n_16.18.16s with or without sim card
see Menu>settings>about phone>baseband
if it is saying unknown, reflash original .890 radio
copy to the fastboot folder from the unzipped unlock.zip file
then reboot phone to ap fastboot mode
and in command prompt
cd desktop
cd fastboot
moto-fastboot flash radio radio2.img
moto-fastboot reboot
baseband should be unknown
unless you still have 890/906 build prop, then it will be N_03.18.29P
then
reflash the XT883 radio
moto-fastboot flash radio radio.img
moto-fastboot reboot
you are getting
sending radio 14404 kb ... okay
writing .....okay
phone is rebooting, and it is showing a screen with a progress bar and it is taking a few to complete? before finishing booting?
Ok, I am going to try that. Baseband says unknown, even though model number says XT883
Ok, I flashed the old radio, thanks for that file, and it still said unknown. reflashed the new radio again
sending radio 14404 kb ... okay
writing .....okay
phone is rebooting, and it is showing a screen with a progress bar and it is taking a few to complete.
I'll be dammed. I got the roaming triangle and a box with a plus sign where the signal goes. says no sim as well... got the baseband number as well. must not have flashed right the first time...
UPDATE: Ok, so I reflashed the radio.. had some funky stuff go on... then remembered again the whole basement thing, so I went to a window. I am now able to make calls and revieve and txt either way. Now that it is all solved, I just have to do my APN.
Thanks you SD_Shadow. I never was going to figure out the radio did not flash... Thanks for your insights and patients, and the files to restore the other radio.
great, your welcome.
Sent from my XT894 using Tapatalk
Hey, thanks for clicking my post. TL;DR Since updating from ARHD 40.3 to Viper One 6.2.0, my radio has been having major intermittent issues. I have a HTC One m7_ul unlocked outright from Optus here in Australia. It is as of right now running the latest firmware linked to by the Viper One/ARHD threads, the latest TWRP, is S-OFF and superCID, running Viper One 6.2.0.
Symptoms:
1) No signal most of the time.
2) Signal appears to return during periods of movement (e.g. driving).
3) Even at full signal, there is no mobile connection (no data, no text/calling).
4) Once every few hours, when it has signal, it will gain mobile connection for a short period of time, after which it will cut out again - repeat to 1).
Here's a short story about how this came to be:
For many many months now it has been running just fine on stock firmware, rooted with S-ON running ARHD 40.3 (since that version came out).
About a fortnight ago I started noticing issues with my contacts application. Something to do with 501 contact link suggestions and certain contacts having hundreds of Facebook profile entries. This would cause issues in the People app (people just wouldn't load) and the SMS app (message histories wouldn't load, including new texts).
After some troubleshooting attempts, I resolved to reinstall a ROM. I opted to install the latest Viper One (6.2.0) successfully. It resolved my issues. However, it introduced a new one. The next morning I woke up to 4 texts from my service provider informing me I'd missed calls. I had no notifications as such, so the calls never reached my phone. I put it down to tower signal flex in my area. I left and as I walked out the door I noticed I had no signal (no bars, x above the icon in statusbar). Driving around seemed to fix the issue though, it got back up to normal values quickly enough.
However, even though I had plenty of signal and mobile data was ostensibly turned on, I couldn't get internet. I tried sending a text to myself but it failed send. Calls out simply waited on signal and then timed out. Every single other function of the device is 100% AOK (wifi, bluetooth, nfc, etc). The entire ROM is fully functional, can't find any other issues with stability or otherwise.
I put up with it for the day and get home and start troubleshooting. Here's what I tried so far, in order:
1) Change from Viper One to latest ARHD (71.1). Installed with no issues. Booted phone, no dice - no signal.
2) Checked SIM by moving to old iPhone 4 - full signal, radios work. It's not a service issue.
3) Revert to last known working ROM - ARHD (40.3). Installed with no issues. Booted phone, no dice - no signal.
4) Research research research. Think it might be a problem with firmware perhaps. Tried revone, failed because I'm not on 4.2.
5) Flash MaximusHD (11.0.0) in order to make use of revone for S-OFF/superCID. Flashed latest firmware linked in Viper One/ARHD threads.
6) Reboot phone. Still no dice with latest firmware on MaximusHD (11.0.0).
7) Retry with latest ARHD. No dice.
8) Retry with latest Viper One. No dice.
In every single instance, all the ROMs are fully functional except for mobile signal - wifi, bluetooth, nfc, etc. radios function perfectly. No issues with ADB or fastboot during any step of these processes. All my device info shows what I expect to see. I've searched as much as I can, to no avail. I turn to first-time posting here as a last resort to maybe find out what the issue is.
I am slowly reaching the thought that the hardware itself might be the issue. I'd appreciate any insight into what could be causing this - be it software or hardware - as well as if there is any way to test or diagnose the radio physically. Even just a confirmation ("Yep, sounds like your radio's FUBAR"). In the meantime, I'll be using aforementioned iPhone 4 (ugh).
Thanks for reading.
Have you attempted to flash a different radio baseband?
Look up the radio version used in ARHD 41. If you find it, search for the radio within the forums and flash it. You can still keep the most current version of your preferred ROM. Search the threads for how to flash a radio baseband, there are plenty of them.
digitalism said:
Have you attempted to flash a different radio baseband?
Look up the radio version used in ARHD 41. If you find it, search for the radio within the forums and flash it. You can still keep the most current version of your preferred ROM. Search the threads for how to flash a radio baseband, there are plenty of them.
Click to expand...
Click to collapse
I found a forum for HTC One radios here, it's in the AT&T section but apparently work on all HTC Ones. I was unable to find out which radio ARHD 41 used, my understanding is that custom ROMs don't usually come with a radio baseband of their own and they don't appear to list any on their thread that I could see. I would inquire but I think there's an issue with new users posting in development sections. Do you think it's worth trying to look further into what radio was used, or should I start flashing radios from the aforementioned list? There's a couple that stand out as possible candidates (the earliest version, the newest version, etc) but I'm not sure I want to just start going crazy on that list until something works. Or do I?
edit: To clarify, and they say explicitly in the ARHD post FAQ, they do not include radio/hboot/firmware in their ROM. So I must assume that I was simply on the stock radio the device shipped with.
edit 2: Confirmed my current baseband matches one of the ones indicated as installed from firmware package. I'm not sure what it was before I updated to Viper One or even while I was using Viper One.
Flashed the earliest radio baseband available from the aforementioned thread. Put the SIM back in, signal achieved, able to send texts/make calls/USSD codes. I was unable to get it to transfer mobile data, however.
Can't believe I didn't think about radio baseband. Didn't even know that was a thing. I just thought it was part of the firmware package. There you go I guess. Thanks again for the tip.
Whitestrake said:
Thanks again for the tip.
Click to expand...
Click to collapse
No problem, just remember that if you're having issues with certain partitions on the device, each partition is technically flashable if you are S-Off and SuperCID.
digitalism said:
No problem, just remember that if you're having issues with certain partitions on the device, each partition is technically flashable if you are S-Off and SuperCID.
Click to expand...
Click to collapse
I've tried just about every radio in that forum. They all seemed to have the same issue for me - at first it seems to have no signal, then it gets normal signal, receives/sends any buffered texts, and then fails to work after that for any purpose regardless of signal. I think I'm back at square one; I don't suppose there are any other simple things to try?
Whitestrake said:
I've tried just about every radio in that forum. They all seemed to have the same issue for me - at first it seems to have no signal, then it gets normal signal, receives/sends any buffered texts, and then fails to work after that for any purpose regardless of signal. I think I'm back at square one; I don't suppose there are any other simple things to try?
Click to expand...
Click to collapse
If you are having issues still, the other alternative is to flash a different firmware version than what the ROM provides. Firmware and radios tend to "talk" to each other in certain ways, so maybe your firmware isn't using your radio the way you need it to. Also, make sure you are installing firmware particular to your device. For instance, do not install firmware originally meant for an AT&T phone if you use Verizon or another carrier. They tend to write the code particular to these things. I would do some research through the forums and see if you can find a good combination in your area that people have tried. Maybe even a Google search will help out if the forums seem daunting to dig through.
And don't forget, the iPhone has a Quad-Band receiver that's capable of receiving cellular signals much clearer. The HTC One, in my opinion, does not match hardware compared to the iPhone. The iPhone will always technically be superior, no matter what opinions people hold to both.
First, thanks again for your patience and assistance.
digitalism said:
Also, make sure you are installing firmware particular to your device. For instance, do not install firmware originally meant for an AT&T phone if you use Verizon or another carrier.
Click to expand...
Click to collapse
I was not aware of this restriction. I suspect I may have flashed firmware for a different region. I isolated the Optus firmware RUU numbers and got a firmware package matching, and the android-info.txt matches the device original CID and modelnum. I'll try it soon.
I'm still having trouble understanding, though, how it could have failed in the first place. My phone was S-ON when the radio stopped working; surely changes to firmware/radio couldn't have occurred anyway? None of the ROMs I've touched have firmware or radio included as far as I could tell.
Flashed the firmware appropriate to my region (4.20.980.1). Came with radio. Rebooted, put in SIM, no signal for 5 minutes. When I get signal, texts don't send and calling times out, USSD codes give connection problem errors. Same as before. How likely is it the actual hardware could be damaged? I did drop it on concrete, on the front of the device at the top, around the time this started happening - very shortly before I flashed Viper One to fix the contacts issue. There was no visible damage.
Whitestrake said:
Flashed the firmware appropriate to my region (4.20.980.1). Came with radio. Rebooted, put in SIM, no signal for 5 minutes. When I get signal, texts don't send and calling times out, USSD codes give connection problem errors. Same as before. How likely is it the actual hardware could be damaged? I did drop it on concrete, on the front of the device at the top, around the time this started happening - very shortly before I flashed Viper One to fix the contacts issue. There was no visible damage.
Click to expand...
Click to collapse
Quick question:
Are you installing your firmware and software without the SIM card in? If so, I would leave the SIM card in and have all the software installed during the process. Damage to the phone should not cause problems for connecting to the cellular network. Have you tried leaving the house, going outside, or getting into a different area to try your signal? Maybe your house is a deadzone and the phone is having a hard time picking it up. My room gets like this since I live in Florida where houses are built with cinder blocks to prevent hurricane damage. It really messes with my signal.
digitalism said:
Quick question:
Are you installing your firmware and software without the SIM card in? If so, I would leave the SIM card in and have all the software installed during the process. Damage to the phone should not cause problems for connecting to the cellular network. Have you tried leaving the house, going outside, or getting into a different area to try your signal? Maybe your house is a deadzone and the phone is having a hard time picking it up. My room gets like this since I live in Florida where houses are built with cinder blocks to prevent hurricane damage. It really messes with my signal.
Click to expand...
Click to collapse
Good ideas, but unfortunately not - every firmware and radio package I've flashed, I've done once with the SIM, once without, thinking along a similar line.
I'm in a known good cell location - coverage in my area is fantastic with my provider (Telstra, usually get 5 bar signal on 3G - I do not get LTE on my plan). I test in multiple places - next to my PC, outside the house, down the street, etc. The behaviour I've noticed is that I have no signal regardless of where I go, for about 5 minutes after booting the phone, after which it gets signal, sends/receives any buffered texts, and then fails to communicate successfully after that (i.e., I get the test text I sent myself, then I resend another test, and it fails to send). The iPhone 4 I've been moving my SIM to has been receiving full signal (as expected) at every place I've been testing the HTC One.
Hmm...
You might have to go into your APN settings to change some things in order to get it to work properly. Go to your Settings, then Mobile Data, then Access Point Names. From this menu click the current APN saved with the phone. After that, it will have you insert some information. Check this website for the specific APN information for your carrier. Make sure it's for your carrier as there is a large list of different ones on there.
http://ausdroid.net/apns/
Other than that, I honestly couldn't tell you what your issue is.
digitalism said:
Other than that, I honestly couldn't tell you what your issue is.
Click to expand...
Click to collapse
Tried the APN thing. There was indeed a few things different from the listed settings, but honestly, they were pre-populated with a bunch of Telstra data beforehand when the SIM was in. I made the changes and noticed no difference.
Thanks again for your help. As a last step I will return it fully to stock. After that I suspect my only recourse would be taking it back to Optus and asking if they'll quote me to fix it.
Unfortunately it does seem to be hardware issue from the history of what you have tried and posted.
Use nkk71's guide listed in my signature to go back to stock for warranty but substitute your local RUU/nandroid/etc.
SaHiLzZ said:
Unfortunately it does seem to be hardware issue from the history of what you have tried and posted.
Use nkk71's guide listed in my signature to go back to stock for warranty but substitute your local RUU/nandroid/etc.
Click to expand...
Click to collapse
Thanks for the link, that's actually one HTC One return-to-stock guide I haven't seen yet and it looks very concise. Cheers.
Whitestrake said:
Tried the APN thing. There was indeed a few things different from the listed settings, but honestly, they were pre-populated with a bunch of Telstra data beforehand when the SIM was in. I made the changes and noticed no difference.
Thanks again for your help. As a last step I will return it fully to stock. After that I suspect my only recourse would be taking it back to Optus and asking if they'll quote me to fix it.
Click to expand...
Click to collapse
Sorry about that, I know having a custom ROM is a lot of fun, but there can definitely be some cons along with it.
Good luck with your phone!