I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus
gus_zernial said:
I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus
Click to expand...
Click to collapse
Flash Stock Rom via ODIN.
Joku1981 said:
Flash Stock Rom via ODIN.
Click to expand...
Click to collapse
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus
Check this thread http://forum.xda-developers.com/showthread.php?t=3335065 I don't know if you have experience with Odin process. Google it preferably look at YouTube video, if you feel shaky on Odin concepts.
Sent from my SM-G935F using Tapatalk
gus_zernial said:
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus
Click to expand...
Click to collapse
1. "I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC." Reflash this FILE via ODIN coz you flashed wrong one and boot in it. Go to next step if doesn't work.
2. Flash Stock ROM via ODIN. SM-G935FD use the same firmwares that SM-G935F.
Careful with ODIN. Make sure you are running on the latest version, as I myself has problems using it for the Galaxy S7 Edge on an offer version
Sent from my SM-G935F using Tapatalk
maybe my question will be weird lol...how can i sofbrick a s7 g930p to be exact and then i can just unbrick flashing the U firmware? thanks.
Related
Hi,
I have a rooted Samsung Galaxy S4, with stock firmware (5.0.1, I think...) and TWRP recovery v3. I tried to flash a file, which got the phone stuck in a boot loop, and when I tried to factory reset it, I somehow accidentally tapped the 'wipe system partition' check box, too. When I tried to boot the phone again, it was stuck on the 'Samsung Galaxy S4 GT-I9505' screen, with no advance to the boot animation.
I tried to flash the stock firmware on again, with an error: "Could not find 'META-INF/com/google/android/update-binary' in the zip file." Using my own knowledge, I've narrowed it down to two options: 1. Either the firmware zip is corrupt, but I have re-downloaded the zip a good five times, and 2. There's something else that also needs to be flashed to the system partition.
I really need some help. Is there anything to do before flashing the firmware zip, and if yes, what? And, is there a good, CONFIRMED WORKING link to a Samsung Galaxy S4 GT-I9505 Stock firmware (LTE, Android 5.0.1, United Kingdom, Vodafone)?
Thanks,
hamzabil11
Firmwares aren't flashed through the recovery, but with Odin.
Firmwares also come with a tar extension. So it should be firmeare.tar
You could flash a custom rom now, or you can go to sammobile.com and download the official firmware from there and flash it with Odin.
Remeber, it has to be a tar file. Sammobile compresses them to zips, so you just extract them to get the tar file.
hamzabil11 said:
Hi,
I have a rooted Samsung Galaxy S4, with stock firmware (5.0.1, I think...) and TWRP recovery v3. I tried to flash a file, which got the phone stuck in a boot loop, and when I tried to factory reset it, I somehow accidentally tapped the 'wipe system partition' check box, too. When I tried to boot the phone again, it was stuck on the 'Samsung Galaxy S4 GT-I9505' screen, with no advance to the boot animation.
I tried to flash the stock firmware on again, with an error: "Could not find 'META-INF/com/google/android/update-binary' in the zip file." Using my own knowledge, I've narrowed it down to two options: 1. Either the firmware zip is corrupt, but I have re-downloaded the zip a good five times, and 2. There's something else that also needs to be flashed to the system partition.
I really need some help. Is there anything to do before flashing the firmware zip, and if yes, what? And, is there a good, CONFIRMED WORKING link to a Samsung Galaxy S4 GT-I9505 Stock firmware (LTE, Android 5.0.1, United Kingdom, Vodafone)?
Thanks,
hamzabil11
Click to expand...
Click to collapse
It appears that you're phone is soft-brick. You need to flash the factory stock firmware.
You can also find all the factory stock firmware for lollipop i-9505 here.
It's not soft-bricked. He just needs to flash a rom. Any rom, either custom or official, should get the phone running again.
GDReaper said:
Firmwares aren't flashed through the recovery, but with Odin.
Firmwares also come with a tar extension. So it should be firmeare.tar
You could flash a custom rom now, or you can go to sammobile.com and download the official firmware from there and flash it with Odin.
Remeber, it has to be a tar file. Sammobile compresses them to zips, so you just extract them to get the tar file.
Click to expand...
Click to collapse
Thanks a lot, I wasn't aware of this. I thought that you could just use the recovery to flash a stock OS, just like a custom OS. Never thought of using ODIN. I will check sammobile for the firmware; I'd heard of it before, just never thought of using it.
I was aware about the .tar extension though, just the websites i used gave them in .zip format.
Thanks,
hamzabil11
hamzabil11 said:
Thanks a lot, I wasn't aware of this. I thought that you could just use the recovery to flash a stock OS, just like a custom OS. Never thought of using ODIN. I will check sammobile for the firmware; I'd heard of it before, just never thought of using it.
I was aware about the .tar extension though, just the websites i used gave them in .zip format.
Thanks,
hamzabil11
Click to expand...
Click to collapse
Sammobile has slow download speeds for non-premium users. So you might as well check the link suggested by sway8966.
GDReaper said:
Sammobile has slow download speeds for non-premium users. So you might as well check the link suggested by sway8966.
Click to expand...
Click to collapse
Yeah Ok, thanks. I found out about the slow download speeds the hard way.
I've already checked the link, and it looks all good. I will try from there.
One more related question: If I flash this stock firmware, will I need to re-root the phone, and re-install TWRP recovery? Not really a problem if ido, but I would like to know in advance so I can be prepared.
Thanks,
hamzabil11
hamzabil11 said:
Yeah Ok, thanks. I found out about the slow download speeds the hard way.
I've already checked the link, but it only seems to offer Android KitKat Firmware. Since this phone is likely to be used offline all the time, I may not have the time to update it to Lollipop.
I will check out other sites, too, though.
Thanks,
hamzabil11
Click to expand...
Click to collapse
SamFirm.
Hello all,
I recently had to factory reset my phone to bring it in for a screen problem, I used SU to fully unroot & my phone has been stuck in a bootloop since. I have tried to reflash the stock rom, but Odin version 3.09 is getting stuck at setup connection, I have also tried using a .pit file but Odin get stuck at nand flash write or something similar.
I have a Galaxy s7 Edge BTU, all the files are for BTU region, I have also flashed back to stock on many galaxy S range phones. Just don't know what is going wrong.
Things I've tried
Odin 3.09
Odin 3.12.3
Different USB ports
Different USB Cables
Reinstalled USB drivers
I have used the 4 files from the stock firmware.zip
I also used a .pit file for EUR HERO2LTE_EUR_OPEN_SAMFIRM.NET.pit (Used along with the 4 firmware files)
I normally just use the 4 files on my previous phones & all was well.
Can someone please help.
EDIT: I managed to get into recovery & mount usb storage, I put a custom rom on the phone & flashed it. It fixed the partition issues & booted up, I then flashed stock everything using Odin.
You need Odin 3.11.1.
nitrous² said:
You need Odin 3.11.1.
Click to expand...
Click to collapse
Thanks for the information, I'll download it & keep it handy for after the repair to re-root.
Hi guys, to my understanding BL/CP are available in tar or zip formats and may be updated via Odin or Twrp respectively. Appreciate any advice as to differences (if any) between the two methods. TIA
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
CuBz90 said:
The only difference is that one (.zip) can be flashed via TWRP (this would mean you have a custom rom and a tripped Knox counter). The other (.tar) is signed by Samsung and can be flashed via Odin without tripping Knox.
Click to expand...
Click to collapse
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Xp3riaXpr3ss said:
I reckon this probably means it doesn't matter to flash with twrp or odin if knox is already 0x1.
Click to expand...
Click to collapse
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
CuBz90 said:
Correct. I find it easier to flash in TWRP because it's simpler to stay where I am and download the file, reboot to recovery and flash. Rather than going upstairs to my computer, downloading the file, putting phone in Download mode, opening Odin and loading the files, then connecting the phone to the computer then flashing the files.
Click to expand...
Click to collapse
True that. I only ever return to Odin to flash official firmware in the event of soft bricks with denied access to Twrp, however, was getting confused partly due to written instructions for roms requiring BL/CP to be flashed in download mode. Thanks for clearing this up. Cheers.
my current booloader is version 1...can anybody tell me how can update it to version 4? i am using s7 edge SC02H(snapdragon) japan.
thanks
Looking for the right modem and bootloader files
Hello,
I'm running Nougat on my s7 g930f it's using the tgp rom. In preparation for an oreo upgrade I atempted to flash an odin-zip file I found on LightRom's page, thinking it would give me a modem update. This was an extremely bad idea. Now my system does still boot, but I have no signal at all, my phone number, base band, IMEI, mobile network, etc all show as unknown under settings, about phone and the various status checks. Now when I atempt to go in to odin again to flash another modem update now I'm told that the atempt has failed. I'd appreciate some help. What file do I need to get the bl and the cp file? I'm running twrp 3.2.3, and i'd like my signal back.
Thanks.
Dave.
Hey,
I wanted to root my Galaxy S4 i9505 using CF-auto root. I cheked the version of my s4 i9505 which was i9505xxuhoj2, then go to https://desktop.firmware.mobi/ find my device model and exact same build (i9505xxuhoj2). I generated cf auto root file, boot phone in bootloader mode, unzip file and used odin (which was in that zip file too) to flash this generated file (using AP). Odin gives me FAIL and I cant boot my phone normally because of error during start (firmware upgrade encountered an issue please select recovery mode in kies).
So I flashed stock firmware (using Odin) with another build. This time i9505xxupqg1. Everything went well my S4 was running normally. So i decided repeated the procedure. Go to https://desktop.firmware.mobi/ and genereate cf auto file (this time for build i9505xxupqg1). I flashed the cf auto root file using odin and again it gives me FAIL.
Below screen of that FAIL:
https://imgur.com/a/SujjD
Can anyone help me with this?
Why this is happening ?
Cheers
Flash back to stock, flash twrp, flash supersu from twrp.
Thanks for reply.
I did this earlier what you said and everything was OK.
I had TWRP and Root using SU.
The problem isnt rooting itself.
The point is i wanted to tested rooting with CF-AutoRoot method.
And I'm wondering what am I doing wrong.
I did everyting correctly (exact same device model and build version) and ODIN gives me FAIL like i said above.
If Odin is failing, try a different version of Odin, a different USB cable, and different USB port.
I got the same problem with a Sprint Note Edge that I tried to root the same way. I'm currently downloading the stock firmware from sammobile.com to flash a stock ROM.
Thomass30 said:
Hey,
I wanted to root my Galaxy S4 i9505 using CF-auto root. I cheked the version of my s4 i9505 which was i9505xxuhoj2, then go to https://desktop.firmware.mobi/ find my device model and exact same build (i9505xxuhoj2). I generated cf auto root file, boot phone in bootloader mode, unzip file and used odin (which was in that zip file too) to flash this generated file (using AP). Odin gives me FAIL and I cant boot my phone normally because of error during start (firmware upgrade encountered an issue please select recovery mode in kies).
So I flashed stock firmware (using Odin) with another build. This time i9505xxupqg1. Everything went well my S4 was running normally. So i decided repeated the procedure. Go to https://desktop.firmware.mobi/ and genereate cf auto file (this time for build i9505xxupqg1). I flashed the cf auto root file using odin and again it gives me FAIL.
Below screen of that FAIL:
https://imgur.com/a/SujjD
Can anyone help me with this?
Why this is happening ?
Cheers
Click to expand...
Click to collapse
Hello
You do not need to generate a CF-AutoRoute, just google and download the original CF-AutoRoute.zip which roots ALL versions of the device, the baseband does not matter.
Ensure debugging is enabled
Place device into recovery (download)
Add device to Odin
Unzip the file, add the .md5 file to Odin and flash, job done.
Hello everybody,
I got a Samsung Galaxy S7 Edge (SM-G935F) DBT version and flashed a Custom ROM (Firmware? idk the difference).
I did that like this: youtube.com/watch?v=_1ofpLHMVvA
Unfortunately there were a few problems there, like the camera is awful now (Bad quality and other camera apps didnt made it better).
So now I want back my Stock ROM. (Yes, Unfortunately I didnt made a Backup)
But I cant get it back, neither with TWRP or with Odin.
At Odin its stops at system.img and fails than and at TWRP I guess I used the wrong Rom because is said Zip file is corrupt!.
The following Stock ROM did I use for Odin and TWRP: updato.com/firmware-archive-select-model?record=2A12F0CE03CD11E7963AFA163EE8F90B
At Odin I unziped it and added it the right way: (BL, AL, CP and CSC).
At TWRP I didnt unziped it and used it like it is.
I hope you can help me there.
I have already made the following:
Changed USB Port
Changed USB cabel
Used Smart Switch
And yes, I can still install custom roms like LineageOS and Resurrection easily via TWRP.
Greetings, Darkatzu.
bump
Darkatzu said:
bump
Click to expand...
Click to collapse
Which procedure you followed to root and install custom rom?
Sent from my S7 Edge using XDA Labs
shah22 said:
Which procedure you followed to root and install custom rom?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Is that important? I dont think so...
Darkatzu said:
Is that important? I dont think so...
Click to expand...
Click to collapse
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
shah22 said:
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I showed a Video Tutorial how I did that.
The reason why I did that, is for me: Not important.
And yes, I did OEM unlock.
shah22 said:
so you need to flash latest nougat for your country/region alongside twrp
Click to expand...
Click to collapse
So far so good.
shah22 said:
you can download latest stock firmware for your region from samfirm application or updato
Click to expand...
Click to collapse
As I did. (both)
shah22 said:
also download odin version 3.13.1, latest twrp recovery
Click to expand...
Click to collapse
Already done.
shah22 said:
super su and no verity opt encrypt from here on xda forums
Click to expand...
Click to collapse
Ok I didnt done that, but now I got I did.
shah22 said:
first check and enable oem unlock
Click to expand...
Click to collapse
Done.
shah22 said:
flash stock rom
Click to expand...
Click to collapse
Aaaand failed as I described already.
Darkatzu said:
I showed a Video Tutorial how I did that.
The reason why I did that, is for me: Not important.
And yes, I did OEM unlock.
So far so good.
As I did. (both)
Already done.
Ok I didnt done that, but now I got I did.
Done.
Aaaand failed as I described already.
Click to expand...
Click to collapse
Maybe you are using an older bootloader ? Can't say for sure whats causing it, the method you used above I think required system modifications, but you are using a march 2017 stock rom, so it looks updato don't has V2 bootloader firmwares for DBT, problems may happen when flashing an older bootloader on a newer one, it could also be your pc or other hardware problem, but in case try again and download samfirm from here : https://forum.xda-developers.com/attachment.php?attachmentid=3803841
Enter DBT as your region and model SM-G935F , it will download the latest stock available, be sure option for auto decrypt, check crc32 and binary nature are ticked.
After that check oem unlock and usb debugging is enabled and follow the steps :
1. Put phone in download mode, use original usb cable, and make sure pc usb port is working correctly. Also phone must be charged above 50%.
2. Download odin 3.13.1 from here https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Latest twrp available https://eu.dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
Latest no verity opt encrypt https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Latest stable super su https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
3. Put phone in download mode, extract the firmware downloaded above from samfirm tool and put the respective files in their boxes, use CSC and NOT HOME_CSC. Make sure no option other than F.reset time is ticked in odin options. Begin the flash procedure. After it is completed, don't reboot and place twrp zip downloaded from above in the AP tab of odin. After it is completed, stay in download mode and hold power+home+vol down to reboot from download mode and immediately switch to vol up button to boot in twrp recovery menu.
4. In twrp recovery menu, you need to swipe for system modifications or tick read only ( if you previously allowed for system modifications then you can do it again it doesn't matter, but if you previously didn't swipe for system modifications then tick read only and download systemless zip from https://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178 )
I will recommend this as you won't need to flash dm verity.
5. Now, go to wipe> format data in twrp recovery, after its done, flash super su and system less zip through twrp to get system less root if you don't want to get dm verity error hassle when flashing stock roms OR flash super su and no verity opt encrypt if you already have allowed system modifications. After that reboot. It may take sometime.
Also to note if you never allowed system modifications before in twrp, and you don't want to root either, then you can safely flash stock without flashing twrp or going through further steps.
This is what I could best explain according to my limited knowledge, if you still fail to flash stock in odin, then I am not sure it may be your pc or other hardware problem and you may need a repair box, try checking on another pc or some expert user to help. Good Luck.
These steps are only for installing stock rom back on previously rooted S7 edge devices using custom roms and for rooting a stock rom.. and only applies to SM-G935F
Sent from my S7 Edge using XDA Labs
shah22 said:
Maybe you are using an older bootloader ? Can't say for sure whats causing it, the method you used above I think required system modifications, but you are using a march 2017 stock rom, so it looks updato don't has V2 bootloader firmwares for DBT, problems may happen when flashing an older bootloader on a newer one, it could also be your pc or other hardware problem, but in case try again and download samfirm from here : https://forum.xda-developers.com/attachment.php?attachmentid=3803841
Enter DBT as your region and model SM-G935F , it will download the latest stock available, be sure option for auto decrypt, check crc32 and binary nature are ticked.
After that check oem unlock and usb debugging is enabled and follow the steps :
1. Put phone in download mode, use original usb cable, and make sure pc usb port is working correctly. Also phone must be charged above 50%.
2. Download odin 3.13.1 from here https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Latest twrp available https://eu.dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
Latest no verity opt encrypt https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Latest stable super su https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
3. Put phone in download mode, extract the firmware downloaded above from samfirm tool and put the respective files in their boxes, use CSC and NOT HOME_CSC. Make sure no option other than F.reset time is ticked in odin options. Begin the flash procedure. After it is completed, don't reboot and place twrp zip downloaded from above in the AP tab of odin. After it is completed, stay in download mode and hold power+home+vol down to reboot from download mode and immediately switch to vol up button to boot in twrp recovery menu.
4. In twrp recovery menu, you need to swipe for system modifications or tick read only ( if you previously allowed for system modifications then you can do it again it doesn't matter, but if you previously didn't swipe for system modifications then tick read only and download systemless zip from https://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178 )
I will recommend this as you won't need to flash dm verity.
5. Now, go to wipe> format data in twrp recovery, after its done, flash super su and system less zip through twrp to get system less root if you don't want to get dm verity error hassle when flashing stock roms OR flash super su and no verity opt encrypt if you already have allowed system modifications. After that reboot. It may take sometime.
Also to note if you never allowed system modifications before in twrp, and you don't want to root either, then you can safely flash stock without flashing twrp or going through further steps.
This is what I could best explain according to my limited knowledge, if you still fail to flash stock in odin, then I am not sure it may be your pc or other hardware problem and you may need a repair box, try checking on another pc or some expert user to help. Good Luck.
These steps are only for installing stock rom back on previously rooted S7 edge devices using custom roms and for rooting a stock rom.. and only applies to SM-G935F
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
As I already said: As I did. (both)
I already tried with samfire.
Same error.
Sorry I couldn't be much help. Does it always stucks in odin at system.img? Looks like its a hardware problem in your pc/usb ports or phone's usb jack. Try getting your phone checked by a repairer, flashing from another pc or changing usb cable. Also try running odin as an admin or try with an older odin version. Good Luck
Sent from my S7 Edge using XDA Labs
shah22 said:
Sorry I couldn't be much help. Does it always stucks in odin at system.img? Looks like its a hardware problem in your pc/usb ports or phone's usb jack. Try getting your phone checked by a repairer, flashing from another pc or changing usb cable. Also try running odin as an admin or try with an older odin version. Good Luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Yes it suck always at system.img!
And I can easily flash custom roms via. TWRP.
And I can flash TWRP via Odin without any errors.
Do u even read my post?
Changed USB cabel
Click to expand...
Click to collapse
And yes, I changed PC 2 and yes tryed other versions of Odin LIKE where AP is named as PDA.
Strange thing if you could flash recovery but not the stock rom, looks like you need to get it checked by a tech. But as a last resort did you tried using pit file and repartition ticked? To get the pit file extract the CSC file and you will find .pit file there, open pit tab in latest odin and select that pit file, then tick repartition box and proceed to flash with all other files selected in their respective boxes. If its still the same then I guess I can be of no more help. Cheers !
!! Warning : Using pit file is never recommended and it could brick your phone permanently if there is any power outage/usb disconnection during flashing with pit, it is used to correct file system partitions if they are changed/corrupted. Its better to outweigh benefits with potential danger. Also a pit file will erase all partitions first, then write flash data from beginning and if you again stuck at system.img when using pit file, you will be left with a permanent brick. So I will recommend to get it checked by a tech if you want stock rom that bad and don't do any risky thing with your pricey phone
Sent from my S7 Edge using XDA Labs
shah22 said:
Strange thing if you could flash recovery but not the stock rom, looks like you need to get it checked by a tech. But as a last resort did you tried using pit file and repartition ticked? To get the pit file extract the CSC file and you will find .pit file there, open pit tab in latest odin and select that pit file, then tick repartition box and proceed to flash with all other files selected in their respective boxes. If its still the same then I guess I can be of no more help. Cheers !
!! Warning : Using pit file is never recommended and it could brick your phone permanently if there is any power outage/usb disconnection during flashing with pit, it is used to correct file system partitions if they are changed/corrupted. Its better to outweigh benefits with potential danger. Also a pit file will erase all partitions first, then write flash data from beginning and if you again stuck at system.img when using pit file, you will be left with a permanent brick. So I will recommend to get it checked by a tech if you want stock rom that bad and don't do any risky thing with your pricey phone
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
A tech is 2 expensive for me.
And yes, I already did it with pit file and the whole CSC file.
#push
#push
#push
#push
Darkatzu said:
#push
Click to expand...
Click to collapse
try with chimeratool, it worked for me, l use a free license to download the firm from server and install it
#push
shah22 said:
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
hi, i used this thread to root my regular s7 from sprint, am i going to be able to just flash the latest firmware back to stock and be good to go or am i hosed?
thanks
hikouka71 said:
hi, i used this thread to root my regular s7 from sprint, am i going to be able to just flash the latest firmware back to stock and be good to go or am i hosed?
thanks
Click to expand...
Click to collapse
No, i don't think so as you already flashed engineering kernel, i won't recommend but if you already tried, do post your results ..
Sent from my S7 Edge using XDA Labs