Database Users

How to revert back to the stock firmware?

Hi All,
A couple of days back, I installed custom ROM (Recreated Remix Leopard) successfully on Zenfone 5. I was on the stock lollipop 3.24.40.87 firmware before that. I rooted, unlocked Bootloader and installed TWRP recovery on the stock ROM and I also took a nandroid backup. After using the custom ROM, I decided to go back to the stock ROM. I used the nandroid backup for restoring and got the stock ROM. But, now I want to go back to the stock Kitkat ROM (as the lollipop sucks) and I also don't want the custom recovery or anything. In short, I want to revert my phone to the real factory condition.
I tried to go back to Kitkat by the ASUS official method. But that didn't work. Then I tried to re-lock the Bootloader with the tool from which I unlocked it. But when I did that, I got stuck on the USB logo screen. So, I unlocked it again with the same tool and the phone starts normally. So, how do I get back now?
What would happen if I flash the stock ROM via TWRP? Will it remove the custom recovery and lock the Bootloader?
I read a couple of articles, a few of them suggested to install the stock ROM with the official ASUS method (copy the files in internal storage and the phone will notify to install the update). The article even says that by this method any custom modifications (recovery, root, Bootloader) will be deleted. Is it true or will this work?
Thanks in advance!

mohit12345 said:
Hi All,
A couple of days back, I installed custom ROM (Recreated Remix Leopard) successfully on Zenfone 5. I was on the stock lollipop 3.24.40.87 firmware before that. I rooted, unlocked Bootloader and installed TWRP recovery on the stock ROM and I also took a nandroid backup. After using the custom ROM, I decided to go back to the stock ROM. I used the nandroid backup for restoring and got the stock ROM. But, now I want to go back to the stock Kitkat ROM (as the lollipop sucks) and I also don't want the custom recovery or anything. In short, I want to revert my phone to the real factory condition.
I tried to go back to Kitkat by the ASUS official method. But that didn't work. Then I tried to re-lock the Bootloader with the tool from which I unlocked it. But when I did that, I got stuck on the USB logo screen. So, I unlocked it again with the same tool and the phone starts normally. So, how do I get back now?
What would happen if I flash the stock ROM via TWRP? Will it remove the custom recovery and lock the Bootloader?
I read a couple of articles, a few of them suggested to install the stock ROM with the official ASUS method (copy the files in internal storage and the phone will notify to install the update). The article even says that by this method any custom modifications (recovery, root, Bootloader) will be deleted. Is it true or will this work?
Thanks in advance!
Click to expand...
Click to collapse
Link rom WW 3.24.40.87 modded, flash via TWRP: drive.google.com/open?id=0B7Py5ad2aHwKMHRsZ1NJM0tfLTQ
If you flash this rom, it will not remove the custom recovery + lock the Bootloader
If you having a problem while flashing this rom, you need to flash stock recovery 2.22.40.54, after that you can sideload stock rom via ADB
Sorry for my bad english ^^

Long Çhïvaš said:
Link rom WW 3.24.40.87 modded, flash via TWRP: drive.google.com/open?id=0B7Py5ad2aHwKMHRsZ1NJM0tfLTQ
If you flash this rom, it will not remove the custom recovery + lock the Bootloader
If you having a problem while flashing this rom, you need to flash stock recovery 2.22.40.54, after that you can sideload stock rom via ADB
Sorry for my bad english ^^
Click to expand...
Click to collapse
Hi, thank you for the reply
You said WW 3.24.40.87 modded, do you mean that this rom is not the official one? Does it improves the battery life and other bugs of the stock rom?
I really appreciate your help!

You cannot flash stock rom via TWRP!
This is modded rom, so you can flash it via TWRP easily....
It's Official rom from Asus, just modded to be able flash through TWRP

Long Çhïvaš said:
You cannot flash stock rom via TWRP!
This is modded rom, so you can flash it via TWRP easily....
It's Official rom from Asus, just modded to be able flash through TWRP
Click to expand...
Click to collapse
Thank you for the info
But the thing is that I am already on the stock 3.24.40.87 rom and I want to go back to Kitkat 2.22.40.54 because it has much more improved battery performance than the lollipop. Is there any modded version of the stock Kitkat rom too? Or how do I go back to it?

mohit12345 said:
Thank you for the info
But the thing is that I am already on the stock 3.24.40.87 rom and I want to go back to Kitkat 2.22.40.54 because it has much more improved battery performance than the lollipop. Is there any modded version of the stock Kitkat rom too? Or how do I go back to it?
Click to expand...
Click to collapse
You need to flash WW 2.22.40.54 recovery via Fastboot first, then sideload rom via adb
drive.google.com/folderview?id=0B1-5RXbzbyk7UmZjZktPcHBTQ3c&usp=sharing

hi, i installed your mod ("UL-ASUS_T00F-WW-3.24.40.87-user-mod")
and now i want downgrade to kitkat because i still have no signal, before that i had 6.0.1
when i copy official rom to internal storage nothing happen.. twrp same.. how to install official rom?

Long Çhïvaš said:
Link rom WW 3.24.40.87 modded, flash via TWRP: drive.google.com/open?id=0B7Py5ad2aHwKMHRsZ1NJM0tfLTQ
If you flash this rom, it will not remove the custom recovery + lock the Bootloader
If you having a problem while flashing this rom, you need to flash stock recovery 2.22.40.54, after that you can sideload stock rom via ADB
Sorry for my bad english ^^
Click to expand...
Click to collapse
Do i have to install gapps too????

mohit12345 said:
Thank you for the info
But the thing is that I am already on the stock 3.24.40.87 rom and I want to go back to Kitkat 2.22.40.54 because it has much more improved battery performance than the lollipop. Is there any modded version of the stock Kitkat rom too? Or how do I go back to it?
Click to expand...
Click to collapse
how do i go back to 3.24.40.87? can u help me? now i'm in 6.0.1. And the bad thing is i didn't have a backup of 3.24.40.87 like u say on the first thread. Have a bug for can't playing video is too disturb me :crying:
Please contact me by email ([email protected]) :fingers-crossed:

SM-G900F STOCK ROM, please help

Hi,
I have been using RR for quite a while now, but lately I am having several troubles and I'd like to go back to the stock version, now that MM is available on S5 officially.
Is it possible? What is the best way to do so? Can I use TWRP to update the rom instead of odin?

nig3d said:
Hi,
I have been using RR for quite a while now, but lately I am having several troubles and I'd like to go back to the stock version, now that MM is available on S5 officially.
Is it possible? What is the best way to do so? Can I use TWRP to update the rom instead of odin?
Click to expand...
Click to collapse
Yes it's possible, just download your official stock rom from sammobile, then extract the tar.md5 file from the zip and flash via odin. 1 point I will say is do a factory reset via twrp first as it's a clean fresh start. Once phone is done reboot to recovery and do another factory reset vis stock recovery. Then reboot and enjoy. I personally went backwards and went back to kk
Sent from my SM-G900F

jimbomodder said:
Yes it's possible, just download your official stock rom from sammobile, then extract the tar.md5 file from the zip and flash via odin. 1 point I will say is do a factory reset via twrp first as it's a clean fresh start. Once phone is done reboot to recovery and do another factory reset vis stock recovery. Then reboot and enjoy. I personally went backwards and went back to kk
Sent from my SM-G900F
Click to expand...
Click to collapse
thanks, why is it Odin needed? Cannot be flashed like another rom using TWRP?
Also, I need to register to sammobile, I guess there is not alternative, right?

nig3d said:
thanks, why is it Odin needed? Cannot be flashed like another rom using TWRP?
Also, I need to register to sammobile, I guess there is not alternative, right?
Click to expand...
Click to collapse
Because it's the official software and unmodified Samsung firmwares must be flash via odin. Plus it's the safest way to get stock back. If u can find a stock MM rom that's already been tweaked and made into a zip u can but modems and bootloader's (which come in official firmwares) can only be flashed via odin. It'll take around 30-50 mind to download on pc, are you wanting unbranded UK firmware? If so give me 20 mind to upload it

nig3d said:
thanks, why is it Odin needed? Cannot be flashed like another rom using TWRP?
Also, I need to register to sammobile, I guess there is not alternative, right?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=106857
Sent from my SM-G900F

jimbomodder said:
Because it's the official software and unmodified Samsung firmwares must be flash via odin. Plus it's the safest way to get stock back. If u can find a stock MM rom that's already been tweaked and made into a zip u can but modems and bootloader's (which come in official firmwares) can only be flashed via odin. It'll take around 30-50 mind to download on pc, are you wanting unbranded UK firmware? If so give me 20 mind to upload it
Click to expand...
Click to collapse
Thanks, I don't remember much since the last time I used odin. I will look up for the instruction. I have just another question, I guess in doing so I will loose the TWRP boot. Is that right? If so, how am I supposed to backup and restore the data?

nig3d said:
Thanks, I don't remember much since the last time I used odin. I will look up for the instruction. I have just another question, I guess in doing so I will loose the TWRP boot. Is that right? If so, how am I supposed to backup and restore the data?
Click to expand...
Click to collapse
Do a backup first and store on ext sd card, no if card do backup and move to pc, then once flashed stock just re-root and flash twrp again and then u can restore your backup.

jimbomodder said:
Do a backup first and store on ext sd card, no if card do backup and move to pc, then once flashed stock just re-root and flash twrp again and then u can restore your backup.
Click to expand...
Click to collapse
oh great! Thanks, it's going to take some times, but I hope it's worth it

I installed the rom/firmware G900FXXS1CPHW_OXA1CPE1_BTU_UK_6.0.1 and I am now stuck in the bootloop...I guess I am not using the right firmware. Any help? (UK Samsung Galaxy S5)
edit: fixed, I forgot to disable the re-partion option on Odin

[Q] Cant flash Stock rom anymore

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

How to convert original stock ROM into flasheable ROM for TWRP?

I have a J7 2017 (J730F) and it does not let me flinch by Odin but I do through TWRP and I would like to know if I can somehow convert the 4 files of the original stock ROM into a single file flashed by TWRP.

ismago said:
I have a J7 2017 (J730F) and it does not let me flinch by Odin but I do through TWRP and I would like to know if I can somehow convert the 4 files of the original stock ROM into a single file flashed by TWRP.
Click to expand...
Click to collapse
The only thing you could possibly flash with twrp, depending on its build, is boot, recovery, system and modem. It is possible to flash others via dd, but it's not a simple process.
It's not recommended though and Tbh honest you need to solve the issue as to why odin will not flash.
There will be a reason.
Odin is the only real way to unbrick a non functioning device, so you really need to solve the issue rather than circumvent it.

T580 stock image file to flash with Odin (and then custom ROM)

Hi,
I have a T580 stuck at Android 7.0 (failed to update).
Ideally, I'd want to change to custom ROM with smaller footprint. It's an old device with only 16 GB storage. I've tried to root the device but failed.
I think I can't flash custom ROM with Odin. So I have to flash to stock ROM first with Odin. And then probably go with TWRP and try a custom ROM.
Which stock ROM is the safest to do this?
Thanks

redhonker said:
Hi,
I have a T580 stuck at Android 7.0 (failed to update).
Ideally, I'd want to change to custom ROM with smaller footprint. It's an old device with only 16 GB storage. I've tried to root the device but failed.
I think I can't flash custom ROM with Odin. So I have to flash to stock ROM first with Odin. And then probably go with TWRP and try a custom ROM.
Which stock ROM is the safest to do this?
Thanks
Click to expand...
Click to collapse
If you can still boot to 7, you don't need to flash another stock ROM. Just make sure OEM is enabled in Developer mode options and then flash TWRP. Then, you can use TWRP to flash custom ROMs. Just make sure you follow the instruction carefully when installing TWRP, because if you let it boot back to stock, it will just write over TWRP. You disable Auto reboot in the Odin options, so you can make it boot to TWRP before booting to system.

lewmur said:
If you can still boot to 7, you don't need to flash another stock ROM. Just make sure OEM is enabled in Developer mode options and then flash TWRP. Then, you can use TWRP to flash custom ROMs. Just make sure you follow the instruction carefully when installing TWRP, because if you let it boot back to stock, it will just write over TWRP. You disable Auto reboot in the Odin options, so you can make it boot to TWRP before booting to system.
Click to expand...
Click to collapse
Great. is there a link to the instruction?
Thanks

redhonker said:
Great. is there a link to the instruction?
Thanks
Click to expand...
Click to collapse
Read through this thread.