Hello Everyone. I've searched XDA and the net high and low trying to figure out what is going on here, but it has come time to post. Hopefully someone can point me in the right direction.
Bought my S3 from T-Mobile a few years ago, have installed a number of roms on it, but most recently updated to CM 10.2. I started having boot issues (phone would stop booting after a couple of restarts, not a sudden death syndrome phone, BTW). After using ODIN to load on root66-UVUEMJC (tmobile 4.3), and running into more issues, I ended up loading Stock 4.3 from Kies (yes, I realize this is a horrible mistake now).
That got me on my feet again, I used ODIN to install clockworkmod rom manager, then re-installed CM10.2. It was at this point where I noticed that I no longer had cellular network connectivity anymore. I've tried another t-mobile SIM in my phone to make sure it wasn't that, and it had the same problems:
On startup, my phone will connect to the cellular network and fill in all the fields under Status (including IMEI), but after a minute or so, I loose that and the device goes to "No Service". Nothing I've tried has been able to get this fixed. I have attempted to flash the latest modem as well with no luck.
As mentioned, any help would be greatly appreciated on what to look for / do to get this thing working so I don't have to drop a load on a new phone.
Thank you!
Related
Hey everyone i recently install a rom posted by a user at the following threat http://forum.xda-developers.com/showthread.php?t=2033132 both mine and my gf's s3's, my install went flawlessly but hers had an issue. the signal was very weak, at first we thought it was a reception problem cause some text and calls were going through (and when i say some i mean almost none). then i went poking around and saw the imei was showing 0, the phone had been rooted with cwm installed on it, so i used so of the tools and the tutorials i found on these forums to restore the imei but still very weak and losing signal, on reboot of the phone there is no signal at all, so i kept on reading in the forums and tried to flash a modem but nothing still, then installed cm10 stable and still nothing finaly i gave up and installed stock rom unrooted the device, used triangle away and all that and still nothing even installed the latest ota updates and still nothing, im at the end of my rope lol and my gf is about ready to kill me, any help would be greatly appreciated . im with bell model number is i747m, the base band that it currently has is i747mvldlk4
ckavvouras said:
Hey everyone i recently install a rom posted by a user at the following threat http://forum.xda-developers.com/showthread.php?t=2033132 both mine and my gf's s3's, my install went flawlessly but hers had an issue. the signal was very weak, at first we thought it was a reception problem cause some text and calls were going through (and when i say some i mean almost none). then i went poking around and saw the imei was showing 0, the phone had been rooted with cwm installed on it, so i used so of the tools and the tutorials i found on these forums to restore the imei but still very weak and losing signal, on reboot of the phone there is no signal at all, so i kept on reading in the forums and tried to flash a modem but nothing still, then installed cm10 stable and still nothing finaly i gave up and installed stock rom unrooted the device, used triangle away and all that and still nothing even installed the latest ota updates and still nothing, im at the end of my rope lol and my gf is about ready to kill me, any help would be greatly appreciated . im with bell model number is i747m, the base band that it currently has is i747mvldlk4
Click to expand...
Click to collapse
I have the same problem, I am looking how to fixing it. If you find a way, please PM me.
Hello everyone, I've seen some other threads about similar signal loss issues or problems on the i927 around xda, but none of them worked or were compatible with the type of problem I'm having. I recently installed the January 6, 2013 build of Paranoid Android v2.+ on my i927, and it works great. However, I've been having one major issue that renders my phone useless. After about an hour or so of having the phone on, I lose ALL signal to my cell network (AT&T). There are no signal bars, no messages/MMS/calls can be made or sent, and I end up having to reboot my phone for it to function properly again for another hour or two.
I've tried what some users around xda have suggested such as taping my SIM card in place or wiping cache/dalvik cache in recovery, but as of yet nothing has worked
If anyone can help me, it would be GREATLY appreciated. I'm stumped at this point after exhausting all the options I thought would work. I really want to keep this ROM on my phone, it works better than stock or any other ROM I've tried yet by far.
Thanks in advance!
-MrDaggs
ALSO, I can post screenshots or any additional information if it's helpful in any way.
How did you unlock? I've had problems with signal when I unlocked via galaxsim unlock tool. Check your /efs/Nv.log for errors, I had an error connected with md5 sum every second or so.
For me, the other unlock way solved all the problems.
can you see in about, your imei, maybe is corrupt. see this link, maybe help http://forum.xda-developers.com/showthread.php?t=2019540
I haven't unlocked my phone, it was sold to me as an AT&T phone. I don't think my IMEI should be the problem
Sent from my rooted Samsung Captivate Glide i927 using Tapatalk
I also experienced this issue on 4.1.2, so I moved to 4.2.1 hoping to avoid it, yet this morning issue happened again with thegreatergood's i927 - CM10.1 - 1/22/2013. My IMEI is ok, unlocked by entering the unlock code given to me by ATT.
Note I am able to restore connection by switching on and off airplane mode, might save the time of reboot.
paganinia said:
I also experienced this issue on 4.1.2, so I moved to 4.2.1 hoping to avoid it, yet this morning issue happened again with thegreatergood's i927 - CM10.1 - 1/22/2013. My IMEI is ok, unlocked by entering the unlock code given to me by ATT.
Note I am able to restore connection by switching on and off airplane mode, might save the time of reboot.
Click to expand...
Click to collapse
Yeah, I've tried every now and then to reset my connection by toggling airplane mode on/off, and it usually works for me too. I'm just stumped on why there's an issue with the signal at all to begin with, it doesn't make sense to me
I confirm, I also experience connection lost from time to time. And I also restore it with switching airplane mod on/off.
The same problem with 4.2.1
Hi! I had the same problem with the phone. The signal was totally off. I was using LiquidSmoth 4.2.1. I gave a solution flashing the rom another time.
I've seen this on AT&T's ICS firmware, it gave me this issue often and for me a reboot was the only fix.
I've upgraded to CM 10.1 and I am hoping it fixed the problem. If not, I will try flipping airplane mode off and on, I don't like battery out reboots, but if it doesn't any more suggestions welcome.
Thanks.
tech927
I've been using cm10.1 for months now & haven't had any issue with signal dropping. Did have if happen with other roms, but I think it's something to do with the kernel more than the rom. They just released rc1 of cm10.1 has the latest kickass kernel.
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 about 6 months ago, I decided to finally try out some custom roms on my t999 after running stock for over a year. I tried a couple of roms and stuck with cm11. Every thing was great until about 3 weeks ago. Out of nowhere, my phone randomly decides to drop connection to tmo towers. Sometimes i have bars and 4g symbol and sometimes i don't have anything. When I pull the battery and restart, I am able to connect to data, make calls, and send messages for a few minutes, but then i lose everything. Randomly throughout the day, I will get signal back for a few minutes but thats it. I flashed a touchwiz rom for now so I can use wifi calling, So that still works.
So I tried to flash a different baseband modem from DocHoliday77 and none of them worked. I also tried going back to stock following DocHoliday77s guide once again, but for some reason that does not work. I launch odin3.07, put my stock firmware in the pda section, make sure only auto reboot and F reset time are checked. I connect my phone in download mode, it is detected and i start the process. The phone restarts but gets stuck at the samsung logo screen. I have tried flashing different roms and none work.
I dont think its an imei problem because I got the phone direct form tmo with a contract.
Does anyone know what I might be doing wrong? ANY help would be greatly appreciated.
Did you factory reset after you flashed the firmware in Odin? That's the only way it will boot coming from cm.. You may just need a new sim if flashing to stock won't fix it.. And BTW T-Mobile doesn't do contracts
Hi,
I recently, flashed a bunch of different ROMS and modems to try to fix my original service issues on my T999L.
Being a noob that I am, I went from 4.2 and numerous other versions, and a couple ROMs had service, but most didn't. I thought I could fix it with flashing a new modem but that killed my service completely (IMEI null/No SIM card)!
SInce then, I flashed back to Stock ROM (using ODIN) and regained SIM recognition, but now my service sends the same text over 10 times, and I keep receiving the same texts messages. Even on wifi, I noticed that I am having issues (when I download apps it only gets to 90% and never finishes).
Does this mean I may have screwed up my EFS files? I never backed them up, and now I am in stock ROM with really strange service issues.
Will flashing a new modem help, or is this how I reached this point in the first place?
Any help would be greatly appreciated! Thanks in advance!