Hey guys! Thanks for reading.
I was trying to flash stock FW to my phone (SM-G530MU, G530MUUHU1AOA2), but i couldnt do it. I downloaded almost all FW available in SAMMOBILE, but all gave me the auth error in odin.
I thought it was because of the recovery, so i flashed the Phil one. Still no luck.
Then I formatted and wiped through recovery, thinking that would be a good way to have everything to stock.
After that, the phone wont get past the Glaxy Grand Prime logo with androidn at the bottom.
I still cante get ODIN to flash any FW because of that Auth error. Have no idea how to fix it.
Also i tried KIES, but once i enter all infor, it simply says "Failed to run firmware update. Unknown error occured".
So yeah, please help. Dont know what to do. Thanks!
I fixed it! Close this Mods! Finally i went to Samsung and they provided me the original firmware for my model. Thanks
I switched from iphone to android recently and i tried to root. Something went wrong because it told me the root didn't work and I couldn't text or make calls. I tried to unroot it but that made it get stuck in a boot loop, where the phone keeps booting up to the hands free activation screen, failing, and rebooting again. I was told the only fix was flashing the stock firmware. I tried searching and I came up with no results for my model number (G935S). Is there either a place that does have my model number, or a way to put a firmware that doesn't match my model on the phone?
Also, I have a backup of my phone and don't know how to put it back on my phone after a factory reset.
i've used updato.com to find/download firmware for my 935FD. here's a link for the 935S S7 edge; not sure however, which version would apply to your phone. GALAXY S7 edge | SM-G935S.
Thank you. Although i put the wrong model by mistake. It shouldv'e been G935PV
HorribleJoysticks said:
Thank you. Although i put the wrong model by mistake. It shouldv'e been G935PV
Click to expand...
Click to collapse
Hi. This should be the latest version of firmware you looking for: http://www.sammobile.com/firmwares/download/85625/G935PVPS2APG1_G935PSPT2APG1_SPR/
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
I have a Samsung Galaxy S7 Edge, I thought I was smart enough to try and root the phone but I was wrong. Now it is in a bootloop. I have tried everything...I did a factory reset, flashed, cleared the cache partition, I have used Kies3, Smart Switch, ADB server, Odin , I tried it all and now I am just needing help if anyone can help me.
I tried to go back to Kies3 but it keeps rejecting my serialnumber for some reason, I even went back to the recovery log in the recovery console to make sure the serial number was right. I also thought maybe I flashed the wrong firmware with Odin? I am not sure I got the right one because I amnot sure what PDA means on the download site, so I am just lost now. The only thing it does is a bootloop and I can get to recovery console, and the bootloader.
If anyone can help I would so appreciate it.
pinkgeek said:
I have a Samsung Galaxy S7 Edge, I thought I was smart enough to try and root the phone but I was wrong. Now it is in a bootloop. I have tried everything...I did a factory reset, flashed, cleared the cache partition, I have used Kies3, Smart Switch, ADB server, Odin , I tried it all and now I am just needing help if anyone can help me.
I tried to go back to Kies3 but it keeps rejecting my serialnumber for some reason, I even went back to the recovery log in the recovery console to make sure the serial number was right. I also thought maybe I flashed the wrong firmware with Odin? I am not sure I got the right one because I amnot sure what PDA means on the download site, so I am just lost now. The only thing it does is a bootloop and I can get to recovery console, and the bootloader.
If anyone can help I would so appreciate it.
Click to expand...
Click to collapse
If you have Bootloader it can be fixed. Download the firmware from sammobile and put the files in the spot it says it is. PDA file will go to PDA etc.
Edit. Sorry forgot that PDA is the old Odin. Download the newer version v3.12 and put the AP files in the AP slot and the same with the CP file and CSC. You might wanna try leaving the BL file out as when I did mine it would only work if I didn't add BL.
I had quite the same thing. I rooted my S7 Edge abd installed Lineage, but I was not satisfied of it, so I decided to come back to stock ROM. This was impossible : flash with Odin, with TWRP, etc... All came to a bootloop or freeze when the phone booted.
And yesterday, after a new attempt, the phone booted and now, it works very well. I don't really understand what changed or what I did more, but it seems that your phone is not bricked. Try another Odin flash with forcing CSC maybe.
I accidently flashed my phone with the wrong version of firmware when i was trying to root the phone and now it wont boot and says it is a different phone. Any suggestion on where i can get firmware to at least get my phone to boot again. Model number is SM-G935V. I tried sammobile but it failed when running odin on my pc unless i didnt do it correctly. Any suggestions to get my phone back tonworking conditions. I have a macbook as a computer right now but could have access to a pc on tuesday.
Thank you
I guess the question would be what exactly was the firmware that you flashed? What is the firmware number. Just want to make sure you didnt flash something that cant be undone.