Hello everyone,
Today my 6T got bricked and was solved. But it got bricked by restoring a nandroid backup from 9.0.15 after installing 9.0.16. The reason I restored my 6T was becuase I couldn't remove/swipe my notifications in the quick settings panel?! Also my dark theme was broken still since 9.0.14. What are people experiencing for the 9.0.16 update? I found the cause of my issue and it was the ainur Sauron magisk module I installed before the update. So I removed it and it is now fixed
Rooted 6T user here. I haven't had an issue with any of the versions. I upgraded to .16 per the upgrade thread the other day, and I haven't noticed anything different. Love this phone. Did the T-Mobile to international conversion when it became available. I also replaced the tray with the dual sim tray, both sim slots work fine. The Verizon mvno sims do not work however, because you cannot specify volte with them. Maybe after the beginning of next year. I wanted to run the 2nd sim as backup when I'm in the boonies sometimes. The ATT sim worked alright, but even it lost reception in spots that T-Mobile had no reception. It's fun to play with.
mmarcz
Just installed it today--running like a dream, but too soon to say if it's stable beyond that.
The install was flawless with instructions from @Funk Wizard here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
no problem has occurred yet. flawless.
It's labeled 'stable'. So it's stable as far as an OS can be stable.
As each build resolves some bugs and gives up to date security features, they is no question to ask...
Related
Posting here since I don't have privileges to post in the development forum. Has anyone tested squid2's CyanogenMod ROM with T-mobile US?
I flashed the ROM after factory wipe and everything works except call sound. However, if I set the network to 2G or 3G the problem goes away. Has anyone been able to get phone calls to work while on LTE? My model is an XT1607.
Similar issue was reported but someone said doing a clean install worked for them. I experienced the same issue as you do but don't have the time to do another install to really see if it solved the issue or not.
Yeah I saw that post as well, unfortunately it did not work for me. I tried wiping and re flashing a number of times. I wonder if this has something to do with VoLTE support like in this thread: forum.cyanogenmod.org/topic/125114-cant-makereceive-voice-calls-on-the-t-mobile-lte-network-after-cm-13 (copy/paste since I can't post links yet)
Same problem here on a clean install of 11/9 cm13. I'm going back to stock for now. Hopefully if we get a working cm14.1 VoLTE will be working.
Hey all,
First time posting, but have been rooting all my android phones using different guides on xda. This one, however, I am having issues with. I have a Moto G4, Amazon subsidized phone, running on Verizon. Whenever I install a custom rom LTE works until I reboot. Once I reboot, it shows 3G regardless of where I am and runs at those reduced speeds.
I have tried Ressurection, Lineage, CM and AOKP. I have two of these phones and on one I upgraded to N firmware and still had the issue. On the one I am using, I am flashing over the stock firmware and all works great until that first reboot regardless of what it is for.
Even if I revert back to a backup made in TWRP, it does not recognize LTE so it makes me think some type of setting is swapping over but I cannot figure out what it is.
Any ideas would be great. I can provide any other information needed, as this is my first time making a post so was unsure what to include. Also, I apologize if this is answered somewhere as my search-fu was failing me.
Thank you!
EDIT: If I restore back to stock firmware using fastboot and lock the bootloader, LTE returns.
I experience the same exact issue with my g4 running on sprint. i do not have the amazon variant. i purchased mine from best buy. i made a post about this a few weeks ago but it never was answered.
I purchased my Moto G4 Plus from Motorola/Lenovo almost a year ago. FIrst I used StaightTalk/ATT and then switched to ATT prepaid. The 4G LTE worked great with both prepaid plans. Soon after I started to use the phone, the updates became very annoying (especially when interrupting GPS/Google maps and navigation while driving) so I followed this guide and rooted my phone:
https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
I did not install TWRP permanently and only ran the image. My bootloader is still unlocked. The only root ap I've used (via SuperSU) is SDMaid, to freeze the Motorola update process. (I purchased both excellent aps to support development, BTW, but they work so well, I've never needed their support!)
I'm moving and ATT towers are not available near my new home so I just switched to Verizon prepaid at Walmart today. 4G stopped working. I have a ticket with Verizon open but I've learned that I'm not the first with this problem--either on the Moto 4G or other phones!
I read as many threads here on the subject as I could stand to read. Those who had some success with changing settings (Settings >> Cellular Networks, APN, network type, etc.) are luckier than I! Nothing is working for me so far.
I'm not a "cell phone guy." What do you experts here in xda-dev recommend for my next steps. I don't have much faith in Verizon customer service!
Oh...I forgot to mention that I also flashed the image to wipe the annoying unlocked bootloader warning image on boot. That's all I can think of in the way of mods I've made to my phone.
Thank you for moving this topic. I thought I was posting in the QA section (my Internet is so slow, the entire screen fails to load and I was not where I thought I was).
My gut feeling is this is a hardware problem (a signal integrity problem in reading the SIM card). For any other Moto G4 users who stumble upon this thread, I found a discussion over on the Lenovo site:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/MotoG4thGen/thread-id/7585/highlight/false/page/1
Thank you all here at xda-developers who have read my post in consideration of my problem. I will restore and try install Nougat, which reportedly fixes the problem sometimes. I will post an update for Moto G4 users here too.
calinb7 said:
Thank you for moving this topic. I thought I was posting in the QA section (my Internet is so slow, the entire screen fails to load and I was not where I thought I was).
My gut feeling is this is a hardware problem (a signal integrity problem in reading the SIM card). For any other Moto G4 users who stumble upon this thread, I found a discussion over on the Lenovo site:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/MotoG4thGen/thread-id/7585/highlight/false/page/1
Thank you all here at xda-developers who have read my post in consideration of my problem. I will restore and try install Nougat, which reportedly fixes the problem sometimes. I will post an update for Moto G4 users here too.
Click to expand...
Click to collapse
What is your model? XT1644? What is your software currently (go to "Settings", "About phone", "Build number"
I un-rooted and took the OTA Nougat update, which fixed the problem (now getting LTE service). I suspect there is either a patch in Nougat for this Moto G4 problem or the problem, by good luck (software / hardware interaction and tolerance stackup, etc.), just doesn't occur with Nougat.
I have an XT1644 and now Nougat 7.0 NPJS25.93-14-4.
Thank you for your reply.
You have to update the radio;
As said above, you have to go back to stock and take whatever OTAs and then unlock your bootloader.
I went through this with Total Wireless (Verizon MNVO) and when the radio was updated to latest, everything is working great.
HueyT said:
What is your model? XT1644? What is your software currently (go to "Settings", "About phone", "Build number"
Click to expand...
Click to collapse
ajw85 said:
You have to update the radio;
As said above, you have to go back to stock and take whatever OTAs and then unlock your bootloader.
I went through this with Total Wireless (Verizon MNVO) and when the radio was updated to latest, everything is working great.
Click to expand...
Click to collapse
Some Moto G4 Plus Android 6 phones worked fine with Verizon LTE. I was just one of the unlucky ones. They all seem to receive Verizon LTE with Android 7, however. Sadly, I have found Android 7 to be far less stable than Android 6 (6 was quite good on my phone). Some of the Android 7 feature like split screen work very poorly too. (Split screen doesn't even work all the OEM-installed Android aps, which comprise a very minimal set of aps on a Moto G4.) I wish I could have avoided the update, but LTE is too important to stay on Android 6.
The OTA update worked well with my unlocked bootloader and there was no reason to re-lock it. Of course I had to return everything but /data to an OEM state (unrooted, etc.).
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!
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
Worry not, I have the same problem on an international unlocked G900F.
The problem is inexistent on latest stock firmware, but it is present on the Oreo custom roms i've tried so far, such as lineageOS, CrDroid, Resurrection Remix.
The Only Workaround i've found so far is to enter the info menu on lineage os, dialing *#*#4636#*#* and turning off radio and On, on the Device Information menu, also updating SMSC proved to work on a few ocasions.
Needless to say, I've tried EVERYTHING this forum suggest, such as full wipe from stock recovery and running latest stock for a few days, or even flashing the latest baseband alone, but it doesn't work. I've read some interesting post about this issue on a Xiaomi Oreo device, and i'ts supposed to be an issue of Oreo roms and the way it measures the signal bars, but no fix so far.
Anyway if anyone finds a way to fix this annoying issue on the next Lineage16 I'd be grateful
Having similar issues with G900V on verizon. I've tried many ROMs old and new, latest LOS16 / RR. also I've tried other network fixes as in original post, and different hardware. I have a few of these, all EMMC15 unlocked bootloaders
Are there any developments here?
Weird thing is, SMS/MMS/calling 'works' two blocks away but I always have the 'roaming indicator off' no matter where I am, and there is a delay in sms IF it work at all. Also, this just started last month. (?) I've been using LOS 16 without network issues for a few months prior. It's is possible Verizon has changed something in the service in my area? I went to verizon to verify compatibility and try a new sim, they were mostly useless but otherwise confirmed that the g900v was on the 2020 list of compatible phones. been trying older builds (including starting fresh on the one that was working last month) but nothing but using stock QL1 magisk rooted ROM works - and that one works very well, reliable, and fast. everywhere. grrr, I'm not ready to retire my fleet of s900v, and I would rather retire them than go back to MM if this can't be fixed.