flashing official firmware through odin stops secure folder from working? - Samsung Galaxy S7 Questions and Answers

Hello,
I'm in a bit of a confusing situation. When nougat released for s6 last year i think, i flashed it through odin and after that samsung launched/introduced secure folder for nougat and i tried it. It wasn't working because my device status wasn't "official" anymore.
So now I'm thinking again to flash uk firmware (from sammobile) for galaxy s7 sm-g930f(not rooted & device status is OFFICIAL) via odin would this problem happen again if i flash it?
Thanks if anyone's interested to answer my query..!

If you flash the correct firmware from a trusted firmware website, you shouldn't have any issues.
But flashing the wrong firmware (e.g. for the wrong SoC) or flashing firmware from a random blog site might get you in trouble, as they can end up being phone dumps instead of the actual official package.
If you use the files from updato, sammobile, or one of the firmware tools (I think this works despite ceasing development https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647) I'd say you'd be safe.

Chances are if your device was Custom, then you have rooted it at some point / flashed custom, in that case KNOX will be tripped (0x1) and if secure folder relies on KNOX being valid (0x0) as a lot of Samsung stock apps do, it will not work any longer

Beanvee7 said:
If you flash the correct firmware from a trusted firmware website, you shouldn't have any issues.
But flashing the wrong firmware (e.g. for the wrong SoC) or flashing firmware from a random blog site might get you in trouble, as they can end up being phone dumps instead of the actual official package.
If you use the files from updato, sammobile, or one of the firmware tools (I think this works despite ceasing development https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647) I'd say you'd be safe.
Click to expand...
Click to collapse
I've always downloaded firmwares from sammobile.

Related

Flashing more recent stock rom from sammobile

Hi
Apologies for what is quite a basic question for I'm just trying to get things straight in my head before proceeding.
I have a UK retail S7 G930F, current running stock
Build G930FXXU1DQC4
Baseband G930FXXU1DQC2
Despite the fact this build only has Android security patch level February 2017, and the latest build is from 2018, my device and Smart Switch insist I am up to date, I want to actually make this the case while remaining on stock firmware.
I have used Odin to flash Galaxy phones before but not since I had a Note 2 and Note 3 so I'm a little rusty.
I have Odin 3.13.1 and the zip download from sammobile for build G930FXXS2DRAA for the same CSC region I'm currently on which is XEU.
All the guides for Odin flashing say to only use the AP file and option in Odin. However as my BL, CP and CSC will all be older as well, and I'm simply going from stock to stock can I (or should I) also flash these parts as well?
Thanks.
I need more information. 6 mm and 7 nougat use the same BL and require no upgrade where if you were on lollipop somehow you would need the bl. Please DO NOT run off and start flashing things like BL without help from here first. I have bricked a samsung device so bad I had to replace the motherboard, so I learned the hard way.
Both current firmware and the one I intend to flash are Android 7, the new one is just a much more recent build with a more up to date security patch level.
My current firmware, as shipped (or possibly updated OTA a long time ago)
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXU1DQC4/127501/
My intended firmware that I plan to flash
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXS2DRAA/205600/
Despite the fact that sammobile says the newer one is available in Smart Switch, it doesn't show any updates when I connect my device to my PC with Smart Switch.
y2kgecko said:
Both current firmware and the one I intend to flash are Android 7, the new one is just a much more recent build with a more up to date security patch level.
My current firmware, as shipped (or possibly updated OTA a long time ago)
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXU1DQC4/127501/
My intended firmware that I plan to flash
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/XEU/download/G930FXXS2DRAA/205600/
Despite the fact that sammobile says the newer one is available in Smart Switch, it doesn't show any updates when I connect my device to my PC with Smart Switch.
Click to expand...
Click to collapse
I get that a lot. I upgraded my s7 to latest n release today and it worked ok.
So, do I just flash AP or everything?
y2kgecko said:
So, do I just flash AP or everything?
Click to expand...
Click to collapse
You need to flash all 4 files: BL / AP / CP / CSC
I do recommend that you flash CSC* and not HOME_CSC*. That way you will reset the phone to factory defaults and it will be ready for future OTA updates.
Backup your files first that you think are important and then start from scratch to configure the phone, install your apps, update the ones on the phone.

Need Help With My S6 ASAP Please.

Hello wise people of XDA,
This is my first post.
I currently use an S6 G920F United Kindom unlocked as my phone and i have been using this phone for a long time. Now its past its warranty I decided to root the phone and see what i can do with it and get rid of the bloatware. Normally i either use KingoRoot or KingRoot but both failed so I searched around on the internet and came across CF Auto Root. After seeing it was successful for others i jumped on the bandwagon. I rooted it and everything was golden until i came across a problem, it would randomly turn off. This was random and infrequent. but not it happens like 5 times a day so i decided to flash a stock rom. For some strange reason Sam mobile wont let me download a stock Rom so after poking around the internet i have download a few stock roms however they always fail in Odin. Now my phone wont even boot as it says "error occured while updating use smart switch emergency recovery feature" so i go onto the Smart switch PC app and then it doesnt recognise. After 2 days of trying i haven't had any luck so I don't know what to so. Every time I try flashing something, when it fails i get some red text on the phone which I don't understand.
Someone please help me as I cant just buy a new phone and this is the only phone i have got. Any help would be very grateful and please don't hesitate to ask any questions.
Edit:
It says on the Download Screen:
Odin Mode
Product Name: SM-G920F
Current Binary: Custom
System Status: Custom
Reactivation Lock: Off
Secure Download: Enabled
Knox Warranty Woid : 1 (0x0500)
RP SWREV: B:6 K:2 S:2
(When it fails it says) SW REV. Check Fail. Device:6 . Binary: 5
Hopefully that helped.
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Bryan48765 said:
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Click to expand...
Click to collapse
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
wasim.1.wt said:
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
Click to expand...
Click to collapse
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Bryan48765 said:
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Click to expand...
Click to collapse
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
wasim.1.wt said:
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
Click to expand...
Click to collapse
U6/S6, "Device:6" is in the odin log so it's already 6 and won't return to 5.

[G955F] Flashing a stock rom: Warranty void?

Hello,
Like many users on this forum, I updated my brand new S8+ to Pie/OneUI and I hate it.
However, i've been digging on the forum for quite a while and I can't find a clear answer.
Would flashing the official Oreo ROM via ODIN void my warranty?
And where can I find the official ROM for my particular version of the phone?
--EDIT-- I found it on updato, thanks to a thread i missed
Any help would be greatly appreciated
SIHS said:
Hello,
Like many users on this forum, I updated my brand new S8+ to Pie/OneUI and I hate it.
However, i've been digging on the forum for quite a while and I can't find a clear answer.
Would flashing the official Oreo ROM via ODIN void my warranty?
And where can I find the official ROM for my particular version of the phone?
--EDIT-- I found it on updato, thanks to a thread i missed
Any help would be greatly appreciated
Click to expand...
Click to collapse
No it won't void your warranty/Trip Knox.
You can download firmware from either sammobil.com or updato.com these are the two i generally use. ( I see you've found it )
If you do downgrade remember to disable software updates so that you don't go back to pie again.
spawnlives said:
No it won't void your warranty/Trip Knox.
You can download firmware from either sammobil.com or updato.com these are the two i generally use. ( I see you've found it )
If you do downgrade remember to disable software updates so that you don't go back to pie again.
Click to expand...
Click to collapse
I read that there's a way to downgrade like it's an update and keep all data and apps installed (via the HOME file on ODIN), is it real?
SIHS said:
I read that there's a way to downgrade like it's an update and keep all data and apps installed (via the HOME file on ODIN), is it real?
Click to expand...
Click to collapse
Firstly before doing anything I recommend doing a backup first. I don't have a preferred method but you could use cloud based service (Google/Samsung) or something like samsung's smartswitch.
You will need to unzip the firmware that you downloaded. In it will be 5 files which will have to be place in the correct sections of Odin.
There will be 2 CSC files:
CSC - clean install will wipe apps and data ( same as a factory reset )
Home_CSC - dirty install will keep your apps and data.
If downgrading you will need the same or higher bootloader version. The BL number is the 5th number from the right of the firmware name you download.

[Resolved] #Solved# Any Possible Solution to Downgrade Back to Nougat?

Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Softwarehttps://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
spawnlives said:
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
Click to expand...
Click to collapse
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
spawnlives said:
tsam19 said:
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Have rooted the device no problem with magisk and patching the original boot img file. Then flashing patched boot img via odin. Causing device verification to need to reformat the device, resulting in correct root.
Once a device , this device is rooted, no official updates can be installed anyway. When you try to uodate software, a pop up shows as the device recognises the software has been modified.
As for TWRP there ISN'T any version of TWRP available for the Samsung Galaxy Active Tab2 (SM-T395). I have even emailed the makers , developers of TWRP why there isn't one in their device inventory list on their webpage.
So no TWRP, and NO custom roms either for this model.
My concern , was all about finding a valid , safe way to downgrade back to original Nougat 7.1. And until someone can produce a working image with a BL with binary 4. Then there's only one optiin and that is to buy another untampered device with Nougat 7.1 out of the box and leave it un updated. :good:
Thanks for replying.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
To answer your question of how is downgrading such a big problem, it is due to security reasons, to keep your device as secure as possible with the newest available software and the latest security updates.
Sent from my SM-S767VL using Tapatalk

Just Bricked my S7, please, i need help

I was trying to root my Verizon Galaxy S7 and sucessfuly did it using the SuperSU root.bat i found in:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
However when i noticed how performance was very affected by this it was an immediate regret, so i tried 3 different versions of Odin (v3.14.1, v3.12, and v3.12 (PrinceComsy)) to use the stock firmware provided in that thread to flash it, however in my las attempt (PrinceComsy) it failed and when i tried to go back (in shame and having failed) the phone wont boot and it says "Software Update Failed, Your device didn't update sucessfuly. Use the Version Software Update Assistant on a computer to repair your device and complete the update."
Edit: 7:16PM Got it to boot, no longer bricked but i still need to either get it back to stock or fix the horrible performance
Download stock firmware either from the samfirm tool, sammobile, or updato. Flash with Odin, make sure you select all four files (AP, CP, CSC, BP)
Most root methods for the USA models involve using an engineering bootloader, which comes with performance and battery impacts you can't get around because it's due to the bootloader. It's either root + performance impact, or stock no root.
Does anyone have a link to the fix/debloat scripts? The links on the thread no longer work. Thx Btw ^

Categories

Resources