Basically since rooting my LS-997 w/Dec 1 patch, bluetooth wont show any devices & wont connect (I'll live lol)
Ive had a few other people say they've had the same issue but ONLY those that rooted on Dec patch.
Can anyone shed some light on this?
I was Dec patched on my 995, rooted with Dirty Santa, and had no issues there, went to modded 5.6, still good, and now on the 996 unlocked rom and it's still good. I don't know if it was kernel related at all, but I was December'd and never had a problem.
Related
I have an S5 from T-Mobile, it is several months old. It is currently using Cyanogenmod 12.1 Nightly from July 4.
I updated to the October 21 Nightly a few days ago, and started seeing an issue, where the mobile signal cuts out after a while (usually after I wake up the phone after a long time of inactivity, such as sleeping). I will see a mobile signal, but there is an exclamation point next to it. LTE data won't work. MMS won't work. I don't know if SMS or Phone Calls will work, but I suspect not.
I asked on Reddit, and someone suggested that my phone might need a Bootloader / Radio update? Someone made the following suggestion:
"Many Samsung devices require a bootloader/radio update to run the latest CyanogenMod versions. You need to make sure it is both the bootloader and radio, becasue many update packages will do one or the other. You can find the flashable zips on the xda forums. "
In the mean time, I have downgraded back to an old July 4 Nightly, but it looks like the problem is now persisting. So, finding a solution is now more urgent.
Does anyone know how to update the Bootloader / Radio for my T-Mobile S5? Directions / Links would be helpful... :-s Kinda newb at this.
Or, if you could recommend a ROM that you prefer over CM, that would be welcome info as well. I do like CM, but you know what they say, the grass is always greener. Plus, I think everyone here likes to tinker.
Device Model: SM-G900T
CM Version: 12.1-20150704-NIGHTLY-klte
Android Version: 5.1.1
Baseband Versioin: G900TUVU1DOB1
It's been a while since I last did this, and I'm afraid I'm quite confused...
I am running a custom ROM (Bliss Beta 6) but remembered that updating my ROM doesn't update my baseband/modem.
Are baseband and modem the same thing?
https://support.t-mobile.com/docs/DOC-10398
Using this site here I see that my current baseband (G900TUVU1CNK2) is super outdated. It tells me that G900T3UVU1FOG6 or G900TUVS1FOL1 are the latest, but I don't get why there are two. Which one should I install?
All that being said, can I install using TWRP and a zip, or do I need to ODIN it?
Any help would be appreciated, as I said I've done this before but can't find any updated tutorials that explain the questions I'm asking (I've tried searching google and XDA, if I missed something obvious I would appreciate a link!).
cheers
More research has helped me answer my own question! Sharing what I've found in case anyone else comes across this thread:
Baseband and Modem are effectively the same thing in this context.
G900T3UVU1FOG6 was released in August 2015 and has the fix for stage-fright.
G900TUVS1FOJ4 was released in November 2015
G900TUVS1FOL1 is pretty much brand new (released in December 2015) so there's not a lot on it. This is the one I'm going to try installing.
Followed the instructions from this thread http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400 to figure it out.
More use information found here:
https://ohthehugemanatee.org/blog/2...m-slash-baseband-firmware-on-a-samsung-phone/
lioncat55 said:
More research has helped me answer my own question! Sharing what I've found in case anyone else comes across this thread:
Baseband and Modem are effectively the same thing in this context.
G900T3UVU1FOG6 was released in August 2015 and has the fix for stage-fright.
G900TUVS1FOJ4 was released in November 2015
G900TUVS1FOL1 is pretty much brand new (released in December 2015) so there's not a lot on it. This is the one I'm going to try installing.
Followed the instructions from this thread http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400 to figure it out.
More use information found here:
https://ohthehugemanatee.org/blog/2...m-slash-baseband-firmware-on-a-samsung-phone/
Click to expand...
Click to collapse
i've been wondering this myself, so did you update your baseband & is there any change in battery or signal quality? (or i guess stagefright detector?)
also wondering if downgrading is no problem or if it affects anything like that (which stock samsung or other device kernels/ROMs do, sometimes blocking root etc)
Hey, so I actually updated to G900TUVS1FOL1 using ODIN. It nuked everything and installed regular TouchWiz which I wasn't a fan of, but I have no problem installing my own ROM later.
If you're doing the T-Mobile one, then there is no issue with rooting, installing kernels, custom ROMs, etc. I don't really know about "downgrading" the baseband or modem, but I don't think you would need to in this case.
Note that if you have Verizon or At&T you probably want to be SUPER careful, because they lock down everything.
lioncat55 said:
Hey, so I actually updated to G900TUVS1FOL1 using ODIN. It nuked everything and installed regular TouchWiz which I wasn't a fan of, but I have no problem installing my own ROM later.
If you're doing the T-Mobile one, then there is no issue with rooting, installing kernels, custom ROMs, etc. I don't really know about "downgrading" the baseband or modem, but I don't think you would need to in this case.
Note that if you have Verizon or At&T you probably want to be SUPER careful, because they lock down everything.
Click to expand...
Click to collapse
it's a g900t yes
i am going to look into upgrading it more directly rather than the complete samsung image... maybe... so you're confirming the official tmobile samsung 5.1.1 complete installation still lets you flash TWRP then cyanogen without a problem? i came from november 2014 samsung 4.4 to CM originally
kn00tcn said:
it's a g900t yes
i am going to look into upgrading it more directly rather than the complete samsung image... maybe... so you're confirming the official tmobile samsung 5.1.1 complete installation still lets you flash TWRP then cyanogen without a problem? i came from november 2014 samsung 4.4 to CM originally
Click to expand...
Click to collapse
yes, I installed G900TUVS1FOL1 with Odin, had root and TWRP installed just fine (couldn't get xposed to work because it was not a deoxdex rom of course). I just installed BlissPop ROM last night which is based on CM13. So yes, it didn't lock me down or anything.
Hi,
My newly bought S7 edge is having problems. I noticed that after some time, it is not possible to make any calls or use data even though the range is shown as full in the status bar.
After thorough trial and error, found that the issue is coming only if 4G/LTE is enabled. Otherwise, if i switch to 3G, it works. This is the issue for both the sim slots :crying:
Anyone else who has had this issue . I'm running the latest October patch of Android 6.0.1. Is this a software bug or a hardware issue. Any help or suggestions would be much appreciated
U can try reflashing an old firmware to discard that the update caused the problem.
alehawk said:
U can try reflashing an old firmware to discard that the update caused the problem.
Click to expand...
Click to collapse
The problem is since, it is a new phone, I don't know whether it is the update which causes the problem. I upgraded the software immediately after receiving the phone. Is anyone with the latest october update having the same issue?
I checked online, and it seems like some people have had similar issues in past. Just not sure whether it is a software issue or a hardware. And I honestly dread doing the set up again, as unlike past times (i always root my phone, but because of knox tripping, haven't rooted yet), when titanium backup was there, this would mean lots of time on re-setup
MMMmmm I only had that problem on a phone that wasnt 4g capable but had that option enabled but was because I flashed a firm that wasnt supposed to use.
If its new you can go to warranty and exchange for a new one but my curiosity will remail if it was about the october patch...
I have the same issue... it might just be a bug that will be resolved in the next update
amritpal2489 said:
I have the same issue... it might just be a bug that will be resolved in the next update
Click to expand...
Click to collapse
Oh, that's a relief. So, this issue came after updating the software. Before that, it was working for you?
Hrithan2020 said:
Oh, that's a relief. So, this issue came after updating the software. Before that, it was working for you?
Click to expand...
Click to collapse
Yes
amritpal2489 said:
Yes
Click to expand...
Click to collapse
I was finally able to get the 4G mode also working. Not exactly sure what did the trick.
Here's what I did:
1. Flashed an older version (Aug version) which I found on samfirwmare -> Didn't work
2. Flashed an even older version (July version) -> Didn't work
and then updated the software -> started working
The funny thing is the software is the same as before (the same version as was earlier - October build)
Mods, please close the thread
Hrithan2020 said:
I was finally able to get the 4G mode also working. Not exactly sure what did the trick.
Here's what I did:
1. Flashed an older version (Aug version) which I found on samfirwmare -> Didn't work
2. Flashed an even older version (July version) -> Didn't work
and then updated the software -> started working
The funny thing is the software is the same as before (the same version as was earlier - October build)
Mods, please close the thread
Click to expand...
Click to collapse
Great to see your issue is resolved
I have read so many threads about Nougat that I have gotten myself a bit confused, I think.
I am running an XT1644 in the US on the Verizon network. My device has an unlocked bootlader and is running stock software, albeit rooted (i like adaway), build number MNPJ24.139-48.
I am quite interested in trying out some of the Nougat-based ROMS, and each of them suggest flashing the soak test first. As I read the threads for the soak test, they seem to suggest that they are all for India or variants other than mine.
At the risk of making myself out to be an idiot, I'd like some clarification/confirmation as to how I can get the correct soak test for my variant. I have no issue with following directions, however, the sheer amount of directions and variations for this model just make me want to be extra cautious before flashing.
Thanks
Don't do it. The soak test was not for our models and it can have issues like missing IEMI or WiFi. Verizon being CDMA as opposed to GSM, you can get in even worse problems.
Ah, and once you flash the N bootloader, you can't go back to the MM one. Reverting to MM will be incomplete and with possible issues. Some people report success, some lost their radio.
You have the stock firmware, there are also available .49 and .64 versions. I have rooted too my G4 Plus and didn't receive the OTA updates anymore.
SoNic67 said:
Don't do it. The soak test was not for our models and it can have issues like missing IEMI or WiFi. Verizon being CDMA as opposed to GSM, you can get in even worse problems.
Ah, and once you flash the N bootloader, you can't go back to the MM one. Reverting to MM will be incomplete and with possible issues. Some people report success, some lost their radio.
You have the stock firmware, there are also available .49 and .64 versions. I have rooted too my G4 Plus and didn't receive the OTA updates anymore.
Click to expand...
Click to collapse
Thank you. This is what I was thinking, but the "tinkering" side of me was itching and I needed the voice of reason to help solidify the decision to wait
The .64 update for the MM works fine on my phone, but I am on ATT network (GSM) so... Idk for Verizon.
myk.robinson said:
Thank you. This is what I was thinking, but the "tinkering" side of me was itching and I needed the voice of reason to help solidify the decision to wait
Click to expand...
Click to collapse
I have the XT1644 on T-Mobile and I'm using a 7.1 ROM. But I never updated my bootloader from MM I just flashed CM 14 and everything still works. The only minor issue I've come across is that it will only allow me to set 1 fingerprint. However, it says every fingerprint fails but I'm still able to use them to unlock the device. So it's apparently just a weird bug. My advice, make a good backup and try either beanstalk 7.1, Xperience 7.1 {my current ROM} Or really any of the others. I've flashed all of them and haven't had any issues. And now there's dual boot so you can always keep one MM ROM and one N ROM on your phone.
---------- Post added at 02:32 AM ---------- Previous post was at 02:30 AM ----------
I have the XT1644 on T-Mobile and I'm using a 7.1 ROM. But I never updated my bootloader from MM I just flashed CM 14 and everything still works. The only minor issue I've come across is that it will only allow me to set 1 fingerprint. However, it says every fingerprint fails but I'm still able to use them to unlock the device. So it's apparently just a weird bug. My advice, make a good backup and try either beanstalk 7.1, Xperience 7.1 {my current ROM} Or really any of the others. I've flashed all of them and haven't had any issues. And now there's dual boot so you can always keep one MM ROM and one N ROM on your phone.
So I just bought an LG V20 US996 (not US Cellular version). I have TWRP installed, and then I installed LineageOS nightly 20170825 and found that the battery meter is stuck at 50% regardless of charge, but more importantly, the touch screen no longer works. Same thing with nightly 20170901. However, after downloading all the nightlies and trying them, I found that the July ones work just fine (ie 20170728, 20170714, and 20170707). Someone on reddit suggested it might be an issue of not having the latest firmware. I did find here at lg-firmwares.com/lg-us996-firmwares that lists the US996 kdz files. It looks like the US Cellular version is more updated than the regular USA version. Is it safe to flash a US Cellular version onto a not US Celllular version even though they're both US996 ?
There are several things to take into account.
First, is you boot loader unlocked using the unlock.bin, or are you using the engineering aboot?
Nevermind. Someone already posted a regression ticket for this. It should be fixed eventually. The person who did it flashed a different kernel and it worked. It appears it might be an issue with the stock kernel.
* UPDATE * I just flashed 20170908 and then flashed the 20170728 kernel and it works. So it must be the more recent stock kernels that are the issue.