Related
i bought a used g1 no physical problems took it into a shop and they couldnt find anything wrong with it internally so im guessing its a software issue....dont know if this guy i bought it from tried to mess with root and messed something up but im thinking its some sort of software stuff....can anyone PLEASE help!?!?!?!?! i either get this phone fixed or keep using my nokia that seems like its from 1998 and its killing me!!!!!!
What are the stats of the phone? You can check the versions in the settings\about phone area. Model #, Firmware version, Baseband version, kernel version and build number information would be helpful.
Is it already rooted? If not, you may want to go ahead and start reading up on the root process. Some of the newer builds may or may not help the issue. But if it isn't rooted and you arent getting a signal, it very well may be a network issue. Also, does your phone service have a data plan? Has the phone gone through and passed all of the sign-in procedure? (being from another country, I am not sure what all you have to do to activate your phone) Sim card good?
thats the problem i did a factory reset to input my gmail info and now i cant get past the damn activation screen! ive been through all the customer support through tmo and cant figure anything out!!! im goin crazy
also ive found this webpage http://developer.htc.com/adp.html that has recovery, system and radio images from htc and every time i try one of them it comes up and says no signature or no verification.......not sure what to do
forum.xda-developers.com/showthread.php?t=452316
you cant apply those because your phone is not rooted. learn what your doing without randomly flashing everything that can killed your phone. and yes, you can kill your phone permanently flashing the wrong **** (i.e radio/spl)
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Kraizk said:
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Click to expand...
Click to collapse
Yes, twice
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
I'm going to try this now thanks
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Kdenery said:
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Click to expand...
Click to collapse
Try flashing a CM10 ROM. I've always seen the option there. The kitkat ROMs I have used do not have the option except for the Nocs GE.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
-TheEdge- said:
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
i'd kinda like to argue a point here as this just happened to me. i am certainly not new to flashing, starting back with the mogul and having almost every sprint smart phone since then unlocked (windows) or rooted (webos and android).
Using TWRP and previously running ecliptic 4.3 i wiped caches, system and data then installed the 4.4.2 from team d3rp and voila... no service no meid no nothing.... yes i have the latest radio on my phone.
i guess my point in this is that there's a number 3 that you didn't mention.
3. sh!t happens and it's not n00b related.
for anyone else that has this issue... flashing CM 10.1 worked for me. i didn't even have to set up anything, it just picked up signal. so i rebooted, wiped and nandroided back to 4.3 and all is well.
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Robert542 said:
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't... it was SuperOneK. i'm certainly not blaming the rom though. especially not when others are flashing it fine. the ONLY thing i can think of possibly happening is a bad download. I was in a rush and didn't check the md5.
I had a similar problem when flashing miui. Nothing worked. Even went back to a sense backup and nothing worked.
Commit failed as well.
Here's what I did to make it work again.
Flashed cm10. Change the network settings for CDMA. (Boom it SAID I had service..but didn't).
Rebooted a few times (probably not necessary).
Flashed a sense 4.3 ROM that was close to stock.
Update msl and all that. Commit.
For me..changed LTE/CDMA to just CDMA (no 4g in wv).
Boom it worked again. Hope this helps!
Sent from my HTCONE using xda app-developers app
My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.
EtherBoo said:
My phone out of nowhere started doing this really fun thing where it drops to roaming at random. From what I can tell, the phone is not making a handoff to the next tower to avoid the roaming. For example, if I'm sitting under a tower with full 4G, everything is fine. If I have 2 bars, it will work in 4G for a while before dropping to 3G roaming. I am able to force it back into 4G by dropping in and out of Airplane mode.
I'm running the official CM11 4/30 nightly (I was on the March Snapshot until this started happening).
First I used some Google-Fu and found it's most likely a bad SIM. I swapped SIMs with my wife, she was stuck in 3G roaming, awesome! Went to Verizon, the switched the SIM, all good, right? Nope, I didn't notice it right away, left the store and thought all was good until I needed to use internet at work.
Next, I thought it was software, so I created a backup, and dirty installed the newest CM11 nightly. No change, so I did a full wipe and install. No luck.
So next I thought maybe the radio was corrupted, so I tried to update the radio, which didn't go so well. I got stuck in a boot loop and had to sideload the old driver and reflash. So I'm back up but still having this problem. I'm thinking my only thing I can do at this point is to go to stock and see if the updated radios make a difference.
I saw another guy is had the same problem, but he had his phone replaced. I'm not sure if that will work for me since I purchased via Swappa (I do have Asurion insurance though).
So what help do I need?
1) Does anyone have any ideas on what I can do to fix this?
2) Are there any good instructions out there for how to flash to stock?*
3) Are there any good instructions on how to re-root and flash back to a custom ROM once taking the newest OTA?*
*Most of the instructions I've found have been pretty confusing and use a lot of acronyms without explaining them. I'd be willing to write some cleaner instructions for a sticky if someone would be willing to help me out with any questions I have.
Thanks everyone, I appreciate any help offered.
Click to expand...
Click to collapse
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.
dr_w said:
Get anywhere? I'm experiencing the same. Roaming all the time. Going to revert back to stock 12b and see what happens.
Click to expand...
Click to collapse
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.
EtherBoo said:
I'm fairly certain it's hardware. I spent a day using my Galaxy Nexus - full 4G the entire day.
I went back to stock, "bricked" my phone about 3 times doing it (quotes because it was salvageable, but I had a couple hours where I was googling like a madman worried I dun ****ed up). Stock and the new radios made no difference. In fact, with stock it would only go to 4G if I restarted it - airplane wouldn't even bring 4G back. Figure that one out.
I went to the VZW store and I'm basically screwed. I can call LG and see if they'll replace it or use Asurion. Since I got the device off Swappa, they cannot replace it. They tried to order me a new one, but the system wouldn't let them. I don't really have time to call LG, so I'm probably going to Asurion it. Their process is stupid simple to do and they'll have a phone to me the next day. Then I can spend all day tinkering with it and getting CM11 back on, which I feel like I'm an expert at right now.
Sorry, wish I had better news. If you got the device from VZW, go to the store after flashing to stock. They might want to try swapping your SIM first though, so make sure you go to a store that has decent 4G coverage in its surrounding area.
Click to expand...
Click to collapse
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great. "
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
dr_w said:
Thanks dude. I think you are right, flash stock and get a new sim first. I have a hard time believing its a hardware problem. I just wrote this in the other post about roaming:
"Same exact problem here. I was on the phone with Verizon last night. I was running cloudy pro 2 (all his roms for that matter as they are international roms) and kept getting the roaming issue you speak of...with 3g. I went back to 11A completely bone stock. Just like you mentioned, I get 4g but then after like 10 minutes I get 3g with roaming. Of course this is after I spent 30 minutes on the phone with tech support. They 'zapped' my sim card and it appeared to work but no dice. Now before doing all this I downloaded build prop editor and changed the ro.build.target_country to US versus COM as everyone suggested in all the forums, still no dice. I've tried the toggle airplane mode trick...works for like 5 minutes and back to 3g roaming. I think maybe a new sim card and avoid international roms...bummer because cloudys roms are blistering fast. Interesting thing though, I installed xdabebbs rom and malladus' rom, after already running cloudys roms, and get 3g but no roaming. I also verified that Verizon wasn't throttling me or something like that. One more thing I tried is reflashing the basebands and 24A modem, no dice. If there is a build prop fix or some other fix I'd love to hear it.
Edit: One think I'd like to mention. When I had an S4 I switched between stock roms and AOSP roms and the network settings were responsible for causing the roaming because the stock rom was an older build than the AOSP. So when I had roaming, I'd reflashed the AOSP rom, changed the settings then flash the stock rom. It worked great. "
Edit#2: Ok making a little progress. Just did this:
Get a build.prop editor from the play store, and change ro.carrier to VZW and ro.build.target_operator to VZW and ro.build.target_country to US.
Initially it worked but when I make calls it gives me Unfortunately, the process com.android.phone has stopped and I cant make calls. I went into Settings, Apps, reset app preferences...that didn't fix it either.
4G/LTE is pretty solid now but again, I cant make calls.
Edit#3: Nevermind...roaming again.
Click to expand...
Click to collapse
Alright, so, I have some interesting news.
I got a replacement device from Asurion - not just a replacement, a brand new device out of the box. I pulled it out of the box, swapped the SIM, same exact issue .
I went to Verizon and *****ed up a storm. They basically said "you bought it on eBay, not our problem" (I actually did Swappa - but they don't know Swappa and they do know eBay).
So I got the guy in the store to do some digging, and apparently Verizon has a point opened up with LG as they're seeing this on more and more devices - especially since KK came out. So I figured I could try an older radio. The device was on 12B when it arrived. I just flashed stock to 10B and it's the same issue. I don't know what's going on at this point - nothing makes sense but its apparently a known issue that's been appearing since the KK update.
I'm going to call Asurion and request a new device again since this one is doing the same thing, we'll see what happens. I'm still leaning towards hardware and thinking there was a slew of bad radios that went out.
Just for giggles - and I have no reason whatsoever to think this will work. I'm going to swap out the new SIM that came with the phone. Originally, I just put in my old SIM since the new one was taking too long to activate. I'm having the exact same issue I had previously. With that, I'm going to leave the new SIM in and see if it has the same dropping issue. The guy in the store had mentioned he could swap out the SIM but after a few days it will crap out again... which makes zero ****ing sense. Because of that, I might as well see what happens if I pop a new SIM in. While again, this makes 0 sense, I'm wondering if maybe the phone is frying the SIM somehow?
Again, it makes no sense at all, but I have nothing else left to try other than getting Asurion to repeatedly send me phones until I find one that works or they replace for another type of phone (which I REALLY don't want). I'll drop an edit in an hour or so if what I try makes a difference.
Quick Edit:
I COULD just keep going to the VZW store and have them repeatedly swap out SIMs since it will fix it for a few days .
EDIT:
Got the new SIM installed and it's working. The guy in the VZW store told me that we can keep swapping SIMs and the same issue will happen, which again, makes no sense to me. I'm at a bit of a loss to be honest. I wonder if it's possible that my old device was frying the SIMs (again, makes no sense) and that maybe the new SIM not going in my old device will fix the issue.
What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk
dr_w said:
What ROMs are you running? A phone frying a Sim does not sound likely at all. I got my new sim card and have been running xdabebbs ROM with no network issues. I feel like my issues stemmed from the Intl ROMs.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The only ROM I've ever run was CM11.
Same thing happened on stock though after flashing through the LG Flash Tool. Then, with the new phone from Asurion, used old SIM - 3G only. Used new SIM - 4G sticks.
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!
I am happily using liquid smooth but wanted to test a few things on stock. when i deploy stock i get stuck on the activating the connection part. I let it sit for about 15 minutes and still nothing. i can restore my nandroid and connect again just fine.
I am new to sprint so i don't really know the ins and outs.
Thoughts?
Also I can only get 3g when I had 4g with this room earlier. Do I need to call sprint?
JustusIV said:
Also I can only get 3g when I had 4g with this room earlier. Do I need to call sprint?
Click to expand...
Click to collapse
Have you used the Sprint fix zip for custom Roms? If not, search around for it. That might help. As far as stock hanging up, I've had that happen too. I usually just cancel and retry and it goes through. You can find the data reset dialer code here:
http://forum.xda-developers.com/showthread.php?t=2949996
That might help too.
Funny... I'm having a similar problem. I switched to CM Nightlies for about three days. I experienced some instability today, so I decided to go back to stock for a while.
I flashed the newest factory image and re-locked my bootloader. It hangs on "Waiting for activation" or something like that. Nothing I do in settings resolves this.
Going to give it a little time and pray it fixes itself. I really loathe having to call customer service.
I skipped and went to more/cell networks/carrier setting/update Prl/update config and it went through. On stock.
Just an update. I moved my phone to Verizon and got instant 4G.
I just couldn't handle the crap service anymore.
Moved from one evil to one super evil.