i was on slim7 so that i could use sd card as internal storage (only reason i left stock rom since all i care about is a stable functioning phone) well when i did that i lost LTE signal and only receive 3g or 1x... i tried updating the modem (its a freedompop phone but i think it originated from boost) so i flashed the updater from buzbees post then the 6.0.1 modem.... well before i did that i switched to aosp extended to see if it worked on lte ( it did not) and when i booted up after all that my sim was not recognized. i restored to my original stock 5.1 rom and all is well, but i still want to use sd as internal storage which i believe needs at least marshmallow. I tried the port from buzbees 6.0 also, that stuck in an infinite loop. So my question is, do you know how i can get MM or N on my surnia xt1526 while still getting LTE with 3g fallback? I dont care about custom anything. i actually like stock. i just wish it would allow me to update to MM or higher.
Sorry for the long drawn out unorganized mess... its 2am and i'm at wits end, i've already spent all day fighting with this thing and i cant go another day without a phone (this is the only one in the house for my family.)
Thanks a bunch!
Ben
Have you tried this ported stock 7.1.1? https://forum.xda-developers.com/moto-e-2015/development/port-moto-stock-rom-moto-e-2015-t3676127
Related
So, I've flashed about 3 ROM's. Jelly bean's ROM, PAC-Man ROM and Team Carbon's ROM. Recently I just flashed Team Carbon's Nightly March 17 ROM build. After that, my 4G was completely gone and my single was acting weird. Wasn't showing Verizon Wireless in the toggles in the notification panel and wasn't getting a data connection at all, also wasn't getting any single bars for regular cellular connection (phone calls and text). But was able to place calls and such. I noticed this when I was about to turn on tether.
I've done my research, tried all possible solutions to the best of my knowledge and still, nothing. Has anyone had this issue before? I've seen one other post by someone who has the same phone and their thread didn't come to any resolution. There must be a fix. Can ROM's edit the sim card data? How can I force to activate when the phone won't let me? *228 won't let me.
I've already tried restoring to stock, factory reset from the stock settings and from TWRP (2.4.4.0). I have plenty of TWRP backups and tried them, but nothing seems to work. I'm betting the data on the sim was changed somehow and I know I did not do this intentionally. How would I?
I really do not want to call Verizon and have to get a new sim card, if they'll even give me a new one. Of course, I won't tell them I've been flashing ROM's and have unlocked my phone. But still.
[Edit] Corrently returning to stock via odin and am going to run a hard reset code. - Didn't Work. *2767*3855# doesn't work on Verizon Apparently.
If my Droid Incredible 4G LTE is connected to Wifi, it disconnects from Cellular Data. When I leave where ever it is connected to WifI, it won't connect back to cellular data. I have to turn off Wifi, then reboot the phone. I haven't tried something like switching to Airplane mode, I will try that. Has anybody else seen this issue? The phone is on Straight Talk Veriozon network, so is using SIM card for 4G LTE and CDMA for voice.
Are you stock?
No. Probably would help to mention that. S-OFF, partitions swapped and rooted CM 1.2.1 FWIW, this was happening with CM 11.2 before the partition swap. It wasn't happening before I did S-OFF and flashed CM 11.2 but I was also living in a different location for several months. It didn't start until I moved to where I am now.
I would try to do a clean reflash and see what happens.
I will think about that but I did a clean install when I did the partition swap and flashed the new ROM. I'd rather not do that again and have to set the phone back up again.
Today it seems to be better, I moved from Wifi to out and about and it switched to LTE properly.
therreid said:
I would try to do a clean reflash and see what happens.
Click to expand...
Click to collapse
I may have to try the reflash after all. The problem's gotten worse and now as of yesterday and today a reboot of the phone isn't getting me cellular data back. This did not start until we moved to a temporary place where I get voice service but not data at home. So the phone spends a lot of time on Wifi and not in a place where it can get data. So I'm wondering if the Verizon network is somehow forgetting about the phone or somesuch. At my old house, it was connected to Wifi but the data network was always available. The phone is S-Off with a custom bootloader and recovery. Assuming I wanted to try, can I put the stock ROM back on it without undoing all that?
crokett said:
I may have to try the reflash after all. The problem's gotten worse and now as of yesterday and today a reboot of the phone isn't getting me cellular data back. This did not start until we moved to a temporary place where I get voice service but not data at home. So the phone spends a lot of time on Wifi and not in a place where it can get data. So I'm wondering if the Verizon network is somehow forgetting about the phone or somesuch. At my old house, it was connected to Wifi but the data network was always available. The phone is S-Off with a custom bootloader and recovery. Assuming I wanted to try, can I put the stock ROM back on it without undoing all that?
Click to expand...
Click to collapse
If you want to go to stock, you will have to reverse the partition swap.
therreid said:
If you want to go to stock, you will have to reverse the partition swap.
Click to expand...
Click to collapse
That part I understand. What I should have asked was "if I want to go back to the stock ROM, do I need to undo the custom recovery, relock the bootloader, go S-ON, etc? Any other ROMS besides CM I might try? That could tell me if it is the ROM or not but, again I did not have this issue until I moved to an area where I can get voice, but no data.
You should be able to remain s-off. here are the stock packages if you don't have them, http://android.cmphys.com/stock-fireball/
crokett said:
That part I understand. What I should have asked was "if I want to go back to the stock ROM, do I need to undo the custom recovery, relock the bootloader, go S-ON, etc? Any other ROMS besides CM I might try? That could tell me if it is the ROM or not but, again I did not have this issue until I moved to an area where I can get voice, but no data.
Click to expand...
Click to collapse
Thanks. I will grab a stock ROM. I really like CM 12.1 (and the swapped partitions) though. I was able to get the phone back to cellular data this morning while I was on a chat with Straight Talk. Why a reboot worked then but not the 3 other times I have no idea. I'm also wondering what happens the next time this happens if I go into APN settings and change it to one that doesn't work, then change it back.
Over looking at the stock ROM downloads I see a link to this patch:
http://review.cyanogenmod.org/#/c/93484/
The ROM I am running now was built on 05/26. I see a newer CM 12.1 ROM dated 06/12 that contains that patch so I will flash that ROM, probably next week. I'm on call this weekend and don't want to risk bricking the phone.
I'm running the 6/12 build and it seems happy. I only run my Fireball on WIFI since I switched to AT&T and have a Nexus 5 for my primary.
crokett said:
Over looking at the stock ROM downloads I see a link to this patch:
http://review.cyanogenmod.org/#/c/93484/
The ROM I am running now was built on 05/26. I see a newer CM 12.1 ROM dated 06/12 that contains that patch so I will flash that ROM, probably next week. I'm on call this weekend and don't want to risk bricking the phone.
Click to expand...
Click to collapse
wmuflyer said:
I'm running the 6/12 build and it seems happy. I only run my Fireball on WIFI since I switched to AT&T and have a Nexus 5 for my primary.
Click to expand...
Click to collapse
Ive thought about getting a new phone on a GSM network but where we are building our house I can't get a ATT signal there, so I'm stuck with Verizon.
I installed Fulmics 5.2 rom on my Verizon lg g3, and now I am stuck in 3g, even though there is great 4g in my area? Anyone found a reliable fix, or should I give up on Fulmics (which is great otherwise)?
android94301 said:
I installed Fulmics 5.2 rom on my Verizon lg g3, and now I am stuck in 3g, even though there is great 4g in my area? Anyone found a reliable fix, or should I give up on Fulmics (which is great otherwise)?
Click to expand...
Click to collapse
+1000 to this request
I wasn't able to install it so you got further then I did. But I had that same issue on a number of non-stock ROMs and never found a "fix" other then trying diff nightlies until one worked. Another is very flaky WiFi which I'm seeing on XenonHD
Just simply give up. Nobody really has ever gotten an international GSM rom with working LTE on the VS985. A couple of months ago we got 3G working on fulmics 5.0. However to my dismay, when I flashed another ROM, I only had 3G data no matter what I used. It turned out that it wiped my EFS partiton, the one that controls call and data information. I had to wipe my phone with the stock KDZ file, and then re root and unlock.That really, really sucked. Moral of the story: give up on the international roms that say they're 'compatible' with the VS985. They're not.
josephsteven41 said:
Just simply give up. Nobody really has ever gotten an international GSM rom with working LTE on the VS985. A couple of months ago we got 3G working on fulmics 5.0. However to my dismay, when I flashed another ROM, I only had 3G data no matter what I used. It turned out that it wiped my EFS partiton, the one that controls call and data information. I had to wipe my phone with the stock KDZ file, and then re root and unlock.That really, really sucked. Moral of the story: give up on the international roms that say they're 'compatible' with the VS985. They're not.
Click to expand...
Click to collapse
Thanks!
Fulmics was a wonderful ROM except for Verizon 4g, so now I'll restore to something else. Wish I knew this first, wasted a bunch of time.
No problem man!
I've got it working, I think, my data icon shows a 4G. I've found a post in fulmics thread that says to get it working you should wipe, flash then bootstack, flash fulmics and once again flash the bootstack.
Some times in former versions i've got it working just wiping, flashing fulmics, booting without data and flashing the bootstack after all, so I guess that flash the bootstack after fulmics gets the point.
Give it a try and post back!!!
jmenc said:
I've got it working, I think, my data icon shows a 4G. I've found a post in fulmics thread that says to get it working you should wipe, flash then bootstack, flash fulmics and once again flash the bootstack.
Some times in former versions i've got it working just wiping, flashing fulmics, booting without data and flashing the bootstack after all, so I guess that flash the bootstack after fulmics gets the point.
Give it a try and post back!!!
Click to expand...
Click to collapse
I've tried that before, however all I ended up getting is a 4G roaming data icon. Is it showing as roaming for you?
I would go back to fulmics, but I'll admit I was only using it to have a little look at UX 5.0. Then it wiped my EFS partition, so I'm not gonna go back. If it works for you then great! Happy on xenonHD right now though.
For the last two weeks, I've miraculously had 4G LTE working on my vs985 despite using the 35b bootstack and 47a stock firmware (rooted and debloated)
I know it was just on band 4, and the 35b radio disables LTE on non Verizon networks. But somehow, amazingly, it was working anyway even across reboots, cache wipes, flashing zips for xposed, and even TWRP backups/restorations.
But when I removed my SIM card, put it in my old phone, and then put it back in my vs985, I lost 4G LTE!
Here are all the details I can remember, although I don't know what might be relevant or accurate:
Originally, I flashed to 10B stock using the TOT. From there I rooted and installed TWRP and flashed various roms to see what works best. I ended up on CM13, but at that point, my SIM card wasn't being detected at all, and I actually took it to AT&T to check my SIM and it was fine. They told me the phone must have re-locked itself. So I went home and wiped everything but microSD. I flashed the 35b bootstack, vs98547a rooted stock. I set up the phone with my google account and put in AT&Ts NXTGENPHONE APN settings. THEN I flashed a debloat zip (even though it gives you more space if you do it before starting the phone.) When I left the house and my phone disconnected from the Wifi, I had a 4G LTE signal! I had no idea how I got so lucky! When I got home, I made a full backup with TWRP, and kept only the zips I had just used for this setup.
So I got comfortable with the phone for two weeks, and now I'm crushed to have lost LTE! I can still use mobile data if I change my APN settings to "phone" instead of NXTGENPHONE, but it's obviously slower.
I wish I knew exactly why I manged that minor miracle for two weeks. I tried everything again, even flashing TOT, but without luck and I have no idea what perfect storm of events may have affected that magical time.
The zips I saved were: 35b bootstack, rooted vs98547a, and a custom debloat zip. I also saved the 10b radio zip, but I just can't remember if I used it that last time. I can't imagine I did, because obviously it wouldn't work with 47a. But then why did I keep it?
My guess is that somehow I got around the disabling of LTE, perhaps by having something specific flashed to a partition that only TOT can reach? Or maybe an LTEconfig got deleted or modified? Did I somehow hybridize the radios? I heard that maybe autoprime is working on a unified radio that might solve this problem?
Do you guys have any ideas? How did I ever make it work?
Before I go willy-nilly downloading things does this solution actually work??
https://forum.xda-developers.com/gal...s-sim-t3640689
It's basic, libsec-ril.so is for sim card.
If your sim card is working before download Lineage OS you simply no need to download baseband/upgrade modem.
1.Need Root device
Example Magisk, SuperSU
2.Need Root File Manager
Example Root Explorer
3.Replace this file
Root/System/Lib/libsec-ril.so
0.How to get working sim card libsec-ril.so ?
-Find Lineage OS previous version that can make your sim card exist in your phone.
-Flash rom to that old version.
-Go to Root/System/Lib/ and backup libsec-ril.so
-Flash rom to new version and go to step 3 to replace file
-Turn Airplane mode on off, if not working reboot.
Or you can use this link to download libsec-ril.so
drive.google.com/file/d/0B8Z3Yq1NlXEfeEVlaFcxSGVXR0U/view?usp=drivesdk
Im sure file in that link is working for all note3 hlte if not please go to step 0
Well I solved the problem by loading a build adapted for Sprint users.. I am no way connected to this project but wanted to update my own question
[ROM][10.0.0_r33] SuperiorOS - Phoenix [OFFICIAL][HLTE/CHN/KOR/TMO]
https://forum.xda-developers.com/galaxy-note-3/development/rom-superioros-phoenix-t4086515
I can receive calls and text but cant send them on my Sprint note 3 (flashed to assurance wireless service *I dont have a sim card never did*) any advice?
SurageBook said:
I can receive calls and text but cant send them on my Sprint note 3 (flashed to assurance wireless service *I dont have a sim card never did*) any advice?
Click to expand...
Click to collapse
I suspect it is a problem with using the Assurance Service.. What ROM are you using?
Im trying to use SuperiorOS - Phoenix
I'm also having issues. Can't send or receive calls/texts and can't access "carrier settings" and most of the dialer codes for hidden menus don't work (SuperiorOS)
I know Sprint is weird because it did not use a SIM card so the ROM has to be compiled in such a way that it can be pre-set with the Sprint onboard chip. I know it worked with Superior OS with my Sprint phone on a Sprint account.
Other than that I am not sure what else I can add to this. I actually returned back to Lineage running Pie since it is configured for Sprint..
Unidave199 said:
I suspect it is a problem with using the Assurance Service.. What ROM are you using?
Click to expand...
Click to collapse
Unidave199 said:
I know Sprint is weird because it did not use a SIM card so the ROM has to be compiled in such a way that it can be pre-set with the Sprint onboard chip. I know it worked with Superior OS with my Sprint phone on a Sprint account.
Other than that I am not sure what else I can add to this. I actually returned back to Lineage running Pie since it is configured for Sprint..
Click to expand...
Click to collapse
What twrp version did you use and what ROM did you have before flashing? Just asking because back in December I was using some ROM and took be about 3 days to get it work where I had the simmiluar issues that was fixed by trying different versions of twrp, wiping, and flashing in different orders I think
SurageBook said:
What twrp version did you use and what ROM did you have before flashing? Just asking because back in December I was using some ROM and took be about 3 days to get it work where I had the simmiluar issues that was fixed by trying different versions of twrp, wiping, and flashing in different orders I think
Click to expand...
Click to collapse
Thats a tricky one... Let me see... I was using a Resurrection Remix Nougat for quite some time.... but then jumped over to Resurrection Remix Pie. I have toyed with Superior OS but waiting for them to fix a few things before I go to it permenantly.
Really the biggest thing is when you jump past Nougat, the Bluetooth just gets unreliable. Bouts of not working, FC's and disconnects abound. But I have been running a automatic script to keep the bluetooth reconnecting if it gets dropped.
I was using TWRP 2.8.7.0 but you will have to move up to TWRP 3.0 and beyond if you want to run Pie or Android 10.
Hope that answers your question!
Dave
Unidave199 said:
Thats a tricky one... Let me see... I was using a Resurrection Remix Nougat for quite some time.... but then jumped over to Resurrection Remix Pie. I have toyed with Superior OS but waiting for them to fix a few things before I go to it permenantly.
Really the biggest thing is when you jump past Nougat, the Bluetooth just gets unreliable. Bouts of not working, FC's and disconnects abound. But I have been running a automatic script to keep the bluetooth reconnecting if it gets dropped.
I was using TWRP 2.8.7.0 but you will have to move up to TWRP 3.0 and beyond if you want to run Pie or Android 10.
Hope that answers your question!
Dave
Click to expand...
Click to collapse
Thanks! I think im on nougat.. Bootanimation is a pink unicorn on steroids. I'll give superior another shot in a few days when I don't feel like talking to anyone