Hi guys.I seem to be in a small pickle here. Ill explain: I have an Note 2 - International N7105. This is what happened.
I wanted to use it on Wind Mobile (Canada, Same as T-Mobile Bands). So my brother took it to someone who apparently tried to do the Note 2 i337 AWS Bands Mod to it. Now this mod works perfectly fine with the AT&T Note 2 i337. But the guy who did it didn't know it is not compatible with the International LTE N7105. Anyways. He did it and it didn't work with Wind Mobile. I put in my local sim card that was working fine before (Bell) and it showed 1 bar for a few seconds and than it just said "No Service". The following is what i have done so far with no luck:
Downloaded the same "modem" as the rom shipped with. And flashed it via TWRP. Rebooted the phone and now it started connecting to Bell. I made a phone call and it worked, along with data. I thought everything is now fixed ----- Wrong .... The phone although it works making voice calls and data. But after a few mins it just drops the signal and says "No service" again and shows that circle with the line crossing through it. If you leave it alone for a few mins it catches signal and works again. But this keeps happening every few mins. And for the last 15 mins it has shown "No Service".
I went to GalaxyNote2Root.com and read the comments on the article where the guy shows people how to do the i337 Note 2 AWS Mod, and someone else who has the N7105 did the same thing as me and the website owner recommended that simply doing a factory reset or flashing a new rom should fix the problem. That user did that and still the problem remained. So i downloaded a stock N7105 Android 4.3 rom & flashed it on the phone. ----- Same problem. as before, where the phone connects and works and than after a few mins it looses signal and vice versa.
So i thought i would try to flash a custom rom. I downloaded and flashed: JediX20 ... and still same problem.
Normally in all the articles i have read about the Note 2 / S4 AWS Mod, using the QPST program they all recommend you make a backup of your stock .QNC file BEFORE flashing the AWS Modded .QNC file that gives you the AWS bands. (in the event that flashing the modded file fails, you can revert to stock with the backup). Can anyone provide me their stock .QNC file from their International N7105 Note 2? I think flashing it should fix this problem. Or if anyone can suggest something i can do to fix it i would be ETERNALLY grateful! Thanks guys.
therockk said:
Hi guys.I seem to be in a small pickle here. Ill explain: I have an Note 2 - International N7105. This is what happened.
I wanted to use it on Wind Mobile (Canada, Same as T-Mobile Bands). So my brother took it to someone who apparently tried to do the Note 2 i337 AWS Bands Mod to it. Now this mod works perfectly fine with the AT&T Note 2 i337. But the guy who did it didn't know it is not compatible with the International LTE N7105. Anyways. He did it and it didn't work with Wind Mobile. I put in my local sim card that was working fine before (Bell) and it showed 1 bar for a few seconds and than it just said "No Service". The following is what i have done so far with no luck:
Downloaded the same "modem" as the rom shipped with. And flashed it via TWRP. Rebooted the phone and now it started connecting to Bell. I made a phone call and it worked, along with data. I thought everything is now fixed ----- Wrong .... The phone although it works making voice calls and data. But after a few mins it just drops the signal and says "No service" again and shows that circle with the line crossing through it. If you leave it alone for a few mins it catches signal and works again. But this keeps happening every few mins. And for the last 15 mins it has shown "No Service".
I went to GalaxyNote2Root.com and read the comments on the article where the guy shows people how to do the i337 Note 2 AWS Mod, and someone else who has the N7105 did the same thing as me and the website owner recommended that simply doing a factory reset or flashing a new rom should fix the problem. That user did that and still the problem remained. So i downloaded a stock N7105 Android 4.3 rom & flashed it on the phone. ----- Same problem. as before, where the phone connects and works and than after a few mins it looses signal and vice versa.
So i thought i would try to flash a custom rom. I downloaded and flashed: JediX20 ... and still same problem.
Normally in all the articles i have read about the Note 2 / S4 AWS Mod, using the QPST program they all recommend you make a backup of your stock .QNC file BEFORE flashing the AWS Modded .QNC file that gives you the AWS bands. (in the event that flashing the modded file fails, you can revert to stock with the backup). Can anyone provide me their stock .QNC file from their International N7105 Note 2? I think flashing it should fix this problem. Or if anyone can suggest something i can do to fix it i would be ETERNALLY grateful! Thanks guys.
Click to expand...
Click to collapse
i337 is Galaxy S4. i317 is AT&T Galaxy Note 2 (i317M is Rogers model). I think that unless you have a QCN file from before the flash, you're screwed unless you can get one from another N7105 user and edit out the IMEI and flash it to your device.
Related
HI,
I'm having this error message on boot and I can't find a solution. Every search I've made for this error comes up empty. The final solution being restore to factory. After doing that and trying to reinstall the rom I get the same error. Phone FC and i don't get time synched from the network anymore.
I'm not using TB. I'm not restoring any data. This is on a fresh clean install of the rom.
Any ideas? I need help!
What did you flash in terms or rom, mods, themes, and how did you flash?
Sent from my Galaxy SII T-mobile using Tapatalk 2
I flashed the new Darkside rom with the TMO base. I'm starting to think that the new base is conflicting with my sim card... I'm not sure what to do about it... I'm with Virgin Mobile in Canada if that makes any difference...
No mods and no themes. Its just on first boot. Any other base seems to work fine. But since the TMO base I get that FC.
Could be a bad download, unlikely but if you haven't tried yet re-download the ROM
I've redownloaded multiple times and checked the md5... so the dl itself is fine... the install is fine... but once it connects to the network com.android.phone force closes... Do you know how to reset the network settings on the sim card itself?
process com.android phone has stopped
Hi,
My HTC One XL from Rogers is doing this when the address book syncs in the car. I have it de-bloated, rooted, and unlocked boot loader. My problem is that nothing seems to have changed. The phone works (Bluetooth )in the car until the address book is synched (or so it seems), then it cuts out. What to do?
Same problem with my ROM. I am using Reliance GSM in India. I tried with Vodafone & Airtel SIM and the phone works perfectly normal. Tried with my Dad's Reliance GSM and the problem is back. Dunno what the problem is exactly. Other ROMs work perfectly fine with Reliance in my cell. Problem is only with this one ROM. Incase you stumble upon a solution, pl do let me know as well.
My Original ROM with the same error
Hello everyone
My phone is Samsung S3, with original software, it asked me to update the system and i agreed after that i found it add some information such as it;s from United Emirates but i live in kuwait, and now i have the same error only when i try to make international call.
please any help without reset the phone?!!!
On some ROMs, they say it has something to do with the DPI
I've encountered this problem on AOKP 07/09 Milestone 6, and from searching in the forums, all I could gather is that it has something to do with my DPI settings.
On 07/05 it was okay, I just don't get it why flashing to 07/09 made this error appear.
UPDATE Now I discovered that turning the phone into Airplane mode removes this error. But then if you deactivate airplane mode again it comes back.
msanl said:
Hello everyone
My phone is Samsung S3, with original software, it asked me to update the system and i agreed after that i found it add some information such as it;s from United Emirates but i live in kuwait, and now i have the same error only when i try to make international call.
please any help without reset the phone?!!!
Click to expand...
Click to collapse
Why dont you post in the S3 forum?
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
Hey there,
I'll try to be as specific as I can about this... So basically, I have the i747 through AT&T but am currently out of the country (in Japan) for a couple months and am using a prepaid data only SIM. Phone is unlocked and data works fine on stock, but I've tried flashing for the first time since leaving the US (with BeanStalk 4.3, MIUI, and LiquidSmooth using first CWM, then TWRP) so I'm guessing this isn't a particular ROM issue.
I'm unable to connect to the Japanese Docomo network when I flash. The phone recognizes the network, IMEI is still intact, but the APN is gone (so I tried APN backup/restore to get the option back, but still no data). Then I reflashed most of the i747u modems, also to no avail.
Also got out my AT&T SIM, which still works on stock. APN shows up, but no voice/data.
Anyone have an idea of what the problem could be? Any other options I missed? As a disclaimer, I don't really have experience beyond clearly written directions posted here, but I read a lot before I try anything and have been flashing my last couple phones with good success.
Thanks so so much to anyone who reads
A few weeks ago I went to China and I brought my Wind Mobile issued T889V. While there I realized that the phone was sim locked so I took it to a place to have it unlocked. Before I got the phone back I was able to use another phone, so I did not realize the problem until I returned to Canada. I do not even know what it was they did over there.
The problem is that I just cannot receive a signal from Wind. I know the screenshot shows full bars, but the phone has remained "no service" for the past several days. So far I've tried hard reset, flashing the rom, flashing the modem (with several different files), all with no luck. Yesterday I took it a phone repair place and the guy told me that it was something wrong with the NV settings. He also told me that he has changed it to the correct settings, but I am still not getting anything. Any help here would be greatly appreciated. Also, please explain like I am 5. Thank you.
Edit: I've tried the NE7 before the NH2 modem file, did not make a difference.
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?