Related
Hello guys,
I bought a soft bricked S7 Edge with a dm-verity error because I thought I could easily fix the issue myself. The previous owner said he went to update the samsung software via android and this happened. But it doesn't seem too easy to fix. I've tried a bunch of different solutions I found on the interwebs but none have worked so far. I would appreciate some help because I don't seem to be making any progress.
EDIT: I've read that some people have reported losing their IMEI after an OTA update. Maybe that is what happened?
NOTE: I do NOT get the "failed to mount /efs" error
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom. So here is what I tried:
1 . First I did the obvious, facotry reset and wipe partition. No change.
2. Downloaded the firmware with SamFirm (SM-G935F Regin ZTO) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error. Then returned to Android Recovery. Observation: When I extracted the firmware, I got a strange corrupted error. I downloaded it again, same corruption error. Is that normal? Also, I am not certain the region is ZTO, maybe this phone is from some other region. Does it matter?
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I tried to flash CF-autoroot but it gave an error in Odin and failed. EDIT: failed because "Blocked by FRP Lock" but I can't unlock the OEM like everyone else because I can't boot normally into android. Any workaround?
5. I downloaded firmware from a different region (UK). I got a DRK error and it booted into Android recovery. The bottom of the phone reads:
No Support SINGLE-SKUSupported API: 3dm-verity error...failed code : 0x02
6. I flashed the combination file and was able to boot into Factory Binary. I went into Settings to unlock OEM but there isn't that option in the Developer Settings!
That's where I am now. Any ideas?
Thanks!
Are you sure that it is an original 935F?
Pet1981 said:
Are you sure that it is an original 935F?
Click to expand...
Click to collapse
On the back of the phone, its has the model number written like this SM-G935F SAMSUNG YATELEY GU46 6GG UK. Is there someway for this to be wrong?
dleeII said:
On the back of the phone, its has the model number written like this SM-G935F SAMSUNG YATELEY GU46 6GG UK. Is there someway for this to be wrong?
Click to expand...
Click to collapse
Samsung Yateley is Samsung's official UK QA facility, they only receive official products direct from the factories and those sent back for repair and refurbishment. I know this because it's literally just down the road from my house and a couple of friends have worked there over the years.
However, "SAMSUNG YATELEY GU46 6GG UK" has been on literally millions of devices worldwide for years.
It's not a reliable Indication of a genuine product or in fact an indication of anything other than the fact that Samsung have a facility in Yateley.
If the device is a refurb or even a fake it's entirely possible that it only says "SM-G935F SAMSUNG YATELEY GU46 6GG UK" because that's what it's supposed to say.
I'm sorry that I can't be of any more help but, I hope I've helped by stopping you from embarking on a wild goose chase.
X1ras said:
Samsung Yateley is Samsung's official UK QA facility, they only receive official products direct from the factories and those sent back for repair and refurbishment. I know this because it's literally just down the road from my house and a couple of friends have worked there over the years.
However, "SAMSUNG YATELEY GU46 6GG UK" has been on literally millions of devices worldwide for years.
It's not a reliable Indication of a genuine product or in fact an indication of anything other than the fact that Samsung have a facility in Yateley.
If the device is a refurb or even a fake it's entirely possible that it only says "SM-G935F SAMSUNG YATELEY GU46 6GG UK" because that's what it's supposed to say.
I'm sorry that I can't be of any more help but, I hope I've helped by stopping you from embarking on a wild goose chase.
Click to expand...
Click to collapse
I flashed the combination software and in the Factory Binary, it says MODEL: SM-G935F [SS]. Is the information reliable? Is there a possibility that the phone is fake? If so, is there a way to tell for sure?
EDIT: I checked the IMEI I got from the Factory Binary at IMEI.info and it seems to be valid.
I don't know
THIS
can help you or not
Try to use z3x box i read some function of z3x box but i'm not sure if it will fix your phone. Just go to gsm-forum for more details.
I thought this error message you're getting is because you flashed something on your phone intended for another model. I got the same error when I first got my S7 Edge because I stupidly thought I had the snapdragon variant when in fact the G935F is the Exynos variant. I got exactly the same error message. Have you tried reflashing stock firmware via Odin? Have you checked the Knox trip counter to see if the phone had been tampered with prior to you buying it? I live a stone's throw away from Yateley (5 mins maximum) if you want me to pop in and enquire?
Sent from my SM-G935F using XDA-Developers Legacy app
Sorry for the delayed response. I left my phone with some technicians with a ZX3 and Octopus Box and they were unable to fix the phone. But they didn't seem very interested either so maybe they just blew me off. Not sure. I'll try to find someone else soon.
speedyjay said:
I thought this error message you're getting is because you flashed something on your phone intended for another model. I got the same error when I first got my S7 Edge because I stupidly thought I had the snapdragon variant when in fact the G935F is the Exynos variant. I got exactly the same error message. Have you tried reflashing stock firmware via Odin? Have you checked the Knox trip counter to see if the phone had been tampered with prior to you buying it? I live a stone's throw away from Yateley (5 mins maximum) if you want me to pop in and enquire?
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
This may be the problem. I have tried flashing the stock firmware with Odin but maybe I'm flashing the snapdragon variant instead of the exynos. How can I tell the difference?
My warranty is 1 (0x0500). That means that Knox was tripped right?
mashardpro said:
I don't know
THIS
can help you or not
Click to expand...
Click to collapse
I've tried this guide and it didn't solve the issue.
I tried flashing a Snapdragon firmware and it failed. So I assume a Exynos firmware is the correct one.
dleeII said:
I tried flashing a Snapdragon firmware and it failed. So I assume a Exynos firmware is the correct one.
Click to expand...
Click to collapse
G935F is exynos yes
Have you tried OEM unlock via adb if possible?
Then flash twrp and https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip ?
Sorry if it's not possible just brainstorming ..
misterashman said:
G935F is exynos yes
Have you tried OEM unlock via adb if possible?
Then flash twrp and https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip ?
Sorry if it's not possible just brainstorming ..
Click to expand...
Click to collapse
No, I haven't tried that yet. How do I access the S7 via adb again? Is it in download mode or in the recovery? Samsungs don't have "fastboot" right?
I'm in the exact same situation, it's FRP locked to me but I can't get passed the DM-Verity to unlock nor root to pass DM-Verity. Hard to believe this could be bricked from a software issue.
---------- Post added at 05:14 PM ---------- Previous post was at 04:44 PM ----------
dleeII said:
No, I haven't tried that yet. How do I access the S7 via adb again? Is it in download mode or in the recovery? Samsungs don't have "fastboot" right?
Click to expand...
Click to collapse
Did you ever find a solution?
Hey, I was able to unbrick the phone. But I had to take it to a technician that used a very interesting technique to reset the phone. Apparently, someone had tried to flash another IMEI on the phone. To reset the device, he switched out one of the memories (there are 3 or 4 slots). Then when you boot up the phone, it is tricked into thinking you are booting up for the first time. At leas that is what I understood. Maybe someone more familiar with phone hardware could explain the solution better.
Rymcbc said:
I'm in the exact same situation, it's FRP locked to me but I can't get passed the DM-Verity to unlock nor root to pass DM-Verity. Hard to believe this could be bricked from a software issue.
---------- Post added at 05:14 PM ---------- Previous post was at 04:44 PM ----------
Did you ever find a solution?
Click to expand...
Click to collapse
Did you ever find a solution?
dleeII said:
Hello guys,
I bought a soft bricked S7 Edge with a dm-verity error because I thought I could easily fix the issue myself. The previous owner said he went to update the samsung software via android and this happened. But it doesn't seem too easy to fix. I've tried a bunch of different solutions I found on the interwebs but none have worked so far. I would appreciate some help because I don't seem to be making any progress.
EDIT: I've read that some people have reported losing their IMEI after an OTA update. Maybe that is what happened?
NOTE: I do NOT get the "failed to mount /efs" error
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom. So here is what I tried:
1 . First I did the obvious, facotry reset and wipe partition. No change.
2. Downloaded the firmware with SamFirm (SM-G935F Regin ZTO) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error. Then returned to Android Recovery. Observation: When I extracted the firmware, I got a strange corrupted error. I downloaded it again, same corruption error. Is that normal? Also, I am not certain the region is ZTO, maybe this phone is from some other region. Does it matter?
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I tried to flash CF-autoroot but it gave an error in Odin and failed. EDIT: failed because "Blocked by FRP Lock" but I can't unlock the OEM like everyone else because I can't boot normally into android. Any workaround?
5. I downloaded firmware from a different region (UK). I got a DRK error and it booted into Android recovery. The bottom of the phone reads:
No Support SINGLE-SKUSupported API: 3dm-verity error...failed code : 0x02
6. I flashed the combination file and was able to boot into Factory Binary. I went into Settings to unlock OEM but there isn't that option in the Developer Settings!
That's where I am now. Any ideas?
Thanks!
Click to expand...
Click to collapse
You tried smart switch if identify the device and instal stock rom?
bricked S7 Edge with a dm-verity error
dleeII said:
Hello guys,
I bought a soft bricked S7 Edge with a dm-verity error because I thought I could easily fix the issue myself. The previous owner said he went to update the samsung software via android and this happened. But it doesn't seem too easy to fix. I've tried a bunch of different solutions I found on the interwebs but none have worked so far. I would appreciate some help because I don't seem to be making any progress.
EDIT: I've read that some people have reported losing their IMEI after an OTA update. Maybe that is what happened?
NOTE: I do NOT get the "failed to mount /efs" error
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom. So here is what I tried:
1 . First I did the obvious, facotry reset and wipe partition. No change.
2. Downloaded the firmware with SamFirm (SM-G935F Regin ZTO) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error. Then returned to Android Recovery. Observation: When I extracted the firmware, I got a strange corrupted error. I downloaded it again, same corruption error. Is that normal? Also, I am not certain the region is ZTO, maybe this phone is from some other region. Does it matter?
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I tried to flash CF-autoroot but it gave an error in Odin and failed. EDIT: failed because "Blocked by FRP Lock" but I can't unlock the OEM like everyone else because I can't boot normally into android. Any workaround?
5. I downloaded firmware from a different region (UK). I got a DRK error and it booted into Android recovery. The bottom of the phone reads:
No Support SINGLE-SKUSupported API: 3dm-verity error...failed code : 0x02
6. I flashed the combination file and was able to boot into Factory Binary. I went into Settings to unlock OEM but there isn't that option in the Developer Settings!
That's where I am now. Any ideas?
Thanks!
Click to expand...
Click to collapse
I Also Have this problem with Samsung SM-G935F
I Solved This Problem With Small Trick
1. Flash Phone With Official Firmware
2. Flash Twrp Recovery
3. Wipe All Data Leave System
4. Reboot
Now I got My device back Alive
You Can Try May Be Its Works For You
I tried the same and my fone booted but its very unstable with crashing apps and random restarts...
With smart switch it ends into dm varity verification hash tree error or dm-varity error
Any solutions...
Please check my answer for the S8+ I believe it should be the same process.
https://forum.xda-developers.com/showpost.php?p=75342726&postcount=10
Good Luck
need urgent help really.
my phone has been rooted and has twrp installed for months now with no issues, all of a sudden my phone rebooted to the samsung logo screen with the mentioned error message. i have no idea how and why this error has occured but my phone wont boot to system. i really dont want flash stock firmware as i havent backed things up, is there a way to fix this issue with out doing a full wipe?
you might have accidentally disable oem unlock. so phone is bricked , and you need to flash stock firmware with odin , no other choices . and as you know knox counter will stay 0x1 , root or no root, once you break knox its permanent as knox is hardware, once you root it break an electronic fuse so once you flash stock firmware I really suggest you to install custom rom and twrp again as many things will be blocked if you stay on stock firmware as your device will stay marked as " rooted "
robhug said:
you might have accidentally disable oem unlock. so phone is bricked , and you need to flash stock firmware with odin , no other choices . and as you know knox counter will stay 0x1 , root or no root, once you break knox its permanent as knox is hardware, once you root it break an electronic fuse so once you flash stock firmware I really suggest you to install custom rom and twrp again as many things will be blocked if you stay on stock firmware as your device will stay marked as " rooted "
Click to expand...
Click to collapse
Yeah I had to do firmware install in the end. It's just crazy though. I very rarely go into dev options, I had noto kernel installed and everything on stock aqh3, rooted with magisk and everything worked great, so annoying as this happened at 3am and I have slow internet connection and took me 2 hours to download the 3.5gb firmware file. Urgh o was on the verge of installing a custom rom too, ah well good job I had a lot of stuff saved in Samsung cloud.
sofir786 said:
Yeah I had to do firmware install in the end. It's just crazy though. I very rarely go into dev options, I had noto kernel installed and everything on stock aqh3, rooted with magisk and everything worked great, so annoying as this happened at 3am and I have slow internet connection and took me 2 hours to download the 3.5gb firmware file. Urgh o was on the verge of installing a custom rom too, ah well good job I had a lot of stuff saved in Samsung cloud.
Click to expand...
Click to collapse
yes hopefully cloud is our new god ^^ yes its annoying I agree but its also a great feeling to begin with a clean phone like new after a reset , and I have also a crappy download speed so yes its a pain to download 4gb , and even better when its corrupted and need to download agin good luck with your device
Hey guys I need help.
My phone got bricked as you said (I accidentally turned off OEM unlock on my rooted phone) so I tried to flash stock firmware, but odin fails and on my phone it says (sw rev. check fail. device:3 binary:2). Plz help!
My phone: S8+
FIRMWARE: CRF7
FRP LOCK: ON
OEM LOCK: ON
Just had the very same problem meself ?
Thank god for Odin and https://updato.com/
Bt like previous posters says its like havin a new phone apart from samsung pay not working
Can someone help??
I got the "FRP lock" on my Samsung S8 (Exynos) and tried to flash Stock Oreo but Odin fails and the device shows "KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2".
This stock Samsung Rom worked earlier today so it should be the right Rom for my phone.
Also tried to flash TWRP recovery via AP in Odin which failed with "RFP lock" message showing on the device..
I tried to add a snapshot here but couldn't.
Anyone please, I'm helpless..
nattyniz said:
Can someone help??
I got the "FRP lock" on my Samsung S8 (Exynos) and tried to flash Stock Oreo but Odin fails and the device shows "KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2".
This stock Samsung Rom worked earlier today so it should be the right Rom for my phone.
Also tried to flash TWRP recovery via AP in Odin which failed with "RFP lock" message showing on the device..
I tried to add a snapshot here but couldn't.
Anyone please, I'm helpless..
Click to expand...
Click to collapse
Your issue is trying to flash older firmware than what is on your phone. You will need to download firmware with bootloader ver. 3 or higher ( bl ver no. is 5th number from right of firmware name )
Flashing twrp failed because of locked bootloader.
spawnlives said:
Your issue is trying to flash older firmware than what is on your phone. You will need to download firmware with bootloader ver. 3 or higher ( bl ver no. is 5th number from right of firmware name )
Flashing twrp failed because of locked bootloader.
Click to expand...
Click to collapse
That helped. Flashing the right version worked just fine.
Thanks!!
FRP lock
Hi people,
I got the "FRP lock" on my Samsung S8 SM-G950F(Exynos) and tried to flash Stock Oreo but when I press start Odin say PASS but recovery won't start.
please help
i flashed my S8 SM-G9500 variant however the phone has been locked and it is saying that i need to see the samsung service provider for the device has been locked. how can i solve this problem
Mark Nyombi said:
i flashed my S8 SM-G9500 variant however the phone has been locked and it is saying that i need to see the samsung service provider for the device has been locked. how can i solve this problem
Click to expand...
Click to collapse
can you get a pic of the screen youre talking about?
Hello guys i rooted my S8+ G-955F and i turned off usb debugging and ome lock
And i have android 9 installed on my device, i tried all the way but for nothink , any help please
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 ?
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.
Hey i couldnt find anything else so i hope this isnt a duplicate,
im somewhat of a noob when it comes to rooting but i know a little bit
Today i rooted my Galaxy s8 , everything whet smooth and without a problem,
but then for some reason i deactivated the OEM unlock and rebooted my phone.
Obviously that locked me out of my phone, after trying to flash my phone with the stock firmware that i downloded through samfirm
i got the error sw rev check fail bootloader device 5 binary 4 and i couldnt get that to work.
My next step was to try the Samsung smart switch emergency recovery, which failed.
I got the error that my device was not supported.
After that my S8 also stared showing me a blueish screen with the message : "An error has occurred while updating the device software....",
i can still access downlod mode tho
At this point i really dont know what to do and i should really be in bed because its 2 in the morning .
I really hope someone can help me out here, thanks in advance and a good night for now.
Hirnvitamin said:
Hey i couldnt find anything else so i hope this isnt a duplicate,
im somewhat of a noob when it comes to rooting but i know a little bit
Today i rooted my Galaxy s8 , everything whet smooth and without a problem,
but then for some reason i deactivated the OEM unlock and rebooted my phone.
Obviously that locked me out of my phone, after trying to flash my phone with the stock firmware that i downloded through samfirm
i got the error sw rev check fail bootloader device 5 binary 4 and i couldnt get that to work.
My next step was to try the Samsung smart switch emergency recovery, which failed.
I got the error that my device was not supported.
After that my S8 also stared showing me a blueish screen with the message : "An error has occurred while updating the device software....",
i can still access downlod mode tho
At this point i really dont know what to do and i should really be in bed because its 2 in the morning .
I really hope someone can help me out here, thanks in advance and a good night for now.
Click to expand...
Click to collapse
Device 5 binary 4 means you are flashing lower version of firmware than what is on your phone. Samsung will let you downgrade ( bootloader ) versions numbers.
You will need to flash a bootloader 5 or higher to fix.
Note: Don't relock oem in developer option.
spawnlives said:
Device 5 binary 4 means you are flashing lower version of firmware than what is on your phone. Samsung will let you downgrade ( bootloader ) versions numbers.
You will need to flash a bootloader 5 or higher to fix.
Note: Don't relock oem in developer option.
Click to expand...
Click to collapse
Thanks for your reply!
That's what I found out too but I couldn't find a "higher" bootloader, I would have thought that if I download it through SamFirm it should have the proper BL
Do you have any recommendations on where to download the proper bootloader?
Yea that was a big f**k up haha
I just tried to get Poke Go to run but it wouldn't let me login because it detected that the Device was rooted I guess and after changing my device fingerprint and adding PokeGo to MagiskHide and still not being able to login I followed some FAQ blindly Wich recommended to turn off OEM unlock, and other things to hide the hardware site or the root, thinking about it again it should have been super obvious that this is a stupid idea, but you are always smarter afterwards right? Haha
spawnlives said:
Device 5 binary 4 means you are flashing lower version of firmware than what is on your phone. Samsung will let you downgrade ( bootloader ) versions numbers.
You will need to flash a bootloader 5 or higher to fix.
Note: Don't relock oem in developer option.
Click to expand...
Click to collapse
Wow I feel stupid, I'm flashing the stock through Odin right now as I type this, I've downloaded 2 firmwares first one was a random one from online second one was the SamFirm , after realizing the first didnt work I must have deleted the samfirm variant by accident, I redownloaded it and now it's working , but thanks for replying!