Related
Hi all, I am getting a sprint LG G2 soon and I am wondering if there is a way that I can use a verizon rom on it. If I can what do I have to do to port it over?
BEFORE YOU DO THIS MAKE SURE YOU HAVE A BACK UP!!!!!!!!!!!! Flash what ever rom you would like and immediately flash a kernal over top of that rom FOR YOUR DEVICE!!!!!!! I have done this with several roms not compatible for my tmo including Verizon international and att and rom. If you use a rom with an aroma installer DONT CHECK REBOOT NOW FLASH YOUR KERNAL OVER TOP OF ROM!!! ANY OTHER WAY AND YOU WILL BRICK. i have had great luck using trwp recovery to do this hope this helps. Also make sure you have titanium backupor something like it to remove what is not needed, also you may lose features doing this, and one more thing please make sure you know the programming code for your data setting to make sure you can switch the rom to evdo sprints 4g data. It may also be verizons code im not sure
I would not recommend this. It will definitely not work 100%.
What features are you looking for? There are several options with xposed mods.
Sent from LG G2 @sdny8
which version of phone are you coming from?
personally I am using U.S tmobile version, i have flashed international and ATT version. Verizon and Sprint seems to have additional hardware and network differences so I never try.
Hello guys. I have the n900t, I am now running tweaked s5 base n4 style v6.0. And I run alot of n9005 ROMS as well. With that said here is my issue. For only the past few weeks ( month tops) every time i make or recieve a phone call my data drips down to hspa. The second i hit call and right before my phone rings is when it happens. After my call the data takes a very long time to jump back up. This is a new issue and i have no idea what it is. However, i did flash back to a stock ROM and the issue was solved. And i forget which rom it was but it was soley TE based and there were no issues. I did try to flash a modem but it didnt take. Is anyone else experiencing this problem? Or can anyone suggest a fix for it.
Thank you for your help.
bump.
Still having the issue. I tried to flash a new modem and it just failed anyway. Dont know if I should try a radio. I just cant fivure out why this happened out of no where. I was fine no matter what ROM I was running. Now...this crap. Please guys, 40 people saw this, can SOMEBODY please help.
mattdiehl83 said:
Still having the issue. I tried to flash a new modem and it just failed anyway. Dont know if I should try a radio. I just cant fivure out why this happened out of no where. I was fine no matter what ROM I was running. Now...this crap. Please guys, 40 people saw this, can SOMEBODY please help.
Click to expand...
Click to collapse
1) Quite strange - your picture suggests you are on Verizon yet you comment about a N900T in the forum for the INTERNATIONAL Note 3. On what network are you? Are you aware that there might be network-specific factors involved which could only be visible for other users on exactly the same network in exactly the same region?
2) Try stock ROM (with corresponding stock modem) from a location with very good signal.
5 he physical device is an n900t, however, I am running as of now, the hyper drive note 5 port with n4 UI. When I do flash back to a full stock TW ROM all is good, A FEW TW based ROMs seem to be OK. Like this one, the calls do not affect the data signal. But most ROMs do effect it in that way. You said that it shows I'm running Verizon?
But I am very curious why all of the sudden I am having this issue. I have never had it before. Except with a few specific AOSP based ROMs. I just can't figure out what it is that's causing it. I have done vigorous wipes of the phone to no avail.
And I am in Philadelphia so there really is no place that is actually bad reception (except in the susubways of course...lol)
And thank you for your reply.
mattdiehl83 said:
5 he physical device is an n900t, however, I am running as of now, the hyper drive note 5 port with n4 UI. When I do flash back to a full stock TW ROM all is good, A FEW TW based ROMs seem to be OK. Like this one, the calls do not affect the data signal. But most ROMs do effect it in that way. You said that it shows I'm running Verizon?
But I am very curious why all of the sudden I am having this issue. I have never had it before. Except with a few specific AOSP based ROMs. I just can't figure out what it is that's causing it. I have done vigorous wipes of the phone to no avail.
And I am in Philadelphia so there really is no place that is actually bad reception (except in the susubways of course...lol)
And thank you for your reply.
Click to expand...
Click to collapse
1) Your avatar mentions Verizon for some reason.
2) If it is all OK with the stock ROM then it is a problem with the custom ROM, ask in the specific thread for that specific ROM. Most likely it has something to do with the modem and the corresponding RIL.
So when ever a new ROM is flashed the modem is flashed as well. Unless the dev says otherwise?
Hello!
I bought my mom an inexpensive S4 and it came with Orange wireless service provider and it's in French out for the box.
It's having some problem suck as MMS issues and all that, not to mention it's just being a pain in the butt to work with.
I want to flash the stock AT&T ROM to it ASAP so she will stop yelling at me about it, but I can't seem to find a copy around here. Maybe I'm just looking in the wrong areas, but I would appreciate some help locating it, thanks!
Also, it's been a while since I have done any ROM changes, so maybe showing me how they do it now would be helpful as well, thanks.
-Dave M.
AT&T ROMs cannot be installed on your phone. Odin will reject it at best, and you could hard brick the S4.
Unlock the phone by using the service menu exploit, RegionLock Away, or by purchasing an unlock code. Once the S4 is unlocked, you can install an unbranded firmware in place of the Orange-branded firmware. Keep in mind that this phone will never get LTE in the states as the frequencies are different.
Yes, I was made aware of the no 4G, no LTE issue with using a European phone by the guy who didn't know what he was doing when he programmed in the wrong APN settings at the AT&T corporate store...
Supposedly, the company I bought it off said this phone was unlocked already, so what then? It's been about 2 years since I did anything with ROMs, so I might be a little out of the know about the new stuff, thanks.
If it's already unlocked, then you can install any I9505 stock ROM you want. Download this ROM from Sammobile and follow the instructions on that page to install it. It's UK firmware so at the language prompt it will default to English. Be aware that you may have to flash the ROM twice before the S4's wireless radios function properly.
If everything goes as expected the APN should be automatically set. If not there are tutorials all over the place on adding an APN.
EDIT: Download the drivers from Samsung's website if not included in the Odin download on Sammobile. You'll need to have them installed for Odin to function.
Thanks. Now, how can I check to make sure this one is unlocked? Service mode is weird, because I had to do the Q followed by 0000 in key input to get it to give me the menu...
Put your Mom's AT&T SIM into the phone. If it asks for an unlock code then the S4 is still carrier locked.
Oh, okay. It's been working for like 2 months like this, lol.
Aren't there still a few carriers that aren't blocked for other regions? I just want to be sure, absolutely. I just want to know if there's another way to check.
Since it was Orange by origin (and those guys tend to lock stuff) I would say you would NOT be able to run AT&T on it as well (Orange ONLY lock - not really region lock)
When you say AT&T works I would assume previous owner already did what was needed and unlocked this device.
Sounds solid, thanks a bunch, fellas.
I just really wish there were a touchwiz ROM from AT&T for this particular model...
No, no you don't. If anything, you have it far easier by not having AT&T firmware. Unless of course you happen to LIKE encrypted (i.e. locked) bootloaders. AT&T and Verizon lock their bootloaders, which makes the simple things like rooting, bloatware removal, and custom ROMs far more difficult, and in some cases bordering on the impossible.
Your Mom may not give a damn, but by not having to deal with the headache of a locked bootloader you've made your life easier.
I've dealt with several so-called finished custom roms, such as the likes of such as Cyanogenmod and others, and lets just say they aren't quite as solid as the stuff that the phone comes with.
There's always something that doesn't work like it's supposed to or some important app that won't work somehow. Last time, I went with a stock rom, custom recovery (I like TWRP) and rooted the device and it ran just like I wanted. SO yeah, I'd like to use a stock touchwiz rom for the US if it's available somewhere.
I understand not wanting to toss a custom ROM on the phone, but that wasn't the point of my post. The ROM I prompted you to download several posts upthread is a stock Touchwiz ROM. In fact, up until this morning it was the same ROM I was using on my O2 I9505 that I'm using here in the US. As the I9505 is not available and never will be available from a carrier in the United States, there will never be a US ROM available for this phone. The ROM I had you download, unlike the AT&T ROM, has no carrier branding of any kind, no carrier bloatware, and no locked bootloader. As a result, you don't have the carrier meddling around with the ROM and making the experience worse by having crud added.
My point is, bluntly, that you're far better off now than you would be with an AT&T device. So, hopefully, now that you got everything sorted out your Mom can enjoy the phone.
Moto g5 plus 64g (single SIM),unlocked bootloader, root...4g works fine on stock ROM rooted w/Xposed
. ..and that's great but Ive flashed custom ROMs
Resurrection
...and Halogen
... and Desolation
... and they are very nice ROM s but I only get 3g (no LTE) and the only info I find on this is a quick-fix w/jio SIM using a DUAL SIM. .... Am I the only unlucky human w/a single SIM 3g problem?
I was so excited about this phone, thought I did all of my research , bought TWO 64g g5 plus phones(not 32g no way because I wanted to BEST lol but its single sim, stupid me).
...should I just give up on custom ROMs ? ...or is there something can be done?
Ive being at this for 2 weeks now...Any/all info very appreciated.
I would've posted in other forum but wouldn't let me due to lack of status....or rep...or bling..or something.
Do you have correct APN set? On some custom ROMs I have installed I had to change APN, because it was set to first in the list by default.
I dont know much about APN ...not durecwhst it's suppose to be set at..im boost mobile.. I'll start researching that next ..thanks brother
No luck.
I found the APN settings on Boost mobile site, I set/saved that to no avail.
I went back to stock/rooted and 4g works fine. But no matter which custom ROM I use I still only have 3g.
Surely someone somewhere knows how to set/fix this.
Can a Mod move this to where someone may have hands-on with this 3g vs 4g issue? Dev or someone?
Month later...5 custom roms later...still either no 4g on custom rom or no camera on simple root w magisk. I still can't post in Dev forum.
No LTE
Bigmotoxer said:
Month later...5 custom roms later...still either no 4g on custom rom or no camera on simple root w magisk. I still can't post in Dev forum.
Click to expand...
Click to collapse
Have the same problem, how did u go back to stock? TWRP restore? or did you fastboot flash stock fireware? I'm not sure if it makes a difference but after reading a few of these it looks like stock firmware may need to be reflashed with fastboot then start flashing custom ROMs with twrp. If you get the answer let me know if i find out I'll let you know?
Thanks
Update: yes there are ROMs that will fix the LTE problem, I was reading someone with a connection problem someone suggested downloading stock debloated , another suggested AOKP, downloaded both , first I tried debloated got LTE , then flashed the other, for VoLTE. Also I'm not sure if this is correct or not but fastboot flashing modems may work I'm not exactly sure and would need to look it up further is something else I read but didn't try as its 2:00am and I'm being yelled at by a hidden speaker in my kitchen which is why it took so long for me to even try to look for a reason because I've been getting yelled at so long I think I got cancer, I hope Santa brings them a tall glass of shut the f up so I get one day without being yelled at , also Lineage 15 says LTE working. I haven't used it since I don't want to mess with 8.0 right now. MeryXMaz
I'm havin the same issue. Also with Boost Mobile. Most other devices I've rooted have had some sort of boost/sprint/virgin APN fix .zip. But I donno....
RozWellZ said:
Have the same problem, how did u go back to stock? TWRP restore? or did you fastboot flash stock fireware? I'm not sure if it makes a difference but after reading a few of these it looks like stock firmware may need to be reflashed with fastboot then start flashing custom ROMs with twrp. If you get the answer let me know if i find out I'll let you know?
Thanks
Update: yes there are ROMs that will fix the LTE problem, I was reading someone with a connection problem someone suggested downloading stock debloated , another suggested AOKP, downloaded both , first I tried debloated got LTE , then flashed the other, for VoLTE. Also I'm not sure if this is correct or not but fastboot flashing modems may work I'm not exactly sure and would need to look it up further is something else I read but didn't try as its 2:00am and I'm being yelled at by a hidden speaker in my kitchen which is why it took so long for me to even try to look for a reason because I've been getting yelled at so long I think I got cancer, I hope Santa brings them a tall glass of shut the f up so I get one day without being yelled at , also Lineage 15 says LTE working. I haven't used it since I don't want to mess with 8.0 right now. MeryXMaz
Click to expand...
Click to collapse
Thanks for responding. I still haven't found a fix for the LTE. I will try to aokp again maybe something has been fixed or added. I did fix my camera problem by flashing elementalX so that's good. But not having LTE is not cool. And I also did not want to message w 8.0 yet.
So I tried AOKP to no avail. Still no 4g/LTE. That's time I'll never get back lol.
had the same problem XenonHD seems to work well...
I'll try it thanks
Hoping it'll get better with the official 8.0 release.
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!