Related
I have a Verizon galaxy tab. During the installation of CWM, my tab was locked up.
I used the recovery image that was mad by Clockworkmod during the process to get back to where I had started. When doing so, I ended up with no gps or 3g functions. The airplane mode is always on, and cannot be turned off.
I have tried installing a stock rom for the US verizon tab, with the same result, no 3g or gps and airplane mode locked on.
I am not sure what got lost in the recovery, and have not been able to find a answer in any searches I have done.
Any help on getting these functions back would be appreciated.
Same issue with Sprint Tab
I had the same issue with my Sprint Tab after installing a basic "Relax and Sleep" app. I fought it for 5 days with the help of Samsung and Sprint. We master reset and data wiped. We tinkered with multiple settings under the secret codes. In the end, Sprint said that they don't cover or service the device. They refused to swap out the device or do anything. Samsung said that I had to send it to them to repair and they would return it in 5-10 business days.
After multiple phone calls, I sent an email to every corporate email address I could find at Sprint. If I hadn't bought my Tab at a Third party vendor (Radio Shack), Sprint was willing to let me out of my contract. In the end I had to settle for 2-3 weeks without my 35 day old toy and a one month credit.
If you find a solution or the root of this problem, I would love to know.
What do you see when you type *#1234# into the phone dialer?
No phone dialer on a verizon tab, so I can't enter that.
Still looking for help in understanding what turned my radio off and how I can get it back.
Some additional information.
I reflashed the stock rom again to my tab. After doing so, I proceeded to re-download some of the apps I had on prior to the flashing. One of these is Z4root. When I opened the app to root the tab, it said the tab was already rooted.
This makes me wonder, is there any area of the file system that is not getting touched when I flash the new rom to the tab? If so, is this where the problem I am having with the radio being off, located.
Any thoughts?
Wi-Fi Calling is not working at all on my stock s7. Is anyone else experiencing this? Getting enablement error. Spoke with sprint tech support who is stumped and now escalating up to higher level team.
Rest of phone (including wifi and hotspot/tethering) working as it should.
Saw one post about disabling Bluetooth and BT share. tried that with no improvement.
-Josh
What kind of testing would help?
I have never used this before, so keep it simple, lol
I have the same problem. . They told me, after escalating, that it was am account code error. . I am trying now to enable. . Update it works now after whatever account coding they updated
cwb1231 said:
I have the same problem. . They told me, after escalating, that it was am account code error. . I am trying now to enable. . Update it works now after whatever account coding they updated
Click to expand...
Click to collapse
That sounds promising.They have called me three times to keep escalating. Any chance you would PM me your #. I can ask them to look at your acct to figure out how to fix mine.
Also if you have air rave try turning that off
cwb1231 said:
Also if you have air rave try turning that off
Click to expand...
Click to collapse
I didn't have any problem with the Airrave and my S5 using Wi-Fi calling.
I think I had to do that sometimes because the phone was trying to use both or maybe just to eliminate that possibility
Anyone have a solution for broken Wifi calling. I tried everything I could find including calling Sprint. Running the latest Sprint S7 update, was working before the phone updated. Really not looking forward to do a hard reset.
It's a problem with the data code on your account.Will need tech suport to fix. They are having issues with s7 not carrying code over correctly.
Thanks for the feedback, do you mean my Data plan is not correctly assigned to my phone. Ill probably have to hold the Sprint tech supports hand to get it going.
No its the actual billing codes for your account and how wifi is coded on it.
No luck, was on the phone with Sprint for almost an hour. They made a Ticket, said said I needed to take my phone to a repair center
I have to tell you after the security update it reset my pattern lock and i ended up with factory reset because the Samsung website unlock feature isn't set up for the s7. Had to use Google website and my Google account to restet. Good luck
cwb1231 said:
I have to tell you after the security update it reset my pattern lock and i ended up with factory reset because the Samsung website unlock feature isn't set up for the s7. Had to use Google website and my Google account to restet. Good luck
Click to expand...
Click to collapse
I know what you mean. Luckily I had fingerprint unlock working cause my pin unlock broke after the update. Hoping for a work around cause I got my phone setup just right. Is there a backup I can do that will restore everything exactly the way I have it now (except Wifi calling of course)? I had titanium backup years ago but it was a pain back then.
WiFi Calling
I have the same issue with my S7 with the enablement error. I have been on the phone with Sprint for over 1 hr with no help - they state it is a Samsung software issue. I went back to Best Buy where I got the phone and exchanged it but still the same problem. I took it to the Samsung reps who were there and they also were stumped. I reached out to "advanced tech Sprint support" who stated its a Samsung issue and will not be fixed until they release a patch. I reached out to Samsung and they stated they were not aware of any issues and to send the phone to their repair center - which made no sense. I see online that some have no issues doing wifi calling so it may be luck of the draw. I think that Sprint will blame Samsung who in return will say no issue. I am going to try to exchange the phone again and hope the third time works!
Did you try a hard reset?
Check wifi calling doesn't support messaging at this time..
Chetski said:
I know what you mean. Luckily I had fingerprint unlock working cause my pin unlock broke after the update. Hoping for a work around cause I got my phone setup just right. Is there a backup I can do that will restore everything exactly the way I have it now (except Wifi calling of course)? I had titanium backup years ago but it was a pain back then.
Click to expand...
Click to collapse
It only recognized my fingerprint a couple times then after power off it wouldn't. Also found out find my mobile isn't set up by Samsung for s7 yet, if ever. . I use nova launcher which allows you to save your homescreen and widget and folder setup. I use helium to back up apps and data. Restore was only really annoying not horrifically annoying. Don't forget to back up your Samsung account settings and take your sd card before you go the Google reset route. . The most help I got was the Samsung rep at best buy
Sent from my SM-T330NU using XDA-Developers mobile app
Thank you, that's a lot of great information.
I had 4 reps tell me to bring it to store for repair, did hard reset etc.... got up to advanced tech support before guy called me and said "fixed the problem, go ahead and try"and worked fine after that.
Hello,
So I recently had my phone sent to repair for the Pink line issue. I activated an old htc one while I waited for my s7 edge to get back. Once it got back I activated the edge again, and now whenever I turn on wifi calling I am getting enablment error? "we are unable to process your request at this time, please power cycle the device and try again" Anyone have this happen? If so how did you fix it? Have tried wiping, updating prl/profile. reverting from beta to stock, nothing seems to work.
Robisgnarly said:
Hello,
So I recently had my phone sent to repair for the Pink line issue. I activated an old htc one while I waited for my s7 edge to get back. Once it got back I activated the edge again, and now whenever I turn on wifi calling I am getting enablment error? "we are unable to process your request at this time, please power cycle the device and try again" Anyone have this happen? If so how did you fix it? Have tried wiping, updating prl/profile. reverting from beta to stock, nothing seems to work.
Click to expand...
Click to collapse
Same here. I deactivated my S7 Edge and went back to my Nexus 6. Then I went back to my Edge and WiFi calling has not worked since. I actually opened a ticket with Sprint and later talked to 2 different engineers......that was almost a year ago, many factory resets and ##72786# as well. I still have the entitlement errors.....it's pretty sweet lol. Please let me know if you figure it out.
D
Is anyone having this issue.
I upgraded to android 8.0 and no longer able to get any Verizon LTE service no matter what location I am in. I get frequent notifications stating I am Roaming and my phone is not rooted and the bootloader was locked, yet Android Pay Pop ups stating it cannot work on my 6p because my phone is either rooted or the bootloader is unlocked.
I flashed several different images to no avail.
Advice?
locolbd said:
Is anyone having this issue.
I upgraded to android 8.0 and no longer able to get any Verizon LTE service no matter what location I am in. I get frequent notifications stating I am Roaming and my phone is not rooted and the bootloader was locked, yet Android Pay Pop ups stating it cannot work on my 6p because my phone is either rooted or the bootloader is unlocked. I flashed several different images to no avail. Advice?
Click to expand...
Click to collapse
Reset Network settings reset, wipe cache partition. When you say you flashed images, do you mean sideloading OTAs.... or are you unlocked and using full images? Your post led me to believe you were getting erroneous messages about being rooted/unlocked (meaning you were not).
v12xke said:
Reset Network settings reset, wipe cache partition. When you say you flashed images, do you mean sideloading OTAs.... or are you unlocked and using full images? Your post led me to believe you were getting erroneous messages about being rooted/unlocked (meaning you were not).
Click to expand...
Click to collapse
Tried it all.
I installed several full factory image versions, locked the boot-loader and then started up the phone. With the boot-loader locked and phone not rooted Android Pay still gave me the error that my phone is running a custom ROM, the boot-loader is unlocked or the phone is rooted.
I have also installed several OTA images and none of the problems I mentioned in my earlier post went away. The only way for me to get Android pay to work is to unlock the boot-loader and root the phone with magisk. However, I still get intermittent Roaming notifications, intermittent signal lost and no LTE whatsoever.
Today:
I called Google and and did 45mins of troubleshooting, the final thing we did was reset my phone and then the agent acted helpless when nothing resolved the issue.
I called Verizon did 30 minutes of troubleshooting with them, reset network setting about 100 times, turned off my phone so that they could re-provision on their end. Turned the phone on and got LTE signal for approximately 60seconds. Then it went back to 3G, then no signal and then the dreadful roaming notification every few minutes.
Are you using the stock recovery or TWRP? And when you installed factory image did you do it through your computer using flash all? Or did you just install the factory image? Personally what I would do if wipe everything out and use your computer to install the latest factory image using the flash all script. So you are completely stock then relock the bootloader. Then you should be completely up to date with modem bootloader recovery vendor and rom. Your lte issue sounds like a modem problem possibly. And the September security patch broke safety net check and therefore Android pay. That build ended in.017. there is a new one up that fixes those issues and I think also the issue with the phone choosing mobile data over WiFi when it should be choosing wifi over mobile. That build ends in.019. try installing that build like I said above. Good luck
mojorisin7178 said:
Are you using the stock recovery or TWRP? And when you installed factory image did you do it through your computer using flash all? Or did you just install the factory image? Personally what I would do if wipe everything out and use your computer to install the latest factory image using the flash all script. So you are completely stock then relock the bootloader. Then you should be completely up to date with modem bootloader recovery vendor and rom. Your lte issue sounds like a modem problem possibly. And the September security patch broke safety net check and therefore Android pay. That build ended in.017. there is a new one up that fixes those issues and I think also the issue with the phone choosing mobile data over WiFi when it should be choosing wifi over mobile. That build ends in.019. try installing that build like I said above. Good luck
Click to expand...
Click to collapse
I wiped DATA so there were no files on my phone.
Downloaded july,august,september factory images and flashed, locked bootloader and tested each image to no avail. I saw the build on the google forum for 019 so i flashed that as well and same sh:silly:t different day.
Last thing I did was to flash 7.1.1 and that did not resolved my problems. Got the OTA notification to install 8.0 hoping all my problems might disappear but they did not.
It has been an hour and LTE seems to be working again
I have a 5X on Project Fi and my 6P is on Verizon(the phone that is having problems).
As a last resort tonight I swapped SIM Cards and after a few minutes the Fi SIM in the 6P showed LTE service. (Maybe proof it was not the phone....??? who knows)
It took alot longer but my Verizon sim then showed LTE service on my 5X which is running Oreo btw. (Baffled at this point)
I placed the SIM cards back in their original phones and LTE is functional on both. On my 6P I enabled WIFI, downloaded data, toggled WIFI, rebooted, ran several speed test and the 6P still shows LTE and I haven't seen the dreadful roaming notification as of this message.
I guess problem solved. Now to install Magisk to get AP working.
Wow that is odd. The one thing I have noticed with 8.0 on my 6p on fi is sometimes I lose data when I'm out and the phone loses wifi and switches back to lte. I have to reset the phone to get lte back.
Thank you so much for posting this issue. My Nexus 6P was doing the same thing after 8.01 October security update. Tried everything, same as you listed. I found your post and recalled that during my initial setup I had to put my wife's Verizon SIM into the 6P due to the same issue occurring. I tried it again this time but it failed, issue persisted. So, based on your post, I got a Project Fi SIM for $30 (1 month) and just tried it again. Powered down, put in Fi SIM, power on, activated Fi (with new phone # for new line... will be cancelled if needed...), and got LTE without issues over Project Fi. Then, I did Network Settings reset, reboot, and powered back up. No issues with Fi.
So, to the point now. I put the Verizon SIM back in the 6P and BAM, full LTE, no issues. Whatever the non-Verizon SIM does to the phone internal settings I have no idea, but I can tell you that it was not a fluke that your process worked. The exact same thing worked for me.
Hope this helps anyone else with the same issue - you need to install a non-Verizon SIM, get LTE going, and then put the Verizon SIM back in.
Thanks again.
JT
Just my 2 centers here for anyone else in this quagmire...
I had same issue. I've got a Nexus 6p on which I dirty flashed an 8.1 update of ABC Rom over an earlier 8.1 version of ABC Rom. After that, the issues began. At boot, I'd be on 3g and if I toggled airplane mode off and then on, I could get LTE for about 10 seconds. However, it would then drop back to 3g. I tried everything, as is stated above: revert to stock, older radio images, different SIM... nothing worked. I read about people manually configuring their APNs. However, I've got a Verizon SIM, so that option was gone.
Anyway, after reading this post, I got the idea that I might be able to mimic the solution without buying a Project Fi SIM that I don't want.
Here's what I did:
Open the Phone's Testing Settings by dialing: *#*#4636#*#*
Tap "Phone Information"
Scroll down and set the "VoLTE Provisioned" toggle to the "on" position.
Then, toggle airplane mode on and off.
Profit!
I'm not sure if this solution has any parallels to the solution that uses a project Fi SIM for a brief moment. However, I speculate that it may.
At any rate, I hope this helps someone else with this issue.
UPDATE:
It turns out this method is more of a work around at best. At first I noticed that I had to toggle airplane mode once after a reboot. That didn't seem too difficult. However, I then discovered that I could no longer make calls. Switching the VoLTE Provisioned toggle back off fixes the calling issue, but puts me back on 3G.
Uggg.
locolbd said:
I have a 5X on Project Fi and my 6P is on Verizon(the phone that is having problems).
As a last resort tonight I swapped SIM Cards and after a few minutes the Fi SIM in the 6P showed LTE service. (Maybe proof it was not the phone....??? who knows)
It took alot longer but my Verizon sim then showed LTE service on my 5X which is running Oreo btw. (Baffled at this point)
I placed the SIM cards back in their original phones and LTE is functional on both. On my 6P I enabled WIFI, downloaded data, toggled WIFI, rebooted, ran several speed test and the 6P still shows LTE and I haven't seen the dreadful roaming notification as of this message.
I guess problem solved. Now to install Magisk to get AP working.
Click to expand...
Click to collapse
Hey is ur 6p still running well with LTE? I did that with a att SIM card and my 6p read as a att SIM so I then put my Verizon Sim back in and it read Verizon LTE but then after like half an hour it changed back to roaming and 3g. I went to Verizon to get a new sim card but that didn't do any help at all. I would like ur feedback if possible. Thank you
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
j2t0621 said:
Thank you so much for posting this issue. My Nexus 6P was doing the same thing after 8.01 October security update. Tried everything, same as you listed. I found your post and recalled that during my initial setup I had to put my wife's Verizon SIM into the 6P due to the same issue occurring. I tried it again this time but it failed, issue persisted. So, based on your post, I got a Project Fi SIM for $30 (1 month) and just tried it again. Powered down, put in Fi SIM, power on, activated Fi (with new phone # for new line... will be cancelled if needed...), and got LTE without issues over Project Fi. Then, I did Network Settings reset, reboot, and powered back up. No issues with Fi.
So, to the point now. I put the Verizon SIM back in the 6P and BAM, full LTE, no issues. Whatever the non-Verizon SIM does to the phone internal settings I have no idea, but I can tell you that it was not a fluke that your process worked. The exact same thing worked for me.
Hope this helps anyone else with the same issue - you need to install a non-Verizon SIM, get LTE going, and then put the Verizon SIM back in.
Thanks again.
JT
Click to expand...
Click to collapse
Hey is the 6p still working well for you? LTE? I been following ur steps but I don't have project fi and I used my friends att SIM to kinda reset the network and I also reset the network too but it went back to 3g and roaming. Any help would be awesome. I don't want to have to get a new phone
Sent from my [device_name] using XDA-Developers Legacy app
reply to divineazn716 (won't let me quote for some reason)
Hello. I have not had any issues with the 6P since posting this. I honestly can't explain why the method posted earlier works, there does not seem to be a visible change in the user accessible settings.... so i don't know if i can help you any further from a technical standpoint. I'm not sure why the Verizon SIM didn't fix it the 2nd time, in my case. Something to do with the internal calibration of the LTE antenna (i'm guessing).
If you're willing to go this far, a factory reset of the phone, then ATT SIM might be an option. I HAVE NO IDEA IF THIS WILL WORK, so take that advice with 'a grain of salt'. Something to consider if you don't mind resetting the phone but don't/can't get a Fi account.
I can say that it was worth the $30 to me for a Fi account since it fixed it, but maybe more importantly the knowledge that if it happens AGAIN I should be able to fix it.
I know that wasn't super helpful but that's been my experience since the post.
(unrelated, but since you're a 6P user you may find helpful, I had the dreaded early battery shut down and it got so bad it almost bricked my phone. I got a new battery by sending it to Huawei customer service and it works like a champ now. Better than when it was brand new, from a battery standpoint.)
j2t0621 said:
reply to divineazn716 (won't let me quote for some reason)
Hello. I have not had any issues with the 6P since posting this. I honestly can't explain why the method posted earlier works, there does not seem to be a visible change in the user accessible settings.... so i don't know if i can help you any further from a technical standpoint. I'm not sure why the Verizon SIM didn't fix it the 2nd time, in my case. Something to do with the internal calibration of the LTE antenna (i'm guessing).
If you're willing to go this far, a factory reset of the phone, then ATT SIM might be an option. I HAVE NO IDEA IF THIS WILL WORK, so take that advice with 'a grain of salt'. Something to consider if you don't mind resetting the phone but don't/can't get a Fi account.
I can say that it was worth the $30 to me for a Fi account since it fixed it, but maybe more importantly the knowledge that if it happens AGAIN I should be able to fix it.
I know that wasn't super helpful but that's been my experience since the post.
(unrelated, but since you're a 6P user you may find helpful, I had the dreaded early battery shut down and it got so bad it almost bricked my phone. I got a new battery by sending it to Huawei customer service and it works like a champ now. Better than when it was brand new, from a battery standpoint.)
Click to expand...
Click to collapse
Tea I bought a new battery on eBay for 10 and got it replaced and it's running awesome. Are you on a custom rom? Just wondering what else I can try to fix this. It's weird while on the att it worked fine with LTE. I'm thinking about getting a fi acct thought
Sent from my [device_name] using XDA-Developers Legacy app
I had this same exact issue... I'm on Verizon and I was running FireHound ROM, which I loved btw, but every time I restarted the phone/toggled airplane LTE would pop up for 30 seconds and I would be stuck on 3G. Huge bummer but I found this to be an issue on every current custom ROM. Defeated and abused I ended up returning to 100% stock, unrooted and locked bootloader, full LTE capabilities now. I did end up buying a new SIM which helped with some of the connectivity issues I was having before granted my original sim was cut twice and I had it for many many years. Try going 100% back to stock, replace your SIM(most places cost about $10) and you should be good to go. I can only chalk this up to be an issue with source provided to developers but I'm not sure where the discrepancy lies for DEVS that isn't consistent with a stock instal...
Tried all these ROMs:
FireHound
ABC
Resurrection Remix
DARK ROM
Cortex - Uneffected by the LTE issue but is a dead ROM as of now and is on a different vendor.
k1ll3ry0 said:
I had this same exact issue... I'm on Verizon and I was running FireHound ROM, which I loved btw, but every time I restarted the phone/toggled airplane LTE would pop up for 30 seconds and I would be stuck on 3G. Huge bummer but I found this to be an issue on every current custom ROM. Defeated and abused I ended up returning to 100% stock, unrooted and locked bootloader, full LTE capabilities now. I did end up buying a new SIM which helped with some of the connectivity issues I was having before granted my original sim was cut twice and I had it for many many years. Try going 100% back to stock, replace your SIM(most places cost about $10) and you should be good to go. I can only chalk this up to be an issue with source provided to developers but I'm not sure where the discrepancy lies for DEVS that isn't consistent with a stock instal...
Tried all these ROMs:
FireHound
ABC
Resurrection Remix
DARK ROM
Cortex - Uneffected by the LTE issue but is a dead ROM as of now and is on a different vendor.
Click to expand...
Click to collapse
I will give this a try this evening
Sent from my [device_name] using XDA-Developers Legacy app
bleh im back to stock unrooted and locked and my signal is still crap. i guess i have to buy a new phone.... =*( i loved this 6P
Sorry to hear that. I'm just running stock android.
My S10+ will not detect the day one OTA update. I check every day and it says software up to date even thought its still on G975USQU1ASAT. AT&T says to contact Samsung and Samsung says to contact AT&T. Anyone else had this problem or have any idea how to fix it? I've already tried factory reset, clearing cache and data on the updater apps with no luck.
Do you need to be connected to WiFi or have a certain battery level? Try charging to 100% and connecting to WiFi then manually search for the update.
What I had to do is go into the date and time and shut off auto time update and manually set it 2 days a head then mine found the update.
loffer said:
My S10+ will not detect the day one OTA update. I check every day and it says software up to date even thought its still on G975USQU1ASAT. AT&T says to contact Samsung and Samsung says to contact AT&T. Anyone else had this problem or have any idea how to fix it? I've already tried factory reset, clearing cache and data on the updater apps with no luck.
Click to expand...
Click to collapse
Two options:
1) Borrow someone else's sim or ask At&t for another
2) Download the S10+ OTA and update via SD
Did you put the sim that came with it in? I used my old sim and had the same problem till I changed the sim card.
Sorry for the late response and thanks for the suggestions. Just returned from vacation so I will try the suggestions. Also yes I used the sim they sent me. I suspect something got messed up in the sim provisioning as I came in as a new line then ported my number in. I will try putting my wife's sim in and report back. Thanks again!
Mine wouldn't detect an update. I'm only using mine on wifi as this one is just a spare phone for now.
To get the update though I needed to put in my att dim and put the date a week in the future. That's the only way I was able to actually get it to check the server.
I'm having the same exact problem. I purchased my S10+ directly from Samsung, but it was the AT&T model. I've been stuck on the ASAT baseband with the Feb 1 Security patch since day 1. I've been on the phone/chat with AT&T for the last 3 days. Each time they've promised that they have pushed the update to my phone, and every time I check, I get the "Software is up to date" message. I just tried setting the date to next week, restarted, and checked for the update..still nothing.
The same thing happened to me with my Note 8, but I was able to get around it using ODIN. I've told AT&T that I'm not paying my bill until this is resolved (like that's gonna do anything). Anyway, I'm at the breaking point on this, and not getting anywhere fast.