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
Hello all,
I tried searching for a similar scenario but wasn't able to find anything so I thought I'd try posting here.
I purchased a flashed Sprint Samsung Galaxy S3 from ebay about 6 months ago. I'm assuming the phone is rooted, I had my number flashed with page plus service to the S3 without problem and it has worked fine since then. Apart from the initial flash to page plus by the ebay vendor I've used the phone daily without flashing anything else, just using apps from the store and basic daily functions like email, social media and camera use. Today while using the phone it randomly shut off. When starting up the phone again it gets stuck on the "Samsung" logo, it does not reboot either.
I know that a hard reset can fix this issue but the problem is I believe a hard reset might break the page plus flash and I'm afraid of losing the number I have on this phone. Has anyone experienced this problem with a phone flashed to page plus and has successfully fixed this? Or will I just have to buy a new phone to flash my page plus number to?
Write down your flashed page plus number to external paper and after hard reset flash it again using dfs software.
Or if you don't want to hard reset... Flash the tar file via Odin to repair the stuck boot then root it.
But i recommend to flash a new rooted ROM from recovery after wiping data/factory reset.. It will not wiping your flashed status.
Sent from my SPH-L720 using Tapatalk
update
Thanks for the reply, unfortunately I don't really flash on my own and didn't quite want to experiment just yet.
What I ended up doing was esn swapping the page Plus number I was using from the Sprint s3 to an htc rhyme that was also activated on page Plus in a hope of salavging my #. I then went ahead and factory reset the s3 and that fixed the stuck on boot problem.
My question is now this, would it be possible to esn swap the number back to the s3 and have it function on page plus once again. from what I can tell in the settings it still has the 65002 prl I believe is uses to flashthis model and my orginal phone number still appears in the s3 device settings (and 3g username aferrad) despite my swapping the number to the rhyme.
I would be happy to provide addtl info and appreciate any help you can offer.
Hi,
I recently rooted an Ace 2 that came to my hands and flashed the CM11 found here.
After this wifi wasnt working so I tried some other MODEM drivers with no success.
Decided that I'd prefer having a WiFi enabled phone even with stock rom, I flashed the Stock one found on Sammobile for the phones' carrier.
Carrier is Bell Canada by the way.
After flashing the stock rom, phone refuses to get into recovery mode, and also refuses to open in generaly, staying in the GT-S7560 bootup screen for an eternity (or at least the 7 hours I left it open).
Phone works in Download mode however, except whatever I do there is like pointless, since nothing happens.
So a quick view is:
1) Bell Canada
2) S7560MVLBNA5
3) Recovery doesn't work
4) Download mode works
5) Phone won't start
If anyone can point me to something I would appreciate it, and as of searching before posting, I did search but found 0 similar problems, since everyone elses semi-bricked devices, worked like a charm after stock rom was installed.
Thanks in advance.
Ok, I give up.
I throw my hands in the air and pray to the tech lords here.
I have reflashed my phone probably 50 times in the past two weeks. And short of a Wifi-only phone at this point, I'm really needing to back track and understand what it is I'm doing (or not doing) right or wrong.
Here's a brief history of my living hell the past two weeks:
1. Get brand-new SGS4 Mini (GT-I9195)
2. Commence to screwing it up royally
Actual Detailed History
1. Get brand-new SGS4 Mini (GT-I9195)
2. Play with it a day
3. Root
4. CWM
5. Install Cyanogen 11
6. Enjoy a bit
7. Decide I need to flash it back to stock
(cue dark and menacing music)
8. 50 Flashes and several near-soft-bricks later
9. I am back on a stock ROM
10. The stock ROM seems like it works just fine
However...
Each and every time I power up the phone and enter my SIM pin (4 digits, normal pin to use the chip), I get:
SIM NETWORK UNLOCK PIN
History of this phone is a new purchase from Movistar, Costa Rica. It was delivered unlocked new, out of the box, and had no restrictions whatsoever. At the point I first got it (day one), it worked on both KOLBI and MOVISTAR SIM chips. Now, only Movistar.
My theory is that I believe, somewhere, somehow, in the series of 25-30 mad flashes I performed over the past several weeks, I have managed to screw up the combination of REGION and/or MODEM and/or CSC to the point that this phone simply is very confused.
DESIRED RESULT: Please get me back to a network-unlocked state.
you ever got this fixeD?
Reset your APN Settings
Why you have flashed 50 Times your ROM ?
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?