Database Users

Help Selecting correct TWRP/Odin for SM-G900W8 (Dec 2017)

I want to install TWRP on my Samsung Galaxy S5 (Telus Canada - SM-G900W8 - Stock Android v5.1.1 ROM) using Odin.
I have found this list on the TWRP site: https://dl.twrp.me/klte/
IIUC, I need to select one of the TAR files to flash with Odin. My plan is to use TWRP to update my device with a Nougat ROM (likely LOS, RR, crDroid.) and root.
My question is: Do I use the latest version, or should I be using an older version?
What about Odin? I found this site: http://www.**********.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/, but I'm not sure which version I should get.
My questions is: Do I use the latest version, or should I be using an older version?
And these apprear to be the correct drivers: https://androidmtk.com/download-samsung-usb-drivers
Option: Samsung Galaxy S5 (All Variants) which points to hee:
http://samsungusbdriver.com/download/samsung-driver-v1-5-63-0
Also are there any MD5s/SHAs for Drivers/TWRP/Odin to make sure that the files haven't been tampered with?
Thanks in advance for any suggestions/assistance.

Working TWRP for SM-G900W8
For the record I can confirm that TWRP v3.2.1-0-klte works for the Canadian Version
of the Samsung Galaxy S5 SM-G900W8
https://dl.twrp.me/klte/twrp-3.2.1-0-klte.img.tar.html
And I used this version of the ODIN Flash Utility for Samsung
Source: http://downloadandroidfiles.org/file-php/?File=/Tools/Odin3v185.zip
File Name: Odin3v185.zip
Filesize: 198.52KB
Uploaded: September 25, 2012
MD5: 0c21e86a38c7868b0b50396eee85721f
It's maybe not the latest, but it seemed to to the job. There seem to be a lot of infected versions of ODIN floating around, which is why the link is *** out. When I didn't get any answer I tried that source, but VirsusTotal flagged the file as infected, so I used an old file that I found a year before. This one seemed to be OK.

rootkitty said:
For the record I can confirm that TWRP v3.2.1-0-klte works for the Canadian Version
of the Samsung Galaxy S5 SM-G900W8
https://dl.twrp.me/klte/twrp-3.2.1-0-klte.img.tar.html
And I used this version of the ODIN Flash Utility for Samsung
Source: http://downloadandroidfiles.org/file-php/?File=/Tools/Odin3v185.zip
File Name: Odin3v185.zip
Filesize: 198.52KB
Uploaded: September 25, 2012
MD5: 0c21e86a38c7868b0b50396eee85721f
It's maybe not the latest, but it seemed to to the job. There seem to be a lot of infected versions of ODIN floating around, which is why the link is *** out. When I didn't get any answer I tried that source, but VirsusTotal flagged the file as infected, so I used an old file that I found a year before. This one seemed to be OK.
Click to expand...
Click to collapse
Hi,
Much newer odin you can take from this link (Instructions section):
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900W8/TLS/download/G900W8VLU1DQB2/126298/

What firmware for XT1681

Hey there !
I have a Moto G5 Plus International edition (XT1681) with firmware NPNS25.137-92-4 (latest January Patch).
I want to know what firmware to download from here (https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/) for factory flash not to get bricked like an idiot.
I don't know which one is good
Thanks

The last 2 ROMs are for your device, if you have a custom recovery I recommend to install the flashable version from this link .
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Here are the same version of your device NPNS25.137-92-4 (20180101 security patch)

Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/

CobraBoyFR said:
Oh nice !
Is it OK to OTA update on these flashable .zip ? As I have also modified the kernel which is not stock anymore :/
Click to expand...
Click to collapse
i didnt try to flash over a fastboot rom, maybe you cant do that.

Thanks
But basically, what I need is flashing full stock firmware (with recovery and kernel), no matter if it's january update or not. Just the factory images I had when I bought the phone. And I don't know what version is OK for my phone (XT1681 with NPNS25.137-92-4 now) 'cause I don't want to hard brick it when OTA updating (to Oreo for example)

From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.

RokCruz said:
From your link the last 2 ROMs are the same so you can use both.
You are on stock right? Do you planning on flashing custom ROMs? If you flash Oreo ROMs and you want to downgrade flashing fastboot rom maybe you lost volte.
Click to expand...
Click to collapse
Right now I'm on stock NPNS25.137-92-4, with TWRP recovery + Magisk root + ElementalX kernel
I'm not planning to flash any custom ROM for the moment. When the official Oreo update comes out, I want to update. But I know it won't go well if I OTA update it with my current configuration. That's why I want to be able to flash stock with fastboot (rough clean install), no matter what version I get : All i want is to be able to update to Oreo when it's out. Problem is, I don't know which image I need to download from here : https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
I know it's there, but don't know exactly the good version.

This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.

RokCruz said:
This is for our device xt1681
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I'm on flashable stock with ex kernel and magisk, when the Oreo ota start rolling out I'll wait for flashable rom so I'll can upgrade (dirty flash) so I don't loose anything.
Click to expand...
Click to collapse
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.

echo92 said:
If your device was flashed with stock firmware newer than NPN25.137-15, I would strongly advise against flashing the NPN25.137-15 stock firmware.
The reason is that downgrading stock firmware downgrades your system, but not usually your bootloader (your bootloader will likely report a security downgrade/pre-flash validation error). As such, you'll have a newer bootloader but older system (in terms of patch levels). For example, you have the NPNS25.137-92-4 stock firmware (before flashing TWRP), so your bootloader is the Jan 2018 patch level. You flash this NPN25.137-15 firmware - you have a Jan 2017 system, but still a Jan 2018 bootloader.
The downgrade generally goes okay. However, taking OTA updates with this mismatch in bootloader and system is generally what results in hard bricks; the OTA update checks for your system patch level - in the above example, you'll probably get the OTA update to upgrade from NPN25.137-15... However, your bootloader is not the NPN25.137-15 patch level bootloader, as such your bootloader may get overwritten by the OTA and gets corrupted in the process, leading to hard bricks. This scenario isn't just applicable for the NPN25.137-15 update, this potentially applies if you flash a stock firmware older than what was on your device and then attempt to use OTA updates (unless you could flash the stock firmware directly preceding the firmware you had).
Easiest way is to re-flash the same stock ROM build you had before flashing TWRP. I don't see any NPNS25.137-92-4 stock ROMs leaked yet from the Motorola Firmware Team page https://androidfilehost.com/?a=show&w=files&flid=171014 or firmware.mirror but hopefully they'll be along soon.
If you're on stock NPNS25.137-92-4, in theory you could flash NPN25.137-92 (the build directly before the NPNS25.137-92-4 Jan 2018 security update), so the next OTA update would update your device to NPNS25.137-92-4 - the OTA would be simply patching your device to the same build it's currently on and in theory that should work. NPN25.137-92 is one of the firmwares currently available so may be worth thinking about. Best thing though is to flash the NPNS25.137-92-4 firmware or newer firmware that is the correct build for XT1681 devices.
Click to expand...
Click to collapse
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?

RokCruz said:
In few words we only can flash ROMs with the same compilation number or higher to avoid hard brick right?
Click to expand...
Click to collapse
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).

echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
That was roughly what I figured out but damn, those explanations, thanks buddy :highfive:

The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.

driverdis said:
The January update's bootloader is the same bootloader that the November security patch update has. You can flash the
POTTER_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC files from fastboot (skip gpt.bin) then OTA to 93 (November Patch), then OTA to 93-4 (January Patch)
The OTA will not brick the phone since the bootloader the OTA flashes is the same one it is currently on.
Also, this is what I did to get onto the January Patch so I can confirm my phone works fine and did not brick.
Click to expand...
Click to collapse
On xt1681 right?
Thanks for your feedback

echo92 said:
Pretty much, yes (or at least it minimises the chances of a hard brick). If you really want to flash older stock ROMs, please do not use OTA updates at all. Ignore the OTA prompt or freeze the Motorola OTA updater if you downgraded your stock firmware. It's not fun seeing a £150-200 (or your regional equivalent) device hard bricked.
However, with Motorola's habit of releasing different builds to different regions, please ensure you flash the correct build for your device, else the Motorola servers may not issue OTAs if you're on the incorrect series of builds for your software channel. The latest available leaked firmware for your device appears to be NPN25.137-92 (we don't have access to NPNS25.137-92-4 yet).
Click to expand...
Click to collapse
yeah i cant apply normal OTA over flashable rom. I was on NPN25.137-92(flashable) i download NPNS25.137-92-4(flashable too) i dirty flashed it and it works perfect without lose my stuff

I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.

jkl555 said:
I ordered XT1681 International version from Amazon.ca. I replaced the recovery with TWRP. I have two questions.
(1) I am prompted to install 137-92-8 via OTA. Where can I find this TWRP flashable ROM for this version ? I am on 137-92-4.
(2) Is there any other compatible stock ROM that I can install on it ? The OTA message is in Spanish. My preference is in English and as long as it supports the dual SIM and the NIC.
Thanks.
Click to expand...
Click to collapse
Just to reply to myself for (2). I found the following link
https://www.stockrom.net/2017/05/st...g5-plus-xt1683-xt1681-android-7-0-nougat.html

Problems with Moto G5 Plus

I'm worried that I've permanently messed up my phone. I didn't make a backup of my stock firmware when I first flashed Lineage OS, and then I was having issues with that, so now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk. That should of been sufficient to factory reset it right? It just keeps having little problems that it didn't have before, like internet loading things slowly and bugs and crashing apps. The reason I switched off the Lineage OS rom is because it had little problems like that too. I just don't know what to do anymore.
Relevant Info:
Device: Moto G5 Plus Unlocked US version
Carrier: T-Mobile

lumbo7333 said:
I'm worried that I've permanently messed up my phone. I didn't make a backup of my stock firmware when I first flashed Lineage OS, and then I was having issues with that, so now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk. That should of been sufficient to factory reset it right? It just keeps having little problems that it didn't have before, like internet loading things slowly and bugs and crashing apps. The reason I switched off the Lineage OS rom is because it had little problems like that too. I just don't know what to do anymore.
Relevant Info:
Device: Moto G5 Plus Unlocked US version
Carrier: T-Mobile
Click to expand...
Click to collapse
What exactly are your problems? Check the thread of the custom ROM you installed and look for fixes there, maybe you installed an outdated version and your problems have been fixed in the updates. Good luck.

lumbo7333 said:
...now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk.
Click to expand...
Click to collapse
What do you mean with "stock but not official"?
Where did you get it from?
There are some sources for official firmwares signed by Motorola here on XDA so what makes you think the one you use isn't official?
If so that could be for sure the reason for problems for I have to say that I haven't seen unofficial stock ROMs except TWRP flashables (you said you flashed using fastboot so it can't be this) or debloated stock ROMs.

Wolfcity said:
What do you mean with "stock but not official"?
Where did you get it from?
There are some sources for official firmwares signed by Motorola here on XDA so what makes you think the one you use isn't official?
If so that could be for sure the reason for problems for I have to say that I haven't seen unofficial stock ROMs except TWRP flashables (you said you flashed using fastboot so it can't be this) or debloated stock ROMs.
Click to expand...
Click to collapse
I mean it didn't come officially from Motorola. I got it from this:
getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated (It's not allowing me to post outside links because I'm a new user, so just add www to that)

lumbo7333 said:
I mean it didn't come officially from Motorola. I got it from this:
getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated (It's not allowing me to post outside links because I'm a new user, so just add www to that)
Click to expand...
Click to collapse
If you can flash the firmware by fastboot it's most likely an official signed firmware that was leaked. To be on the safe side use the firmware found here on XDA like this source:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Just make sure to use the same firmware you we're on or a newer one that fits to your region.
I recommend to reflash the latest stock firmware, maybe something went wrong the first time.
And remember to always make a backup before you flash anything that could cause problems.

It the latest stock firmware different from the stock rom I flashed?

You can also try the repair function in Lenovo Moto Smart Assistant app.
https://support.motorola.com/us/en/solution/MS126499

Hmm. Now my security updates are failing.

goodjuju said:
You can also try the repair function in Lenovo Moto Smart Assistant app.
https://support.motorola.com/us/en/solution/MS126499
Click to expand...
Click to collapse
Will doing that use official firmware?

lumbo7333 said:
It the latest stock firmware different from the stock rom I flashed?
Click to expand...
Click to collapse
lumbo7333 said:
Will doing that use official firmware?
Click to expand...
Click to collapse
Sure. The firmwares from Moto Smart Assistant are the same like the ones I've posted above, I compared the hash files.
Would be interesting to know what firmware you're on at the moment.

I'm on OPSS28.85-17-2
I thought my firmware was unofficial since it was leaked. Also do you why I can't update?

lumbo7333 said:
I'm on OPSS28.85-17-2
I thought my firmware was unofficial since it was leaked. Also do you why I can't update?
Click to expand...
Click to collapse
Any firmware you'll find is leaked even the official ones. Motorola doesn't release any firmwares except the ones you can download with Lenovo Motorola Smart Assistant.
The link I posted https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
contains official firmwares too. The latest one for the US (85-17-4) can be found there too.
What happens exactly when your OTA fails?

Wolfcity said:
Any firmware you'll find is leaked even the official ones. Motorola doesn't release any firmwares except the ones you can download with Lenovo Motorola Smart Assistant.
The link I posted https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
contains official firmwares too. The latest one for the US (85-17-4) can be found there too.
What happens exactly when your OTA fails?
Click to expand...
Click to collapse
- I download the update the update
- It reboots and goes into TWRP for some reason
- I have to manually reboot to system from TWRP
- My phone boots to system and says update unsuccessful
(This is a security update by the way.)

lumbo7333 said:
- I download the update the update
- It reboots and goes into TWRP for some reason
- I have to manually reboot to system from TWRP
- My phone boots to system and says update unsuccessful
(This is a security update by the way.)
Click to expand...
Click to collapse
You can't take any system updates when you have TWRP installed!
For OTA you have to be on unrooted full stock ROM incl. stock recovery. This is a very important rule.
So you have to ways to handle this:
- Flash clean stock firmware and apply to the OTA afterwards (if you flash the latest firmware 17.4 you don't need the OTA anymore). You will loose your internal storage data or skip the "erase userdata" command.
Firmware from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
- Take a TWRP flashable build but be aware that you can't take OTA updates at all in the future which is not needed as the firmwares are up to date.
TWRP flashables here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482

Wolfcity said:
You can't take any system updates when you have TWRP installed!
For OTA you have to be on unrooted full stock ROM incl. stock recovery.
So you have to ways to handle this:
- Flash clean stock firmware and apply to the OTA afterwards (if you flash the latest firmware 17.4 you don't need the OTA anymore). You will loose your internal storage data or skip the "erase userdata" command.
Firmware from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
- Take a TWRP flashable build but be aware that you can't take OTA updates at all in the future which is not needed as the firmwares are up to date.
TWRP flashables here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Click to expand...
Click to collapse
Will flashing a new build delete my data?

Unable to root my Verizon Samsumg Galaxy S7 Edge

​ Hello, stop I'm attempting to get my phone successfully rooted. But I can't get anything but the official stock firmware to flash in Odin. I have downloaded multiple stock and custom firmware files, just about all of this threads Odin files with no luck. My conclusion is the CSB1 update patched root.
Here's my software details:
Android Version 8.0
Samsung Experience version 9.0
Baseband version
G935VVRS9CSB1
Kernel version
3.18.71
[email protected] #1
Fri Feb 1 19:05:16 KST 2019
Build number
RT6NW.G935VVRS9CSB1
SE for Android status
Enforcing
SEPF_SM-G935V_8.0.0_0016
Fri Feb 01 19:20:33 2019
Knox version
Knox 3.1
Knox API level 25
TIMA 3.3.0
Security...
...
...
Android security patch level
February 1, 20191
Am I ****ed or is it able to be rooted?

Same problem. For one, we have a v9 bootloader. In addition to that there is something, possibly patched boot

aviberk77 said:
Same problem. For one, we have a v9 bootloader. In addition to that there is something, possibly patched boot
Click to expand...
Click to collapse
Can we flash the UU or something to it?

The u firm with the v9 bootloader is the only thing besides regular Verizon stock, yes. You have to use this
Sm-g935uueu9csa3

aviberk77 said:
The u firm with the v9 bootloader is the only thing besides regular Verizon stock, yes. You have to use this
Sm-g935uueu9csa3
Click to expand...
Click to collapse
Can i flash root with that??

aviberk77 said:
Same problem. For one, we have a v9 bootloader. In addition to that there is something, possibly patched boot
Click to expand...
Click to collapse
You can do it with G935V_REV_9_ENG_ROOT-YEMEN-PRO, ... regards

Galaxy S8+ G955F stuck on Oreo July's patch

Hi, thanks for reading. My S8+ G955F stopped finding updates after 2018 July's security patch, when I try to search for updates manually it says that the device is up to date already (its 2019 April's 20th today).
I never flashed a custom ROM, it's 100% stock and Knox is intact.
I wonder if there is a way to just update with Samsung official tooling or just flash with TWRP the OneUI Pie official ROM without having to go through every update to date manually (there must be dozens of them).
I attached my current build and firmware below.
Thanks for reading and have a great day.

xRaevyn said:
Hi, thanks for reading. My S8+ G955F stopped finding updates after 2018 July's security patch, when I try to search for updates manually it says that the device is up to date already (its 2019 April's 20th today).
I never flashed a custom ROM, it's 100% stock and Knox is intact.
I wonder if there is a way to just update with Samsung official tooling or just flash with TWRP the OneUI Pie official ROM without having to go through every update to date manually (there must be dozens of them).
I attached my current build and firmware below.
Thanks for reading and have a great day.
Click to expand...
Click to collapse
You could try first Samsung's Smart Switch to see if that will update your phone.
If not the other way would be to download your firmware and flash with Odin.

spawnlives said:
You could try first Samsung's Smart Switch to see if that will update your phone.
If not the other way would be to download your firmware and flash with Odin.
Click to expand...
Click to collapse
having the same issue . do you need to go update by update if you decide to install by odin? or can you just pick the last version and install it?

zoiden said:
having the same issue . do you need to go update by update if you decide to install by odin? or can you just pick the last version and install it?
Click to expand...
Click to collapse
No you don't need to do incremental updates
Just update to the version you want