Hi, I think I f***** up badly...
I wanted to root my S7 Edge SM-G935F running android 7.0 so I enabled USB debugging and OEM unlock.
I used Odin to flash a CF auto-root I found for the 935F for android 7 and the site just said I had to install SuperSU after that but it was just boot looping.
After that I installed TWRP for my phone and installed the zip with Superuser. I kept receiving the error "failed to mount /data (invalid argument)".
I googled it and found a video that said I had to change my system "file system" from EXT4 to FAT. It was stuck so I rebooted the phone...
Now I can't load TWRP (it's stuck at the loading screen) to do a factory reset and when I do a normal boot it doens't go further than the S7 Edge screen, it doesn't go to the flashing SAMSUNG screen.
Now when I choose to reboot in Odin mode it says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I tried to do that but it says "unsupported device" and it doesn't see my phone in the Emergency Software Recovery tab.
I could have done a factory reset before but it's not the first time I root a phone and I never had a problem so I didn't back anything up but I have some very important pictures on my phone for school.
I enabled adoptable storage so I couldn't just take out the 128gb Samsung Pro + micro sd and copy the pictures on my pc.
Can somebody please tell me how to factory reset my S7 Edge even if I lose all my data. Sorry for my English it's my third language.
Thanks in advance
If I can remember correctly the "An error has occurred while updating th......." screen is actually the same as download/odin mode, so you can odin flash back stock rom.
Your data has probably already been lost during file system changing which automatically format /data.
Also I have never seen any phone run on FAT file system. S7 only support EXT4 and F2FS(required custom rom and kernel). So be careful next time.
AFAIK, there's currently no root available on stock nougat touchwiz rom unless you use modified kernel&rom.
For TWRP to be able to read /data.
/Data need to be FORMAT in TWRP once to remove encryption, so that TWRP can read it.
Sent from my SM-G935F using Tapatalk
yeah iv done the same
so turns out i have done exactly the same as you did here
what did u do to fix this
MatthieuB said:
Hi, I think I f***** up badly...
I wanted to root my S7 Edge SM-G935F running android 7.0 so I enabled USB debugging and OEM unlock.
I used Odin to flash a CF auto-root I found for the 935F for android 7 and the site just said I had to install SuperSU after that but it was just boot looping.
After that I installed TWRP for my phone and installed the zip with Superuser. I kept receiving the error "failed to mount /data (invalid argument)".
I googled it and found a video that said I had to change my system "file system" from EXT4 to FAT. It was stuck so I rebooted the phone...
Now I can't load TWRP (it's stuck at the loading screen) to do a factory reset and when I do a normal boot it doens't go further than the S7 Edge screen, it doesn't go to the flashing SAMSUNG screen.
Now when I choose to reboot in Odin mode it says "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
I tried to do that but it says "unsupported device" and it doesn't see my phone in the Emergency Software Recovery tab.
I could have done a factory reset before but it's not the first time I root a phone and I never had a problem so I didn't back anything up but I have some very important pictures on my phone for school.
I enabled adoptable storage so I couldn't just take out the 128gb Samsung Pro + micro sd and copy the pictures on my pc.
Can somebody please tell me how to factory reset my S7 Edge even if I lose all my data. Sorry for my English it's my third language.
Thanks in advance
Click to expand...
Click to collapse
It's a long story but I soft bricked my G928F.
I bought it off Gumtree in the U.K and it had an frp lock on it, the seller stated that she had wiped it off so would not take it back. I had a read around and it seemed that Wondershare Dr. Fone would take off the frp lock........it didn't, rather it messed up the stock recovery. When attempting to enter recovery I get the following message and am stuck in a bootloop:
No Support SINGLE - SKU
Supported API: 3
dm-verity error
failed code: 0x02
E: failed to mount /cache (invalid argument)
While Odin will recognise the phone Smart Switch will not so I am unable to use the emergency recovery procedure.
I have read similar posts where it implies Smart Switch is the last resort but in my case that doesn't seem to be an option
Can anyone suggest a way to recover the phone or do I throw it in the bin? Any help appreciated
meohmy said:
It's a long story but I soft bricked my G928F.
I bought it off Gumtree in the U.K and it had an frp lock on it, the seller stated that she had wiped it off so would not take it back. I had a read around and it seemed that Wondershare Dr. Fone would take off the frp lock........it didn't, rather it messed up the stock recovery. When attempting to enter recovery I get the following message and am stuck in a bootloop:
No Support SINGLE - SKU
Supported API: 3
dm-verity error
failed code: 0x02
E: failed to mount /cache (invalid argument)
While Odin will recognise the phone Smart Switch will not so I am unable to use the emergency recovery procedure.
I have read similar posts where it implies Smart Switch is the last resort but in my case that doesn't seem to be an option
Can anyone suggest a way to recover the phone or do I throw it in the bin? Any help appreciated
Click to expand...
Click to collapse
Flash this using odin :
https://drive.google.com/uc?id=1tg9hJOCquyfuyROYtgpxyVKNbuidzdL8&export=download
Then, you will be able to flash latest version normaly, and also your will remove frp lock.
Thanks for that, I will flash it when I get home and report back.
Didn't work for me, the combination file gave an 'md5 error! Binary is invalid' message when loading into Odin, while renaming to .tar the flash failed.
firmware update start
Single download
sboot bin
param.bin
FAIL
Thanks for your suggestion though.
I tried installing firmware G928FXXS5CRH1 (VOD) but it failed at hidden system image, I removed that file and created a .tar which flashed successfully but the phone rebooted
to recovery initially but still showed a dm-verity error. I deleted the cache and then factory reset which appeared to also complete successfully but the phone would not boot up.
I then tried flashing the hidden sys image on its own but that failed and the phone went to the Smart Switch error recovery page, Smart Switch will not recognise the phone so will not allow access to the emergency recovery facility.
Still trying though if anyone has any idea's.
Hi there,
Im in the same boat. It had the verity error too.
BUT:
For me it worked to flash the 4-part firmware of the G928FXXS5CRH1 via Odin then.
The device boots again, without the verity error
It had Android 5.1 before, when I could flash the COMBINATION ROM and use it just fine.
(but it was a Android 7 combination ROM) :/
After flashing Android 7 debranded (G928FXXS5CRH1) in 4-parts (BL, AP, CC and CSC file) the FRP lock is still there of course,
but the phone is booting again without the verity error.
COMBINATION ROM will no longer let me flash it, though.
https://forum.xda-developers.com/s6-edge-plus/help/g-928f-verity-0x02-modem-bin-fail-t3886122
The download I did via the tool "samfirm" use chk32 and decrypt on downloading !
"SM-G928F_1_20180828170540_5avji4munw_fac"
Thanks for the reply, I fixed it myself in the end. I spent 2 days over Xmas until I eventually tried the solution that you have suggested. I eventually found a 4 part software. AS to the FRP lock, be it good luck or persistence, I managed to get rid of that as well using Samsung FRP Tool.
meohmy said:
Thanks for the reply, I fixed it myself in the end. I spent 2 days over Xmas until I eventually tried the solution that you have suggested. I eventually found a 4 part software. AS to the FRP lock, be it good luck or persistence, I managed to get rid of that as well using Samsung FRP Tool.
Click to expand...
Click to collapse
Hell Friend, Not sure If you could get this message, If yes, Kindly help me., I am facing the same issue with my Samsung Galaxy Note 5 (N920G/I) but could not find 4 parts FRP unlock firmware. Do let me know If anyone finds one.
Thanks!
Good day from UK
Having rooted several Samsung 'phones with cfautoroot I am familiar with the process, but I have just purchased a
J5 (2017) with Android 8.1.1 and gone through procedures of enabling developer, usb debugging and download.
Used the latest offering from Chainfire and latest Odin and gone through installation process.
Phone rebooted with error like "device has problem reset device" and done so as per one post and then
tried Odin to flash the AP again.
Nothing happens. Goes through the various reboot processes and returns with a standard 8.1.1 with no root
access and no Super SU installed but device says "custom" on information.
I have looked through lots of threads but not found any answer! Might haved missed something so sorry
for duplicate post if so. On this link says to reste then reflash - but this does nothing.
https://forum.xda-developers.com/ga...nt/guide-root-twrp-recovery-sm-j530f-t3685871
Any help please!
many thanks
John
UK
P S
Also tried the home/vol up/power option but reports error
then goes to menu with error:- E:Failed to find /misc partition
Cleared cache partiton then says same error of E:Failed to find /misc partition
PPS
Sorry typed too quickly
Booting into recovery says "no command" THEN goes to the recovery screen
Resetting the phone as factory reset also gives the error E:Failed to find /misc partition
well!
Finally tried manually installing Super SU Pro
and
lo and behold it worked!
Still interested to know what the problem was if anyone can help!
Hi everyone! Help! Need help! As titled, i have almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP recovery or boot into normal recovery, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary TWRP recovery/boot blocked by frp lock when the device was working fine running custom rom, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom to boot up system, but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem?
No menu in stock recovery, it's just saying:
#fait to open recovery_cause(No such file directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE=SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
I'm having the same and exact problem as in this video with same brand device S7e https://youtu.be/l8-ccufk4Q0 the man could save the device by installing TWRP because frp was off. I can't do the same because I got frp on
I used to play with a whole Frp Remover Tools but nothing helped or worked, and also tried some cracked boxes but unfortunately they seem just like interfaces and didn't work as well
If I ended with frp lock turned successfully off then everything will be easy, installing TWRP then flashing through it no_verity_encryption will solve the issue and the device will boot the system successfully, I need to turn it off, if anyone has a solution please help!
TheDevelopper said:
Hi everyone! Help! Need help! As titled, i have almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP recovery or boot into normal recovery, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary TWRP recovery/boot blocked by frp lock when the device was working fine running custom rom, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom to boot up system, but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem?
No menu in stock recovery, it's just saying:
#fait to open recovery_cause(No such file directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE=SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
Click to expand...
Click to collapse
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
What happens when you Odin your full firmware package?
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thank you man, yea, you're right cause we tried almost everything but unfortunately can't recover it too :/
klabit87 said:
[/HIDE]
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
What happens when you Odin your full firmware package?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Odin success passed the firmware's packages without problems, and it is the right one @klabit87, actually, there is a chance to recover the phone, I have found a video on YouTube having the same and exact problem as me with same brand device S7e, the man could save the device by installing TWRP because frp was off, I can't do the same because I got frp on https://youtu.be/l8-ccufk4Q0
TheDevelopper said:
Odin success passed the firmware's packages without problems, and it is the right one @klabit87, actually, there is a chance to recover the phone, I have found a video on YouTube having the same and exact problem as me with same brand device S7e, the man could save the device by installing TWRP because frp was off, I can't do the same because I got frp on https://youtu.be/l8-ccufk4Q0
Click to expand...
Click to collapse
I think there are ways around frp though... I could be wrong though.
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
I think there are ways around frp though... I could be wrong though.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
If only it can be turned off, I'll flash TWRP
TheDevelopper said:
If only it can be turned off, I'll flash TWRP
Click to expand...
Click to collapse
I wonder if you could use a custom kernel with dm-verity removed altogether. You could Odin it. No need for twrp. What firmware version is currently installed? I will compile it for you if you want to try it. Maybe try verity will get you to a point where you could remove frp while booted. Is your bootloader still unlocked? As in OEM unlock I mean.
Sent from my Pixel 2 XL using Tapatalk
q
klabit87 said:
I wonder if you could use a custom kernel with dm-verity removed altogether. You could Odin it. No need for twrp. What firmware version is currently installed? I will compile it for you if you want to try it. Maybe try verity will get you to a point where you could remove frp while booted. Is your bootloader still unlocked? As in OEM unlock I mean.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
When tried to flash TWRP, it says custom binary recovery block by frp lock
And when tried to flash a custom boot that I took from a custom ROM and I Tared it, it says custom binary boot blocked by frp lock, I don't know if frp is related to OEM unlock or not and I don't know why it failed to Odin the boot that I took, the current firmware is CSC1 ..link for appropriated boot.img https://desktop.firmware.mobi/device:454/firmware:19931 if the device will read it as a custom one I don't think it will bypass it so, I would not disturb u if actually the phone will refuse it
But if crom service still off that means the bootloader is unlocked, once running for the first time on the device no need to use it anymore and the bootloader will be unlocked, but I don't know if OEM is enabled and it says in download mode secure download enabled
TheDevelopper said:
qWhen tried to flash TWRP, it says custom binary recovery block by frp lock
And when tried to flash a custom boot that I took from a custom ROM and I Tared it, it says custom binary boot blocked by frp lock, I don't know if frp is related to OEM unlock or not and I don't know why it failed to Odin the boot that I took, the current firmware is CSC1 ..link for appropriated boot.img https://desktop.firmware.mobi/device:454/firmware:19931 if the device will read it as a custom one I don't think it will bypass it so, I would not disturb u if actually the phone will refuse it
But if crom service still off that means the bootloader is unlocked, once running for the first time on the device no need to use it anymore and the bootloader will be unlocked, but I don't know if OEM is enabled and it says in download mode secure download enabled
Click to expand...
Click to collapse
Ah ok. You're right it won't flash then. Sounding like a qcom CDMA tool might help. I've seen a couple that allow you to remove frp but I believe it requires entering qshusb mode. But it seems like options just get more and more slim now
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
Ah ok. You're right it won't flash then. Sounding like a qcom CDMA tool might help. I've seen a couple that allow you to remove frp but I believe it requires entering qshusb mode. But it seems like options just get more and more slim now
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yes, playing around a right tool can remove it, searching and testing ..
Edit: @klabit87, all the tools failed
I have same model and same problem. Did you find any solution?
hi, do you have any update? I have the same problem and the same model too
Do anyone still need help in fixing this issue?
I would like you to join me in this experiment to fix your device.
how we start it ?
bawsobb said:
how we start it ?
Click to expand...
Click to collapse
Please PM me then we will first try to fix it and then post a tutorial here on XDA.
Backstory:
Received the message "Custom binary blocked by FRP lock" when restarting my phone. I had a custom ROM installed so this was probably why, but I had flashed no-verity-opt-encrypt previously so I don't know why I randomly got this message.
Tried to flash the latest Android 8.0.0 stock firmware from sammobile, successfully flashed through Odin but when the phone boots it keeps looping into recovery, followed by "No command".
When I try to access the recovery settings by pressing power+up it comes with:
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
Along with a bunch of lines saying failed to mount /system and dm-verity failed.
I've tried flashing many different stock ROMs but only the factory binary combination ROM is able to boot up. Therefore, I cannot turn off FRP lock. I am struggling to find out why, even though Odin successfully flashed the whole stock BL, AP, CP and CSC, the recovery cannot be opened.
Any ideas would be greatly appreciated.
Edit: Managed to fix it through a YouTube video by Mr.Lee
Try downgrading to nougat or marshmallow. That should remove FRP.
Sent from my SM-G935FD using Tapatalk
I've tried but I cannot find any marshmallow/nougat version which does not result in a SW REV CHECK FAIL error, my kernel only accepts Oreo or higher it seems.