The definitive guide on hacking the Nexus 4, part 5: How to permanently enable LTE on Android 4.2.2

space2

Update (March 19, 2013): Dear T-Mobile users, apparently, T-Mobile has been testing their LTE network and various users have reported being able to connect to it. All of the steps in this guide are still valid, however we would like to clarify step 15 for T-Mobile users. If you wish to get LTE to stick upon reboot, you will likely need to change the APN stored in the apns-conf.xml file. Users report that you need to use APN fast.t-mobile.com in order to access T-Mobile’s LTE network, but the XML document in the Nexus 4 has a default APN of epc.tmobile.com under “T-Mobile US”. We have no way of testing this as we’re not with T-Mobile, but according to this post and this post on XDA, the following changes should work (changes to XML file). Please make a backup of the XML first and try to make these changes and let us know in the comments below if it works. All that we did was simply replaced all of the APNs for “T-Mobile US” (as we didn’t know which one would be picked up) to fast.t-mobile.com and added a new APN called “T-Mobile US LTE” (just in case–it doesn’t hurt). You may ask, “why do you need to change the APN in the XML file instead of in Android under settings?” Apparently, as XDA users discovered, if you go into “settings” and change the APN after editing the “build.prop” (and doing a factory reset), you will lose LTE on the next reboot. If you have any questions, please leave us a comment below. Good luck!

The definitive guide on hacking the Nexus 4, part 5
This is part 5 of an 8 part series of articles on the Nexus 4. This guide assumes that you have successfully rooted your phone phone (part 2). This guide will describe how to permanently enable LTE on the Nexus 4 running Android 4.2.2.

Legal disclaimer: We are not responsible for any damage or loss to your device or computer system. Therefore, should you decide to follow these steps, you do so at your own risk and peril and agree to hold us harmless from any damage or loss you may experience. Should you disagree with the foregoing, please do not read any further.

As you may have heard by now, the Nexus 4 unofficially supports LTE in Canada. Back in November 2012, we conducted a short interview with the person that first made this discovery. If you haven’t read the interview yet, you can find it here.

On February 14, 2013, Google released an update to Jelly Bean called Android 4.2.2 which effectively killed unofficial LTE support for the Nexus 4 (not surprising as Google didn’t get LTE certification at the FCC). However, thanks to our friends at XDA-dev, we’re going to show you how to get LTE back. Furthermore, we’re going to show you how you can permanently enable LTE so that it “sticks” even if you reboot your phone. By using the standard trick to enable LTE, every time that you reboot your phone, you lose LTE until you select the proper LTE profile. It’s a bit annoying.

As you are already aware, the Nexus 4 only supports LTE (band 4 AWS) which is mostly used in Canada and by Telcel (Mexico). Therefore, if you live elsewhere, this guide isn’t really for you. However, if you live in a country that supports Band 4 AWS LTE and you have a Nexus 4, you may find this guide useful.

There are many guides on the internet on how to enable LTE on the Nexus 4, but it’s probably best to ignore all of those guides. They’re just going to confuse you. Those guides are all temporary LTE fixes and those methods don’t work with the latest Android 4.2.2.  If you don’t mind enabling LTE on every reboot, please follow this guide instead (but install the .33 radio first by following step 1-5 below). Enabling temporary LTE is much simpler, but you need to do it on every reboot. Fortunately, there’s a workaround, but it requires your device to be wiped. Also, Google Now sort of stops working if you enable LTE. Well, Google Now still works under LTE, but it requires a GPS lock and you need to be outside as aGPS seems to stop working (assisted GPS).

Before we get started, there are a few prerequisites for the following hack to work. You need (1) a Nexus 4 that has been rooted (2) you’re with Rogers, Bell, Telus, Fido, Kodoo, Virgin, MTSSasktel, Telcel (and for some lucky users T-Mobile) –for greater certainty, this guide will definitely NOT work with Wind Mobile, Mobilicity or Public Mobile in Canada or AT&T, Verizon, etc.), (3) you have an LTE sim card–you cannot use a regular sim card and (4) your data plan supports LTE (most data plans are LTE enabled, but some really old ones do not, ask your carrier if you are unsure). If you meet all of those requirements, please follow the below steps.

We would like to warn you that you will need to edit a few files, so be mentally prepared. It’s not very difficult, but it can appear a bit intimidating. Also, in case you’re interested, the source of this guide was found on this and this thread on XDA.

How to permanently enable LTE on the Nexus 4 running Android 4.2.2

The first thing that we’re going to do is install an older “radio” or “baseband”. Most people use the term “radio” and “baseband” interchangeably. The radio firmware controls basic low-level functions like network connectivity, Wifi, and GPS. Usually upgrading your radio will not give you any new features but will fix connectivity issues, increase range or performance, decrease battery usage, etc. However, in our case, by downgrading to an earlier radio, we’re going to get LTE back. We have not noticed any issues using the earlier radio with Android 4.2.2. Everything seems to work perfectly. Well, except with LTE wifi hotspot, but we’ll cover that in part 6.

1) Go into “Settings” then “About Phone” and go down to “Baseband” to see which version you’re running. The last 2 digits will tell you which version you’re running. If you’re running Android 4.2.2, it probably says “.48“. That version disables unofficial LTE support. Therefore, we’re going to install the earlier version called “.33“.

2) Download radio version .33 from this site (or direct link cwm-radio-mako-m9615a-cefwmazm-2.0.1700.33.zip) from your PC or from your phone. It’s about 20 megabytes. The MD5 for version .33 is 3607ae33dea2764c44e0e03c44cce7f9. You can verify the checksum if you like (see step 3 in part 3 which explains how to use WinMD5). Some users reported issues using  radio .33, but we didn’t experience any difficulties. If you do experience any issues, try installing version .27 to see if that resolves it.

Update (March 20, 2013): Users on stock Android have reported incompatibilities with baseband .33 and Android 4.2.2 (people can’t hear you when you’re talking on the phone), therefore it’s recommended to use the methods described in this guide if you’re running a custom ROM like CyanogenMod. CyanogenMod users have not had any issues.

3) If you downloaded the radio from your PC, transfer the zip file to somewhere in your phone (see step 4 in part 3 if you have trouble transferring the file). If you downloaded it using the browser in your phone, it’s probably saved at /sdcard/Download. If that’s the case, you can leave it there.

4) Turn off your phone and enter into Fastboot mode then enter into ClockworkMod and flash the zip file (see step 5 in part 3 if you forget how). We don’t think that there’s a need to clear the cache in ClockworkMod, but it doesn’t hurt. One the flash is complete, select reboot to reboot into Android.

5) Once the phone is booted, go into “Settings” then “About Phone” and down to “Baseband”. If you see .33 in the last 2 digits. It worked. You’re successfully downgraded to radio .33. You’re getting closer to LTE nirvana.

radio

6) Send yourself an email (choose an email address that is easily accessible from your phone) with the following text in the content of the email (we’ll need this text later). You can type it out by hand, but in order to avoid any possible typos, it’s safest just to send it to yourself by email.

telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
ro.ril.def.preferred.network=9

Some users may say that you only need the 1st line, but we tried that and it didn’t work. Trust us, you need all three lines.

7) Install your favorite file manager. We’re going to use ES File Explorer because it’s free and it’s good enough for our purposes, but you can use any file manager that can have root access.

Screenshot_2013-02-24-04-07-25

8) We’re going to enable Root in the file manager now as we need to edit some system files. In ES File Explorer, click on the context menu button “…” select “Settings” and scroll down till you see “Root Settings”, as shown below. Click on “Root Settings”

Screenshot_2013-02-24-04-08-11

9) Enable all of the boxes.

Screenshot_2013-02-24-04-08-58

10) We’re going to now edit the build.prop file. You can do this following our instructions below or you can use a dedicated app such as Build Prop Editor (Free) or build.prop Editor (Free). This file controls a lot of things. It tells Google what device you have, which country you’re in (therefore which Google Play Store you have access to), the LCD density of your device, etc. It’s basically your device’s ID card. Therefore, if you don’t know what you’re doing, don’t edit random things in this file! Now, go back to the main screen of ES File Explorer and navigate to /system/ (default location is /sdcard/ so you’ll have to go up one directory in order to see /system/). Scroll down till you see a file called “build.prop“. Make a copy of this file and rename the copy as build.prop.original (but we probably won’t ever need it–just to be safe).

11) Long click on “build.prop” and select “Open As“, select “Text“, select your favorite text editor. We’ll be using ES Note Editor in our example below. You’re now editing the build.prop file. If you scroll down the text editor, you’ll see a line that starts with “telephony.lteOnCdmaDevice=0“, as shown below.

Screenshot_2013-02-24-04-10-29

12) Delete that entire line and replace it with the text in the content of the email that you sent yourself. The end result should look exactly like below. Try to avoid leaving empty spaces at the beginning or at the end of the lines. Once you’re satisfied that it looks correct. Click on “…” then push “Save”

Screenshot_2013-02-24-04-10-48

13) In the next few steps, we’re going to add your carrier’s LTE APNs directly into Android (if you’re with Rogers or Fido) because the build.prop trick only works if you don’t change the APN in Android. Therefore, if you’re with Bell, Telus, Virgin or Kodoo or Telcel (Mexico), you can likely safely skip this step as the APNs in the XML file are likely already correct (but you can check to make sure). If you’re with Fido or Rogers, you will have to modify the XML file as we do below. If you don’t know what your carrier’s APN settings are, you can visit this page to find your carrier and take note of the LTE APN settings. In our example below, we’ll be changing the APN under “Fido Default”.

14) In ES File Explorer, navigate to /system/etc/ and look for a file called apns-conf.xml. Make a backup of this file by copying it and rename the copy to apns-conf.xml.original. It’s a very long text file to navigate. Therefore, send it to yourself by email so that you can edit it on your computer more comfortably.

Screenshot_2013-02-24-04-11-57

15) Install Notepad++ on your PC. It’s free and probably one of the best text editors for Windows. Open up the apns-conf.xml file in Notepad++. Search for your carrier. In our example, we’ll be searching for “Fido”. Fido was found on line 530. In our example below, you can see that the APN for “Fido Default” is “fido-core-appl1.apn“. Let’s replace that APN with “ltemobile.apn” (as mentioned on this list). You can leave everything else the same. It’s not necessary to change anything in “Fido Internet” or “Fido Tethering“. If “Rogers LTE” already has “ltemobile.apn” as its APN, you probably don’t need to edit anything, you can skip this step.

notepad

16) Save the apns-conf.xml in Notepad++ and send it to yourself by email. You may have trouble downloading the file from gmail on your phone if Android can’t find a program to open .xml documents. In that case, rename the file extension from .xml document to .txt, send it to yourself by email, download it from your phone to /sdcard/Download, rename the file extension to .xml and replace the apns-conf.xml file located in /system/etc with the one that we just edited.

Screenshot_2013-02-24-04-22-15

17) Now, we have to factory reset your phone. There’s no way around this unfortunately. It’s the only way to get the settings to “stick”. Go into “Settings” then “Backup & Reset”. You’ll see something like below. Click on “Factory data reset”.

Screenshot_2013-02-24-04-23-50

18) Click “Erase everything”.

Screenshot_2013-02-24-04-23-57

19) You’re going to have to go through the Android setup, feel free to setup your Google Account and Wifi. However, in order to test LTE, turn off Wifi and give it 5 minutes to connect to the cell towers. After a few minutes, you should see the 4G icon appear at the top right.

Screenshot_2013-02-24-04-45-05

20) If you’re so inclined, you can download the speedtest app and give it a whirl.You should see a substantial speed increase over 3G, but LTE speeds vary greatly depending on where you are currently located. Download speeds can be as low as 10Mbps and as high as 60Mbps.

speedtest

If you’ve ever read any “how to enable LTE on a Nexus 4 guide”, it will tell you to go into the Android dialer and input *#*#4636#*#* in order to access the config menu. After the factory reset, NEVER enter the *#*#4636#*#* config menu. Otherwise, it will revert back to WCDMA as the preferred network profile. If you enter that config screen, you would need to perform another factory reset in order to get LTE to stick again. Also, do not change your APN in Android once everything has been setup or LTE won’t stick anymore.

Finally, if you would like to change the little 4G icon to LTE, you can follow the instructions here (www.androidcoliseum.com). It doesn’t change anything performance wise. It’s purely for aesthetic purposes, but it’s kinda neat. Thanks ou7shined for the link :)

.4GtoLTE

In part 6, we’ll discuss how we can get LTE wifi hotspot working. It’s broken by default.

  • Felipe Cebada

    Hello!

    Excellent guide. Congratulations! I followed it step by step and now mi Nexus 4 has LTE once again. Thank you very very much!!! As a feedback, for Telcel (México) you can skip steps 13-16. I was so disappointed when new version of Android was released and after installing, noticed that LTE was gone. Thanks again! One question: do you think that in future Android updates (to Key Lime Pie most likely) the LTE will be disabled again? Hope not.

    Have a great day!!

    Felipe

    • Hippowise

      It’s great to hear that it worked out well! It’s hard to go back to 3G once you’re used to LTE. I’ll update the article to mention that Telcel users can skip steps 13-16. It’s pure conjecture, but I think that LTE will most likely be disabled in any future android updates for the Nexus 4 (key lime pie included). They don’t want to get into trouble with the FCC.

      • Doug Lee

        How’s the battery life though with lte permanently enabled? What are your thoughts about the changes?. Do you recommend this preference to power users?

  • Guest

    Thanks for this tutorial.

    My ROM supports init.d scripts so I’ve put those 6 iptables lines in a script in /system/etc/init.d/ with 755 permissions. When I run it with Script Manager, it works, but when it runs at boot (and I can confirm that it does run), it still does not fix LTE tethering. Any ideas?

    • Hippowise

      Hmm, did you happen to edit the script in windows first? shell scripts tend not to run properly when you edit them in windows. If you did do that, try creating the script in Android and see if that works. Please let me know. Thanks!

      • Marc Andrews

        I actually created it from within Android with Script Manager.

        • Hippowise

          interesting… in that case, I would just let Script Manager autorun the script for you on boot (instead of adding a script to the init.d yourself).

  • Guest

    I am a T-Mobile US user so this guide has no use for me… yet, but is the best guide for LTE in the whole universe. Thumbs up.

    • Hippowise

      T-Mobile is working on Band 4 AWS, so it looks like if it’s just a matter of time till you can use LTE on your Nexus 4. Let’s hope!
      http://www.tmonews.com/2013/03/t-mobile-2/

      • Hao Shen

        That’s why I said “yet.” Could you tell me how to set APNs for T-mobile? I will try this method when LTE rolls out, and let you know to keep this article updated.

        • Hao Shen
          • Hippowise

            Great! please let me know if it works when it’s rolled out in your area and i’ll update the guide

          • Hao Shen

            Bad news is: I can’t get any radio other than .48 to work with 4.2.2 stock without breaking the audio of phone calls. This is a well known issue for using Tmobile US.

          • Hippowise

            The problem appears to go away if you’re using CyanogenMod 10.1. I’ve always used CyanogenmMod and I never had any problems. You can give that a try if you’d like http://forum.xda-developers.com/showpost.php?p=38112538&postcount=108

          • 9

            Aokp roms work too. I’d avoid the Mysterious Aokp rom since I had it reboot twice from downloading a few apps and snapping some pics.

          • guest

            I tried .33 radio on AOKP build 6 and it works great! I will try the new Tmoble LTE in Washington DC over the weekend. However, I actually prefer to switch on/off LTE radio manually instead of using the method in this guide to make it stick. I don’t have constant LTE coverage and do not reboot phone very often. Thanks for this excellent guide anyway!

  • Robert Navarro

    Is there a way i can revert this? Im a Telcel Mexico user and experiencing an issue that when the phone goes from 3G/H/H+ to 4G or viceversa, the signal will drop for a couple of seconds. Besides, since Telcel Mexico just release the LTE update for the iPhone 5. The LTE speed was reduced dramatically, getting a max of 7 Mbps download and 15 Mbps upload. Please help removing the LTE :(

    • Hippowise

      Try to open up your phone dialer, enter *#*#4636#*#*, tap on “Phone information”, open “Set preferred network type:”, select the appropriate profile for Telcel (pick a profile that doesn’t include LTE). Afterwards, go into “Settings” and change the APN to the regular non-LTE APN for Telcel (if there is a different APN). Restart the phone and LTE should be permanently gone.

      • Robert Navarro

        Thanks! its gone! Too bad that Telcel LTE network got too crowded. I recall when it was released i was getting some lovely 50MBps down and 30 up.

        • Hippowise

          Glad it worked! Hopefully they will improve their LTE network soon :)

        • Felipe Cebada

          Hello Robert, It is weird that your Nexus 4 can only get that speed. Mine is almost the same since January when I purchased it. The result of speed test some minutes ago.: 35ms Ping. 23.7 Mbps Download, 20.1 Mbps Upload. México City.
          I am very happy with going back to 4G. Let´s see how long it works. Thanks to Hipowise again!

          • Robert Navarro

            The thing is that in Monterrey not all city have LTE speeds yet. And since San Pedro is where we have this speeds. Is where most of the people has smartphones especially the iPhone 5, and since Telcel released the LTE update the speeds where affected dramatically. :( 3G ~ LTE

  • John M. Kuchta

    At this point in time, this does not work for T-Mobile in Los Angeles.

  • Javier Camacho

    Man!! I was having a blast with lte, everything was working just fine, suddenly, i was driving around, i had wifi enabled, it got connected to a wifi spot those without a password, and when i got on the mobile data back, i couldnt get it to connect to lte anymore =(, i even made a factory reset, nothing, it doesnt stick to lte =(. have to dial the ¨#¨#4636#*#* code to get on lte. Do you know what might the problem be?? im in telcel in mexico.

    • Hippowise

      Hmm, I have no idea. Never heard of this happening. My only suggestion is to retry the steps. Sorry!

      • Javier Camacho

        Yeah, just did that and its working fine now. I changed the numbers 9 for 10, but i messed up the com.android.phone app, returned it to 9 and now it seems to be sticking to it everytime i reboot, thanks for this tutorial you and the people from xda rule!! Just did step 6 to enable tethering with lte, working great so far. Thanks!!

      • Javier Camacho

        Mann!! I Have another issue now!! D´: now the phone doesnt get my location through the network, maps shows the message your location is temporarily unavailable. And im almost sure thats due to either this hack or the one to enable the tethering with lte, help please!! anybody having this issue??

        • Hippowise

          Did you turn on “Location Settings” in Settings? It’s pretty common that assisted GPS (for indoors) is broken when you have LTE enabled, but regular GPS (for outdoors) still works.

          • Javier Camacho

            Yeah, normally I have the gps off and the wifi too, so the phone uses the carrier network to locate. Ive been reading on several threads on xda and this is a regular issue among n4 users, since the phone wasnt supposed to be lte, the config to detect the lte network doesnt work properly, only on 3g, why dont you try to use google now or maps disabling gps and wifi, youll see how its kinda broken. Ive been looking for a fix, but noone seems to have the answer for this issue. I hope you or someone find the way to fix it. Thanks man.

          • Hippowise

            Ya, its a pretty common issue. I haven’t seen a fix for it yet though. Hopefully, someone figures it out.

          • Javier Camacho

            Damn! again jumped to 3g and not sticking to 4g after reboot =( right after a call. Hope im not the only one with this issue,

          • Hippowise

            That’s odd. LTE should stick after reboot. I’m not sure what the problem is.

  • Jacky

    I have just tried and followed your guide, checked twice on the setting (radio .33, build.prop and APN) and they are all in modified correctly, however I cannot get the LTE working (but the 2G is working fine tho). Can you suggest what I can possibly do? btw I am using Fido with CM10.1 ROM.

    • Hippowise

      It’s pretty hard for me to diagnose from afar, but I’m on Fido as well and just installed a new custom ROM called Paranoid Android w/ Franco Kernel nightly’s custom kernel and LTE is working fine. If for some reason LTE doesn’t work, my only advice is to try and re-install everything. Hopes it works!

      • Jacky

        Hi I followed your instruction and re-do all the steps again but no luck. This time I am using your Paranoid Rom and Franco Kernel too. One thing I noticed is that in the setting the “access point names” is actually empty after factory reset, instead of showing me the fido apn. There’s another apn-conf.xml file under folder /etc too (other than system/etc), do i need to do anything about it? Thanks for the help! much appreciated!

        • Hippowise

          I’ve only ever edited the XML file under system/etc, so I don’t think that you need any other file. I’m not sure what appears under APN as I’m too afraid to go into access point names (as it may make me lose LTE on the next reboot). If I had to guess at what the problem is, it’s probably caused by the XML file. If you can get LTE to work by manually adding an APN, it probably means that it’s not picking up the APN from the XML file. Maybe you’re missing a punctuation mark or something? I would double check to make sure that the XML file is correct and try to do another factory reset.

      • Jacky

        An update to this post, I can get it to work now but somehow I have to manually setup the APN in setting/Access Point Names, it still work even tho I reboot the phone… so basically the apn-conf.xml cannot be detected after I modify it?

      • Sukanta Sen

        Hey man I’m also on Paranoid Android and Franco’s kernel, and I ran into the no audio issue during calls (can’t hear voice both ways or any ringing when making calls). Are you running into that issue?

        • Hippowise

          Nope, no issues here. It’s very interesting… I’ve never heard of that problem occurring on a custom ROM. I’m currently using Paranoid Android (with the kernel that came with) and battery life is pretty remarkable. I haven’t had any voice or calling issues. I’m still getting the no Assisted GPS problem, but I don’t think that there’s a way to fix that. I’m not sure what’s causing your specific problem. My only suggestion is to try a different custom ROM and try again? Sorry.

          • Mega

            Thanks, where can I get Paranoid Android? And can I follow the same instructions you gave in this guide? I’m on T-Mobile US by the way. Thanks for the help

        • Mega

          I’m having the same issue, calls connect but no audio. Did you figure it out?

          • Hippowise

            Are you using Stock Android? The audio problem goes away if you’re using a custom ROM such as CyanogenMod, Pac-Man ROM or Paranoid Android, etc. so that’s what I would suggest. Hope that helps.

          • Mega

            I followed this guide to the tee, used CyanogenMod, audio issue was there.

          • Hippowise

            Hi Mega, I’ve never heard of the audio issue happening with a custom ROM before, sorry. I don’t know how to fix it.

        • Mega

          This is killing me, no audio, I tried doing a factory reset and nothing. I can call people, but there is no audio during calls. Anyone have a fix?

  • Jackson

    How would you go about doing all this on T-Mobile USA to allow permanent LTE? Thanks in advance.

    • Hippowise

      You can use this guide for T-Mobile, except for step 15, follow my suggestions in the first paragraph :)

      • Dion Mac

        In the T-Mobile exception of step 15, I noticed a line that read “”

        But I did not see this one in my apns.conf.xml file. Also, just to confirm… In step 15, we are to change T-Mobile US 160, 200, 210, 220, 230, 240, 260, 270, and 310… but there are also T-Mobile US 490, 580, 660, and 800 that still says epc.tmobile.com. Should this remain the same or change those to fast.t-mobile.com as well?

  • Felipe Cebada

    Hello. I have some kind of strange question. Since the N4 is not blocked I have tried to have data connection using another carrier´s SIM. This, after processing this tutorial (it works in 4G with Telcel´s Sim). When the other Sim is installed, there is no data at all, just voice. I guess this is because the changes made to enable LTE isn´t? Just to confirm so I can stop to bother IT guys of the other company LOL. Thanks a lot!

    • Hippowise

      The settings that you put in the build.prop should allow for both 3G and LTE, so it should fall back on 3G when LTE is not available. You can try entering the config menu and changing the network profile to see if data works on the 2nd SIM card, but you will lose LTE on the next boot (meaning, you have to enter the config menu to enable LTE on every reboot). On the phone dial screen, enter #*#4636#*#* to enter the config menu (if you wish).

      • Felipe Cebada

        Ok. Something must be wrong because when using SIM card 1 the N4 can access on any available network (3G, H+, 4G, etc) depending of availability. But when insert SIM 2, there is no data at all, just voice. Thank you again!!

      • http://jeremyperez.com Jeremy

        I’ve found you can fix LTE not “sticking” on reboot. You need to edit the settings database. I did it via adb shell command line, but an app that will let you edit databases as root will work as well.

        The db is located @ “/data/data/com.android.providers.settings/databases/settings.db” You need to edit the global table and change the value of “preferred_network_mode” to ’9′. If you have the sqlite3 binary installed you can just do (all on one line):

        sqlite3 /data/data/com.android.providers.settings/databases/settings.db ‘update global set value=9 where name=”preferred_network_mode”‘

        • @vnovakovich

          Yes, this works for me, it keeps the LTE after the restart. Thanks!

  • http://www.facebook.com/josef.izchaki Josef Izchaki

    Wow it worked :)

  • http://www.facebook.com/josef.izchaki Josef Izchaki

    Ok now i am confused, woke up in the morning and the phone is on H not LTE and not even H+, i Didn’t even restart the phone even though should not make a difference. any suggestions?

    • Hippowise

      Hmm, if you have LTE in your area, it should automatically connect to LTE in preference to other data connections. Your phone will usually only fall back on H or H+ when LTE is not available. My only suggestion is to try to reboot your phone and see if it connects to LTE when you’re in a different area of the city.

    • De Pig

      Hi, Josef,
      Did your LTE ever back?

    • PreachJohn

      I use Network/Play Store to reset or make sure my Nexus 4 is on LTE/4G. I set it to LTE/GSM auto(PRL), and reset it to speed up Reconnect on Reboot sometimes. It normally would do this on its own if left alone.
      I’m in Calgary. Alberta where Wind Mobile and Mobilicity are both on the AWS 1700/2100 spectrum. The other in Canada is Videotron. T-Mobile and Cincinnati Bell are the two in USA on this spectrum.
      Android 4.2.2/Rooted held LTE/4G on Reboot. In fact said Recommended! And still does in Settings/Mobile Networks/Preferred Network… in CM11. CM11 doesn’t recognize more than 3G in Settings??

  • Kingread

    first of all thanks for the post, I’m trying to connect to T-mobile’s LTE (USA) and after reboot I get LTE but after a second reboot the LTE is gone, I’m trying to edit the XML file but all those files and lines are so confusing, I don’t really know how to edit it, I am afraid to mess up the apn’s plus I have no idea how or where to place the lines, if you could help me I will appreciate it :)

    • Kingread

      Update: I managed to edit the XML file and I did all the process all over again and still I get LTE after the first boot but after that I have to dial the number and set up to LTE it does stick somehow, any ideas of how to fix, it might be me with the wrong XML edit

  • http://twitter.com/ernestoal Ernesto Aldape

    I could successfully enable LTE permanently on my N4 using Telcel as a carrier (skipping steps 13-16). I would like to know if I would be able to do data roaming over 4G if I travelled to Canada or if I would have any issues if I were to use my device in another country with a national SIM card (and this carrier’s LTE weren’t Band 4- I wouldn’t expect 4g naturally but would I have any problems with H+, H, 3G, E?).

    • Jonathan Hernandez

      Hola amigo¡¡¡ que version de android tienes?? yo no lo quiero actualizar porque dicen que da problemas con el 4.2.2 y ponerle el radio .33

    • Eduardo A

      en que correo te puedo contactar?

  • Fernando Cordova

    Hello, as you stated .33 radio can make stock 4.2.2 Android fail when calling. Does this happens also with .27 radio??
    Thanks in advance

    • Hippowise

      I’ve never had to try .27, so I don’t know, sorry.

      • Fernando Cordova

        So I can be sure that .33 works just fine then. I am only worried about the “people won’t hear you” part. Is it a common issue?

        • Hippowise

          I don’t recommend trying to get LTE to work on stock android as the audio bug usually happens.

          • Fernando Cordova

            Shrugsss… I did it already, well if I happen to get the bug I will simply flash .48 radio and forget about LTE. Oh about that, if I have to do taht do I have to reverse modifications to build.prop or do they change along with the flashing??

            By the way, you are awesome for posting this. Thank you very much

          • Hippowise

            build.prop will automatically change when you install a new custom ROM.

  • De Pig

    I followed this instruction and got 4G successfully on Fido one week ago. However, since today, I can’t get 4G any more. It always switch between 3G and H. I’ve checked my apn is ltemobile.apn. Is it possible that Fido banned my IMEI from 4G?

    • Hippowise

      I don’t think that’s likely. Fido doesn’t care if you’re using LTE on the Nexus 4 or not.

    • Samuel Begin

      I’m having the same problem. I checked every step in this guide again and the only thing left is the facto reset. Have you found any solution? Will the reset do the job?

  • jose95

    can’t edit won’t work any advise?

    • Hippowise

      the file is probably read only, you need to change the permissions of the file.

  • Kevin

    My apn-conf.xml file does, only has one entry for Rogers — unlike your example. How do I update?

    • Hippowise

      Use this APN for Rogers LTE: LTEMOBILE.APN I would copy your Rogers entry and make another one called “Rogers LTE” and put the same settings for both entries.

  • Patrick

    Does anyone know if flashing new kernels or other .zips will break the LTE edits? I remember trying to restore SMS after doing the edits and it would take away LTE functionality so i’m hesitant to flash anything new…

    • Keith

      It does reset the apn settings but your broadband version will still be .33

  • Olu Akins

    Just wanted to stop by and say thanks for the excellent write up on getting 4G Lte on my Nexus 4 in Maryland. Nexus 4 just got a new life. The instructions I followed where mostly cwm zips files created to do the exact same thing and doing a reset on the Apn network. Thank you very much.

    • Hippowise

      I’m happy that I can help! Cheers!

  • Michael Thompson Parker

    Trying to save the build prop but keep getting errors

  • gabe

    hey Im having an issue connecting to the lte on tmobile.. I have he .33base band and did everything sated above, but it still wont work. I was wonderin if there was any solutions

    • gabe

      never mind I found the issue, when I copied the an settings I left a space somewhere where it wasn’t supposed to be.

      • nathan.k

        can I ask what apn u edited??? also on T-Mobile (US)

  • Jose Ramos

    Hey, I follow the parts 1, 2 and 5,and I don´t install the custom ROM and custom Kernel… I haven´t LTE conection, I need install the Custom ROM and Custom Kernel to run LTE?

  • nathan.k

    Does anybody happen to know the apn that you edit for T-Mobile US?

    • nathan.k

      in the apns-conf.xml file that is?

      • Mario E Hdez

        nathan.k, read my post above. just search for “epc” and change the apn to what I noted above.

  • Mario E Hdez

    For any US T-Mobile users: For the “apns-conf.xml” file, search for “epc” and you should see an entry titled
    T-Mobile US 160. Change the apn line that starts with “epc” to “fast.t-mobile.com”. There are other “epc” entries with different numbers (T-Mobile US 200, 210, 220, etc…) so I edited each apn to read “fast.t-mobile.com” and it works great for me. Hope this helps anyone.

    • Denis Nikiforyan

      do i need to add the fast.t-mobile to access points please help

    • jetscreamer

      That’s what I did, it took awhile to make sure I got every T-Mobile APN changed. But it was worth the effort.

      • hadak

        Why would it take a while? ssh or adb shell in, vim /system/etc/apns-conf.xml, then enter the following command in vim:
        %s/epc.tmobile/fast.t-mobile/g

        Hit enter, and they’ve all been changed. :wq, or shift-z-z to save and exit.

  • MJavier

    Quick question, on the last part when hippowise said ” Also, do not change your APN in Android once everything has been setup or LTE won’t stick anymore.” Does this mean if ever I did, I have to redo the whole process or not even that. As in its a one time shot? Sorry for a dumb question I’m just curious.

  • Datcon

    Do you have to factory reset after updating cyanogenmod version? I’m running cm 10.1 rc5 right now and am thinking about installing the just released stable version.

    Thanks a lot for the awesome guide!

    .d

    • Datcon

      I just got LTE working on my Nexus 4. A few learnings:

      1. updating your ROM will wipe out these changes and require a factory reset.

      2. regarding the APN xml for Rogers: the APN value should be ‘ltemobile.apn’ for BOTH carrier references ‘Rogers’ and ‘Rogers LTE’ not JUST ‘Rogers LTE’. My apn xml already had the correct setting for ‘Rogers LTE’ and I was unable to get 4G connnecting until the ‘Rogers’ carrier was also edited.

      Thanks again for the awesome guide.
      .d

  • Den

    А в России работает?

    • Rus

      Вроде бы только МТС

      • Hippowise

        Если у тебя есть LTE данные для МТС, я могу написать инструкцию для Росси.

  • Bowen9284

    You are the man. If you follow the guide precisely it will work! I am picking up LTE in the Providence, RI area. 12 down and 9 up. Not amazing but the service is much better in my house now. Thanks again

  • Malcolm Bates

    I get the 4g symbol beside the bars, but the bars are grey. They were blue before, but only when wifi was off. When I turned on wifi, the bars became grey. After a factory reset now they don’t go blue at all.

    • Malcolm Bates

      Never mind tried it again and it worked fine this time

      • Malcolm Bates

        The issue is that it does not co-operate with ultimate dynamic navbar’s “hide real soft keys option using build.prop modification”. I still use the app, but I use a different app to make it go full screen instead.

  • jetscreamer

    Does anyone know if this will stick when you update to the latest Cyanogenmod?

  • Eduardo Arias

    I got the .33 by rooting and flashing the 4.2.1 Baseband and was going to wollow your steps 7 – 20 I can’t find the rooting options in the ES explorer… Please Help! Running on Telcel carrier and with plan that supports LTE

    regards

  • Gonzalo

    Man i need help, hope u can help. Ive just received the OTA update for jelly bean 4.3, but dont know what will happen if i update it. Ive read on xda threads that this has a new baseband, so i dont know what will happen then, will i have to do everything again? will it work? help man!

    • Yaki Forto

      it will work…MOST likely… I did it on KITKAT 4.4 lol

  • Gonzalo

    Man i have a problem, hope u can help. Ive just received the OTA update for jelly bean 4.3, but dont know what will happen if i update it. Ive read on xda threads that this has a new baseband, so i dont know what will happen then, will i have to do everything again? will it work? help man!

  • jetscreamer01

    I just upgraded to CM 10.1.3, and fortunately the LTE modification stuck. I did notice the update changed the Build.prop and apns-conf.xml file. I am a T-Mobile user, and all the T-Mobile apn that I changed have been altered, except for the one for T-Mobile USA LTE, It still show fast.t-mobile.com. I guess that is only one that matters.

  • Danny Doan

    Hi All,

    Just wondering if anyone has or had any problems with GPS?

    My GPS won’t lock and it keeps saying “Waiting for location”. I’m on CM 10.1.3, in San Jose, CA, on T-Mobile and I’m getting LTE.