Database Info

Need help with potential softbrick with G955F

Hi guys,
I need help with my G955F. I was on Carotid's ROM and attempted to flash the AQL5 (BTU) firmware downloaded from Samfirm to go back to stock. The flash failed during writing the system.img and now it is stuck on the "Error has occurred while updating the device software" screen.
I can get into Download mode and I can boot into TWRP using ODIN.
Each attempt to flash a firmware in ODIN throws up a "FAIL" during the system.img write portion.
Each attempt to reflash a ROM from my external SD card in TWRP throws up an error while writing to system. /System is unmounted when I start up TWRP and I have to manually mount it each time.
The phone is "not supported" in Samsung Smart Switch.
Anyone have any ideas?

Never mind!
I noticed that whenever I plugged the phone into the PC when the "Error has occurred while updating the device software" screen was on it flashed up as "added" in Odin.
So I tried flashing the stock AQL5 firmware while on this screen and it worked!
I'm just going to leave this here because it's an avenue I never considered and haven't seen online.

ianrobbie said:
Never mind!
I noticed that whenever I plugged the phone into the PC when the "Error has occurred while updating the device software" screen was on it flashed up as "added" in Odin.
So I tried flashing the stock AQL5 firmware while on this screen and it worked!
I'm just going to leave this here because it's an avenue I never considered and haven't seen online.
Click to expand...
Click to collapse
Good observations.
You are correct, if the first flash fails, immediately re-enter download mode and flash again.

JeffDC said:
Yes, if the first flash fails, immediately re-enter download mode and flash again.
Click to expand...
Click to collapse
Yeah, but that's the thing. I wasn't even in Download mode for the successful flash. I was just on the Emergency Recovery screen and when I started the firmware flash, a small progress bar appeared on the screen below the text.

ianrobbie said:
Yeah, but that's the thing. I wasn't even in Download mode for the successful flash. I was just on the Emergency Recovery screen and when I started the firmware flash, a small progress bar appeared on the screen below the text.
Click to expand...
Click to collapse
Have not heard of that before - new to me, interesting find.
So the way to replicate is . . .

The way I got there was to have a screwed up install. I tried to flash a stock firmware and it generated a FAIL in Odin during the /system.img write.
The phone then rebooted to a pale green screen with a large triangle and exclamation mark advising me that the phone was in Emergency Recovery Mode and I should restore it by plugging it into a PC with Smart Switch installed.
Interestingly, Smart Switch refused to recognise my phone, saying it was an "unsupported device".
After numerous attempts to flash new firmware through Odin and TWRP (even using the two-step method of getting into Download mode) and using different cables/ports I was planning on getting it professionally repaired until I noticed that when Odin was running and I plugged the phone in, with the emergency screen on, it was "added" as it would be during Download Mode.
I loaded up the AQL5 firmware, and tried to flash. A progress bar appeared under the text on screen and it got about halfway through flashing /system when it failed again, but this time it has progressed much further than any other attempt.
I then reset everything, used an official Samsung cable and a port directly connected to the motherboard on my PC (I had been using a USB extension cable before) and attempted another flash and it worked!
I don't know how you would go about replicating those circumstances without risking your phone but if you find yourself stuck in the same situation, give it a try.
It worked for me.

Thanks, ianrobbie.

Bricked when returning to stock (No command)

Hey guys,
decided to flash the latest DBT Firmware via Odin to get back to stock completely. (G930FXXU3ESA3)
After flashing the firmware through Odin the phone reboots and then installs an update and erases data (blue background).
After a second reboot I end up with a blue screen and the simple error: "No command".
I can not get into recovery, as I end up with the same error message wether booting into recovery or the system.
I CAN however get into downloadmode and flash twrp, after that I can boot into system but I want to keep the whole system vanilla, without TWRP.
Installing TWRP keeps the device encrypted, no matter what. I can wipe, then install no-verity-encrypt and as soon as I reboot the device is encrypted again.
Ive tried: Different Firmware Version (December 2018), 3 different cables, different odin versions.
Edit: attached an Image of the message that Pops up after about 30sec on the no command screen.

Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.

FLASH No verity.zip
VIA TWRP
https://forum.xda-developers.com/attachment.php?attachmentid=4490455&d=1525176288

cooltt said:
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
Click to expand...
Click to collapse
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP

Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)

Scorpionea said:
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Click to expand...
Click to collapse
Did a efs backup through TWRP just in case, then flashed the latest DBT firmware with nand erase -> still the same problem.
I can only guess that this was caused by using a backup from another phone back when Oreo came out, this probably messed something up really badly. Very weird, im kinda lost.

Killuminati91 said:
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Click to expand...
Click to collapse
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.

cooltt said:
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
Click to expand...
Click to collapse
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.

Killuminati91 said:
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Click to expand...
Click to collapse
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.

cooltt said:
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
Click to expand...
Click to collapse
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.

Killuminati91 said:
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Click to expand...
Click to collapse
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.

cooltt said:
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
Click to expand...
Click to collapse
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.

Killuminati91 said:
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Click to expand...
Click to collapse
Thats because he's a scammer. Never donate to get your phone fixed! Donate to Rom developers and things you like but never to get the phone fixed, they're usually lying.
The serial number should be the same ON the phone as displayed IN phone. Tell me the story about the phone, how did you get it? what region? where are you? what firmware was installed? Can you still flash a ROM with TWRP? Can you check OEM unlock?
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
nmnmnmnmnmnmnmnmnm

Pretty sure he was just trying to remote repair for a price, which is not allowed on XDA. Would obviously donated on my own if he actually fixed it.
Bought the phone unlocked directly from a provider (simply - germany - dbt - g930f) back in 2016. Tripped kn0x after a few months, installed a few custom roms until Oreo came out.
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Since then I had constant connection problems, weak internet connection, dropped calls and so on.
Broke my screen and then decided to repair it myself. Bought a new frame, screen, battery, usb-port, earpiece and vibrator - managed to assemble all of that.
I can install all latest official firmwares (bootloader 3) through Odin. If I leave it at that I have no recovery and end up with the initially shown screen and "No command".
If i install TWRP from there and simply root with magisk or apply dm-verity-fix I can boot into the stock firmware with everything working.
I can also install ROMs. Just going completely vanilla is not possible anymore. OEM Unlock is checked, USB debugging works.
Edit: What is also astounding: If I flash version DBT-G930FXXS3ERHD-20180918145033 (oldest possible Oreo Version) I can enter recovery and do a factory reset and wipe cache.
If I do that however I am stuck at the Galaxy S7 Logo, not even bootlooping.

Killuminati91 said:
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Click to expand...
Click to collapse
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.

cooltt said:
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
Click to expand...
Click to collapse
Dang it. Thank you! Off to find someone who can do this via remote access or in Berlin.

Same situation right now with my S7. Damn.

Hi everyone. Did you guys find any way to resolve this issue? i have exactly the same issue here.. but in my case i cannot use twrp cuz i never installed it before... the issue happened right after i tried to enter the recovery mode by pressing the buttons...
my wife's galaxy s7 touch screen was acting weird and i tried to get into the recovey mode..which is pretty muh easy to do... but once i tried the no command msg came up and now i have exatly the same case as the guy that opened this thread....also done everything hes done....any clue about this anyone?
id appreciate some help..
thanks in advance
Diego Boffa

Anyone?

I have exactly the same error with "fail to open recovery_cause(No such file or directory)#
My Tablet is now stuck with a blue "android dead" screen saying "No command".
My history to disaster:
- i've recovered a "broken" Samsung Tablet (sm-T585) with corrupted file system via
* Download Mode works -> TWRP install -> Mount option -> use ADB to recreate EFS partition -> re-flash stock image (android 8) with odin
- device works fine
- then i've noticed it can only be used with a certain cell provider (o2)
- then i've tried to flash an older version of the stock rom (android 7) due some problems in Android 8 (often some slow downs while operating)
- this doesn't work, the flash don't start
- therefore nothing should be happend, or?
- then i've can't get anymore in the stock recovery to wipe all data
...therefore the mess began:
* i can't flash TWRP anymore
* i can't flash stock recovery anymore
* i only can get into download mode
* i can only flash a certain rom type successfully (green PASS within odin), but with the final stuck with boot loop, with the mentioned blue screen
* other rom version can't flashed
I hopefully ask you guys here, if anyone can help me?
Any help would be very appreciated ...

How to fix bootloop (can't boot into recovery or system)?

My Galaxy S7 (SM-G930R4) has decided to not want to boot. I can't boot normally or into recovery. I can only boot into Odin mode.
I've tried to flash stock rom, but it doesn't seem to work. I've heard that I should use the ROM from samsmobile, so I'll try that next.
This all started to happen after I accidentally turned on the phone right before I took the battery out. I put that battery back in and it booted fine, but after a few minutes it rebooted and started to reboot over and over again. It won't even show the charging screen when it is turned off and plugged in.

OK, I tried to flash the stock rom with Odin, but it still is in a boot loop. I've flashed it 3 times. I've firmware files from different sites. It seems that this S7 is dead. Please help!

Try to flash another rom and keep in mind that it sometimes takes up to 10-15 minutes at the first boot.
You could also just flash TWRP...

ATP-Flo said:
Try to flash another rom and keep in mind that it sometimes takes up to 10-15 minutes at the first boot.
You could also just flash TWRP...
Click to expand...
Click to collapse
TWRP for the Samsung Galaxy S7 (SM-G930R4)???
Also, now I've been greeted with the screen that says "An error has occurred while updating the device software." It says to use the Samsung Smart Switch PC software to fix it. Hopefully that works.

Where are you?
What firmware are you using? Branded or unbranded?
Have you looked on Sammobile for the correct firmware?
Are you able to boot into system recovery? Home+VOLUME UP+Power (Not Download)?

Oh you have got the G930R4. I thought G930F.
Then I don't know if there is a TWRP you could flash.
But if there is one you could just flash it and enter recovery mode and install a new ROM from within the TWRP environment.
Check this out.
https://dl.twrp.me/herolte/
Sounds like your device is currently bricked anyways, so just give it a try.
Maybe you can get a working TWRP recovery mode again.
Also check these links:
http://www.techzai.com/root-galaxy-s7-s7-edge-android-8-0/
and
https://twrp.me/samsung/samsunggalaxys7.html

cooltt said:
Where are you?
What firmware are you using? Branded or unbranded?
Have you looked on Sammobile for the correct firmware?
Are you able to boot into system recovery? Home+VOLUME UP+Power (Not Download)?
Click to expand...
Click to collapse
I am in the US.
I'm on Android 8.0 (Oreo)
I have a US Cellular Branded phone.
As soon as the phone is turned on, it tries to boot into recovery, but it can't so it keeps on trying over and over again. I've tried the firmware from SamMobile, but nothing seems to work.
When I flash to Stock ROM, and I turn the phone on, it stays in a bootloop of the "Recovery Booting..." screen.
When I flash the rooted Engineering rom, and I turn the phone on, it stays in a bootloop of the Samsung S7 logo. I can't boot into safe mode.
I tried to use Samsung Kies... didn't work... I tried to use Samsung Smart Switch... didn't work... I've tried 3 or 4 different ROMs from different websites.... didn't work.

i have the same problem. was able to enter download mode several times, but at some point it died completely (not charging anymore). how do you manage to take the battery out? does the SM-G930R4 the possibility to easily remove it?

Cloud2F said:
i have the same problem. was able to enter download mode several times, but at some point it died completely (not charging anymore). how do you manage to take the battery out? does the SM-G930R4 the possibility to easily remove it?
Click to expand...
Click to collapse
The glass panel on the back is glued onto the phone. If you remove the glass, there are screws and from there, it's easy. I broke the glass in the process... so yay me.
Mine won't charge either. It is completely dead, but it will still turn on when I plug it into my computer.

Really strange. Mine is not turning on, even tried several locations, charger, etc. Once I had download mode while having a black screen. Keep an eye on odin and instantly flash firmware if it got recognized. I press all three buttons while plugging in; that's how it worked the first time for me....

Stock-S7 freezes on startup after Oreo-update (full wipe, different stock ROMs)

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!

Issue with Samsung Note 8 SM-950F

Hi all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.

lexlex121 said:
Hi all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.
Click to expand...
Click to collapse
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I don't understand how to get into recovery mode. The phone, when the charger plugs in, attempts to boot all the time.
I know the Recovery mode key combo but I have no idea to power off this phone. I've let the battery run.