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
Related
My one rebooted and lost all data and cell service about 3 weeks ago. Theres no MIN# or phone number shown and I have tried multiple backups, ROMs, and data settings. I brought it to sprint and they were useless. I have WiFi and I got 4g for a brief second in Idaho Springs, CO. Is this a hardware issue or software issue? I tried an RUU once, but messed up and deleted everything but the bootloader from my phone. I am cautious to try it again as I am on 1.31.651.2. Is there any way to tell if this is a software issue or if the antenna itself is broken?
Thanks
mgolland45 said:
My one rebooted and lost all data and cell service about 3 weeks ago. Theres no MIN# or phone number shown and I have tried multiple backups, ROMs, and data settings. I brought it to sprint and they were useless. I have WiFi and I got 4g for a brief second in Idaho Springs, CO. Is this a hardware issue or software issue? I tried an RUU once, but messed up and deleted everything but the bootloader from my phone. I am cautious to try it again as I am on 1.31.651.2. Is there any way to tell if this is a software issue or if the antenna itself is broken?
Thanks
Click to expand...
Click to collapse
If you are on a ROM that will support it try to dial ##72786# and then tap menu in the top right corner, then reset. This should force your phone to reactivate. Hope this helps!
I'm having the exact same problem with the exact same Sprint experience. As far as I can tell, the radio is borked somehow and it will not allow the MSID to commit. I believe it has something to do with the NV setting, but I am not sure where to access subscription settings in a CM based ROM following this thread.
http://forum.xda-developers.com/showthread.php?t=2447361
thisguy81 said:
If you are on a ROM that will support it try to dial ##72786# and then tap menu in the top right corner, then reset. This should force your phone to reactivate. Hope this helps!
Click to expand...
Click to collapse
jamesissocool said:
I'm having the exact same problem with the exact same Sprint experience. As far as I can tell, the radio is borked somehow and it will not allow the MSID to commit. I believe it has something to do with the NV setting, but I am not sure where to access subscription settings in a CM based ROM following this thread.
http://forum.xda-developers.com/showthread.php?t=2447361
Click to expand...
Click to collapse
Trying a CM Rom now, I alread tried ##72786# a few times no luck.
jamesissocool said:
I'm having the exact same problem with the exact same Sprint experience. As far as I can tell, the radio is borked somehow and it will not allow the MSID to commit. I believe it has something to do with the NV setting, but I am not sure where to access subscription settings in a CM based ROM following this thread.
http://forum.xda-developers.com/showthread.php?t=2447361
Click to expand...
Click to collapse
It worked! my phone is showing service and 3g, but i think I need to reactivate my phone ( i get a message saying i can't call the number i dialed when I make calls). Can I do that from a CM based rom or do I need to reflash a sense rom?
mgolland45 said:
It worked! my phone is showing service and 3g, but i think I need to reactivate my phone ( i get a message saying i can't call the number i dialed when I make calls). Can I do that from a CM based rom or do I need to reflash a sense rom?
Click to expand...
Click to collapse
I backed up my CM Rom and flashed a stock rooted Rom for activation. It activated itself on stock. Glad you are back up and running.
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
This has happened to me before, and I had never actually fixed it. Basically what happened was out of the blue, I had no service. I did not do anything to cause this, or at least I don't think I did. I don't know if 4G works, but I'm sure 3G does not. This is all the info I have at the moment (see picture). Last time this happened, I met this guy at my local Sprint store who was cool enough to give me a new phone and make this all go away. But I don't have that option this time, and I would love any help. Thank you in advance.
What did you do before this happened? Did you flash a different ROM? If so, what ROM were you on and which one did you flash to?
I am currently running the latest version of Cyanogenmod, (11/30/13) and when I had updated to today's release there was no sign of the service being gone.
When you go to CDMA subscription in settings, is it set to NV or RUIN/SIM?
How would I get to that in settings on 4.4.1?
Settings>more>mobile networks>CDMA subscriptions
This is what that brings me to.
Hmm network type?
It just brings up a menu to choose either 2G, 3G, or LTE.
I'm not sure but I think the 4.4.1 CM version doesn't have the option. Flash back to 4.3 version and make sure you are set to NV. I think that is your problem.
Installing right now, I'll keep posted
Make sure it is a CM based ROM as the sense based ROMs don't necessarily give you the option either.
After flashing a 4.3 CM ROM and making sure the network mode is set to NV, everything that was in my settings (MIN, MEID, IMEI) is back to normal, except for it still saying it is out of service.
EDIT: 4.2.2 ROM*
OK. Now flash a stock ROM and do a handsfree reactivation. That should get you back up.
Flashing this: http://forum.xda-developers.com/showthread.php?t=2467607 I hope this works.
You sir, are a life saver. I just wish I knew this info when I had my old phone. Thank you very much I hope this helps many other people as well.
Also, I tried flashing the latest CM after all of this, and right after it booted it asked me to insert a sim card. My sim card is in, and I don't know what the problem is there. I also had no service either.
If you are happy with the rom you might want to check with CM devs and see if you can toggle that setting some other way than flashing something else.
RealROGWaffle said:
This has happened to me before, and I had never actually fixed it. Basically what happened was out of the blue, I had no service. I did not do anything to cause this, or at least I don't think I did. I don't know if 4G works, but I'm sure 3G does not. This is all the info I have at the moment (see picture). Last time this happened, I met this guy at my local Sprint store who was cool enough to give me a new phone and make this all go away. But I don't have that option this time, and I would love any help. Thank you in advance.
Click to expand...
Click to collapse
This used to happen to my Galaxy Nexus. The cause may have been the radio I was flashing was a bad download. I would try flashing a new radio in recovery to see if that works...
i removed the default tapatalk signature
Oh, and another thing. What is your IMEI SV supposed to look like? because mine is 00 at the moment.
EDIT: I realize that is normal. I flashed the new radio, and I'm about to see if it works on CM 11
As some of you may have read, my phone is somewhat hosed.
I have a new one on the way (which might be a refurb). But I have nothing to lose playing with this one.
I highly suspect, one or more of the bands are disabled.
If you google around you see lots of folks fiddling around with Band Priorities and/or Enabling. Especially with "TirBand" phones (which this is). (Nexus 5 and HTC One, HTC One Max).
Most of the time people access this through EPST using ##4636# but my phone does not respond to this.
But the Galaxy S5 and HTC One (M8). Are in new Territory with Spark and even more bands I believe. So their might be new Menus for these phones and that info has not been leaked out yet.
Currently if I'm in a formally strong 4G area I get great 3G (no 4G at all). Yes 4G is enabled.
If I'm in Moderate to Weak 3G area. I get 1x or nothing. It really feels like a Band got shut off.
I'm not sure what caused it.
I was running Corporate PRL (56018). That seemed to not be causing any harm. Ran it for a few weeks.
Ran Barebones 1.0 (on stock firmware) and that ran fine too. After that it was down hill.
My only issue was Roaming Guard was on and Locked out. Which others have reported is a long standing issue (was a problem on M7 too).
All I needed to do was do a Full Wipe and enable it before it gets locked again. Not everyone has this locking issue, but MANY do.
I updated to OTA firmware. Not sure of status here because I had WIFI on normally.
Then I decided to run BadBoys Harman. Without firmware. Again not sure of status here as WIFI was on.
Somewhere I believe I did an Update Profile. I suspect at that point I was hosed.
It was when I put BadBoys on that I noticed an issue because he shows when you are on 1x.
Not sure if I started to see 1x that was before or after update profile.
I don't know if it's combination of having been on the corporate PRL when I did the update Profile or what.
I always try to do update Profile over mobile network.
I was not clear what the problem exactly was until I "Fully" upgraded (Harman with Harman firmware).
Just to be clear, I'm not blaming anyone but me. And there may be nothing wrong with anything out there than more or my phone. I just don't know.
I highly suspect it's something trivial that got turned off or the phone so happened to lose a band or antenna.
But I suspect it's some combination of SuperCID, Corporate PRL, new OTA Firmware or Harman Firmware along with Update Profile hosed me.
I do have new phone on the way. But I sure would like to know what happened.
I didn't do anything "out of bounds" from this forum. I simply may have done things in a different order or something.
I am S-OFF and running TWRP 2.7.0.2
I have reactivated, wiped the gazoo out of it. Ran Harmon RUU. etc.
I sure wish there was an RUU for the Shipped Config. Or even for the OTA version.
Seems a coincidence the phone "Broke" just when I started Flashing Firmware and Updating Profile.
I know I was good on Stock Rooted, S-OFF, Corporate PRL. Because I'd even see 4G at my house occasionally which is a reach. Now I'm lucky to get 1x at my house.
I will tell you this, I'm staying on Stock Firmware and Stock PRL when the new phone arrives until more is learned.
I will try to compare phones as best I can.
Which is another reason I sure would like to see the Band configuration on this phone so I can compare it to the new phone.
Thanks for any tips.
I think you were trying to do *#*#4636#*#* to access the Menu. The EPST command would be ##3282#.
I'd be interested in your comparison. I think I may have a hosed phone as well. I have it on cdma only and I'm constantly losing data, dropping calls, and missing calls in places I didn't before. The only roms I have flashed are Captain's 1.54.651.8, and my BareBones rom.
Captain_Throwback said:
I think you were trying to do *#*#4636#*#* to access the Menu. The EPST command would be ##3282#.
Click to expand...
Click to collapse
Thanks when I saw people posting *#*#4636#*#* I stupidly assumed they were trying to get past some HTML issue with ##. *#*#4636#*#* works !!
Turns out when you use the Google Play app called "Advanced Signal Status" when you click "Advanced" it brings up the same Menu as *#*#4636#*#*.
I didn't realize it was bringing up something built into the phone.
Any way,
It looks like on HTC Max it was *#*#3282#*#* which does not exist on HTC One (M8). You have to use ##3282# but that does not offer the same Band settings that HTC Max has with *#*#3282#*#*.
Just a quick reminder that Questions go in the Q&A section.
metalfan78 said:
I'd be interested in your comparison. I think I may have a hosed phone as well. I have it on cdma only and I'm constantly losing data, dropping calls, and missing calls in places I didn't before. The only roms I have flashed are Captain's 1.54.651.8, and my BareBones rom.
Click to expand...
Click to collapse
When and how often have you:
Updated Profile?
Changed Firmware?
Changed from factory PRL?
I think my problems may have started after I flashed Captains Firmware for OTA (which I got the link from you ROM thread).
I'm not saying it was, but it was around that time. It may have been something to do with PRL's but those are usually harmless and very revertible.
I'm 99% sure I was ok on your ROM with Stock Firmware. Except for Roaming Guard on and locked out. Not sure if that is an early symptom of problems though.
Some things in firmware (on past phones) are not revertible (ever !!!)
Your symptoms sound a lot like mine. I only get good 3G in locations where I used to get good 4G. And I get no 4G at all now.
My phone generally works but many calls go to voice mail or get dropped. Or end up being one way (one of us can't hear the other).
I think it's one of these:
Band issue (disabled or low priority)
Some sort of ID issue that got lost (like a lost security Key)
Some of Power Saver issue (i.e. Extreme Power Save kicking in when it shouldn't)
The reason I mention power is it does this.
WIFI On
Running "Advanced Signal Status"
All looks ok.
Shut off WIFI and things go nuts.
EVDO (data) RSSI Signal: drops to -120db (0%)
Then network type switches to 1xRTT from eHRPD.
It's like the extreme power saver is on. Which, guess what, OTA firmware was supposed to enable !!!
I have tried disabling it in settings. But I think something is haywire.
This is what extreme power save does. And came with the OTA update.
QUOTE: Basically it shuts down all connections but still allows phone calls and texts to come through. You can manually refresh e-mail if you want — but only in HTC's e-mail app. Your smartphone essentially is turned into a dumb phone. And to make sure you don't cheat and try to actually make it do things, the M8 gets a new home EXTREME home screen, with shortcuts to the Phone, Messages, Mail, Calendar and Calculator apps. To exit EXTREME mode, you'll need to hit the dedicated "Exit" button.
HTC says that with only 5 percent battery remaining, you can eke out 15 hours in this EXTREME mode. On a full battery? It'll last something like a dozen days. We'd consider this to be more of an emergency mode than EXTREME, however. END QUOTE
It sure feels like this is what my phone is doing. I think it's stuck on Extreme Power Save mode (in the RADIO only).
I flashed the firmware twice, updated prl many times, never changed prl. Sounds like same symptoms.
metalfan78 said:
I flashed the firmware twice, updated prl many times, never changed prl. Sounds like same symptoms.
Click to expand...
Click to collapse
I highly suspect it's not PRL. When you say "update prl" I assume you mean from settings -> system update menu.
I suspect firmware. Of which there is nothing available to go back to.
Can you get 4G?
I rarely get 4g, it hasn't been fully implemented where I am. I got it on my gs3 only sometimes. And yea, updated prl through settings
---------- Post added at 08:58 PM ---------- Previous post was at 08:18 PM ----------
I'm definitely going to a Sprint store. I was just on Sprint chat and they confirmed it is not network related but a defective device. Dammit.
This is what extreme power save.came with the OTA update.
HTC/Sprint removed the band priority section from the menus in the Max so it's either hidden deep OR it's not there and Sprint is controlling what band you actually use on their end which is highly possible....
Sent from my 831C using Tapatalk
sgt. slaughter said:
HTC/Sprint removed the band priority section from the menus in the Max so it's either hidden deep OR it's not there and Sprint is controlling what band you actually use on their end which is highly possible....
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Ahh, thanks for the info. I think that's what is messed up on my phone some how. Some Key or ID so it knows the appropriate ones to pick.
I've been switching back and forth on firmware and flashing mainly between Viper Rom and Bad Boyz H/K Rom without any issues at all. I had one issue where I couldn't get data or roam, I temporarily fixed by flashing some stock files, but since a clean install all has been well. I've updated profile and prl quite a few times without any issues so far.
I don't get lte at home, but it worked great in Indianapolis over last weekend. Just thought I would share the info.
Also s-off and super cid if that helps any.
dazednconfused said:
I've been switching back and forth on firmware and flashing mainly between Viper Rom and Bad Boyz H/K Rom without any issues at all. I had one issue where I couldn't get data or roam, I temporarily fixed by flashing some stock files, but since a clean install all has been well. I've updated profile and prl quite a few times without any issues so far.
I don't get lte at home, but it worked great in Indianapolis over last weekend. Just thought I would share the info.
Also s-off and super cid if that helps any.
Click to expand...
Click to collapse
That's interesting you lost Data / Roam and managed to got it back. Perhaps if I had put the dialer on like you did at that first problem I would have got it back too.
So you are running H/K firmware as well?
I've made it as close to stock as I could including recovery. Went to 4G area (where I can get 3G). Factory Reset (from boot loader), Redid Activation, Updated Profile/PRL etc. All worked (albeit slowly).
But still no 4G and no 3G when in normally 3G only areas.
Then I tried running H/K RUU back to back twice. Still stuck.
I may try RUU one more time, then try reactivate/profile/prl again in the 4G area.
Is there any need to change hboot? I have left what the H/K RUU put on there sometimes and other times used the one posted here that removes the red unlocked text etc.
The only thing I've messed with on hboot was the mask to remove the tampered text and red text on boot screen.
Yeah I was the one that sent you the message about losing mine until I flashed stock phone apk. But you said it didn't work for you though. But after I did a clean install of the Rom I haven't had any more issues luckily. Hopefully your replacement will work a lot better for you. Maybe just got a bad phone hopefully.
Yes I'm back on H/K firmware again. I went back to old firmware when I flashed viper a few days ago.
Sent from my 831C using XDA Premium 4 mobile app
dazednconfused said:
The only thing I've messed with on hboot was the mask to remove the tampered text and red text on boot screen.
Yeah I was the one that sent you the message about losing mine until I flashed stock phone apk. But you said it didn't work for you though. But after I did a clean install of the Rom I haven't had any more issues luckily. Hopefully your replacement will work a lot better for you. Maybe just got a bad phone hopefully.
Yes I'm back on H/K firmware again. I went back to old firmware when I flashed viper a few days ago.
Sent from my 831C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe I need a round of Viper to fix it
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.