Database Info

4G will not connect with differet ROM's (Wifi also)

Hey everyone!
Been lurking for months here and finally got the guts to try myself at installing a new ROM.
I have an LG G2X with Videotron here in Quebec Canada, we are stuck on Froyo and it will never get upgraded. :/
I rooted it without issues!
I also flashed CWM 5.0.2.8
I have backed up my stock ROM to SD Card.
I have installed the following ROM's with issues.
aokp_p999_build-37
won't boot, stays at LG logo
BionixReloaded_v1.4.1_FINAL
It runs. No 4G, Wifi connects and disconnects in a loop.
update-cm-7.2.0-RC1-p999-signed
Does not boot, stays at CM screen
update-cm-7.1.0-G2x-signed
It runs. No 4G, Wifi connects and disconnects in a loop.
Bionix2-TheLegacyContinues-RC1 with Bionix2-RC1-Patch
It runs. No 4G, Wifi connects and disconnects in a loop. I had 4G work in this ROM for a bit then it stopped.
Steps I have done from CWM
Wipe phone
Wipe Cache
Wipe Davik cache (or something like that!)
Formated System
Installed ROM from ZIP
reset permissions
I also backed up my APN settings from my stock rom and added into the packaged ROMS and still no go. The APN settings for Videotron were in them already. Phone portion works and SMS also, it does say Videotron when connected with cell antenna..
I know some people on Videotron have done it in the past and the only issues were with PAN settings which seem to have been added in newer ROMs.
I have searched endlessly and now I'm at a point where I can't see straight! lol
Any ideas would really be appreciated.
Marc

Ah man nevermind! lol I was tired and figured it out while driving back from work!
Thanks anyway!

Can you post your solution in case other people have the problem?
Sent from my LG-P999 using XDA

No probs!
In most cases I was just installing an update so I'm guessing that the ROM was partially running as I had not installed the base ROM and then the updates. But some of the full ROM's listed would not get passed the splash screens...
Now I have EaglesBlood™ Ice Cream Sandwich [AOSP 4.0.4] and it's running with minimal issues!
My Wifi and 4G are running without issues!
I've had a few EBLauncher crashes that required a battery pull...
The Voicemail notification does not work with this ROM for me...
EDIT: GMail does not Sync, I need to deactivate and reactivate Sync for it to work for 1 time only... Have to do this everytime I wan't to know if I have emails...
So far, no other issues. I will try to search for the issues I am experiencing now and see what I can fine. Could not find anything on the voicemail notification issue.

Trying to fix LTE

Hey guys, I have my HOX running AOKP JB 1.3 (found here) and have noticed that my LTE doesn't work. I only have an HSPA mobile connection.
Now in the FAQ's it says this:
**Q: No LTE?**
**A: Flash to a 4.0.3 based ROM, then flash AOKP**
Unfortunately, I'm such a noob I don't know exactly what that means. At first I assumed Android, but now I'm thinking it's the HTC Sense??
Digital fingers in the right direction greatly appreciated.

You assumed correctly just flash a 4.0.3 Rom, then flash cm. (After wiping of course)
Sent from my One X using xda app-developers app

CleanROm 4.0 is 4.0.3 base
blinkbomber said:
Hey guys, I have my HOX running AOKP JB 1.3 (found here) and have noticed that my LTE doesn't work. I only have an HSPA mobile connection.
Now in the FAQ's it says this:
**Q: No LTE?**
**A: Flash to a 4.0.3 based ROM, then flash AOKP**
Unfortunately, I'm such a noob I don't know exactly what that means. At first I assumed Android, but now I'm thinking it's the HTC Sense??
Digital fingers in the right direction greatly appreciated.
Click to expand...
Click to collapse
4.0.3 refers to the "base" version of android that a given ROM is built from.
Try flashing CleanRom 4.0 - it is based on android 4.0.3 You can find it here: http://www.scottsroms.com/downloads.php?do=file&id=161

Here is what I did (I'm on att)...it worked for me, I can't guarantee it will work for you and I am not responsible if you end up with a brick
1) Hop on over here and download cleanrom 4.0 standard edition (towards the bottom )
http://www.scottsroms.com/downloads.php?do=cat&id=34
2) Reboot your phone to recovery, factory reset, wipe cache, dalvich cache
3) Install the cleanrom 4.0 you downloaded above
4) Restart your phone and make sure you have lte (no need to set up accounts or anything)
5) Boot to recovery, factory reset, wipe cache, dalvich cache
6) Install aokp jb 1.3
7-28) Enjoy
You might be able to start with step 0.5 and backup your current rom/settings and restore to that backup in step 6 instead of reinstalling jb 1.3 as the above method will reset your phone and remove your current setup.
This method did not require me to change apns or dial *#*#4636#*#* or anything.
Good luck!

Thanks guys. I'm downloading CleanROM as we speak. so I've got my fingers crossed. Will update upon completion.

hmm, well saw the 4G symbol on my status bar with CleanROM, but not the LTE symbol so maybe my specific area (Macon, GA) doesn't have LTE at the moment and just that super duper HSPA 4G thing, lol. oh well. it was fun! thanks anyways for the help guys! yall are awesome!

Thought I'd retry an old thread. I had AOKP like 6 weeks ago and LTE worked great. Recently I have been using CR4.5Dev, CR4.5, or CM10. All of them I have had no problems with LTE.
Went to flash AOKP today and had no LTE. Remembered I had to come from a 4.0.3 ROM, so I flashed CleanRom 4.0 and booted up to check my LTE. Worked great. Went back and flashed AOKP. No LTE. I tried deleted the APN and reinserting it with no luck.
Going to try to re-reflash CR, and then flash AOKP for the 3rd time and hope for the best.
I can't live without LTE in San Diego. HSPA+ doesn't work on my drive home for streaming because it's way over used.

[Q] Wifi Issues

I would have posted this in the Sensation Android development area, but I don't have sufficient privileges to do so.
I no longer have WiFi.
I am using the 4.1.2 CM Kang, and I originally had WiFi working with that ROM, but it stopped working about a weeks ago, and I can't get it to come back.
If I watch the Wifi on/off toggle, I can see it blink white for a split second then return to grayed out about once every 5-10 seconds.
I've checked the WiFi settings, and the only thing that looks peculiar is that the region code under Advanced says "Europe," but when I try to change that, it just reverts.
I have tried a factory data reset,re-flash of the ROM, and installing newer versions of the ROM with no luck.
Does anyone have any suggestions?

tried this ?

WiFi will not turn on
ganeshp said:
tried this ?
Click to expand...
Click to collapse
I tried to install WiFix Manager, and I followed the directions closely, but WiFi still will not turn on.
The country code always reverts back to Europe in the Advanced WiFi Settings.
I'm on T-Mobile US, running AOKP aokp_pyramid_unofficial_Oct-19-12.zip; a JB ROM; 4.1.2
I previously tried the CM10 Kang for the HTC Sensation, but switched ROMs to make sure that it wasn't issue with the ROM.
To be clear, my problem is not that the WiFi radio never locks to a particular signal, it's that the WiFi radio won't even turn on.
When I go to WiFi settings it just says, "Turning on WiFi...," and never actually turns on.
My best guess was that it had something to do with the WiFi country code, but that's really just a stab in the dark; open to suggestions.
Thanks

bump
Surely, there's someone out there that can help?

kosstheory said:
Surely, there's someone out there that can help?
Click to expand...
Click to collapse
In order of easiest and quickest to longest time it will take to do each one...
Install the latest version of the ROM (10/23) overtop of your existing rom (5 minutes)
If that doesn't work...
Do a full wipe and install a fresh copy of the latest version. (15 minutes, with Nandroid backup)
If that doesn't work...
Format your SD card (save all the contents to your computer first) (40 minutes between copying every to the computer and back to the SD card)
NON ROM RELATED OPTION IF YOU ARE S-OFF
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops. (5 minutes, but a little more involved)
My guess is that the full wipe and fresh install is the most likely to work the first time.

Skipjacks said:
Reinstall your firmware as it's possible something got messed up. You will have to boot to recovery after this and wipe cache and dalvik or you will get bootloops.
Click to expand...
Click to collapse
is there a sensation specific guide for this procedure?

Still perplexed
How do I know which kernel and radio combination should work best with my ROM. I switched out to AOKP to see if that was the problem, and I believe I'm using the 3.33 Kernel, but I don't know how to check to make sure it installed correctly.

Had the same problem as you but a full wipe and reflash would bring it back. Seems to be a CM10 problem since it happens with Bruce's and Paranoid roms. Try a Sense rom and see if wifi works.

Is OpenSense considered a "Sense ROM?"

http://forum.xda-developers.com/showthread.php?t=1926858
Try that rom, more stable and better performance than all the popular roms.

I had the same problem only option was another room Android_Revolution_HD-Sensation_6.8.0 (this is the rom)

so long, and thanks for all of the fish...
I figured it out.
I bought a Samsung Galaxy S III. WiFi is working again.
Thanks for all of the help!

wifi cm10
I have tried several CM10 roms. It is as you said about the region code. It reverts back to the original and doesnt save it on the settings

Even though editing db file doesn't work. Actually it changes the country code. I guess the ROM changes it during booting. Because while it boots you can see that the wifi is connecting first then goes off. I have tried several roms. DOnno what the problem is. probably JB both on cm10 and aokp

[Q] SMS won't send. Can receive/send MMS calls and Data

The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.

This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already

It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899

Just looking for more info
Sent from my SCH-I535 using Tapatalk

Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.

I'm 717
Sent from my SCH-I535 using Tapatalk

I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.

I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk

Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658

DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.

Anyone try aosp to see if fixed yet?

Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.

capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...

What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app

capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app

I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.

capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.

I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.

Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,

Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.

[Q] HELP NEEDED - No Service after installing AOSP ROM

Can someone please help me out with an issue I am having...?
I can't seem to get Service after installing an AOSP ROM. I have been messing around with this issue for several days now. When I install a 'NON AOSP' ROM such as 'the 'MOAR ROM' it works fine, but then I go to in recovery (Newest TWRP or Newest Philz Touch) and do all of the required 'Wipes' then Install an AOSP ROM like 'Fusion', 'PAC' or the most recent 'CM11 Nightly' and I do not get any Cellular Service (WiFi is fine) and I have been looking for answers for several days and I can't seem to find any.
Can someone please help me out and let me know what I need to do, or point me to the right direction?
Thanks in advance for any help and/or resources that anyone can provide me with. It will be greatly appreciated.
Phone:
Sprint Samsung Galaxy S5 NE5 (Rooted with Knox Tripped :crying
MOAR ROM Installed / Touchwiz Interface.
_________________________________
My Web Design Portfolio

Same was happening to me on philz recovery . so I install trwp for sprint/Verizon . then I installed trwp manager from play store . I install the PAC ROM from in the app and let it wipe it self . and that did the trick at least for me. I have tried many ways like your self. Nothing work that's the only way I got it working. Hope that help.
Sent from my unknown using Tapatalk

I'll give it a shot and see what happens. Thanks for the tip...
Has anyone else had this problem? If so, can you post anything you did to get it working...
My Phone Thanks You...

Im having the same problem on both TW and AOSP. If I mess around with the connection settings I can get a signal but when I reboot its lost.
Ive tried both recoveries and its the same on both. Ive tried flashing modems but that did nothing
EDIT: Seems that any kernel that I flash breaks my phones signal, I need to test further to see what part of the kernel flash is causing this.

Whenever I download klte roms I had that problem. I could receive data and text, but I couldn't send any. I used Google voice until I flash kltespr roms. once I flashed the specific roms for our device it worked. Though I had to install ktoonez's version of twrp to get them to flash. That file can be found on the AICP thread.

Shad Stang said:
Whenever I download klte roms I had that problem. I could receive data and text, but I couldn't send any. I used Google voice until I flash kltespr roms. once I flashed the specific roms for our device it worked. Though I had to install ktoonez's version of twrp to get them to flash. That file can be found on the AICP thread.
Click to expand...
Click to collapse
I think you guys need to flash an APN package with klte roms. Kltespr roms should not have this problem, but if you run into it flashing the APN package shouldn;t hurt there either. Not sure if there is still an APN zip floating around, you may have to manually fix your APN.

It turns out that the custom kernel I was using broke the signal for some reason. Other than that, I had no problems as long as I flashed a kltespr rom. Klte roms worked for data if i used a virgin mobile apn, but there was no texting or calling.
I attached the flashable zip I used to get the virgin mobile apn. I would recommend flashing it right after you flash your rom.

having this same issue also..
i have tried several things.. going back to complete stock and working forward
no matter what i do i get no service on any AOSP rom.. im going to try this apn fix. hopefully it doesnt further break anything lol

Anyone figure this out yet? I've tried about 4 aosp roms and no luck.

PacMan rom with PA Gapps and Ktoonsez kernel worked for me. None of the others did so it must be a ROM issue.

Part of the reason kltespr was de-unified was because of issues like this.
When I'd fix something it would break something else for T-mobile or international.
So I would recommend sticking to kltespr builds for the time being.
Hopefully some work I'll be putting in soon will help get this back in gear.

garwynn said:
Part of the reason kltespr was de-unified was because of issues like this.
When I'd fix something it would break something else for T-mobile or international.
So I would recommend sticking to kltespr builds for the time being.
Hopefully some work I'll be putting in soon will help get this back in gear.
Click to expand...
Click to collapse
I couldn't get data on any kltespr builds except Pac Man and even then I lost data the next day for some reason. The new lollipop build has data working for me even though it's "GSM only" so just hoping it stays that way haha Waiting on fixes for battery drainage and I'll run it daily