Database Info

Upload Mode: MODEM CRASHED!

I was running the NKD Odexed ROM, and out of nowhere my phone just froze up and eventually went to Upload Mode where I was able to see that my Modem Crashed. When I pulled the batter and restarted my phone, I had no mobile service, and my Baseband and Software information both say Unknown. I cannot reboot into recovery, it just keeps bootlooping . I was able to flash the NK4 full restore, but when that loads up, even though it shows the LTE icon, my mobile data network status is set to disconnected. I also cannot boot to recovery from NK4 or any 4.4 bootloader to restore a backup. Any help would be incredibly appreciated. I'll be more than happy to buy some beers for anybody who can help me with this. Sprint is unable to help me on their end.
Edit: I should also note that I've tried Odin'ing the NKD modem several times when I am on android L, and the NK4 when on 4.4, neither do a thing to help.

jsmcmahon89 said:
I was running the NKD Odexed ROM, and out of nowhere my phone just froze up and eventually went to Upload Mode where I was able to see that my Modem Crashed. When I pulled the batter and restarted my phone, I had no mobile service, and my Baseband and Software information both say Unknown. I cannot reboot into recovery, it just keeps bootlooping . I was able to flash the NK4 full restore, but when that loads up, even though it shows the LTE icon, my mobile data network status is set to disconnected. I also cannot boot to recovery from NK4 or any 4.4 bootloader to restore a backup. Any help would be incredibly appreciated. I'll be more than happy to buy some beers for anybody who can help me with this. Sprint is unable to help me on their end.
Edit: I should also note that I've tried Odin'ing the NKD modem several times when I am on android L, and the NK4 when on 4.4, neither do a thing to help.
Click to expand...
Click to collapse
I had almost the same problem yesterday and was able to restore my backup this morning.
Here's the steps I took:
1. Using Odin 3.10.0
2. Make sure your phone is completely off (battery pull if necessary).
3. Go into Download Mode (Volume Down, Home, Power), then Volume UP
4. Plug phone via USB to computer, run Odin. Make sure you have a blue ID:COM light in Odin.
5. Uncheck Auto-Reboot.
6. Odin either NE5 firmware or NK4 firmware (depending on what your nanoid was).
7. Wait till Odin gives you a PASS, unplug USB and immediately go into Recovery (Volume UP, Home, Power).
8. Restore your nanoid and reboot.
This is assuming you have an extSD card and your nanoid is on it. If you don't you'll need to get one. If you don't have a nanoid, copy the rom you want to flash onto extSD and replace step 8.
Edit: FYI, the firmware files include the modem and TWRP recovery.
Edit: My reading skills are a little slow today, if you prefer the firmware with Philz, here's NE5 and NK4 firmware with Philz.

Ramer said:
I had almost the same problem yesterday and was able to restore my backup this morning.
Here's the steps I took:
1. Using Odin 3.10.0
2. Make sure your phone is completely off (battery pull if necessary).
3. Go into Download Mode (Volume Down, Home, Power), then Volume UP
4. Plug phone via USB to computer, run Odin. Make sure you have a blue ID:COM light in Odin.
5. Uncheck Auto-Reboot.
6. Odin either NE5 firmware or NK4 firmware (depending on what your nanoid was).
7. Wait till Odin gives you a PASS, unplug USB and immediately go into Recovery (Volume UP, Home, Power).
8. Restore your nanoid and reboot.
This is assuming you have an extSD card and your nanoid is on it. If you don't you'll need to get one. If you don't have a nanoid, copy the rom you want to flash onto extSD and replace step 8.
Edit: FYI, the firmware files include the modem and TWRP recovery.
Click to expand...
Click to collapse
Unfortunately, I can't count how many times I've tried this, both the firmware with TWRP, and firmware with Philz, my recovery will not boot. I get RECOVERY BOOTING.... in blue, RECOVERY IS NOT SEANDROID ENFORCING in red and Set Warranty Bit : recovery in yellow. This lasts about 30 seconds, and then it reboots to the same thing. The only way to get out of the recovery bootloop is to flash a firmware and not try to boot into recovery after, but then stuck with my modemless problem .
I can't even just go back Stock everything because I won't have service, my phone is basically a paperweight at this time.

jsmcmahon89 said:
Unfortunately, I can't count how many times I've tried this, both the firmware with TWRP, and firmware with Philz, my recovery will not boot. I get RECOVERY BOOTING.... in blue, RECOVERY IS NOT SEANDROID ENFORCING in red and Set Warranty Bit : recovery in yellow. This lasts about 30 seconds, and then it reboots to the same thing. The only way to get out of the recovery bootloop is to flash a firmware and not try to boot into recovery after, but then stuck with my modemless problem .
I can't even just go back Stock everything because I won't have service, my phone is basically a paperweight at this time.
Click to expand...
Click to collapse
Have you tried to odin the .tar version of Philz?
---------- Post added at 04:14 PM ---------- Previous post was at 04:05 PM ----------
As a last resort type thing, this is a one-click file from @rwilco12 to bring you back to stock unrooted NE5.

Ramer said:
Have you tried to odin the .tar version of Philz?
---------- Post added at 04:14 PM ---------- Previous post was at 04:05 PM ----------
As a last resort type thing, this is a one-click file from @rwilco12 to bring you back to stock unrooted NE5.
Click to expand...
Click to collapse
Yes, a previous version of Philz I can try this newer one though. I've also tried just TWRP. It's looking more and more like the weirdest brick I've ever heard of :-\.

Ramer said:
Have you tried to odin the .tar version of Philz?
---------- Post added at 04:14 PM ---------- Previous post was at 04:05 PM ----------
As a last resort type thing, this is a one-click file from @rwilco12 to bring you back to stock unrooted NE5.
Click to expand...
Click to collapse
Thanks for your attempted help , I actually ran both a NI3 and NE5 restore today . It would be safe to say I am not a noob at this stuff, I think I just got me a lemon :-\. I've been doing this for way too long now, I just don't get it.

jsmcmahon89 said:
Thanks for your attempted help , I actually ran both a NI3 and NE5 restore today . It would be safe to say I am not a noob at this stuff, I think I just got me a lemon :-\. I've been doing this for way too long now, I just don't get it.
Click to expand...
Click to collapse
It just seems to me that if you can get into Download Mode, it should be solvable. @tdunham, do you have anything to add that I didn't cover?

Try to do a phone reset with ##786# from the dialer. It's possible the phone cant authenticate with the network and that is why you're not getting signal.
I think this wipes internal storage but its worth a try to begin.
Next...
Pull the SD and the Sprint sim card.
Odin custom recovery and wipe absolutely everything including internal storage.
Power off the phone again, either from the recovery menu or battery pull.
Reinsert the sim card only, no SDcard, and do FULL factory Odin tar install, not the mini-bootloaders.
Let the rom boot fully but skip logging into Google and anything else and go straight into settings/backup and reset/factory reset.
Reboot again and see how it goes.
As a last resort you can try to re-pit (repartition) the phone but lets see how it goes from here.

tdunham said:
Try to do a phone reset with ##786# from the dialer. It's possible the phone cant authenticate with the network and that is why you're not getting signal.
I think this wipes internal storage but its worth a try to begin.
Next...
Pull the SD and the Sprint sim card.
Odin custom recovery and wipe absolutely everything including internal storage.
Power off the phone again, either from the recovery menu or battery pull.
Reinsert the sim card only, no SDcard, and do FULL factory Odin tar install, not the mini-bootloaders.
Let the rom boot fully but skip logging into Google and anything else and go straight into settings/backup and reset/factory reset.
Reboot again and see how it goes.
As a last resort you can try to re-pit (repartition) the phone but lets see how it goes from here.
Click to expand...
Click to collapse
I pulled the SD and Sim Card, and odin'd a custom recovery, but I cannot reach a custom recovery, just goes through the RECOVERY BOOTING.... boot loop explained in the OP. From there I've already done everything else close to 50 times now it just doesn't work.
When you go into settings/backup and restore/factory reset it's supposed to do something on it's own, mine just goes to recovery (ONLY IF STOCK RECOVERY IS INSTALLED OTHERWISE IT RECOVERY BOOTLOOPS) and the android guy falls over. It does not do the reset, I have to manually do it from stock recovery, but it doesn't seem to be helping.
Also, ##786# doesn't do anything. Neither does ##72786# as the Sprint rep was suggesting. My dialer (for one is lagging to all hell along with my keyboard) does not react, it just continues to show that #. This is on 100% stock too.

jsmcmahon89 said:
I pulled the SD and Sim Card, and odin'd a custom recovery, but I cannot reach a custom recovery, just goes through the RECOVERY BOOTING.... boot loop explained in the OP. From there I've already done everything else close to 50 times now it just doesn't work.
When you go into settings/backup and restore/factory reset it's supposed to do something on it's own, mine just goes to recovery (ONLY IF STOCK RECOVERY IS INSTALLED OTHERWISE IT RECOVERY BOOTLOOPS) and the android guy falls over. It does not do the reset, I have to manually do it from stock recovery, but it doesn't seem to be helping.
Also, ##786# doesn't do anything. Neither does ##72786# as the Sprint rep was suggesting. My dialer (for one is lagging to all hell along with my keyboard) does not react, it just continues to show that #. This is on 100% stock too.
Click to expand...
Click to collapse
It sounds like you corrupted your efs but I cant say for sure because I haven't seen it happen too often. You can always try to flash pit through odin and repartition. I'll attach the pit file in a zip so you can try it.

It seems like I would be more likely to have luck on Android L because at least when I flash that I have a phone that somewhat functions, I am missing a modem, and can not get one to stick at all, but I can at least connect to wifi, log into gmail accounts and do anything else. Where as on a stock 4.4 refresh I have a sick lag, it shows I have a modem but I am not provisioned for data, and sprint support is no help. They want me to bring my phone to a tech which is not something I am looking to do knowing I tripped the KNOX flag.

tdunham said:
It sounds like you corrupted your efs but I cant say for sure because I haven't seen it happen too often. You can always try to flash pit through odin and repartition. I'll attach the pit file in a zip so you can try it.
Click to expand...
Click to collapse
I odin'd that pit and tried to start fresh, no luck. I can't thank you guys enough for your continued effort
Edit: I am reading this post http://forum.xda-developers.com/showthread.php?t=2610757
I have never used the Nand Erase All or Phone EFS Clear options in Odin, but this seems like it might help?
2nd Edit: After flashing the PIT file with NE5 stock rom I achieved data. Now I have an incredibly laggy stock rom, which might just have to do for now, because I still can't get to a custom recovery.
I did not use Nand Erase All or Phone EFS Clear, but am still very interested.

Realized a new issue today. My phone will only charge when off. Still open to suggestions.

Im haveing the exact same issue you are and no clue what to do about it.

Wow I must be lucky all I did was a battery pull and my phone worked again (back when I was on moar 5.0) (i haven't encountered it on moar 6.1)
Sent from my SM-G900P

gtuansdiamm said:
Wow I must be lucky all I did was a battery pull and my phone worked again (back when I was on moar 5.0) (i haven't encountered it on moar 6.1)
Sent from my SM-G900P
Click to expand...
Click to collapse
I don't think you are haveing the same issues we are.

I had similar happen to me and the only thing that fixed it was to go back to the first stock, ND2 I think and work my way back up. It happened to me on NKD also, not sure if it was the same exact thing but sounds close. IIRC after flashing back to the first stock ROM thing started working but prior to that I Odin flashed every package that came with a pit file.

miked63017 said:
I had similar happen to me and the only thing that fixed it was to go back to the first stock, ND2 I think and work my way back up. It happened to me on NKD also, not sure if it was the same exact thing but sounds close. IIRC after flashing back to the first stock ROM thing started working but prior to that I Odin flashed every package that came with a pit file.
Click to expand...
Click to collapse
i was on nkd last i could remember but as far as know you cant downgrade the bootloader.

jackrabbit72380 said:
I don't think you are haveing the same issues we are.
Click to expand...
Click to collapse
well back when i had the issue id randomly take out my phone from my pocket and see it stuck on a screen that said upload mode modem crashed
lets hope that there isnt a second issue out there as well
back then it was a 50/50 shot doing a battery pull and getting the phone to boot
sometimes even while i had charge i would have to plug phone into a power supply and then try turning it on
but regardless i wish you guys best of luck

jackrabbit72380 said:
i was on nkd last i could remember but as far as know you cant downgrade the bootloader.
Click to expand...
Click to collapse
Downgrade on the sprint s5 is possible with Odin, no negative side effects. FWIW theres a few threads around too that back this statement.

Bricked S7?

So I went to flash a Rom with Odin and now I can't get past the recovery screen. The phone will not show up when I plug into USB either. Is this phone officially toast?

Our crystal ball here at XDA is on the blink, unfortunately you're going to have to manually provide more information

Wlane1979 said:
So I went to flash a Rom with Odin and now I can't get past the recovery screen. The phone will not show up when I plug into USB either. Is this phone officially toast?
Click to expand...
Click to collapse
Hi mate
You said past recovery screen in recovery mode?
What firmware you flashed with odin , which files ?
If you can get into download mode there is hope still... can you? , go to recovery factory reset see if you can boot now , if not flash again firmware with odin , to avoid losing data use your home_csc file if that does not work flash again this time using CSC and checking re partition option in Odin

The phone orginally was stuck in a boot loop so I downloaded what I thought was a working Rom to fix it. Apparently something went wrong because now all I can do is get to hard reset recovery screen. I can wipe cache and format and all but it does not do anything.
I tried to plug the phone onto my computer and nothing happens now where as before it would recognize as a s7 and would recognize in Odin.

Wlane1979 said:
The phone orginally was stuck in a boot loop so I downloaded what I thought was a working Rom to fix it. Apparently something went wrong because now all I can do is get to hard reset recovery screen. I can wipe cache and format and all but it does not do anything.
I tried to plug the phone onto my computer and nothing happens now where as before it would recognize as a s7 and would recognize in Odin.
Click to expand...
Click to collapse
Model S7?
ROM you Flashed?
Download mode should still work no matter what you do with firmware tbh

It was a live demo stuck in boot loop. G930x
I'm not sure I remember the file name but it was the stock ldu rom

Wlane1979 said:
The phone orginally was stuck in a boot loop so I downloaded what I thought was a working Rom to fix it. Apparently something went wrong because now all I can do is get to hard reset recovery screen. I can wipe cache and format and all but it does not do anything.
I tried to plug the phone onto my computer and nothing happens now where as before it would recognize as a s7 and would recognize in Odin.
Click to expand...
Click to collapse
But what did you try to flash a custom rom or a stock firmware?
What did you format in recovery?
Sometimes during bootloops getting into download mode is tricky , keep trying
@*Detection* sorry mate i did not see your replies

MAX 404 said:
@*Detection* sorry mate i did not see your replies
Click to expand...
Click to collapse
Don't worry, two heads are better than one
---
Yea OP, as above, getting into DL mode sometimes takes a few attempts, keep Volume Down & Home & Power pressed until the phone reboots twice, after the second reboot keep them pressed and see if it boots into download mode
AFAIK with the demo units you need to flash the G930F firmware to them to unlock
But still no modem or fingerprint reader even after that iirc

But I can't used my pc to flash anymore. It does not show a device connected like if I plug in my s8.

The picture shows where I am stuck

Ok I got past that screen in dl Mode and found the right firmware or so I believe. Odin freezes when trying to add AP file. Without it my phone stays on the load screen. Help!

Wlane1979 said:
Ok I got past that screen in dl Mode and found the right firmware or so I believe. Odin freezes when trying to add AP file. Without it my phone stays on the load screen. Help!
Click to expand...
Click to collapse
Wait, ODIN takes a long time to load AP, and looks like it has frozen, just wait and it will add eventually

Can someone point me to the correct thing I need to download then? There are so many. What do I need since its a sm-g390x?

Wlane1979 said:
Can someone point me to the correct thing I need to download then? There are so many. What do I need since its a sm-g390x?
Click to expand...
Click to collapse
Maybe you can use the emergency recovery from samsung.. with serial number it will flash the correct firmware.

I'm not sure being a live demo unit

Wlane1979 said:
I'm not sure being a live demo unit
Click to expand...
Click to collapse
G930F firmware for demo units

*Detection* said:
G930F firmware for demo units
Click to expand...
Click to collapse
There are many of the 930f I have found but none of which for the United States.

Wlane1979 said:
There are many of the 930f I have found but none of which for the United States.
Click to expand...
Click to collapse
That's because it's an International firmware, use United Kingdom (BTU)

I did the firmware flash. Everything seemed to go smoothly but now I am stuck on a flashing Samsung screen

Wlane1979 said:
I did the firmware flash. Everything seemed to go smoothly but now I am stuck on a flashing Samsung screen
Click to expand...
Click to collapse
Did you use CSC rather than HOME_CSC?
Try booting into recovery and factory reset

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

SM-G930F reboots no Recovery possible

I got an S7 that reboots a feew seconds right after it shows the very first screen:Samsung Galaxy S7 powered by Android.
I can only acces Download modus and were able to sucessfully flash the recent firmeware via odin but it did not fix the phone.

Huzalio said:
I got an S7 that reboots a feew seconds right after it shows the very first screen:Samsung Galaxy S7 powered by Android.
I can only acces Download modus and were able to sucessfully flash the recent firmeware via odin but it did not fix the phone.
Click to expand...
Click to collapse
You MUST flash the correct firmware for device and region.
1. Uncheck "auto reboot" in Odin
2. Flash firmware again
3. Disconnect phone Do Not Power On!
4. Wait 2 minutes
5. Boot into recovery volume up+home+power
6. Wipe cache, factory reset, then reboot device.

cooltt said:
You MUST flash the correct firmware for device and region.
1. Uncheck "auto reboot" in Odin
2. Flash firmware again
3. Disconnect phone Do Not Power On!
4. Wait 2 minutes
5. Boot into recovery volume up+home+power
6. Wipe cach, factory rest, reboot device.
Click to expand...
Click to collapse
Tried that no luck. Wasnt able to boot in recocery from download modus. Tried to reset via power+vol down and immidetly switching to power+home+power up phone wasnt booting. Started booting as soon as i released the keys

Huzalio said:
Tried that no luck. Wasnt able to boot in recocery from download modus. Tried to reset via power+vol down and immidetly switching to power+home+power up phone wasnt booting. Started booting as soon as i released the keys
Click to expand...
Click to collapse
Mate keep trying you have to be really quick when it goes off to quickly press volume up

cooltt said:
Mate keep trying you have to be really quick when it goes off to quickly press volume up
Click to expand...
Click to collapse
Okay just to be shure should i force the phone to restard after the 2 minutes or should it shut off by itself?

Huzalio said:
Okay just to be shure should i force the phone to restard after the 2 minutes or should it shut off by itself?
Click to expand...
Click to collapse
If it doesn't shut off after you flash firmware do a force restart by holding volume down+home+power. As soon as the phone goes off and before the galaxy splash screen appears you press volume up+home+power. If the splash screen appears before you do this then you are too slow. Repeat the power off process and try again

cooltt said:
If it doesn't shut off after you flash firmware do a force restart by holding volume down+home+power. As soon as the phone goes off and before the galaxy splash screen appears you press volume up+home+power. If the splash screen appears before you do this then you are too slow. Repeat the power off process and try again
Click to expand...
Click to collapse
Yeah did exactly that switched to the combo before it showed anything no succes.

Huzalio said:
Yeah did exactly that switched to the combo before it showed anything no succes.
Click to expand...
Click to collapse
Not sure what's wrong with it then

Huzalio said:
Yeah did exactly that switched to the combo before it showed anything no succes.
Click to expand...
Click to collapse
you need to hold the buttons for 7 seconds .. you can also boot to recovery without flashing new firmware ... can you confirm that the volume up button still works ?

Ulf3000 said:
you need to hold the buttons for 7 seconds .. you can also boot to recovery without flashing new firmware ... can you confirm that the volume up button still works ?
Click to expand...
Click to collapse
able to confirm to enter download modus

Huzalio said:
able to confirm to enter download modus
Click to expand...
Click to collapse
Ok the only reason it will not boot after a successful firmware flash with Odin is if the EFS partition is corrupt or missing.
You need to tell us exactly what you've done with the phone before this happened.
What country are you in?
What firmware did you have on your phone originally?
Where have you got the firmware files from?
Does Odin says "success" when flashed and "passed"?
Does the phone reboot after Odin flash?
Have you ever flashed a custom Rom to the phone?
Have you in any way modified the bootloader?

cooltt said:
Ok the only reason it will not boot after a successful firmware flash with Odin is if the EFS partition is corrupt or missing.
You need to tell us exactly what you've done with the phone before this happened.
What country are you in?
What firmware did you have on your phone originally?
Where have you got the firmware files from?
Does Odin says "success" when flashed and "passed"?
Does the phone reboot after Odin flash?
Have you ever flashed a custom Rom to the phone?
Have you in any way modified the bootloader?
Click to expand...
Click to collapse
Okay. I got the phone like this it started to happen slowly sometimes 10 minutes reboots then working fine.
I have the latest german dbt firmeware from samfile.
If i check auto reboot it reboots after the flash.
It says succes yes.
I have never flashed a custom rom or bootloader to it it has still the frp lock on.

Huzalio said:
Okay. I got the phone like this it started to happen slowly sometimes 10 minutes reboots then working fine.
I have the latest german dbt firmeware from samfile.
If i check auto reboot it reboots after the flash.
It says succes yes.
I have never flashed a custom rom or bootloader to it it has still the frp lock on.
Click to expand...
Click to collapse
This is your problem. Even when the phone boots on your going to have a major problem getting past this.
Look for a guide on how to bypass FRP Lock on Oreo, it can be a tedious process of installing TWRP and flashing combination firmware. Never ever ever ever flash anything with FRP lock on it causes so many problems and there's lots of threads about it here.

cooltt said:
This is your problem. Even when the phone boots on your going to have a major problem getting past this.
Look for a guide on how to bypass FRP Lock on Oreo, it can be a tedious process of installing TWRP and flashing combination firmware. Never ever ever ever flash anything with FRP lock on it causes so many problems and there's lots of threads about it here.
Click to expand...
Click to collapse
Okay i see.
Do you somehow have a good tutorial?

Huzalio said:
Okay i see.
Do you somehow have a good tutorial?
Click to expand...
Click to collapse
i had the frp lock too!! ,
https://forum.xda-developers.com/galaxy-s7/help/frp-lock-please-help-t3925674
for me it helped only flashing the AP and nothing else .. but you are already beyond that point becasue you flashed the bootloader BL i think ,
once the recovery and system partition are stock you should be able to boot (frp lock blocks modified recovery twrp or system , you must enable oem unlock in the developer options or it will frp lock for customizations you probably disabled it without knowing what it is(like me) ) ..
but ive red some other stories here , and they all boiled down to NOT flash the BL becasue it messes up the flashing for the otehr partitions ...
TRY FLASHING without BL !
i hope its not hardbricked or needs tons of tinkering
try to flash this AP : it worked for me , maybe it works for you ! (lets pray) (its from german vodaphone but it shouldnt matter)
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B

Ulf3000 said:
i had the frp lock too!! ,
https://forum.xda-developers.com/galaxy-s7/help/frp-lock-please-help-t3925674
for me it helped only flashing the AP and nothing else .. but you are already beyond that point becasue you flashed the bootloader BL i think ,
once the recovery and system partition are stock you should be able to boot (frp lock blocks modified recovery twrp or system , you must enable oem unlock in the developer options or it will frp lock for customizations you probably disabled it without knowing what it is(like me) ) ..
but ive red some other stories here , and they all boiled down to NOT flash the BL becasue it messes up the flashing for the otehr partitions ...
TRY FLASHING without BL !
i hope its not hardbricked or needs tons of tinkering
try to flash this AP : it worked for me , maybe it works for you ! (lets pray) (its from german vodaphone but it shouldnt matter)
https://updato.com/firmware-archive-select-model?record=92A63C2C07D011E99F15FA163EE8F90B
Click to expand...
Click to collapse
sadly no succes :/

Huzalio said:
sadly no succes :/
Click to expand...
Click to collapse
I think it's obvious you don't know what your doing, no offence. Everything that's been suggested should work with no problems. You are better off taking it to a Samsung centre to fix it. I doubt anyone will be able to help you here.

unbricking with the factory binary
This method is not for the faint of heart; it involves downloading 1) the factory binary for your phone, and 2) the correct firmware for your phone (which you can find at sammobile). I don't know if it will fix your particular problem but if everything else has failed, it's worth a try. You will basically be taking your phone back to its state when it was first set up at Samsung factory, before the firmware for your region was installed. I used this to get past a drk imei error, it's worth taking a look. Anyone else who knows more than me, please weigh in on what you think about it.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516

S10e Literally stuck in bootloops after 2020 Update

So i updated my phone automatically yesterday from the latest update, after it was done, i haven't been able to access my phone in anyway, it keeps on looping samsung logo and a window that says "This phone's bootloader is unlocked´and its software integrity can't be verified" and so on, ive tried to enter either Download mode and recovery mode, but none of the methods seems to have an affect on the phone at all, please help, thanks

Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.

FakerS3 said:
Hmm if u have PC download Smart Switch and do Emergency Firmware recovery. That should fix it totally.
Click to expand...
Click to collapse
- The phone does not show up on the pc either

Was your phone rooted? That could explain it.

riggerman0421 said:
Was your phone rooted? That could explain it.
Click to expand...
Click to collapse
Yes

thorius95 said:
Yes
Click to expand...
Click to collapse
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?

chibuche said:
Same issue here. s10e stuck in boot loop (between samsung logo and warning about the bootloader being unlocked) after yesterday's update.
So far I had no success putting the phone into recovery or download mode.
The phone was rooted, then flashed with custom ROM, then flashed again with stock firmware. I kept the bootloader unlocked because I read it was risky to re-lock the bootloader.
So, is it now hopelessly bricked?
Click to expand...
Click to collapse
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way

Never attempt to update if you have rooted and made any changes to the system, deleted or added system apps, modified kernel, changed boot logo,etc.

thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
So, here's how I put the phone in download mode.
I left the battery to drain completely, then without pressing the power button, I pressed the volume down and Bixby button; and only then I plugged the cable. Without pressing the power button, the phone started straight into Download mode.
Now Odin sees the phone, I'm about to flash it with the stock firmware and see what happens.

thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
Maybe this thread helps: https://forum.xda-developers.com/galaxy-s10/help/galaxy-s10-bootloop-updte-to-android-10-t4023201
It's probably Samsung's vaultkeeper that caused the bootloop.

thorius95 said:
Thats a good question, far as i know, my phone is unable to get any form of connection to the pc, not able to start up in recovery or download mode either. What i know for sure, there is a way out, we just have to find the way
Click to expand...
Click to collapse
I just wanted to give an update of how I rescued my phone and kept all the information on the phone memory intact (this was one of the challenges, as I had some photos on it).
I put it in download mode by draining the battery, then tried to flash the updated firmware. It didn't work, leading once again to boot loop and all I could do was boot to the stock Android recovery - not helpful.
So I got it to download mode again and flashed the stock firmware it originally came with (prior to the update). In Odin, I put HOME_CSC in the CSC field, to keep the phone memory from being erased. This solved it.
Hope this info can help someone having the same issue.