Hi guys! I have a galaxy s7 G930W8 (Canadian version). I've been trying to install Kali Nethunter for a couple weeks now. The only real requirement i need is Touchwiz 6.0.1. So first I tried using odin to flash the stock marshmallow firmware. Replacing the CP file usually broke my Bell service so i leave that empty and only flash the AP. But the Camera doesn't work. Next I tried Hydrarom 1.4, and again, everything working except the camera.
Right now I'm running Lineage Os, running nougat. Camera works. Same thing for stock Nougat firmware. Camera works. I guess what I'm looking for is a rom that is still being updated because hydrarom and stock marshmallow firmwares are from 2016. I heard about "Jesse's Note 7 rom for s7", but all the downloads seem to be broken. I even tried looking for the old lineage 13 but i'm unable to find that too.
Do you guys have any ideas? Rom suggestions? I enjoy the fully debloated roms without google or samsung. Thanks!
Hello,
I've a SGS7 (G930F) currently running The Galaxy Project (rooted and TWRP too, duh). I want to downgrade to stock 7.0 G930FXXS2DRDI since I'm displeased with overall performance of every 8.0 (both stock and custom) I've encountered so far. Now as I've read some threads regarding this matter I developed some doubts and questions. To be exact - would flashing stock 7.0 over my current rom (custom with 8.0 bootloader and modem) cause my phone to brick or as I've read in other threads cause problems with vibration/camera? If so could I just flash 7.0 AP, CSC and Modem and leave the 8.0 bootloader (seems silly, but I'd rather ask)?
Thank you
If you do the full flash with AP, CSC, CP and BL you shouldn't have any issues. The vibration/camera issues are usually caused by having a BL version that doesn't match your AP.
However the last 7.0 release locked phones from downgrading via Odin, I would have expected this to carry into Oreo
All you need to do is download the latest version of nougat and flash.
Well I flashed an older one - FXXS2DRAA and unfortunately it failed at Odin, after rebooting told me to use emergency option in Smartswitch. Flashed back to 8.0 no problem though.
Hi, put the fone on download again and reflash 8.0, that is all. I maked.
Hello,
I would like to downgrade a Galaxy Note Edge (N915FY) to Android Kitkat but I haven't done it in a few years. I wanted to make sure I understood everything before I made any mistakes. I saw on differents topics on XDA that Samsung was preventing to downgrade on their devices since android 5.0.1.
In this case :
Is reinstalling the bootloader of an Kitkat firmware with Odin is enough to reinstall an stock android 4.4 firmware after ?
Did you know where I can find an Android 4.4 bootloader for N915FY (can I extract it from the stock firmware) ?
Did I need to do and tick "Re-Partition" on Odin ?
If I do a re-partition, what PIT file should I use (see on sammobile.com) ? (TBLTE_EUR_OPENBTU_HIDDEN100M.pit or TBLTE_EUR_OPENBTU.pit)
What is the difference between SM-N915FY and SM-N915F, I understand that one was for the European market and the other for the international market (bootloader?, partition?, LTE frequency?) ?
Do any of you have a Kitkat full stock firmware (BL, AP, CP, CSC) region XEF ? I can't find any on Internet, all the links are dead.
Thanks a lot for your help
Feel free to answer me even if you only have part of the answer !
trucmuchebidule abc said:
Hello,
I would like to downgrade a Galaxy Note Edge (N915FY) to Android Kitkat but I haven't done it in a few years. I wanted to make sure I understood everything before I made any mistakes. I saw on differents topics on XDA that Samsung was preventing to downgrade on their devices since android 5.0.1.
In this case :
Is reinstalling the bootloader of an Kitkat firmware with Odin is enough to reinstall an stock android 4.4 firmware after ?
Did you know where I can find an Android 4.4 bootloader for N915FY (can I extract it from the stock firmware) ?
Did I need to do and tick "Re-Partition" on Odin ?
If I do a re-partition, what PIT file should I use (see on sammobile.com) ? (TBLTE_EUR_OPENBTU_HIDDEN100M.pit or TBLTE_EUR_OPENBTU.pit)
What is the difference between SM-N915FY and SM-N915F, I understand that one was for the European market and the other for the international market (bootloader?, partition?, LTE frequency?) ?
Do any of you have a Kitkat full stock firmware (BL, AP, CP, CSC) region XEF ? I can't find any on Internet, all the links are dead.
Thanks a lot for your help
Feel free to answer me even if you only have part of the answer !
Click to expand...
Click to collapse
I don't think is good idea downgrading to KK, i have try it myself flashing with odin and rooting and oll that but then KK was crashing often as it look like the phone is dying, then i have to flash LP and MM to get reed of that crashes every few minutes.
Here are all the updates for note edge. http://samsung-updates.com/device/?id=SM-N915FY flash with odin in download mode.
Alboooz said:
I don't think is good idea downgrading to KK, i have try it myself flashing with odin and rooting and oll that but then KK was crashing often as it look like the phone is dying, then i have to flash LP and MM to get reed of that crashes every few minutes.
Here are all the updates for note edge. http://samsung-updates.com/device/?id=SM-N915FY flash with odin in download mode.
Click to expand...
Click to collapse
Hello,
Thanks for your answer, I finally left the phone with the latest version of marshmallow available. What surprises me is that I only saw positive opinions on the kitkat version, since the phone works pretty well so I thought it wasn't worth the risk of downgrading.
Maybe the bugs you had come from a problem with the memory chip in your note 4, I have the impression that this often happens after a few years.
Edit: Oh! And did you have to dowgrade you bootloader before install kitkat ? I also tried to install kitkat on a defective note 4 motherboard and I had a lot of bug, but it was without repartion and with a one file firmware (I did'nt find any 4 files/repair firmware for the n915fy with android 4.4). Also an important part of link of firmware listed on samsung-update for kitkat are dead.
Hi All
my company have some reason must use S7 for Android 7.0, we purhcse new phone but found Based version is G930FXXU3ERI4, is possible roll back to OS 7.0?
If it's a G930F them yes, you just need to firmware files and can flash via Odin using a guide like https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Sammobile and Updato both host firmware files.
Stock flashes don't void warranty or anything of the like.
bakemoro said:
Hi All
my company have some reason must use S7 for Android 7.0, we purhcse new phone but found Based version is G930FXXU3ERI4, is possible roll back to OS 7.0?
Click to expand...
Click to collapse
Is not possible cause u have a last security patch U3
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