yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] frone0:
Thanks for the info!

I'm not sure how to answer your first question. The stock firmware I downloaded was from this link at updato.com:

Samsung firmware download - find All Official Android & Samsung Updates | updato.com

Are you looking for the official Samsung software to download? At updato.com, you'll find the latest Android device updates. Check on your own!

updato.com

The download extracted to this file, which I used to flash it to stock:

ALL_VZW_G900VVRU2DQL1_G900VVZW2DQL1_CL8025411_QB16020535_REV00_user_low_ship_MULTI_CERT.tar.md5

That file was about 4.2GB in size.

I also do not think that I flashed it twice with this firmware yet. I have flashed it with a few different ones in trying to revert to stock though.

I'll leave my EFS partition alone for now if you think I should.

Thanks again!
[Samsung Galaxy S 5 Unified Development] bmwdroid:
So it was a one part file and then there's no chance for choosing different CSC files.

If it was mine I'd do:

Download multiple part stock using GitHub - ivanmeler/SamFirm_Reborn.

Fill in device name and region (look them up here: https://samfrew.com/)

Check "binary nature" and "decryption".

Results in one zip file containing at least AP, BL, CSC, CP.

Unzip it and flash them with Odin.

Regarding EFS you don't tell if IMEI is present.
[Samsung Galaxy S 5 Unified Development] frone0:
It took some doing, but I was able to download both .ZIP files. I have Odin ready to go and have used it in the past by populating the AP with a file and then flashing, but I'm not sure what I need to do with these two .ZIP files.

Please let me know what to put where in Odin for the test flash.

How can I check if IMEI is present so I can report back?

Thanks for all of the help!
[Samsung Galaxy S 5 Unified Development] kurtn:
There should be tar files in those zip archives
[Samsung Galaxy S 5 Unified Development] frone0:
There is a .tar.md5 in the second link you provided, but the first appears to be only source code from GitHub. Should I populate the AP in Odin with the .tar.md5 from the first link? What should I do with the source code from GitHub to move forward?

Thanks again for all the help!
[Samsung Galaxy S 5 Unified Development] bmwdroid:
These files you get when unzipping the downloaded latest stock ROM file for G900F for DBT.
[Samsung Galaxy S 5 Unified Development] bmwdroid:
That's where you put your files.

Name matches its box.
[Samsung Galaxy S 5 Unified Development] bmwdroid:
@frone0 I probably mislead you by writing "unzip them" instead of "unzip it and flash them".
[Samsung Galaxy S 5 Unified Development] bmwdroid:
Should be shown in the info about your device.
[Samsung Galaxy S 5 Unified Development] frone0:
I was able to check for my IMEI and it showed that both IMEI and MEID are populated with what looks like very similar numbers - just a couple off of each other.

I think I'm screwing up with the SanFirm Reborn-master GitHub portion. I downloaded the files, but do not know what to do with them. The .tar.md5 I pulled down from the samfrew.com site was done by searching the site for my phone model number. I figure there might be something I need to be doing with the GitHub files to do this properly and be able to unzip and find the AP, BL, CSC, and CP files. I would be able to use Odin to flash, but I cannot find these files.

Should I be compiling the source code that I downloaded from GitHub for the Sanfirm Reborn-master portion?

Sorry I am taking so long to figure this out. I really appreciate the help!
[Samsung Galaxy S 5 Unified Development] bmwdroid:
You probably see the site like attached pic.

Click on the right hand side where is says "Releases" on green "Latest" do get the zipped files.

Unpack and start the .exe
[Samsung Galaxy S 5 Unified Development] frone0:
***Edited - see below***

Ahhh - that got me a step closer!

I am now running the utility and attempting to download the ZIP file. Ran into another issue. I checked the samfrew.com site to gather my phone model and region of "SM-G900V" and "VZW - United States". I entered the model and tried both 'VZW' and 'VZW - UNITED STATES' but these two attempts returned the following:

Could not fetch info for SM-G900V/VZW. Please verify the input or use manual info

Could not fetch info for SM-G900V/VZW - UNITED STATES. Please verify the input or use manual info

Any ideas on what I might be doing wrong here? I did check on 'Binary nature' and 'Decrypt automatically'. I get the error when clicking 'Check Update'

Thanks again!

*Edit1

I located the PDA and CSC numbers by opening the samfrew page for the latest update. I chose 'manual' info and copy/pasted the PDA and CSC numbers. I put in 'SM-G900V' for the 'Phone' field (and tried a few other iterations). Here's what I got when hitting 'Check Update':

Checking firmware for SM-G900V/VZW/G900VVRU2DQL1/G900VVZW2DQL1/SM-G900V/G900VVRU2DQL1

Error: Could not send BinaryInform. Status code 200/400

Request was invalid. Are you sure the input data is correct?

Getting closer maybe?

**Edit2

I had tried 'G900VVRU2DQL1' for the 'Phone' section in the download utility, and it failed. I just retried and found that I had a trailing space after the entry. Removed the space and am now downloading.

Thanks again!

***Edit3

When the download completed, I unzipped the file "SM-G900V_1_20171219155127_sptischw1b_fac.zip" which gave me a folder with this file only in it "ALL_VZW_G900VVRU2DQL1_G900VVZW2DQL1_CL8025411_QB16020535_REV00_user_low_ship_MULTI_CERT.tar". I uncompressed this file to find files such as system.img.ext4, userdata.img.ext4, cache.img.ext4, modem.bin, etc. I must be downloading it wrong to not get it split into AP, BL, CSC, and CP files.

Any ideas? thanks!
[Samsung Galaxy S 5 Unified Development] bmwdroid:
There is of course the possibility that for branded phones the stock ROM file is different to the free one.

But perhaps you can still use these separate files to flash with Heimdall. I'm not familiar with this just knowing that it needs a lot more separate files than Odin.

I think there's a how-to in English for that but idk where and mine is only in German and for Linux.
[Samsung Galaxy S 5 Unified Development] frone0:
My daily driver is a Linux box. I'd be glad to give it a run. I'm just wondering if I am doing something wrong to get the .ZIP instead of the Odin files.
[Samsung Galaxy S 5 Unified Development] frone0:
As long as I have not bricked this phone, should there be a path to getting it back to Stock ROM completely? Is there another part of the phone software that you think I might need to flash to remove any trace of the LineageOS software?

Thanks!
[Samsung Galaxy S 5 Unified Development] bmwdroid:
This is the German how-to site.

For my N910F for instance I get a .zip file containing several files for Odin, but as I wrote...

Hope you didn't forget to check the 'binary nature' box in SamFirm_Reborn_0.3.6.3 when starting the download.

If you didn't forget it there seems to be only that one file existing for your model.
[Samsung Galaxy S 5 Unified Development] bmwdroid:
Even when flashing only one part stock file afaik no traces will be left except the triggered Knox counter.
[Samsung Galaxy S 5 Unified Development] frone0:
I just tried downloading the file again - thought I could have easily forgot to choose 'binary'. I made sure to verify that I chose 'Binary nature' this time, but looks like it downloaded the same file. I extracted the .ZIP, which contained a single .TAR.MD5 file. This TAR then extracted into 15 files. I've attached a screen shot of the files which were extracted.

Is there another route to get the files needed for Odin?
[Samsung Galaxy S 5 Unified Development] frone0:
So flashing it with LineageOs and then back to stock, wouldn't require a modem re-flash or anything? I've seen people mention the EFS partition, but don't know if upgrading to LineageOS affects that at all.

Thanks again!
[Samsung Galaxy S 5 Unified Development] bmwdroid:
Not necessary at all.

EFS partition contains the devices IMEI.

Only if it's lost you have to touch this partition.
[Samsung Galaxy S 5 Unified Development] bmwdroid:
So there's only a one-part stock file for G900V but you can flash these extracted files seperatly using Heimdall.

Probably not as it's a Verizon branded phone.

Don't know what will happen if you try another firmware, but, as I saw in your pic, your device seems to have a special Verizon pit file so it is possible, that these phones get partitioned differently to the non branded ones.

Just had a look for my G900F open EU pit file but can't examine it further.

Btw. on one of my devices I once had to flash the firmware at least twice to be successful.

Perhaps you try that as well.

Shouldn't do any (more) harm than flashing once.
[Samsung Galaxy S 5 Unified Development] bmwdroid:
@frone0 I've downloaded your file, extracted the pit and opened it in Pitmagic.

Same with the pit for EUR-open.

The results are attached as txt files, but comparison has to be done by you as I'm to lazy right now.
[Samsung Galaxy S 5 Unified Development] frone0:
Wow - thanks for this!

I ran an FC command on these two to find some differences in the "Block Size" and "Block Count" fields. Also looks like a difference in both the 'Partition Name' and the 'Flash FileName'. I've attached the FC output in a text file here.

This is getting a bit over my head, but I'm assuming that them being different means that I cannot use the second option you were thinking of.

Please let me know if you can think of any other options.

Thanks again!!
[Samsung Galaxy S 5 Unified Development] frone0:
I'm glad to try flashing it again to clear things up. Which method should I use for this?

Thanks!
[Samsung Galaxy S 5 Unified Development] frone0:
I guess I'm not sure if the upgrade to LineageOS or attempts to get it back to stock would have affected the IMEI.
[Samsung Galaxy S 5 Unified Development] bmwdroid:
To me it's obvious that some partition sizes differ.

Afaik the partitions are not hard-coded but am not sure .

On a S2 I9100 I once changed partition sizes to be able to flash a bigger custom ROM so there they weren't hard-coded.

It may be possible to flash another firmware with changing pit but idk.
[Samsung Galaxy S 5 Unified Development] bmwdroid:
This time I would try Heimdall with all the files necessary you extracted.
[Samsung Galaxy S 5 Unified Development] frone0:
It took some doing, but I was finally able to flash with Heimdall and have the phone boot up. After successfully flashing the phone, I went through the initial setup, connecting to wifi, Google account, etc. Everything seemed to work great until I turned off the WiFi. The mobile data (Internet browsing, etc.) again failed with wifi off, but I was able to successfully send and receive MMS messages. Voice phone calls work fine as well.

There were some files that were listed when I ran the print.pit on the phone that were not included in the files that were extracted, so I obviously did not flash them. Not sure if there is a better 'source' for a complete firmware release with more files? Any ideas of what I might be doing wrong here?

Just an FYI, I used the following post to help with flashing under Heimdall:

https://xdaforums.com/t/sm-g900f-st...stock-rom-under-linux-using-heimdall.4354577/

Thanks again for the help!
[Samsung Galaxy S 5 Unified Development] bmwdroid:
Glad I could help a bit.

Can you name the partitions you had no files for?

As imho all stock ROM files should contain all necessary parts I strongly doubt that there are versions which include more than you got.

Of course you can have a look at samfrew.com, youmobile.org, sammobile.com and maybe more.

I once had the necessity to flash the same stock at least twice to be successful.

Perhaps it helps here as well.
[Samsung Galaxy S 5 Unified Development] frone0:
Sorry about the slow reply - had to step away for a bit.

I've attached two files. The 'print-pit-partitions.txt' is the list of partitions on the phone when I run the print-pit command included. The other text file is a list of the stock files that I get when extracting the stock ROM download. Just guessing by what I am seeing, it looks like there are a few partitions without flash files on the phone and there are partitions with flash files that are not included in the stock ROM download. I don't know if these are unimportant or not, just trying to help with the info here.

I am not 100% sure that I have flashed the same stock twice before testing or reflashing. When you did not do this and it failed, was it that it would not boot up, or that something like the mobile data only failed? Mine seems to boot up fine every time after flashing a new stock rom, with only the mobile data failing.

Sure hope this helps - thanks for all of your help in it!
[Samsung Galaxy S 5 Unified Development] bmwdroid:
No sure either, but some may be permanently on the device without being altered when flashing stock or are filled with data when system starts the first time after flashing.

I never cared much about stock ROMs containing more or less files than the device had partitions named.

As I wrote I usually flash with Odin which always worked anyhow.

It didn't boot up at all then.

To make comparison easier I've put your files in one xlsx table (extension to change)
[Samsung Galaxy S 5 Unified Development] kurtn:
Do you have a tl:dr ?
[Samsung Galaxy S 5 Unified Development] frone0:
Thanks again for all of the help with this. I was able to think about it over break and think I might see if I can view/export the files on the unmodded G900V that I am using as my current/backup phone. It still works fine and I figure I might be able to find what is missing.

In the meantime, I'm going to try and run through the super-detailed 'flash to stock' write up that LouLuo just posted above this. The updated modem sections are of interest to me. I'm hoping this might fix the persistent mobile data issues.

I'll report back with my results. Thanks again to bmwdroid and LouLuo!
[Samsung Galaxy S 5 Unified Development] frone0:
First off - Thank you for this great write up with detailed steps!

I ran through this a few times with these steps (trying to stay concise):

- Performed the 'clean' steps by wiping the system and cache in the Android Recovery. (no TWRP yet here)

- Used Odin to flash 4.2GB file:

ALL_VZW_G900VVRU2DQL1_G900VVZW2DQL1_CL8025411_QB16020535_REV00_user_low_ship_MULTI_CERT.tar.md5

- Odin flash passed successfully. Bootup, initial Samsung config (bypassing most). Connected to Wifi.

- Inserted SIMM and booted backup to find a text to come through at first and then fail again.

- Mobile data and voice calls both failed.

- Rebooted several times with no change.

- Swapped SIMM back to unmodded g900v, which worked fine.

- Waited 12 hours and swapped the SIMM back to the test phone.

- Booted several times with the same voice and mobile data failures.

At this point, I realized that I probably needed TWRP installed and such. Followed these steps:

- Stepped through another post to use RootTools package to setup TWRP and re-root the phone.

- After the steps completed successfully this was the reported status of the phone from the post:

"When finally booted you will have an unlocked bootloader with TWRP recovery running a Deodexed Rooted QL1 stock MM 6.0 Rom Rooted with Magisk."

- Powered off the phone and installed the SIMM card.

- Booted up and completed the Samsung setup with SIMM card installed.

- Found everything to work, including MMS without WiFi - except mobile data/browsing.

- Rebooted to find voice calls to fail along with mobile data.

- Used TWRP to format data and wipe directed cache, data, Dalvik.

- Used Odin to flash 2.848GB file:

G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5

- Completed the setup again.

- Found both voice calls and mobile data to fail through several reboots.

- Moved SIMM card to third test phone (also failing after upgrade) running latest LineageOS.

- Voice calls and mobile failed.

- Moved the SIMM card back to unmodded g900v and tested all successfully.

Quick problem rundown here:

- I had a g900v running LineageOS 18.1 smoothly.

- OTA update caused mobile data to fail.

- Purchased a stock g900v and tested with same SIMM successfully.

- Upgraded new phone to LineageOS 18.1.

- Tested new phone successfully.

- OTA update again caused the new phone's mobile data to fail.

- Every attempt to get the new test phone's mobile data working have failed.

- Trying to get it back to stock and working so I can figure out which update killed them.

Hope I gave you the right amount of info here. If I can provide anything else please let me know. It just seems to me like an OTA update must have modded/added something that is being left behind during the flashing process. I'm at a loss - any help will certainly be appreciated.
[Samsung Galaxy S 5 Unified Development] LouLuo:
So, you have 2 klte devices g900v.

Device A was running LOS 18.1 just fine until an OTA.

After OTA, modem (data, call & texts) were broken.

SIM card tested sucessfully with other device.

Flashed device A to stock: ALL_VZW_G900VVRU2DQL1_G900VVZW2DQL1_CL8025411_QB16020535_REV00_user_low_ship_MULTI_CERT.tar.md5

-

Then I'm not sure if modem worked for a moment or not at all.

What do you mean with "booted backup to find a text to come through at first and then fail again." ?

-

Then, you used RootTools to customize your running system. - Which likely won't solve the modem issue - : calls & text & mms worked for a while, not data. After a reboot, modem is failling.

You bought a new g900v with stock fw, let's call it device B.

Modem works with it, as well as in LOS 18.1.

But modem broke again with an OTA upgrade.

I suspect an incompatible BL and modem version to run properly from Android 6.

As it have been with mine until I forced it to upgrade from stock fw, following the steps from my previous post.

I am doubtful about LOS18.1 OTA breaking modem in such way it doesn't work back from stock Android 6 fw.

If my tutorial doesn't work for you,

I suggest you to flash latest Android 5 stock fw and see if modem is working and stable.

Then upgrade with Odin to the oldest Android 6 version with the same country&carrier code.

Now if modem works reliably, you should be able to restore your LOS18.1 backups if you have it, and enjoy a working modem :)

Few questions:

- Can you specify the current running bootloader version of your devices from getprop cmd or equivalent? Is it matching your flashing files?

- Can you specify which version of Android was running on your new device B g900v, before flashing LOS 18.1?

- Do you have a backup of your stock Samsung system+modem to flash back with TWRP?

- Have you made a modem and EFS partitions backup before the OTA, when modem worked?

- Can you provide Odin's both log to check which partitions are flashed back to stock from the 2 differents .tar.md5 files you used?
[Samsung Galaxy S 5 Unified Development] frone0:
Looks to me like we are close to being on the same page with Phone A and Phone B:

Phone A was my initial phone that was upgraded to 18.1, worked great for about a year, then failed after the OTAU. I have not yet reinstalled this one since the initial failure. I have been performing OTA updates to it and testing after each. The mobile data continues to fail on an otherwise perfectly running system.

Phone B was purchased to try and troubleshoot the problem. It came with Verizon Stock 6.01 Android and worked with the same SIMM card from Phone A. I upgraded it to LineageOS 18.1 and tested successfully. Then when taking an OTAU, it the mobile data failed just like Phone A. This is the phone I have been testing on since having issues with Phone A.

Not sure if it is important, but I also purchased a third (Phone C) one that does not have a unlockable bootloader. It is the same model as the others, but has the eMMC that starts with '11'. I have been using it as my daily driver with the same SIMM card used above while troubleshooting the mobile data issue.

Concerning the "booted backup to find a text to come through at first and then fail again." question, after flashing Phone B with the stock firmware, I was able to receive a text at first, but after more testing, it failed. I'm not 100% sure that I didn't have mobile WiFi connected at first and that's why it might have worked. I'll be glad to test again if needed.

I was only able to find one version of Verizon stock Android 5 firmware. It is version G900VVRU2BPB1 from updato.com. I am currently downloading it and will attempt to flash with Odin using your tutorial once it finished downloading.

Here are the current bootloader versions from the three phones:

PhoneA: G900VVRS2DQB2

PhoneB: G900VVRU2DQL1

PhoneC: G900VVRU2DQL1

I'm assuming that we are looking to make sure Phone B's bootloader version matches the flashing files, which it appears that it does as the file name matches the G900VVRU2DQL1.

Phone B was running stock Verizon Android 6.01. However, I'm not sure exactly which release it was.

I sure wish I had, but do not have any backups of the system, modem, or any partitions from when either Phone A or Phone B was working. I don't know if it helps, but I do have Phone C that is working fine currently, including mobile data and on the same SIMM card. As I mentioned, this phone does not have an unlockable bootloader, so I'm not sure if it is any help to us. Just wanted to mention it if it does help.

Are you looking for an Odin 'boot' log here? Not sure if this is something I need to enable during my next flash attempt or if you are looking for the past log files from flashing with Odin previously. Please let me know and I'll try to get this information to you.

Thanks again for all of the help! I really appreciate it!!
[Samsung Galaxy S 5 Unified Development] curiousrom:
What is your network provider?

FYI LineageOS does no support VoLTE on any Samsung devices @ the present because the devs could not reverse engineer Samsung's proprietary VoLTE implementation so far.

That could be a deal breaker if your network provider drops 2G & 3G as only VoLTE will work for voice calls after that.

Some providers will disable data if the device is not currently supporting VoLTE.

BTW if talking about 18.1 on the S5 klte* family you are in the wrong thread. The correct one is:

https://xdaforums.com/t/rom-official-11-lineageos-18-1-for-samsung-galaxy-s5-klte.4267517/

***
[Samsung Galaxy S 5 Unified Development] frone0:
My network provider is Verizon. The VoLTE issue could be a problem in the future. I'm starting to think about giving up. It just nags at me that I can't get the phone to revert to stock and work for some reason. I'd love to get it to work and then Flash an older version of LineageOS from before the OTAU that I 'suspect' may have caused the problems. I'd love to get to the bottom of this - even if I do need to just buy a new phone at this point.

Not sure how I got in the wrong thread with this. I could swear I was working away on your 18.1 upgrade thread. I have read over the rules, but am new to the board. Any chance I can DM you with etiquette questions on how I can move this thread or start a new one while alerting those helping and not being a bother?

Thanks again!
[Samsung Galaxy S 5 Unified Development] frone0:
Just another quick question. As I am going through your steps to flash the phone, it start off with "Format (not wipe) the data partition from TWRP". As I am flashing stock firmware, it no longer has TWRP each time I reflash. Is it OK for me to instead of doing so in TWRP, boot to stock recovery and use the wipe cache/data and factory reset here instead? I spent some time trying to get TWRP reinstalled with the stock Android 5, but am running into problems there.

Thanks again!