Related
I assume that the U.S. cellular version of this phone is a lot like the Sprint version, so I was hoping one of you could help me.
This has also been posted on the Team US Cellular forum: http://teamuscellular.com/Forum/topic/3446-phone-cant-access-mobile-data-now-stuck-on-activating/
I had been running my phone on Liquid Smooth for a day or two now, and today I turned on and off my phone a few times because I started to run low on battery and needed the phone later. Then, when I turned it on it said I was in recovery mode and all of my widgets were off of my homescreens. Now, the phone can't connect to mobile data or wifi so I cannot make phone calls, receive text messages or go on the internet. I then proceeded to attempt to wipe the cache, dalvik cache, and factory reset the phone through Clockwork Recovery, and when the phone booted up, it still could not connect to anything and now it is stuck on "Activating..".
At this point, I just want to return my phone to normal without root and get my service back. Could anyone please help me quickly? I need to use my phone by Monday... Thanks!
Also the phone signal thing has an R next to it, if that means anything to any of you all.
The "R" stands for Roaming, to into settings - mobile data - network operators - find your carrier. Hope that helps!
Sent with my Google Nexus 7 through the XDA Developers APP.
You need to flash a stock/stock-based ROM and follow the activation through
Then you can flash back or unroot, most likely what happened is that you either A) restored data (sometime gives weird problems) or B) didn't wipe completely/enough
Dr.Molestratus said:
The "R" stands for Roaming, to into settings - mobile data - network operators - find your carrier. Hope that helps!
Sent with my Google Nexus 7 through the XDA Developers APP.
Click to expand...
Click to collapse
CNexus said:
You need to flash a stock/stock-based ROM and follow the activation through
Then you can flash back or unroot, most likely what happened is that you either A) restored data (sometime gives weird problems) or B) didn't wipe completely/enough
Click to expand...
Click to collapse
A very nice user on Team US Cellular helped me out one on one, I have managed to unroot the device and bring it back to stock through download mode, and will not have to bring it into a US Cellular store to get my number back on it. Thanks for the help!
BloodyRory said:
A very nice user on Team US Cellular helped me out one on one, I have managed to unroot the device and bring it back to stock through download mode, and will not have to bring it into a US Cellular store to get my number back on it. Thanks for the help!
Click to expand...
Click to collapse
This happened to me on sprint. They couldn't fix it and I had to exchange my phone for a new one
Sent from my SPH-L710 using Tapatalk 2
I brought it into the store today and they didn't know what to do. They factory restored the phone again and managed to get signal (the signal bar as a triangle next to it), but whenever I try to activate the phone, it tries to activate it on Verizon. I did not flash the wrong rom, I know that. Is there any way to fix it right now or do I have to wait until tomorrow until I can take it to their tech guys at a different location? Thanks.
Sprint Galaxy Nexus
4.2.1
Not rooted
I performed a factory reset on my phone yesterday due to it bogging down and being rather slow. I never did a reset after getting the 4.2.1 update so I figured it was a good time. I woke up this morning, putzed around the house, and setup Tasker again. I laid my phone down for ten minutes while I got ready for work. Whenever I tried to wake my phone and nothing happened. I tried a few more times and the screen would not wake up. I pulled the battery, hard reset, reinserted battery and the phone wouldn't turn on. Then, I wiped the contact terminals (on the battery and the phone) and reinserted the battery and the phone booted up. However, since then I have had some major problems.
1. Power button does not always work properly. I have to press it several times to sleep or wake the phone. (Okay, not major, just inconvenient and probably unrelated to the issues below)
2. No data connection whatsoever.
3. In the data usage menu, there is no longer a data toggle switch.
4. Under the Network Mode option, LTE/CDMA produces absolutely no cell signal whatsoever. I have to switch to CDMA only. (WiFi works fine)
5. Toggling airplane mode, as some have suggested, does not cause the phone to connect to mobile data. Another factory reset did not restore mobile data. Rebooting did not restore mobile data.
6. All of these problems are true before and after factory reset. No new problems were created and nothing was exacerbated as a result of performing a factory reset.
I've been from one end of the internet to another looking for solutions to this problem and I have found that many are having a similar issue but toggling airplane mode or rebooting fixes it. Not the case for me. Most also seem to be having this problem after rooting. Again, not the case for me.
Any suggestions? I would prefer to not return the phone. Purchased from Radioshack and the 30-day warranty has expired. This is my second gnex already, as the first one's charging port broke. It took over a week to get this one from another store which graciously shipped it in to my store. There's also the issue of being broke and not really being able to afford another $30 activation fee on top of the deductible for a new phone.
Why not try reflashing the stock image and updating again to 4.2.1?
Beauenheim said:
Why not try reflashing the stock image and updating again to 4.2.1?
Click to expand...
Click to collapse
Wouldn't I have to root first?
nburns1825 said:
Wouldn't I have to root first?
Click to expand...
Click to collapse
Not at all. You'd use Odin . Myself I have very spotty sprint signal in my home. Spoke to a corporate executive and they mailed me an AirRave free . Never have less then full bars 3g all around home. You should a- flash to stock using Odin following posts in sprint sextjon . b - call up and try to get an airavana.
Sent from my Galaxy Nexus using Tapatalk 2
n0ve said:
Not at all. You'd use Odin . Myself I have very spotty sprint signal in my home. Spoke to a corporate executive and they mailed me an AirRave free . Never have less then full bars 3g all around home. You should a- flash to stock using Odin following posts in sprint sextjon . b - call up and try to get an airavana.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Excellent. I will give it a shot at some point today or tomorrow and then let you know how it worked out. Thanks!
So, I restored the phone to stock. Signal is still non-existent on LTE/CDMA mode. Cannot perform Profile or PRL updates. Still no mobile data. I'm guessing hardware failure?
Also, on setup it asks for a SIM card. And at the bottom of the drop-down menu, it says "No SIM card|Sprint" or "No SIM card|No Service" depending on if I am in CDMA or LTE/CDMA.
Also, in the Status menu:
My phone number
Unknown
MIN
Unknown
PRL Version
Unknown
ICCID
Unknown
Seems a little odd to me.
Attempted fully rooting and flashing radios. No luck there either. It's also not wanting to update. Tells me my phone is up-to-date (connected via WiFi). Downloading Cyanogen now to see if it will work in the morning.
And while attempting to flash a new ROM, got the famous "can't copy anything to the device ever, under any circumstances" error.
Update: Got CM10 installed. Still "No SIM" error, no 3G, no data, no LTE. Found some more information on this No SIM error. Apparently a few others have had this same problem and in the end had to get a new phone.
Anyone know anything?
You should a- flash to stock using Odin following posts in sprint sextjon
I've been back to stock twice now. The first thing I did was flash to stock. Then I played around a bit and now I'm back to stock again.
Is there a difference between using Odin and Nexus Root Toolkit to return to stock?
Bump
Wow, one day and my thread is buried!
After battling for about a day, I got updated to JB 4.2.1, I can do profile and PRL updates again, but there is still no 3G/mobile data, and I still have zero bars on LTE/CDMA and have to use just CDMA. I am currently stock but the bootloader is unlocked, no root.
If anyone has heard any solution, please help. Also, if there's a difference between flashing to stock with Odin vs NRT, please say so.
nburns1825 said:
Wow, one day and my thread is buried!
After battling for about a day, I got updated to JB 4.2.1, I can do profile and PRL updates again, but there is still no 3G/mobile data, and I still have zero bars on LTE/CDMA and have to use just CDMA. I am currently stock but the bootloader is unlocked, no root.
If anyone has heard any solution, please help. Also, if there's a difference between flashing to stock with Odin vs NRT, please say so.
Click to expand...
Click to collapse
Try fastboot flashing your LTE and CDMA radios again. As far as I know, fastboot commands do NOT require root. I had a similar issue.
Edit: link to post with directions http://forum.xda-developers.com/showthread.php?p=39446679
Sent from my R2-D2 unit on the far side of the moon
Indeed, fastboot does not require root. I've flashed my radios several times now in various different ways. I even flashed different versions. I attempted again but with no luck. I have normal service when using CDMA but nothing on LTE/CDMA. Still no data, still "No SIM card" error.
Pretty sure I'll have to get it replaced. I've gone from stock JB back to stock ICS, rooted, CM10, back to stock ICS, rooted, back to stock JB unrooted, and flashed three different radios. I'm surprised I haven't managed to brick it yet.
UPDATE: Sprint is sending me a new phone, for free.
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
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
I started to experiment with different custom ROMs available for the d2att (now, apparently called the d2lte). My phone is using TeamWin 2.6.3.1 for recovery, I have been using it for everything. So far I have only been familiar with two certain ROMs: Cyanogenmod and CarbonROM. I have not flashed anything except for the recovery.
I complete the installation of my new ROM by first wiping cache, dalvik, data and system. My ROMs are stored on an external SD.
CarbonROM was the first one to be installed, but I found it quite buggy and unstable. I have since been using different snapshots of CM to test functionality and stability...since I plan to hang up my LG G2 and start using my SGS3 w/7200mAh battery as my daily phone. So it needs to be very reliable. I also enjoy picking with settings so the more settings the better.
So, question number #1:
When I install CM the normal way, add my APN, and select the proper mobile network mode, how come I cannot get a signal, no matter what I try? I have searched around many forums for the answer to this...many have nothing to do with my problem or are using different phones. I can confirm my SIM card works, as it was used in my LG G2. Carrier is Virgin Mobile Canada. Network mode is GSM/WCDMA Auto. It does not work with any other modes including Global.
Q #2:
If I plan on using custom KK (4.4.2) ROMs, is there anything extra I need to flash to the phone in order for the cell radio to work successfully? When I researched this, I found lots of people talking about flashing a custom bootloader, but I could not find an exact answer to my question. I would rather not brick my phone by attempting this blindly.
Q #3:
Since I am looking for a reliable custom ROM, is CM the best developer to choose? Is there a more reliable ROM out there?
Mike
EDIT: I did more reaseach on bootloaders and modem firmware and found that my bootloader is already at the most recent version. I did find however that my modem firmware was out of date, so I updated from UEMK5 to UEND3. This however did not solve my problem as I still have no service...
I am contemplating now about starting from scratch and wiping my internal storage... will this help or is it unnecessary?
For question # 1, do you have a proper imei after installing CM11? You can check it in the dialer by typing in *#06#.
For question #2, the modem must be compatible with the bootloader. Custom ROMs will only install if the phone has a compatible bootloader.
For question #2, I prefer Validus which is an AOSP-based ROM.
audit13 said:
For question # 1, do you have a proper imei after installing CM11? You can check it in the dialer by typing in *#06#.
For question #2, the modem must be compatible with the bootloader. Custom ROMs will only install if the phone has a compatible bootloader.
For question #2, I prefer Validus which is an AOSP-based ROM.
Click to expand...
Click to collapse
I have an IMEI number. That is what has me kind of confused...everything is there to show signal, it's just that it will not pick up a tower. When I throw a SIM card in it recognizes it. One thing to also mention is it pins the signal at 0, -1, or 258692378... or another outrageous number.
First things first have you followed the method of going back to a stock TW ROM, obtaining a GPS lock, and then flashed your Custom KitKat rom?
Sent from Mission Control
UnknownTroll1 said:
First things first have you followed the method of going back to a stock TW ROM, obtaining a GPS lock, and then flashed your Custom KitKat rom?
Sent from Mission Control
Click to expand...
Click to collapse
I am now on stock 4.3 firmware. I have obtained a GPS lock.
No service at all.
But... I had a funny feeling, so I went into stock android recovery and wiped cache...and voila, service!
Only problem is, I'm losing it almost constantly. The only way to fix it is by wiping the cache, but I can't keep doing that whenever I lose service.
Will I be okay to flash the custom recovery and custom ROM at this point?
Do you have the latest modem installed?
mpelley92 said:
I am now on stock 4.3 firmware. I have obtained a GPS lock.
No service at all.
But... I had a funny feeling, so I went into stock android recovery and wiped cache...and voila, service!
Only problem is, I'm losing it almost constantly. The only way to fix it is by wiping the cache, but I can't keep doing that whenever I lose service.
Will I be okay to flash the custom recovery and custom ROM at this point?
Click to expand...
Click to collapse
If you are still on the Stock TW ROM here is a method to try. It will clear most of your mobile data problems.
1. Enter the Samsung service mode by typing this code into the dial pad *#197328640#
2. Then go to Mainmenu>UMTS>Common>NV REBUILD>NV REBUILD> (Important: don't exit the menu yet!)
3. Wait 30+ sec
4. Long press power button and select "Restart / Reboot"
5. Now check your GPS from any software that may use GPS like "Maps" or "GPS Status"
Credit: S3Rx ROM Development Thread.
EDIT: Afterwards you should be good to go on your custom ROM. This issue seems to have arisen when a d2lte build broke most people's LTE/Mobile data.
Sent from Mission Control
UnknownTroll1 said:
If you are still on the Stock TW ROM here is a method to try. It will clear most of your mobile data problems.
1. Enter the Samsung service mode by typing this code into the dial pad *#197328640#
2. Then go to Mainmenu>UMTS>Common>NV REBUILD>NV REBUILD> (Important: don't exit the menu yet!)
3. Wait 30+ sec
4. Long press power button and select "Restart / Reboot"
5. Now check your GPS from any software that may use GPS like "Maps" or "GPS Status"
Credit: S3Rx ROM Development Thread.
EDIT: Afterwards you should be good to go on your custom ROM. This issue seems to have arisen when a d2lte build broke most people's LTE/Mobile data.
Sent from Mission Control
Click to expand...
Click to collapse
I am still unable to get service. This time it is pinned at -113. I am although, registered on a network. Not able to make calls or text.
mpelley92 said:
I am still unable to get service. This time it is pinned at -113. I am although, registered on a network. Not able to make calls or text.
Click to expand...
Click to collapse
Yea at this point I am stumped. I guess its a hardware issue. But before calling quits what is your baseband and boot loader?
Sent from Mission Control
UnknownTroll1 said:
Yea at this point I am stumped. I guess its a hardware issue. But before calling quits what is your baseband and boot loader?
Sent from Mission Control
Click to expand...
Click to collapse
Bootloader and baseband: I747MVLUEMK5
mpelley92 said:
Bootloader and baseband: I747MVLUEMK5
Click to expand...
Click to collapse
You're running the most recent release so I'm not sure what's causing the issue.
audit13 said:
You're running the most recent release so I'm not sure what's causing the issue.
Click to expand...
Click to collapse
I have found the problem with the service. I live in an area where signal is not too great. My LG G2 has a tendency to pick up the correct tower for my area, but my Galaxy S3 does not choose the same tower... It looks for one in a completely different direction.
Forgive me, this thread is going to take a bit of a turn.
Is there any way to choose which cell tower the phone connects to? In my area there is one directly east and the other is directly west. I need the western tower in order to make/receive calls/text and in order to get any data reception. Right now where my phone sits, it does not connect to the western tower so I cannot use it. I used OpenSignal to observe which tower both phones connect to.
The other issue I found is my extended battery (Anker 7200) also interferes with reception quite a bit. In town, it's not noticeable. But out on my acreage it stops my phone from getting any signal. I compared it to my LG G2 and my Galaxy S3 with the old 2100mAh battery. The G2 hovers around -95, S3 w/OEM battery at -101 and the S3 w/Anker battery at -113 (no service).
Mike
mpelley92 said:
Is there any way to choose which cell tower the phone connects to? In my area there is one directly east and the other is directly west. I need the western tower in order to make/receive calls/text and in order to get any data reception. Right now where my phone sits, it does not connect to the western tower so I cannot use it. I used OpenSignal to observe which tower both phones connect to.
Mike
Click to expand...
Click to collapse
Try changing the mode to LTE only under your settings. This may force the stronger connection.
x0ne215 said:
Try changing the mode to LTE only under your settings. This may force the stronger connection.
Click to expand...
Click to collapse
Unfortunately that won't work either. In my area I can only pick up HSPA....
mpelley92 said:
Unfortunately that won't work either. In my area I can only pick up HSPA....
Click to expand...
Click to collapse
Hmm. Out of curiosity, have you tried a different ROM on 4.4.2? I've had weird issues with ROMs and signal, ie MIUI caused me to have my signal cut in and out at random intervals. Worth a shot at least. I've been using SlimKat if you want one for reference (probably the quickest download due to size).
Unfortunately all I can suggest is trying to play with tasker and seeing if you can get it to skip over the crap tower, but to my knowledge there's no way to prevent connection to said tower.
I guess if you wanna get into a gray area you could modify said tower....but I claim no responsibility for your actions with that
x0ne215 said:
Hmm. Out of curiosity, have you tried a different ROM on 4.4.2? I've had weird issues with ROMs and signal, ie MIUI caused me to have my signal cut in and out at random intervals. Worth a shot at least. I've been using SlimKat if you want one for reference (probably the quickest download due to size).
Unfortunately all I can suggest is trying to play with tasker and seeing if you can get it to skip over the crap tower, but to my knowledge there's no way to prevent connection to said tower.
I guess if you wanna get into a gray area you could modify said tower....but I claim no responsibility for your actions with that
Click to expand...
Click to collapse
I've been using Liquidsmooth the past few nights and am losing signal more than ever.
Would the OS control how the modem is used? I would think that it's hardware only that changes how and when you get service.
I'm going to try the UEND3 modem firmware and see if that makes a difference. Also going to try SlimKat like you suggested.