Hi, after buying my s7 edge i rooted my device and changed my original recovery to the TWRP recovery.
After a couple of days a firmware update ( 81.74mb) showed up but i cannot install it because i no longer have the original recovery.
Is there a way to install the update with the twrp recovery or can i find somewhere my original recovery or do i have to flash the full firmware inside odin ?
you need to backup your "data" partition with TWRP, then install the last firmware with ODIN and restore the "data" partition...
contrinsan said:
Hi, after buying my s7 edge i rooted my device and changed my original recovery to the TWRP recovery.
After a couple of days a firmware update ( 81.74mb) showed up but i cannot install it because i no longer have the original recovery.
Is there a way to install the update with the twrp recovery or can i find somewhere my original recovery or do i have to flash the full firmware inside odin ?
Click to expand...
Click to collapse
Yes, Look for a app on the play store called "FlashFire"
This will allow you to flash the whole Firmware package ontop of your Current ROM.
You can overwrite or keep Data, And you can also re-install TWRP from within this app if you update your bootloader.
Very good app and of course you loose nothing.
danw84 said:
you need to backup your "data" partition with TWRP, then install the last firmware with ODIN and restore the "data" partition...
Click to expand...
Click to collapse
You dont have to do it via odin.
If your device is rooted, you already have all the power you need.
Look at a app called Flashfire in future.
Thanks Dave. That was an easy solution. At first i was stuck at the (default) recovery after flashing my firmware but i got everything working ok now. Let's hope the update was worth all the trouble
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
Hi, i have magisk root from asf3 firmware. What are the steps to upgrade to asg8? Anyone tried it? Thanks
Note: OEM unlocking @ settings>developer options> is not greyed out. Is it normal? Ok?
Can I flash immediately via odin? BL CP CSC is required? I have already patched AP via magisk from firmware from asf3.
Do i still need to wipe data via recovery after flashing?
Thanks in advance.
Yes, magisk patch the new firmware. Load it in odin, patched AP BL,CP, and Home csc. No need to wipe for updating new firnware. Only wipe if you installing TWRP for the first time
Player04 said:
Yes, magisk patch the new firmware. Load it in odin, patched AP BL,CP, and Home csc. No need to wipe for updating new firnware. Only wipe if you installing TWRP for the first time
Click to expand...
Click to collapse
Thanks, so i will just turn off the phone. Boot to download mode, flash the latest firmware and patched AP via Odin, and its ok to set auto restart and not manually restart to recovery mode and wipe?
odson56 said:
Thanks, so i will just turn off the phone. Boot to download mode, flash the latest firmware and patched AP via Odin, and its ok to set auto restart and not manually restart to recovery mode and wipe?
Click to expand...
Click to collapse
yes
Ok thank you. Done updating to ASG8 with root
and data not wiped. But I still have a broken
Playstore. Apps dont show up and i cannot update.
Will a data wipe fix this? How to wipe data if phone
Is rooted? Do i have to do it via stock recovery? Is
There any thing I have to take in consideration?
Thanks.
Hi friends;
I need your helps.
My Samsung S8 has custom Oreo rom.
-Could i flash stock Oreo rom via TWRP?
-If i can flash by this way, will bootlodder and TWRP deleted?
Thanks in advance
If you flash a modified stock ROM specially prepared for use with TWRP, then BL and TWPR will remain unchanged.
If you flash the original stock ROM (firmware) then you can only do it through Odin or Heimdall, and in that case you will lose TWPR and BL (if it was different from the existing one).
ze7zez said:
If you flash a modified stock ROM specially prepared for use with TWRP, then BL and TWPR will remain unchanged.
If you flash the original stock ROM (firmware) then you can only do it through Odin or Heimdall, and in that case you will lose TWPR and BL (if it was different from the existing one).
Click to expand...
Click to collapse
Thank you very much;
I have one more question to you.
Now bootloader is unlocked. I can flash custom roms via TWRP.
If I flash the original stock ROM (firmware) via Odin, will bootloader be locked?
After flashing you activate developer mode and re-enable unlocking if it is not already enabled.
ze7zez said:
After flashing you activate developer mode and re-enable unlocking if it is not already enabled.
Click to expand...
Click to collapse
Thank you very much.
Surely you know that your stock ROM will not have all the functionality that the original has, because you have a Knox flag violation on your phone.
ze7zez said:
Surely you know that your stock ROM will not have all the functionality that the original has, because you have a Knox flag violation on your phone.
Click to expand...
Click to collapse
I need "car mirrolink" feature.
Existing custom Oreo rom has car mirrorlink feature(in Settings-Other connections menu),
but when i connected phone to car i cant use mirrorlink apps because there is not certificates.
If I flash stock Oreo Rom via Odin, can i use car mirrorlink feature flawless?
Once in TWRP, backup to an external microSD and copy the resulting directory to another device.
Flash the original firmware and see if what you need works.
If you have problems, you can re-upload TWRP via Odin and restore a copy of the custom ROM from the microSD.
ze7zez said:
Once in TWRP, backup to an external microSD and copy the resulting directory to another device.
Flash the original firmware and see if what you need works.
If you have problems, you can re-upload TWRP via Odin and restore a copy of the custom ROM from the microSD.
Click to expand...
Click to collapse
Thank you very much.
Best regards