Hi guys,
I have a stock Moto G that has not been used for a long time. Everything works perfectly till i insert my sim card. Starting from that, lots of problems occurred such as :-
- microphone not working
- speaker not working
- can't call
- can't record video
- audio jack not working
So basically, all media could not work in this phone. However, i tried to root this phone and install a custom rom (Dirty Unicorns 6.0 MM) and still, the problem occurred. I could not think any other solution than wiping cache, and re-flashing the rom several times. The sim card was not inside the tray at the moment. I hope to hear any solution from you guys. Thanks in advance guys!
rixalis said:
Hi guys,
I have a stock Moto G that has not been used for a long time. Everything works perfectly till i insert my sim card. Starting from that, lots of problems occurred such as :-
- microphone not working
- speaker not working
- can't call
- can't record video
- audio jack not working
So basically, all media could not work in this phone. However, i tried to root this phone and install a custom rom (Dirty Unicorns 6.0 MM) and still, the problem occurred. I could not think any other solution than wiping cache, and re-flashing the rom several times. The sim card was not inside the tray at the moment. I hope to hear any solution from you guys. Thanks in advance guys!
Click to expand...
Click to collapse
I have a similar issue on a old moto g (falcon)
At weekend I stuck the latest CM 14.1 on my newer moto g (peregrine) and worked great so I thought I would put the matching ROM for the falcon on and once I'd updated the bootloader and twrp it actually runs really smooth but it doesn't detect any sim cards which was a intermittent fault with it anyway which I presumed may be the software but seems its hardware now.
So anyway after all my waffling give that ROM a blast.
Sent from my XT1039 using Tapatalk
steve.loveday said:
I have a similar issue on a old moto g (falcon)
At weekend I stuck the latest CM 14.1 on my newer moto g (peregrine) and worked great so I thought I would put the matching ROM for the falcon on and once I'd updated the bootloader and twrp it actually runs really smooth but it doesn't detect any sim cards which was a intermittent fault with it anyway which I presumed may be the software but seems its hardware now.
So anyway after all my waffling give that ROM a blast.
Sent from my XT1039 using Tapatalk
Click to expand...
Click to collapse
thats for the suggestion. i think i might try it soon. but is it possible that its my hardware problem?
rixalis said:
thats for the suggestion. i think i might try it soon. but is it possible that its my hardware problem?
Click to expand...
Click to collapse
Yeah definitely possible
Try popping the back off and remove the screws and you can see the sim card holder have a check its in good condition and the solders not loose
Sent from my XT1039 using Tapatalk
If those problems are related to software, install the stock firmware through mfastboot commands, including wipes on the data and cache partitions to see if that solves the problems.
If not, then its a hardware problem and there's not so much to do..
good luck
Installed a new battery and screen, and since then sim card is not detected on Pixel. Sim works fine in other devices, just not being recognized by the pixel. IMEI number also does not show up in the system.
Any ideas on how I might have jacked something up installing the new battery and/or screen. Other than that phone seems to run fine. I've flashed a few different roms and stock back onto the device, with success, but still Sim is not recognized.
Desperate for any help with this.
MontoyaWA said:
Installed a new battery and screen, and since then sim card is not detected on Pixel. Sim works fine in other devices, just not being recognized by the pixel. IMEI number also does not show up in the system.
Any ideas on how I might have jacked something up installing the new battery and/or screen. Other than that phone seems to run fine. I've flashed a few different roms and stock back onto the device, with success, but still Sim is not recognized.
Desperate for any help with this.
Click to expand...
Click to collapse
I had this error updating to Android Pie. I found and posted an updated fix in the Pixel forums; if you are on the latest Pie, extract the Modem.img file and just reflash that file; fixed it for me. Good luck.
LBN1 said:
I had this error updating to Android Pie. I found and posted an updated fix in the Pixel forums; if you are on the latest Pie, extract the Modem.img file and just reflash that file; fixed it for me. Good luck.
Click to expand...
Click to collapse
I had this error too,what can I do?
Hi all,
When I got the Mix 3 I was running EU MIUI as my daily driver, that was MIUI 10 back then. Bluetooth absolute volume was working fine back then.
I own a pair of Sony WF-1000xm3 and since EU MIUI 11 or the last Sony update of these headphones I can't get bluetooth absolute volume to work on the mix 3 with MIUI. I have been using AOSP based roms for half a year now but the unstability (alarms not functioning because of a soft reboot during the night for example) made me go back to MIUI.
Using any AOSP rom the absolute volume works fine and it was working fine half a year ago on MIUI 10 with the Developer option absolute volume.
I have flashed MIUI 10 from half a year ago but I just can't get absolute volume to function. Since my bluetooth speakers that also support absolute volume don't function like they should aswell on MIUI I'm suspecting something else is wrong in my configuration. Even reflashing using Mi Flash Tool to global rom doesn't solve my issue and different firmwares also didn't solve my problem.
Who can help me?
Don't know about the volume problem, but the reboot overnight is caused by a wireless charging bug in AOSP, although on mine it's a hard reboot all the way back to the bootloader, not just a soft reboot of the rom.
Well, it seems I have magically resolved it.
In what I believe I haven't done anything different this time than previous tries I have done, but these are the steps I have taken (from memory)
Reflashed fastboot global rom using Mi Flash tool and relocked the bootloader.
Booted the rom, unlock bootloader check in developer options
Unlock the bootloader using Mi Unlock Tool
Flash TWRP and flash MIUI 11 EU weekly rom, boot
Format data and wipe all storage options except internal storage in TWRP
Flash pixelexperience rom, boot
Format data and wipe all storage options in TWRP
Flash MIUI 11 EU weekly rom, go to developer options and disable the 'disable absolute volume' check.
Pair bluetooth headphones.
And suddenly it works! It might be that some steps seem unnecesary but I have tried so many times using different patterns that I will keep using above pattern.
Hope this helps someone someday if he/she faces the same issues as I did.
Finally enjoying my mp3 player with phone capabilities again
sjsimon1996 said:
Well, it seems I have magically resolved it.
In what I believe I haven't done anything different this time than previous tries I have done, but these are the steps I have taken (from memory)
Reflashed fastboot global rom using Mi Flash tool and relocked the bootloader.
Booted the rom, unlock bootloader check in developer options
Unlock the bootloader using Mi Unlock Tool
Flash TWRP and flash MIUI 11 EU weekly rom, boot
Format data and wipe all storage options except internal storage in TWRP
Flash pixelexperience rom, boot
Format data and wipe all storage options in TWRP
Flash MIUI 11 EU weekly rom, go to developer options and disable the 'disable absolute volume' check.
Pair bluetooth headphones.
And suddenly it works! It might be that some steps seem unnecesary but I have tried so many times using different patterns that I will keep using above pattern.
Hope this helps someone someday if he/she faces the same issues as I did.
Finally enjoying my mp3 player with phone capabilities again
Click to expand...
Click to collapse
I was looking to get the Sony WF-1000XM3s, is LDAC working properly on Xiaomi.eu in MIUI 11? I'm on MIUI global stable 10.3.2.0 right now and I can't select any codecs aside from SBC (AAC is the only one my headphones support but still) and I'm kind of sick of it. I was thinking of jumping ship to Xiaomi.eu anyway but I'm a little apprehensive about how well it works in the US
Rockmadeofrock said:
I was looking to get the Sony WF-1000XM3s, is LDAC working properly on Xiaomi.eu in MIUI 11?
Click to expand...
Click to collapse
I have enabled LDAC in developer options but it doesn't seem to make a difference in comparison with AAC or SBC.
sjsimon1996 said:
I have enabled LDAC in developer options but it doesn't seem to make a difference in comparison with AAC or SBC.
Click to expand...
Click to collapse
If you look at the device in your Bluetooth settings does it say LDAC next to it, showing it's actually being used? Because I know that has historically been an issue as well, where you select a codec in Dev Options but it doesn't actually change and then reverts back to SBC as soon as you close the settings.
Even if AAC works it would still be a marginal upgrade over SBC which is what I'm stuck with now.
Rockmadeofrock said:
If you look at the device in your Bluetooth settings does it say LDAC next to it, showing it's actually being used? Because I know that has historically been an issue as well, where you select a codec in Dev Options but it doesn't actually change and then reverts back to SBC as soon as you close the settings.
Even if AAC works it would still be a marginal upgrade over SBC which is what I'm stuck with now.
Click to expand...
Click to collapse
No, it still says AAC, so that doesn't seem to be working.
sjsimon1996 said:
No, it still says AAC, so that doesn't seem to be working.
Click to expand...
Click to collapse
Just realized only the over-ear WH-1000xm3's support LDAC so your bluetooth is working as it should.
I am currently facing a very weird(to me at-least) problem that seems to be exclusive to me, since I cant find similar posts on any forums.
The network of both the sim cards on my phone are continuously being reset- as if I was continuously enabling and disabling airplane mode, but the Wi-Fi, bluetooth and everything else is fine.
I'm using a network carrier called Jio, and have been getting horrible speeds for quite some time now. Today I noticed that whenever I was connected to someone on a call, my internet speeds were exponentially higher(2 mbps - 12 mbps), which seemed strange and after a little research, was revealed to be the cause of my LTE band being locked on band 3 whenever I was on a call.
So I started looking for a way to make that band lock permanent, in hopes of getting good speeds. I found about these two tools called QPST and QXDM which are supposedly have very broad uses like resetting IMEI etc, which I have no knowledge of how to do.
I was stupid enough to not properly read any documentation or proper guides of how these tools are used. I just saw in some articles and videos that QXDM can also be used to directly change the value of the variable that holds the code of what 4g band is being used, so I tried changing that.
Here's the steps I performed:
Looked for and installed the correct Qualcomm diagnostic mode drivers for my phone(adb and fastboot were already installed).
enabled DM using adb.( su -> setprop sys.usb.config diag,adb in an adb shell)
Started QPST and QXDM in that order.
Selected the LTE values in NV Browser of QXDM and tried to modify those to the codes corresponding to the band I wanted to lock to(band 5 that has code 16).
I read the default value, copied it, then wrote required value and clicked on "Write" which failed giving the error : "DIAG error received: Invalid Command Error Response"
After this the aforementioned problem started, and I tried restarting the phone first, which sent it into a bootloop.
I fixed the bootloop by clean flashing my current rom(without formatting the storage).
But the problem is still there.
I was using an app to monitor what band is currently being used. Even the app is not working anymore, it says that drivers are not properly installed.
I am also unable to access any network related settings in my rom settings.
My RN7 is a violet.
I am currently on Pixel Experience 10, latest build.
With the latest miui firmware installed.
Orange fox recovery.
I guess I shouldn't have messed with things I have no idea about, specially without proper research, but I am really clueless now about what might be causing the problem and how, if at all, I could fix it, I thought of a complete re-flash of stock MIUI using mi flash tool, but not sure if it would help or not.
Any help will be much appreciated!
First of all, you shouldn't have used these tools if root was available as there is an app called Network Signal Guru. Now this app requires root and u can easily lock any of the band you want.
Now if you are facing any problem i recommend a clean install of fastboot rom. With formatting data and storage so none of the problem remains. I guess there is a problem being faced by many though i didn't checked myself about sensors not working on stock rom after pixel exp. Rom but some says flashing miui10 via mi flash and then updating it to miui11 via recovery the sensors strt working.
You need to check for that but if you want to go back to pixel rom then its fine.
To lock bands remember to use this app. It works fine.
Moreover flashing the rom may remove the problem you were facing of signal but i guess it was only due to phone changing bands.
Network signal guru doesn't work with Custom Roms.
gursewak.10 said:
First of all, you shouldn't have used these tools if root was available as there is an app called Network Signal Guru. Now this app requires root and u can easily lock any of the band you want.
Now if you are facing any problem i recommend a clean install of fastboot rom. With formatting data and storage so none of the problem remains. I guess there is a problem being faced by many though i didn't checked myself about sensors not working on stock rom after pixel exp. Rom but some says flashing miui10 via mi flash and then updating it to miui11 via recovery the sensors strt working.
You need to check for that but if you want to go back to pixel rom then its fine.
To lock bands remember to use this app. It works fine.
Moreover flashing the rom may remove the problem you were facing of signal but i guess it was only due to phone changing bands.
Click to expand...
Click to collapse
Thanks for the reply, though I agree I shouldn't have tried using things that I don't fully understand.
I did use the app that you mentioned and it did not work, after which I tried this method.
I just clean flashed the miui11 through fastboot using mi Flash tool and it's fixed now, thanks!
Redmi note 7 pro mobile data dropping
Hello,
Sorry for introducing a new issue(as a new and inexperienced member hoping for solution) related to the mobile data problems on redmi note 7 pro.
I have the phone since a month and the network data was working perfectly fine and since several days the internet via mobile data drops every 5 minutes. I have to reboot the phone or turn off/on mobile data several times.
I contacted my internet provider and all is correct from their side and they even gave me a new sim card that i tested on my galaxy m20 and it works fine.
I was looking for solutions on forums but it didn't help and i turn around here hoping to find solutions on my issue.
Thanks
Originally, this was thread was centered on the LineageOS 17 GSI by AndyYan, however, CodeF86 has so very generously made a working GSI for the Moto G6 which you can try out now!
Unlike AndyYan's generic GSI, for this you do NOT need to flash johnaltg1's LineageOS 16 image (if you do, this GSI will NOT boot). It is recommended you use stock Pie firmware. Oreo firmware has not been tested and may result in bugs.
Download here—Compiled Feb 22nd, w/ working LTE!
See CodyF86's thread post
Some notes:
Unlike the generic GSI, calling works.
Also unlike the GSI, the colors don't invert randomly.
Magisk DOES NOT work at the moment, neither phhuson's nor regular Magisk. Flashing it will cause a bootloop.
Bluetooth audio has been reported to not work
As with many Android 10 GSIs/ROMs, Chrome freezes or crashes because GApps packages currently are missing the new Trichrome WebView implementation which replaces Chrome as the default WebView. This being worked on (see OpenGApps wiki and issue #773 on their GitHub.) For now, use another browser (like LineageOS's default browser) if you install GApps. —As soon as Trichrome is added onto the ARM package just as it has for ARM64, Chrome should be stable.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient! If you see any bugs, report them here.
Extremely huge shoutout to CodyF86 for this GSI!
The developer of this ROM has moved on to another phone and the community now has a full fledged 64-bit ROM which has much better support for things.
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. Things may break randomly, whoops, so please be patient!
Click to expand...
Click to collapse
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
everything works for me
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
so you can make phone calls without WIFI conection?
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
yesssss
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
taiyofurukawa said:
yesssss
Click to expand...
Click to collapse
How? What is your modem version/phone model?
Can't Boot
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
Bluetooth is horribly broken for now, it causes the app playing audio to lag and crash so please stay away from it.
Chrome is wonky at the moment. It'll work and then all of a sudden cause the whole OS to lag and crash or become unresponsive. This is possibly an upstream GApps issue.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient!
I am documenting everything on here. Stay tuned to that page for more info and further updates. Addiotionally, I have filed a bug report regarding calling, please add on to that GitHub issue and bump it so it can get resolved.
Click to expand...
Click to collapse
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
SomeAndrodGuyWithInternet said:
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
Click to expand...
Click to collapse
First off, are you unzipping the file? The standalone uncompressed file is unflashable. It needs to be decompressed from it's .gz (or whatever it was compressed to) form. If you have, have you tried using fastboot flash system <lineage file name> from a PC?
AgentICS said:
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
Click to expand...
Click to collapse
Just wanted to jump in here and say I'm seeing same bug on xt1925-6 with callers not able to hear me on any 10 gsi's and speakerphone does not work at all. Phh aosp 10 build 209 with stock pie 55-37-7-2 boot vendor boots fine, other gsi's will only boot using the Ali lineage full ROM boot- vendor but call audio is broken as well. Thanks for submitting the bug report, hopefully it will get fixed in future builds.
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
CodyF86 said:
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
Click to expand...
Click to collapse
That's amazing! Could you upload it please so I can test it?
Thank you!
AgentICS said:
That's amazing! Could you upload it please so I can test it?
Thank you!
Click to expand...
Click to collapse
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
CodyF86 said:
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
Click to expand...
Click to collapse
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
AgentICS said:
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
Click to expand...
Click to collapse
May have a fix for LTE compiling it now, using the stock apn file with the adjusted mcc mnc numbers.
If I could get root I could get it for sure, but I can't get it to boot with a magisk flashed kernel, even the android 10 special version of magisk.
I got LTE but now mobile network stays disconnected although there is an LTE connection. It's an apn issue will work on it. if I get it working will make a thread...not sure why magisk won't work with my builds / kernel though yet.
https://github.com/codyf86
I've noticed that restarting always restarts to the bootloader. I don't know if it's just me but that's weird
Could you provide a link to the kernel source used in the rom?
Uclydde said:
Could you provide a link to the kernel source used in the rom?
Click to expand...
Click to collapse
It's on his GitHub
The kernel is actually just the stock kernel from the latest firmware with the ',verity' flag hexedited out to disable encryption. (You also need to change the fstab that is in all the guides ever made including my original one), but I'm working on building the kernel and making it work...but I got LTE to woooooork with some changes to the stock apn file lineage provides ! lol.
Only thing now is that it thinks my external sd card is corrupted and wont format right unless i set it to adaptive storage, so make a backup of your external sd card for now. Going to try using TWRP to format it with a couple different file systems.
Here she is boys.
Lineage-17.1-02.22.20-treble-arm-system
Still working on getting it to boost with magisk not sure why it won't when it was fine in Pie.
Still playing with the apn file the apn its using says sprint ehrpd but not sure what makes it pick which apns to show on the screen, but the apn is set to x.boost.ispsn which makes LTE work. I'll clean it up soon.
(All of this is assuming you're on Boost / Sprint)