Database Info

No download mode, no recovery, detected by odin, not kies

Hi,
I rooted my brandnew GT-P3110 with cf, flashed pacman and cwm recovery. I do not blame anybody alse for my issues but myself. I guess I messed up the restoring of NON-system-apps:
After a day of troublefree use the tablet randomly rebooted and came back with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". No booting into recovery possible, no booting into download mode, no regular boot. Just the same message over and over again. Battery is unremovable.
I installed Kies, updated it, it downloaded drivers but under "emergency recovery" my tablet didn't appear. I then followed the "Firmware Upgrade and Initialization" procedure wich downloaded the necessary files but aborted with a korean text shown in the attachment after replugging the tablet. I tried this with 2 different USB-cables on several USB-ports. Kies btw asked me to remove the battery (not possible) after entering device number and serial-number. I turned off by pressing the off button instead and it turned on again.
I uninstalled Kies, rebooted, installed the samsung drivers manually, rebooted. I installed odin 1.85 (and later 1.3) and downloaded my contry's stock firmware (and later a newer version of the same firmware and another country's stock) from sammobile. I tried to flash them first without "repartition" ticked, later with it ticked but without a pit file (i can't find it!). I got four different errors, two are attached, the third was somethign like "cant write (line 1876)" and "cant write (line 1440)".I tried three stock firmwares with two version of odin with two USB cords on everal ports on ONE computer. I remove the tablet every time, exited odin every time, run it as admin, disabled firewall, xp-antispy and antivirus. I'm on Windows 7.
Besides a million other threads I found this one, but I wasn't able to solve my issue with it: http://forum.xda-developers.com/showthread.php?t=1652398
For 48 hours i tried to solve this problem by myself. Now I hope to find out if there's a point in continuing or if I can give up and throw away the piece of samsung.
Cheers,
404

android404 said:
Hi,
I rooted my brandnew GT-P3110
404
Click to expand...
Click to collapse
Try odin 1.61 1.85 sometimes itll jar it loose

vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?

vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
Thanks but it didn't work.
wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Mine is still bricked. Good luck.

facing same problem in my samsung tab 2 p3100 after root

wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.

novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
Click to expand...
Click to collapse
Thanks. Well, I understand the theory. I have had trouble finding a PIT file that I am sure is for my device. I did save a PIT file but I think it is corrupt because using it requires me to let the battery die afterwards to get back to download mode. Same for the bootloader. I have a few things I've tried, but not sure I have one that is exactly for the GT-P5113 (in fact, I never did find a JB for the 5113 just the 5110 and it never would load).

Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.

I can do each thing you mentioned, but my device is not getting detected by my PC. When I insert USB it says USB not recognized and it is not detected by Odin, adb and anything else. I am stuck on Boot Logo for my P3100 and when I go into recovery, it says USB not recognized. Fully messed up. Can you help me out here.
novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.
Click to expand...
Click to collapse

2 years later .... did you ever unbrick this? I'm dealing with a P5113 now that's stuck at the "Firmware upgrade encountered an issue" screen. <sigh>
wd5gnr said:
Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.
Click to expand...
Click to collapse

No. I finally sent it to one of these ebay guys who will JTAG it since I was too lazy to wire up one of my JTAG probes. They worked on it and said it was simply dead and the only alternative would be to replace the flash chips.
Bought a Nexus 7.

I've got the pit files for P311x and P3100 on my website https://sites.google.com/site/jrc2swebsite/downloads/samsung-galaxy-tab-2-70-p31xx

Samsung galaxy S6: Recovery is not seandroid enforcing

I tried to root my sgs6 with an CF auto root. This didn't work because after the first reboot of my Phone I got the message:
"Recovery is not seandroid enforcing"
I've been looking on the internet and have seen several options which didn't work, including:
- Getting into recovery mode (home + on/of button + volume UP). This doesn't work somehow.
- Try to install stock firmware.
- Retry the same root
- Try a different root.
Also; connecting via Kies/Smart Switch gives me the reply that the S/N isn't valid. This however, is not true.
The biggest problem that I seem to have is connecting my phone to my computer properly. And I can't turn on 'USB debugging' anymore (I turned it on when I started with my root).
So maybe my first question is: How can I get my phone to connect with my computer properly?
And after that; How can I fix the failed root.
Additional info:
Model name: SM-G920F
Android 5.1.1. before I tried to root my phone.
If additional information is required, please let me know.
Thanks in advance.

Hello,
Welcome to XDA.
To better assist you, your thread will be moved to your device Q&A forum linked below.
http://forum.xda-developers.com/galaxy-s6/help
The experts there may be able to help. Good luck.

Not an expert, but I've got the same message in the top left corner on the bootscreen after installed TWRP trough Odin and flashing adam-kernel.
Does not interfere with my phone working though. Even SmartSwitch still recognises it. Maybe wrong version of autoroot?

We found the solution:
We downloaded the original stock firmware and installed it through odin. Some things we encountered during the solving:
- It failed on the hidden.img
- We had to extract that file and load it seperatly through odin.
At that point the phone kept resetting, but after removing the cable from the computer and charging it with the normal charger it booted like normal again. The android sign (which we saw before but the phone went rebooted all the time) stayed in the screen and after a couple of minutes it started installing.
After 10-15 minutes the phone worked again!
Tnxs for your efforts!

[Completed] Bootloop and softbrick on Verizon Galaxy S3 SCH-I535

Hey Folks,
So as the title says... I'm lost and with a bootloop's fan with is a softbrick by now.
About my phone:
Verizon Samsung Galaxy S3 SCH-I535 from 2012
Acquired with Jelly 4.3 and root it with towelroot and SuperSU so I could use it abroad. Upgraded it using the Verizon Upgraded tool to Kitkat 4.4.2 and everything was fine.
The Story:
I encountered an issue with my apps (Fb, German Bahn and Whatssapp to mention the first ones). Facebook was completely wiped out on its own and I had to install it again. The other apps their icons turned into the Android Icon and although I could use whatsapp to receive calls, I couldn't open it and I had to uninstall it. Said this I lost my whatsapp ID because of my number being different and my being abroad. I got a few new apps to solve that but once resintalling Whatsapp it told me to erase a task killer app (Battery Doctor) and I did. Two to three hours after my phone restarted itself and told me I had to factory reset which freaked me out and I looked for information to avoid this. I found none but a good recovery tool for numbers and messages.
I confronted the factory reset button like a man and nothing happened. Just bloop bloops.
I've tried flashing it with Odin and I followed so many instructions with must of them failing to some spot (NAND write FAIL!, cache.img.ex2-3-4 NOT Auth, and at some point I tar(ed) and untar(ed) my tar.md5 files and remade them in certain order I found in a post here about solving the NAND Write issues. Part of it included ticking the "NAND erase all" (which I fear by now already deleted the data I so much wanted to keep) and remake them my files with extension xxx.img for all the important ones but xxx.bin and xxx.mbn.
I succesfully flashed a recovery.img from a file called "Verizon_SCH-I535-StockRecovery.tar" (you can find it online) but now it won't even let me get to the factory reset screen and automatically reboots itself.
NOTE: it never gave me the menu option in recovery mode because it would restart. But when I didn't try to go into recovery mode I would see the factory reset screen. I am not sure what happened there.
PLEASE, I've been 5 days working on this and I also encountered issues with my laptop after downloading so many ROMs and Odin versions but I was able to fix that.
Any ideas?
List of ROMs I've tried flashing to no avail.
-ROM for my phone getting into Jelly 4.3
-ROM for my phone for Kitkat 4.4.2
-BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship-tar.md5
-i535VRUDNE1_I535VZWDNE1_I535VRUDNE1_HOME.tar.md5
-openrecovery-twrp-2.8.5.0-d2vzw.tar
-StockVerizonGalaxyS3WithRoot.zip
-stock.vzw_root66.tar --> here the issues where the cache.img.ext4 which I changed the just -.img, -.img.ext2, -.img.ex3 and nothing happened.
Did create a tar file with the recovery.img of the stock.vzw_root66.tar file and it did work for flashing on the PDA but when it restarted I am still in a bootloop after getting into recovery mode within 4-5 seconds.
NOTE about RECOVERY MODE:
I don't have any menu to work with the sequences of holding POWER button and pressing VOLUME UP once and releasing didn't work. Neither the other way around. Tried also with POWER, VOLUME UP and HOME and I get a seemingly working Android figure during one second and then turns into the dead Android one for 4-5 secs and restarts.
Succesful ones but with no change for better or for worse:
-VRALEC.bootchain.tar.md5
-Said before recovery.img from the stock.vzw_root66.tar file
AND the pitfile for my phone SCH-I535_D2VZW_16gd.pit (Which I already used and gets me the PASS word... but nothing else)
Please can any one help me fix it? I looked the the right ROM several times and still not working. Should I just turn into a different OS other than Kitkat and/or Jelly? I haven't tried upgrading to Lollipop yet but I am thinking/fearing it might be a solution.
To Sum up,
- Recovery mode doesn't give me any option
- My phone reboots itself on recovery mode - checked all the buttons and I took them off even but still does.
- I can go into ODIN mode and stays there all day!
On ODIN mode it says:
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER RP SWREV: 2
ODIN fails to flash any WHOLE ROM file and just can "flash" the PIT and two different recovery.img (the latest from the stock.vzw_roo66.tar file.
Hope this doesn't give anyone a headache after reading it!

XDA Visitor said:
Hey Folks,
So as the title says... I'm lost and with a bootloop's fan with is a softbrick by now.
About my phone:
Verizon Samsung Galaxy S3 SCH-I535 from 2012
Acquired with Jelly 4.3 and root it with towelroot and SuperSU so I could use it abroad. Upgraded it using the Verizon Upgraded tool to Kitkat 4.4.2 and everything was fine.
The Story:
I encountered an issue with my apps (Fb, German Bahn and Whatssapp to mention the first ones). Facebook was completely wiped out on its own and I had to install it again. The other apps their icons turned into the Android Icon and although I could use whatsapp to receive calls, I couldn't open it and I had to uninstall it. Said this I lost my whatsapp ID because of my number being different and my being abroad. I got a few new apps to solve that but once resintalling Whatsapp it told me to erase a task killer app (Battery Doctor) and I did. Two to three hours after my phone restarted itself and told me I had to factory reset which freaked me out and I looked for information to avoid this. I found none but a good recovery tool for numbers and messages.
I confronted the factory reset button like a man and nothing happened. Just bloop bloops.
I've tried flashing it with Odin and I followed so many instructions with must of them failing to some spot (NAND write FAIL!, cache.img.ex2-3-4 NOT Auth, and at some point I tar(ed) and untar(ed) my tar.md5 files and remade them in certain order I found in a post here about solving the NAND Write issues. Part of it included ticking the "NAND erase all" (which I fear by now already deleted the data I so much wanted to keep) and remake them my files with extension xxx.img for all the important ones but xxx.bin and xxx.mbn.
I succesfully flashed a recovery.img from a file called "Verizon_SCH-I535-StockRecovery.tar" (you can find it online) but now it won't even let me get to the factory reset screen and automatically reboots itself.
NOTE: it never gave me the menu option in recovery mode because it would restart. But when I didn't try to go into recovery mode I would see the factory reset screen. I am not sure what happened there.
PLEASE, I've been 5 days working on this and I also encountered issues with my laptop after downloading so many ROMs and Odin versions but I was able to fix that.
Any ideas?
List of ROMs I've tried flashing to no avail.
-ROM for my phone getting into Jelly 4.3
-ROM for my phone for Kitkat 4.4.2
-BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship-tar.md5
-i535VRUDNE1_I535VZWDNE1_I535VRUDNE1_HOME.tar.md5
-openrecovery-twrp-2.8.5.0-d2vzw.tar
-StockVerizonGalaxyS3WithRoot.zip
-stock.vzw_root66.tar --> here the issues where the cache.img.ext4 which I changed the just -.img, -.img.ext2, -.img.ex3 and nothing happened.
Did create a tar file with the recovery.img of the stock.vzw_root66.tar file and it did work for flashing on the PDA but when it restarted I am still in a bootloop after getting into recovery mode within 4-5 seconds.
NOTE about RECOVERY MODE:
I don't have any menu to work with the sequences of holding POWER button and pressing VOLUME UP once and releasing didn't work. Neither the other way around. Tried also with POWER, VOLUME UP and HOME and I get a seemingly working Android figure during one second and then turns into the dead Android one for 4-5 secs and restarts.
Succesful ones but with no change for better or for worse:
-VRALEC.bootchain.tar.md5
-Said before recovery.img from the stock.vzw_root66.tar file
AND the pitfile for my phone SCH-I535_D2VZW_16gd.pit (Which I already used and gets me the PASS word... but nothing else)
Please can any one help me fix it? I looked the the right ROM several times and still not working. Should I just turn into a different OS other than Kitkat and/or Jelly? I haven't tried upgrading to Lollipop yet but I am thinking/fearing it might be a solution.
To Sum up,
- Recovery mode doesn't give me any option
- My phone reboots itself on recovery mode - checked all the buttons and I took them off even but still does.
- I can go into ODIN mode and stays there all day!
On ODIN mode it says:
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
BOOTLOADER RP SWREV: 2
ODIN fails to flash any WHOLE ROM file and just can "flash" the PIT and two different recovery.img (the latest from the stock.vzw_roo66.tar file.
Hope this doesn't give anyone a headache after reading it!
Click to expand...
Click to collapse
Hi,
Kindly register yourself at XDA post which you can query in http://forum.xda-developers.com/galaxy-s3-verizon/help
Experts there may be able to help you

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

Did I just brick my device?

Hey guys!
So basically I will start from the top:
1. Device is Samsung Galaxy Note 10 Lite (SM-N770F) (F/DS if it matters really)
What happened is:
I've wanted to install Android 11 update on my phone - downloaded SamFirm app, searched for correct firmware for my region (I've made sure to select appropriate device and region).
Then I've downloaded Odin (3.14.1), loaded all files correctly - no errors or anything, started the process in Odin and after some time I got an error on the phone - Custom Binary(SUPER) Blocked By OEM Lock.
Now what happens is that I can't do literally anything with my device - it's turned on constantly on the same screen, on the top I can see the above error in red font, while on the center of the screen there is message "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." - which I of course did, but Smart Switch doesn't even see the device or anything.
I can't turn off the device - while I press power and volume down button, it just goes black for a moment and comes right back up on the same screen no matter what.
Although, I think it's in downloading mode - Odin still sees it correctly (when I plug it in or out I can see changes in Odins screen).
Tried downloading older versions through SamFirm, other versions of Odin, other USB in computer, other cable - no luck at all.
Did I fully bricked the device? Or is it just soft bricked? Is there anything I can do now? Can Samsung center help me? I've tried chatting with them but they just sent me to their facility.
I'd do literally anything to fix this. Please help me, I'm desperate.

If you can get into recovery, i would try factory reset there. Then go to downloadmode and try complete new flash of newest version with csc (not home_csc). But im not sure, wether it is possible to flash with odin if bootloader is not unlocked in this new samsungs. I allways used odin with unlocked bootloader.

can't get into recovery - only thing I see is the above mentioned screen and there is 0 possibility of going anywhere else

priamusx said:
Hey guys!
So basically I will start from the top:
1. Device is Samsung Galaxy Note 10 Lite (SM-N770F) (F/DS if it matters really)
What happened is:
I've wanted to install Android 11 update on my phone - downloaded SamFirm app, searched for correct firmware for my region (I've made sure to select appropriate device and region).
Then I've downloaded Odin (3.14.1), loaded all files correctly - no errors or anything, started the process in Odin and after some time I got an error on the phone - Custom Binary(SUPER) Blocked By OEM Lock.
Now what happens is that I can't do literally anything with my device - it's turned on constantly on the same screen, on the top I can see the above error in red font, while on the center of the screen there is message "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." - which I of course did, but Smart Switch doesn't even see the device or anything.
I can't turn off the device - while I press power and volume down button, it just goes black for a moment and comes right back up on the same screen no matter what.
Although, I think it's in downloading mode - Odin still sees it correctly (when I plug it in or out I can see changes in Odins screen).
Tried downloading older versions through SamFirm, other versions of Odin, other USB in computer, other cable - no luck at all.
Did I fully bricked the device? Or is it just soft bricked? Is there anything I can do now? Can Samsung center help me? I've tried chatting with them but they just sent me to their facility.
I'd do literally anything to fix this. Please help me, I'm desperate.
Click to expand...
Click to collapse
I experienced similar situation, but in my case, even my phone stuck in download mode screen, ODIN did not detect my phone, even PC wasn't response when plug in USB cable. As same as you say, when I tried to power off, it was power on itself and "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" message appear on screen.
Then I tried to enter download mode again in download mode screen, by pressing power off, and after screen go black press immediately volume up+down. After that phone enter the download mode screen (again), it was looks like the same, but this time I was able to install firmware. Actually I really dont understand why this method work but you can give a try.

Unfortunately, still no luck.
But I've thought about other thing. Do you think it's possible to use .PIT file and re-partition option in Odin?
From what I've read everywhere this will wipe all partition data (so basically it should wipe every single thing) from the device, so it should be possible to overcome this oem lock, shouldn't it? Or will I just brick the device even further? I'm kinda desperate here as the phone is about 2-3 months so it's as brand new...
Edit: I think I've found another issue here. My device model is SM-N770F/DS so it's a Dual Sim model, while everywhere I only see firmware for SM-N770F so without dual sim. May it cause problems as well? How about the above option with flashin firmware with pit file and wiping partitions?

If you have figured it out by now good for you. If not, that emergency screen you see is nothing to fear. You can flash firmware with Odin from that screen...no worries your not bricked. Just do as you would if the device were in download mode..flash away.

Was your bootloader unlocked?