Related
Hey guys quick question before I download and attempt it, I have an Australian i9506 (Cat 4 LTE) but we don't have an official 5.0.1 firmware yet.
Can I just download the Nordic version from http://www.sammobile.com/firmwares/database/GT-I9506/ and install it, or would it brick my phone/radios not work?
Thanks
juzza87 said:
Hey guys quick question before I download and attempt it, I have an Australian i9506 (Cat 4 LTE) but we don't have an official 5.0.1 firmware yet.
Can I just download the Nordic version from http://www.sammobile.com/firmwares/database/GT-I9506/ and install it, or would it brick my phone/radios not work?
Thanks
Click to expand...
Click to collapse
Hi mate,
Yes you can !! it will not brick it , you may have (or not) problems with the modem as maybe is not the best for your region but you can always flash another...
should not be a problem
BACKUP first , nandroid and your EFS Folder, just in case there is a problem
Just to add to the previous suggestion, use Wanam's EFS Backup Tool rather than Samsung Tool, as it not only backs up the EFS partition but the hidden partitions where the IMEI and the modem are stored.
Strephon Alkhalikoi said:
Just to add to the previous suggestion, use Wanam's EFS Backup Tool rather than Samsung Tool, as it not only backs up the EFS partition but the hidden partitions where the IMEI and the modem are stored.
Click to expand...
Click to collapse
+1 mate!!
It also depends if your phone is carrier locked.
Thanks for the advice guys I'm giving it a try now, will edit as I go. My phone is not carrier locked (Voda AU don't lock them fortunately but they provide the codes on their website for free to unlock anyway).
So I downloaded Odin3 3.09 and the firmware I9506XXUDOA6_I9506NEEDOA6_NEE (this is the link from sammobile).
I'm following the instructions I found on another site but it's basically put the phone into download mode (home, power and volume down), agree to enter download mode, in Odin for AP select the .tar.md5, make sure Auto Reboot and F. Time Reset are ticked but not Re-Partition or anything else and start.
EDIT 1: The phone rebooted into recovery and updated something, now the phone is booting with a new boot animation. (for those referring to this I was on the latest AU Voda FW, then updated to CM12 5.0.2).
EDIT 2: After the usual nerve-wracking amount of time of first boot the boot logo finally went away and the usual "optimizing apps" message has come up and it's started (235 apps whoa the bloat). Waiting for that but at least it's working to a point where I can recover it. I just realised it's 6:10AM now and I FORGOT TO MAKE A BACK UP. I hope this works but worse case scenario there's a 4.4.2 Vodafone firmware I could flash and try my luck with if this doesn't work out.
EDIT 3: I'm not sure if it's part of the setup process but the word "UP" then a short progress bar appeared on the screen, now I've got only a black screen with a status bar (4G icon is there but no clock). I have rebooted from the power menu, let's see what's going on here.
EDIT 4: Cache wipe from stock recovery didn't work, trying factory reset from stock recovery. I note that the first time I set up the phone it was plugged into the computer with ODIN still running, I don't think it could have interfered but I unplugged the phone this time just in case.
EDIT 5: I'm not sure if it was ODIN or needing to do a factory reset but it's working now, I'm running through the set up. WiFi is working 100%.
Final EDIT: Everything is working 100%, tested the camera, proximity sensor, screen rotation, voice calls, mobile data, wifi and it's all 100%.
juzza87 said:
Thanks for the advice guys I'm giving it a try now, will edit as I go. My phone is not carrier locked (Voda AU don't lock them fortunately but they provide the codes on their website for free to unlock anyway).
So I downloaded Odin3 3.09 and the firmware I9506XXUDOA6_I9506NEEDOA6_NEE (this is the link from sammobile).
I'm following the instructions I found on another site but it's basically put the phone into download mode (home, power and volume down), agree to enter download mode, in Odin for AP select the .tar.md5, make sure Auto Reboot and F. Time Reset are ticked but not Re-Partition or anything else and start.
EDIT 1: The phone rebooted into recovery and updated something, now the phone is booting with a new boot animation. (for those referring to this I was on the latest AU Voda FW, then updated to CM12 5.0.2).
EDIT 2: After the usual nerve-wracking amount of time of first boot the boot logo finally went away and the usual "optimizing apps" message has come up and it's started (235 apps whoa the bloat). Waiting for that but at least it's working to a point where I can recover it. I just realised it's 6:10AM now and I FORGOT TO MAKE A BACK UP. I hope this works but worse case scenario there's a 4.4.2 Vodafone firmware I could flash and try my luck with if this doesn't work out.
EDIT 3: I'm not sure if it's part of the setup process but the word "UP" then a short progress bar appeared on the screen, now I've got only a black screen with a status bar (4G icon is there but no clock). I have rebooted from the power menu, let's see what's going on here.
EDIT 4: Cache wipe from stock recovery didn't work, trying factory reset from stock recovery. I note that the first time I set up the phone it was plugged into the computer with ODIN still running, I don't think it could have interfered but I unplugged the phone this time just in case.
Click to expand...
Click to collapse
Hi mate
How is it going?
If trouble , do a factory reset and flash it again....
Thanks mate that did the trick!
juzza87 said:
Thanks mate that did the trick!
Click to expand...
Click to collapse
glad to hear it mate, you did it!!
Thanks for let in us know.
For any other Aussies out there trying this I'm on day two and everything is working perfectly, getting root is super easy too, just use Odin to flash a custom recovery (Solk's CWM from May 2014 works great), boot into the recovery and install UPDATE-SuperSU-v2.45.zip, exit and when it asks if you want to repair root say yes. Reboot, go to the play store, update to the latest SuperSU and all is well.
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Use the original usb cable and use Smartswitch recovery, on the back is your serial number you need. And then keep on trying in Smartswitch, it took me a while but it worked and could restore my S6 to stock. And fixed Knox and the FRP lock. And I also tried everything but Smartswitch recovery saved my phone.
Sent from my SM-G928F using XDA-Developers mobile app
SOLVED
Hello, I after countless attempts with firmware that seemed to stock it did not work I SOLVED downloading the firmware directly from the Samsung server using "SAMFIRM" and then flash it with ODIN.
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
CrazyTechnoBoy said:
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Click to expand...
Click to collapse
HI, i just have the same issue .
Have you found the solution?
tried everything.
Hopefully you can help
Just found myself here. My perfectly working S7 Edge Nougat now has frp on and do-verity.
vooks said:
Just found myself here. My perfectly working S7 Edge Nougat now has frp on and do-verity.
Click to expand...
Click to collapse
nazreen nasaruddin said:
HI, i just have the same issue .
Have you found the solution?
tried everything.
Hopefully you can help
Click to expand...
Click to collapse
Here's the thing. I had a guy help me fix the FRP problem. And even he had some trouble doing so. And this was done last year, so I only kind of remember how he helped fixed it and I can't guarantee your guys' issue will be fixed if you follow my steps. And you guys may have to know the email and password associated with the phone. I took care of the dm-verity issue on my own afterwards.
Again, I THINK these steps may work, so please don't get mad if these steps don't work. if you guys can, try to flash TWRP or a custom kernel (via ODIN). I know you guys may be having the same problem, but try it out first. If you can't, try finding a combination file for your device (yes, combination file. On Google, search for "[model number] combination file" and download it). Afterwards, flash it to your phone via ODIN. This will allow the phone to boot up, but it's functionality will be very limited. Now, I think this is where you'll be able to login to Google in the settings and the FRP problem will be fixed, IIRC. If you can't login or don't have the details, there's not really much more I can help out with since I believe this is what fixed my problem (really fuzzy memory, sorry). Try rebooting and flashing TWRP again. The combination file itself may have fixed the issue.
If the above fixed the frp problem, GREAT! You should now be able to flash TWRP via ODIN. When you flash TWRP, the dm-verity problem should be fixed, as well. But now your phone needs a ROM and custom kernel. So now find the ones you want. Your phone should be working now!
If for whatever reason your phone still won't work, let me know. I may have another solution.
CrazyTechnoBoy said:
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Click to expand...
Click to collapse
Dont try to flash a zip you downloaded. Connect to smart switch and tell it to restore the phone. It downloads the right firmware for you.
godkingofcanada said:
Dont try to flash a zip you downloaded. Connect to smart switch and tell it to restore the phone. It downloads the right firmware for you.
Click to expand...
Click to collapse
Naa. I did that. Plenty of times. It simply didn't work. Lol. By saying I tried flashing the stock firmware via Smart Switch, I meant I let Smart Switch do its work. It might work if you only had one issue or the other, but if you have both FRP and dm-verity isses, it probably won't work.
CrazyTechnoBoy said:
Naa. I did that. Plenty of times. It simply didn't work. Lol. By saying I tried flashing the stock firmware via Smart Switch, I meant I let Smart Switch do its work. It might work if you only had one issue or the other, but if you have both FRP and dm-verity isses, it probably won't work.
Click to expand...
Click to collapse
you make me calm, cause i think combination file will save my phone which also i encountering the same like what you encountered before. and now i've read this post that you solved by flashing the combination file. i'm still waiting for my combination file cause i have binary 5 official rom while the combination files that i found is binary 4.
thanks!
Hi all,
New user here, not much experience rooting or messing with firmware for phones. I was following the guide on how to flash the SM-935U firmware to the verizon model of the Galaxy S7 Edge, and may have bricked my phone. Here's what I did.
Followed the guide to the letter.
Powered off phone, booted to Download mode
Fired up Odin, selected the SM-935U firmware files, and clicked start.
It gave me an Auth error, which research revealed means that I forgot to turn off Reactivation Lock. I figured, "Fine, I'll just disable it. However, I can't get the phone to boot again. Every time I leave download mode, it boots into Android Recovery, where, no matter what I do, it just reboots into Android Recovery. I can't Wipe anything because it can't mount /system - probably due to Reactivation Lock?
I've been research and researching ways around this, and everything I find just points back to flashing it with the stock firmware. But then I read that you can't even do that if Reactivation lock is on, because Odin will still fail with the Auth error. So, I can only get it to boot to recovery mode, and I can't flash it with anything?
I did read somewhere that if I choose to wipe the phone's EFS with Odin that it should override activation lock, but then it clears the phones IMEI, which is an even bigger mess, isn't it?
I feel like I have to be missing something... since it never did the wipe, why is it that I can't get past the recovery mode. Shouldn't I still be able to get into the system somehow?
Does Anyone have any thoughts or suggestions for me? I'd really like to not be stuck with a permanently bricked S7 edge if at all possible....
Solved
Just wanted to post this to help anyone else who might have this issue. Turns out that you can flash the stock firmware, as long as you're flashing at least the same version or newer of the stock firmware as what the phone was running prior to getting stuck in recovery mode. It shows you what version it was running in the recovery mode at the top.
So for me, I googled the exact firmware version that recovery mode said the phone was running, downloaded it, flashed it with ODIN, and it worked just fine. Had to choose to wipe with the recovery mode after I flashed it, but then it booted like normal. - Then I enabled OEM unlocking under the developer menu, and tried flashing the U firmware again with ODIN, and it still failed with the auth error. Huh.
Turns out (maybe I wasn't doing it right or something) that you can't flash older versions of the firmware to the phone. But, as long as OEM unlocking is enabled, you can flash the U (unlocked) version of the current firmware to the phone and it will take just fine. Hint: I was able to determine the "version" number by looking at the last 4-5 characters of the build number... the verizon version I was running for my SM-935V was: VZW-G935VVRU4API3 - So I googled the API3 firmware and found the U (unlocked) version for my carrier (I happen to be using T-Mobile) on this site: https://samsung-firmware.org/model/SM-G935U/ and found the zip file name which was TMB-G935UUEU4API3-20161011161050.zip, googled that, got the rapidgator link, downloaded it, and that flashed just fine to the phone, and now my T-Mobile SIM works perfectly in what was previously the SM-935V, which now identifies as an SM-935U in settings. It's beautiful.
Also, you need the PIT file, but I was able to use the PIT file for the phone model number (again, found at the top of the android recovery menu), which for my phone was: HERO2QLTE_USA_VZW.pit (googled that and got it off androidfilehost) - I was able to use that PIT file for the T-Mobile U version of the firmware and it worked just fine.
Hope this helps someone.
(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 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.