yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] derAndroidler:
But I have the problems after restoring the original CM 14.1 , which works when I made the backup with TWRP.

So I don't understand why backup is not working.
[Samsung Galaxy S 5 Unified Development] mattnin:
I've had problems with 3.0.2.2, that's why I suggested it. Did you backup with 3.0.2.0 first before you restored the the zip that 3.0.2.0 made?
[Samsung Galaxy S 5 Unified Development] haggertk:
Hmm, looks like I need more logging -- one of two values is no good. Recompiling.
[Samsung Galaxy S 5 Unified Development] derAndroidler:
No, I made the backup with 3.0.2-2
[Samsung Galaxy S 5 Unified Development] thaidroid:
It's something with TWRP and CM14, restore does not work for some reason. You always loose developer options and other (but not all)settings on restore. I think it's the same on all models.

It was discussed in the early days you can search on the topic.

My Stock debloated MM restores with no problems at all.
[Samsung Galaxy S 5 Unified Development] actinhic:
True. Even on Note 4 for all CM 14.1 versions...
[Samsung Galaxy S 5 Unified Development] mattnin:
I just recreated the same problems. Could not restore backup. Not even wiping data, caches, system, and reflashing lineage helped. I think it has something to do with permission settings in Lineage. Not even able to restore system apps using

su
mount -o rw,remount /system
[Samsung Galaxy S 5 Unified Development] derAndroidler:
Don't know, what to do now?
[Samsung Galaxy S 5 Unified Development] mattnin:
I got my phone working again by wiping caches, data and system, reflashed cm13 snapshot and Gapps and restoring old TWRP cm13 backup before I came over to lineage.
[Samsung Galaxy S 5 Unified Development] tinroofrusted:
Here is what I did...

Restore the one u want. Do a titanium backup of your data\apps. Wipe everything in TWRP flash clean with lineage. Boot new system then restore with titanium. Hope this helps.
[Samsung Galaxy S 5 Unified Development] prinzkazimir:
Maybe this is important enough to be announced at the first page, because this makes dirtyflashing from cm14.1 loosing sim.

Q12: Can I dirty flash from CM to LineageOS?

A12: Absolutely
[Samsung Galaxy S 5 Unified Development] thaidroid:
You can just Flash again and set it up again after that only dirty flash new builds....(you can also dirty flash an older build over a new one if you want to go back)
[Samsung Galaxy S 5 Unified Development] derAndroidler:
If I restore CM 14.1 and then flash lineage I have the same problems
[Samsung Galaxy S 5 Unified Development] haggertk:
Which cm-14.1 were you on? Reports of no modem/SIM started 25 Dec. If you aren't coming from 25 Dec nightly then it is inconclusive that this is a lineage problem. Especially considering that there is nothing related to radio that changes between CM and lineage.

Of course, not one single person has offered a regular or radio logcat of the problems...
[Samsung Galaxy S 5 Unified Development] derAndroidler:
Perhaps I should go back to CM 13 if backup with 14.1 is not working correctly. I don't know
[Samsung Galaxy S 5 Unified Development] haggertk:
If you don't mind being a guinea pig again:

https://www.androidfilehost.com/?fid=745425885120697958

I don't expect it to solve things, but it should give me some more logs so that I can see what's up.
[Samsung Galaxy S 5 Unified Development] prinzkazimir:
Alas i'm not able to send a logcat for the Moment now, but i will AS soon AS possible.

I made a clean install after a full wipe.
[Samsung Galaxy S 5 Unified Development] mattnin:
I tried clean flashing lineage and that didn't work. I believe it requires clean flashing a stock ROM zip and then flashing lineage for it to boot properly. I am not home so I don't have access to a stock ROM to try it though. Fortunately I still had a cm13 snapshot and backup and that worked.
[Samsung Galaxy S 5 Unified Development] aguarello:
It's not a build problem I think. When I was using Alexdr DevBase you had to manually upgrade your bootloader to the newest one, since the newer builds "needed it" somehow (I don't know the "technical" explanation) . Otherwise you would get things like no signal or "no SIM" showing. He used to put "MANDATORY BL AND CP UPDATE FOR THE NEWEST DEVBASE", or "RECOMMENDED UPDATE, BUT NOT NECESSARY" for other ones.

Happened to me to on the Lineage build. I just went to his thread and got the latest BL and CP files and flashed it like I mentioned a few pages before. Solved the "no SIM" issue and I think it has worked for all the users with this problem.

EDIT: here's his thread

http://xdaforums.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628/

For G900F users you can get BL and CP files from the third post.
[Samsung Galaxy S 5 Unified Development] mattnin:
I wish I was home because I would get you a logcat. Get your VZW S5, back it up in TWRP, then immediately after restore it. You'll lose sim. I believe it's a permissions problem.
[Samsung Galaxy S 5 Unified Development] derAndroidler:
Without backup 14.1 is unusable.
[Samsung Galaxy S 5 Unified Development] Arthedes:
Can't seem to find much info about the S5 modem and bootloader, can you guys explain why I should update it, what it does and where to find the updates?
[Samsung Galaxy S 5 Unified Development] systemcrash:
:good:

http://lmgtfy.com/?q=info+about+the+S5+modem+and+bootloader
[Samsung Galaxy S 5 Unified Development] gerrycooper:
See attached logcat file from test build 2, sim 1 is sill muted.
[Samsung Galaxy S 5 Unified Development] Arthedes:
Yeah but what does it do and why do i need to update it? I wont do that just for the sake of running the latest version if this one is running fine.
[Samsung Galaxy S 5 Unified Development] jdrch:
I safely dirty flashed the Dec 30 LOS build over that exact same CM 14.1 build and it works just fine for me :)
[Samsung Galaxy S 5 Unified Development] derAndroidler:
Can modem and bootloader get damaged so that you have to reflash them or is that not possible ?

Have G900FXXU1CPK3 and modem G900FXXU1CPJ1

(There is G900FXXS1CPLV already but I don't know what XXS1 is)
[Samsung Galaxy S 5 Unified Development] denyo81:
+1
[Samsung Galaxy S 5 Unified Development] jdrch:
Bootloader is what loads the OS when the phone turns on. While I know you have to unlock it to run custom ROMs, I've never heard of updating it thereafter. AFAIK that shouldn't be necessary.

The "modem" typically referred to on XDA is the firmware for the hardware modem in the phone that connects the phone to your provider's network. This firmware is separate from the OS that runs on the phone and is usually what the Baseband entry in About Phone refers to. The latest version is usually found in the XDA support forum for your specific model number, (e.g. Verizon Samsung S5).

---------- Post added at 12:02 ---------- Previous post was at 12:00 ----------

I've never heard of that specifically happening, but it is possible to mess up your GPS NVRAM and have to rebuild it (I had to do this once and to this day I'm not sure how I messed it up in the 1st place) so it could be possible.
[Samsung Galaxy S 5 Unified Development] mattnin:
I believe if you want to update firmware like modem and baseband that the bootloader has to be on the same software revision. For example, if you want PJ2 BASEBAND and modem, you would need the PJ2 bootloader. Am I correct?

Sometimes there are reliability or efficiency differences in new firmwares.
[Samsung Galaxy S 5 Unified Development] ML_Outlaw:
Odd enough but looks like the file manager issue is fixed ....

Wiped internal storage, installed lineageos ... No error on SD card anymore
[Samsung Galaxy S 5 Unified Development] jdrch:
Not for custom ROMs. I haven't updated my S5's bootloader since I unlocked it, & am currently running the PJ2 baseband. AFAIK updating unlocked bootloaders relocks them, which would make the phone unable to boot.

Literally the only time the bootloader is used is at boot, and its only job is to load the OS (and, in the case of locked bootloaders, ensure that only the original OS signed by the OEM is allowed to boot).
[Samsung Galaxy S 5 Unified Development] derAndroidler:
Mm, then I have to install CM 13 again, because backup and restore with 14.1 isn't possible.

Is there no other solution than downgrade to 13.0 ?

---------- Post added at 19:47 ---------- Previous post was at 19:43 ----------

Samsung bootloaders aren't locked. You only need to change recovery.
[Samsung Galaxy S 5 Unified Development] jdrch:
That depends on which model you're using. The Verizon model (SM-G900V) which I have ships with a locked bootloader that took nearly a year to defeat.
[Samsung Galaxy S 5 Unified Development] street_samurai:
I have a g900w8 with the same modem as you and everything is working the same as before (basically perfect) with the 1230 build. The only issue I've seen is the known screen rotation problem.

Massive thanks to the devs for all their time and effort!
[Samsung Galaxy S 5 Unified Development] haggertk:
I'm on business travel right now. I have both my 900F and 900V with me but may not have time to play for a couple days. I'm pretty sure it's selinux and not permissions exactly, based on this commit from another phone that does the symlink thing:

https://review.lineageos.org/#/c/154049/

But my "no logcat" message is directed towards the no sim at all on builds after 24 Dec, not the on-restore case.
[Samsung Galaxy S 5 Unified Development] jdrch:
Wow, that's a monumentally bad bug if you're right. If were you I'd post your issue at the official S5 TWRP thread here before doing anything too drastic
[Samsung Galaxy S 5 Unified Development] street_samurai:
For those having SIM not found or the phone app crashing on startup. Just before Christmas, I decided to update my modem and when I got back into CM/Lineage I had the SIM not found issue. Spent almost an entire day trying to sort this out (mostly waiting for SamMobile downloads).

Here is how I solved the problem:

1. Made a Nandroid backup onto the external SDCard

2. Installed Samsung Kies (not Kies3 which doesn't support the S5). Yes Kies sucks.

3. Attached my phone in download mode and got Kies to update the firmware/modem etc.

4. Installed Odin, download mode on phone and flashed TWRP

5. Rebooted into Recovery

6. Flashed CM/Lineage and Gapps

7. Restored the Data partition from my Nandroid

8. Cleared Dalvik/Cache and rebooted to system

9. Profited

Everything is now running fantastically on my KLTE G900W8, Modem G900W8VLS1DPF3, TWRP 3.0.2.2 and the 1230 Lineage build.

As has been mentioned by others, there seems to be a problem with TWRP not backing up and restoring everything properly. I couldn't figure out exactly what the problem was but the method above got me updated and back to where I was before. Hope this helps some of you out.
[Samsung Galaxy S 5 Unified Development] rayzen6:
I think this backup restore network error was solved by [MENTION=2693412]haggertk[/MENTION] way back in 7.0.0. Is it came back or it needs a new recovery?? Not sure,let's wait for dev himself to clarify :)

Edit:- oh sorry dev didn't seen ur comment above.
[Samsung Galaxy S 5 Unified Development] jdrch:
This would only be the latest of many issues, but folks on the official TWRP support thread seem intent on blaming ROM devs & jcadduono (S5 TWRP maintainer) doesn't respond to anything you send him.

I'm still trying to figure out how to keep TWRP from vaping the data on my adopted SD card. It's a semi-known problem on that thread (read: users report it, devs don't acknowledge it) and the only solution I've been able to find is to never use TWRP with my adopted SD card inserted.
[Samsung Galaxy S 5 Unified Development] haggertk:
I haven't had any problems since flashing a build I made myself. Maybe I'll upload it sometime soon.
[Samsung Galaxy S 5 Unified Development] haggertk:
They're is actually no need to flash a full TW load in order to update all the fw partitions. Maybe I'll upload appropriate tar balls when I get a chance.
[Samsung Galaxy S 5 Unified Development] jdrch:
Yeah this reminds me of the GPS NVRAM issue I had which could be fixed only by flashing back to (rooted) stock TouchWiz.

Kind of a dumb question of curiosity: is the identity of the adopted SD card stored in /system or /data partitions? i.e. if I were to encounter the same problem and apply the same solution, would the data on my adopted SD card still be readable because the OS instance and SD card would still "match," or would I have to reformat the SD card and start over from scratch?

---------- Post added at 13:58 ---------- Previous post was at 13:56 ----------

That would be greatly appreciated.

Slightly off-topic: you don't use the official XDA app? ðŸ¤”

---------- Post added at 13:59 ---------- Previous post was at 13:58 ----------

I thought the same and was looking through his steps trying to figure out an easier way to get that done. You read my mind.
[Samsung Galaxy S 5 Unified Development] haggertk:
Basically you download the full flashable image from somewhere like sammobile, extract all the files, delete the ones you don't want (system, boot, recovery, hidden, aboot if you are vzw), and then tar up the rest.

I have the latest full Samsung images for every variant on my server.
[Samsung Galaxy S 5 Unified Development] derAndroidler:
I still have no recognized SIM card and phone app crashing and default settings.

Don't know, if I should downgrade to CM 13.0 or wait for a solution
[Samsung Galaxy S 5 Unified Development] street_samurai:
For whatever reason, just flashing the SamMobile fw/modem didn't fix the SIM not found issue for me. At first I thought I'd flashed the wrong file but re-downloading and flashing didn't fix the issue.
[Samsung Galaxy S 5 Unified Development] Arthedes:
Bootloaders purpose is very clear now, thank you!

So the modem or baseband is like a driver is for a video card. I don't see what gets updated though with newer versions. What gets improved with an updated baseband?
[Samsung Galaxy S 5 Unified Development] jdrch:
You're welcome! AFAIK Samsung never posts baseband changelogs, but you can kinda figure out what improvements have been made based on the changelog for the corresponding carrier update. I assume they include better connectivity and lower battery life consumption, etc.
[Samsung Galaxy S 5 Unified Development] jiml8:
I am a firm believer in "if it ain't broke, don't fix it."

I am not aware of any exploits against the modem; if there are some I would love to know about them.
[Samsung Galaxy S 5 Unified Development] jdrch:
Which would explain why you're using a custom ROM instead of the OS that came with your phone. Got it :p

It's not about exploits. A phone modem isn't any more exploitable than the Wi-Fi or Ethernet NICs in your PC. Carrier networks are constantly changing & basebands are updated accordingly. Also basebands are occasionally updated to keep pace with the actual phone OS.
[Samsung Galaxy S 5 Unified Development] jiml8:
I would expect the modem to be exploitable; its programming is firmware, not hardware, and it is done in rtos, if I am not mistaken. Nonetheless, I am not aware of any exploits.

And I have exploited USB WIFI adapters, for particular reasons It can be done. :D Needed to modify a sierra wireless device so I could get it to work with a particular FreeBSD product.

Your talk about updating basebands makes sense, but I don't believe that happens quickly or very often. It does suggest a question, though. Do the gsm/LTE variants of this phone all use the same hardware modem? If the answer is yes, that would suggest an interesting project to build modem firmware with global support. I haven't reversed an rtos firmware image in a couple of years. Might be fun. :P
[Samsung Galaxy S 5 Unified Development] jdrch:
Don't think so. US carriers typically restrict the phones they sell to transmitting and receiving over that carrier's frequencies only, as "world phones" that work with all frequencies are an upsell.
[Samsung Galaxy S 5 Unified Development] jiml8:
I am not totally sure what you mean by "identity", but the encryption key is kept in /data/misc/vold if you have adopted it and encrypted it, and I infer from your question that you have encrypted it.

The adoption occurs through a mount bind, and if it isn't encrypted you should be able to read the contents of the sd card on a linux machine if you dismount it from the phone.
[Samsung Galaxy S 5 Unified Development] jdrch:
That answers my question, thanks. Also, all adopted storage is encrypted per Google's specification of the feature.
[Samsung Galaxy S 5 Unified Development] Arthedes:
I'm kind of reluctant to update it, as everything is working now and I'm located in the Netherlands, a fairly small country. I'm scared that updating the modem on my G900F might cause connectivity issues. Then again, it might fix my battery issues.
[Samsung Galaxy S 5 Unified Development] jdrch:
As long as you flash the modem corresponding to your model you'll be OK.
[Samsung Galaxy S 5 Unified Development] Arthedes:
Today in 14 hours the battery dropped 40 percent with 45 minutes or sot with automatic brightness at 25℅. Not sure what is going on. Thre drain should not be that high when I'm only looking at the screen for 45 minutes and going about my day. Im using Naptime and disabled all the draining features like ambient display.

With cm13 i got at least an hour or 1h20m out of 40℅ battery during the day without any optimisation.

Android system and Android OS used the most battery today.
[Samsung Galaxy S 5 Unified Development] derAndroidler:
Absolutely frustrating.

Display is flickering , if brightness is set to minimum.

Often read about people having this problem.

Now after TWRP restore phone is broken.

No sim card detected

Phone app still crashing

Many settings set to default.

Absolutely frustrating day.

Still don't have a solution

---------- Post added at 01:26 ---------- Previous post was at 01:24 ----------

Perhaps I should buy an iPhone. :silly:
[Samsung Galaxy S 5 Unified Development] PorchSong:
Flickering is due to hardware failure on your phone. Nothing you can do. Restore issue is new to 14.1 since 12/25 CM. Still looking for solution. Try restoring without restoring your modern and see if that works. I suspect modem is failing on restore and causing sim not found, phone app, etc issue.
[Samsung Galaxy S 5 Unified Development] haggertk:
Modem is only one of many firmware partitions (aboot, non-hlos, rpm, sbl, sdi, tz, etc). By flashing a full TW rom you ensure that you get the rest of the ones that the people who often package the modem updates often omit.
[Samsung Galaxy S 5 Unified Development] thaidroid:
Well, You are never going to find out if it will solve your issue unless you upgrade. As for modem I have never had a problem upgrading a modem(as long as it's for your phone:D) Samsung to my knowledge has never released a build with a bad modem, it's probably the first thing they test Considering that it's a phone.

TWRP has never worked for me trying to restore any CM14 build. Mind you I stopped trying mid December (Still backing up new builds after I flash them;)not sure why)

---------- Post added at 10:28 AM ---------- Previous post was at 10:10 AM ----------

Agree [MENTION=2693412]haggertk[/MENTION] I always install the latest Release ROM with ODIN to make sure that every bit is upgraded. (the release new builds for a reason)
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Your battery may damage, should change a new original battery from Samsung.

40% can give me 2h of screen on time unlike you only got 1h.
[Samsung Galaxy S 5 Unified Development] GRANTY5050:
Thanks for the great Rom. kltedv running well on my 900I. Clean install with recommended Gapps. As others have mentioned, the stock CM File Explorer failed with the SD card read, but ES File Explorer works fine.
[Samsung Galaxy S 5 Unified Development] haggertk:
I actually never flash the full release ROM. I download them because I want to extract things from the stock ones, but then I build my own ODIN-flashable image that omits the stuff that will overwrite my load (i.e., system, recovery, boot, cache, and aboot on my vzw).

And since SM-G900F (I need to know your EXACT variant in order to make these) are the largest group of people who seem to have this "I don't have radio after 24 Dec" problem, here's precisely what I have flashed on my own SM-G900F. I always use the firmware associated with the BT Unbranded (BTU) releases. If you have the issue, and not the "I restored my backup and now don't have SIM" one (don't even try now if you had it and THEN tried a restore), please try it. If you can successfully use something after 24 Dec then I'd stick with the "if it ain't broke, don't fix it" mindset unless you really feel like a crack flasher.

- Turn off your phone 100%. Do not reboot to bootloader. Turn it off. If you are unsure that you turned it off, pull the battery.

- Boot directly into download mode using VOL-DN+HOME+POWER.

- Flash in the AP/PDA slot of ODIN.

https://www.androidfilehost.com/?fid=745425885120698058
[Samsung Galaxy S 5 Unified Development] derAndroidler:
So flashing new modem and bootloader is not enough to update a phone ?
[Samsung Galaxy S 5 Unified Development] dollardollar:
So, [MENTION=2693412]haggertk[/MENTION], Few clarificatins.

I have SM-G900S variant and extracting only these from Samsung firmware files, creating tar file and flashing it in download mode will update my modem and the current LineageOS is uneffected.

or do i have to flash the LineageOS top of it.
[Samsung Galaxy S 5 Unified Development] haggertk:
If you repack the tar.md5 correctly then it will not overwrite your currently-installed LineageOS/CM.
[Samsung Galaxy S 5 Unified Development] grey1213:
I'm still on 24/12/16. Looks like there are some problems after that? Either way I'll stick to this until there is official LineageOS and check if there's any issues then.
[Samsung Galaxy S 5 Unified Development] thaidroid:
[MENTION=2693412]haggertk[/MENTION], You do that because you can:o, but most of us mere mortals cannot build our own ROMs. Yes I do flash modems and BL using ODIN but I still think it's a good thing to ODIN any new build from Samsung to make sure all the other drivers and bit's are the latest before I go on flashing XDA Roms again.

I guess you included the file and instructions for those who have a sim problem. No such thing here.
[Samsung Galaxy S 5 Unified Development] d00m178:
LockClock widget doesn't work on latest LA 14. I even can't find it in Applications menu.
[Samsung Galaxy S 5 Unified Development] haggertk:
So you restored a backup and your radio doesn't work? I have a good handle on what is going on -- somehow things are attempting to get remigrated with crap SELinux file contexts. For now, after restoring and before rebooting into the ROM, delete these two directories within TWRP (the file manager works fine):

/data/data/com.android.providers.telephony/databases/

/data/data/com.android.providers.telephony/shared_prefs/

This WILL NOT delete any of your telephony data. This is all related to the symlinking we are forced to do because our RIL blobs are hardcoded with the old paths and we cannot hexedit them to the new ones -- the new paths are longer than the old. These two directories hold the symlinks.

Still working on something that will help when you restore *future* backups. Restoring any backups of ROMS that are older than the perm fix will require always require this kind of workaround. Maybe I can create a flashable, that's secondary right now. I will go ahead and add a note in the first post.
[Samsung Galaxy S 5 Unified Development] haggertk:
That is certainly a sure-fire way of making sure you have all of the partitions updated!

I take shortcuts because I don't like to spend the time flashing the full TW image and then restoring or clean flashing LineageOS/CM.
[Samsung Galaxy S 5 Unified Development] rayzen6:
Will this workaround will also work if someone's device not able to get sim/network after clean flash?? I'm not facing any issue like this but many are having all across different ROMs which are based on these device trees.