Related
This is my first experience with rooting a phone and I think I messed up...big time! All I wanted to do was get rid of preloaded garbage on the phone to save battery life. Now I have a red message, "Custom Binary blocked by FRP lock".
My G920T was completely stock until today when I loaded CF_Auto_Root into it with Odin.
The phone immediately went into a boot loop after the install. I was able to boot into device recovery and did a factory reset at that point. I didn't know until after I reset to factory that I had accidentally installed Auto_Root for the G920F.
No problems here, booted back into initial setup, and I completed all of the setup items. Logged into Google, Samsung, etc. Because this was my first time and ended with a boot loop, I decided I'd just deal with the battery life problems. I turned off USB Debugging and the Bootloader modify option. The phone seemed to be working normally until I unplugged the phone from my computer, plugged it into wall fast charger, the rebooted the phone.
Now all I get is the Samsung home screen with the red message in the upper left corner. It will continually loop between the home screen and a black screen if the phone is plugged in. I cannot get back into the recovery menu as the phone is unresponsive to home + power + vol. up. I can however boot into the download menu.
I have tried reflashing the stock tar file, a stock bootloader, and stock modem with Odin 3.10.6 and 3.10.7. When I attempt the reflash I get the failed message in Odin, and "SW Rev. Check Fail. Device: 3. Binary: 2.
Are there any other options I have at this point, or something I'm doing wrong or incompletely?
Thanks
Edit:
I have fixed the phone after about 10 hours of messing around with stock firmwares, Odin, Smart Switch, Kies, etc. If the option was there, I tried it.
The FRP Lock is easily fixed by flashing in the stock firmware, but it must be the version the phone was at before rooting. This seems to be pretty common knowledge but my problem was I didn't know which version I had. I started with 0F6, that didn't work because I would then get "sw rev check fail device 3 binary 2" in the download screen and Odin would show a red fail almost immediately.
At this point I was getting pretty beat up by the phone and was trying anything I could find. I noticed, when entering the download menu before you press the vol. up button, that you can press the home key and the phone will show the barcode. This was the turning point for fixing my phone. It was in the barcode screen that I found my phone's S/N. Perhaps it is located other places, like behind the battery I can't remove, or on a carriers website (checked T-Mobile and didn't see it), but this is where I found it. I then remembered that Smart Switch had an option for 'Emergency software recovery and installation'. When you enter that menu the program asks you for your phone's model number, then the phones S/N. I could now use this option because I had the required info. I thought I was making progress but this method failed at 60% of downloading the software and drivers and an error in the download screen of "sw rev check fail device 3 binary 2".
The key for Smart Switch is, after you enter your model number and serial number, the program tells you what firmware version the phone was at. The 3 fields that pop up all read "OJC". More progress! The firmware version I was trying to install, which was the newest one I could find without knowing what to look for, was 0F6. I found the OJC .zip file at sammobile.com. It took 2 hours to download to 95% and the download failed. Restarted the download and waited 2 more hours.
While the OJC was downloading I was still messing with options I was reading about from google searches. I read multiple times to try different versions of Odin, try different USB ports, try different sequences of loading/connecting device to pc. I changed USB ports on the PC and the samsung drivers started installing for the device. A second driver installed this time for Samsung Modem 2 (I only particularly remember the Modem 2 part) that I didn't see install on the other USB port. At this point I decided to try Smart Switch again. This time, with the extra driver, the download completed to 100% and started to install some files onto the phone. But, it only got to 20% installed and erred again. This time the error was "sw rev check fail device 3 binary 1". I also noticed that the Current Binary field on the download screen changed from "custom" to "Samsung Official". More Progress. At this point there was nothing more I could do until the OJC was finished downloading.
As soon as I unzipped the OJC I opened Odin v3.10.7 and loaded the firmware into the AP, plugged in the phone, hit start. Red Fail. Then tried loading the firmware with Odin v3.10.6. Loaded OJC into the AP, connect device, hit start. Red Fail, but, I made it past the Nand Write Start and got all the way down to the system installation part before it failed. More Progress! Tried v3.10.7 again and didn't make it past Nand Write before it failed again. Then I started changing the order of when I opened Odin, loaded the firmware, and connected the device. There are tutorials everywhere that specifically say, "CONNECT IN THIS ORDER OR THE FLASH WONT WORK", I found this to not be entirely true.
How I eventually got the OJC firmware loaded back onto the phone was to Restart the phone into the Download screen, connect phone to pc and wait for Odin to recognize the device, then load OJC into the AP, hit start. In v3.10.7 the install failed every way I tried at different points in the install. v3.10.6 is the one that ended completely re-flashing the phone to stock OJC firmware.
If you're new, or stuck, make sure you do the following:
- Verify you are trying to load the correct firmware with smart switch. (OJC is the last 3 characters of the file names)
- Try different versions of Odin
- Try different orders of setup processes
- Try different USB ports and MAKE SURE you have all Samsung device drivers installed
I might add .. don't forget to run ODIN as administrator.
Also, to avoid this in the future, disable the OEM Lock in Developer Options.
YOUR AN ANGEL :d
Hello there. I got "Custom Binary(RECOVERY) Blocked By R/L, I have odin and firmware but odin can`t see my phone. What i have to do?
1sicgsr said:
This is my first experience with rooting a phone and I think I messed up...big time! All I wanted to do was get rid of preloaded garbage on the phone to save battery life. Now I have a red message, "Custom Binary blocked by FRP lock".
My G920T was completely stock until today when I loaded CF_Auto_Root into it with Odin.
The phone immediately went into a boot loop after the install. I was able to boot into device recovery and did a factory reset at that point. I didn't know until after I reset to factory that I had accidentally installed Auto_Root for the G920F.
No problems here, booted back into initial setup, and I completed all of the setup items. Logged into Google, Samsung, etc. Because this was my first time and ended with a boot loop, I decided I'd just deal with the battery life problems. I turned off USB Debugging and the Bootloader modify option. The phone seemed to be working normally until I unplugged the phone from my computer, plugged it into wall fast charger, the rebooted the phone.
Now all I get is the Samsung home screen with the red message in the upper left corner. It will continually loop between the home screen and a black screen if the phone is plugged in. I cannot get back into the recovery menu as the phone is unresponsive to home + power + vol. up. I can however boot into the download menu.
I have tried reflashing the stock tar file, a stock bootloader, and stock modem with Odin 3.10.6 and 3.10.7. When I attempt the reflash I get the failed message in Odin, and "SW Rev. Check Fail. Device: 3. Binary: 2.
Are there any other options I have at this point, or something I'm doing wrong or incompletely?
Thanks
Edit:
I have fixed the phone after about 10 hours of messing around with stock firmwares, Odin, Smart Switch, Kies, etc. If the option was there, I tried it.
The FRP Lock is easily fixed by flashing in the stock firmware, but it must be the version the phone was at before rooting. This seems to be pretty common knowledge but my problem was I didn't know which version I had. I started with 0F6, that didn't work because I would then get "sw rev check fail device 3 binary 2" in the download screen and Odin would show a red fail almost immediately.
At this point I was getting pretty beat up by the phone and was trying anything I could find. I noticed, when entering the download menu before you press the vol. up button, that you can press the home key and the phone will show the barcode. This was the turning point for fixing my phone. It was in the barcode screen that I found my phone's S/N. Perhaps it is located other places, like behind the battery I can't remove, or on a carriers website (checked T-Mobile and didn't see it), but this is where I found it. I then remembered that Smart Switch had an option for 'Emergency software recovery and installation'. When you enter that menu the program asks you for your phone's model number, then the phones S/N. I could now use this option because I had the required info. I thought I was making progress but this method failed at 60% of downloading the software and drivers and an error in the download screen of "sw rev check fail device 3 binary 2".
The key for Smart Switch is, after you enter your model number and serial number, the program tells you what firmware version the phone was at. The 3 fields that pop up all read "OJC". More progress! The firmware version I was trying to install, which was the newest one I could find without knowing what to look for, was 0F6. I found the OJC .zip file at sammobile.com. It took 2 hours to download to 95% and the download failed. Restarted the download and waited 2 more hours.
While the OJC was downloading I was still messing with options I was reading about from google searches. I read multiple times to try different versions of Odin, try different USB ports, try different sequences of loading/connecting device to pc. I changed USB ports on the PC and the samsung drivers started installing for the device. A second driver installed this time for Samsung Modem 2 (I only particularly remember the Modem 2 part) that I didn't see install on the other USB port. At this point I decided to try Smart Switch again. This time, with the extra driver, the download completed to 100% and started to install some files onto the phone. But, it only got to 20% installed and erred again. This time the error was "sw rev check fail device 3 binary 1". I also noticed that the Current Binary field on the download screen changed from "custom" to "Samsung Official". More Progress. At this point there was nothing more I could do until the OJC was finished downloading.
As soon as I unzipped the OJC I opened Odin v3.10.7 and loaded the firmware into the AP, plugged in the phone, hit start. Red Fail. Then tried loading the firmware with Odin v3.10.6. Loaded OJC into the AP, connect device, hit start. Red Fail, but, I made it past the Nand Write Start and got all the way down to the system installation part before it failed. More Progress! Tried v3.10.7 again and didn't make it past Nand Write before it failed again. Then I started changing the order of when I opened Odin, loaded the firmware, and connected the device. There are tutorials everywhere that specifically say, "CONNECT IN THIS ORDER OR THE FLASH WONT WORK", I found this to not be entirely true.
How I eventually got the OJC firmware loaded back onto the phone was to Restart the phone into the Download screen, connect phone to pc and wait for Odin to recognize the device, then load OJC into the AP, hit start. In v3.10.7 the install failed every way I tried at different points in the install. v3.10.6 is the one that ended completely re-flashing the phone to stock OJC firmware.
If you're new, or stuck, make sure you do the following:
- Verify you are trying to load the correct firmware with smart switch. (OJC is the last 3 characters of the file names)
- Try different versions of Odin
- Try different orders of setup processes
- Try different USB ports and MAKE SURE you have all Samsung device drivers installed
Click to expand...
Click to collapse
HOW can i get The Serial NUMBER AND WRITE IT DOWN ON SMART SWITCH OR KIES ?? IF IT IS A BARCODED IN THE DEVICE ?!??!
Likebeast said:
HOW can i get The Serial NUMBER AND WRITE IT DOWN ON SMART SWITCH OR KIES ?? IF IT IS A BARCODED IN THE DEVICE ?!??!
Click to expand...
Click to collapse
smh, there is number on top of barcode that saids S/N
After Reading this post i felt dumb, because I thought imei on back of my phone was S/N whole time
I used SmartSwitch Emergency software recovery and installation, went through 2 cycles of installation somehow and it finally fixed my phone.
I'm using SM-920T galaxy S6
Hey sir did u just flash the stock rom u downloaded and it fix the frp lock?? I need ur help i also accidentally activated the oem.. please helppp sir
Hello, I seek help. I'm new to phone customization subject, so forgive me if I'm unclear.
I tried to root my phone with this method - http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
The problem started after flashing AP file - the phone was showing "Recovery is not seandroid enforcing" on bootscreen, then some other info after, which I am not available to provide.
After that I've tried flashing some custom ROM, the phone just stops at bootscreen with red "Recovery is not..." message.
Then I tried this - http://www.teamandroid.com/2016/07/...-android-6-0-1-marshmallow-official-firmware/
Downloaded G930FXXS1APG3_G930FOXX1APD4_XEO firmware, started with odin, but nothing happened for at least 30 minutes. I don't have logs. The first box was showing Set Partition message, so I went researching and decided the phone should be flashed also with PIT file. I got HEROLTE_EUR_OPEN.pit form csc file.
And at this moment stopped, as I really don't want to do anything stupid that may brick my phone permanently.
Current state:
Stuck on bootscreen with "Recovery is not seandroid enforcing",
KNOX tripped,
Can enter download mode
Can't enter recovery screen (almost sure)
I thought about using kies firmware recovery, but I recklessly lost sticker with s/n and it isn't present on box.
At this moment I'm inclined to flash mentioned firmware on the phone with repartitioning, but my main issue is that I'm not 100% sure if HEROLTE_EUR_OPEN is proper pit file for this. Also, forgive my lack of knowledge, I don't know if I should choose other region, I didn't check it when the phone was working and I'm uncertain if there is no risk in installing same-model but other region soft version.
I will be grateful for help.
Download latest firmware from here
http://updato.com/firmware-archive-select-model?q=G930F
Use ODIN 3.12.3
Phone in download mode
Add all 4 parts, AP, BL, CP, CSC
Hit start, wait for phone to hopefully reboot into Android again
777aaa said:
Hello, I seek help. I'm new to phone customization subject, so forgive me if I'm unclear.
I tried to root my phone with this method - http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
The problem started after flashing AP file - the phone was showing "Recovery is not seandroid enforcing" on bootscreen, then some other info after, which I am not available to provide.
After that I've tried flashing some custom ROM, the phone just stops at bootscreen with red "Recovery is not..." message.
Then I tried this - http://www.teamandroid.com/2016/07/...-android-6-0-1-marshmallow-official-firmware/
Downloaded G930FXXS1APG3_G930FOXX1APD4_XEO firmware, started with odin, but nothing happened for at least 30 minutes. I don't have logs. The first box was showing Set Partition message, so I went researching and decided the phone should be flashed also with PIT file. I got HEROLTE_EUR_OPEN.pit form csc file.
And at this moment stopped, as I really don't want to do anything stupid that may brick my phone permanently.
Current state:
Stuck on bootscreen with "Recovery is not seandroid enforcing",
KNOX tripped,
Can enter download mode
Can't enter recovery screen (almost sure)
I thought about using kies firmware recovery, but I recklessly lost sticker with s/n and it isn't present on box.
At this moment I'm inclined to flash mentioned firmware on the phone with repartitioning, but my main issue is that I'm not 100% sure if HEROLTE_EUR_OPEN is proper pit file for this. Also, forgive my lack of knowledge, I don't know if I should choose other region, I didn't check it when the phone was working and I'm uncertain if there is no risk in installing same-model but other region soft version.
I will be grateful for help.
Click to expand...
Click to collapse
Hi
Ok let's go back to the beginning....
1 flash a stock rom, follow this guide , download the firmware from that thread or from here
2 root follow this guide or if you plan to install a custom recovery the follow this guide
3 the right pit is included with the CSC file on the firmware, do not use the other if you are not sure
+1 on the post above , is also valid
I inherited a Galaxy S7 from my brother after he recently passed away. He was with T-Mobile, so it's a G930T (I have the original box, too, which has come in handy). I brought it back home with me... to France. I figured I'd have it unlocked and replace my old smartphone with this newer one.
Since I didn't know what his pin was, I did a factory reset... and found myself stuck in FRP!
At that point I called T-Mobile and was able to have myself added as an authorized user on my brother's account. They gave me the pin (too late! gah!) and unlocked the phone on their end, as it had been fully paid for. But as far as the FRP thing they were unable to help.
After a lot of googling, I found a bunch of how-to videos explaining how to bypass FRP, I thought I was in luck... except none of them worked for me. Then I came across a comment stating that flashing the device might do the trick. So I decided to try that... but now I'm locked in a boot loop (on the Samsung Galaxy S7 screen that keeps flashing on and off).
Here's what I did, step by step:
1) I installed Odin 3.13.1 from samsungodin.com
2) I downloaded & unpacked a stock ROM from sammobile.com, more specifically this one:
G930TUVS8CRJ1 - GALAXY S7 SM-G930T TMB USA (T-MOBILE)
3) I connected the phone to the laptop
4) I ran Odin and selected (with the AP button) the AP_GS30T* file & hit "start"
Odin said PASS! and I thought all was good... except it wasn't.
So I went googling some more and found a great page... which I am not allowed to link to yet, apparently, but it's on thedroidguy's website.
Only problem is that I can NOT get into the Recovery Menu. When I try the procedure (Home+Volume Up+Power) all I get is "recovery booting" in a bright blue font and THAT starts flashing on and off instead of the Galaxy S7 screen. If I redo the same button sequence, it just switches back to the other screen.
The ONLY other screen I can get to (unless there's another trick I haven't heard of yet) is the blue 'Warning' screen from which you can install ROM's (Home+Volume Down+Power).
So I tried to reinstall that same ROM two other times. First because I wasn't sure if I'd ran Odin as an administrator the first time around, figured that might be the issue, but that didn't change anything. Then I gave it another shot, this time using the phone's original USB cable (I had initially used mine), hoping that would make a difference... but of course, it did not.
So... is there anything I can do at this stage? Did I maybe go for the wrong ROM? Is there another one I can try?
I just hope it's not permanently bricked :-o
So I managed to unbrick my device, yay me! It took me some time to figure it out, but the solution was quite simple. Up until that point I had only been flashing the AP file alone. What fixed my problem was to also flash the bootloader (BL) file. This got me out of that boot loop.
I still haven't managed to bypass that annoying FRP lock, though. Every technique I've tried has failed.
On the plus side, I'm becoming an expert at flashing :-o
I just came across a method that, I think, could work: flash the factory combination file, enable usb debugging, then flash the regular firmware (with all files except CP).
My problem is that I can only find ONE combination file for the G930T but it doesn't match ANY of the firmwares available on sammobile... is this a problem?
The filename is similar to the v6 firmwares, only the last 4 characters don't match.
The other issue is that none of the v6 firmwares will flash on my device (they all fail pretty quickly while going through the AP file)... will using the combination file fix this?
Any thoughts or suggestions would be greatly appreciated.
Hi,
A few days back I bought an S7 and put a custom rom on it (Havoc-OS) however I wanted to put the stock firmware back on the phone so that I could resell it.
And the problems begin. Odin (3.10.6, 3.10.7, 3.13.1 are the versions I've tried) will not work, the phone either does nothing, Odin stays put at certain stages like "NAND Write" or "SetupConnection", and this morning I made a bit more progress as I've managed to get the phone to TRY to flash but the AP fails, so I've tried flashing the BL and CP, CSC all individually. Right now the phone is stuck on a screen saying...
"An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
The problem in doing that is that the software won't work without a recovery code that I do not have.
The only thing I can think of is to try and put TWRP back on the phone and keep using Havoc-OS since Samsung has apparently made it infuriatingly hard (to me) to put their own software back on their phone.
I also have a Galaxy Note 3 and have had very few issues with it... Odin works fine with it, the only quirks with the phone really are with any custom roms I use on it and not the phone itself.
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
philipp-h said:
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
Click to expand...
Click to collapse
Philip, it helps if you let us know what country your in.
Anyway the solution to your problem is pretty straight forward, you just need to flash the latest firmware for your region with Odin. No need to mess about with TWRP at this point.
Official firmware will contain a copy of the stock kernal which will also be installed when you flash with Odin 99% of the time. If for some reason the kernal is not flashed (it happens) and you continue to get the reboot issue then you will need to flash the kernal seperately first with Odin then the firmware afterwards.
The issue with the FRP lock will remain after this but should allow you to unlock with google email and password.
So we're talking, downlaod mode, flash official fimrware and go from there.
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
philipp-h said:
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
Click to expand...
Click to collapse
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
cooltt said:
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
Click to expand...
Click to collapse
Hi cooltt and thanks for your help!
Unfortunately the BTU-ROM did not solve the freeze-reboot-problem but led to another: After flashing the phone gets stuck with a blue screen "Erasing". After several hours I force rebooted and now it is showing a similar screen with "Error!" and a percentage which is increasing to a random number from 0% to 12% on each boot. On first boot it shows the boot screen ("Galaxy S7"), then "Installing system update" shortly and then "Erasing". After force-reboot it shows boot screen, "Erasing" then "Installing system update", both for a very short time (sometimes misses "Installing...")
As suggested I used SamFirm to download the newest BTU-ROM (SM-G930F_1_20191218140415_dgobhw6g3v_fac; G930FXXS7ESL5/G930FOXA7ESL5/G930FXXS7ESL5/G930FXXS7ESL5). I just ticked F. Reset Time and Reboot. Re-Partitioning did not change anything. Using Odin v3.13.1 does not make a difference. The other ROMs, like SM-G930F_1_20191226131628_8ds2p6kf0v (G930FXXS7ESL9/G930FDBT7ESL9/G930FXXS7ESLA/G930FXXS7ESL9) which I downloaded with Frija (should do the same: download enc4-files from Samsung and decrypt) make the phone going to the initial setup fine, but with the reboot-problem. Tried also with Odin 3B patched.
At this point I was going to write, that I could not access the recovery mode with the BTU-ROM but just now I started it unintentionally when looking for the sequence of screens showed on boot. So I used my chance, made a full wipe and screenshot. After this the phone booted until the glowing "Samsung"-logo appeared. Then rebooted and went to initial setup (after "Androi"Installing applications") in German. The freeze-reboot-issue appears as with all the other ROMs.
The phone is certainly an original SM-930F as it was bought directly from a big, trustworthy dealer and then just used by my aunt. The only one touching it when problems appeared was me. There is SM-G930F printed on the backside and showed in download mode.
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
philipp-h said:
Hi cooltt and thanks for your help!
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
Click to expand...
Click to collapse
Hi Phill
The only options checked in Odin should be F-Reset and Auto reboot. Don't check any others.
The blue screen erasing and updating is normal after a flash with Odin, the phone will restart a couple of times, just leave it do it's thing for a bout 10 minutes or so. If it's any longer than that as you have mentioned then it's stuck as you've said.
So we're going to start from the begining again but do something slightly different.
1. Place the phone into download mode
2. Run Odin but uncheck "Auto Reboot" so the only option checked is F-Reset Time.
3. Use whatever firmware you want, BTU or DBT the latest version. Make sure files are in the correct boxes.
4. Connect phone and flash with Odin, wait until Odin says "succeed 1" and "dissconnected" . It may even say "pass" in green, not important but "succeed 1" is important.
5. Your phone will show the bar and do not disconnect. So....disconnect from laptop / PC. The screen should remain "do not disconnect".
6. Hold volume down+home+power (in that sequence).
7. As soon as the screen goes black move your finger to volume up, while still holding down home + power. You are trying to get the phone into Recovery mode as you said earlier.
8. The option to choose in the recovery menu is "wipe cache partition" NOT "wipe/factory reset". I can see from your pictures that this option has failed because the FRP lock is still on!!
9. When you've chosen "wipe cache partition" then choose "reboot system now"
The phone should go through it's normal set up routine, erasing, update, installing apps etc, just leave it do this and hopefully the phone will boot then ask for the Google email and password which was used on the phone.
There are very few reasons for the phone to get stuck on boot....
1. Incorrect firmware,
2. Water damage
3. The phone has been Rooted with FRP lock on. It is very rare to be a hardware issue.
You should always turn FRP lock off and enable OEM unlock in settings before flashing to a phone. I know it's a little late for that but something to remember.
To check for water damage.
1. Remove SIM card and holder
2. Shine a light in the hole, you will see a WHITE sticker which turns PINK if water has ever got inside the phone.
Thanks a lot again for your great efforts!
I tried as you wrote but did not manage to start recovery immediately after flashing (tried >10 times). But after some while the BTU-ROM started and now keeps doing so even after new flash without wiping cache afterwards. Wiping data worked for me in past when I sometimes had enough time to enter Wi-Fi-password. It was saved even after reboot and away when I did data wipe in recovery. With the newest ROMs I never got beyond typing Wi-Fi credentials.
I cannot see a water damage. A root was never tried before (and OEM-lock and FRP were always on because stock, which is very bad now ). Would be absolutely no problem if this !#@*#% stock ROMs would work... TWRP installation was directly blocked when I tried my luck as last resort. I did not try other images.
Thanks nevertheless for your time and patience!