Develop Bugs

[Q] Lost IMEI now stuck in boot loop after ODIN to 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

[Q] Poor mobile data connection after loss and subsequent reinjection of IMEI

Hello everyone, please excuse my noobness. I have spent two days now searching and trying to solve my issue, but no luck. Here are the series of events:
1. rooted i747 and got cwm 5.5
2. flashed liquidsmooth with cwm 5.5 and gapps
3. everything was fine (i think)
4. i tried to flash cm 10.1 with cwm 5.5 not realizing i needed 6.x and the flash failed
5. restored to my liquidsmooth back up
6. realized my imei was 0 at this point and no cell signal
7. used odin 3.07 to flash back to stock 4.1.1 rom from samsung
8. injected my imei using NV items reader writer method
After this sequence of events, regardless of the rom (stock, cm, liquidsmooth), my modem connects to LTE and is fine while i'm using it, but then after idling for 20 mins or more is on GPRS. Sometimes it has no data connection whatsoever. If i go to airplane mode and then come back out of airplane mode it will find the LTE tower and be fine again until I leave it alone or use it for more than 20 minutes.
I am using the correct APN (phone or pta on ATT)
my IMEI is correct under status in the about section in settings.
I have also done this : http://forum.xda-developers.com/showthread.php?t=2036891
i have also flashed my modem with this rom : I747UCDLK3_I747ATTDLK3_ATT (My baseband version is UCDLK3) from this thread: http://forum.xda-developers.com/showthread.php?t=1831898
The issue isn't that I can not connect to HSPA+ or LTE ... the issue is I lose that connectivity after 20-30 minutes and can not gain it back unless I toggle airplane on and off.
Any help or suggestions would be greatly appreciated.

I wanted to update this thread, in case others had the issue.
There was no solution that could be found. I ended up taking the phone in to ATT after resetting to factory defaults and resetting the flash counter. They replaced it and now on CM10.1.2 with normal functioning radio.

[q] lost my 3g

I can't seem to fix my signal after flashing a ROM anymore. only get 1x which is only better than no signal at all. At one time in the earlier releases of M.O.A.R I was getting LTE and 3G with no problems then later releases I've lost both. I unrooted and went back to stock and my 3G was back and rooted again, went back to MOAR and still no 3G. So now I'm on beenstalk and still cant get a signal. I love both of these ROMS hands down and would like to fix this issue without experimenting with every ROM in the forum. Has anyone else had this issue? I've resetted radios flashed different modems (except MK3) and I still end up with bad network. I need help

Open the dialpad, and then ##72786# . The Device will reboot a few times. Just let it do it's thing. It will go through the Handsfree Activation Process. This will reset your Data.

[Q] Problem with Signal/Service - weak Signal, breakdowns

my device now: i9195, I9195XXUCNE6-DBT
I experience weak signal and many connection dropdowns. When this occured first, after i upgraded f4ktion Kernel 1.3.6 to 1.4.5 and
an older version of Carbon Rom (4.2.2) to 4.3 Carbon Rom. Until than everything was fine, flash of rom and kernel did not made any problem.
Btw i used Odin3 3.09 and clean install (step by step like in the guides) all the time.
After some days this realy annoyed me, so i went back to the older Carbon and kernel - problem still occurs.
So i went back to stock rom I9195XXUBML4-DBT (original was UBML4) - problem still existing.
Some time later f4ktion 1.5 and Carbon 4.4.4 was available, so i tried this..still no solution.
Now i am back to stock and updated to I9195XXUCNE6-DBT, same problem.
Some research told me many ne stuff to know..like flashing modem only. I tried some, nothing helped.
After hours of pointless googleing i noticed something on my phone.When i dont type the pin, i have normal signal. As soon as i type the pin
and "activate" my simcard, the signal strength drops. So i googled again and found this:
[Bug Watch] Android 4.3 Radio Bugs Causing Cell Connection Drops On Some Nexus 4 Handsets, Fixes In Sight (not allowed to post links)
I changed the network type to WCDMA only - it helped for some minutes(not many..maybe 2-3). I changed to GSM only and i had normal,
stable signal for like an hour. But later signal loses strenght again, and i need to change network type again.
I have the feeling, that its like a reset or restart of the radio.
But now i am all out of ideas and need some help.
Last thing i can do, is to bring it to repair. But my Knox says 0x1, so maybe you can help me before i ask Samsung.

I have similar problem since ugrading to KitKat roms. I had no problems with previous none Knox roms with MH3 modem but now with NE6 and NF7 KK modems the signal swings constantly up and down from 4 to 1 bars. This is in areas I previously had good signal. Internet also keeps dropping out requiring data toggling on and off. I've reflashed KK 20+ times and haven't been able to get rid of this problem yet.
I'm not sure if pre knox modems are installable but I intend to try and reflash MH3 modem, once I manage to do a successful backup.

I solved a similar problem by downgrade to 4.2.2 Brazil NE2, knox 2. Flashing separate modem (NE2), and reflashing full rom again. No problems for now

Now you stay on 4.2.2 ?
I dont understand why some people do have problems and some not. Is there different hardware version causing the trouble ?
Give me pls some information how you did the downgrade.
-Nandroid Backup
-philz
-Odin (if yes which version)
-why did you choose that rom
I tried to, but wasnt succesfull. I used Odin3 3.09 to flash 4.2.2 (UAMF5 i think) rom and got a brick. When trying to fix this nothing helped until i tried to flash with Odin3 3.04. But all i could do was flashing newest FW again. Did not test more after that, because i was very busy.
If you say that going back solved your problem, i will try again go go back myself. I've found some information on that and when its done i give some informations.

Same here, help?
I'm having the same problem with a newly acquired handset. I have full signal on some places and nothing on others, unfortunately in my house I have no signal! So it's quite exasperating.
My baseband version is I9195XXUCNE6
Android version is 5.0.2 with 3.4.0-cyanogenmod-g92aec50 [email protected] #1 kernel
Cyanogenmod version is 12-20150306-UNOFFICIAL-serranoltexx
Would it help if I flash a separate modem file through Odin? In that case, which one should I flash?
Any help would be appreciated a lot.
Thanks

franzasensi said:
I'm having the same problem with a newly acquired handset. I have full signal on some places and nothing on others, unfortunately in my house I have no signal! So it's quite exasperating.
My baseband version is I9195XXUCNE6
Android version is 5.0.2 with 3.4.0-cyanogenmod-g92aec50 [email protected] #1 kernel
Cyanogenmod version is 12-20150306-UNOFFICIAL-serranoltexx
Would it help if I flash a separate modem file through Odin? In that case, which one should I flash?
Any help would be appreciated a lot.
Thanks
Click to expand...
Click to collapse
If you have warrenty left then you should go to customer service then they will change your mainboard. and it would bw okay.

Poor Cellular Reception After COI5 Firmware Update

I flashed the firmware for COI5 manually via odin and ever since then I cannot connect to LTE. Furthermore, I can barely connect to any signal. The bars show up, but it often takes a while for the 4G icon to show up. When it does, I am still not able to place a call, with Wi-Fi calling being the only hope I have to do so, but calls placed to me that way go straight to voicemail, so I have to call out from my phone.
Note: Knox is tripped, as I was rooted. I am also in an area where I alway get full bars of LTE, so location is not the issue.
Troubleshooting steps I have tried:
Reflashing COI5 firmware via odin.
Adding the LTE APN for T-Mobile.
Using Smart Switch to do emergency recovery.
Flashing BOH6 firmware (did not work as I don't believe you can downgrade firmware, was worth a shot anyways).
Flashing different custom ROMs (all repeated the same problem, which is how I narrowed it down to having to do with the firmware).
I am currently running completely stock at the moment. If anybody has any suggestions on what I should try next or how I can fix this, I would greatly appreciate it.