Problem with TWRP Recovery v3.1.1 on my Samsung SM-j701M - Samsung Galaxy J7 Questions & Answers

Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando

If you have to downgrade the boot loader, it means the firmware you are flashing is older than the one on your fon.
Go to www.updato.com and look for the he latest J701M firmware.
You can sort the list by date and by region.
And the site is download manager friendly ?
Good luck!
Sent from my SM-J700F using Tapatalk

Thanks for your answer! One more question about the region. Should I download firmware from the country that I bought the phone or firmware from the country that I am?

Look for your country specific firmware first.
Otherwise Samsung usually has regional software - i.e for several countries in a region e.g. Argentina, Paraguay.
Sent from my SM-J700F using Tapatalk

MikeEinziger said:
Hello there
I bought a Samsung J7 Neo (SM -J701M) on another country than mine (Im from Argentina, device bought on Paraguay). Anyway, I started to look another way to get some space on the internal storage and I remember that android had an option to expand it, using a SD Card. Unfortunately, i realize this option is not allowed on samsungs device, but it works (i read it, because can't do it) if you get root user.
So I looked how to do it and i found a group of files
ODIN v3.12
Magisk v.14.5
twrp v.3.1.1 -j7 neo
Im not sure if I downloaded the right files, but im start the process anyway.
I followed point by point
First I installed TWRP Recovery v3.1.1 (which is supposed to be correct to my model) and then already on twrp rom I installed magisk 14.5 from sd card and did wipe data.
Turned on the phone and I restored all apps from a google backups, and I realized I cant find app "Magisk" on the device, so I decided to reboot the phone and it starts to do a bootloop with this error "kernel rev. check fail, device:2 binary:1"
At this point, I failed every attempt to fix this error
I tried installing the last official firmware that i found (and Im not sure if its the correct one)
J701MUBU3ARC2_J701MUWT3ARC1_UFN
And I got this error
"SW REV. CHECK Fail (BOOTLOADER) Device :5 Binary 3:
I searched on google this kind of error, and I found that I have to downgrade the bootloader. And this is why im here beacause I dont know how to do this, and if its works, i don´t know how to continue the process to root and expand my internal storage. So I really appreciate if someone one could help me with this. I can learn fast and I love to do this things by myself.
Thanks for your time!
Fernando
Click to expand...
Click to collapse
@MikeEinziger
Hi There,
Did you have any luck with your Phone? I have the same exact model but I have Android Version 8.1.0, Samsung Experience version 9.5; Android security patch level -Feb 1, 2019; Baseband version: J701MUBS6BSB3 and like you, I love doing things myself, and I can't seem to abide a smartphone that's not rooted.
I'm not exactly a newbie, I've been assisting devs with testing and such on AT&T SGS3 for quite some time. But I can't seem to find a stable method for rooting for this phone, no one seems to be doing any development on it.
I would love to hear your story thus far.

im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again

Ezeka93 said:
im needing help myself, i have the SM-J701M (J7 NEO), with android pie 9 official, but the binary is 7 (because Argentina Geniuses of course) and of all the things i tried nothing works, and the only thing they did was brick the phone, so i flash and stock firmnware to be usable again
Click to expand...
Click to collapse
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.

Jemec26 said:
What have you done? I saw your messages on TG but everyone ignores usually, I had another problem and footbed the solution myself as I got ignored for days.
So, what have you done? Maybe we can figure it out a way to root it, but to avoid telling you things that you may have already done it is better if you let us know your already followed steps.
Click to expand...
Click to collapse
i tried flashing TWRP like a guide said (Latest version) but then got stuck with a boot loop in the Samsung Galaxy Logo, then when i enter to flash the latest global firmware it didn't work because it was binary 6, so i searched for the version in Argentina that has binary 7, after that i didn't try anything else in fears of getting fully bricked, i was thinking of the magisk canary way of rooting (patching the AP) but i don't know what happen if it fails the flash

Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?

Some success.
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also I'm from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
iKmaster01 said:
Hi, i have the same device, SM-J701M, but when i try to flash the stock, it says that the device binary is 9 and the rom is 8, but i cant find the binary 9 rom in any place, only 8. I have the trwp installed, so I was thinking if I format all data (system and files) and try to flash again, it will work ?
Also im from Brazil (SM-J701MT), and the device was buyed in Paraguay (SM-J701M) too. Should i install the SM-J701MT ROM right ?
Click to expand...
Click to collapse
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.

CoperaN said:
Ok, guys, I've had a bit of progress with my device Samsung Galaxy J 7 Neo (SM-J701M- Android version 8.01)
On this phone, the option to unlock the bootloader was missing in Dev Opt and I knew that in order to achieve anything I was going to have to unlock the bootloader.
I searched and found that, via adb/fastboot (Google's Platform Tools) rebooting the phone to the bootloader you could enter the code: 'fastboot oem unlock' or 'fastboot flashing unlock' and voila! everything would be fixed...But...my device wasn't even being recognized by "fastboot" ! adb yes but no fastboot! Always the message: "Waiting on any device". Trying to find and install the drivers to do this was next to impossible.
It actually caused me soft brick my device. However, it was a blessing in disguise; I knew what had to be done, I was going to have to reinstall the firmware via Odin. I searched the site (Sammobile - you'll have to create an account.) and found the Oreo and the Pie Firmware, I downloaded both but played it safe and restored my device with the Oreo first.
And lo and behold the option to unlock bootloader was there! No hesitation, clicked that sucker fast!!
Now, I'm running PIE (No one has done a Custom ROM for this baby just yet) and with the unofficial TWRP in the first link below, it's a bit buggy but until they make an official one for us ... I guess we'll have to wait.
Oh! And don't forget to make a backup with Smart Switch!
And pay attention to the advice here:
Code:
1. Extract the firmware file you just downloaded. You should get 5 files:
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC_*** (Country / Region / Operator)
HOME_CSC_*** (Country / Region / Operator)
2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data.
3. Reboot your phone in Download / Odin mode (make sure your device is off) with the following button combo: POWER + VOLUME DOWN + BIXBY
Other options in case first option did not work or isn't possible.
Option 2 VOLUME DOWN + VOLUME UP then USB cable
Option 3 POWER + VOLUME DOWN + VOLUME UP
Option 4 POWER + VOLUME DOWN + HOME BUTTON
Option 5 (Note9) USB cable + VOLUME DOWN + BIXBY
Option 6 (Note10) POWER + VOLUME UP
4. Once in download mode, connect your phone to the PC, preferably using the original USB cable you got with your phone. Odin should detect your device and a BLUE box will show up with the COM port number. (Be sure, the SAMSUNG-drivers are installed on your PC!)
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
5. Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC
These are some of the links I found helpful:
https://unofficialtwrp.com/root-twrp-galaxy-j7-neo-sm-j701m/
https://www.androidexplained.com/galaxy-note-9-restore-firmware/
https://forum.xda-developers.com/galaxy-j7/samsung-galaxy-j7-prime--j7-on-nxt-exynos7870/recovery-twrp-3-2-0-galaxy-j7-prime-t3716355
---------- Post added at 01:39 PM ---------- Previous post was at 01:30 PM ----------
I think that's because you have to be specific with the carrier; Orange; Nextel; Movistar...that makes a lot of difference in with the firmware. If you can, check to see what you had before and try that first.
Click to expand...
Click to collapse
Hey, I noticed we have the same android version and and phone model, I wanted to know which version of Twrp you used . I am guessing version 3.1.1?

It's an Un-official version of TWRP, so the version #( 3.2.1-0) may not count, you can check the links out to get more information.

hola tengo un problema, tengo un sm-j701m binario 11 android 9 y quiero intalarle un twrp pero no se cual descargar y que funcione

Don't know if anyone's still following this thread or even still has this phone but there's been quite some progress with this device. (i.e: SM-J701M) The posts below will certainly help to bring your device up to date re: rooting; flashing etc.
https://forum.xda-developers.com/t/...or-galaxy-j7-nxt-neo-core-10-08-2021.4222703/
https://forum.xda-developers.com/t/...laxy-j7-nxt-neo-core-j701-02-02-2021.4227921/
These posts contain links to ROMS and recoveries which have been sucessful, I can personally attest to this, my device was rooted and a custom ROM installed. I hope you will find them helpful.
Good Luck

Related

Developer Edition S5-Do's and Don'ts

So you have decided, or maybe trying to decide, to invest a good chunk of money into a Developer Edition S5 instead of a retail version. Here are a few tips and general information that you need to know before you start to "tinker" with the Developer Edition S5:
1) The Developer Edition S5 can only be obtained from the Samsung online store (site). When you receive the S5 you should understand that it is going to look, feel and perform exactly like the retail version of the S5. The only way you can tell the difference is to pull the battery and look for the words "Developer Device" printed on the S5's board under the battery. You will have all the bloat etc that a retail version has. The only difference is that your bootloader, unlike the retail version, is unlocked. The phone will come with the latest version of Android that Samsung currently supports...the same version as the retail S5.
2) After your initial boot, and before you do anything else, go to settings>security and disable (uncheck) the Reactivation Lock. If you don't do that before "tinkering" with your phone you stand a very good chance of successfully bricking your phone while flashing a recovery or rooting your phone. Next go to About Phone>Build Number and tap it about 6-7 times and enable Developer Option and then enable USB Debugging.
3)A word of advice: Never, never take an OTA update. If you do, you stand a real good chance of locking your bootloader. Samsung has never released a OTA update specifically for their Developer Edition phones. Allowing a retail OTA update to download and install on you Developer Edition will most likely lock your bootloader for good. Sending it back to Samsung will not help you. They will not unlock your phone, and you cannot unlock your phone. You are stuck with a very expensive retail version of the S5. Keeping the Developer Edition up to date is not a problem. Our developer community does a great job taking the latest updates and creating ROMs that are safe to flash on our devices. It may take them a day or two, but it happens.
4) Installing a custom recovery...the first step: First, download and install the latest Samsung drivers on you PC. Then download and install on your PC the latest version of ODIN. Version 3.07 also works if that is what you already have. I recommend TWRP as the best custom recovery to use. Download the latest version of TWRP and place it on you PC. Start ODIN. Power off your phone and then holding down the volume down - button and the power button boot into Download Mode. Once in Download Mode connect your phone to your PC using the supplied USB/charging cable. Wait for ODIN to recognize your phone (phone info will appear in the ID:COM window in ODIN). In the Message window in ODIN find the TWRP .tar you downloaded and highlight it with your cursor. Select the PDA block in ODIN. Now select start. Allow ODIN to do its thing. Do not disconnect your phone until you get the Green Pass notification in ODIN. Disconnect your phone and reboot. You now have a custom recovery installed. NOW DO A BACKUP using your TWRP recovery. Do it right now!!
5)Rooting: After installing a custom recovery (TWRP), download the latest version of SuperSU and place it in your internal storage or external sdcard. Boot your phone into Recovery, wipe cache and delvek, you can also do a Factory Reset if you choose, then select install, find the SuperSU .zip, and flash it. Reboot. Now you are rooted. You can confirm (recommended) that you are rooted by installing Root Checker from the Play Store and running it.
6). OK, you have a custom recovery and rooted. You can now take advantage of the benefits of an unlocked bootloader. There are a number of good ROMs you can flash in the Android Development Section. Caution...Do not flash a ROM that says "Retail". Most developers will say whether it is safe for Developer Phones. There are also some AOSP ROMs that are "Works In Progress" in the Unified Section. You can flash those, but they are not quite ready for prime time yet.
7) Just a reminder: Do not take an OTA. Do not flash Retail Firmware.
Thanks!
Been reading and reading, and reading some more to learn all I can about my Developer Edition. Appreciate this post, and the concise information. :good:
ruh roh
I had S5 dev edish for 2+ years with TWRP + rooted 4.4.2, and life was great. Then when I went to sell it I thought I would update it first to 6.0.1.
1.) Was that a horrible mistake??
2.) If I locked the bootloader by flashing stock 6.0.1, how can I confirm this?
3.) Is my only option to have Samsung revert/unlock the phone to 4.4.2? Or can I root 6.0.1?
4.) If you were selling it on ebay, I assume it's more valuable as 4.4.2 root/unlock than dumb retail 6.0.1?
P.S. I've spent over an hour trying to find these answers myself.
If you have a dev ed then it shouldn't lock the bootloader even if you go to MM.
It's not really worth more one way or the other unless someone is looking for a device already rooted, ready to go.
To check if locked:
Power off
Hold home button, down volume button, and power together
At warning screen, press up volume button
On "Downloading" screen - look to see if it says "Mode: Developer"
(If it does, you're unlocked)
If you're locked, I believe you can just go back to Lollipop, root, and unlock again using this thread:
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Add this to the list - BACK UP YOUR ABOOT AND PUT IT IN A SAFE PLACE

G930F locked on Combination firmware

Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Try to connect with smart switch.
On windows pc or laptop
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
It will flash stock firmware and solve all binary problem
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Intall smart connect or smart switch in pc
Sent from my [device_name] using XDA-Developers Legacy app
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Flash latest stock firmware for your region and enable OEM unlock in developer settings to avoid FRP in future. Also try to remember your google account password :silly:
Solved. I flash the latest firmware with an old version of odin
frp lock
marcoar said:
Solved. I flash the latest firmware with an old version of odin
Click to expand...
Click to collapse
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
kira31390 said:
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
Click to expand...
Click to collapse
Odin 3.12.5
Firmware: fxxu2drb6
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Matty1993 said:
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Click to expand...
Click to collapse
after the combination file flash, the phone normally starts with the combination firmware
marcoar said:
after the combination file flash, the phone normally starts with the combination firmware
Click to expand...
Click to collapse
Thanks so much for the reply i appreciate it i might try my combination file with the G930FXXU2DRB6 firmware you used as i need to test my hardware and fix imei but cant get the factory binary to boot on G930FXXU2DRBE firmware my thinking that it wouldnt boot was as its FA60 is android 6.0 MM where as my U2DRBE firmware is FA70 7.0 nougat is your device nougat or marshmallow ? Just trying to work out whats going wrong where for it to not boot on my device as ive lost my imei number flashing a custom rom and dont have access to my TWRP back up for another 3 weeks
Thanks
Hello. I have a similar problem. I have the latest firmware on it: G930FXXS2DRDI There are no ways to lift the Google lock. I have tried everything possible: Bluetooth does not work, Talkback, Realterm, etc. Please for help
My Android Version is: 7.0 (Nougat)
Frp g930fxxu2ara1
Hello my friend, i have this problem too. Have you a fix? this security patch for FRP is incredible....
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
ATRAC3, do you have the combination files and firmware for the SAMSUNG S7 SM-G930FD please and thank you for your wonderful tutorial here.
my odin(tried on v3.12.5/v3.12.7/v3.13.1 ) keep failing while flashing HOME_CSC but will success with CSC, and still required to login google account, what is the issue here ? (are we supposed to insert the pit file by ATRAC3 ? )
flashing at the lastest FW G930FXXS2DRCE
phone version:SM-G930F
ATRAC3 said:
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
Click to expand...
Click to collapse
Hi mate ive used the G930FXXU2DRBE XSA Firmware and also G930FXXU2DRB6 firmware with the G930FXXU2ARA2 combination rom however it will not boot past the samsung logo the nad passes and is provisioned in top left corner and when plugged into the computer comes online with ADB bypass flasher but it just sits there even if i do a cache wipe and factory reset it comes up with a tango console error or something like that when reset then reboots back to samsung logo and when re installing firmware HOME-CSC will fail every time the only thing ive been able to put it down to is that (1) the firmware is FA_70 which is nougat OS and the combination rom is FA_60 MM or (2) my knox warranty bit is tripped and will not allow a samsung factory binary to be run on it, may i ask what would be the difference with the firmware you have listed to the firmware im already using with the combination rom ? Need to sort my imei number out with the factory nad asap dont have access to my TWRP backup for another week and a half, if it helps my device is not FRP locked and is oem unlocked.
Thanks
Matthew
P.S to all those whom have a bit 2 bootloader on S7 all the loopholes have been patched the only way is to use the combination files ive been through absolutely everything and tried everything this new bootloader update is impenetrable i can google unlock samsung S8 and S9 no dramas and with S9 the OEM lock option dissapears for a week if tampered with but still 15 minutes and its done this **** but got me goin loco holmes !!!!! Maybe they figured this out also as there is only bit 1 bootloaders for both the S8 and the S9 however with S8 i found a stock firmware that allows another way to unlock the device without the need to flash any combination rom.
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
LEVY P said:
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
Click to expand...
Click to collapse
If it gets stuck on the console error and wont reboot to download mode then hold the power button volume down button and power button for 40 seconds and it will re boot to download mode for stock firmware re installation in short basically no theres way to remove the FRP unless you can get the combination rom to boot which from what ive seen some will boot the binary but then it also depends if HOME_CSC will flash to keep usb debugging enabled to use adb bypass program im now using the new G930FXXU2ERE2 8.0 OREO so I've given up on the binary 2 nougat FRP unlocking for now might be best to wait a while for someone to receive a factory binary on the nougat or oreo when sent off and returned so it can be dumped and built into a flashable rom until then not much can be done and i may have to wait another week and a half for my EFS backup :'(
We will be waiting from u for the new combination file when out bro, our hope are hinged on u!
No one is coming up with any method about the bootloader binary 2 for the Samsung S7 G930FD...?
Sent from my SM-G930F using Xposed Modules
FRP can be done so easy from any GSM tool by combination, anyone need it it will be my pleasure to help

[Guide] How to downgrade from Android Oreo 8.0 to 7.0 (Non-rooted)

How to downgrade a non-rooted S7 Edge from Android Oreo 8.0 to 7.0 and keeping your Knox 0x0!
So if some of you are looking for a 'how-to' guide, look no further! ​(I believe it works on your S7 too, but make sure you have downloaded the correct firmware)​
*IMPORTANT*
-I don't take ANY responsibility if you bricked your device during the flash!
-Follow the guide below before flashing your official firmware using Odin!
On the phone
-Sign-out any accounts on settings
-Have OEM-unlock & USB Debugging ON (developer options)
-*optional task, just in case* Screenshot your device information on the settings tab (IMEI, Baseband, Software Info, Model number)
-*optional task, just in case* Backup your device using Samsung SmartSwitch software
Things to download
-For this guide I used Odin v3.13.1 https://dl.sammobile.com/Odin3-v3.13.1.zip
-You can install the Samsung driver using SmartSwitch if your Win PC can't detect your Samsung phone (it should show on Device Manager > Modem > something like Samsung Modem)
-*READ* You can't flash back to version 6.0 now because of (Android Oreo 8.0 is using different version of boot-loader) but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2, so binary v1 it will be conflicted and won't work upon flash.
-*NOTE* Download the correct firmware of your phone model by following the baseband, that's why I recommended to take screenshots of your phone, you can search it on here https://www.sammobile.com/firmwares/, for mine, I've searched SM-G935F and BTU is my choice, the filtered results should be your correct firmware. But in my case I used (v7.0 in March 2018) because it has the binary boot-loader v2 with it (whatever it called, it's important otherwise it will not work which I've tried)
-*optional*, if you find sammobile download speed is way too slow* You can use https://updato.com/firmware-archive-select-model?q=SM-G935F&exact=1&r=&v=Nougat%28Android+7.0%29%2COreo%28Android+8.0.0%29&rpp=100, and basically look for the correct firmware which I have mentioned above.
-Extract your firmware onto a single folder, don't mess them up! (you should see something like AP_G935blahblahblah.md5, and you will need AP_, BL_, CP_, CSC_ for downgrading)
Follow the steps:
1. Now you have the correct firmware and Odin running on Admin right
2. On Odin you can add AP_, BL_, CP_ & CSC_ onto the correct selection, for example: https://i.imgur.com/DIB2d1S.png
3. Have your phone on Download mode, google it if you don't know how (make sure you followed the On the phone step first, it's very important)
4. Find a data USB cable and plug into USB2.0 port, make sure your phone appeared on Odin (you will see something like 0:[COM5])
5. On Odin (only Auto Reboot, F. Reset Time) is needed, it should be ticked by default.
6. Now you can safely click 'Start' on Odin.
7. DO NOT TOUCH YOUR PHONE in case your USB is loose which I had experience before.
8. Wait until it shows a green PASS! like this: https://i.imgur.com/FYosmx2.png
9. When see a blue screen with Erasing text on it, please wait until it reboot and hold (Volume UP + Home Button + Power Button) boot to recovery mode
10. Wipe cache partition, and data/factory reset then reboot system now
11. Wait for it to boot into your sweet sweet Android Nougat 7.0 (Late version)
12. Disable auto-update if you wish, mine was on auto-update so I had to pause it half-way
Hope you find this guide helpful, I tried to remember the steps on my head as I typed, (*sorry for the grammar if you find it hard to understand) and if you think I've missed something here, let me know! I would update the guide if any step is missing, just in case
Thanks
I'm guessing Knox counter wouldn't have incremented?
ZionMainframe said:
Thanks
I'm guessing Knox counter wouldn't have incremented?
Click to expand...
Click to collapse
No, not at all, if you are using the official firmware! Just follow the guide closely
Please help me downgrade from G935FXXS3ERHD to G935FXXU2DRAG.
I tried nand TWRP BL restore, BL and stock firmware flash in Odin. Nothing works.
Edit:
I found a solution, see: Original post
but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2
can you upload the bootloader?
How to know each android 7.0 bootloader is V2?
Now with the lattest update the binary changed to 3 then i cant downgrade to Nougat
(Im spanish)
Oreo to nougat
I have a s7 edge with the Data firmware Version 2018/09/18 8.0.0
PDA: G935FXXS3ERHD
CSC: G935FITV3ERG2
is it possible to downgrade from oreo to nougat? I have the battery that you always download
I tried but doesn't work
Hello dear!
I have a S7 edge SM-G935T and I tried to flash the last version of Nougat 7, but doesn't work. Odin don't let me finish the process. Maybe you wrote this thread before my cellphone received the last update of Oreo.
Do you have any solution in this case. I really appreciate it.
King regards, _/\_
Unfortunately the bootloader was updated in last updates, now the bootloader is version 3 as the phone said to me when i tried to flash the last version of Nougat.
i have stupid question but, i have R16NW.SM-G930FXXS3ERKE (oreo) but i think im not supposed download this(G930FXXS3ERKE) if i want downgrade to nougat but rather (G930FXXS2DRC3) because the first firmware i mentioned get me oreo again.... am I right??? i don t wont screw things up....
TheLoller221 said:
Unfortunately the bootloader was updated in last updates, now the bootloader is version 3 as the phone said to me when i tried to flash the last version of Nougat.
Click to expand...
Click to collapse
YES, the Guide is NOT working ANYMORE...
Does this work still
Help with G930A
Hello um I have a Samsung Galaxy S7 on AT&T (G939A) and it's on 8.0 (G930AUCS9CSB1). I've tried to root it but after some research I've come to find out I have to downgrade it to nougat to root it. But the problem is everytime I load a firmware it fails and I did more research I think it said something about the bootloader blocking it and the only way to downgrade the bootloader is downgrading the firmware which I can't do because of that cycle. Can someone please help me all I want to do is root install a custom recovery and a custom rom I love playing around with android tweaks but I can't get it because of this. I hope someone can help me please and thank you.
freshair4552 said:
I have a Samsung Galaxy S7 on AT&T (G939A) and it's on 8.0 (G930AUCS9CSB1)...
Can someone please help me all I want to do is root install a custom recovery and a custom rom...
Click to expand...
Click to collapse
Your bootloader cannot be unlocked due to it being Snapdragon, so unfortunately there is nothing you can do. Only Exynos variants can be modified.
Hello guys,I have a problem with my galaxy s7 sm-g935f(Exynos version).Few months ago I flashed my phone from android Nougat SEE CSC(South East Europe) to UK's Oreo BTU CSC.I'm curious is there any other way to downgrade it from oreo to nougat,otherwise than Odin.I tried flashing it a few times with the latest Odin version (3.13.3) and nougat SEE CSC(South East Europe) because that's my original CSC.Odin recognizes the device normally,but when i click start,it comes to setup connection and then FAIL.The reason I'm trying to downgrade is very poor battery life and heating,and the phone is very laggy.I even tried through Samsung Smart Switch Emergency software recovery but it seems that Samsung has restricted that option...please help if anyone has/had similar problem.Thank you!
Mine is Sprint g935pvpsbcta1
Am I screwed also?
Hi, I have
SM-G935F​and I can't find any nougat firmware with baseband of: G935FXXS8ETCA.. Can I flash any country / baseband 7.0 firmware? And will it improve the SOT? I'm currently getting upto 5 hours SOT.
lovetv said:
How to downgrade a non-rooted S7 Edge from Android Oreo 8.0 to 7.0 and keeping your Knox 0x0!
So if some of you are looking for a 'how-to' guide, look no further!
(I believe it works on your S7 too, but make sure you have downloaded the correct firmware)​
*IMPORTANT*
-I don't take ANY responsibility if you bricked your device during the flash!
-Follow the guide below before flashing your official firmware using Odin!
On the phone
-Sign-out any accounts on settings
-Have OEM-unlock & USB Debugging ON (developer options)
-*optional task, just in case* Screenshot your device information on the settings tab (IMEI, Baseband, Software Info, Model number)
-*optional task, just in case* Backup your device using Samsung SmartSwitch software
Things to download
-For this guide I used Odin v3.13.1 https://dl.sammobile.com/Odin3-v3.13.1.zip
-You can install the Samsung driver using SmartSwitch if your Win PC can't detect your Samsung phone (it should show on Device Manager > Modem > something like Samsung Modem)
-*READ* You can't flash back to version 6.0 now because of (Android Oreo 8.0 is using different version of boot-loader) but there are some late Android 7.0 with updated boot-loader, those are using boot-loader binary v2, so binary v1 it will be conflicted and won't work upon flash.
-*NOTE* Download the correct firmware of your phone model by following the baseband, that's why I recommended to take screenshots of your phone, you can search it on here https://www.sammobile.com/firmwares/, for mine, I've searched SM-G935F and BTU is my choice, the filtered results should be your correct firmware. But in my case I used (v7.0 in March 2018) because it has the binary boot-loader v2 with it (whatever it called, it's important otherwise it will not work which I've tried)
-*optional*, if you find sammobile download speed is way too slow* You can use https://updato.com/firmware-archive-select-model?q=SM-G935F&exact=1&r=&v=Nougat%28Android+7.0%29%2COreo%28Android+8.0.0%29&rpp=100, and basically look for the correct firmware which I have mentioned above.
-Extract your firmware onto a single folder, don't mess them up! (you should see something like AP_G935blahblahblah.md5, and you will need AP_, BL_, CP_, CSC_ for downgrading)
Follow the steps:
1. Now you have the correct firmware and Odin running on Admin right
2. On Odin you can add AP_, BL_, CP_ & CSC_ onto the correct selection, for example:
https://imgur.com/DIB2d1S
3. Have your phone on Download mode, google it if you don't know how (make sure you followed the On the phone step first, it's very important)
4. Find a data USB cable and plug into USB2.0 port, make sure your phone appeared on Odin (you will see something like 0:[COM5])
5. On Odin (only Auto Reboot, F. Reset Time) is needed, it should be ticked by default.
6. Now you can safely click 'Start' on Odin.
7. DO NOT TOUCH YOUR PHONE in case your USB is loose which I had experience before.
8. Wait until it shows a green PASS! like this:
https://imgur.com/FYosmx2
9. When see a blue screen with Erasing text on it, please wait until it reboot and hold (Volume UP + Home Button + Power Button) boot to recovery mode
10. Wipe cache partition, and data/factory reset then reboot system now
11. Wait for it to boot into your sweet sweet Android Nougat 7.0 (Late version)
12. Disable auto-update if you wish, mine was on auto-update so I had to pause it half-way
Hope you find this guide helpful, I tried to remember the steps on my head as I typed, (*sorry for the grammar if you find it hard to understand) and if you think I've missed something here, let me know! I would update the guide if any step is missing, just in case
Click to expand...
Click to collapse
I just wonder this solution will be work as well? my phone is s6 edge plus G928C.
And i want to downgrade to 5.1.1 or 6.0 because 7.0 was really terrible.

Someone HELP!!!

Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number

How to really downgrade Galaxy S6 SM-G920F firmware from 7.0 to 5.0.2/5.1.1/6.0.1?

Hello
I've been reading forums and downloading files for days. Many of the links in the posts no longer work. Posts are 5 years and older. There are no new ones. At least not one that actually works. Downgrade I mean. That's why I wrote this question and I'm asking for help - how to really downgrade my Galaxy S6 G920F.
Thanks for the help.
PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.

			
				
I'm laughing because you write quite a lot in three days. Of course, this method does not work.
Is there anyone willing to help?
Totesnochill said:
PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.
Click to expand...
Click to collapse
That is assuming they have TWRP.
Also, the part you mention about "boot into download mode, connect to PC then boot to TWRP via fastboot" is not correct because Samsung is not compatible with fastboot, adb works but fastboot does not. Some Samsung devices technically have a "fastboot mode" but it isn't functional, it doesn't respond to fastboot commands, it's basically useless.
Also, you can't flash a firmware that has a lower binary than the currently installed firmware so if the binary of the downgraded firmware is lower than the binary of the currently installed firmware, the downgraded firmware can't be flashed.
Samsung is making it harder and harder to downgrade their devices.
OK. I'm afraid I'm missing the point of what's being said.
I know it is possible and there are also posts about it, but they are old, the links in them do not work. I'm asking for an expert who knows how to do this, philosophizing about what it would be like if it somehow doesn't really help me and I'm not interested either
I'm only interested in a positive thought, help and not brainstorming, if you understand me?
No offense

Categories

Resources