Develop Bugs

Emergency Calls Only...

Hi,
last night this problem just came out of nowhere. I was texting and calling fine like hour before I noticed it happen, but whenever I try to call it hangs up, and whenever I try to text it tells me to try again when service is available. On the lock screen it tells me "Emergency Calls Only", but sometimes it shows "Virgin" I'm with Virgin Mobile Canada, but still doesn't work. I've tried the following:
1. Pulling out battery and putting it back in.
2. Nandroid restore to when I first rooted it, and when it was working fine.
3. Take out SIM card, battery, and memory stick
4. Putting it into airplane mode and disabling airplane mode about 30 seconds later.
5. Unrooted to original Bell Stock Rom image from a thread and now have normal recovery
6.Data/factory reset
The only thing I do have a possible lead on is that yesterday I created a recovery tar file, from a recovery image I got from cwm website under AT&T, thought it was also for Bell (Model wise) as well, so don't know if that's the case, does that have to do with anything? I'm back to stock recovery and rom and from a thread here: http://forum.xda-developers.com/showthread.php?t=1739426 and downloaded the Bell/Virgin image, and flashed with Odin, I am back to stock, but still did not fix issue. It says Virgin on the top sometimes, and sometimes back to "Emergency calls only" could the recovery flash have changed radio or something? I also did do a restore before I flashed the new recovery and when phone was being normal just before unrooting but that also didn't work. Now I am unrooted and not on custom recovery. But still no service. Most of the time the service is 1 bar, but even when it's on 5 for like 10 seconds, it still doesn't work. Is it me or my carrier? I also noticed that even when the signal shows full strength it tells me "Emergency Calls Only". Thanks for the help.

I'd call Virgin and ask if your service was interrupted for any reason.

Yeah I'm going to do that, but I just looked at the IMEI number on the back of the phone, and looked at it in settings, but it did not match the number it had at the back. It just says 0 in the phone settings. Does that have anything to do with it? I wanna know if this is has anything to do with that first before calling.
EDIT: Okay so I did some research and yes that is apparently the problem, so I rerooted to custom recovery, and followed this guide: http://forum.xda-developers.com/showthread.php?t=1801997 my IMEI is back, and matches, and it says "Virgin" now at the top of my lockscreen, but still, I can't send messages or call. Did the deleting of IMEI also delete something else I should restore? Or is it something on their side? I am connected to Virgin Mobile, but the connection is extremely weak, and does not complete any calls or texts. There's also "IMEI SV" under settings and it says "01" is that an issue?
EDIT 2: Nevermind I just had to follow post 3 after fixing IMEI in that thread I linked and it worked! In case you researched and got here. Follow thread I linked up.

rise chicken
I'd like to resurrect this thread for a moment. Papaniz's problem is exactly like mine, same carrier & country.. but the link is dead.. any idea what the process was or where another link might be? Thanks Guys

tutorialhedz said:
I'd like to resurrect this thread for a moment. Papaniz's problem is exactly like mine, same carrier & country.. but the link is dead.. any idea what the process was or where another link might be? Thanks Guys
Click to expand...
Click to collapse
The thread was remove to avoid illegal problem. You'll most likely have to look somewhere else to recover your IMEI if flashing stock firmware doesn't fix it.

[Q] Lost IMEI now stuck in boot loop after ODIN to stock

Hello,
I'm having a lot of difficulty getting my Note II (SGH T889V) in working order . I'll try to explain the situation in an organized way. Thank you for your time and kind help!
Background
I have a Note 2 from Wind Mobile in Canada - SGH T889V. I got it 2.5 months ago. It was rooted, was running TWRP and I only loaded one ROM, flashed once, on it - 4.1.2 modified touchwiz ROM. Never once had an issue. The ROM was super stable and in great working order.
I got it unlocked about 2 weeks ago because I was visiting the states. When I got to the states, I put in a T-Mobile sim card which was working great for a few days. One afternoon during my vacation I was having slow data issues, so I thought to change the modem/radio from a Wind Mobile radio to a T-Mobile radio. That gave me 4G data speeds but killed my calls. So I tried to go back to the Wind Radio and that had my phone complaining that there was no SIM card. I went back to the T-Mobile radio and I got calling back but only 2G data.
My IMEI was corrupted - it showed up as zero. I left the T-Mobile radio on the phone when I got back. My home network wouldn't recognize me and thought I was still roaming.
Attempted Fixes
Tried a basic factory reset. Tried a different ROM. Tried wiping all internal data.
I got home and tried to flash to stock ROMs found on XDA for Wind Mobile phones. That didn't solve the issue. The IMEI remained null. The phone would reboot automatically every few minutes unless I turned Airplane Mode on. I figure the phone was looking for a signal and couldn't because of the IMEI problem.
So I looked around on the net and found a link about injecting the IMEI back using QPST (http://forum.xda-developers.com/showthread.php?t=1206275) but I couldn't get the program to detect my phone so I gave up and thought I could just get my binary count to 0 and stock and I'll just take it back for warranty.
I tried Triangle Away but I couldn't get the counter to go to 0 even with stock ROM and recovery. So I thought I would take it to a cell repair shop locally. I took it there and all they did was cause an issue on the phone to make it appear that KIES firmware upgrade failed so that it would be repaired under warranty. You would see a emergency firmware upgrade error the minute you turned the phone on. However, download mode still showed the custom binary count at 1, they didn't get it down to 0.
I spoke with my carrier and with Samsung anonymously, they said the counter would be an issue if I sent it in.
I came back home and tried doing the following, with the hopes of trying Triangle Away again:
1. Installed TWRP via ODIN and ran the restore on the backup I created in TWRP when I first got the phone. I restored everything including EFS. Phone boots to the stock samsung rom but it would restart automatically every few minutes. Even with Airplane mode on, it would still reboot on it's own.
The KIES error message doesn't appear anymore.
2. Went back to ODIN. It was getting stuck on SYSTEM in ODIN version 3.07 when flashing a stock rom. So I switched the USB port on my computer and used ODIN 3.04 then the flashes went through properly with no hang ups.
So I tried to flash a prerooted (http://forum.xda-developers.com/showthread.php?t=1975560&highlight=wind) stock ROM
and
also a basic stock ROM (http://forum.xda-developers.com/showthread.php?t=2061031), along with a stock recovery
Both just get stuck in a bootloop. I tried going to the stock recovery and wiping data, cache, factory reset several times. No luck - still boot loops. Wont go into the ROM.
I did not try "Re-partition" in ODIN. I'm not sure if that'll hard brick the device but maybe that way I can repair all of the partitions? - http://forum.xda-developers.com/showthread.php?t=860432&page=2
__________
Im hoping to get back into a prerooted ROM or stock ROM to try this Triangle Away Method - http://forum.xda-developers.com/showthread.php?t=2272966 to get the custom binary down to zero.
I tried to use the Triangle Away ODIN method but it doesnt go through in ODIN, it just gets stuck.
If I can get into the ROM without it boot looping or rebooting automatically- I think I can fix my IMEI like this person did - http://forum.xda-developers.com/showthread.php?t=2145967
Outcomes Im hoping for
To stop the bootlooping/ automatic reboots, then
1. To get the custom Binary count to 0 so I can send it back in for warranty to Samsung or my carrier, Wind Mobile. The binary says Samsung Official. - http://forum.xda-developers.com/showthread.php?t=2068156
or
2. To get the phone to working order so I can try this persons method - http://forum.xda-developers.com/showthread.php?t=2145967
The phone is still responding and it's still working with ODIN. It makes me think the issue is software or partition related and not hardware related per se. If it is hardware, I just want to get this phone back to Samsung but I need to unroot/clear the binary counter.
The phone has never been dropped or damaged physically. I've really babied the phone. This is my third Samsung Galaxy phone (I've had a Vibrant and S2x before this one.)
This has really ruined my week. I need my phone for work. I greatly appreciate any kind help or guidance. I know the collective genius here at XDA will be able to find a solution.
Thank you so much!

If you have flashed the tmobile modem you will now have to keep the tmobile one in order to get your phone to boot. Flashing a t889v modem will cause loops. Dont know of any way to get back to t889v modems.

Hey, don't worry, you aren't the first to experience this problem. Many users have reported that the T889V will bootloop with the T889V modem after flashing another modem. Many have also restored IMEI and service to their phones, so there is a solution. I don't have the specifics, but there are many threads about this problem with solutions. I have quickly searched for one and I believe it has everything you need to fix it.
http://forum.xda-developers.com/showthread.php?t=2119074&page=3

Byangmang said:
Hey, don't worry, you aren't the first to experience this problem. Many users have reported that the T889V will bootloop with the T889V modem after flashing another modem. Many have also restored IMEI and service to their phones, so there is a solution. I don't have the specifics, but there are many threads about this problem with solutions. I have quickly searched for one and I believe it has everything you need to fix it.
http://forum.xda-developers.com/showthread.php?t=2119074&page=3
Click to expand...
Click to collapse
Thank you. I'm going to give that a shot. I'll install CWM then install a T889 TMobile Radio to see if it boots.
I'll report back. Fingers crossed.

I had same issue... this is how I fixed it
http://forum.xda-developers.com/showthread.php?t=2274843

sniperess said:
I had same issue... this is how I fixed it
http://forum.xda-developers.com/showthread.php?t=2274843
Click to expand...
Click to collapse
Thank you all!
I got the boot loops to stop by flashing CWM recovery, then flashing a TMobile Radio.
From there, I followed the QPST instructions of installing a QCN file on the phone to reenable the AWS spectrum. Then I used the IMEI creator and NV Writer programs and I was back.
Data seems alright, getting alright speeds on Wind right now. I just found my bluetooth a little hard to hear in the car this morning.
So with this process, I should stick with a Tmobile radio from now on right? If I flash a Wind/ T889V modem it'll boot loop?
Have you guys noticed any signal or performance issues after restoring the phone this way? I'm wondering if it's worth the trouble to get the custom binary counter to clear and return this phone for warranty. Seems to be working for the most part so far.
Thank you so much again! I thought I was going to have to pay $100 to get it JTAGed.

Glad to here your back and running.
I have a t889v using it on telus, and since I am stuck on tmobile modem I get lower phone signal but never loose signal. On a plus I now get lte speeds.

First day back it seems good for the most part.
Only issue I had was Bluetooth in my car would cut out at a high rate of speed (when I was on the highway). It worked really well while I was on local roads but once I hit the highway I couldn't hear the other side at all pretty much. I had to put them on speaker to hear them. They could hear me really well, better than before when I was driving on local roads.
Never occurred in the past. Could it be a radio issue? Signal seemed okay and I was able to continue the conversation over the phone speaker on the highway.

lilroach said:
First day back it seems good for the most part.
Only issue I had was Bluetooth in my car would cut out at a high rate of speed (when I was on the highway). It worked really well while I was on local roads but once I hit the highway I couldn't hear the other side at all pretty much. I had to put them on speaker to hear them. They could hear me really well, better than before when I was driving on local roads.
Never occurred in the past. Could it be a radio issue? Signal seemed okay and I was able to continue the conversation over the phone speaker on the highway.
Click to expand...
Click to collapse
The bluetooth issue doesn't seem to be a problem anymore. Disappeared on it's own.

lilroach said:
The bluetooth issue doesn't seem to be a problem anymore. Disappeared on it's own.
Click to expand...
Click to collapse
I noticed I have serious data issues when the network goes into HSPA+ mode. I get really good data for a minute then it'll cut out totally for like an hour. I tried rebooting, tried battery pulling. It seems the T-Mobile radio doesn't interface well with Wind's HSPA+ . I had full bars but the internet wouldn't load. It was pretty non-functional for most of the day.
It works decently when it's not on HSPA+
Tried switching to a Wind modem, went into boot loops. Went back to T-Mobile radio. Should I try a different T-Mobile radio?

how to fix your T889v if you accidentally overwrite the radio
If you get stuck with no IMEI, in my case, flashed omnirom 4.4.1 t0ltetmo, which uses Tmobile radio... it killed the Wind Mobile radio... restoring form nandroid did not help.
solution:
flash omnirom t0lte (not t0ltetmo) and your problems are gone!
lilroach said:
I noticed I have serious data issues when the network goes into HSPA+ mode. I get really good data for a minute then it'll cut out totally for like an hour. I tried rebooting, tried battery pulling. It seems the T-Mobile radio doesn't interface well with Wind's HSPA+ . I had full bars but the internet wouldn't load. It was pretty non-functional for most of the day.
It works decently when it's not on HSPA+
Tried switching to a Wind modem, went into boot loops. Went back to T-Mobile radio. Should I try a different T-Mobile radio?
Click to expand...
Click to collapse

[Q] Band Handover/voice network issues

So I have been waiting patiently for the 4.3 update to roll out to me OTA with hopes that it would fix my issues but my phone has been saying download interrupted and so I have gone back to completely stock and triangle away to get my device status back to normal but it still wont let me download. When looking around for other possible causes I saw that my build number is JRO03L.I747UCDLK3 which comes up as a build number for a nexus 7, the correct build number for my att should be JRO03C. I have no idea how it got that way but I am wondering if the person who bricked it might have put the wrong version of the bootloader or some other part of the firmware on and it somehow didn't brick but is detecting a conflict and not letting me OTA. Or that is what is causing my cell network issues as well. Wanting input from a a few devs as I am not 100% sure what the first part of the build number represents.
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for tag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.

Bump
Bump!...not looking good.

madnesshero86 said:
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for Jtag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.
Click to expand...
Click to collapse
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail

Tried
View attachment 2362929
winosxbuntu said:
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail
Click to expand...
Click to collapse
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?

madnesshero86 said:
View attachment 2362929
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?
Click to expand...
Click to collapse
I think I can help, I just need to pull up some files and I might get you the software or program I used to back -up and restore my EFS folder/files
Even fix it, so plz hang in there........will report back later on

Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

madnesshero86 said:
Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
this is the software/programme i used to back-up, recover or even fix my EFS files (if they are corrupt and can be used) NV items reader writer
type it on google and pretty sure you will find something , try different links and again am sure you will find a download
have you tried flashing the new 4.3 stock firmware and modem follow this link for everything http://forum.xda-developers.com/showthread.php?t=2498233 or you can wait for AT&T to release the official 4.3 firmware and that will be 100% satified to be stable and will fix all your EFS/IMEI problems FOR GOOD :laugh:
i have the NV items reader writer software that can fix your problems but i dont know how i can share it with you without breaking any rules
ULTIMATE/final solution send it to MOBILETECHVIDEOS and will fix it like its nothing, take it to samsung and have to play some ball, or BUY A NEW PHONE
tried kernels (idont think it will make any difference) but its good to check

I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

madnesshero86 said:
I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
NV items reader writer
type exactly as it is on google or here on XDA

New Info
See new info in OP Please, and before anyone says anything I have spent half the day searching with various keywords trying to find a fix so be kind if it seems obvious to you, I couldn't find it and I did try.

Bump

[Q] No data when connected to 3g

Hey guys,
I have a really weird problem that's been persistent throughout my ownership of this phone. If my phone ever goes into 3g mode, I can't access the internet on my phone or do anything that requires data. I live in a mostly 4g area so it isn't normally an issue, but when I travel elsewhere it becomes a huge headache, forcing me to go running in search of a wifi hotspot.
I have the newest radios, and even flashed the latest RUU to reset my phone to stock. The problem is still there.
Is this an issue for anyone else, or does anyone have any suggestions as to how I can fix it? Any help at all would be GREATLY appreciated. Thank you in advance.

BABABANG said:
Hey guys,
I have a really weird problem that's been persistent throughout my ownership of this phone. If my phone ever goes into 3g mode, I can't access the internet on my phone or do anything that requires data. I live in a mostly 4g area so it isn't normally an issue, but when I travel elsewhere it becomes a huge headache, forcing me to go running in search of a wifi hotspot.
I have the newest radios, and even flashed the latest RUU to reset my phone to stock. The problem is still there.
Is this an issue for anyone else, or does anyone have any suggestions as to how I can fix it? Any help at all would be GREATLY appreciated. Thank you in advance.
Click to expand...
Click to collapse
I have the same issues regardless of what ROM I'm on. 3G is pretty iffy for me, sometimes I will get a data connection whereas some other times I don't get any data at all. I would hope that phone should say "no service" or something like that. Your best bet at this point is to try to do a factory reset to rule out any residuals from other ROMs (remember to make a backup before hand on a computer because it will wipe everything). Also take the time to update firmware
Stock Rom
http://forum.xda-developers.com/showthread.php?t=2485319
Firmware here
http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
Keep in mind sometimes the recovery can cause issues, I remember I was using specific versions of TWRP and most of the time it would work fine but other ROMs I had errors. I can't comment on Philz cause I never used it. Currently on TWRP 2.7.1.1 and so far no issues.
Lastly, the only thing I could think of is try getting a new SIM card. You want to go to the corporate stores and NOT the authorized Verizon retailers. You'll know because the authorized retailers will charge you for a new sim card whereas corporate stores do not.

AznInertia said:
I have the same issues regardless of what ROM I'm on. 3G is pretty iffy for me, sometimes I will get a data connection whereas some other times I don't get any data at all. I would hope that phone should say "no service" or something like that. Your best bet at this point is to try to do a factory reset to rule out any residuals from other ROMs (remember to make a backup before hand on a computer because it will wipe everything). Also take the time to update firmware
Stock Rom
http://forum.xda-developers.com/showthread.php?t=2485319
Firmware here
http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
Keep in mind sometimes the recovery can cause issues, I remember I was using specific versions of TWRP and most of the time it would work fine but other ROMs I had errors. I can't comment on Philz cause I never used it. Currently on TWRP 2.7.1.1 and so far no issues.
Lastly, the only thing I could think of is try getting a new SIM card. You want to go to the corporate stores and NOT the authorized Verizon retailers. You'll know because the authorized retailers will charge you for a new sim card whereas corporate stores do not.
Click to expand...
Click to collapse
Wow, thank you for taking the time to write all of that. It means a lot! I tried everything else, but I think a new sim card might do the trick. I didn't even think about that.

Signal problems after root, twrp and reflash

I'm having an issue with connectivity, please help if able.
1. used CF auto root method from this link https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862 when I went to TWRP it would say recovery is not seandroid enforcing, but would go on to TWRP anyway.
2. made backups
3. connectivity problems started. could make and receive phone calls in certain places. dropped phone calls and went straight to roaming with unstable connection.
4. reflashed stock firmware from Koop1955's post
5. noticed I still had connectivity issues even when back to stock
6. reflashed twrp and root
7. still have connectivity issues
8. not able to activate through hands free activation or dialer codes.
9. can see sprint then it goes away. will get LTE in other places
10. Any ideas or direction to how I can start to affirmatively diagnose issues?

@Saafir, I have been trying to help, but I am out of ideas. Any suggestions for him?

Tried dialer code
Saafir said:
##72786# ?
Click to expand...
Click to collapse
I tried that dialer code on it, it goes to SCRTN then reboots and goes to Hands Free Activiation where it fails all times.

Thanks
Saafir said:
Providing you have your MSL # do the ##data# menu, and make sure you have all of the LTE bands enabled. Carrier aggregation too. Other than that not sure what to recommend besides a trip to a Sprint store.
Click to expand...
Click to collapse
I have MSL code and looked at ##data#. All bands are enabled on the LTE front. Would placing a new SIM card work? or should I try going through more advanced diagnostics? The phone works and makes and recieves calls as long as i'm not in a bad spot. The thing is, there are ALOT more bad spots and it shoots me to roaming in the same area my fiancee has LTE and good reception. Same phone, same service. Any way this information can help?

One more thing
Saafir said:
Providing you have your MSL # do the ##data# menu, and make sure you have all of the LTE bands enabled. Carrier aggregation too. Other than that not sure what to recommend besides a trip to a Sprint store.
Click to expand...
Click to collapse
I had to get the phone repaired about a month ago. They placed a new daughter board completely on it. Could this affect it after flash? I had no problems with reception before root and twrp so I didnt think this would be relevant but maybe you guys know how to check if that is where this issue is coming from.

rigidframe said:
I had to get the phone repaired about a month ago. They placed a new daughter board completely on it. Could this affect it after flash? I had no problems with reception before root and twrp so I didnt think this would be relevant but maybe you guys know how to check if that is where this issue is coming from.
Click to expand...
Click to collapse
Doing a wipe via TWRP and then flashing the TAR should return the phone to stock state. Since the problem happens when you are unrooted and back to stock recovery (as well as when you are rooted and running TWRP) it seems likely that it is hardware. If I were you, I would do another wipe (System, Data and caches) then Odin the latest TAR and bring the phone back to where the repair was done. Tell them that you took the latest OTA update and the phone failed and that they need to fix it.

koop1955 said:
Doing a wipe via TWRP and then flashing the TAR should return the phone to stock state. Since the problem happens when you are unrooted and back to stock recovery (as well as when you are rooted and running TWRP) it seems likely that it is hardware. If I were you, I would do another wipe (System, Data and caches) then Odin the latest TAR and bring the phone back to where the repair was done. Tell them that you took the latest OTA update and the phone failed and that they need to fix it.
Click to expand...
Click to collapse
Thanks @koop1955 and @Saafir ill reset and bring it in, I'll check back in if that fixes it or doesnt.