Database Info

PLEASE HELP ME with galaxy S2 SHW-M250K Boot problem

Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.

Gombyz said:
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Click to expand...
Click to collapse
As u mentioned, I think that your phone has gone to a Soft Brick. I don't know much about the Korean build, so Google it to solve the Soft Brick. Try flashing the stock rom via odin but I don't recommend it since it may cause your phone to be hard bricked if not done properly.
So go to the service centre, you'll get more help there

Sushant Rohan said:
As u mentioned, I think that your phone has gone to a Hard Brick. I don't know much about the Korean build, so Google it to solve the Hard Brick. But it is very hard to solve
Click to expand...
Click to collapse
I thank you sir for responding to this. From what you have said, I think the best decision is to take it to Samsung service center. (For I have tried to google it but I couldn't get a solution). I would also like to know if it is repairable, and about the cost, is it worth repairing or should I think of buying a new phone?
I am stranded.

Gombyz said:
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Click to expand...
Click to collapse
Download stock firmware (like xxxx.tar.md5 full Odin package) of ur device ,enter into Download mode of ur device & flash stock firmware with Odin.
Try this...

Firmware upgrade encountered an issue

First off: Ive searched the forum and there are a few similar posts to my problem but I thought I would ask my question before trying any of the things Ive found because I think its in this mess because Ive messed somehting up so dont want to make it worse.....
So I got given an AFAIK unrooted GT-P5100 (from Belgium) by my friend to try and fix as they had got the Interpol/ FBI thing on it. So i looked around the web and tried Safe Mode but couldnt get that to work at all so I thought I would just do a factory reset. So I got into the options by pressing volume up or down (whichever one it is) and selected wipe cache partition it displayed "erasing" then followed by "error" and the tablet rebooted back to the Interpol screen. Then I tried wipe data/factory reset it seemed to go through it very quickly, no errors displayed and then it either rebooted automatically or I selected reboot I cant remember, but straight back to the Interpol screen.........
Then I thought Odin, Ive used it in the past to flash custom ROMs on my rooted phones...
I downloaded the firmware from sammobiles - P5100XXDNA1_P5100PRODNA1_P5100XXDMG1_HOME.tar.md5
I followed these instructions with odin v3.10
- Run Odin3.exe
- Click on PA button and Select the firmware file.
- Connect your phone to PC via USB cable, And wait until Odin3 detects the phone.
- Click on Start button and wait until the operation done.
All seemed to be going OK, it added it on Com3 and several bits of text appeared saying success
Then Odin came up with fail when it seemed to be abou 90% of the way across, the bar stopped on the tablet and didnt move. Im guessing at this point I should have asked for help
Like a muppet I also closed Odin before I took a screenshot... doh!!!!!!
After a while I disconnected the cable and tried to put it back into download mode but all that comes up on the screen now is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
So I installed Kies and tried recovery mode but it doesnt detect the tablet at all.
Odin can still connect, this time on Com5
I've read about installing TWRP through Odin, is this something I should try or have I just trashed this tablet now?
Thanks for any advice!!

HELP! S6 gm920F stuck on samsung logo

i have sgs6 gm920F NEE, i tried to root it but ended up to brick my phone. When i power it up it just get stuck in the "samsung galaxy s6" screen with little red text in the left top corner saying "recovery is not seandroid enforcing"..
I cant get to recovery or get the device up and running, all i can do is to get in odin mode/download mode.
i have downloaded official 5.1.1 firmware, i have tried using different versions of odin but everytime its the same, after the "nand write start" it just fails, every single time. i have tried to use the hidden.img only from the firmware but it ends up just booting the samsung logo over and over again. also i have tried different usb ports..
Basically i cant install new firmware via odin, i cant install it via kies (i dont know the phones serial number, receipt or the box wont say this, or the phone either)..
Is there anything i can do to this?
thx, i dont want my expensive phone to be a brick.

Try this: http://forum.xda-developers.com/galaxy-s6/general/project-zero-pac-firmware-pit-file-t3181133

Try flashing stock firmware via Smart Switch.
1. Download Smart Switch.
2. Put your phone in download mode
3. Press "more"
4. Press "Emergency software recovery and initialization"
5. Device initialization
6. search for you device - For example SM-G920F
7. Type in S/N number that was on the back of your phone.
8. Follow the steps and it should reinstall stock android for you.
!!Beware that your files and stuff will be gone!!

It worked, Quintz! Thank you so much.
At first, I had a wrong modem and could not make phone calls.
After your method, I reinstalled it again using Kies and now I have my old working phone back.
Thank you sooo much !

SM-G920T: Custom binary blocked by FRP Lock [FIXED]

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

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 ...