Felt confident, shouldnt have - Sprint Samsung Galaxy S7 Edge Questions & Answers

I recently carrier unlocked my SM-G935P (2016 version) from Sprint and brought it over to ATT. All was working fine but wanted to get rid of the Sprint bloatware. After spending most of the day reading threads of flashing, felt confident that I could walk through flashing over to "U" FW. This is my first attempt at flashing and it has FAILED!
Used ODIN 3.12 , and files from UPDATO
It failed after first attempt and then was stuck in boot loop
I then realized that I never set the Developer options before flashing
have tried flashing back to half dozen different version stocks, deep clean flash, and various other work arounds I have seen on here to no avail
Only things that have PASS since the initial FAIL have been when I tried various BL individually, but no change in device
I am at the point that I can only access Download screen and ODIN still recognizes. Other option is the device starts to open in Recovery Boot, Installing Software Update comes up, about 10 lines of code start scrolling then phone goes black.
I'm still OFFICIAL, FRP Lock on, warranty void is 0x0 and AP SWREV is B5(2, 1, 1, 1, 1) K1 S4, and Secure Download is Enabled
I'm way past my comfort and capability in trying to get this even back to stock. Any guidance would be greatly appreciated... Finally broke free of the Sprint chains and on the edge of bricking my phone!

PA_Pyroholic said:
I recently carrier unlocked my SM-G935P (2016 version) from Sprint and brought it over to ATT. All was working fine but wanted to get rid of the Sprint bloatware. After spending most of the day reading threads of flashing, felt confident that I could walk through flashing over to "U" FW. This is my first attempt at flashing and it has FAILED!
Used ODIN 3.12 , and files from UPDATO
It failed after first attempt and then was stuck in boot loop
I then realized that I never set the Developer options before flashing
have tried flashing back to half dozen different version stocks, deep clean flash, and various other work arounds I have seen on here to no avail
Only things that have PASS since the initial FAIL have been when I tried various BL individually, but no change in device
I am at the point that I can only access Download screen and ODIN still recognizes. Other option is the device starts to open in Recovery Boot, Installing Software Update comes up, about 10 lines of code start scrolling then phone goes black.
I'm still OFFICIAL, FRP Lock on, warranty void is 0x0 and AP SWREV is B5(2, 1, 1, 1, 1) K1 S4, and Secure Download is Enabled
I'm way past my comfort and capability in trying to get this even back to stock. Any guidance would be greatly appreciated... Finally broke free of the Sprint chains and on the edge of bricking my phone!
Click to expand...
Click to collapse
With the last ROM I've tried to use, on the device the red text comes up saying SW REV CHECK FAIL : [aboot] Fused 5 > Binary 2
Is there a different ROM I should be trying?

PA_Pyroholic said:
With the last ROM I've tried to use, on the device the red text comes up saying SW REV CHECK FAIL : [aboot] Fused 5 > Binary 2
Is there a different ROM I should be trying?
Click to expand...
Click to collapse
It sounds like you may have gotten sprint's update, not sure tho. Check your software version by going to about phone. If it ends with something like 5BRA1 (the 5 is whats important as that stands for binary ver. 5) then you might not be able to use the U firmware. You can try the U FW from this post: https://forum.xda-developers.com/sprint-s7-edge/how-to/successful-root-g935u-g935uueu4bqd2-t3598647
If that FW does not work, then you will either have to wait til they update the U FW to binary 5 or see if sprint can reload the OS, I would recommend asking them if they can give you an older version of the OS so you can use the U FW.

Fear_The_Fluff said:
It sounds like you may have gotten sprint's update, not sure tho. Check your software version by going to about phone. If it ends with something like 5BRA1 (the 5 is whats important as that stands for binary ver. 5) then you might not be able to use the U firmware. You can try the U FW from this post: https://forum.xda-developers.com/sprint-s7-edge/how-to/successful-root-g935u-g935uueu4bqd2-t3598647
If that FW does not work, then you will either have to wait til they update the U FW to binary 5 or see if sprint can reload the OS, I would recommend asking them if they can give you an older version of the OS so you can use the U FW.
Click to expand...
Click to collapse
I did get the update to 5 unfortunately and am no longer with sprint, paid everything off an account is closed. I did some more digging and realized many mistakes yesterday. I tried the latest 'U' FW (binary 4), it failed, and then I tried the latest 'P' FW (binary 5) right afterwards and it failed... But I didn't cycle the phone in between attempts so of course it was going to fail. Ended up reflashing with the latest 'P', and went through the easy, "just say yes to everything" set up and all the bloatware reloaded onto it. Reflashed and wiped device, and was careful this time... 90% of the bloatware I wanted was gone. Package disabled the rest. Only thing I can't seem to get rid of is the Sprint logos on start up.
After stumbling my way through this first attempt, I'll do better research next time!
Sent from my SM-G935P using Tapatalk

PA_Pyroholic said:
I recently carrier unlocked my SM-G935P (2016 version) from Sprint and brought it over to ATT. All was working fine but wanted to get rid of the Sprint bloatware. After spending most of the day reading threads of flashing, felt confident that I could walk through flashing over to "U" FW. This is my first attempt at flashing and it has FAILED!
Used ODIN 3.12 , and files from UPDATO
It failed after first attempt and then was stuck in boot loop
I then realized that I never set the Developer options before flashing
have tried flashing back to half dozen different version stocks, deep clean flash, and various other work arounds I have seen on here to no avail
Only things that have PASS since the initial FAIL have been when I tried various BL individually, but no change in device
I am at the point that I can only access Download screen and ODIN still recognizes. Other option is the device starts to open in Recovery Boot, Installing Software Update comes up, about 10 lines of code start scrolling then phone goes black.
I'm still OFFICIAL, FRP Lock on, warranty void is 0x0 and AP SWREV is B5(2, 1, 1, 1, 1) K1 S4, and Secure Download is Enabled
I'm way past my comfort and capability in trying to get this even back to stock. Any guidance would be greatly appreciated... Finally broke free of the Sprint chains and on the edge of bricking my phone!
Click to expand...
Click to collapse
Unfortunately, your phone is on the newest firmware, B5. You'll only be able to flash one of the latest sprint firmwares to get your phone to work. All the other carriers and U firmware are still running an older binary boot. You may also need the special version of ODIN...you can probably find it in the same forum about installing the U firmware. But if you download the latest sprint firmware, your phone should boot again.

Related

Soft-bricked AT&T S7 Edge trying to unroot / go back to stock

I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
vexx32 said:
I'd attempted (and succeeded) in rooting the s7 Edge without much of a problem, it seemed to be working fine. I was considering flashing a custom ROM as well, but before I could get to that point the phone started behaving oddly. It would refuse to boot, freezing at the AT&T logo screen and vibrating in a 1-3 pattern (1 vibration, then pause, then 3, etc., ad nauseum). I realised I still had ADB access at that point in boot (somehow, I have no idea) and used it to reboot to bootloader and see what I could do with Odin.
ALL VERSIONS of Odin I have tried (3.12, 3.12.3, PrinceComsy variants of both) have failed to restore the stock image and unroot the device. I have attempted to use multiple different stock images I've found around these forums and elsewhere, and all attempts have resulted in either the phone throwing an error about the Odin version I'm using, or Odin itself telling me that the flash failed and the phone indicating some strange message about the boot or the firmware being 'fused' or something. Exact error is SW REV CHECK FAIL : [system]Fused 3 > Binary 1
All I appear to have accomplished is preventing the device from ever booting properly -- it refuses to boot normally, and by default enters Recovery mode (the stock recovery, which is essentially useless and won't do anything at all). I would very much appreciate some help getting this device off the ground again; I'm sure we can figure something out together! As I type this, I am attempting yet another version of the stock firmware I've dug up, so... fingers crossed that gets some better results. If not... please help. Currently trying the APK1 version of the stock firmware.
Cheers,
vexx32
Click to expand...
Click to collapse
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
dirtydodge said:
You have to use either the stock version of the firmware that your phone was on or newer. You can't use any older versions. APK1 is the latest version i believe. Use the official Odin. The .12 version and you should be good.
Click to expand...
Click to collapse
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
vexx32 said:
Thankyou. It took me longer than it really should to figure out which firmware version to load. Downloading that now... fingers crossed, heh.
Do you think it's worth attempting to re-root and install a modified ROM on it for the performance tweaks that I've seen cropping up here and there? Or should I just count it lucky it's still mostly salvageable?
Click to expand...
Click to collapse
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
dirtydodge said:
Depends on what you want. Personally i would root it and go to the Verizon forum and download Stang5.0litre rom. That's an awesome rom. I'd stay away from echoe rom, seems like the devs are hit or miss on support. The dev for the stang rom is awesome and very active. I ran both of then and prefer stange.
Click to expand...
Click to collapse
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
vexx32 said:
Woah, woah, what? You can flash a rom based on another carrier? Will it still work? O.O
Click to expand...
Click to collapse
Yea it works. I know that one does. You'll get a message that says "unauthorized SIM card: or something like that. Just ignore it and use WiFi to setup the phone. Once you have it setup use package disabler or titanium to freeze "setup wizard" and that'll get rid of that notification. You'll have to manually setup your AT&T APN. After that your golden.

S7 SM-G930P ~ Boot Loader Issues? SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4

Hi All.
Thank you for any help you might give me in advance with this issue...
Last week, I tried to root the phone with the SM-G930P CF-Autoroot heroqltespr files with Odin found in this forum. I have rooted a few other phones but am no expert. The root after a few attempts failed (verified a few ways), however, some files must have been affected because the phone "identifies" as heroqltespr. Identifies as when I could plug into my PC heroqltespr would be the name. It was not set this way in the obvious name your device areas. I ended up doing a hard reset to clear the phone and other than the ghost naming everything was working fine.
A day or 2 ago Sprint rolled out a new OTA update which the phone installed. Since then the phone was draining battery life. After uninstalling and reinstalling the SD card today, it seems to have tripped a "Security Notice: Unauthorized Actions". That is when the trouble started. The phone started running hot, basically leaking battery power, and was all lagging. I'm assuming the CPU going Ludicrous speed.
Now, I am in a Samsung Splash screen loop, or or a recovery loop. The only thing it does is go into download mode.
I have tried flashing stock firmware, it fails. I've tried flashing with and without the SD or Sim card. Not really sure what I should be doing. The "P" version of my phone seems to be the bastard child of S7s. Any help you guys cold give me would be great. THANK YOU!
The Download Screen Reads:
Odin Mode (High Speed)
Current Binary: Samsung Official
System Status: Custom
FAP Lock: Off
Warranty Void: 8x8
Qualcomm Secure Boot: Enabled
AP SWREV: 85(2,1,1,1,1) K1 S4
I get this error when I try to flash back to stock SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
Stupid question but is your phone in a case?
Sw rev check fail : [aboot]fused 5 > binary 4
freakboysays said:
Stupid question but is your phone in a case?
Click to expand...
Click to collapse
No it isn't.
I get this error message on the download screen. SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
If you dont mind me asking, did you ever find a way to root the G930P with the 5th bootloader updates? Is it even possible at this point in time? Im new when it comes to rooting but with the amount of time Ive spent browsing the web it seems as if there is nothing. Thanks.
tonysak said:
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
Click to expand...
Click to collapse
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Chanman said:
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Click to expand...
Click to collapse
EDIT: Nevermind...sounds like you aren't on sprint.
lvpre said:
EDIT: Nevermind...sounds like you aren't on sprint.
Click to expand...
Click to collapse
Actually, I am on Sprint, and your directions were awesome, thank you so much! The only thing I had to do was change the line to:
settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
I'm going to put a link to the thread so others can refer to it. https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446
Hi all,
EDIT: I posted this in another thread that was about two years old, where I followed the instructions that caused this: https://forum.xda-developers.com/sp...msung-galaxy-s7-sm-g930p-root-xposed-t3503599
That thread seems dead-ish and if you managed to fix this issue maybe you can help me also. Also what was lvpre's original post before he edited it, and would it apply here?
So the worst has happened - got a new (used) phone from Boost Mobile, tried this guide, and now I can only boot to the "An error has occured while updating the device software. Use the Emergency Recovery function in the Smart Switch PC software." screen. Sometimes it does take me to the original "Download mode" screen.
Now, I should be able to resolve this by flashing the original firmware correct? (As in, the firmware that was installed when it came)? Or does it just need to be firmware from the same date range that has the same bootloader? ODIN will still let me attempt flashing on this screen, but I still get the same error when I try again, which on the Download mode screen showed "SW REV CHECK FAIL : [system]Fused 4 > Binary 1"
Any advice here? My S6 bricked when somehow OEM unlock enabled itself and I can't get around the FRP lock, I will be VERY annoyed if the same thing happens with a NEW phone. If I can't fix this I am never buying Samsung again. Any advice on this is very welcome! I emailed Boost to ask them which firmware is installed (because I'm an idiot and didn't write it down but have never had flashing go this wrong before).
EDIT: Booting to recovery just shows a blue "RECOVERY BOOTING...." for a second in the corner and gives a recovery bootloop, just keeps flashing that.
EDIT: I apparently tried to flash an earlier bootloader/etc through ODIN according to the directions in the post I linked above, and after that I now have this problem. Nobody else in the thread seems to have had this problem, and your post is the closest to anything I can find on this issue. I would be in your eternal debt if you could help me out here.
PLEASE HELP!
EDIT: Theoretically if I can find the original firmware it was on I should be fine, right? Everywhere I read if flashing goes wrong you just flash the original stock on it. I guess worst case scenario I download gigs upon gigs of firmwares for Sprint 930P over the last year and find the one that sticks? Or is the fact my recovery is bootlooping and I can only go into download mode mean I'm bricked?
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
slvmecha said:
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
Click to expand...
Click to collapse
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Switched from Sprint to T-Mobile. Am I out of luck?
lvpre said:
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Click to expand...
Click to collapse
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
jbuck2 said:
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
Click to expand...
Click to collapse
If your phone is uicc [sim] unlocked from sprint... you can try the following.
1. Odin a dec/Jan firmware...like QJ3. But replace the cp slot with the file from the latest u firmware. This is the modem file.
2. When your phone starts, you will receive a pop up message, just hit cancel.
3. Install a package disabler like sabs, bk, adhell2. Disable securitylogagent . This should remove the annoying message. Sabs takes a little effort to setup, but you may need it for the disabler part. Restart after disabling.
4. Pop in sim. See if the additional bands are unlocked.
If you fail, you can always just odin back to a v5 sprint firmware. But don't try it unless you are stuck on the current firmware and your phone is doing nothing. It won't brick your phone.
While the firmware is not downloadable, modem files can downgrade one major update.
This worked for me, but I only have sprint and haven't tried it elsewhere.
Here is an article https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/
Is this triggers the knox counter ?

downgrading problem oreo to nougat s8

hello,
i managed to get the phone back to get in download mode. stock everything, no root whatsoever. my goal is to root my phone and i have experience doing so but i guess i was just unlucky this time.
i tried searching allover the internet for a fix, searching xda etc.
first off: my device is running oreo 8.0 and it's type is G950FX.
I want to downgrade to 7.0 because FRP lock is on, i did turn on oem lock before starting however i am unable to log in to my old google account connected to my phone.
when i try to flash any bootloader i get SW REV CHECK FAIL DEVICE 2, BINARY 1. i tried almost any trick in the book like downloading 7.0 from sammobile, flashing using odin.
the things i run into when flashing are:
1.can't flash the bootloader, probably because of frp lock.
2. when i don't flash the bootloader for 7.0 i get dm-verity error 0x2.
3. when i only flash 8.0 oreo pda & csc and then flash 7.0 pda on top i do get to boot but i get encryption interrupted error.
4. i am able to boot in 8.0 but can't get past the frp.
i'm out of answers, i really hope anyone can help me out of this situation as i want to use my phone.
Help is much appreciated!
edit: i tried flashing multiple versions of android 7.0 but i keep getting sw rev check fail bootloader device 2 binary 1
i basicly want to do this, a downgrade: https://forums.androidcentral.com/s...s8-plus/878062-how-downgrade-oreo-nougat.html
the problem is i didn't sign out of google or samsung accounts before resetting to factory
You can't. You have a new bootloader v2.
A simple search gives you this answer, if you have u2 and CRED bootloader installed you are stuck. No way to go back anymore.
i'm on u2 and CRED bootloader. i did search for this indeed but i didn't want to give up.
do you think there will be ever be a way to get back into my phone again?
If you have FRP lock good luck. I haven't seen a way yet.
I know it's been 5 months and you've probably either gotten rid of the phone or it's sitting in a dusty bin somewhere, but have you tried Galaxy Reaper? It's a pretty legit FRP bypass tool.
Edit: Scratch that. It's apparently been patched since I last knew it to work. Just wanted to double check, and sure enough..

S7 Different PDA and Phone models.

I have an s7 edge that my buddy gave me, saying it stopped working after he tried to downgrade the OS or something, now the phone only boots to Factory Binary. On the back of the phone, it says it is a G935v, however, in the factory binary, it lists the model as G935a. So which firmware do I use to fix it? And if you could, how would I go about getting the phone to boot normally instead of in factory binary?
When booting into factory binary, the PDA is FA60_G945AUCU5ARA2, the model is SAMSUNG-SM-G935A [SS], and the Phone is G935VVRU4BQH4. To my knowledge these are listing as 2 different models. Also I tried to flash the official firmware from Sammobile, and I got errors like [aboot] Fused 5 > Binary 4, etc, every time.
I would really like to get this phone working. Thanks in advance!
Bump
If I remember correctly you can flash AT&T firmware on a Verizon. Not so sure about vice-versa. As for the errors in Download Mode, make sure you're not downgrading (e.g from 7.0 to 6.0)
And I think your phone was sold by Verizon and its firmware was changed to AT&T
Also, I found this
That is not good news.
Each time VZ updates their software for these phones, they update a value in a fuse.
That started as 1 with MDK, went to 2 with ME7, 3 with MI1, and 4 with MJ7. At least that's what I think the revisions did to the qfuse.
So it's seeing that you're trying to flash a binary with revision 3 (BINARY:3) but it remembers a flash with revision 5.
Now, there's nothing out there that I know of for the i545 that's rev 5 - the next update after MJ7 will be rev 5. So, your phone is probably not going to be recoverable until VZ and Samsung release another software update for the I545. Something corrupted the fuse storing the update level.
You can verify this by flashing MJ7 - it'll probably say FUSED:5, BINARY: 4.
Sorry for the bad news.
Click to expand...
Click to collapse
That was for a SGS4, so I guess the same applies today.
Im assuming the A following the 935 stands for AT&T, and the V would stand for Verizon. So according to what you quoted, I'm trying to "downgrade", and the OS wont allow it? Or am I misunderstanding?
Also for what it's worth, in recovery mode it says 6.0.1 is the current firmware, but again it is listing itself as 935A, and I can't get it to boot properly, it only goes to a "factory binary".
Yes. That's about it. Try flashing a Nougat or Oreo firmware.
Or
Try flashing a combination file and then an ordinary firmware
Sent from my SM-G935FD using Tapatalk
im having almost the same issue except it is saying Fused 8 binary 4. it is also a Verizon phone for sure. Everytime I look to find the exact firmware for nougat because I want to downgrade to get away from this stupid security update it keeps failing. any ideas?
codeb12 said:
im having almost the same issue except it is saying Fused 8 binary 4. it is also a Verizon phone for sure. Everytime I look to find the exact firmware for nougat because I want to downgrade to get away from this stupid security update it keeps failing. any ideas?
Click to expand...
Click to collapse
Check in the verizon section?

Sm-g955f bricked - flashing stock firmware only made it worse

Hi All,
So, I have spent 2 days trying to get my Galaxy s8+ back to normal. However, I seem to only have made it worse. It all happened when I decided to change the /data partition from ext4 to another format and then back again to get the /data partition to mount in TWRP after flashing Pascal Rom. However when I rebooted, nothing worked, no boot up screen, no recovery, no life, but all I could get was download mode. It then must of froze up after another restart and I couldn't get anything for 12 hours or so.
The next step I tried once i got download mode again was to flash stock firmware for the G955F, I can't remember the version of this firmware, but I still had nothing change. So then i flashed the latest firmware from SamFirm's downloading client, which was G955FXXU2CRF7 - Australian Optus Branded Firmware (OPS). I was able to get as far as the "hello start screen" and then my phone restarted, it then tried to upgrade my system again, then started "erasing" and then it rebooted and I still had the same issue, nothing but download mode and still no recovery, it still wouldn't turn on. So I flashed the latest International/Unbranded Australian firmware (XSA) - G955FXXU3CRGH, still the same result. I now can't go back to the OPS version of firmware because I get the Check error with the bootloader (since it's a more recent version), so I can't go backwards. I also can only flash "Official Binaries" now. Oh and to make things worse, I read that Odin Option "Nand Erase" just erased user data, so I thought I might as well try it, and as a result, I now can't flash even the (XSA) firmware because of ODIN failing and I now have an "An Error has Occurred while updating the device software. Use the emergency recovery function in the smart switch PC Software.". I am a bloody idiot :good: . Oh, I have tried multiple versions of Both Samsung Kies & Smart Switch (Which both had the option for "recovery & initialisation"), however, I get a message that my device is unsupported after adding in my device model and S/N. I tried a PIT file and then found out it's now included in all the latest firmware img files.. so yeah lol. Fun times. Soooo I feel like I am out of Options, nothing I do is working. The worst of all this is my wife is not happy haha which means after years of tinkering with android phones (flashing custom ROMS, Kernels, Root Solutions, e.c.t ), this may be the end of the road for me if I can't fix this phone. I really hope this thread isn't true too : https://forum.xda-developers.com/galaxy-s8+/help/sm-g955fd-access-download-mode-t3748228
So Please, someone help me out if it is at all fixable even if it requires opening the phone up lol.
The stats i have on download mode are the following:
RMM State as Prenormal
OEM Lock: OFF
FRP Lock: OFF
CARRIER_ID: OPS (which is super weird because it only accepts XSA to be flashed :S )
Secure download: Enabled
System Status: Custom
Warranty Void: 1
Current Binary: Samsun Official
If you need more, just let me know.
Ok, quick update: I have got rid of the error that I mentioned. I managed to flash XSA firmware again, it went to the blue Andriod is updating the system screen, then started "erasing" then rebooted and nothing again, still only download mode available. Nothing happens when I try to turn it on or try recovery mode.
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Quick Update: Maybe Fixed now!
Even though no one has replied yet, as it's only been an hour or so. I just wanted to let anyone else know who is experiencing a similar issue in the future on how to possibly fix it.
This was a real nightmare, however quick disclaimer, I am not responsible for any damage incurred to your device/property by following my instructions.
So the way I have fixed it, is I flashed the AP file only (from the firmware zip i had downloaded from SamFirm) with "Auto Reboot" Off. When ODIN finished, I held the Vol Down + power button, to reset it. It gave me a blue "No Command" Screen, I then waited and it then went black and the recovery screen appeared. I cleared the cache, rebooted to bootloader, which it didn't turn back on, so I left it because I thought it was the same thing. Came back 10 mins later and turned it on (or hard restarted, can't remember) and it worked. It booted!
I did soon learn it looks like it was having a charging problem because it had no charge and kept telling me there was water in the port (even though it was dry), I restarted it again after putting it on a wireless charging pad and it is seeming fine so far with the USB charger. So big note to anyone in the future, that it could be possibly bugging out with charging as well if you can't get it back on. I did have the device tell me here and there the last two days that there was water in the port when it was off. So kinda weird.
I know this all sounds a little hocus pocus, superstitious almost, but hey, my phone is working, so maybe replicating my actions may just help lol. :cyclops:
spawnlives said:
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Click to expand...
Click to collapse
Oh right, well, I did hear that SamFirm is not supported anymore, as that's where that firmware came from. Maybe it's dishing out incorrect firmware now? Possible the structure of where ever it is getting its firmware from (pretty sure it's pulled from samsung) has possibly been altered?
Just for reference I use www.updato.com for downloading firmware it is usually up to date. No reference to the firmware you mentioned (not for Australia anyway)
The screenshot I took: Imgur link:
https://imgur.com/a/lqyzWW7
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
spawnlives said:
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
Click to expand...
Click to collapse
Yeah, it's seeming to work now, but my fast charge isn't working. However, my other oreo ROM didn't work with fast charge either. So i am unsure if it is my phone or an orio bug :/ lol
Well at least you got it working and not using as a door stop
that was really sad story man.....
spawnlives said:
Well at least you got it working and not using as a door stop
Click to expand...
Click to collapse
Yeah haha, so glad it's not a door stop haha

Categories

Resources