Hi, I recently flashed lollipop to my galaxy s4 and I want to root it but when I go in download mode, there is a new text in blue saying "secure download=enabled"
Can I still root my phone using Odin and CF auto root with this enabled ? And if not how can I disable it ?
k0spwn said:
Hi, I recently flashed lollipop to my galaxy s4 and I want to root it but when I go in download mode, there is a new text in blue saying "secure download=enabled"
Can I still root my phone using Odin and CF auto root with this enabled ? And if not how can I disable it ?
Click to expand...
Click to collapse
I am not sure but as far as i know you should unlock your bootloader. But like i said i am not sure,if you do more research about this it will be good for you. Sorry for bad English :good:
k0spwn said:
Hi, I recently flashed lollipop to my galaxy s4 and I want to root it but when I go in download mode, there is a new text in blue saying "secure download=enabled"
Can I still root my phone using Odin and CF auto root with this enabled ? And if not how can I disable it ?
Click to expand...
Click to collapse
Ignore the message. Everyone has it.
EmreAskin said:
I am not sure but as far as i know you should unlock your bootloader. But like i said i am not sure,if you do more research about this it will be good for you. Sorry for bad English :good:
Click to expand...
Click to collapse
No need to unlock the bootloader. Secure download was introduced on the Lollipop release and it doesn't act anything on your bootloader, even if you flash insecured file (.tar without .md5) via ODIN.
ive been through thousands of pages of forums and so far this is best answer to this question lol so this secure download enabled will not stop u from flashing causing odin to fail write and if so what will stop it from flashing stock or any rom ?
secure download enabled have one purpose... you CAN'T download (flash) old or low baseband (firmware) to your device... so you can't flash anything old than the one you already have installed.. well not by odin itself.. but you still can flash recoverys if your device support it, and flash any custom rom also..
edit: this not applied to old s5, s4, etc devices.. but s6 and new 2016 devices because the hardware checks
Serge Winters said:
secure download enabled have one purpose... you CAN'T download (flash) old or low baseband (firmware) to your device... so you can't flash anything old than the one you already have installed.. well not by odin itself.. but you still can flash recoverys if your device support it, and flash any custom rom also..
edit: this not applied to old s5, s4, etc devices.. but s6 and new 2016 devices because the hardware checks
Click to expand...
Click to collapse
You can!! I have same problem! on S7 herolte phone screen i have blue " Secure Download : Enable " and " RP SWREV: B:6 K:4 S:5 . And heimdall give "permission denied" message when i try load TWRP. With Patched Odin it write TWRP it to phone without problem. Than TWRP whipe all do sideload by heimdall and instal new system Thanks! picture https://forum.xda-developers.com/showpost.php?p=81418691&postcount=29
pawelnrg said:
You can!! I have same problem! on S7 herolte phone screen i have blue " Secure Download : Enable " and " RP SWREV: B:6 K:4 S:5 . And heimdall give "permission denied" message when i try load TWRP. With Patched Odin it write TWRP it to phone without problem. Than TWRP whipe all do sideload by heimdall and instal new system Thanks! picture https://forum.xda-developers.com/showpost.php?p=81418691&postcount=29
Click to expand...
Click to collapse
I was walking about Binarys (bits) you cant flash old binarys.. but you can flash recoverys or same bits even if they are from different OS versions but the bit itself is the same number.
Hi guys. I need help on restoring my s4 on complete stock. I messed up real hard
Here my problem. I have an i9505 s4 which is simlocked to globe philppines(mobile carrier). I tried to get rid of its booting animation because it's so annoying for me so I wanted to flash a stock rom of i9505 international version via Odin 3.07 but I rooted it first via Odin also. The time I am flashing GalaxyS4-CWM-6.0.4.4-GT-i9505 tar file, I got a fail in Odin then my S4 won't boot anymore and it says firmware upgrade encountered an issue blah blah kies. I tried to boot to recovery and that's what is also shows up. I tried to use Kies but what it does is just connecting to my device which takes forever. So I flashed a stock rom via Odin and it worked but the very problem is It's very laggy and says that process stopped responding, camera not working, status bar also not working, wifi not working. In short, all core apps are not working or just works for a minute and then stops and hang the phone. Sometimes i get a wallpaper screen(nothing else, just my wallpaper which occurs when it hangs).
Luckily I still haven't hardbricked my phone yet so I need all your help to fix it before I hardbrick it :crying::crying::crying:
Please help me how to restore my S4 to the very stock like fresh android software because I'm trying to still fix it days ago. I WILL TRY TO ANSWER ALL YOUR QUESTIONS REGARDING TO MY PROBLEM JUST PLEASE HELP ME PLEASE ! IM VERY WORRIED
You can chill. Nothing wrong with your phone and you didn't mess up anything. Things like that happen. You cannot brick your phone this way. It's almost impossible to brick it.
1. Perform factory reset in recovery.
That will probably fix it. Report back if it doesn't.
ps do not use CWM because it's outdated. Use TWRP and uncheck auto-reboot before flashing it trough Odin.
Lennyz1988 said:
You can chill. Nothing wrong with your phone and you didn't mess up anything. Things like that happen. You cannot brick your phone this way. It's almost impossible to brick it.
1. Perform factory reset in recovery.
That will probably fix it. Report back if it doesn't.
ps do not use CWM because it's outdated. Use TWRP and uncheck auto-reboot before flashing it trough Odin.
Click to expand...
Click to collapse
Is it okay to flash any build number on my s4? I just downloaded one of them "I9505XXUHOA7_OXAHOA7" and I flashed it on my phone. I tried to factory reset/wipe cache partition/ and wipe dalvik cache in cwm 6.0.4.4 touch but it always hangs and core apps are not responding. Maybe the rom is the problem? I don't know but I'll try to flash twrp and report back if it doesn't work.
I have installed TWRP and its stuck on bootloop. Tried to reset its factory settings but stuck on bootloop then cache partition and dalvik cache. I tried to install the rom via TWRP and it says installation failed. Should I download other rom ?
I just want it to make it work like what an s4 should be. Even on stock or custom rom.
cdd23 said:
I have installed TWRP and its stuck on bootloop. Tried to reset its factory settings but stuck on bootloop then cache partition and dalvik cache. I tried to install the rom via TWRP and it says installation failed. Should I download other rom ?
I just want it to make it work like what an s4 should be. Even on stock or custom rom.
Click to expand...
Click to collapse
I need more details.
- What does it say your model is when you are in download mode?
- What rom are you trying to flash?
- What is the error?
Lennyz1988 said:
I need more details.
- What does it say your model is when you are in download mode?
- What rom are you trying to flash?
- What is the error?
Click to expand...
Click to collapse
-When I boot to odin mode, what I see is:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANT VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
-I tried to flash a stock rom but it always fails even in twrp, so I downloaded a custom rom just to try it to install but It also hangs and core apps are malfunctioning. I think all rom I install fails miserably. I think I messed up real hard because I flashed two pit files in my unit.
-There is no error code in TWRP everytime I fail installing rom. It just says error installing zip.
I really need to restore it to complete stock. Every rom I successfully install hangs and crashes core apps in my unit.
I WILL TRY TO ANSWER ANY MORE QUESTIONS BECAUSE I NEED IT TO USE NOW. PLEASE
cdd23 said:
-When I boot to odin mode, what I see is:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANT VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
-I tried to flash a stock rom but it always fails even in twrp, so I downloaded a custom rom just to try it to install but It also hangs and core apps are malfunctioning. I think all rom I install fails miserably. I think I messed up real hard because I flashed two pit files in my unit.
-There is no error code in TWRP everytime I fail installing rom. It just says error installing zip.
I really need to restore it to complete stock. Every rom I successfully install hangs and crashes core apps in my unit.
I WILL TRY TO ANSWER ANY MORE QUESTIONS BECAUSE I NEED IT TO USE NOW. PLEASE
Click to expand...
Click to collapse
You did not mess it up. But you are still not giving enough details. What is the excact rom you are trying to flash? The excact rom you are trying to flash in TWRP?
XTE-I9505XXUEMKE-20131212184031 is the name of the zip file. From here http://forum.xda-developers.com/showthread.php?t=2265477. I can't flash it through odin and twrp
cdd23 said:
XTE-I9505XXUEMKE-20131212184031 is the name of the zip file. From here http://forum.xda-developers.com/showthread.php?t=2265477. I can't flash it through odin and twrp
Click to expand...
Click to collapse
No you cannot flash that with TWRP. You cannot flash stock roms with TWRP. You can only flash it with Odin. Besides you need to unpack that .zip file.
Keep in mind that you also cannot flash that package if you were on Lollipop.
Download a rom from here:
http://samsung-updates.com/device/?id=GT-I9505
Take this version: I9505XXUHOJ2
It doesn't matter which one. Then flash it using that guide from the link you gave me.
Wow thank you helped me alot.It worked but I have this little problem. "Unfortunately, google play services has stopped" and same as filter installer, always popping up on my screen and I can't access messaging app because it always crashes next to google play pop up. Any fix for it ? Im really grateful you helped me.
cdd23 said:
Wow thank you helped me alot.It worked but I have this little problem. "Unfortunately, google play services has stopped" and same as filter installer, always popping up on my screen and I can't access messaging app because it always crashes next to google play pop up. Any fix for it ? Im really grateful you helped me.
Click to expand...
Click to collapse
Your welcome.
Did you perform a factory reset from the recovery?
Lennyz1988 said:
Your welcome.
Did you perform a factory reset from the recovery?
Click to expand...
Click to collapse
Yes. I have factory reset it and wiped cache partition and works now perfectly. Thank you again
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
Yesterday I tried root my S8 (SM-G950FD) and I made the mistake of not allowing system modifications before flashing because I misinterpreted a guide. I flashed the no-verity zip and Magisk. The phone booted successfully and magisk was installed. Then I went to reboot into recovery to change some TWRP settings IE: Brightness. Then my phone said "Only officially released binaries are allowed to be flashed." That left me unable to boot my phone and also made it unable to boot into recovery. The only thing I can boot my phone into is download mode. I've tried flashing some stock roms that are 7.0 to remove the prenormal lock but they failed. I happened to make a TWRP backup before flashing but I can't use TWRP because of the official binary stuff. I'm wondering if I use the nand erase all option if that will let me flash the 7.0 stock roms then boot into TWRP and restore my backup or if they is way to convert the backup into something that Odin can flash. Does anybody know any confirmed methods to solve my problem?
Unbrick-me said:
Yesterday I tried root my S8 (SM-G950FD) and I made the mistake of not allowing system modifications before flashing because I misinterpreted a guide. I flashed the no-verity zip and Magisk. The phone booted successfully and magisk was installed. Then I went to reboot into recovery to change some TWRP settings IE: Brightness. Then my phone said "Only officially released binaries are allowed to be flashed." That left me unable to boot my phone and also made it unable to boot into recovery. The only thing I can boot my phone into is download mode. I've tried flashing some stock roms that are 7.0 to remove the prenormal lock but they failed. I happened to make a TWRP backup before flashing but I can't use TWRP because of the official binary stuff. I'm wondering if I use the nand erase all option if that will let me flash the 7.0 stock roms then boot into TWRP and restore my backup or if they is way to convert the backup into something that Odin can flash. Does anybody know any confirmed methods to solve my problem?
Click to expand...
Click to collapse
You will need to flash the same or higher version of Android to fix official binary error. Use default settings in Odin.
You cannot.flash earlier versions of Android if your bootloader is lower than what is on your phone ( 5th number from right of firmware name ). If in doubt flash the latest version.
Then I went to reboot
Click to expand...
Click to collapse
And i same problems "Only officially released binaries are allowed to be flashed"
---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------
Then I went to reboot
Click to expand...
Click to collapse
And i same problems "Only officially released binaries are allowed to be flashed"
spawnlives said:
You will need to flash the same or higher version of Android to fix official binary error. Use default settings in Odin.
You cannot.flash earlier versions of Android if your bootloader is lower than what is on your phone ( 5th number from right of firmware name ). If in doubt flash the latest version.
Click to expand...
Click to collapse
Ok so in few minutes from now the rom will be finished downloading. When that is done what version of Odin should I use and what files should place in Odin. I know this may seem stupid to ask but I'm not going to let myself make anymore stupid decisions after not installing the rmm bypass.
Quick Update, the rom finished downloading. I wasn't able to flash it. It gave me the error that the Bootloader had: 4 and the binary had 3... I was able to flash cp by itself tho and that set the system status to samsung official but the binary status is still custom. That made it so my phone only booted into a "Update failed screen use smart switch" screen ( I've tried smart switch before it doesn't detect my device). I can still get it back into recovery and flash old cps to get it to turn off without bootlooping into the smart switch screen. I'm wondering if I flash csc to factory reset if that will help at all. Guys what do I do??
Excuse my language but I ****ING DID IT!!! I don't know this worked but I am going to roughly call my process. So flashing the stock rom initially failed. I flashed then CP which for some reason always works and then AP which began but failed. This set the binary text to "Samsung Official", system status was still ****ed as custom. So I restored the cp and ap(?) from the crgb oreo files posted here. Then I flashed cp that passed, then csc which passed and then tried AP. After some time... It passed. The phone rebooted. The official binary bull**** was gone from the bootscreen and the phone booted into recovery. It installed some sys update stuff up to 30$ then erased some things which took awhile. Then the phone booted into initial setup and I now have ACCESS TO MY PHONE AGAIN!!!
For anyone interested in what FW I flashed PM me.