Related
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
I'm running CM-10.1.3 (stable) on my phone (T999) with the UVMD5 modem and last night I lost all signal for about 30mins. I rebooted a few times and toggled air plane mode on and off without any success. Eventually, I got signal again but no data. I can send and receive calls and SMS but I have no data connection (can't browse, no email notifications, etc.). I have tried all the options under the Network Mode settings without any success. Occasionally, I'll see the "E" sign for Edge/2G but there is no data available even then. I also tried updating the modem to UEMJ4 and UEMJC but observed no changes. WiFi works just fine. Could this be a hardware issue? Is the antenna somehow damaged? Is there anything else I could try?
Try another Kernel. If that does not help, Odin flash to Stock. If that too doesn't work then suspect tower issue.
Hardware is a possibility. But lets not get ahead of ourselves
Thanks, I'll give that a shot and report what I find. I doubt that it's tower related since I'm having the same issue at home and at work and my roommate, who has an original Galaxy and is also on Tmobile, is not having any problems.
I flashed stock JB 4.1.2 (UVDMD5) using Odin since I had it laying around and I'm still seeing the same issue. What else can I try?
EvilBoz said:
I flashed stock JB 4.1.2 (UVDMD5) using Odin since I had it laying around and I'm still seeing the same issue. What else can I try?
Click to expand...
Click to collapse
Check your APNs. Those are under Settings > Advanced > Network. Its called Access Point Names. It should be set to epc.t-mobile.com. See this thread for details.
Try UVDLJC or the prior version to MD5. If that too does not help then take to T-mo for antenna Repair.
Check your IMEI number. If it is zeroed out PM me. Otherwise just let us know here, (but don't actually post it).
DocHoliday77 said:
Check your IMEI number. If it is zeroed out PM me. Otherwise just let us know here, (but don't actually post it).
Click to expand...
Click to collapse
The IMEI is 0. I never backed up the EFS folder but I was able to get the number from tmobile.
I have been having the same issue since June 2013 after doing to 4.1.2 OTA update from T-Mobile, at the time I didn't realize the IMEI was listed as unknown. So for months I have not gotten a cellular data connection better than Edge. Also after that update trying to check for a software update on the phone resulted in an error, and Kies told me my firmware was not supported for upgrade. Looking in some support forums and talking to T-Mobile got me nowhere, so I have just been dealing with it.
Wanting to upgrade I recently used Odin to load the official T-Mobile 4.3 ROM on the phone, actually hoping that would fix my issue (still in the dark about IMEI) which it did not.
I had never backed up the EFS folder, since as a standard user I had no idea what it was and while performing an update from my provider I didn't realize anything would need to be backed up outside of Kies. Now that my warranty is expired and having to take matters into my own hands I am on a quest to find a fix, however I don't want to "brick" my phone in the process, at this point I know enough to be dangerous.
Currently;
Android 4.3 Official T-Mobile ROM
BASEBAND is good T999UVUEMJC
Kernel 3.0.31-1962493
IMEI is Unknown
Looking at some other posts here at xda-developers I tried to follow some instructions on repairing or restoring IMEI using NV reader/writer, however I cannot get NV reader/writer to connect to my phone.
I have noticed in 4.3 when using *#7284# in the dialer the QualComm settings are no longer present, only MODEM and PDA are available.
I have poked around in Service Mode *#197328640# and found a setting that I thought might help, but I have a feeling it is the same thing as 8#7284#
[1] UTMS > [6] COMMON > [4] DIAG CONFIG > [1] USB or [2] UART
So at this point I don't know how to proceed, again I am not thrilled about loading a custom ROM, or really any ROM for fear of making the issue worse or bricking the phone. I have read a lot of posts about no longer being able to make calls due to IMEI issues. Everything works right now except cellular Data.
Hey guys, i'm having a bunch of connectivity issues, all revolving around cell service. WiFi works greats. First issue is that text message get sent and received sporadically(meaning sometimes i send texts and they send right away, while other times they fail and require a few resends). Second issue is incoming calls not reaching my device(doesn't even ring on my phone) and going straight to voicemail after 2 rings/outgoings calls not ringing at all. Last and hopefully least, data seems to drop or hang on upload after a few minutes of use. Now all these issues occur sporadically and at seemingly random times, but it seems like once one of these 3 issues occur, they all get triggered.
I've checked and reset APN settings and they seem correct, although instead of "Not Set" for the username, there is "none" and there is a four digit password that has been censored by *, and for Server there is one digit *.
I've called T-MO customer service and their suggestion to solving it was a Master Reset, which is essentially a Factory Reset including wiping the Internal SD card. I've yet to do this, but i have tried a regular Factory Reset from TWRP, but the issue still persists. Not sure what to do at this point, was considering ODIN'ing back to stock(4.1.1 root66 to be exact).
If it matters, I'm running Dandroid 4.1.2, with DLJA baseband and stock kernel. Sometimes rebooting or flipping airplane mode on/off fixes it for a couple more minutes.
Any insight or suggestion would be GREATLY appreciated. Thanks for taking the time to read this.
I had this problem on my Nexus 5 and it seems to be sorted out now. But I'd highly recommend ODINing to the latest stock if you change your baseband radio and you're still experiencing the same issue. (I'm also a T-Mobile customer)
Also, I recommend heading to the market and downloading Offline SIM APN Database to verify you have the entirely correct APN.
Hey, thanks for the swift reply. Firstly, i checked the offline sim database and my APN settings match those, so hopefully APN settings are out of the question. And by latest, are you referring to 4.3? Also, i don't think i've ever flashed a radio/modem of any kind, and my baseband has been DLJA since i first bought this phone ~1 year ago.
I believe so that 4.3 is latest.
Before flashing 4.3, make sure you Sim unlock the phone first.
It sounds to me like its probably one of the following causing your issues....
Bad SIM card
Network problems on T-Mobile's end
Corrupted firmware or data
Or just part of the actual hardware going bad
(Listed what I think is most likely first)
Go to a T-Mobile store and ask an employee if they can test your device with their sim, or better yet, since its random ask if they can just replace yours.
Call T-Mobile to ask if there are any known problems in your area. If not ask if they can reset your account.
Flashing firmware with Odin (not mobile odin) can help determine if it may be a hw or sw problem. I do recommend factory resetting with stock recovery though. This actually formats /data, where custom recoveries just selectively delete things.
If its still giving problems after all of the above, its a pretty good chance some piece of hw has gone bad.
Thanks the replies guys, I'll report back with some results. Just wanna add, I've tried my sister's S4 LTE Sim on my phone and the issue still seems to occur regardless.
Sent from my SGH-T999 using Tapatalk 4
TheKucho said:
Hey guys, i'm having a bunch of connectivity issues, all revolving around cell service. WiFi works greats. First issue is that text message get sent and received sporadically(meaning sometimes i send texts and they send right away, while other times they fail and require a few resends). Second issue is incoming calls not reaching my device(doesn't even ring on my phone) and going straight to voicemail after 2 rings/outgoings calls not ringing at all. Last and hopefully least, data seems to drop or hang on upload after a few minutes of use. Now all these issues occur sporadically and at seemingly random times, but it seems like once one of these 3 issues occur, they all get triggered.
I've checked and reset APN settings and they seem correct, although instead of "Not Set" for the username, there is "none" and there is a four digit password that has been censored by *, and for Server there is one digit *.
I've called T-MO customer service and their suggestion to solving it was a Master Reset, which is essentially a Factory Reset including wiping the Internal SD card. I've yet to do this, but i have tried a regular Factory Reset from TWRP, but the issue still persists. Not sure what to do at this point, was considering ODIN'ing back to stock(4.1.1 root66 to be exact).
If it matters, I'm running Dandroid 4.1.2, with DLJA baseband and stock kernel. Sometimes rebooting or flipping airplane mode on/off fixes it for a couple more minutes.
Any insight or suggestion would be GREATLY appreciated. Thanks for taking the time to read this.
Click to expand...
Click to collapse
Funny that I came across this. I was experiencing (seemingly) the exact same problem very recently. I even picked up a new SIM card, but that didn't fix it. I was beginning to fear it was hardware related. But like Doc suggested, I used ODIN to flash stock fw, and all is well again. It appears that my problem was related to data corruption. Thought I'd post to confirm returning to stock via ODIN fixed the issue for me - in case it happens to anyone else.
Ditamae said:
Funny that I came across this. I was experiencing (seemingly) the exact same problem very recently. I even picked up a new SIM card, but that didn't fix it. I was beginning to fear it was hardware related. But like Doc suggested, I used ODIN to flash stock fw, and all is well again. It appears that my problem was related to data corruption. Thought I'd post to confirm returning to stock via ODIN fixed the issue for me - in case it happens to anyone else.
Click to expand...
Click to collapse
Thanks for the reply! Unfortunately I'm still experiencing this problem. May I ask which Android version you ODIN'd? If 4.3, MJC or NC2? I've ODIN'd two firmwares, 4.1.1 LJA and 4.1.2 MD5. I've held back on doing 4.3 because I know after that, there is no way back. But if that fixes the issue, I'm all in. Thanks!
Sent from my SGH-T999 using Tapatalk 4
TheKucho said:
Thanks for the reply! Unfortunately I'm still experiencing this problem. May I ask which Android version you ODIN'd? If 4.3, MJC or NC2? I've ODIN'd two firmwares, 4.1.1 LJA and 4.1.2 MD5. I've held back on doing 4.3 because I know after that, there is no way back. But if that fixes the issue, I'm all in. Thanks!
Sent from my SGH-T999 using Tapatalk 4
Click to expand...
Click to collapse
I used UVDLJA 4.1.1, and so far I'm free of the connection issue. I feel the same as you... don't want to flash 4.3 without being able to downgrade. I picked the LJA fw because that's what my phone shipped with, and the radio/bootloader combo always worked well for me. Sorry it hasn't worked for you! Maybe a stupid question, but did you factory reset after ODIN flashing?
Out of curiosity, did the issue resurface while you were still running stock fw? Or had you changed ROMs?
Ditamae said:
I used UVDLJA 4.1.1, and so far I'm free of the connection issue. I feel the same as you... don't want to flash 4.3 without being able to downgrade. I picked the LJA fw because that's what my phone shipped with, and the radio/bootloader combo always worked well for me. Sorry it hasn't worked for you! Maybe a stupid question, but did you factory reset after ODIN flashing?
Out of curiosity, did the issue resurface while you were still running stock fw? Or had you changed ROMs?
Click to expand...
Click to collapse
Yeah, I've factory reset from the stock recovery and had everything wiped. Well first the issue initiallly surfaced on the Dandroid 4.1.2 ROM, but I had ran that ROM for close to a year without any issues, then all of a sudden it happened. I ODINd the 4.1.1 and factory reset and at first I thought it worked but a few minutes later, the problem resurfaced, so to answer your question, yeah it still happened on stock fw. I may try it again just in case I take it in to a T-Mobile store.
Sent from my SGH-T999 using Tapatalk 4
Well since you ruled out the SIM card already, the 2nd part I mentioned would be my next suspect. (Network problems on T-Mobile's end. )
Is there any way you can get maybe 5-10 miles away from your usual locations and test there? (Remember to reboot after making it to a new location). If its still giving problems there, its very unlikely to be a tower problem. (Still possible, but very unlikely. ) Also, call T-Mobile support and ask if they can perform a reset on your account. (Can't remember what they call it exactly, but they should be able to take some sort of similar action on your account from their end.)
Finally, if you are still running 4.1.2 or 4.1.1 firmware, you can try flashing the different modems I have in my baseband thread. (Stickied in development). I can't remember right now if the 4.3 modems will work on the older firmware, but its ok to try them all. Once you update to 4.3 you can no longer use the older modems.
If, after all of that, you still are having trouble, you can pretty much rule out network problems. It'd still be a possibility, but only a very unlikely one.
After this, you might want to seriously consider flashing the MJC firmware, then NC2 if necessary. If none of that is helping I don't think there will be much more you can really do....
Was on nf1 and experienced lte data dropping out of nowhere. It happened once everyday, sometimes more than that. After a toggling data on and off it would work again.
I updated to NF4 and problems have continued. Anybody else having this issue?
sd97cl said:
Was on nf1 and experienced lte data dropping out of nowhere. It happened once everyday, sometimes more than that. After a toggling data on and off it would work again.
I updated to NF4 and problems have continued. Anybody else having this issue?
Click to expand...
Click to collapse
No.
I do see that when the phone transitions between 4G and LTE or vice versa, I loose data for a few seconds. But that is rare.
I've been experiencing this forever. Seems like no one else is though. Only thing I can do is toggle airplane mode on and off and deal with it...
Sent from my SM-N900T using XDA Free mobile app
I ues aosp. It goes from lte to h+ something. Is that considered data dropping?
polarbbr said:
I ues aosp. It goes from lte to h+ something. Is that considered data dropping?
Click to expand...
Click to collapse
If you can still use data than no. Data dropping is when it completely cuts out.
I have an N900t on T-Mobile but was experiencing the same random signal loss/no data issue as the OP after the 4.4.2 OTA and updating the baseband to NF4. Afterwords I rooted using the (CF-Auto-Root) for NF4 method and installed the Effortless 4.4.2 stock based ROM. Had the same signal issues so I went back to stock NF4. I immediately got notification for update to baseband NF9. Did the update and so far so good on the sudden random dropped signal issues. Now trying to figure out if the Rooting NF4 (CF-Auto-Root) still applys to rooting the phone after the NF9 update.
jackk said:
I have an N900t on T-Mobile but was experiencing the same random signal loss/no data issue as the OP after the 4.4.2 OTA and updating the baseband to NF4. Afterwords I rooted using the (CF-Auto-Root) for NF4 method and installed the Effortless 4.4.2 stock based ROM. Had the same signal issues so I went back to stock NF4. I immediately got notification for update to baseband NF9. Did the update and so far so good on the sudden random dropped signal issues. Now trying to figure out if the Rooting NF4 (CF-Auto-Root) still applys to rooting the phone after the NF9 update.
Click to expand...
Click to collapse
Would you mind posting a screenshot of your "About Device" page showing the baseband and build? TIA
Screenshot from my N900T
sd97cl said:
Was on nf1 and experienced lte data dropping out of nowhere. It happened once everyday, sometimes more than that. After a toggling data on and off it would work again.
I updated to NF4 and problems have continued. Anybody else having this issue?
Click to expand...
Click to collapse
Yes, I'm having the same issue. Usually turning on airplane mode then turning it back off fixes it. I updated to nf4 a few days ago and still have the issue. Stock t-mobile rom, not rooted, service with t-mobile.
WatermelonSlim said:
Yes, I'm having the same issue. Usually turning on airplane mode then turning it back off fixes it. I updated to nf4 a few days ago and still have the issue. Stock t-mobile rom, not rooted, service with t-mobile.
Click to expand...
Click to collapse
I'm nf4 and updating stopped the data drops on lte but on switching to 4g data takes about a minute to respond, on NB4 lte would become unresponsive. ..so that seems fixed for me on nf4.......i did a full wipe including internal sdcard and everything has been working fine except the handoff to 4g. Don't know if it helped but i took out sim during the whole process. Ran stock nf4 firmware with pc odin, then rooted and replaced custom recovery then booted to recovery wiped everything except External Sd then rebooted the recovery back into the recovery then flashed the rom I'm currently running.
In your case since your mostly stock I'd get the pc odin tar, remove the sim, then run odin and select the "update bootloader" switch (or something like that) and run it and then boot into the rom (still without sim) setup phone then power down and pop sim in and try the features again that you've had problems with.
(^^^just a suggestion, maybe someone else has a fix)
Also backup your internal sdcard prior just to be safe.