Database Users

Help with network signal loss

2 S4. Both running the same rom. Both running the same kernel. Both have the latest firmware (according to sammobile). They are both International versions.
The only difference is: One was bought from Germany and one from Romania. The German S4 belongs to a friend. The other one is mine.
The problem started this morning-noon. Last night, around 8 PM, I flashed the latest GPE build by Danvdh, with the latest Googy-Max kernel on both devices.
They both worked fine since first boot. But the German S4 started acting up today. It randomly lost network signal.
My S4 works fine. Haven't lost signal or anything.
I can't explain why this happens. Or why it didn't happen until today, around noon.
Someone in the rom thread suggested it might be a firmware/modem issue.
Well.. Firstly: It worked fine with previous builds.
Secondly: Why would it work during the night but in the morning it fails?
Thirdly: It already has the latest firmware..
I thought about a re-flashing the rom. But not until I hear some more opinions

T-Mobile Updating Baseband/Modem?

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.

Turbo 2 XT1585 - Stock flash-Phone has a newer version than the 7.0 img on the forum?

Hi all,
Trying to solve some terrible freezing/lag on my Verizon XT1585 Turbo 2 (sometimes upwards of 30 seconds delay between keypresses). Wiping cache and factory reset has no effect. It happened after the OTA 7.0 update so I wanted to try and flash the full 7.0 image and start fresh.
However I noticed that the firmware available here on the site may be slightly older than what I have on my phone, and I'm worried about bricking by trying to flash what is technically an older version.
The build number of the firmware here on the site lists itself as: NCK25.118-10, but my phone shows it's build number as NCK25.118-10.2. This appears to be two OTA updates behind, from February. Newest one is from August.
Am I being overly paranoid about minor OTA updates, or would I have issues if I were to try and flash?
Thanks!
EDIT: With some googling I have found the newest NCK25.118-10.2 firmware was uploaded just yesterday by Motorola-Firmware-Team on AndroidFileHost (I can't post the link because I'm still too new)
Would it make sense to update the firmware download thread with this new firmware? And would I have been boned if I flashed the older file?

you can only flash NCK25.118-10.2 , the one you mentioned in your post, this is because your device is on the latest buildNCK25.118-10.2 and currently, flashing older builds or downgrading is not possible.
also reflashing NCK25.118-10.2 build will not fix random reboots as i am experiencing it first hand.

ferolac said:
you can only flash NCK25.118-10.2, the one you mentioned in your post, this is because your device is on the latest buildNCK25.118-10.2 and currently, flashing older builds or downgrading is not possible.
Click to expand...
Click to collapse
That's what I thought, glad the most recent firmware just came out. Thanks very much! I'm worried that my problem is a hardware issue as well, it seems to freeze whenever it's accessing files (reading image thumbnails, cached data etc. Maybe memory going bad or bad solder connections). I thought it couldn't hurt to flash fresh as long as I had the correct file.
How would we go about getting the firmware thread updated with the new file?

Darkhand said:
That's what I thought, glad the new firmware just came out. Thanks very much! I'm worried that my problem is a hardware issue as well, it seems to freeze whenever it's accessing files (reading image thumbnails, cached data etc). Maybe memory going bad etc. Thought it couldn't hurt to flash fresh as long as I had the correct file.
How would we go about getting the firmware thread updated with the new file?
Click to expand...
Click to collapse
this build was already available here, long before it was uploaded to android filehost. As for how to update the firmware thread here . . . informing the mods i guess

Android 8 Oreo Update

Deleted

Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?

that was the Sprint answer

SprintBama said:
Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?
Click to expand...
Click to collapse
If anything, they would change it to v7. Maybe they are waiting for a merger, which could happen next week

I checked for update today and got 1627.64mb g930pvpu6cre7 Samsung experience 9.0 with oreo.

I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.

Just received oreo on my s7 for boost. So far I'm not impressed. I was really hoping for Dolby on this but guess not. The build number is SMG930PVPU6CRE7

kalala said:
I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.
Click to expand...
Click to collapse
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.

i manfully updated @ 4:15. they sent it @ 1627.64 mb. still downloading. when I got my att update I tried all the batch root methods for my 935a. saving magisk for last bc I didn't have the boot.img for the cre4 update.
I I only had the "att beta" update from March. long story short it won't boot with the nougat eng.boot. I gave it an hour. I cleared the cache, factory reset, tried to add flash all of the earlier img files I had for oreo, nothing worked. had to flash it back to nougat bra1. I immediately requested the update again. they approved. the next day I attempted to flash magisk 16.4. w/ the modified odin 3.1.3 version. it wouldn't flash. with the cre4 boot.tar in hand, I tried every method on gods green earth to gain some sort of r/w access. it was late, I was tired, I flashed the eng boot. once again it was stuck at the Samsung boot logo. it wouldn't allow me into recovery to push the cre4 update zip. once again I'm back to bra1 nougat. I booted into recovery & updated it from the sd card. when it booted I noticed it wasn't anywhere as clean & polished as the ota I had twice. I've flashed back to brd1 ten times, & requested the ota. after smart switch, I used all the avail windows software I could acquire & kept trying, they won't send it. but they did provide me with a new picture for my samsung account. I'll post it later. gotta check out this 930p oreo.

razor001_ said:
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.
Click to expand...
Click to collapse
I don't think Heimdall works on High Sierra or even Sierra anymore.

I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?

schmism said:
I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?
Click to expand...
Click to collapse
almost zero... asuming that Oreo for "U" Variants step up with BL on this month maybe next one, is something pausible but stepping up two versions in any short time is questionable... but who knows. The best you can do is wait this or the next month for BL update on U variants.

To be clear I'm still on version 5. I will continue to put off the upgrade to 6.

Installing Previous Stock ROM Fails

Hello guys,
I recently updated my NoteFE firmware to KSA August update but it felt like it's gotten worse so i tried to go back to July update.
When i try with odin 3.13 it fails directly.
When i try with older versions it stucks at NAN Write....
Any ideas on what causes this issue ?
Thank you.

agokgoz said:
Hello guys,
I recently updated my NoteFE firmware to KSA August update but it felt like it's gotten worse so i tried to go back to July update.
When i try with odin 3.13 it fails directly.
When i try with older versions it stucks at NAN Write....
Any ideas on what causes this issue ?
Thank you.
Click to expand...
Click to collapse
You cant flash back if the bootloader version was updated. Samsung implemented this BS sometime ago.
I would like to flash back also, the oct update borked my LTE, full signal but super slow speeds. But im stuck on the current version
sent from my S9 Plus (Exynos) Pixel 2XL or Note FE