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
Related
(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
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 used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!
Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.
Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.
JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously
Good luck.
Deleted
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.
sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you
Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082
hello, i just bought a used note 4 (SM-N910F) today.
And when i went into the download mode to install latest stock firmware using Odin, i found that the product name is wrongly listed as SM-N910T3.
Eventhough the phone is shown as N910F on the box and in the settings menu too.
Anyways, i still went ahead and tried to put the latest firmware of n910f into it using odin and i got the error message - emmc write fail aboot.
I then came out of it and tried to factory reset it from the settings menu which then took me to the recovery menu for some reason instead and showed me various options including wipe factory data reset.
And below that i was getting this error message in red that "dm-verity verification failed"
I still went ahead and performed the wipe, during which i got the error message "e failed to mount/preload (no such file or directory".
After that i rebooted the phone and thankfully after waiting for 15+mins it booted up and seemed to have reset the phone.
But now I'm pretty sure the earlier owner messed up n installed the wrong firmware for it besides rooting it (as shown by the knox trip count).
So my question is, how do i install the correct firmware for it?
thanks for any help.. will be greatly appreciated.
A.Ahmed79 said:
hello, i just bought a used note 4 (SM-N910F) today.
And when i went into the download mode to install latest stock firmware using Odin, i found that the product name is wrongly listed as SM-N910T3.
Eventhough the phone is shown as N910F on the box and in the settings menu too.
Anyways, i still went ahead and tried to put the latest firmware of n910f into it using odin and i got the error message - emmc write fail aboot.
I then came out of it and tried to factory reset it from the settings menu which then took me to the recovery menu for some reason instead and showed me various options including wipe factory data reset.
And below that i was getting this error message in red that "dm-verity verification failed"
I still went ahead and performed the wipe, during which i got the error message "e failed to mount/preload (no such file or directory".
After that i rebooted the phone and thankfully after waiting for 15+mins it booted up and seemed to have reset the phone.
But now I'm pretty sure the earlier owner messed up n installed the wrong firmware for it besides rooting it (as shown by the knox trip count).
So my question is, how do i install the correct firmware for it?
thanks for any help.. will be greatly appreciated.
Click to expand...
Click to collapse
Your original model is SM-N910T3 thats Tmobile note 4 usa model not the N910F European model.
Your original.model is shown correct in download mode that's your motherboard model.
Probably its refurbished device with Modified software and box and sticker behind the battery just for looks like N910F international model because N910F has more value in market.
I personally had same experience before as you i bought N910F online and i found it was N910P sprint usa model in download mode.
Dont try to flash any N910F firmware your device may end up hard brick and completly useless
you can flash N910T3 firmware it will flash without errors.
Trex888 said:
Your original model is SM-N910T3 thats Tmobile note 4 usa model not the N910F European model.
Your original.model is shown correct in download mode that's your motherboard model.
Probably its refurbished device with Modified software just for looks like N910F international model because N910F has more value in market.
Dont try to flash any N910F firmware your device may end up hard brick and completly useless
you can flash N910T3 firmware it will flash without errors.
Click to expand...
Click to collapse
ok thanks alot, i'll try to download a N910T3 firmware and retry and update here again.
Hi, my SM-G935FD has been acting weird lately, auto reboot and massive hanging issue. Thus i decided to do a factory reset. To my surprise, the factory reset was unable to complete!
It shows error E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
Now i cant do anything with my phone, i tried to flash using odin with various stock, but it stucks at system.img. I cant do a custom rom flash either because FRP Lock is ON.
Any experts out there able to provide with some help and your expertise?
Your help is greatly appreciated!
grasscut said:
Hi, my SM-G935FD has been acting weird lately, auto reboot and massive hanging issue. Thus i decided to do a factory reset. To my surprise, the factory reset was unable to complete!
It shows error E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
Now i cant do anything with my phone, i tried to flash using odin with various stock, but it stucks at system.img. I cant do a custom rom flash either because FRP Lock is ON.
Any experts out there able to provide with some help and your expertise?
Your help is greatly appreciated!
Click to expand...
Click to collapse
Use Samsung smart switch to restore your phone to stock just type your serial number in it I think it works even without ur screen on.
pingufanpoy said:
Use Samsung smart switch to restore your phone to stock just type your serial number in it I think it works even without ur screen on.
Click to expand...
Click to collapse
Tried that too. But it stated does not support. So i cant do anything with it
anyone help?
same thing here on G935FD. Started acting up after Oreo update
Samsung refusing warranty claim as my phone bought in another country.
Bluetoth10 said:
same thing here on G935FD. Started acting up after Oreo update
Samsung refusing warranty claim as my phone bought in another country.
Click to expand...
Click to collapse
Any experts can give us a hand?
i received 2 pm from this user instrumentaly who claims to know how to resolve the issue. but he is asking for remote access to my phone to his server. I think its likely a scam? anyone received such pm from this user?
No more help with this? I am stuck in loop with installing system update and then the samsung logo screen.
Contact me in 8921154867 Whatsapp
Let me try if I can help you(If you want)
[emoji3][emoji3][emoji3][emoji3]
Sent from my Lenovo K33a42 using Tapatalk
Cant use phone lol! It's not letting me past loading screens or installing update.
i received 2 pm from this user instrumentaly who claims to know how to resolve the issue. but he is asking for remote access to my phone to his server. I think its likely a scam? anyone received such pm from this user?
I/O error most likely means the internal storage has failed, to be sure use samfirm to download the latest firmware for your device. Check the binary nature box to get the full firmware and flash with odin.
DrFredPhD said:
I/O error most likely means the internal storage has failed, to be sure use samfirm to download the latest firmware for your device. Check the binary nature box to get the full firmware and flash with odin.
Click to expand...
Click to collapse
I am unable to flash the firmware to the phone. it stuck when its at system..
grasscut said:
I am unable to flash the firmware to the phone. it stuck when its at system..
Click to expand...
Click to collapse
Unfortunately this does sound like an eMMC failure.
DrFredPhD said:
Unfortunately this does sound like an eMMC failure.
Click to expand...
Click to collapse
So my phone is dead then? nothing i can do to salvage it?
Hi all 0/
I'm creating this post because well I have a bricked phone (I know, another bricked phone thread) and am asking if anybody can help or point me in the directions of help.
P
The Problem
So my phone failed to install the latest security update that was released in September; just gave me the update failed error on reboot. I ignored this for a month as it didn't bother me but it started to get progressively more buggy, random crashes then random restarts then google play services just stopped working. This point I looked into it and the internet told me to use smartswitch to apply the update (which I assumed to be the problem at the time). Smartswitch couldn't update it which through it into emergency recovery mode. Smartswitch was then blocked by FRP lock when I tried to use emergency recovery mode.
I then tried by use Odin to flash stock firmware, which FRP lock blocked. Now i'm stuck as I can't flash anything with odin or use smartswitch so am stuck with either download mode of emergency recovery page.
I have extracted and reflashed all the sys.img flash expect system which has allowed me to boot to recovery but have the error
DM verity failed
E/ failed to mount system (invalid argument)
All the fixes for dm verity failed system, frp lock etc don't work as i think i have a combination of problems
Neither have I found a post that describes this problem anywhere
Thank you very much for reading
If you can boot the phone do you know the google email and password to remove the fpr?
godkingofcanada said:
If you can boot the phone do you know the google email and password to remove the fpr?
Click to expand...
Click to collapse
Yes I do, which is the most annoying part!
Skyscripter said:
Yes I do, which is the most annoying part!
Click to expand...
Click to collapse
Don't use Odin, use the actual Samsung app smart switch and factory restore/emergency mode restore option.
godkingofcanada said:
Don't use Odin, use the actual Samsung app smart switch and factory restore/emergency mode restore option.
Click to expand...
Click to collapse
That's what I originally tired and it gets blocked by the frp lock
Skyscripter said:
That's what I originally tired and it gets blocked by the frp lock
Click to expand...
Click to collapse
The fpr lock isn't supposed to block you from installing official factory firmware. But it has to be the exact firmware. It should install and then ask for your gmail
godkingofcanada said:
The fpr lock isn't supposed to block you from installing official factory firmware. But it has to be the exact firmware. It should install and then ask for your gmail
Click to expand...
Click to collapse
That's what I thought, but when I've tried to use smart switch it blocks me, and every version of firmware I've found with odin it blocks. How can I find out which firmware my phone was on before it bricked its self? or do you think its a case of trying many?
assuming smartswitch is unable to find the firmware that i need is there any way of telling it which version to flash?
Skyscripter said:
That's what I thought, but when I've tried to use smart switch it blocks me, and every version of firmware I've found with odin it blocks. How can I find out which firmware my phone was on before it bricked its self? or do you think its a case of trying many?
assuming smartswitch is unable to find the firmware that i need is there any way of telling it which version to flash?
Click to expand...
Click to collapse
Smartswitch can't flash it because whatever crapped out changed the device ID or some info it looks to for authentication. I had that happen once. After a fw flash my phone changed from SM-G928W8 to G928F and smart switch wouldn't touch it. So what I had to do was find the exact match, you need to know what carrier your phone came from to get the model for firmware, like t mobile or Verizon, and then get that version, I think nougat or mm would work but our device shipped with mm. Odin will work but it the fw has to match the device. Then once it boots your gmail info is needed.
godkingofcanada said:
Smartswitch can't flash it because whatever crapped out changed the device ID or some info it looks to for authentication. I had that happen once. After a fw flash my phone changed from SM-G928W8 to G928F and smart switch wouldn't touch it. So what I had to do was find the exact match, you need to know what carrier your phone came from to get the model for firmware, like t mobile or Verizon, and then get that version, I think nougat or mm would work but our device shipped with mm. Odin will work but it the fw has to match the device. Then once it boots your gmail info is needed.
Click to expand...
Click to collapse
Okay I think I understand, so i need the exact firmware it was on before it crapped out, otherwise it will think i'm trying to flash new firmware an frp lock stops it right? My phone came unlocked in the UK., will i just have to try many different versions in hope one works?
Noob question, what does fw flash stand for?
Thanks so much for answering my questions : )
Hello Everyone,
First of all I am a newbie when it comes to Android, so forgive me for asking such a noob question.
So here is the story, my girlfriend's dad passed away few months ago. He used an old Samsung S8, sadly we do not know what the login pattern is or his Google account password (We did try recovery options but to no avail)
As there was no other option, I went ahead and had the phone factory reset, and from what I learned the phone is now FRP locked.
After a reading a few more guides I downloaded a tool called Odin and some 'Stock ROM' and flashed it hoping that would resolve the issue (Oh boy, how wrong I was) and the phone is now stuck on a screen saying "Error occurred while updating the device software, use the emergency recovery function"
My girlfriend just wanted to be able to use it for some time, and now I feel really bad for screwing it up.
Just wondering what my options are and if the phone is salvageable at all?
Hey, are you sure you downloaded the right ROM for this S8? Since there are two models of this phone, each with a different chipset (Exynos / Qualcomm Snapdragon). I feel like this error could come from a bad firmware? Does Odin still see the phone when you connect it to the PC?
Edit: Apparently people solved this problem using Samsung's Smart Switch on PC.
Yes, I think I downloaded the correct one. The phone is from Telstra Australia and so downloaded the ROM from Samfrew that was listed as Telstra, I typed in the model number which is SM-G950F it is this firmware that came up.
Yes when I put the phone into Recovery mode and connect to PC, Odin detects it, but the flash gets stuck halfway. I've loaded the BL, AP, CP and CSC that came within the ZIP file from Samfrew and under options only ticked 'Auto Reboot' and 'F.Reset Time'
Also tried just with the BL and AP but same deal.
blackslash said:
Also tried just with the BL and AP but same deal.
Click to expand...
Click to collapse
Have you tried Samsung's Smart Switch app on PC? Apparently people successfuly fixed this error with it.
blackslash said:
Also tried just with the BL and AP but same deal.
Click to expand...
Click to collapse
I've never had to deal with a Samsung that has a FRP lock, that could just be the reason why the flashing fails, i wouldn't know. I hope you can get the Factory Reset to work :/
Also tried the Smart Switch app but it would recognize the phone. Thank you for looking into this.
You could send a message to this user "makeyourself" : https://forum.xda-developers.com/t/i-think-i-screwed-the-pooch-on-this-one.3939572/post-79729654 , he seems aware about the FRP locks / flashing issues.
Good luck with your S8.
@Derbi75 thanks heaps, will message makeyourself now.
Ideas? Anyone?
blackslash said:
Ideas? Anyone?
Click to expand...
Click to collapse
From what I know, the error only appears if the phone was interrupted during flashing. Such as, Odin was writing into phone but you probably removed the USB or stuff. The screen you see is actually download mode. It is just renamed. Try plugging in your device when it's on the error screen then re-flash it.