So, here's my situation:
I'm running a CDMA Gnex with Apex v.1.0.1 as my rom. I flashed a new radio, [Radio Hybrid] VZW EK5 CDMA(4.0.2) / EK4 LTE(4.0.3), in the hopes I could improve the hand off between 3G and 4G... Nope! The phone will no longer, no matter what I do, connect to the 3G network
OK... I figure, no big deal. I'll just flash a different radio set. Next up were the Leaked 4.0.3 Radios. Same thing. NO 3G at all!
Now I'm getting worried. I flash the stock 4.0.2 radios... Still cannot force it to use the CDMA network. I either have 4G data service or none at all...
What am I doing wrong? I've re-booted each radio set a couple times before dumping them for a different set. I've restored the nandroid back up from before I started messing with the radios. No fix there either. I've removed the sim card and reinstalled it (knowing full well it only controls 4G). Nothing doing...
I've seen similar posts about 3G/4G connectivity issues, but mine is strange because it's just the 3G radio that doesn't work. Voice calls and 4G data work fine.
Bigxie's rom has been rock solid, and since all the radios I've used presented the same issue, I'd be hard pressed to say it was one of them. I'm a noob, so I'm thinking user error somewhere along the line. Any help would be appreciated.
Update:
This was a CDMA network issue, not an issue with the Radios or Rom!!!
I magically picked up 3G this morning while at work. Since I was still running the leaked 4.0.3 radios and the Apex Rom, I realized that this was a network problem, not a software problem. I confirmed this with Verizon just now. They brought down the node closest to my place for emergency repair last night. The CDMA radio came back up as soon as it hit a tower that let it authenticate... It was just a coincidence that it occurred right when I flashed my first radio set, and frankly I feel dumb that I didn't see network error as a possibility sooner.
Try going all the way back to stock with stock radios and see if that fixes it?
http://code.google.com/android/nexus/images.html
flash the bootloader before the radio, reboot after flashing the
bootloader then flash radio, reboot, then flash stock.
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 have spent countless hours restoring the stock firmware, re-rooting, updating, and even replacing the SIM in order to figure out why out of the blue during a simple reboot my S3 decided not to communicate with anything but Edge and an ocasional call. The IMEI was set to zero and now is reset (using QPST) and the phone is talking to the network just fine (according to several senior level support techs!). WIFI is working. The modem signal strength is weak.
d2att_I747UCUEMJB_modem
I am back to running @PwnCakes193 4.4.2 Quantum ROM and I am at a loss! No LTE, 3G, and poor signal quality.
ANY help would be greatly appreciated! I have been flashing ROMS and android devices for YEARS and never have I been so stumped!
btafoya said:
I have spent countless hours restoring the stock firmware, re-rooting, updating, and even replacing the SIM in order to figure out why out of the blue during a simple reboot my S3 decided not to communicate with anything but Edge and an ocasional call. The IMEI was set to zero and now is reset (using QPST) and the phone is talking to the network just fine (according to several senior level support techs!). WIFI is working. The modem signal strength is weak.
d2att_I747UCUEMJB_modem
I am back to running @PwnCakes193 4.4.2 Quantum ROM and I am at a loss! No LTE, 3G, and poor signal quality.
ANY help would be greatly appreciated! I have been flashing ROMS and android devices for YEARS and never have I been so stumped!
Click to expand...
Click to collapse
I am having the same issues after flashing Validus 5.0 RC1 (Kitkat 4.4.2) I am back on CM 10.2.1 now and it has been holding signal, but it still drops occasionally. I was wondering about flashing back to stock and re-rooting re-flashing.. But, not sure if a) that will work b) which stock to flash back to (I originally rooted from 4.1.2 if I remember correctly
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
Problem started about a week ago. Whenever i go into an area without signal coverage, and later, return to an area with coverage, my oneplus 3 is unable to reconnect to the network.
Only fix is a reboot, but re-occurs when i go into an area without coverage...
Phone was working great before. Issue started after the update to 3.2.2.
I performed factory reset and reflashed to stock rom (3.1.2) but problem still occurs ...
Anyone else experiencing this issue?
Bouilfr1987 said:
Problem started about a week ago. Whenever i go into an area without signal coverage, and later, return to an area with coverage, my oneplus 3 is unable to reconnect to the network.
Only fix is a reboot, but re-occurs when i go into an area without coverage...
Phone was working great before. Issue started after the update to 3.2.2.
I performed factory reset and reflashed to stock rom (3.1.2) but problem still occurs ...
Anyone else experiencing this issue?
Click to expand...
Click to collapse
As a follow up on this. I'm thinking it has something to do with my radio/modem. As this is probably not updated when i flash a new rom, I'm thinking i should just flash the stock radio/modem. But I don't know how.
Does someone here know how to flash back the stock radio/modem?
Thx in advance!