Related
Hi All,
Can we retrieve the call history from a Samsung galaxy S5 (SM-I900H).
The phone actually belongs to a deceased person(a blood relative) and we want to see whats in the phone.
I have tried a few methods such as
invoking MyPhoneExplorer application from adb. (unable to share the exact link due to xda restriction.)
USB debugging is OFF so I could not proceed further.
The phone was booting and waiting for correct password on the login screen at that point of time.
Recently I tried another windows application called
"Wondershare Dr.Fone for Android".
It has a feature called Android Data Extraction, it tried to download some image to the phone. My bad that there was mis-match between the actualy device model(SM-900H) and the model selected in the Dr.Fone application(SM-900I).
The download was terminated in the middle and now the phone doesnt boot up. I am getting the below message when the device is switched on
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
Can somebody please help in data extraction from the device.
Bumping the thread to get some response
seenudn said:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
Click to expand...
Click to collapse
That part is easy (ish)
Youll need to download firmware for the device (I use fw.updato.com) and flash with Odin. (google/xda search)
Usually there's a 99.9% chance this will go fine without loosing the data on the phone, essentailly at this point, you kinda have to take the 0.01% chance of data loss, you wont get it any other way...
Wondershare's website list compatibility up to 5.0 for that device, id strongly recommend flashing the 5.0 OS, and not upgrading to 6.0.1 until after you are sorted.
As far as the data recovery, from there you are on your own, never used that soft ware, but the above will get you a booting device
Thank you so much Sam for replying.
Wish you a very happy new year !!
The current Android version on the device is Marshmallow (6.0.1).
I found a 5.0 firmware version for India region from fw updato website, but can you please suggest for the below queries.
Should I download all the 3 binaries (PDA, CSC, Phone) to the device?
If I download all the 3 binaries using odin, is there a good chance that the data will still be available?
Thank you in advance.
(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
Hi All.
Thank you for any help you might give me in advance with this issue...
Last week, I tried to root the phone with the SM-G930P CF-Autoroot heroqltespr files with Odin found in this forum. I have rooted a few other phones but am no expert. The root after a few attempts failed (verified a few ways), however, some files must have been affected because the phone "identifies" as heroqltespr. Identifies as when I could plug into my PC heroqltespr would be the name. It was not set this way in the obvious name your device areas. I ended up doing a hard reset to clear the phone and other than the ghost naming everything was working fine.
A day or 2 ago Sprint rolled out a new OTA update which the phone installed. Since then the phone was draining battery life. After uninstalling and reinstalling the SD card today, it seems to have tripped a "Security Notice: Unauthorized Actions". That is when the trouble started. The phone started running hot, basically leaking battery power, and was all lagging. I'm assuming the CPU going Ludicrous speed.
Now, I am in a Samsung Splash screen loop, or or a recovery loop. The only thing it does is go into download mode.
I have tried flashing stock firmware, it fails. I've tried flashing with and without the SD or Sim card. Not really sure what I should be doing. The "P" version of my phone seems to be the bastard child of S7s. Any help you guys cold give me would be great. THANK YOU!
The Download Screen Reads:
Odin Mode (High Speed)
Current Binary: Samsung Official
System Status: Custom
FAP Lock: Off
Warranty Void: 8x8
Qualcomm Secure Boot: Enabled
AP SWREV: 85(2,1,1,1,1) K1 S4
I get this error when I try to flash back to stock SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
Stupid question but is your phone in a case?
Sw rev check fail : [aboot]fused 5 > binary 4
freakboysays said:
Stupid question but is your phone in a case?
Click to expand...
Click to collapse
No it isn't.
I get this error message on the download screen. SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
If you dont mind me asking, did you ever find a way to root the G930P with the 5th bootloader updates? Is it even possible at this point in time? Im new when it comes to rooting but with the amount of time Ive spent browsing the web it seems as if there is nothing. Thanks.
tonysak said:
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
Click to expand...
Click to collapse
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Chanman said:
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Click to expand...
Click to collapse
EDIT: Nevermind...sounds like you aren't on sprint.
lvpre said:
EDIT: Nevermind...sounds like you aren't on sprint.
Click to expand...
Click to collapse
Actually, I am on Sprint, and your directions were awesome, thank you so much! The only thing I had to do was change the line to:
settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
I'm going to put a link to the thread so others can refer to it. https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446
Hi all,
EDIT: I posted this in another thread that was about two years old, where I followed the instructions that caused this: https://forum.xda-developers.com/sp...msung-galaxy-s7-sm-g930p-root-xposed-t3503599
That thread seems dead-ish and if you managed to fix this issue maybe you can help me also. Also what was lvpre's original post before he edited it, and would it apply here?
So the worst has happened - got a new (used) phone from Boost Mobile, tried this guide, and now I can only boot to the "An error has occured while updating the device software. Use the Emergency Recovery function in the Smart Switch PC software." screen. Sometimes it does take me to the original "Download mode" screen.
Now, I should be able to resolve this by flashing the original firmware correct? (As in, the firmware that was installed when it came)? Or does it just need to be firmware from the same date range that has the same bootloader? ODIN will still let me attempt flashing on this screen, but I still get the same error when I try again, which on the Download mode screen showed "SW REV CHECK FAIL : [system]Fused 4 > Binary 1"
Any advice here? My S6 bricked when somehow OEM unlock enabled itself and I can't get around the FRP lock, I will be VERY annoyed if the same thing happens with a NEW phone. If I can't fix this I am never buying Samsung again. Any advice on this is very welcome! I emailed Boost to ask them which firmware is installed (because I'm an idiot and didn't write it down but have never had flashing go this wrong before).
EDIT: Booting to recovery just shows a blue "RECOVERY BOOTING...." for a second in the corner and gives a recovery bootloop, just keeps flashing that.
EDIT: I apparently tried to flash an earlier bootloader/etc through ODIN according to the directions in the post I linked above, and after that I now have this problem. Nobody else in the thread seems to have had this problem, and your post is the closest to anything I can find on this issue. I would be in your eternal debt if you could help me out here.
PLEASE HELP!
EDIT: Theoretically if I can find the original firmware it was on I should be fine, right? Everywhere I read if flashing goes wrong you just flash the original stock on it. I guess worst case scenario I download gigs upon gigs of firmwares for Sprint 930P over the last year and find the one that sticks? Or is the fact my recovery is bootlooping and I can only go into download mode mean I'm bricked?
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
slvmecha said:
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
Click to expand...
Click to collapse
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Switched from Sprint to T-Mobile. Am I out of luck?
lvpre said:
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Click to expand...
Click to collapse
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
jbuck2 said:
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
Click to expand...
Click to collapse
If your phone is uicc [sim] unlocked from sprint... you can try the following.
1. Odin a dec/Jan firmware...like QJ3. But replace the cp slot with the file from the latest u firmware. This is the modem file.
2. When your phone starts, you will receive a pop up message, just hit cancel.
3. Install a package disabler like sabs, bk, adhell2. Disable securitylogagent . This should remove the annoying message. Sabs takes a little effort to setup, but you may need it for the disabler part. Restart after disabling.
4. Pop in sim. See if the additional bands are unlocked.
If you fail, you can always just odin back to a v5 sprint firmware. But don't try it unless you are stuck on the current firmware and your phone is doing nothing. It won't brick your phone.
While the firmware is not downloadable, modem files can downgrade one major update.
This worked for me, but I only have sprint and haven't tried it elsewhere.
Here is an article https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/
Is this triggers the knox counter ?
hello,
i managed to get the phone back to get in download mode. stock everything, no root whatsoever. my goal is to root my phone and i have experience doing so but i guess i was just unlucky this time.
i tried searching allover the internet for a fix, searching xda etc.
first off: my device is running oreo 8.0 and it's type is G950FX.
I want to downgrade to 7.0 because FRP lock is on, i did turn on oem lock before starting however i am unable to log in to my old google account connected to my phone.
when i try to flash any bootloader i get SW REV CHECK FAIL DEVICE 2, BINARY 1. i tried almost any trick in the book like downloading 7.0 from sammobile, flashing using odin.
the things i run into when flashing are:
1.can't flash the bootloader, probably because of frp lock.
2. when i don't flash the bootloader for 7.0 i get dm-verity error 0x2.
3. when i only flash 8.0 oreo pda & csc and then flash 7.0 pda on top i do get to boot but i get encryption interrupted error.
4. i am able to boot in 8.0 but can't get past the frp.
i'm out of answers, i really hope anyone can help me out of this situation as i want to use my phone.
Help is much appreciated!
edit: i tried flashing multiple versions of android 7.0 but i keep getting sw rev check fail bootloader device 2 binary 1
i basicly want to do this, a downgrade: https://forums.androidcentral.com/s...s8-plus/878062-how-downgrade-oreo-nougat.html
the problem is i didn't sign out of google or samsung accounts before resetting to factory
You can't. You have a new bootloader v2.
A simple search gives you this answer, if you have u2 and CRED bootloader installed you are stuck. No way to go back anymore.
i'm on u2 and CRED bootloader. i did search for this indeed but i didn't want to give up.
do you think there will be ever be a way to get back into my phone again?
If you have FRP lock good luck. I haven't seen a way yet.
I know it's been 5 months and you've probably either gotten rid of the phone or it's sitting in a dusty bin somewhere, but have you tried Galaxy Reaper? It's a pretty legit FRP bypass tool.
Edit: Scratch that. It's apparently been patched since I last knew it to work. Just wanted to double check, and sure enough..
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.