I tried to root my Sprint variant with Odin (Credo mobile is the carrier). Although Odin said it PASSED, the phone went into a boot loop. I tried the Sprint firmware to unroot it - Odin said it FAILED. If I hold Volume-up/home/power, I do not get a recovery menu, but just another loop, with "Recovery Booting" flashing in blue at the top. Held the buttons a long time, did everything over, etc. I can get to download mode, and the recovery mode loop, but nothing else. Suggestions?
Kanzeon said:
I tried to root my Sprint variant with Odin (Credo mobile is the carrier). Although Odin said it PASSED, the phone went into a boot loop. I tried the Sprint firmware to unroot it - Odin said it FAILED. If I hold Volume-up/home/power, I do not get a recovery menu, but just another loop, with "Recovery Booting" flashing in blue at the top. Held the buttons a long time, did everything over, etc. I can get to download mode, and the recovery mode loop, but nothing else. Suggestions?
Click to expand...
Click to collapse
Go into download mode and try flashing the firmware again. Tell us the error and I can try and help you fix your phone. By the recovery booting error, I assume you need the pit file to repartition your phone.
Here's the whole sad story, according to Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone says:
SV REV CHECK FAIL: [system]Fused 3 > Binary 1
I don't know about pit files, but at this point I will try pretty much anything. Thank you!
im having same issue
please help
I had the same issue happened to me when trying to use Odin to flash my Galaxy S7 G930p
It would boot the very first Samsung logo in a shutdown restart and do it again repeatedly I then went back and downloaded a different firmware and it resolved the issue but now shows a unlocked padlock Below Samsung and says modified and I still don't have TWRP recovery installed but at least it fixed my boot.img I think you have flashed the wrong boot image to your phones both of you guys tell me the full model of your phone and firmware version and maybe I could help you resolve your phones
My Galaxy S7 g930p I have the Chinese version Qualcomm Virgin Mobile phone
Odin img TWRP recovery ? does anyone have the proper boot.img I need.
I'm the on android version 7.0 nauget.
Not the S7 Edge
Thank you much
Related
I was updating my samsung galaxy grand prime duos (SM-G531H) with kies, not knowing my cable was broken while the updating the phone disconnected and i ended up with a screen saying "firmware upgrade encountered an issue. please select recovery mode in kies and try again" i changed the cable and decided to flash the update with odin... process went through and the phone booted up normal with the new update installed... now i decided to factory reset so i went into the stock recovery and did but it came up with a bunch of errors which i didn't take note of... i flashed twrp and repaired the file system, wiped system and then i flashed the the firmware together with the pit file on odin once more... the phone booted up normal and i was using it and eveything when i put it to charge and came back 10 mins later the phone was off.... when i powered it on it just stays on the "samsung galaxy grand prime" screen and doesn't boot... it doesn't go into recovery anymore it just hangs whe're it says "recovery is not seandroid enforcing" i tried flashing the firmware with odin again but every single time i tried it keeps failing at...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried the repair firmware together with the pit file and it gets stuck at
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
it's been like that for over an hour now... any help would be much appreciated guys.
No
Try with orignal firmware
nihu.46 said:
Try with orignal firmware
Click to expand...
Click to collapse
I tried everything and nothing seems to work
I also get this problem. Does anyone know how to fix it?
Ghettovybz said:
I tried everything and nothing seems to work
Click to expand...
Click to collapse
Remove kies. Reinstall samsung drivers.
Find and flash TWRP 3.0.0 with odin ( on recovery is not SEAndroid enforcing hold volume up and home for 5-10 seconds. Also flash the Custom Kernel by eyeless95 on the forum, its sepermissive.
u0aol said:
Remove kies. Reinstall samsung drivers.
Find and flash TWRP 3.0.0 with odin ( on recovery is not SEAndroid enforcing hold volume up and home for 5-10 seconds. Also flash the Custom Kernel by eyeless95 on the forum, its sepermissive.
Click to expand...
Click to collapse
What about for SM-G530H?
Do u have the link for the kernel?
After installing kernel what should I do then?
Two ways. Find stock rom in Sammobile and install via Odin (newest). Or try once again install it via Kies. You sould can restore it with Kies, but dont plug phone to computer. Write down S/N or something like that (it's under battery) and model, and Kies will download system
argounaut said:
What about for SM-G530H?
Do u have the link for the kernel?
After installing kernel what should I do then?
Click to expand...
Click to collapse
I have a g531h so I'm not sure. I'm below ten posts so i cant post links.
There are kernels and recoverys in the development section that work fine for your phone .
EDIT: I HAVE SOLVED THE ISSUE. I am not sure how but I got into a different download mode and the flash worked. I also used different SM-930A Files and it worked but system status is still custom.
I want to put my phone back to stock after I have installed a custom ROM. I have an AT&T S7. I get this error while flashing the firmware using Odin
----------------------------------------------------------------------------------------------------------
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
------------------------------------------------------------------------------------------------------
On the phone it says the following
"SW REV CHECK FAIL : [system]Fused 3 > Binary 1"
If you could tell me how to flash my phone back to stock without getting this error it would be very much appreciated.
I got the same error a while back. For me, it was because I was using Odin 3.11.1. Once I updated to Odin 3.12.3, the restore went smoothly. Someone correct me if that's not the way to fix this issue, but that is what worked for me.
lukemarcondes said:
I got the same error a while back. For me, it was because I was using Odin 3.11.1. Once I updated to Odin 3.12.3, the restore went smoothly. Someone correct me if that's not the way to fix this issue, but that is what worked for me.
Click to expand...
Click to collapse
I have resolved the issue. I have been trying for almost a month now to fix the phone and I finally did it. The device still says custom although I have flashed the official firmware on. Somehow I got into an alternative download mode that accepted the flash. I have no clue how I got it into the mode but it only said "downloading" and showed nothing in the top right corner. No white text.
ColbyTrip1 said:
I have resolved the issue. I have been trying for almost a month now to fix the phone and I finally did it. The device still says custom although I have flashed the official firmware on. Somehow I got into an alternative download mode that accepted the flash. I have no clue how I got it into the mode but it only said "downloading" and showed nothing in the top right corner. No white text.
Click to expand...
Click to collapse
I see. Glad you were able to fix it!
I installed the Superstarz ROM and TWRP onto my phone (Samsung Galaxy On5) (SM-G550T). The phone booted, and everything was working fine.
Like an idiot, I decided I didn't need to keep "usb debugging" and "oem unlock" enabled, so I turned them both off. When I restarted my phone, it was stuck at the boot screen ,with "custom binary blocked by frp lock" showing in red.
I cannot boot into recovery or into the system. I'm only able to boot into download (Odin) mode. I tried to flash the stock ROM in Odin, but FRP prevents anything from being flashed. I cannot re-enable "oem unlock" or "usb debugging" because I'm unable to boot into the system.
What are my options here?
halomaster said:
I installed the Superstarz ROM and TWRP onto my phone (Samsung Galaxy On5) (SM-G550T). The phone booted, and everything was working fine.
Like an idiot, I decided I didn't need to keep "usb debugging" and "oem unlock" enabled, so I turned them both off. When I restarted my phone, it was stuck at the boot screen ,with "custom binary blocked by frp lock" showing in red.
I cannot boot into recovery or into the system. I'm only able to boot into download (Odin) mode. I tried to flash the stock ROM in Odin, but FRP prevents anything from being flashed. I cannot re-enable "oem unlock" or "usb debugging" because I'm unable to boot into the system.
What are my options here?
Click to expand...
Click to collapse
You should still be able to flash full stock from recovery, the version of Android you were on or higher. Even with frp.
Sent from my SM-T350 using Tapatalk
Koognod said:
You should still be able to flash full stock from recovery, the version of Android you were on or higher. Even with frp.
Sent from my SM-T350 using Tapatalk
Click to expand...
Click to collapse
This is what happens when I try to flash anything in Odin. Same results in both Odin 3.12.3 and 3.10.7
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Flashing latest firmware will solve this problem...
Or
Other you can try Z3X Box ...
There are many tutorial on youtube..
Was there no answer to this problem or some what of a outcome? I am having the same issues,odin log identical
i have done this same thing - do not know enough about "flashing" and "roms" to understand these solutions. can someone please help?
do i need to just download Odin and try to "flash" from my pc?
fixed mine with this SM-G550T1 BRICK FRP BLOCK FIX
glennnall said:
i have done this same thing - do not know enough about "flashing" and "roms" to understand these solutions. can someone please help?
do i need to just download Odin and try to "flash" from my pc?
Click to expand...
Click to collapse
The stock rom you have is the wrong version. i got the info and fixed mine here..
https://androidforums.com/threads/galaxy-on5-metropcs-t-mobile-stock-firmware.1140060/
then i got the software from:
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
the exact firmware for metropcs is:
Country/Region USA
Product Code TMK
OS Version Marshmallow (Android 6.0.1)
Release Date 23.03.2017
PDAG550T1UVU2AQC4
CSCG550T1TMK2AQC4
Phone G550T1UVU2AQC4
once downloaded and extracted it is self explanatory on where to place files in Odin (files are labeled for appropriate slots) hope this helps. mine was bricked for 2 weeks determination is the key to success.
I had used TWRP to install SuperSU to root. This seemed successful, but a day or two later the phone had powered itself off, and on power-up loops displaying the tiny red "Custom binary is blocked by FRP Lock" message. The phone will boot into download mode, but won't enter recovery mode.
I tried repeating the install of TWRP using ODIN 3.12, but now that fails. Tried installing factory images (\BL_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5 etc.) w/ ODIN, and that fails too.
Is this an indication I don't have the latest image files? ODIN messages below:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Made some progress
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.
BHarris said:
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.
Click to expand...
Click to collapse
what worked? and what firmware. I have 2 on5's one sm-G-550T and a sm-g550T1 that both ended up with the "custom binary blocked by FRP lock" on the same day..
Please help!
I just tried a bin I downloaded from S U site and it didn't work. Gotta love the On5 lol.
Custom Binary Lock
The same happened to me: i have not found a complete solution, the closest i get to anything is; i put the On5 in Odin3 v3.12 and select the AP option and putting the recovery.tar file and running it. it goes good till its done and the result is Custom Binary (recovery) blocked by FRP lock in green letters. but still no success. i have tried trwp recovery, the home.tar file, each file by them selves and having trouble. i may not be an expert at this type of programimng but i pick things up quickly if there is any solution to my problem please let me know. thx............ by the way i have also tried kies and wont connect to it as well
Same Problem FRP Blocked Bootlooping
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!
SeleneKnightress said:
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!
Click to expand...
Click to collapse
You need to reinstall the firmware using Odin. Then, when you root again, you need to make sure you have oem unlock and usb debugging on in the developer options. Not having those on and rebooting when rooted cause the custom binary problem.
"Only officially released binaries..." error and I can't flash the stock firmware
I sort of bricked my phone (i think this is considered bricked anyway) after rooting it and getting the "only official binaries allowed" message. I tried to flash the stock firmware via odin, and it was stuck at "NAND write start" with the box reading "set partition". The only options ticked in odin were f.reset time and auto reboot. I'm really scared I've messed it up permanently somehow, please help if you can.
Model: SM-G950F, Exynos (I don;t know what other info to include or how to find that info without my phone on, if anything is needed, please tell me and Ill try and find it)
LOG:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin.lz4
<ID:0/005> NAND Write Start!!
UPDATE: tried again, three lines were added
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I also tried it on another machine, got the same thing including those three lines but in a different order:
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007>Complete(write) operation failed.
<OSM> All threads complete. (succeed 0 / failed 1)
<ID:0/007> Removed!!
In addition, I'm not certain if this was there before, but a line in my download mode says:
"SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 3, BINARY: 2"
I saw a similar line on one of the threads, so I realise that may be important
Thanks for any help in advance
--End Update
Exact steps taken to root the phone:
I decided to root my phone via magisk. I installed TWRP via odin, didn't quite immediately boot into recovery, so I flashed it once more, and this time managed to. I kept it read only, and then formatted the phone via TWRP, rebooted into recovery again, flashed the no-verity file (no-verity-opt-encrypt-6.0). I did not flash that RMM file I've seen after looking for solutions, and then rebooted my phone. It worked fine, magisk was installed, I went through the initial setup, restored my stuff from a backup etc. and then, I tried to install the xposed module in the magisk repo. Rebooted, and got the whole "Only official released binaries are allowed to be flashed" message and couldn't boot up past the initial "samsung galaxy 8 - powered by android" screen, nor into my recovery. So, I went looking for solutions, and did something dumb. I tried to flash this file here (Nougat G950FXXU1AQL5 bootloader) before restoring the original firmware. I'm not sure what problems that might have caused, and the flash failed anyhow, but I don't know still. Moving on,
twinsniper said:
I sort of bricked my phone (i think this is considered bricked anyway) after rooting it and getting the "only official binaries allowed" message. I tried to flash the stock firmware via odin, and it was stuck at "NAND write start" with the box reading "set partition". The only options ticked in odin were f.reset time and auto reboot. I'm really scared I've messed it up permanently somehow, please help if you can.
Model: SM-G950F, Exynos (I don;t know what other info to include or how to find that info without my phone on, if anything is needed, please tell me and Ill try and find it)
LOG:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin.lz4
<ID:0/005> NAND Write Start!!
UPDATE: tried again, three lines were added
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I also tried it on another machine, got the same thing including those three lines but in a different order:
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007>Complete(write) operation failed.
<OSM> All threads complete. (succeed 0 / failed 1)
<ID:0/007> Removed!!
In addition, I'm not certain if this was there before, but a line in my download mode says:
"SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 3, BINARY: 2"
I saw a similar line on one of the threads, so I realise that may be important
Thanks for any help in advance
--End Update
Exact steps taken to root the phone:
I decided to root my phone via magisk. I installed TWRP via odin, didn't quite immediately boot into recovery, so I flashed it once more, and this time managed to. I kept it read only, and then formatted the phone via TWRP, rebooted into recovery again, flashed the no-verity file (no-verity-opt-encrypt-6.0). I did not flash that RMM file I've seen after looking for solutions, and then rebooted my phone. It worked fine, magisk was installed, I went through the initial setup, restored my stuff from a backup etc. and then, I tried to install the xposed module in the magisk repo. Rebooted, and got the whole "Only official released binaries are allowed to be flashed" message and couldn't boot up past the initial "samsung galaxy 8 - powered by android" screen, nor into my recovery. So, I went looking for solutions, and did something dumb. I tried to flash this file here (Nougat G950FXXU1AQL5 bootloader) before restoring the original firmware. I'm not sure what problems that might have caused, and the flash failed anyhow, but I don't know still. Moving on,
Click to expand...
Click to collapse
For starters use latest Odin 3.13.1 it supports the lz4 compression.
Device 3 binary 2 error means you are trying to flash early version firmware use the same or later version firmware
Oh wow, okay, I didn't realize I was flashing an earlier firmware, it's one I flashed earlier in the year and still the latest on updato for vodafone, but yeah there was an update to that. Thank you, so, so much. I was terrified and up till like 5 am last night trying to fix it, sick to my stomach etc. thinking I'd permanently messed things up.
For anyone reading this in the future, as of right now, the latest Vodafone SM-G950F Firmware (Australia) on updato is not the latest firmware (from what I understand you don't want to flash anything with XXU2. you want XXU3), but if you go to sammobile or use samfirm (helluva lot faster download speed for the record) you can get the latest firmware.
Anyway, thanks a lot spawnlives, really appreciate the help, and its good to know for the future If i ever do anything like this again what that message means.
twinsniper said:
Oh wow, okay, I didn't realize I was flashing an earlier firmware, it's one I flashed earlier in the year and still the latest on updato for vodafone, but yeah there was an update to that. Thank you, so, so much. I was terrified and up till like 5 am last night trying to fix it, sick to my stomach etc. thinking I'd permanently messed things up.
For anyone reading this in the future, as of right now, the latest Vodafone SM-G950F Firmware (Australia) on updato is not the latest firmware (from what I understand you don't want to flash anything with XXU2. you want XXU3), but if you go to sammobile or use samfirm (helluva lot faster download speed for the record) you can get the latest firmware.
Anyway, thanks a lot spawnlives, really appreciate the help, and its good to know for the future If i ever do anything like this again what that message means.
Click to expand...
Click to collapse
Glad you got sorted out.
I am aware of the new firmware with ver3 bootloader it has been out for a while. Samfirm is probably the best for latest versions. I am using XSA (Australian unbranded) firmware i try not to use branded firmware like Telstra,Optus or Vodafone.