Good Afternoon everyone,
I've been experiencing issues with my Mobilicity S3 T999v.
I recently removed root from the device, and am having issues with the network service. It connects to my service provider koodo, but nothing works. When trying to connect manually it just times out forever.
I have verified i have an IMEI, via *#06# , the phone worked fine before the unrooting. Ive attempted flashing stock firmware a few times now with odin to no avail. Could this be baseband related?
If it makes any difference i used Mskips toolkit for all the rooting/unrooting. Device software still says modified after triangle away.
captaincheese said:
Good Afternoon everyone,
I've been experiencing issues with my Mobilicity S3 T999v.
I recently removed root from the device, and am having issues with the network service. It connects to my service provider koodo, but nothing works. When trying to connect manually it just times out forever.
I have verified i have an IMEI, via *#06# , the phone worked fine before the unrooting. Ive attempted flashing stock firmware a few times now with odin to no avail. Could this be baseband related?
If it makes any difference i used Mskips toolkit for all the rooting/unrooting. Device software still says modified after triangle away.
Click to expand...
Click to collapse
Im going to re-install root via root66, and try a different baseband. Ill let you guys know the results.
captaincheese said:
Im going to re-install root via root66, and try a different baseband. Ill let you guys know the results.
Click to expand...
Click to collapse
ugh didnt go to well. Constant errors about android.process has stopped responding. Think im going back to stock the root66 files are not working for me.
I guess another day of tablet as my phone. :crying:
Related
*Bad english ahead*
The problem is that my phone seems to refuse to get any service at all. The signal icon just shows a big "X" and it is stuck in "Searching for service".
Phone status shows that the Signal strenght is on -79 dBm, so i guess the anthena is working just fine. But below Service Sate it just shows "Out of service".
Im using a EB13 Modem with the SyndicateROM.
In fact, the phone was working just fine with MidnightROM until i flashed the SyndicateROM over.
Already tried reverting it to Stock rom and nothin, any suggestions?
Did you try reflashing (Just) the modem through ODIN?
Let me try...
Does this one should work? (The odin one)
http://forum.xda-developers.com/showthread.php?t=963774&highlight=modem.tar
Here is a direct download link
Click Me!
Did you flash your Epic to Telcel? If so, that process might be causing you some problems. After using Odin to get back to stock, install CWM3 then SRF1.0.1, then once you're stable there, try the carrier flash again.
063_XOBX said:
Here is a direct download link
Click Me!
Click to expand...
Click to collapse
Thanks but it didn't work. Still stuck with no service.
Did you flash your Epic to Telcel? If so, that process might be causing you some problems. After using Odin to get back to stock, install CWM3 then SRF1.0.1, then once you're stable there, try the carrier flash again.
Click to expand...
Click to collapse
What do you mean by "Flashing my epic to telcel" and that "Carrier flash?" is on Iusacell, since Telcel dont support CDMA.
And one last thing, what is SFR1.0.1?
EDIT:
Im reverting back to DI18 Stock rom with odin to see if i can do something.
Homeroe said:
What do you mean by "Flashing my epic to telcel" and that "Carrier flash?" is on Iusacell, since Telcel dont support CDMA.
And one last thing, what is SFR1.0.1?
Click to expand...
Click to collapse
Oh okay - the banner under your username says Telcel, so I figured they were it. I thought I'd read they support CDMA but I was mistaken.
SRF1.0.1 is SyndicateROM Frozen 1.0.1.
On the flash, let me rephrase - did you do anything special to get the Epic to work on Iusacell, or did it work there out of the box?
That's the reason then. You can't change ROMs if you're on a carrier other than Sprint, it will revert your phone back to Sprint.
k0nane said:
Oh okay - the banner under your username says Telcel, so I figured they were it. I thought I'd read they support CDMA but I was mistaken.
SRF1.0.1 is SyndicateROM Frozen 1.0.1.
On the flash, let me rephrase - did you do anything special to get the Epic to work on Iusacell, or did it work there out of the box?
Click to expand...
Click to collapse
Nope, the phone was working just fine out of the box. It had signal (Roaming) and all.
I even flashed like 3 roms before Syndicate and it was working just fine. Was just yesterday that i decided to try this ROM out and got the problem.
Homeroe said:
Nope, the phone was working just fine out of the box. It had signal (Roaming) and all.
I even flashed like 3 roms before Syndicate and it was working just fine. Was just yesterday that i decided to try this ROM out and got the problem.
Click to expand...
Click to collapse
I'm not entirely sure what to tell you - there's nothing in SRF that should/will/can cause any problems of that sort. Going back to full stock via Odin didn't help?
I followed this guide: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700 to return to Stock rom, but i can't get this thing working
Im pretty much lost as well.
EDIT:
Oh god what the... I was just messing around with the phone. Turned on the Flight mode. Made a Factory reset via Privacy setting, Rebooted the phone, turned off the a Flight mode and suddenly had signal again.
I dont know what happened, since i tried the factory reset before with no luck... But well, im glad its working now. Thank you to both of you for the help anyways.
I have a similar problem as the OP, and I'm pretty sure it's ClockworkMod that's causing it.
Seems like every other time I do something in CWM, I get no service and an unknown Baseband and Hardware version in the phone's settings.
So far the only reliable way I've found of fixing it is to Odin all the way back to DI18 and start fresh.
For some reason Odining the modem or EB13 doesn't work (I still get no service).
And I must say, it's incredibly frustrating.
I guess I'll just have to get SRF flashed and never touch CWM again (because doing so almost always breaks my phone).
I'd like to be able to make Nandroid backups though, but unfortunately, doing so breaks the modem (which really doesn't make any sense).
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've gotten my phone into a state where I see signal bars, I can make calls and send texts, but no LTE or H+ is displayed and if I try do anything involving the internet it says there's no network connection. Wifi works just fine.
Here's how I got into the predicament. I should have learned my lesson from last time I flashed a Verizon ROM, but I didn't, and I flashed SkyNote RC9Z-3.9.1. Data works just fine in THAT ROM, but any subsequent ROM flashed after that... the network data is completely HOSED. I've tried enabling and disabling network data in settings. I've tried flashing the Devil kernel. I've tried restoring several different ROMS from nandroid backups. All restore fine and all have completely non-working network data. Last time I ran into this I had to flash the stock image in Odin to fiz the issue. This time however, that didn't work. The images flashed successfully, but upon reboot all I got was a a welcome screen bootloop of the samsung swirly logo and the T-Mobile logo.
I'm guessing this has something to do with the 4.3 bootloader? I'm downloading T889UVUCMK7_T889TMBCMK7_TMB.zip from SamMobile site and boy is it taking FOREVER! 7 hours left on the download. My thinking thoug is that If I unzip this new 4.3 firmware and flash it with Odin (or Kies if I absolutle have to) my device will start behaving again, and Network data will work, and I can go about ROM flashing and hopping again (though I'm gonna stay away from those Verizon ROMs let met tell you!).
Does anyone else have any other suggestions on what I can do to get my data back or to patch my bootloader to the 4.3 version? I was looking at this thread and wondering if it's safe to follow this procedure for patching once I have installed the 4.3 stock image:
http://forum.xda-developers.com/showthread.php?t=2500823
Any help is appreciated.
ddi you check your APN settings?
Probably your apn like iamsixnine said
Sent from my GT-I9305 using Tapatalk
Okay so i have the T-Mobile Galaxy s3. It has been rooted for a while with zero problems. I got tired of the older android on it and decided to install a rom. I installed Cyanogenmod 13.0-20151208-unofficial-d2tmo running android 6.0.1. When i first got it all booted and loaded with gapps, i noticed that it recognized my sim and that i had a signal but i couldn't use any LTE or just all around data. basically i couldn't go online (in case i just didn't explain that well enough. Phone service is a mystery to me). I did some searching online and found a lot of people saying that i needed to update my baseband. i found a baseband for my model (T999) and tried to flash it in TWRM. Once i rebooted, it said "No SIM card - No service." in the upper left-hand side. i have tried flashing multiple different basebands the same way with no luck. i tried backing up my EFS folder and the restoring it because someone said to do that and that just... just no... it didn't do anything. even Odin 3 said it was a "FAIL!". So here i am with this android equivalent to an Ipod and i hate this. Everything else in this ROM works perfectly aside from this but this is a super big problem. PLEASE HELP!!!! A phone isn't a phone if you cant even send a text.
Did you update the phone's bootloader and modem to the latest version before flashing CM?