Related
I HAVE FOUND TWO ROMS THAT ARE COMPLETELY FLASHABLE ON THE VERIZON GALAXY NOTE 3...FINALLY!!
NOTE: IN ORDER TO FLASH THESE ROMS YOU NEED TO HAVE A ROOTED VERIZON GALAXY NOTE 3 RUNNING THE NC2 OR NC4 FIRMWARE/BOOTLOADER AND SAFESTRAP VERSION 3.72
ALL FEATURES CURRENTLY WORKING (EXCEPT DATA)
NEED EXPERTISE:ALTHOUGH ALL FEATURES ARE CURRENTLY WORKING I CANNOT SEEM TO GET THE APN WORKING CORRECTLY I BEG OF YOU PLEASE FLASH BOTH ROMS THEY ARE VERY FUN TO PLAY AND AND TRY TO GET THE VERIZON NETWORK WORKING.... I CAN SEND/RECEIVE PHONE CALLS AND RECEIVE TEXTS HOWEVER I CANNOT SEND TEXTS/MMS AND GET THE DATA TO WORK..PLEASE NEED YOUR HELP
THESE ARE THE LINKS TO THE ROM THREADS AND YES I KNOW THEY ARE NOT IN THE VERIZON NOTE 3 THREAD THEY WORK COMPLETELY....
http://forum.xda-developers.com/showthread.php?t=2737234/U]
http://forum.xda-developers.com/showthread.php?t=2737257/U]
SIDE NOTES: THE PHONE RECOGNIZES ITS ON VERIZON AND DISPLAYS VERIZON AS A CARRIER...MY PHONE NUMBER SHOWS UP IN THE SETTINGS/PHONE INFO....I CAN RECEIVE SMS FINE WITHOUT CHANGING ANY APN SETTINGS...ANYONES INPUT IS NEEDED
Actually there is one more ROM that i was able to successfully flash, but it has some issues like the wifi wont scan any networks, which is a huge downside for me....so for now ima stick with the stock room. And if anyone wants to try it out and tell us if it works or not for them the ROM is here:http://forum.xda-developers.com/showthread.php?t=2752687
Any Luck?
Have you got data working yet? Might download it and play around with features.
Here are guides to porting roms ima noob so i cant really help
http://forum.xda-developers.com/showthread.php?t=2069850
http://forum.xda-developers.com/showthread.php?t=1908008
Hello everyone,
I'm a long-time member but seldom poster; owned several Samsung/Android devices in the past and rooted/installed custom ROMs in all of them, so I'm a not a newbie, have read the FAQs, searched, etc. I just got an I337M on my Fido renewal and was somewhat overwhelmed by warnings about requiring different approaches to rooting depending on the basebands, etc. Anyway, I have a couple of questions I did not find adequately answered and I hope you guys would be so kind to help.
In the course of composing this post, I took the plunge to root using CF-Auto-Root and install TWRP 2.8.3.0 - I guess Knox is now tripped and the warranty on my week-old phone is gone - oh well. Next on the agenda is to:
1) Unlock my phone;
2) Try to improve cell reception with a different modem (I have noticed I seldom have more than 2-3 bars while I have 2 other different devices in the same room on Koodo with full signal strength);
3) Flash @Danvdh's awesome 5.0.1 Lollipop GPE ROM.
My questions:
1) To unlock, it seems I have to downgrade to 4.2.2. first. @veryluckyguy suggests to get the MDJ ROM and only extract/flash the modem.bin and follow the rest of the instructions. Does the modem.bin get flashed over with any new complete ROM I flash or are they separate things? Will I lose the unlock when I flash a new ROM?
2) Are modems generally interchangeable across Android versions? For example, can I flash a 4.x modem in 5.0?
3) Anyone have experiences with poor reception on Fido/Rogers and solve it by flashing in different modem? If so, which?
Thanks for all help.
Like you I was on Fido and switched
1) To unlock I simply used online service for SIM unlocking. Cost $20
2) I am using a 4.x modem in 5.0.1 GPE ROM
3) I cannot answer your 3rd question as I simply switched service.
Hope this helps
I'd recommend you to not try any software related unlocking methods, they tend to give problems with some sim cards lately. requesting an unlock code with your imei is the best and safest way to unlock.
Thanks for the advice guys. Part of my wanting to do this was as a learning and tinkering experience. I could take my car to a garage to have it repaired or hire someone to do home reno work, but like most members of the site we are tinkerers. I don't have an immediate need to unlock my phone, so I'll wait for now until I have more time and maybe unlocking procedures/tools become more mature and robust. I'm happy that my phone is now rooted, TWRP'ed and 5.0.1 GPE'ed without having bricked it .
I'm still going to try to flash a different modem to try to get better reception.
Thanks to all the amazing help here!
1) To unlock, it seems I have to downgrade to 4.2.2. first. @veryluckyguy suggests to get the MDJ ROM and only extract/flash the modem.bin and follow the rest of the instructions. Does the modem.bin get flashed over with any new complete ROM I flash or are they separate things? Will I lose the unlock when I flash a new ROM?
2) Are modems generally interchangeable across Android versions? For example, can I flash a 4.x modem in 5.0?
3) Anyone have experiences with poor reception on Fido/Rogers and solve it by flashing in different modem? If so, which?
Click to expand...
Click to collapse
If you're still willing to unlock, consider flashing stock MDJ, rooting, then unlocking with RegionlockAway. From there, you can work your way back up to GPE 5.0.1 and the unlock will remain. I'm my experience, modems can be Odin flashed across Android versions, but compatibility discrepancies may subject the device to overall instability (ie. bootloops etc). I have found though that the modem from stock NC1 allows for Rogers LTE in 5.0.1.
Long story short, I was in a similar boat, but thanks to the help and advice from the members and contributors on this forum, I managed to find the solution. Here is a step-by-step. Good luck
Hello everyone,
I'm getting no service on my Sprint Galaxy S4 SPH-L720.
I've tried Slimkat 4.4.2, 5.0.1 and Google Play 5.0.1. I get service at times but it keeps cutting out for no reason. I am on baseband L720VPUFNAE, and PRL version 55020. I'm using an app called Roam Control which keeps the phone on roaming mode but it won't stay connected either. Even when set to force roaming it trys to connect to Sprint service. Perviously it would stay connected to Verizon.
Also on Slimkat 5.0.1 when enabling Roam Control it says "please make sure device is rooted" I know it is, because roam control doesn't give me that error on Slimkat 4.4.2 or Google Play Edition 5.0.1
I started having these issues about a week ago, before that everything was working fine. I was on Google Play Edition for a week, and then I started having these issues and went back to slimkat which worked flawlessly.
So to summarize this, phone will not stay connected to roaming no matter what I do. It wants to go back to Sprint, I've tried calling the ##872283# number or whatever it is. That didn't work, it told me it was unavailable and to try again.
Also, one time my cat knocked my phone off the table and it said no sim card inserted so I rebooted my phone and have been having issues since that day.
Did you check to make sure the SIM card didn't get jarred loose when it fell. If that's not it do you have a backup of your stock Rom you could restore? I have had connection problems before and going back to stock TW Rom restored it.
Hi, thanks for replying
I removed the sim card and put it back in, but that isn't fixing it.
I'm on GPE 5.0.1 latest update. Sometimes Roam Control works, and my phone will stay on roaming network, and sometimes it won't. Whenever I go to switch between Home and Roaming it doesn't want to go back to roaming. I have no idea what's going on.
Hi again,
So this is what i've noticed so far.
Slimkat 4.4.4 = Confirmed working, phone goes in and out of roaming back to Sprint network just fine. All data/mms works perfectly.
Slimkat 4.4.2 = Confirmed working, phone goes in and out of roaming back to Sprint network just fine. All data/mms works perfectly.
GooglePlayEdition 5.0.1 = Phone has intermediate service
Sacs Custom Rom v4 = Phone has no wifi, but the Roam Control works.
Slimkat 5.0.1 (Beta/Alpha) = Phone tells me it isn't rooted.
So the good news is, i've got the phone to be atleast usable now. But I want to know why these other roms are giving me problems, is it the baseband/modem I am using? Which one's am I supposed to be using for these roms?
From what I've read here on xda you have to be on the latest firmware, NG2 to have any success getting lollipop working smoothly. So I would look up how to use Odin to upgrade that. All the rooms that I've flashed recently have mentioned in the op to be sure you're on the latest firmware so it may also help with the other KK rooms.
I'm on Baseband version L720VPUFNAE isn't that the latest one?
No NAE is more than a year old NG2 was released last summer.
Hi,
I went ahead and updated to NG2 baseband using this file http://www.androidfilehost.com/?fid=23622183712458249 and Odin. (I am stating this to help people who might be Googling). It updated my Modem from the NAE one to the NG2 baseband, I am still on Slimkat 4.4.4. I will try flashing Google Play Edition 5.0.1 and see what happens.
Thank you guys for the assistance!
Does everything work the way it should on SK 444? If so make a backup so you have a solid place to revert to if you need it in the future. Also be sure to get a good GPS lock before flashing to a 5.0 Rom.
Yes everything works in Slimkat 4.4.4. The phone goes in and out of roaming without any hiccups. Also what do you mean by make sure you get a good GPS lock?
Furthermore, I have went back to Google Play Edition 5.0.1 and I am still experiencing the issue where my phone does not want to go back to roaming after being on the Sprint network. I will be out of service and the phone will just say "searching for service" even though I have Roam Control set too "Roam Only Mode". In order to get my phone to get service back I have to go into Cellular network settings and select System select and put my phone on Home only and then go back to Automatic to make the phone connect to the roaming network.
This is becoming a real nightmare.
The GPS not working was a common problem with GPS 5.x and having a good lock on your position in a stick TW Rom before flashing to GPE is supposed to fix it. So my comment was merely a preventive one. I have no idea for you on the roaming problem in GPE.
---------- Post added at 02:58 PM ---------- Previous post was at 02:52 PM ----------
Have you tried updating the profile and prl while in SK 444? Then flash into GPE, that's one thing I would try if you haven't done so.
Wonk258 said:
The GPS not working was a common problem with GPS 5.x and having a good lock on your position in a stick TW Rom before flashing to GPE is supposed to fix it. So my comment was merely a preventive one. I have no idea for you on the roaming problem in GPE.
---------- Post added at 02:58 PM ---------- Previous post was at 02:52 PM ----------
Have you tried updating the profile and prl while in SK 444? Then flash into GPE, that's one thing I would try if you haven't done so.
Click to expand...
Click to collapse
How would I go about updating the profile and PRL while in SK 444? It's based off of Cyanogenmod kernal, as is GPE.
trenth said:
How would I go about updating the profile and PRL while in SK 444? It's based off of Cyanogenmod kernal, as is GPE.
Click to expand...
Click to collapse
You must be on a stock touchwiz rom in order to update your data profile or prl.
Sent from my GT-I9505G using Tapatalk
My bad, I meant have you tried updating the prl and profile while in a stock TW rom? My apology for the confusion.
Here's another thought, perhaps try one of the other non GPE 5.x Roms to see if your troubles are limited to the one GPE Rom or if it's a lollipop issue. That may be useful info for those smarter than I to help you work this out.
trenth said:
Hello everyone,
I'm getting no service on my Sprint Galaxy S4 SPH-L720.
I've tried Slimkat 4.4.2, 5.0.1 and Google Play 5.0.1. I get service at times but it keeps cutting out for no reason. I am on baseband L720VPUFNAE, and PRL version 55020. I'm using an app called Roam Control which keeps the phone on roaming mode but it won't stay connected either. Even when set to force roaming it trys to connect to Sprint service. Perviously it would stay connected to Verizon.
Also on Slimkat 5.0.1 when enabling Roam Control it says "please make sure device is rooted" I know it is, because roam control doesn't give me that error on Slimkat 4.4.2 or Google Play Edition 5.0.1
I started having these issues about a week ago, before that everything was working fine. I was on Google Play Edition for a week, and then I started having these issues and went back to slimkat which worked flawlessly.
So to summarize this, phone will not stay connected to roaming no matter what I do. It wants to go back to Sprint, I've tried calling the ##872283# number or whatever it is. That didn't work, it told me it was unavailable and to try again.
Also, one time my cat knocked my phone off the table and it said no sim card inserted so I rebooted my phone and have been having issues since that day.
Click to expand...
Click to collapse
I may be having a related issue. I didn't want to make a separate thread in case this is the case.
My data was just fine about a week ago. Then I decided I'd try out a new ROM because there's a couple things that annoy me with CM12 at the moment, so I tried the GPE ROM. It was all great except I wasn't getting service when I'm at work.
The problem is that this is now the case with EVERY ROM I flash. I also tried nandroid restoring what I had before flashing GPE. I even went back to stock, did the whole PRL and Profile thing, but I still have no service.
What's also a problem is that I have service (LTE) at home, so whenever I get home to try a new thing that will hopefully fix the issue, I can't find out til I go back to work or leave home or whatever. So far, every day has been unsuccessful.
Edit: A weird thing is that even where I have LTE, if I go to view my network status, it shows "Out of service" under Service State, and Mobile Network State as disconnected. Actually just noticed this, but my phone number is 0.
Alright, so further testing has commenced.
I went over to a Touchwiz rom, updated my PRL, activated the phone, and did all of that. Went back to SlimKat 4.4.4 and thought my phone was on "Roam Only". Well turns out I was wrong, the phone is set to Roam Only and I am still trying to connect to Sprint towers while at home (Where I have no Sprint service) so something definately up. Maybe I need to re-root my phone as I am having some weird issues when it comes to root. Can someone perhaps link me to a thread to get started on rooting the device? I don't remember how I did it last year when I bought the phone. But I am comfortable with using Odin and SamsungKey drivers.
Hello all.
I am having some issues with my Galaxy S4.
I have read through a lot of the signal loss threads the last couple of days.
But I'll explain why those were not helpful to me.
I started by rooting my phone with cf auto root jfte.
Via Odin 3.10.
I then installed twrp and some cm roms.
And experimented with a few different roms and software.
I wasn't bothered about bricking my phone.
I think I did soft brick it a few times but thanks to the help from xda threads I got it back a few times. So thanks for that guys.
Now I am running an official EE rom and modem.
Everything works perfectly and smoothly I am no longer rooted.
But no longer have any signal.
The imei is in tact.
The sim is being read by the phone and also knows what network it's supposed to be on etc.
The phone can search and see the networks sometimes but cannot register on them.
I did try an app while I was patting about with roms called region lock away. As some people said it can some times network unlock the phone.
And it seemingly did with mine.
However a few roms later and I cannot revert whatever it done.
Any ideas on how I can get my signal back would be greatly apreciated.
Thanks.
Andy.
Can anyone assist with this?
So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew
drewcu said:
So I have posted before without any replies and am still seeking help...
I know there are others out there in the same situation as me:
On an Unlocked VZW bootloader
On Verizon Wireless 4G LTE in the US
Trying to run a Custom ROM on their phone
But for some reason, I seem to be the only one who has a random delayed texts (both SMS and MMS) issue (by 1-15 minutes) on these forums. Sometimes on Custom ROMs the texts come in normally but other times there is a long delay and it makes having a conversation with people very difficult and irritating. There is NO text delay on rooted (Magisk) QL1, the latest Samsung stock TW S5 6.0.1 ROM, and I have gone back to it since I have no more ideas left to try.
What I have tried:
AEX 5.8 (Oreo 8.1), Havoc OS (8.1), Lineage 15.1 (Latest 8.1), crDroid 3.8.5 (7.1.2), MoKee (7.1.2), AOKP (7.1.2)
Changing APN settings to include the MMSC http://mms.vtext.com/servlets/mms and leave blank which is the default on Custom/Stock ROMs
Changing APN settings to match the stock VZW settings exactly
Flashed new VZW APN files from an ltefix.zip file I found on XDA
Changing CDMA to be Home and not just Automatic
Changing from Global to CDMA/LTE+EVDO
Went to the Verizon store and got a new SIM card
Booted up without SIM and powered off; then inserted SIM and booted up again
Tried different Modem/Non-HLOS versions like QC2 and QL1
Went into the secret *#*#4636#*#* Phone menu to see what differences exist between stock and Custom ROM settings
Added some lines from the stock VZW Build Prop to Custom ROM Build Prop
Removing HD Voice/VoLTE from my Verizon account
Avoided installing any apps after flashing a Custom ROM to see if the problem remained
Nothing worked! Still get Delayed Texts trying everything I could think of, except when on the stock VZW ROM. Custom ROMs may boot up showing my carrier as Verizon Wireless, but then after some random amount of time will show the Carrier as either "Unknown" (7.1.2) or "Roaming Indicator Off" (8.1). It is usually at that time when the Delayed Texts issue arises once the phone loses its lock on Verizon.
This makes me think it is a Verizon Band issue where for some reason not enough Bands are available for my phone to use on these Non-Verizon Custom ROMs. Or it could have something to do with VoLTE being active on my account at one point (I turned it off on My Verizon to try to combat this problem). Or maybe something to do with how we all unlocked the bootloader in the same way.
But what I don't understand is why I am the only person with this issue since I am pretty sure there are a lot of people on Verizon with CID 15 on Custom ROMs who don't seem to be mentioning this problem!
Any thoughts on how to fix it? Could it be a matter of augmenting the Bands my phone has access to on the Custom ROMs?
Thank you very much!
Drew
Click to expand...
Click to collapse
When you are on stock you are seeing the verizon lte correct? It not showing unkown?
I have a CID 15 I can try and see if that one is having an issues. it has an older lineage rom on it but it should still work for a test.
Fear_The_Fluff said:
When you are on stock you are seeing the verizon lte correct? It not showing unkown?
I have a CID 15 I can try and see if that one is having an issues. it has an older lineage rom on it but it should still work for a test.
Click to expand...
Click to collapse
Yes, stock shows Verizon as the Network in Settings/About Phone/Status and Verizon Wireless as Carrier and LTE as Type in the secret phone settings page I get to through the app Advanced Signal Status.
Appreciate your assistance in testing Lineage on your CID 15. Since no one else seems to be complaining I have a feeling it will show as Verizon as you'd expect. Feels very lonely on my island lol, but at least rooted stock with Xposed is livable for now.
drewcu said:
Yes, stock shows Verizon as the Network in Settings/About Phone/Status and Verizon Wireless as Carrier and LTE as Type in the secret phone settings page I get to through the app Advanced Signal Status.
Appreciate your assistance in testing Lineage on your CID 15. Since no one else seems to be complaining I have a feeling it will show as Verizon as you'd expect. Feels very lonely on my island lol, but at least rooted stock with Xposed is livable for now.
Click to expand...
Click to collapse
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Fear_The_Fluff said:
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Click to expand...
Click to collapse
Thanks for trying! Assume you waited a while with the S5 in Lineage before responding because mine will start as Verizon but then after 1-30 minutes will switch over to Unknown.
Yeah I recently came across the same post in my research on this. Seems like most of the people who used that guide weren't able to do anything with their modem like call or had missing SIM card messages. I have always had the ability to call except when I debloated the stock ROM too much lol! I am hesitant to start deleting modem files and find myself in worse trouble than I am in now when stock works perfectly (aside from the lagginess).
Besides this issue with Lineage Oreo, I also found AOSP Extended Oreo to be a huge battery hog because my phone ran HOT (but maybe it's related to my main modem? issue). On stock, I almost never find the thing getting warm, it's just not as smooth as Oreo is. I am going to let S5 Oreo mature further and improve on the battery performance before going back to it I think and just stay on working stock for now. If I had concrete evidence that my daily driver could be fixed without any risk, I might consider following instructions.
Appreciate your assistance regardless since no one else has really made any suggestions!
Thank you!
Drew
drewcu said:
Thanks for trying! Assume you waited a while with the S5 in Lineage before responding because mine will start as Verizon but then after 1-30 minutes will switch over to Unknown.
Yeah I recently came across the same post in my research on this. Seems like most of the people who used that guide weren't able to do anything with their modem like call or had missing SIM card messages. I have always had the ability to call except when I debloated the stock ROM too much lol! I am hesitant to start deleting modem files and find myself in worse trouble than I am in now when stock works perfectly (aside from the lagginess).
Besides this issue with Lineage Oreo, I also found AOSP Extended Oreo to be a huge battery hog because my phone ran HOT (but maybe it's related to my main modem? issue). On stock, I almost never find the thing getting warm, it's just not as smooth as Oreo is. I am going to let S5 Oreo mature further and improve on the battery performance before going back to it I think and just stay on working stock for now. If I had concrete evidence that my daily driver could be fixed without any risk, I might consider following instructions.
Appreciate your assistance regardless since no one else has really made any suggestions!
Thank you!
Drew
Click to expand...
Click to collapse
I tried this one once when my old sprint S5 didn't have 4G. I ended up with no network at all, I had to do a forget network and reboot to get everything back. I never got that phone fixed I know there is another forum about that issue as well:
https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-galaxy-note-3-sprint-help-t3698708
Most people were able to get it fixed by replacing the SIM, but since you did that I didn't mention this post.
UPDATE:
Forgot to ask, have you tried a different messenger? I know it wont fix you unknown errors but I thought I'd ask. Also, when you did the modem update, was it this update: https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630
Fear_The_Fluff said:
I tried this one once when my old sprint S5 didn't have 4G. I ended up with no network at all, I had to do a forget network and reboot to get everything back. I never got that phone fixed I know there is another forum about that issue as well:
https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-galaxy-note-3-sprint-help-t3698708
Most people were able to get it fixed by replacing the SIM, but since you did that I didn't mention this post.
UPDATE:
Forgot to ask, have you tried a different messenger? I know it wont fix you unknown errors but I thought I'd ask. Also, when you did the modem update, was it this update: https://forum.xda-developers.com/verizon-galaxy-s5/development/modem-modems-t3154630
Click to expand...
Click to collapse
Thanks for the quick reply!
You tried the deleting the modems fix or the link in your prior post for your Spring S5? And what is a "forget network" fix -- just resetting all network settings in Android?
Yeah I was really hoping the replacement SIM would fix it but sadly it was a dead end.
I have tried several messengers like the stock Lineage one, Google Messenger, and landed on Textra because it has the most configuration options.
Yeah I tried Odining modems from both the link you referenced and extracting them myself from the firmware. Not sure if this is essentially the same thing as overwriting the modems in the corrupted TWRP modem guide. I am tempted to try this over the weekend after making an EFS backup. Hard for me to believe that deleting modemst1 partitions and not restoring them afterwards as is what seems to be the fix... Does the system automatically rebuild them or something?
Fear_The_Fluff said:
No issues with my S5, but I later remembered this post:
https://forum.xda-developers.com/galaxy-s5/help/solved-unknown-baseband-fixed-t3680402
Try it, I know it was a huge problem awhile back, maybe this will help you.
Click to expand...
Click to collapse
So I decided to bite the bullet and run the dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and 2 in TWRP terminal and got the "No space left on device" in the output (tried over ADB with the same result). Supposedly this isn't necessarily a bad thing as evidenced https://forum.xda-developers.com/showpost.php?p=68532486&postcount=115. Had no problems on stock after doing this (but had no problems on stock prior either).
Then I switched back to AOSP Extended 5.8 (Oreo) and sadly I got the Roaming Indicator Off right away. I tried zeroing out the modemst's again with the same No Space result and back in Oreo got the same delayed texts and Roaming Indicator Off after a few minutes. Dead end, but at least I tried I guess. I am back on stock and my only other thought is to unlock some LTE bands but that may be too technical for me to bother with. Stock works with the current bands so I wonder why I should have to do that on Lineaage.
drewcu said:
So I decided to bite the bullet and run the dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and 2 in TWRP terminal and got the "No space left on device" in the output (tried over ADB with the same result). Supposedly this isn't necessarily a bad thing as evidenced https://forum.xda-developers.com/showpost.php?p=68532486&postcount=115. Had no problems on stock after doing this (but had no problems on stock prior either).
Then I switched back to AOSP Extended 5.8 (Oreo) and sadly I got the Roaming Indicator Off right away. I tried zeroing out the modemst's again with the same No Space result and back in Oreo got the same delayed texts and Roaming Indicator Off after a few minutes. Dead end, but at least I tried I guess. I am back on stock and my only other thought is to unlock some LTE bands but that may be too technical for me to bother with. Stock works with the current bands so I wonder why I should have to do that on Lineaage.
Click to expand...
Click to collapse
This bug has been around for awhile and affects all S5s differently and at different times. There are still S5s that work great, who knows if they will ever gets this bug. You may want go to the Lineage post on XDA to see if they maybe able to help you. Maybe something has changed since I gave up on my S5. Good Luck!
Fear_The_Fluff said:
This bug has been around for awhile and affects all S5s differently and at different times. There are still S5s that work great, who knows if they will ever gets this bug. You may want go to the Lineage post on XDA to see if they maybe able to help you. Maybe something has changed since I gave up on my S5. Good Luck!
Click to expand...
Click to collapse
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100 (think we all have the same)? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
drewcu said:
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
Click to expand...
Click to collapse
My Verizon S5 (this is the working phone) is a CID 15 (I don't have the phone with me right now to get the CID ID), I can look around for the setup I used. It was some months ago when I ran the bootloader unlock and root. BUT! the phone I had an issue with the LTE was a sprint S5 that was unlocked for years before they started locking the bootloaders. This bug affects all carriers, but mostly sprint and verizon.
drewcu said:
Can you do me one more favor and tell me if your CID is 1501004d414732474300bd6d97165100 (think we all have the same)? Not sure if my problem relates to the way my S5 was unlocked as I originally used one of the early unlock methods (wipe the SD) from https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909. Thanks!
Click to expand...
Click to collapse
Here is the root I used: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Fear_The_Fluff said:
Here is the root I used: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
Thanks yeah that's the more recent method and I am just trying to figure out if that results in the same CID I have. If not, there may be some issue because I am using the same CID as others. But perhaps we all are using the same CID and then I can cross that theory off my long list haha. When you get a chance, can you please check the CID of the Verizon S5 you have?
Thanks!
drewcu said:
Thanks yeah that's the more recent method and I am just trying to figure out if that results in the same CID I have. If not, there may be some issue because I am using the same CID as others. But perhaps we all are using the same CID and then I can cross that theory off my long list haha. When you get a chance, can you please check the CID of the Verizon S5 you have?
Thanks!
Click to expand...
Click to collapse
The CID doesn't change, its just the Chip ID of the phone. You either have the CID 11, which you wouldn't be able to unlock the boot loader let alone put lineage on it. Then there's the CID 15 which does let you unlock the boot loader. I never used the CID checker I ended up finding out if I had a 15 by going to this forum: https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
Now, with that being said, could there be some sort of correlation between a CID 15 with a specific version number and the bug? Its possible, I could have a different CID 15 version than you and that one may not be affected. Who knows
Fear_The_Fluff said:
The CID doesn't change, its just the Chip ID of the phone. You either have the CID 11, which you wouldn't be able to unlock the boot loader let alone put lineage on it. Then there's the CID 15 which does let you unlock the boot loader. I never used the CID checker I ended up finding out if I had a 15 by going to this forum: https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
Now, with that being said, could there be some sort of correlation between a CID 15 with a specific version number and the bug? Its possible, I could have a different CID 15 version than you and that one may not be affected. Who knows
Click to expand...
Click to collapse
Pretty sure this whole unlocking the bootloader on CID 15 requires that you change your CID to match the Developer CID. I know that my current CID is referenced in the thread https://forum.xda-developers.com/ve...locking-galaxys-s5-bootloader-t3337909/page39 back when this was all just coming out (and when I first unlocked it using the old method 4 - https://forum.xda-developers.com/ve...t/rd-unlocking-galaxys-s5-bootloader-t3337909). I used to have a different CID that's saved somewhere else.
Any chance you can look your CID to see if it matches 1501004d414732474300bd6d97165100?
Thanks!