Related
Please follow all the steps or you'll have bricked device
Step 1 :
This is the easiest way to enable USB debugging.
Dial *#0808#
Select last option, DM+Modem+ADB
YOUR PHONE MUST ASK FOR USB DEBUGGING AUTHORIZATION ! YOU MUST CHECK ALWAYS ALLOW FROM THIS COMPUTER AND THEN PRESS OK. IF YOU DO NOT GET THIS DO NOT PROCEED
Step 2:
Reboot phone into download mode
Select PDA slot in odin
And flash the tar file root kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Your device will not have display but it will still be working, run saferoot.
Step 3:
Use saferoot thanks to k1mu, Surge1223, download is at the end of the post linked below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
After phone reboots for first time remove USB and enter download mode.
Step 4:
Select PDA slot in odin
And flash the tar file restore display kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Step 5:
Install Supersu from market and open it. Continue with saferoot, that is waiting for the phone.
When flashing the root_boot.tar.md5 i get an error.
<OSM> MD5 hash value is invalid
<OSM> root_boot.tar.md5 is invalid.
---------- Post added at 03:24 PM ---------- Previous post was at 03:12 PM ----------
nvm, I fixed it by removing the .md5 extension.
You're awesome! Thanks!
Nice work.
Looks like we're flashing 4.2.2's kernel, rooting, then flashing 4.4.2's kernel again.
I guess this also means there is the potential to downgrade back to 4.2.2 completely with mobile odin now...
Did you guys have any trouble getting SuperSU to update the su binary?
SU works, just prompts me to update the binary and fails.
az4x4runner said:
Nice work.
Looks like we're flashing 4.2.2's kernel, rooting, then flashing 4.4.2's kernel again.
I guess this also means there is the potential to downgrade back to 4.2.2 completely with mobile odin now...
Click to expand...
Click to collapse
You can downgrade to 4.2.2, just flash the stock bootloader first, then it will let you flash the ROM. I had to do it because I bricked at the 4.4.2 upgrade.
Trying this root now!
djdevin said:
You can downgrade to 4.2.2, just flash the stock bootloader first, then it will let you flash the ROM. I had to do it because I bricked at the 4.4.2 upgrade.
Trying this root now!
Click to expand...
Click to collapse
I have not been able to find the JB bootloader. It's out there? The ROMs on Sammobile don't include it... I had previously bricked trying to downgrade due to the locked KK bootloader.
az4x4runner said:
I have not been able to find the JB bootloader. It's out there? The ROMs on Sammobile don't include it... I had previously bricked trying to downgrade due to the locked KK bootloader.
Click to expand...
Click to collapse
Sorry, I misspoke. I don't know if it was the bootloader or something else. Check this out: http://forum.xda-developers.com/showpost.php?p=55251936&postcount=18
Also, root works!
Someone want to explain how those two files could be flashed via ODIN?
djdevin said:
Sorry, I misspoke. I don't know if it was the bootloader or something else. Check this out: http://forum.xda-developers.com/showpost.php?p=55251936&postcount=18
Also, root works!
Someone want to explain how those two files could be flashed via ODIN?
Click to expand...
Click to collapse
They are stock kernel images. I've never had issues flashing stock kernels or recoveries with Odin.
az4x4runner said:
They are stock kernel images. I've never had issues flashing stock kernels or recoveries with Odin.
Click to expand...
Click to collapse
stock images from the sm-g730a? or another device?
djdevin said:
stock images from the sm-g730a? or another device?
Click to expand...
Click to collapse
From the SM-G730A.
"Root kernel" is simply the 4.2.2 stock kernel, which worked with Saferoot previously, and still does.
"Restore display kernel" is the stock 4.4.2 kernel you started with, you're just reflashing it after rooting.
I extracted boot.img from each ROM (4.2.2 and 4.4.2), created my own tar.md5 files and was able to root successfully also. I'm not sure why the ones in this post don't work with the md5 extension. It's a great idea.
az4x4runner said:
From the SM-G730A.
"Root kernel" is simply the 4.2.2 stock kernel, which worked with Saferoot previously, and still does.
"Restore display kernel" is the stock 4.4.2 kernel you started with, you're just reflashing it after rooting.
I extracted boot.img from each ROM (4.2.2 and 4.4.2), created my own tar.md5 files and was able to root successfully also. I'm not sure why the ones in this post don't work with the md5 extension. It's a great idea.
Click to expand...
Click to collapse
ah I see. that makes sense
az4x4runner said:
Did you guys have any trouble getting SuperSU to update the su binary?
SU works, just prompts me to update the binary and fails.
Click to expand...
Click to collapse
i have the same trouble
I just finished step 4 and how it keeps restarting and vibrating.
FIX for "Installation Failed when Updating Binary on SuperSU"
bam056 said:
i have the same trouble
Click to expand...
Click to collapse
az4x4runner said:
Did you guys have any trouble getting SuperSU to update the su binary?
SU works, just prompts me to update the binary and fails.
Click to expand...
Click to collapse
It seems that the SuperSU version (2.01) that is currently (13/10/2014) on the Play Store is outdated. You need to do the following:
1) Download v 2.13 of Chainfire's SuperSU from his Google+ page (I cannot post the link here as I am a new user)
2) Extract the .zip file and find 'Superuser.apk'
3) Transfer 'Superuser.apk' to SD card of your phone
4) Open 'Superuser.apk' from your phone and install/update
5) After the installation/update is complete, open SuperSU and update binary (normal method)
Good luck. I just used this thread to root my Samsung SIII Mini (SM-G730A) from Fido. Working great so far. Thanks atinder! :good:
Great post
It's a great post, I would like thank az4x4runner and wisdom and all of you guys, if you do it step by step is a 123 solve for the ATT S3 Mini SM-G730A 4.4.2 Root :good::good::victory::victory:
I can confirm that I've rooted my G730A using the steps given and with the SuperSU apk provided. The first thing I did was bypass Kitkat's SD card limitations -- everything is now exactly the way I want it. Thank you all!
I need help. I tired to root my g730a and I followed all the steps and now my phone has a blank screen with the blue light on. How can I fix this? thanks!
-----------------------------------
nvm, I got it to work.
Recovery
Which recovery works for 4.4.2?
Will this work on Verizon SIII mini running 4.4.2? I successfully rooted my Galaxy Tab with Odin and it was easy as pie. This looks a lot more complicated and I have already tried TowelRoot, Saferoot, etc with no success.
atinder said:
Please follow all the steps or you'll have bricked device
Step 1 :
This is the easiest way to enable USB debugging.
Dial *#0808#
Select last option, DM+Modem+ADB
YOUR PHONE MUST ASK FOR USB DEBUGGING AUTHORIZATION ! YOU MUST CHECK ALWAYS ALLOW FROM THIS COMPUTER AND THEN PRESS OK. IF YOU DO NOT GET THIS DO NOT PROCEED
Step 2:
Reboot phone into download mode
Select PDA slot in odin
And flash the tar file root kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Your device will not have display but it will still be working, run saferoot.
Step 3:
Use saferoot thanks to k1mu, Surge1223, download is at the end of the post linked below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
After phone reboots for first time remove USB and enter download mode.
Step 4:
Select PDA slot in odin
And flash the tar file restore display kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Step 5:
Install Supersu from market and open it. Continue with saferoot, that is waiting for the phone.
Click to expand...
Click to collapse
After flashing 1st boot.tar you say screen goes blank then run saferoot. After saferoot reboot will you have screen display again?
Hello guys hoping to get some help with this issue. So...I flashed the update for SuperSU on my S7 Edge using FlashFire, after flash it went into boot and this is what i got; "Custom binary blocked by SECURE BOOT (boot.img)" on left cornor and "Security Error: This phone has been flashed with unauthorized software & is locked. Call your phone operator for additional support." I can go into recovery mode, I tried to factory reset but did not work. Any help would be greatly welcome. I am still noob at this so please go ez on me
Stock Firmware for S7 Edge G935T UVU3APG1
Duggi1663 said:
Hello guys hoping to get some help with this issue. So...I flashed the update for SuperSU on my S7 Edge using FlashFire, after flash it went into boot and this is what i got; "Custom binary blocked by SECURE BOOT (boot.img)" on left cornor and "Security Error: This phone has been flashed with unauthorized software & is locked. Call your phone operator for additional support." I can go into recovery mode, I tried to factory reset but did not work. Any help would be greatly welcome. I am still noob at this so please go ez on me
Click to expand...
Click to collapse
Update..
So... I decided to flash Stock Firmware and now its working like a charm . hope this helps others with the same situation. Cheers
Duggi1663 said:
Update..
So... I decided to flash Stock Firmware and now its working like a charm . hope this helps others with the same situation. Cheers
Click to expand...
Click to collapse
Its not necessary to flash stock, simply reflashing the engboot will suffice, and does not wipe the device.
First of all you wanted to Flash SuperSu.... Did you enable Android Debugging.... Then check OEM Unlock?
If not you messed up there...
Next You need use Odin to flash CF-Root. You are now running a patched Kernel and SuperSU
Use TWRP app to install twrp for your device.
i have the same exact problem, been trying to flash stock firmware but cant get it to work. help please!!!! which firmware? can i get a link please!!!!!!!!!!
qwewqa said:
Its not necessary to flash stock, simply reflashing the engboot will suffice, and does not wipe the device.
Click to expand...
Click to collapse
Hello, having same issue. Didn't realize you can only make backups with flashfire, not actually flash them back with the program too...
I have the original files I installed with Odin, are one of these the engineering boot file? (BL, AP, CP, CSC?)
Or are you talking about something else...? Thanks!
BobTheTenth said:
Hello, having same issue. Didn't realize you can only make backups with flashfire, not actually flash them back with the program too...
I have the original files I installed with Odin, are one of these the engineering boot file? (BL, AP, CP, CSC?)
Or are you talking about something else...? Thanks!
Click to expand...
Click to collapse
You flash the engboot file you used to root the device, the one you placed in AP and is around 20 mb in size (not the actual firmware) .
qwewqa said:
You flash the engboot file you used to root the device, the one you placed in AP and is around 20 mb in size (not the actual firmware) .
Click to expand...
Click to collapse
Thanks!
Recovery locked
please help!! How To Root Galaxy J5 Prime Android 7.0?
Magisk Boot Patch + Odin worked for me. If you encounter dm-verity verification failed:
1. Do a factory reset;
2. Don't login to samsung account or set up fingerprints;
3. Flash Magisk Boot Patch again.
boot.img (required for making Magisk patched_boot.img.tar) can be extracted from AP
duyquangdo329 said:
Magisk Boot Patch + Odin worked for me. If you encounter dm-verity verification failed:
1. Do a factory reset;
2. Don't login to samsung account or set up fingerprints;
3. Flash Magisk Boot Patch again.
boot.img (required for making Magisk patched_boot.img.tar) can be extracted from AP
Click to expand...
Click to collapse
How did you get it to work? Mine is stuck at Flashing
- Device platform: arm
- Extracting files
My model is SM-G570M
xX_Kale_Xx said:
How did you get it to work? Mine is stuck at Flashing
- Device platform: arm
- Extracting files
My model is SM-G570M
Click to expand...
Click to collapse
I failed multiple times before I got it work.
1. Flash stock firmware using Odin,
2. Skip any logins and fingerprint (just to save my time),
3. Flash Magisk patched boot image with Odin (not a custom recovery). Here I got "signature verification failed". I tapped on "Reset".
4. Skip any logins and fingerprint (this's important),
5. Flash Magisk patched boot image again.
My G570Y is now rooted. Good luck! and I'm not a developer btw.
duyquangdo329 said:
I failed multiple times before I got it work.
1. Flash stock firmware using Odin,
2. Skip any logins and fingerprint (just to save my time),
3. Flash Magisk patched boot image with Odin (not a custom recovery). Here I got "signature verification failed". I tapped on "Reset".
4. Skip any logins and fingerprint (this's important),
5. Flash Magisk patched boot image again.
My G570Y is now rooted. Good luck! and I'm not a developer btw.
Click to expand...
Click to collapse
Thanks
---------- Post added at 07:21 AM ---------- Previous post was at 06:56 AM ----------
duyquangdo329 said:
I failed multiple times before I got it work.
1. Flash stock firmware using Odin,
2. Skip any logins and fingerprint (just to save my time),
3. Flash Magisk patched boot image with Odin (not a custom recovery). Here I got "signature verification failed". I tapped on "Reset".
4. Skip any logins and fingerprint (this's important),
5. Flash Magisk patched boot image again.
My G570Y is now rooted. Good luck! and I'm not a developer btw.
Click to expand...
Click to collapse
Did you get, "Only official release binaries are allowed to be flashed(BOOT) message on your phone when you tried flashing the patched boot image?
xX_Kale_Xx said:
Thanks
---------- Post added at 07:21 AM ---------- Previous post was at 06:56 AM ----------
Do I have to change the patched boot image file extension from .img to patched_boot.img.tar?
Click to expand...
Click to collapse
Yes but not manually. Magisk Manager has an option for that.
duyquangdo329 said:
Of course but not manually. Magisk Manager has an option for that.
Click to expand...
Click to collapse
I realized that after I posted. Did you get, "Only official release binaries are allowed to be flashed(BOOT) message on your phone when you tried flashing the patched boot image?
xX_Kale_Xx said:
I realized that after I posted. Did you get, "Only official release binaries are allowed to be flashed(BOOT) message on your phone when you tried flashing the patched boot image?
Click to expand...
Click to collapse
No. Never got that. May be your image is not official. Try to redownload your full firmware from Sammobile or simply find your boot.img on firmware.mobi.
duyquangdo329 said:
No. Never got that. May be your image is not official. Try to redownload your full firmware from Sammobile or simply find your boot.img on firmware.mobi.
Click to expand...
Click to collapse
I downloaded it from Sammobile. Are you running nougat 7.0 or marshmallow 6.0.1?
xX_Kale_Xx said:
I downloaded it from Sammobile. Are you running nougat 7.0 or marshmallow 6.0.1?
Click to expand...
Click to collapse
I'm on Nougat.
duyquangdo329 said:
I'm on Nougat.
Click to expand...
Click to collapse
Maybe it just doesn't work on my model, did you use the 6.0.1 or the 7.0 boot image?
xX_Kale_Xx said:
Maybe it just doesn't work on my model, did you use the 6.0.1 or the 7.0 boot image?
Click to expand...
Click to collapse
7.0 of course. Follow my steps, and if it does not work, just find your own way.
duyquangdo329 said:
7.0 of course. Follow my steps, and if it does not work, just find your own way.
Click to expand...
Click to collapse
When I try to flash anything in Odin I get this error, "Only official released binaries are allowed to be flashed." I can't flash anything thats 'unoffical' or not supported by Samsung for my model.
xX_Kale_Xx said:
When I try to flash anything in Odin I get this error, "Only official released binaries are allowed to be flashed." I can't flash anything thats 'unoffical' or not supported by Samsung for my model.
Click to expand...
Click to collapse
I've never been in that situation. :angel:
Does it allow you to flash the stock firmware? If not, you are probably using the wrong Product code.
duyquangdo329 said:
I've never been in that situation. :angel:
Does it allow you to flash the stock firmware? If not, you are probably using the wrong Product code.
Click to expand...
Click to collapse
Yes, I can flash the stock firmware, that's the same firmware I have, the product code is not wrong
xX_Kale_Xx said:
Yes, I can flash the stock firmware, that's the same firmware I have, the product code is not wrong
Click to expand...
Click to collapse
hi there, i´ve got the same error about only official released binaries are allowed.
have you found another way?
thanks
davidvd102dvd said:
hi there, i´ve got the same error about only official released binaries are allowed.
have you found another way?
thanks
Click to expand...
Click to collapse
Unfortunately, I haven't found anything yet.
davidvd102dvd said:
hi there, i´ve got the same error about only official released binaries are allowed.
have you found another way?
thanks
Click to expand...
Click to collapse
The only way i found is to downgrade to 6.0.1, flash all four files (BL, AP, CP, CSC) in Odin v3.12.10
and follow the instructions on this thread: https://forum.xda-developers.com/ga...evelopment/twrp-twrp-galaxy-j5-prime-t3605990
Download this firmware for the SM-G570M VERSION ONLY!
https://www.sammobile.com/firmwares/galaxy-j5-prime/SM-G570M/ZTO/download/G570MUBU2AQK2/195928/
or
http://updato.com/firmware-archive-select-model?record=17CBB3ECCB7211E7B7BDFA163EE8F90B
xX_Kale_Xx said:
The only way i found is to downgrade to 6.0.1, flash all four files (BL, AP, CP, CSC) in Odin v3.12.10
and follow the instructions on this thread: https://forum.xda-developers.com/ga...evelopment/twrp-twrp-galaxy-j5-prime-t3605990
Download this firmware for the SM-G570M VERSION ONLY!
https://www.sammobile.com/firmwares/galaxy-j5-prime/SM-G570M/ZTO/download/G570MUBU2AQK2/195928/
or
http://updato.com/firmware-archive-select-model?record=17CBB3ECCB7211E7B7BDFA163EE8F90B
Click to expand...
Click to collapse
downloading now, will try later at home and report it back, thanks so much,
other thing that i realize, when update to 7.0 QJ2 firmware form TTT (Trinidad y Tobago) is that when i turn on wifi no network available are displayed unless airplane mode is on, then i see them all, i'm live in cuba (country code "cu") and i know this was a problem with 4.4.* and 5.0.* android on samsung devices but never imagine that would be a problem again.
xX_Kale_Xx said:
The only way i found is to downgrade to 6.0.1, flash all four files (BL, AP, CP, CSC) in Odin v3.12.10
and follow the instructions on this thread: https://forum.xda-developers.com/ga...evelopment/twrp-twrp-galaxy-j5-prime-t3605990
Download this firmware for the SM-G570M VERSION ONLY!
https://www.sammobile.com/firmwares/galaxy-j5-prime/SM-G570M/ZTO/download/G570MUBU2AQK2/195928/
or
http://updato.com/firmware-archive-select-model?record=17CBB3ECCB7211E7B7BDFA163EE8F90B
Click to expand...
Click to collapse
!Works great, thanks so much.
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.