I have a samsung galaxy j400G and my current baseband version is j400GDXS6BTE1.
I cant find an exact baseband version to download a firmware for my phone
The closest one i found is J400GDXU2ARH1
Can i use it on my device?
Im planning to install magisk manager for internal audio recording because my current version is on android 9 and its not possible for me to record internal audio without rooting please help
Recommend me something an easier way to record internal audio on android 9 feel free to comment
suzakuharu said:
I have a samsung galaxy j400G and my current baseband version is j400GDXS6BTE1.
I cant find an exact baseband version to download a firmware for my phone
The closest one i found is J400GDXU2ARH1
Can i use it on my device?
Im planning to install magisk manager for internal audio recording because my current version is on android 9 and its not possible for me to record internal audio without rooting please help
Recommend me something an easier way to record internal audio on android 9 feel free to comment
Click to expand...
Click to collapse
That firmware is for your device, but, you won't be able to flash it because the binary version is lower than the binary version that you already have on the device. The 5th character from the right end of the firmware is the binary version. The binary version that you currently have installed is a binary 6 firmware, the firmware that you are asking if can be flashed is a binary 2 firmware. You can only flash a firmware that has an equal or higher binary, you can not flash a firmware that has a lower binary version. If you were to update to a binary 7 firmware, you would not be able to go back to the binary 6 firmware that is on your device now but you could flash a binary 7 or binary 8 firmware.
Sent from my SM-S767VL using Tapatalk
Related
Hi There
I have been searching for a way to change the Binary version on a Samsung device or Firmware.
I have multiple devices that i need to change the carrier type on and can only do it with the version of Odin i have if the Binary version is the same or higher for the Firmware.
For example:
I can change a device with G935PVPU4BQH1 on it to G935UUEU4BQD2 as the Binary is 4 for both
However if the version is G935PVPS5BQK1 or G935PVPU6BRD2 i cannot currently load G935UUEU4BQD2 onto it.
It there a way to either bypass the Binary rule or change the binary on the device or firmware i have as i cannot find a higher version for all the models i need to process.
So you want to downgrade?
Good luck with that...
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
i cant flash stock rom (INS) pie version using oding 14.1, i did try using xtc firmware it says sw rev. check fail(bootloader) device 8 binary 6 too. how to fix this?? please help
Hello! sw rev. check fail(bootloader) device 8 binary 6 means that the ROM you have downloaded has a binary 6 while the device has a binary 8. In Android, or at least Samsung phones you cannot go to a lower binary than the one present in your device. Basically the only fix I believe is to download a ROM that has a binary of 8. If you do not know what binary it has I will leave a screenshot showing which number signifies a binary (Only mind the number in the binary, the U is a part of that but you just need to look at the number when you're downloading the correct ROM).
download latest stock
You have updated your device to Binary 8. Which means you have an updated bootloader. Samsung no longer allows the bootloader to be downgraded so you are stuck there. Anyways there's no worries. There are alot of ROMs and mods to use that you may enjoy.
Bootloop
Hi. Sorry for my bad English.
My problem is that despite uploading the rom, my phone is in a loop and uploading the rom does not help. Please help.
AdamAnd said:
Hi. Sorry for my bad English.
My problem is that despite uploading the rom, my phone is in a loop and uploading the rom does not help. Please help.
Click to expand...
Click to collapse
Flash last ROM latest release of your country
Test latest releases of your country
Downgrade not possible
hacker812c said:
Flash last ROM latest release of your country
Test latest releases of your country
Downgrade not possible
Click to expand...
Click to collapse
Hi. Thanks for the suggestion, but unfortunately after successfully uploading the latest software from my region (XEO) nothing changes. The phone is rebooting and it's still looped.
Region - firmware:
sammobile.com/samsung/galaxy-j6/firmware/SM-J600FN/XEO/download/J600FNXXU8CTF5
I can go to Download Mode and Recovery.
I guess there is something wrong with Recovery.
The recovery on my phone looks like this:
Android Recovery
samsung/j6ltexx/j6lte
10/QP1A. 190711.020/J600FNXXU8CTF5
user/release-keys
Android Recovery
samsung/j6ltexx/j6lte
10/QP1A. 190711.020/J600FNXXU8CTF5
user/release-keys
Sorry, but I connected to the topic and I think I should start a new topic with my problem.
I am asking the moderator for information or to move my posts to the right place. Thank you.
SirDoz said:
You have updated your device to Binary 8. Which means you have an updated bootloader. Samsung no longer allows the bootloader to be downgraded so you are stuck there. Anyways there's no worries. There are alot of ROMs and mods to use that you may enjoy.
Click to expand...
Click to collapse
I cannot find a Saudi Arabia KSA region rom for my SM-J730F ( I can't use my sim because of that)
The rom I can find on sammobile is at u4, and my phone has s7 so it gives the error. However there is another rom that is latest but that rom is Saudi Arabia ACR Please help me
got the same issue on a s10... device 9, binary 8
Fanges4033 said:
got the same issue on a s10... device 9, binary 8
Click to expand...
Click to collapse
any solution for this?
Fanges4033 said:
got the same issue on a s10... device 9, binary 8
Click to expand...
Click to collapse
find the latest and cointain number 9
at middle
Can't we downgrade using Combinational rom?
Aleks Skuber said:
Hello! sw rev. check fail(bootloader) device 8 binary 6 means that the ROM you have downloaded has a binary 6 while the device has a binary 8. In Android, or at least Samsung phones you cannot go to a lower binary than the one present in your device. Basically the only fix I believe is to download a ROM that has a binary of 8. If you do not know what binary it has I will leave a screenshot showing which number signifies a binary (Only mind the number in the binary, the U is a part of that but you just need to look at the number when you're downloading the correct ROM).
Click to expand...
Click to collapse
My SM G950F shows binary 12,but i cant find any b12 files
rtyuakatsuki said:
find the latest and cointain number 9
at middle
Click to expand...
Click to collapse
where can I find the binary 8 for the S7 SM-G930F, the samobile firmware page sucks
marinson said:
where can I find the binary 8 for the S7 SM-G930F, the samobile firmware page sucks
Click to expand...
Click to collapse
Find it in samfw
How to convert sm-n976n to sm-n976b? Please help me!
Diyorbek98 said:
How to convert sm-n976n to sm-n976b? Please help me!
Click to expand...
Click to collapse
They both have the exact same hardware, so, you should be able to download the stock firmware for SM N976B and flash it on the SM N976N using Odin without issues.
On the SM N976N device, go to system settings>about>software information>build number. Look at the build number and find the 5th character from the right, this is the currently installed binary version.
Then, when you find the firmware files that are available for the SM N976B, look at thier build number and make sure that the 5th character from the right(the binary version) in the build number is equal to or higher than the binary version of the firmware build number that is currently installed on your SM N976N device. Do not try to use a firmware that has a binary version that is lower than your current binary version, it will not work.
Hello hope you're having a good day, I'm looking for way to downgrade a53 5g from Android 13 to Android 12 ??? I found some firmwares for Android 12 but the binary number is 4 and Android 13 is actually on binary number 5 , no way to do the downgrade with Odin?
I read somewhere that is not possible to flash a firmware with different binary number is it true ??
I would like to comeback to android 12 it's better if someone has a solution it would be so helpful
Impossible to flash lower binary versions with Odin
Lipelipo said:
Hello hope you're having a good day, I'm looking for way to downgrade a53 5g from Android 13 to Android 12 ??? I found some firmwares for Android 12 but the binary number is 4 and Android 13 is actually on binary number 5 , no way to do the downgrade with Odin?
I read somewhere that is not possible to flash a firmware with different binary number is it true ??
I would like to comeback to android 12 it's better if someone has a solution it would be so helpful.
Click to expand...
Click to collapse
you can try grab a a51 4g firmware, then extract system.img from it and then flash it with twrp as a system image (yes) (yes) (yes) (yes again)