Hello,
Is it possible to downgrade from Android 10 to 9 please with my sm-g970f (s10e)?
I am currently on a baseband version with S9 in the middle of it.
Phone isnt rooted or any mods.
I have tried to flash to Android 9 via Oden with a stock rom I found, however it gets stuck on the boot.img bit and doesnt move.
Any help appreciated.
Thank you.
mpwilson99 said:
Hello,
Is it possible to downgrade from Android 10 to 9 please with my sm-g970f (s10e)?
I am currently on a baseband version with S9 in the middle of it.
Phone isnt rooted or any mods.
I have tried to flash to Android 9 via Oden with a stock rom I found, however it gets stuck on the boot.img bit and doesnt move.
Any help appreciated.
Thank you.
Click to expand...
Click to collapse
Hi, What bootloader version are you on?
For example if software version is: G970FXXU3ASJD than bootloader is U3
Related
Hi guys a bit of help please. I'm about to fully flash my device back to stock.
I have a o2 UK variant s6. I have downloaded the correct 5.1.1 rom via sammobile. However the worry I have is about the bootloader, do I have to do anything with it.
Thanks in advance.
THE BIG 360 said:
Hi guys a bit of help please. I'm about to fully flash my device back to stock.
I have a o2 UK variant s6. I have downloaded the correct 5.1.1 rom via sammobile. However the worry I have is about the bootloader, do I have to do anything with it.
Thanks in advance.
Click to expand...
Click to collapse
You shouldnt have to if you have any concerns just do it though smart switch on your pc once the program opens up click over to emergencey recovery and punch in your device name eg. SM-G92xx and your serial number make sure its all capitals it will download the correct software for your device and flash it for you. If this dosent work then you shouldn't have problems with odin as long as your not downgrading from 6.0.1 to 5.1.1
That's the wierd thing. Smart switch will not recognise my phone. Windows dose and Odin just not smart switch. Is it because I'm rooted running a custom rom.
I was on 6.0.1 but reverted back to a 5.1.1 custom rom. Dose that make a difference.
Thanks
THE BIG 360 said:
That's the wierd thing. Smart switch will not recognise my phone. Windows dose and Odin just not smart switch. Is it because I'm rooted running a custom rom.
I was on 6.0.1 but reverted back to a 5.1.1 custom rom. Dose that make a difference.
Thanks
Click to expand...
Click to collapse
Im rooted on custom rom and it sees my phone hmmm well aslong as u flash a 5.1.1 bootloader when u came back you should be fine
I have a Sprint phone that is unlocked and now on T-Mobile. I was attempting to flash the device to use the universal software. I followed the instructions from another thread, but the attempt failed. No failure error was given in Odin.
The phone showed eMMC write fail: aboot
Device info:
Model = SM-G930P
Software = G930PVPS5BRA1
Android Version = 7
Files I tried to flash with:
AP_G930UUES4BRA1_CL12483084_QB16439472_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G930UUES4BRA1_CL12483084_QB16439472_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G930T1UVS4BRA1_CL12142063_QB16359088_REV02_user_low_ship_MULTI_CERT.tar.md5
CSC_OYM_G930UOYM4BRA1_CL12483084_QB16439472_REV02_user_low_ship_MULTI_CERT.tar.md5
What are my options? I basically just need this device to have a universal or T-Mobile firmware installed, so WiFi calling and VoLTE can work.
Brand new at this.. Now the phone is just flashing the Galaxy Logo over and over. I tried entering in boot mode, but that just flashes over and over as well.
LevelOneTech said:
I have a Sprint phone that is unlocked and now on T-Mobile. I was attempting to flash the device to use the universal software. I followed the instructions from another thread, but the attempt failed. No failure error was given in Odin.
The phone showed eMMC write fail: aboot
Device info:
Model = SM-G930P
Software = G930PVPS5BRA1
Android Version = 7
Files I tried to flash with:
AP_G930UUES4BRA1_CL12483084_QB16439472_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G930UUES4BRA1_CL12483084_QB16439472_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G930T1UVS4BRA1_CL12142063_QB16359088_REV02_user_low_ship_MULTI_CERT.tar.md5
CSC_OYM_G930UOYM4BRA1_CL12483084_QB16439472_REV02_user_low_ship_MULTI_CERT.tar.md5
What are my options? I basically just need this device to have a universal or T-Mobile firmware installed, so WiFi calling and VoLTE can work.
Brand new at this.. Now the phone is just flashing the Galaxy Logo over and over. I tried entering in boot mode, but that just flashes over and over as well.
Click to expand...
Click to collapse
The problem is that your phone has a version 5 of bootloader and you try to flash a 4 version bootloader, you need to flash back a version 5 bootloader rom, you original one.
hope it can help
pippone121263 said:
The problem is that your phone has a version 5 of bootloader and you try to flash a 4 version bootloader, you need to flash back a version 5 bootloader rom, you original one.
hope it can help
Click to expand...
Click to collapse
Thank you for the reply. As someone who's inexperienced in this, how do I know what version I'm using? 4 vs 5.
Do you know where I can get a version 5 ? Preferably one for T-Mobile?
LevelOneTech said:
Thank you for the reply. As someone who's inexperienced in this, how do I know what version I'm using? 4 vs 5.
Do you know where I can get a version 5 ? Preferably one for T-Mobile?
Click to expand...
Click to collapse
you have to look to this number: G930PVPS 5 BRA1
pippone121263 said:
you have to look to this number: G930PVPS 5 BRA1
Click to expand...
Click to collapse
Thank you very much. it worked.
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
hi i have a sm g610y and have a few question regarding updating
how do i upgrade from android 6 to android 7. and if i did upgrade is it possible and safe to downgrade.
what things do i lose out if i upgrade from 6 to 7?
anthony001 said:
hi i have a sm g610y and have a few question regarding updating
how do i upgrade from android 6 to android 7. and if i did upgrade is it possible and safe to downgrade.
what things do i lose out if i upgrade from 6 to 7?
Click to expand...
Click to collapse
Since the j7 prime never recieved any bootloader upgrades it is possible to downgrade. I would suggest upgrading to oreo however,or maybe installing android 10 custom roms. anyway, to install stock 7/8 go to this link and enter your device model and country and download the latest stock firmware for you. then download odin . once you have both downloaded, unzip both of them, and open up odin. When you get you should see ap, bl, cp,csc . press the 4 buttons mentioned before and go to where you extracted the stock firmware, and you can select the appropriate file. Then boot your device to download mode by holding volume down, power and home button at the same time for 5-10 seconds. press continue. Then connect your phone to your pc, and press start in odin.
santhosh ravi said:
Since the j7 prime never recieved any bootloader upgrades it is possible to downgrade. I would suggest upgrading to oreo however,or maybe installing android 10 custom roms. anyway, to install stock 7/8 go to this link and enter your device model and country and download the latest stock firmware for you. then download odin . once you have both downloaded, unzip both of them, and open up odin. When you get you should see ap, bl, cp,csc . press the 4 buttons mentioned before and go to where you extracted the stock firmware, and you can select the appropriate file. Then boot your device to download mode by holding volume down, power and home button at the same time for 5-10 seconds. press continue. Then connect your phone to your pc, and press start in odin.
Click to expand...
Click to collapse
why oreo? and whats the difference between a normal android 10 and a custom android 10? do i need to root to install custom android 10? also if i upgrade will my files be deleted? how much disk space is needed?
anthony001 said:
why oreo? and whats the difference between a normal android 10 and a custom android 10? do i need to root to install custom android 10? also if i upgrade will my files be deleted? how much disk space is needed?
Click to expand...
Click to collapse
oreo is the latest official firmware recieved by this phone. There is no official android 10 rom for this phone. Yes you will likely lose all your data.
santhosh ravi said:
oreo is the latest official firmware recieved by this phone. There is no official android 10 rom for this phone. Yes you will likely lose all your data.
Click to expand...
Click to collapse
if lets say i successfully flashed 8.1.0 using the above instruction how do i go back to 6.0.1?
i searched my firmware on samfw and the only available fw for my model and country is 6.0.1. if i flash other countrys fw with same exact model will it work or will it not work? the only available firmware is 7.0.0
bump anyone?
anthony001 said:
bump anyone?
Click to expand...
Click to collapse
You can flash firmware of any county, since is for the exact same model you have (ex: SM-G610) there's no problem. But keep in mind some have bootlogo/apps from operator, and/or extra functionality s/bloatwares.
Hey guys all good?
I got my hands on an A53 already on Android 13 (U.I 5.1), then I unlocked the bootloader, rooted, magisk working but then I decided to downgrade from 13 to 12 because of a few things
I tried via Odin (13.14.4 and 13.12.7) and both didn't work the first odin it fails the flashing and the second pass but it didn't flash the whole thing just reset the phone
any idea? or I'm now stuck with Android 13?
Cheers
From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.
sandsofmyst said:
From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.
Click to expand...
Click to collapse
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now
biustech said:
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now
Click to expand...
Click to collapse
You could flash a GSI image, but I guess that wouldn't be OneUI anymore
Hello you all hope you're having a good day, so no 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