Related
Several days ago, my Verizon Galaxy Nexus began showing an "R" in the signal area, and "Roaming" in the pulldown. Sure enough, it shows that I'm roaming in the about phone information.
The strange thing is that I'm still getting 4G speeds, but my phone is no longer seeing 3G at all, and any time I make a phone call it goes from "R" to 4G.
I cannot dial any Verizon short codes as it tells me they are not valid.
I was on Liquid ROM with 4.0.4 radios when I noticed the issue, and switched to the 4.0.2 radios but the issue persists. I'm currently running CM9 and can't seem to fix it.
Verizon tech support was clueless too. I've verified with my wife's Galaxy Nexus that this isn't a specific issue with our tower, and my sim works great in her phone without issues.
Anyone seen this before?
What happens if you return to stock?
I'm doing that now
Flashed back to stock 4.0.2, same issue persists.
Anyone else have any suggestions?
I am having the same issue, did you find a resolution?
Verizon GNEX
Rom: ParanoidAndroid 1.4
Kernel: Lean Kernel 3.10.0
I have the same problem, but mine maybe a bit different.
I am stuck on "R" here, but I was roaming for 2 weeks in Canada. I am a crack flasher and I flashed JellyBean while in Canada so I am thinking I am provisioned for roaming there? I am downloading a new rom to flash here back in the USA on Verizon, hoping to fix the problem. I cannot access my dialer in JellyBean after I *228, so I cannot hit 1 to provision.
SoI will do a SuperWipe and flash will hopefully do the trick. If anyone figures out what to do please update
I ended up having to do an exchange on mine :-(
damn, that is gonna be lame if that is the case. I bought mine at BestBuy, so I have to do their Rapid Exchange program. Glad I purchased the warranty while I worked there
oc3rulz said:
damn, that is gonna be lame if that is the case. I bought mine at BestBuy, so I have to do their Rapid Exchange program. Glad I purchased the warranty while I worked there
Click to expand...
Click to collapse
Shouldn't really matter where you bought it. It's still under the manufacturers warranty so Verizon should take care of it unless I'm mistaken.
URPREY said:
Shouldn't really matter where you bought it. It's still under the manufacturers warranty so Verizon should take care of it unless I'm mistaken.
Click to expand...
Click to collapse
Verizon will take care of it if it is still under the manufactures warranty, just don't tell them where you bought it (they won't ask). I got mine from Wire Fly, and had to get it replaced due to faulty hardware, they sent it no questions asked.
thanks for the info guys!
Wanted to let you know my problem did indeed go away after I reflashed Slim Bean Alpha 4 here in the USA. I was roaming when I flashed JB, so I guess it picked up their provisions.
did you turn it off, pull the sim card.. wait 1min, then put the sim back in and start it up
Zep, I tried everything originally to make this thing work correctly. nothing helped every time to phone booted it went straight to R and never moved!
HOWEVER I do believe I have found the culprit!!! So everything worked beautifully all yesterday, no problems at all. This morning I decided that I would change the T-CDMA 64 on the bottom back to Verizon Wireless, well guess what. The second I added the "eri.xml" file to /data and reboot, I STARTED ROAMING!!!!
I went to root explorer and deleted the /data/eri.xml file and rebooted! VIOLA I have 4G back and it's not switching over!! So something is causing that eri.xml file to freak my phone and most likely others phones out!
oc3rulz said:
Zep, I tried everything originally to make this thing work correctly. nothing helped every time to phone booted it went straight to R and never moved!
HOWEVER I do believe I have found the culprit!!! So everything worked beautifully all yesterday, no problems at all. This morning I decided that I would change the T-CDMA 64 on the bottom back to Verizon Wireless, well guess what. The second I added the "eri.xml" file to /data and reboot, I STARTED ROAMING!!!!
I went to root explorer and deleted the /data/eri.xml file and rebooted! VIOLA I have 4G back and it's not switching over!! So something is causing that eri.xml file to freak my phone and most likely others phones out!
Click to expand...
Click to collapse
Glad that worked for you. I tried everything including a complete wipe and mine was still roaming even after reflashing the stock ROM.
Hello,
A bit about my Nexus: Bought it online, it's the Domoco version, unlocked, rooted and been using just fine with many custom ROMs.
So yesterday morning, I was talking on the phone with a friend without any problem. After hanging up for a few hours, when I was about to call someone else, I realized my phone didn't have any signal at all. And it has been like that until now, about 48 hours.
It happened so suddenly without any warning. The phone has never been dropped and everything else working just fine.
So here's what I have tried:
- Restart the phone (multiple times)
- Batter pull (multiple times)
- Factory reset the phone (multiple times)
- Wipe cache and dalvik cache in CWM (multiple times)
- Downloaded SetCPU and set the minimum to 700Mhz (instead of 350Mhz)
- Reflash the ROM and tried with other Custom ROMs (I tried Xenon, Xylon, PA, and Carbon ROMs)
- Reflash the Radio and tried with other Radios too (I tried UILH1, XXLH1, SC04DOMLE3 and some others ...)
- I also went to Tmobile and request a new sim card - same problem.
- I borrowed a sim card from another Tmobile customer to try it on my phone - no signal - but the sim card works just fine on his phone.
I ran out of thing to try and I dont understand what happened ... anyone has an idea or something else for me to try ?
Anyone experience this before ?
Welcome too my hell. I have a playstore one now but my first Gnex was an international one and it has this same issue. Its a PCB problem a warranty would fix. I'm near Chicago and a few people have told me there is an electrical engineer downtown that fixes stuff like this. I don't have a price but I think something like this is your only option. Mine sadly is still a battery charger:thumbdown:
Sent from my Galaxy Nexus using xda premium
I know it sounds stupid, but have you tried toggling airplane mode? I run into the occasional loss of signal when im at work [fair to weak signal in the big metal box], and a reboot is the only thing that fixes it for me. Mines a play store model.
bodh said:
I know it sounds stupid, but have you tried toggling airplane mode? I run into the occasional loss of signal when im at work [fair to weak signal in the big metal box], and a reboot is the only thing that fixes it for me. Mines a play store model.
Click to expand...
Click to collapse
Ah yes, I actually did try that too but forgot to mention. I tried toggle airplane mode on and off, also the 2G only mode on and off. But it didn't help with anything.
Thanks for the suggestion.
JediDru said:
Welcome too my hell. I have a playstore one now but my first Gnex was an international one and it has this same issue. Its a PCB problem a warranty would fix. I'm near Chicago and a few people have told me there is an electrical engineer downtown that fixes stuff like this. I don't have a price but I think something like this is your only option. Mine sadly is still a battery charger:thumbdown:
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So I guess I have to look for an electrician then, cause I have this phone just a little bit over a year so warranty is a no go for me.
Thanks for the idea.
PS: anyone else has more option for me ? I just wondered if I have bricked my phone ... cause I flashed lots of diff. ROMs to try out but never gotten a bricked phone before, could this be a bricked phone ?
Bricked refers to a phone that does what a brick does: nothing. It doesn't boot, it does not light or attempt to boot, it does nothing. This is a signal issue..I have no prior experience with docomo, but this thread came up on search: http://forum.xda-developers.com/showthread.php?t=1574018, maybe it'd be helpful. Have you converted it to yakju or takju and tried a google factory image?
And this: http://forum.xda-developers.com/showthread.php?t=1554150. If it is a circuit board, it kinda looks like s.o.l., and im sad to say that to you.
I wanted to let you know that I experienced the same issue. I bought the unlocked Docomo Galaxy Nexus, and had it working fine on T-Mobile for half a year, and then suddenly had no signal on Tuesday. Nothing I did - factory reset, battery in and out, sim card in and out - could fix it. Have you tried using different sim cards in your phone to see what works and what doesn't?
I figured out that my phone will accept AT&T, and actually does connect to T-Mobile while roaming (I used an international sim card). But, my phone will say "Cannot find mobile network" when any T-Mobile sim card is inserted.
chowabbajack said:
I wanted to let you know that I experienced the same issue. I bought the unlocked Docomo Galaxy Nexus, and had it working fine on T-Mobile for half a year, and then suddenly had no signal on Tuesday. Nothing I did - factory reset, battery in and out, sim card in and out - could fix it. Have you tried using different sim cards in your phone to see what works and what doesn't?
I figured out that my phone will accept AT&T, and actually does connect to T-Mobile while roaming (I used an international sim card). But, my phone will say "Cannot find mobile network" when any T-Mobile sim card is inserted.
Click to expand...
Click to collapse
I also have the same problem with the docomo phone. ATT Sim card works. Tried other's T-mobile sim cards and it doesn't work. I wonder if somehow the IMEI has been blocked by T-mobile.
wocman said:
I also have the same problem with the docomo phone. ATT Sim card works. Tried other's T-mobile sim cards and it doesn't work. I wonder if somehow the IMEI has been blocked by T-mobile.
Click to expand...
Click to collapse
I know others who bought their GNEX through the Play Store and those work just fine with T-mobile. I tried their sim cards in my phone and it doesn't work. I don't think T-mobile is intentionally blocking the docomo phones, because I'm getting T-mobile through roaming, when I use an international sim. My guess is they're doing something to the cell network that just somehow leaves our configuration out. Hopefully it's temporary, but who knows.
Worse case, I'll just purchase a Nexus 4, because I love 4G data for just $30/month with T-mobile. Anyone else got suggestions?
wocman said:
I also have the same problem with the docomo phone. ATT Sim card works. Tried other's T-mobile sim cards and it doesn't work. I wonder if somehow the IMEI has been blocked by T-mobile.
Click to expand...
Click to collapse
Alright, update on this and there' good news. I called Tmobile and they said my IMEI is actually Blocked. The reason, according to him, is that Tmobile usually sweep the network to clean up all "un-supported" devices, so my device is apparently one of them and therefore got blocked about 2 days ago.
So he said for this, he needs to escalate it to business support and they surely can unblock it for me, but I have to wait until Monday since they don't work on weekend. But well, that's surely a good news. phewwwwwwwwwwwwww !!!
So to all of you guys who are in the same situation, make sure you call Tmobile first before flashing crazy like I did LOL.
Thanks for all the help.
I'd love to know if you are able to get this unblocked and working as I have the same problem as of Tuesday. I was traveling and went into a TMO store, and they told me it was NOT IMEI blocked. In fact they looked at the IMEI and read the page and said 'it was not eligible for blocking'.
I called TMO to see if my phone is IMEI blocked, and through three levels of support the universal answer was no. I'm now fully confused because if it's a hardware issue, why did several people all have the same problem all on Tuesday. For those others who are having issues, can you see the TMO network but not connect to it? That's what I have, I can see TMO and AT&T but haven't been able to connect to either one since Tuesday.
simple23227 said:
Alright, update on this and there' good news. I called Tmobile and they said my IMEI is actually Blocked. The reason, according to him, is that Tmobile usually sweep the network to clean up all "un-supported" devices, so my device is apparently one of them and therefore got blocked about 2 days ago.
So he said for this, he needs to escalate it to business support and they surely can unblock it for me, but I have to wait until Monday since they don't work on weekend. But well, that's surely a good news. phewwwwwwwwwwwwww !!!
So to all of you guys who are in the same situation, make sure you call Tmobile first before flashing crazy like I did LOL.
Thanks for all the help.
Click to expand...
Click to collapse
I'll call up T-Mobile tomorrow and ask if they IMEI blocked my device. I had them reset my signal and give me a new SIM card, but didn't realize it could have been IMEI blocked. I'll give them a call on Monday and let you know what the result is. Maybe it won't be too late to cancel my order on that Nexus 4...
I'm quite confused. I've been told last Thursday in a TMO store and with tech support that I didn't have an IMEI block, and the same with three reps tonight. I know the Sim Card is good, and so I'm being told its a hardware issue. However, several of the same phones had the same issue on the same day, so I can't buy it's a hardware issue. Has anyone with this issue flashed a new or different radio into the phone, either before or after the service loss? I have not, running it as it came out of the box.
I just got off the phone with T-Mobile Support, and they told me the device is not blocked. The reason is that T-Mobile cannot block or unblock devices that are not registered to T-Mobile. So I'm back to square one on this.
chowabbajack - When did you first have a problem, last Tuesday? Did you prior to that do any flashing or radio changes to the phone?
We're in the same spot....
alexwinsberg said:
chowabbajack - When did you first have a problem, last Tuesday? Did you prior to that do any flashing or radio changes to the phone?
We're in the same spot....
Click to expand...
Click to collapse
I did not do any kind of flashing or radio changes prior to Tuesday, when I lost signal.
chowabbajack said:
I did not do any kind of flashing or radio changes prior to Tuesday, when I lost signal.
Click to expand...
Click to collapse
That makes me think its something to do with the radio software, because I am the same the problem overall doesn't seem as large as the number of phones I perceive were bought on the Docomo deal.
Ive been using the docomo version of the nexus as well on tmobile for almost a year and it was since last tuesday when it no longer recieved any singal. with some digging around and too many phone calls, I found that the imei number on the phone is not the same as the one under the battery. i have the generic 004999010640000 imei right now and it not sure how i got it. as i bought it unlocked.
what i have tried:
reboot, battery plug, reinsert sim, factory reset, root and flash, got a new sim card, relocked, unlocked
sim card works on other phones.
also i have called tmobile and samsung endlessly and this is what i got:
tmobile cannot unblock the imei since it is not from them.
samsung is redirecting me to their japan branch.
docomo i cannot reach.
my phone before last tuesday:
unrooted stock 4.2.1
been testing different things to see if there is any way to restore the imei
also using root explorer, i cannot find my efs folder....
I've got the same problem since last Tuesday with my GNex and T-Mobile.
Mine is not from docomo though, but the French phone provider SFR, unlocked through FDocomo apk.
Rooted phone, running 4.2.1., no changes whatsoever in the past month and it worked fine until Tuesday, so I don't think I'm responsible for having no signal.
Honestly, I am relieved to see we are quite a few to have this problem, and also very pissed at T-Mobile for causing all this. What should be the next step then? Is there any chances they fix the issue quickly? If not, I might just go to the competition. I've tried AT&T sim cards and they work fine.
vanessax17 said:
Ive been using the docomo version of the nexus as well on tmobile for almost a year and it was since last tuesday when it no longer recieved any singal. with some digging around and too many phone calls, I found that the imei number on the phone is not the same as the one under the battery. i have the generic 004999010640000 imei right now and it not sure how i got it. as i bought it unlocked.
what i have tried:
reboot, battery plug, reinsert sim, factory reset, root and flash, got a new sim card, relocked, unlocked
sim card works on other phones.
also i have called tmobile and samsung endlessly and this is what i got:
tmobile cannot unblock the imei since it is not from them.
samsung is redirecting me to their japan branch.
docomo i cannot reach.
my phone before last tuesday:
unrooted stock 4.2.1
been testing different things to see if there is any way to restore the imei
also using root explorer, i cannot find my efs folder....
Click to expand...
Click to collapse
I have the exact same generic IMEI number as you, which does not match the number under the battery. I'm not liking the news that you did flash and still no go. I'm a novice at this stuff so please keep us posted.
Recently i have purchased a used Verizon Galaxy Nexus from a seller on ebay. It is in excellent shape and has no cosmetic damage to the phone. The persone i purchased it from was a reputable seller and had the feedback to back it up. Now with that said. The phone was listed as broken because the seller could not get the phone to connect to the Verizon cell network.
So i bought the phone thinking that maybe the phone had some deleted files on it that i could replace or better yet. Just flash all new software to the phone and remedy the problem. Thus i would have bought a phone for a quarter the price of a new one and have a fully functioning phone.
As far as flashing and roming goes. I am no novice. I have owned many Android phones, in fact thats all ive owned lol, but this one is causing me some frustration. So here is a list of the things i have done to remedy the problem to no avail...
1) Factory Reset- no go
2) Complete Re-Flash of the entire framework - Im talking everything. Careful fastboot flash of every elemet of the android ecosystem
3) Radio swapps from older versions to newer versions.
4) Multiple reboots and toggleing airplane mode over and over again.
5) Flashed several aftermarket roms.
6) Toggled the test mode in phone settings using the hidden menu (*#*#4636#*#*)
For a short period of time last night i was able to get the phone to display up to 3 bars of service using the method described in #6 I NEVER got data working and i could only temporarily call out. My girlfriend would see me calling in on her phone but immediately upon answering it would drop my call. The phone never rang on my end and it cannot receive calls. Also cannot send text messages.
I thought for sure i could fix this one, but for some reason it is being stubborn. Please Help me XDA!!! Your my only Hope!!!
P.S. As an aside i did take the phone apart and check to make sure nothing was damaged. All the components look top shape and all the little snap connectors are securely fastened. No metal contact prongs are bent and everything is clean of dirt and debris.
does it display your IMEI *#06#?
maybe some NV_DATA corrupted or it can be hardware issue
Does indeed show imei and I had it checked for lost / stolen / blacklist by Verizon. At the store now to get it checked out.
And that is actually meid that that code pulls.
Sent from my large and in charge GN2 using Forum Runner
And the verizon store could not do any good. Has anyone ever ordered a replacement back casing from ebay or anywhere else on the web? Im thinking it may be a ribbon cable somewhere. Maybe even the bottom board that houses the headphone jack and a series of winding antenna leads.
I am still open to suggestion though so anyone with any information on the matter please let me know.
EDIT: Been looking at Cell phone repair shop and they have the antenna / headphone replacement in stock. They also have the back mid frame with all the antennas on it as well.
I feel like this is a 50/50 shot in the dark as to which part i need to fix this problem. Gonna give them a call tomorrow and see.
I've ordered a new mid frame in the hopes that there is a torn ribbon cable somewhere in the old one. I'm still not certain that's what it is though.
Anyone with some insight please get back to me.
Sent from my Galaxy Nexus using Forum Runner
Bump.
Still need some help guys. This is a very perplexing problem that i would like to fix.
Anyone? Mods? Admins? Devs? I need some help here. Don't let me down xda!!!
Sent from my large and in charge GN2 using Forum Runner
sounds like a unconnected/torn radio cable to me.
Zepius said:
sounds like a unconnected/torn radio cable to me.
Click to expand...
Click to collapse
I've been all through the device and checked all the connections and hardware. Everything has a firm connection and is in top shape. I even replaced the back midframe cover with a brand spanking new (OEM Samsung) one. Its behaving like a software problem in that I can toggle between 3G and 4G and get 3G for a brief moment and can even call out, but the moment that someone answers the call it drops service and i have to start the process all over again.
UrbanDroid said:
I've been all through the device and checked all the connections and hardware. Everything has a firm connection and is in top shape. I even replaced the back midframe cover with a brand spanking new (OEM Samsung) one. Its behaving like a software problem in that I can toggle between 3G and 4G and get 3G for a brief moment and can even call out, but the moment that someone answers the call it drops service and i have to start the process all over again.
Click to expand...
Click to collapse
Try fastboot flashing the factory images from google.
Sent from my Nexus 7 using xda premium
blackhand1001 said:
Try fastboot flashing the factory images from google.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I've done this as well several times. 4.2.2 and 4.2.1 and yes i made sure i had the correct firmware for my version of the phone. Verizon toro.
Edit: Has anyone ever sent in their phone to Samsung for RMA? I called and talked to someone and tried to work through the problem and she came to the conclusion that I should send it in at no cost and that I wouldn't be charged anything unless I authorized them payment before. Essentially they will run through the phone and check everything out for free and see if it can be fixed.
UrbanDroid said:
I've done this as well several times. 4.2.2 and 4.2.1 and yes i made sure i had the correct firmware for my version of the phone. Verizon toro.
Edit: Has anyone ever sent in their phone to Samsung for RMA? I called and talked to someone and tried to work through the problem and she came to the conclusion that I should send it in at no cost and that I wouldn't be charged anything unless I authorized them payment before. Essentially they will run through the phone and check everything out for free and see if it can be fixed.
Click to expand...
Click to collapse
I did the same thing. Bought one from ebay in good shape. Was told it functions. I have the HTC Rezound so the sim wouldnt fit. Went to Verizon and they put in the mini sim and no service. Reset the phone and even tried a new sim. I have since tried different roms and radios, but still no service. Luckily the seller has a 100% guarantee so looks like this one is going back. From what I have read, these are prone to radio issues.
Sir Lemmiwinks said:
I did the same thing. Bought one from ebay in good shape. Was told it functions. I have the HTC Rezound so the sim wouldnt fit. Went to Verizon and they put in the mini sim and no service. Reset the phone and even tried a new sim. I have since tried different roms and radios, but still no service. Luckily the seller has a 100% guarantee so looks like this one is going back. From what I have read, these are prone to radio issues.
Click to expand...
Click to collapse
Yeah. I've read multiple threads about radio issues, but here's the thing. Every one of them claiming to have signal issues also had the random reboot issue. They all were even having problems flashing any Roms or anything else for that matter.
I on the other hand have had zero problems flashing anything. Fastboot works 100%, Recovery flash works 100% and I can unlock and lock the boot loader without issue. Its an odd problem.
Sent from my large and in charge GN2 using Forum Runner
UrbanDroid said:
Yeah. I've read multiple threads about radio issues, but here's the thing. Every one of them claiming to have signal issues also had the random reboot issue. They all were even having problems flashing any Roms or anything else for that matter.
I on the other hand have had zero problems flashing anything. Fastboot works 100%, Recovery flash works 100% and I can unlock and lock the boot loader without issue. Its an odd problem.
Sent from my large and in charge GN2 using Forum Runner
Click to expand...
Click to collapse
I've had an issue flashing, it would abort for no reason. I would also have issues getting into CWM. After playing around with it all night, I don't think its a software issue. I've been reading the antenna has given other people issues and some have even tried to replace them. a Rep from Verizon thought it was the sim reader. I don't believe that because the phone registers a sim and the number tied to it (which is my number). Under status, I does read different every time.
Network: searching for service
Signal strength is usually at: -120dBm 99asu
Mobile network type: (varies) CDMA - 1xRTT:7 or LTE: 13 or unavailable
Service state: out of service
Roaming: not roaming
Mobile network state: (varies) Disconnected or Connected
I've tried different combos such as CDMA and Home LTE Automatic and so on. I think its just a poor design. Seems to be only the CDMA devices tho.
Did OP ever arrive at a solution or at least pinpoint the cause of this problem? I am currently experiencing a pretty much identical problem to the one described (with the exception that I don't even get a 3G signal -- complete lack of signal). My problem started after a brief Airplane mode toggle yesterday and I haven't been able to get on the network since.
Thanks.
I think it's a hardware problem tbh.
I modded mine to work with the palm pre touchstone inductive charging kit. In the process wires were soldered, rear housings were mutilated and the phone was tortured a bit. I was never happy with Samsung's **** build quality so I eventually just ditched it altogether.
I decided to repair it and give it to a family member so I replaced the back housing and USB port with parts ordered off ebay. Ever since my repair work the thing cosmetically looks almost mint. However no OS will recognize it anymore (windows throws an "invalid descriptor" and won't install a driver) and 3G/4G/wifi reception is almost nonexistent. Switching roms or radios doesn't seem to help, and obviously I can't odin a factory image. Pretty much boned.
pbourdyk said:
Did OP ever arrive at a solution or at least pinpoint the cause of this problem? I am currently experiencing a pretty much identical problem to the one described (with the exception that I don't even get a 3G signal -- complete lack of signal). My problem started after a brief Airplane mode toggle yesterday and I haven't been able to get on the network since.
Thanks.
Click to expand...
Click to collapse
Had a similar problem in regards to a lack of signal. It just completely gave out while driving a couple days ago (interestingly enough, the music I was streaming via Soundcloud stopped right as I passed the Facebook headquarters in Menlo Park, which ironically is a 4G dead zone for Verizon). This was a refurbished replacement device that I got about 15 months ago, and was running the latest OmniMetal rom flawlessly for the last few months.
I arrived at this thread and followed all the steps that OP took to try and fix it. Ended up reverting to an earlier 4.2.2 rom and reflashed the radios thinking that might solve the problem. Upon reboot was able to connect to mobile data and make phone calls briefly, but about an hour later the same thing happened. Brought it to the store and swapped out the SIM card for a new one, no dice.
Fortunately VZW is doing open enrolment for phone insurance, so I added it for $10/month to get an extended warranty. Now I'm going to restore everything to stock, lock the bootloader and send it back for a new one. Assuming there are no problems with the replacement, I can cancel the insurance plan, bringing the cost of the replacement Gnex to just 10 bucks.
Was anyone out there able to successfully modify the radio hardware for cheap?
coltronathon said:
I think it's a hardware problem tbh.
I modded mine to work with the palm pre touchstone inductive charging kit. In the process wires were soldered, rear housings were mutilated and the phone was tortured a bit. I was never happy with Samsung's **** build quality so I eventually just ditched it altogether.
I decided to repair it and give it to a family member so I replaced the back housing and USB port with parts ordered off ebay. Ever since my repair work the thing cosmetically looks almost mint. However no OS will recognize it anymore (windows throws an "invalid descriptor" and won't install a driver) and 3G/4G/wifi reception is almost nonexistent. Switching roms or radios doesn't seem to help, and obviously I can't odin a factory image. Pretty much boned.
Click to expand...
Click to collapse
I did the same mod, and other than losing my pc connection (which frankly is never needed) it's been great. You have to be very careful and take your time. I'm not even convinced that my pc connection issues are related to the Palm mod, I think they just happened to coincide. Either way, I don't need it so I never bothered tracing it down.
I have searched the forum but I'm not sure how to search this and I haven't found anything. I cracked the screen on my note ii a month or two ago so I ordered a new one from eBay to replace it. The one I ordered said it was compatible with the i317. I switched it out and everything seemed to be fine. The issue I'm having is that ever since then I have has next to no GSM signal.i have pulled the phone apart to check the connections and everything looks fine. I can get LTE without issue, but when I try to make phone calls or send texts, the signal drops drastically and the message or call usually fails. I have flashed multiple roms and even returned to stock but none of that helped. I don't see any issues with the GSM antenna but I'm not sure how to tell. Does anyone have any other ideas I could try?
One thing I noticed that you didn't mention anything about. Changing your modem, or checking your Apn setting...
Those are the two things that could cause those issues!
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
I tried those initially but after that I used Odin to go back to stock. At this point my phone is completely stock and I am still having the issue.
Hi,I have this issue with my T-Mobile Galaxy S3 (SGHT999)
.It seems to be in the Edge network even though I'm in a 3g/4LTE service area. The phone is slow.I could use a solution and looking for suggestions on how to fix this 4G network phone.I have another Galaxy S3 (SPH-L710) with another carrier with no problems. Well one problem I'm not with that carrier any longer. This phone doesn't have a sim card slot like the T-Moble phone has. The other problem is the wifi reception. Its ok in the room with the router but you go say 30' away and communication is spotty. Other S3 phone I could be 100' away no problem. I thought all Galaxy S3's were the same. Thanx for any help.
What carrier are you using it with? Make sure you have correct apn settings. For the WiFi not sure, 100 foot seems a little extreme for no problems, unless they were different routers
Sorry to resurrect an old thread but Im facing this exact same problem right now. I have two SGH-T999s, both unlocked, and while 4G works perfectly on one, the other only works in GSM/EDGE mode and will find no signal when I switch to WCDMA only. Both phones in the same location, the exact same sim switched between both handsets, works fine on one and not on the other. I have already reset the phone multiple times, reflashed the stock firmware, replaced the stock firmware with CyanogenMod 11 as well as the 12.1 nightly, NOTHING makes a difference. It will stick to GSM and EDGE only and will just not connect in 3G/4G.
At this point, I am guessing this is a hardware problem. The same exact stock firmware has been flashed on both devices, so it cannot be a difference in version. The phone with the trouble has been dropped and has a shattered front glass. I wonder if something else might have been knocked loose when it fell. I opened it up and tried to reconnect the antenna, but noticed that only one end was using a connector, the other end appears to be soldered. I did not try to pull the motherboard out, nor touched the sim tray.
Does anybody have any suggestions on where to look next to troubleshoot this problem?
I am also having this same problem; I've tried everything, including the things on this thread: http://forum.cyanogenmod.org/topic/...ge-on-phone-and-not-34g-imeidata-issue-fixed/
If anyone has found a solution, that would be great...
Check to make sure the imei in About Device isn't blacklisted and that it matches the one under the battery.
If it does and you have Odin flashed the stock firmware and factory reset, it is most likely a hardware problem.
FYI, the antenna you see when you open it up is the wifi antenna, not the cellular one.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Check to make sure the imei in About Device isn't blacklisted and that it matches the one under the battery.
If it does and you have Odin flashed the stock firmware and factory reset, it is most likely a hardware problem.
FYI, the antenna you see when you open it up is the wifi antenna, not the cellular one.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Hmm, I saw that there was an IMEI present, but never considered it could be different!!! You are right, the IMEI on the back of the phone does not match the one shown in About Device! How could this have happened? The person who used it before is not someone who fiddles with their phone... The best I can think of is that whoever unlocked the phone for them must have done this!
I did see numerous threads about missing IMEI, but didn't pay attention because mine was not MISSING it! Also noticed it is against xda site rules to even discuss that stuff. But since I inherited a phone that came like this, I guess the mods will forgive me for saying "let me google this"
EDIT: Oh yes, the IMEI on the back of the phone checks out.
Also, did not know the antenna was the wifi one! But since its IMEI related, I guess thats not an issue anymore
Fixed it!!!
UPDATE: As per DocHoliday77's advice, I'm deleting the links and explicit instructions. Suffice it to say all the information you need to do this is available on this site itself.
After @DocHoliday77 pointed out that the IMEI may be incorrect, I did some research and managed to restore my IMEI as well as get 4G back.
I was able to restore my device because I had the advantage of having a fully working device with me from which I could pull the EFS partition as well as get an NV dump. For those that do not have a second device, I do not know how they can get things working again. In anycase, all of the information I needed to accomplish this was found in three threads on this site. The only additional piece of information that T-Mobile users need is that to get your device into Diagnostic mode, the dialer code is *#0808#.
Wanam's Partitions Backup & Restore... does a much better job at backing up the correct partitions for EFS.
EFS Professional for everything else.
And before anybody asks, sorry I cannot provide you a copy of my EFS backups. Only becuase I am not knowledgable enough to know how much personal information is contained in that partition, but given that the IMEI is dependent on it, I hope you can understand why I cannot share mine. Perhaps DocHoliday77 will be able to suggest a way for others to get this sorted out.
That's great that you got it fixed! And kudos for figuring it out on your own!
Though you may want to edit out any instructions and links as they are not allowed to be posted. (Too many people jump on this stuff in an attempt to get stolen devices to work again....highly illegal) (it's why this stuff is so hard to find usually!)
If anyone does have problems with this please feel free to PM me and I will do my best to help.
Sent from my SGH-T999 using Tapatalk