Related
Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!
Flash the stock firmware with ODIN
Envoyé de mon SM-G935F en utilisant Tapatalk
Thanks for the reply,
Sorry but I'm new. How do i do that?
pr0cupid said:
Thanks for the reply,
Sorry but I'm new. How do i do that?
Click to expand...
Click to collapse
What model? Country
Sent from my Blackberry Bold
Model : SM-G935FD
Country : Singapore
frp lock s7 edge
pr0cupid said:
Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!
Click to expand...
Click to collapse
i have same issue here, did you find any solutions ?
AFAIK when you factory reset your phone etc. if rooted you must remember to go back into Developer Options and re enable OEM Unlocking. This depends on the method you used to root, if you flashed dm-verity then you "May not" have this issue but cannot say for sure.
If it is already too late for you then I think you need to flash stock via Odin, plenty of threads out there on where to find the firmware (SamMobile) and how to do it. Even a quick google of the error gave me plenty of results...
One thing I have read is that you may have to keep trying to get your phone into download mode as the timing is much stricter with this error message.
I've the same problem with my g935x blocked on FRP when ii treid to root if any one can help .plz
https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.
djluisbento said:
https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.
Click to expand...
Click to collapse
@djluisbento This method seems to be interesting. But would you please clarify more about it. How to install the apk file on official recovery? Or it's enough to have the pendrive connected? And if yes, when this step should take place, after flashing the official ROM or when?
I'm stuck in a boot loop into recovery mode with dm-verity error, and unfortunately I have the FRP locked, so I can't install TWRP to flash the no-dm-verity.zip file to skip it.
Appreciate your suggestions.
I have the same issure. stock firmware wont install either. im just stuck on the FRP screen, cant even get into recovery
Same issue here, please help
Everything was fine with rooting and installing TWRP. after that did a restart/ attempt to goto twrp recovery, from then the s7 edge is stuck at "Custom Binary Blocked By FRP" and doesnt boot. please help!!
Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Click to expand...
Click to collapse
just quoting from the original thread by jcadduono.
Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.
maxkento said:
Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
just quoting from the original thread by jcadduono.
Click to expand...
Click to collapse
taiseer999 said:
Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.
Click to expand...
Click to collapse
Yes, flashed both Zips in recovery. I used my regular google account during the initial set up. If i wait for 72 hours, will the phone just boot back online just fine? Still, how do i make sure it wont goto the FRP lock again while trying to reboot or reboot to TWRP?
Solved,
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.
anoopgopalpt said:
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.
Click to expand...
Click to collapse
Helo
But U did this after 72 hours?
There are several methods depending on firmware version installed on your phone. Basically you have to enter in your phone, launch chrome, install an app which gives you the possibility to log into your google account from chrome and not set-up program.
I used successfully the Bluetooth method. Search for with google. You need a bluetooth headset and follow the steps described on youtube.
BTW. My phone was brand new and I flashed different official samsung firmware ( csc). I had to change google password in between and that resulted in FRP lock....
The wait time is 24 hours as is stated in google docs from site
Sent from my SM-G935F using XDA-Developers mobile app
Hello I have a related problem, opened a new thread, but my thread was closed, because my problem is related to this one, but more complicated. I have the same problem with FRP lock as described here, I can turn on the download mode but it wont be recognized by my computer. I tried different usb cables, drivers, even computers, it wont help. I cant flash it with odin, smartswitch, kies, no matter what I try. If I go to recovery mode it says `dm-verity verification failed...`and if I choose `apply update from ADB or SD card` it says `update from external storage disabled`. I dont know what to do anymore Its a new phone
FRP Block - no Dev Tools enabled
Hey guys,
you're my last resort, I've tried everything I happened to come across, to no avail.
First off, I did something incredibly stupid, don't even ask me why, as I have no idea what the heck drove me to do this in the first place.
Anyways, I was using the stock ROM on my S7 Edge, not tweaked or tinkered with besides the usual CF-Auto_Root. It never caused any trouble whatsoever. But for no reason at all this morning I decided to disable USB debuggin and OEM unlock. A short while later I rebooted my phone, which ended up in "Custom binary blocked by FRP Lock".
I gave a factory reset a try, but that obviously didn't change a thing. So I went to sammobile.com and downloaded the latest official stock ROM for my device and tried flashing it with Odin. Unfortnately Odin always fails with "Complete(Write) operation failed.", which I assume is because I messed with the settings in dev mode.
Next stop: ADB. I've never used that thing before, but I thought I should possibly be able to get it done following a simple guide. Unfortunately ADB won't even list my device when typing "adb devices". It's just an empty list.
So please guys, give me some tipps on how I can bring my phone back to life.
The Story
Don't even know where to start. Okay so I have a SM-935W8 (Canadian Version) and it was working perfectly fine running Project Dream rom the S8 one. I decided to flash angelo's Pixel rom for S7 Edge and for some reason when it booted, the network had a cancel sign meaning no network. Once I finished the initial setup, calling, messaging , and data weren't working. Luckily I have a backup for EFS and RADIO in tar, img. and tar.gz formats. So I downloaded the Partitions Backup app and restored the EFS and Radio files, it said successfully restored. I rebooted my device and the issue was still there, no network. So then I installed the stock ROGERS (Provider) rom from SAM MOBILE and it came up with some DRK error and my phone would not boot. So then I quickly used ODIN to flash twrp and then flash Superman Rom (Love it) and use dm-verity bypass.zip to get past the drk error. Then I attempted many other things but to no avail such as flashing the EFS tar through ODIN which caused a "Software Error" and phone to be stuck on a light blue software error screen so I had to use smart switch to FULLY restore the phone back to booting up, then once again I flashed twrp and Superman rom with dm-verity so I atleast have root and a decent rom to work from.
The Problem and What I Have at Disposal
So essentially, I currently have a new section in settings under Connections called "SIM card manager" for managing sim cards even tho I only have 1 slot, it shows that the SIM is ROGERS and LTE/3G/2G in there, but it can't connect to a network and keeps saying Not Registered on a Network. Also, there are 2 IMEI's since my phone thinks theres 2 SIM slots but I really only have 1 slot. BUT HERE IS THE MAIN ISSUE, THE ROOT OF ALL PROBLEMS, the IMEI is reading as "000000000000000" and the IMEISV is "01". Hence im getting Not Registered on a Network. No secret codes such as *#06# are working, keeps giving the Not Registered on a Network error.
I have the EFS and RADIO backups in img, tar, and tar.gz formats as well as screenshots of all my MAC and Bluetooth addresses, IMEI and Serial #'s and all that information. So essentially I feel fully ready to solve the problem but everything I try keeps failing. My EFS restoration says successful in the APP but upon reboot, theres no change. Flashing the EFS through ODIN messes up phone harder. When I use EFS Professional Tool, where do I place the partitions so they show up in the tool?
I used this post to try to fix it: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
BUT when I'm flashing the combination through ODIN in AP, it goes to NAND write or whatever and gets stuck, sometimes it gets stuck on Analyzing files or something. I tried every single ODIN version. I really could use some expertise on this issue. A step by step written tutorial, some method anything!!!! Help on this post or even teamviewer or skype for live help would be appreciated. Please help and I'm willing to compensate for successfully helping me fix my issue..
Did you ever sort this out? I'm in a similar situation, except that it does occasionally show my IMEI but also 'baseband unknown'. But still no network access.
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
012345678 said:
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
Click to expand...
Click to collapse
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
jamesroodney said:
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
Click to expand...
Click to collapse
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
012345678 said:
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
Click to expand...
Click to collapse
Sorry, I should have clarified. I have an S7 (SM-G930W8). I only tried this thread because the issue was identical to mine and I couldn't find anything similar referencing the S7 specifically.
For anyone coming across this thread in the future, although mine was an S7 I think the issue would apply to both. I ended up ordering a z3x in order to use the patch certificate. But it wasn't that easy; the firmware had to be downgraded to marshmallow first which wouldn't work in Odin until I tried just flashing the BL and CP files first, then rebooting and flashing the AP and CSC files separately. In fact, the AP file froze the first time but passed on the second attempt. After that, everything was downgraded to android 6 and then the patch certificate option worked and my s7 connects to the network again.
I'm having a similar problem with my sm-g935w8 Rodgers but has been unlocked. A couple days ago i looked at my phone and it was showing a no signal symbol and I look for my phones information and it showed unknown in all categories, the imei say unknown, and it's not reading the sim. Help me
I am having the same problem after installing TGP ROM.
Graschuk said:
I am having the same problem after installing TGP ROM.
Click to expand...
Click to collapse
Did u Found any solution? am still in the same position as u r in.. i have also installed TGP ROM ... I Have Also Posted there my issue that i selected the latest bootloader nd modem blah blah
Wipe everything in twrp advanced and..
Flash latest stock rom for your model and it'll fix the issue
I think u need to see this
https://forum.xda-developers.com/showthread.php?p=78868375#post78868375
These two threads are the fountains of info :
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
This one specifically for S7 edge, whole lots of info.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
This one for advanced users who know what they are doing.. it isn't specifically for s7 series but has a universal approach to understand concepts.. don't use the provided drk (prov data) and csc restoring files, they aren't for s7 edge.
Always backup efs and all radio/serial related info firstly after rooting. Good luck
Sent from my S7 Edge using XDA Labs
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
jaszfalvi.tamas said:
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
Click to expand...
Click to collapse
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
shah22 said:
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I set a password when I enabled Secure Startup.
jaszfalvi.tamas said:
I set a password when I enabled Secure Startup.
Click to expand...
Click to collapse
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to confuse them. If it still happens, then I guess there's got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
shah22 said:
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to remember them. If it still happens, then I guess there got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I entered the password correctly, as it stated "Starting Android..." then the rotating padlock took forever. More than 10 hours even. But in the end, a factory reset helped me. But rip my photos and memories...
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Right, but i use encryption and i could update without any problem, don't know what caused this issue with him. But one should backup all data BEFORE updating, as i did to save yourself from such hassle.
Sent from my S7 Edge using XDA Labs
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Yeah, it's a sure thing I won't turn on Secure Stratup anymore. I don't know what OEM unlock does or does not, but right now, I don't have dev options enabled. If I had a microSD then I couldn't care less about resetting my phone, but since I don't have, because I have two SIM cards and a memory card has no place left, I feel bad.
Still, I don't know caused this issue. I had OTA updates before with full device encryption enabled and I had no issues before. I kinda used the same disk space at every OTA, so it should have took the same time... And I have to mention, that I did not tamper with the software. No root, no custom rom, and software only from the play store.
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
benjamen50 said:
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
Click to expand...
Click to collapse
Never had OEM unlock enabled, because I didn't know what is does, so thanks for the info. I reflashed the correct stock firmware, but that didn't help either, so I had to resort to wiping the data... Regarding this, do you know by any chance a good software for recovering data without root?
I don't know of any unfortunately, if anyone has any good paid ones that actually work please post here.
Morning Guys,
Ive had all sorts of fun and games with this damn G950F every time i root it it throws up a problem.
It had just gotten to unlock time for the third time, but started throwing up 'SystemUI has stopped working' errors when i hit the 'app list' button. Didnt think much of it, and went to root. SuperSU took and was granting root permissions but would not update the binary. I fell asleep at some stage and didnt go back to it until this morning.
Went to use the phone this morning and its reset itself and thrown up a big red message about only having stock binaries installed. Queue about 7 hours of not being able to resurrect a phone that had spat out TWRP and now appeared to have a locked down bootloader again. Finally realised i could flash the stock XSA rom without the bootloader and resurrected the phone.
Fired it up, and its no longer detecting the SIM card, and *all* of the Mobile Network settings are missing. Cant find an answer to this anywhere. Im hoping like hell its a software issue (another non answered question i have is that i get weird ass settings options with strange labels and duplicate entries and options that crash the settings app after some re-flashes.
Anyway.. wat do plez?
Have tried - Factory resets and cache wipes both in UI and recovery. Reflashing AP, CP, CSC and/or CSC_HOME. Cant flash BL as its currently 'prenormal'. Keep reading the 'download mode, start odin, quickly hit buttons' trick but have never gotten it to work, and ill try it again right now to triple check but im 99.9999% sure it wont let me re-flash Nougat on it for the same reason.
Cheers in advance.
UPDATE - So it looks like something has accidentally'd the IMEI. Now looking for non root non bootloader methods to bring it back. Looks like thats my problem.
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.