To give a back story on what I'm trying to accomplish, I'll explain my situation.
I work for Bell, in a retail store, the main reason I came to these forums was to find a way to re-flash phones in store to avoid having to doa what little stock we have of the phones. One of my colleagues from another location told me about the new update from Kies locking phones up at a ridiculous rate of 25%, so I'm trying to be pro-active about it.
Once I got in, I got a bit carried away with 2.2 software and what not. Now, i'm no expert, but I'm computer literate and made sense of most of the process, some extra guidance would be nice though.
Playing with the phones we have in store, I was able to flash every available software I could find on said phones, however a constant issue is found. I can not get a solid data connection. If I disable data, everything works fine, soon as I turn it back on, nothing happens.
Furthermore, I followed a thread regarding re-flashing everything back to Bell's stock settings and it didn't help me along at all.
I have done some searches, but i'm coming up dry. I know you've probably heard this hundreds of times and I'm sorry for being new to the process, some guidance towards this all would be great.
Bellkingsway said:
however a constant issue is found. I can not get a solid data connection. If I disable data, everything works fine, soon as I turn it back on, nothing happens.
Click to expand...
Click to collapse
Can you elaborate more on this?
what do you mean by unable to get a solid data connection?
what kind of data connection are you referring to?
USB cable between phone to PC?
or Wifi data
or APN (3G) data?
Bellkingsway said:
I work for Bell, in a retail store, the main reason I came to these forums was to find a way to re-flash phones in store to avoid having to doa what little stock we have of the phones. One of my colleagues from another location told me about the new update from Kies locking phones up at a ridiculous rate of 25%, so I'm trying to be pro-active about it.
Click to expand...
Click to collapse
not sure where you got that number from, but it's not that accurate
the reason for the ridiculous high amount of returned phones is due the Internal SD card problem that was found.
even under normal conditions if it gets formatted a lot or used a lot it seems to die faster than its Europe counterpart.
apparently on the Canadian version of the I9000 they use a bad batch of Flash Disk for the storage memory
there is a sticky Topic Poll about it.
it is NOT the ROM flash from Kies that are killing the units, just anything software that constantly access the internal SD can produce the same effect.
http://forum.xda-developers.com/showthread.php?t=793404
the rest of the returns you guys at Bell are seeing are due this other problem discussed here http://forum.xda-developers.com/showthread.php?t=775017
it can be reproduced, but you need the ideal conditions to do it.
it has to do with signal quality and tower availability
AllGamer said:
Can you elaborate more on this?
what do you mean by unable to get a solid data connection?
what kind of data connection are you referring to?
USB cable between phone to PC?
or Wifi data
or APN (3G) data?
Click to expand...
Click to collapse
I'm referring to 3G connection. I have set up the APN, even tried different settings, all producing the same results.
In regards to your second reply, the phones I've seen at this location for DOA's have mostly because of a failure to fully turn on, the display won't show. I've experienced similar issues when a flash doesn't work properly, a re-flash fixes it. We started seeing this issue after samsung released the update. However, I'm not going to flash a customers phone to have them lose 3G connectivity, or open up other issues.
Basically, I'm looking for two things. Primarily a way to re-flash everything to work as if it were out of box, with the latest software update. Secondly, to be able to get a stable 3G connection on 2.2, everything else seems to work fine at this point.
i'm not even going to touch the 2.2 topic as it's not even released officially.
the current stable official flash is JH2, on JH2 3G should work properly (stable), another thing you can do is to go into the service menu using the secret codes (wiki) and make sure the proper 3G bands are selected for WCDMA
1900 and 850 should both have a start next to it
next check is the *#0011* to see if the towers keeps constantly changing
that's another reason for unstable 3G if the phone keeps jumping towers every few seconds
this is also related to the 2nd link i mentioned about people getting Comatose Syndrome on the phones, which locks up the phone, and they have to reset the phone to get the phone to work again.
I'm running JH2 currently, I ran *#2263# 850 and 1900 are available. Also, ran *#0011# both are available, ran a test on youtube it worked for 5 minutes.
Any ideas?
**Edit**
I lied, on the *#0011# it only shows 1900.
Bellkingsway said:
the phones I've seen at this location for DOA's have mostly because of a failure to fully turn on, the display won't show. I've experienced similar issues when a flash doesn't work properly, a re-flash fixes it.
We started seeing this issue after samsung released the update. However, I'm not going to flash a customers phone to have them lose 3G connectivity, or open up other issues.
Click to expand...
Click to collapse
Get something straight
the update samsung released was JH2, and it is not causing the problems you've seen.
the problems with the symptoms described are after they were flashed by the Alpha & Beta versions of Froyos 2.2, which many of them do end up losing the 850 band, the band issue can be fixed with much work.
there have been at least 4 different leaks of froyo, each one bringing its own volume of chaos and bugs, the most dangerous 2 are JPH and JPK, one loses the IMEI / ESN number ID, the other one kills the internal SD
Bellkingsway said:
I'm running JH2 currently, I ran *#2263# 850 and 1900 are available. Also, ran *#0011# both are available, ran a test on youtube it worked for 5 minutes.
Any ideas?
**Edit**
I lied, on the *#0011# it only shows 1900.
Click to expand...
Click to collapse
Since the I9000M and I9000 are hardware based bands, you should always have the 850 and 1900 bands for 3G
Many who have tried Froyo and back had come across the problem of losing the 850 band, mainly because the Froyo leaks were intended for the Korea test team running international I9000 devices
some times just by flashing the Firmware back to stock or Froyo betas doesn't actually activates the 850 band, even though it shows as selected in the Service Menue
if you go back to the Band Selection screen of the Service Menue, you should choose bands that are knowingly not available in canada, like say band 900 for example, and then go back again to the service menu, and band selection to only choose 850
once you can confirm 850 works, then you can select 1900 as well, and now both of the bands should be active permanently until some body else screws it up again.
using *#0011# and trying to call the voice mail are the fastest way to verify for line and for 3G on 850
you can also try the app speedtest from speedtest.net
http://www.appbrain.com/app/speedtest-net-speed-test/org.zwanoo.android.speedtest
AllGamer said:
Can you elaborate more on this?
what do you mean by unable to get a solid data connection?
what kind of data connection are you referring to?
USB cable between phone to PC?
or Wifi data
or APN (3G) data?
Click to expand...
Click to collapse
AllGamer said:
Since the I9000M and I9000 are hardware based bands, you should always have the 850 and 1900 bands for 3G
Many who have tried Froyo and back had come across the problem of losing the 850 band, mainly because the Froyo leaks were intended for the Korea test team running international I9000 devices
some times just by flashing the Firmware back to stock or Froyo betas doesn't actually activates the 850 band, even though it shows as selected in the Service Menue
if you go back to the Band Selection screen of the Service Menue, you should choose bands that are knowingly not available in canada, like say band 900 for example, and then go back again to the service menu, and band selection to only choose 850
once you can confirm 850 works, then you can select 1900 as well, and now both of the bands should be active permanently until some body else screws it up again.
using *#0011# and trying to call the voice mail are the fastest way to verify for line and for 3G on 850
you can also try the app speedtest from speedtest.net
http://www.appbrain.com/app/speedtest-net-speed-test/org.zwanoo.android.speedtest
Click to expand...
Click to collapse
Sweet, I will try this as well.
Just a note, I have a galaxy s that is untouched, out of box and it also shows only 1900....
I'm starting to think location might be part of the issue.
there's also this sticky
http://forum.xda-developers.com/showthread.php?t=770041
with additional info you can do on the phone to get 850 back
So here's the deal, I have scoured the intarwebs and can't seem that find a solution to my problem, so as such I will toss my problems before you.
I have a Verizon Nexus 6 stock ROM, bootloader unlocked and rooted, TWRP with the current Franco Kernel. No other mods. So here's the issue, I can get LTE, but when the phone hands over to 3g service I get stuck there. The phone remains in 3g until I am forced to go to the cellular network menu and choose lte/gsm/umts so that it ignores CDMA. Once it finds lte again (almost instantly) I can return to global or even the lte/CDMA and have no issues until LTE drops and I have to do it again. I have even gone and got a new SIM with no fix.
Any ideas on a solution
First of all let me apologize to all those who I did not believe when they said they got LTE on their H version of the Note 4.
What I did was download the C version for Croatia (tele2) from www.sammobile.com.
I then removed the modem, hidden, and, sboot.bin from the firmware and re-packaged it using TAR_MD5_PACKAGER.
In recovery I factory reset the device, powered off and installed my packaged MD5 of Croatia (tele2) using Odin.
Then I flashed a C version modem even though it failed.
The problem is after a while I loose LTE. It will switch from LTE to 3G then to HSPA+.
I have changed my build prop to mimic an AT&T phone as well as the CSC others.xml file to mimic an AT&T phone and used AT&T's NxtGen APN but eventually I will lose LTE.
I can go into settings then More networks then Mobile networks then chose Network mode and switch from LTE/WCDMA/GSM to WCDMA/GSM and then back to LTE/WCDMA/GSM to get LTE working again but eventually I lose LTE and am back to H+.
I have done speed tests and I do get comparable speeds that I normally get on my AT&T LTE devices so I am sure that I am really getting LTE. Has anyone figured out a way to keep LTE without having to restart or go through the settings to get it back?
By the way I am not sure that it matters what firmware of the C version you use as long as you factory reset.
Edit: Added another screenshot, it seems that it only kicks me off of LTE when the signal is too weak and the phone has switched back to LTE at times on it's own.
Sounds like you need to either reinstall the original stock firmware for your Note 4 or install another custom ROM for it. As it seems the LTE drivers for the ROM that you are currently using aren't working very well.
Or your Note 4 may have developed a fault and needs to be repaired/replaced.
Also since you have a N910H, which is a 3G model of the Note 4 you should not have LTE/4G capabilities.
Greetings folks. I own a Nexus 6 XT1103 Unlocked. I'm on MetroPCS currently (piggybacks off T-Mobile LTE).
On Android 6.0.1 ROMs the device connects to LTE networks with no issue whatsoever. The real issue arises when I flash an Android 7.x ROM. The device connects to 3G (UMTS/HSDPA) and remains there even though the network setting is on LTE.
The phone momentarily connects to LTE when I reset the radio from LTE Discovery app and then reverts to 3G (the LTE signal detected just drops off to N/A). Also when the device is momentarily connected to LTE, the carrier label changes to 'No Service' even though network is available and LTE data works for those few moments. After those few moments it's back to UMTS and the carrier label returns to 'MetroPCS'
I've tried the following things to fix this (all in vain)
1. Flashed different radios (05.32, 05.34, 05.42) and bootloaders
2. Flash Android N stock image and then flash custom 7.x ROM
3. Go to the *#*#4636#*#* menu and set LTE only.
4. Resetting APN to default and manually adding APNs (both MetroPCS and T-Mobile)
I know the LTE network in the area is fine otherwise and anyway the moment I'm back on MM the issue the device connects to LTE properly (with a valid MetroPCS carrier label). This issue occurs on any Android 7.x ROM but it didn't happen as often in the Dev Preview, if I remember right.
I request all of you folks to help out if you've seen something like this or have any solutions. Cheers.
PS: Google Connectivity Services installed/uninstalled/disabled doesn't fix it
Have you tried a network settings reset? This worked for me when I lost LTE connectivity.
Settings>Backup & reset>Network settings reset.
Make sure you select network settings reset and not factory reset. They're right next to each other, so if your finger slips and you select the wrong one you'll be very unhappy.
Fixed it!! Flashing the 05.39 radio on fastboot before flashing the ROM seems to do it. Now LTE works with the proper carrier label too. I'd forgotten about the 05.39 radio as it was the one bundled with the N Dev Previews.
Cheers!
Trying this forum before I commit to re-flashing ROM.
I'm running lineage 14.1 on an HTC 10, and since I went thru using my phone with UK, Canadian and Mexican SIMs, my radio will randomly completely lose signal on a US SIM, and it seems more frequent when I allow LTE than when I have it set to UTMS only, though it still happens then.
I have to go into #*#*4636*#*# and toggle between gsm only and gsm+LTE, sometimes reboot my phone, and eventually I get signal back with full LTE.
It seems to me like my phone stops searching for towers until I prompt it to do so again by messing with its config and rebooting.
Looking for any ideas before I decide to reinstall my system.