My phone (SM-G955F) wont enter recovery mode, and wont restore back to stock firmware - Samsung Galaxy S8+ Questions & Answers

Dear mods if this is wrong place please by god move it to the correct place
Hello, so I flashed the latest TWRP recovery to my phone but it gave me errors so went back and forth to stock firmware just to try to get it work.
so Finally I flashed an older TWRP recovery through Odin. after that my phone stopped going into recovery, so I tried to flash back to the latest version of TWRP through Odin. but this time I failed.
so I tried to do what I did earlier and tried to flash stock firmware but no Odin just gives me an instant fail when trying to flash back to stock.
and my phone now only boots into download mode but its useless as it stopped working on flashing the stock firmware...
and when not entering download mode its freezes on Samsung s8+ screen and wont go into recovery.
Is it a hardware failure maybe?

should also add I'm now at this wery moment downloading another firmware to see if I am able to flash that firmware on to this device, even tried using PIT files without a luck :/

Okay. I would recommend to restore back to stock before anything. Do that using smart switch from Samsung.
Phone needs to be in download mode and then you open smart switch and click on more. Then choose Emergency Software and Initialization. Now click on the*device Initialization*tab.
You'll need your s/n number which can be found on the back of your phone and you'll need build number.
Which is:
SM-G950F
or
SM-G955F for plus model

Sweet I am trying it right now and going to give feedback if it works
so any clue why TWRP gives me verification failed no matter what I trY, it litterly allways ends upp telling me to factory reset my phone

so here we go
Shuuin said:
Okay. I would recommend to restore back to stock before anything. Do that using smart switch from Samsung.
Phone needs to be in download mode and then you open smart switch and click on more. Then choose Emergency Software and Initialization. Now click on the*device Initialization*tab.
You'll need your s/n number which can be found on the back of your phone and you'll need build number.
Which is:
SM-G950F
or
SM-G955F for plus model
Click to expand...
Click to collapse

Shuuin said:
Okay. I would recommend to restore back to stock before anything. Do that using smart switch from Samsung.
Phone needs to be in download mode and then you open smart switch and click on more. Then choose Emergency Software and Initialization. Now click on the*device Initialization*tab.
You'll need your s/n number which can be found on the back of your phone and you'll need build number.
Which is:
SM-G950F
or
SM-G955F for plus model
Click to expand...
Click to collapse
it ended up as a fail saying that the device is not supported, im ****ed

It keeps saying that, everytime you try to restore using smart switch ?
Okay if.
Then, when you boot into Download mode. Reboot into download mode again, just fast.
With that i mean, hold ( Power, volume-down, bixby ) enter download mode, when youre in download mode, repeat (power, volume-down and bixby) and enter download mode.
That fixed my problem i had once, where it said fail with everything i tried to transfor with odin and with smart swtich.
Hope you understand.
Sorry, late reply. work

Shuuin said:
It keeps saying that, everytime you try to restore using smart switch ?
Okay if.
Then, when you boot into Download mode. Reboot into download mode again, just fast.
With that i mean, hold ( Power, volume-down, bixby ) enter download mode, when youre in download mode, repeat (power, volume-down and bixby) and enter download mode.
That fixed my problem i had once, where it said fail with everything i tried to transfor with odin and with smart swtich.
Hope you understand.
Sorry, late reply. work
Click to expand...
Click to collapse
Thanks it did work thanks mate

Related

[Q] no battery pull precludes recovery

I tried to use chainroot, and got stuck on the logo screen. normally you'd battery pull, go to recovery and wipe data. but i can't find any way to shut down the phone, before doing power-upVol-home.
And now i've tried to odin a stock recovery to undo chainroot, odin fails. could re-run odin with auto-reboot off, but again, no way to shut off and go to recovery.
at this point i'm stuck with the blue screen asking me to use smart switch on PC to do emergency recovery. but smartswitch says the device is not recognized.
thoughts? thanks!
I was stuck rooting on the boot logo too. Had to use odin 3.10 and did "run as administrator". Also if this helps to reboot the stuck phone press vol down+power together until the screen blanks out. If you need to get into download mode, as soon as the screen blanks out, press and hold the Home button ( Don't let go of the vol down and power though ).
Good grief.... the non-removable battery has made these recovery tricks so difficult
thanks twisted_mind. at this point, i only get the blue screen asking me to do smartswitch recovery, and the one thing i CAN seem to do is volDown-power-home and it easily goes to download mode. i have not been able to get to recovery mode no matter what i do (including volUp-power-home, even before this smartswitch message came up after i tried to odin a stock recovery).
so i can still go to dload mode, and stick in a stock rom. the ones i've tried are from sammobile, and a potential issue is that i don't know the exact one to pick (this phone is a demo here in europe and i didn't note the details under settings when it was working). so the ones i try end in an odin FAIL. again, i've also tried odin unchecking auto-reboot, but then the phone is stuck at the very end of dload ("don't turn off target", etc), and i have no way to battery pull, etc.
Instead of holding power to shut off you have to hold power and vol down
jasonastley said:
I tried to use chainroot, and got stuck on the logo screen. normally you'd battery pull, go to recovery and wipe data. but i can't find any way to shut down the phone, before doing power-upVol-home.
And now i've tried to odin a stock recovery to undo chainroot, odin fails. could re-run odin with auto-reboot off, but again, no way to shut off and go to recovery.
at this point i'm stuck with the blue screen asking me to use smart switch on PC to do emergency recovery. but smartswitch says the device is not recognized.
thoughts? thanks!
Click to expand...
Click to collapse
Hello
I'm stucked on the same corner, i used Chainroot with odin 3.10.6 with no luck, just as what
happened with you, my S6 international module stucked on logo screen.
where did you get S6 stock recovery from?
Thanks
ktetreault14 said:
Instead of holding power to shut off you have to hold power and vol down
Click to expand...
Click to collapse
I have the turquoise screen that says "an error has occurred... use the emergency recovery function in smart switch...". if i do power + volDown there OR when the phone is stuck in download mode after the odin fail, the phone turns off but then comes right back on with the turquoise error screen. i've tried quickly going to the recovery key combo right when or right after the screen goes dark, but to no avail.
I can easily do power +volDown + home and go to dload mode. i just can't get into recovery mode no matter what i've tried so far.
if i could just find a stock rom that wouldn't fail in odin, or something else to use as AP/PDA in odin, i'd be set i think. wish i knew how to do this. hitting nand erase all in odin doesn't do the trick by the way.
ammsamm said:
Hello
I'm stucked on the same corner, i used Chainroot with odin 3.10.6 with no luck, just as what
happened with you, my S6 international module stucked on logo screen.
where did you get S6 stock recovery from?
Thanks
Click to expand...
Click to collapse
got the stock rom from the sammobile site. but a problem is that they have many rom's listed for the G925F and i am not certain which variety i have, or if that matters: http://www.sammobile.com/firmwares/database/SM-G925F/
jasonastley said:
got the stock rom from the sammobile site. but a problem is that they have many rom's listed for the G925F and i am not certain which variety i have, or if that matters
Click to expand...
Click to collapse
I managed to root my G920F after "odin flashing" the UK version from Sammobile, release date 11-4-2015,
Then i flashed back the CF-Auto-Root.
Know my device is booting fine and rooted
ammsamm said:
I managed to root my G920F after "odin flashing" the UK version from Sammobile, release date 11-4-2015,
Then i flashed back the CF-Auto-Root.
Know my device is booting fine and rooted
Click to expand...
Click to collapse
is the version you flashed the same version that you had prior (do the apps look the same, etc)?
so odin passed? (mine FAILs, with 4 different sammobile stock recoveries). I have the S6 Edge, maybe the S6 works fine and I just need the correct S6 Edge firmware.
jasonastley said:
is the version you flashed the same version that you had prior (do the apps look the same, etc)?
so odin passed? (mine FAILs, with 4 different sammobile stock recoveries). I have the S6 Edge, maybe the S6 works fine and I just need the correct S6 Edge firmware.
Click to expand...
Click to collapse
No its not the same version, mine was G920FZDAXSG and i flashed G920FXXU1AOCV, its a UK version, some Version
store apps was pre installed in the rom nothing more.
Odin passed normally with no issue.
i used two identical Odin v3.10.6 versions the second one i used is the one i flashed the rom and the root with.
Download the odin from this link:
samsungodindownload. com
ammsamm said:
No its not the same version, mine was G920FZDAXSG and i flashed G920FXXU1AOCV, its a UK version, some Version
store apps was pre installed in the rom nothing more.
Odin passed normally with no issue.
i used two identical Odin v3.10.6 versions the second one i used is the one i flashed the rom and the root with.
Download the odin from this link:
samsungodindownload. com
Click to expand...
Click to collapse
umm, hey ammsamm, i went to the link you just mentioned, installed it and GOT SOME NASTY SPAMWARE INSTALLED on my machine from it. I'd normally flag you immediately as a bad user, but your other comments sound legit. do you have anything to say about this?
jasonastley said:
umm, hey ammsamm, i went to the link you just mentioned, installed it and GOT SOME NASTY SPAMWARE INSTALLED on my machine from it. I'd normally flag you immediately as a bad user, but your other comments sound legit. do you have anything to say about this?
Click to expand...
Click to collapse
Actually this is not the link i downloaded the odin from i tried to
Atthach the one i have but faced with the upload limit, even
After ziping and spilting the the odin, upload failed,
So, you better find another odin 3.10.6 a version with all the buttons
are enabled.

[Q] Need help with FRP Lock PLEASE read me.

.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Odin Mode
Download Speed: Fast
Product name: SM-N920T
Current Binary: Custom
System Status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warrenty Void: 1
AP Swrev: B:2 K:0 S:0
=========
Custom Binary (Recovery) BLOCKED by FAP Lock
.
Click to expand...
Click to collapse
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.
Thibor69 said:
.
Hi - I really am in need of help. My phone which is a T-Mobile Samsung Galaxy Note 5 (was) running latest 6.x firmware,
but custom and rooted via DarkStalker's awesome ROM. All was running fine for months. I did do one thing before my phone died,
I turned OFF developer option and forgot to turn it back ON before I i rebooted. Now the phone is bricked ( I pray it is SOFT not
hard bricked ). When I turn ON the phone it just says "FRP Lock is ON" and then shuts off.
I can enter download mode but NOT recovery. This phone is my work phone and has so much important stuff on it, I just have to fix this.
Plus my wife will shot me for paying $700 and breaking it.
Anyway ... I assume I must go back to stock some how. I can boot to download mode and connect to Odin. But I tried to flash:
1) SM-N920T_1_20160702132553_r0dr7864oe.zip
Also I tried this file ( again via Odin )
2) Noble_Kernel_Auto-Root_N920T_v0.1_Rebuid3.tar.md5
But BOTH files resulted in a FAIL on the Odin screen. ( SEE PIC BELLOW )
Now when I boot it boots to a screen that says this:
Sooooo basically I can NOT boot to the OS because the FRP lock is ON and I guess should be OFF, but when I try to Odin Flash I get a FAIL at the end of the flash. ( again see picture bellow )
PLEASE HELP I will try anything. .. My job and my wife are going to kill me soon.....
Cheers to all
Thanks
.
Click to expand...
Click to collapse
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)
.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
josezr said:
If you are in the latest firmware (PH2) you have to flash the same firmware (PH2)
Click to expand...
Click to collapse
Thibor69 said:
.
Thank you sir. But ... im not sure how to tell if I am PH2 or not. Either way, could you point me to a download link for the firmware and I will try it .. please
Cheers
Click to expand...
Click to collapse
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE
josezr said:
I don't know if I can put links here, but here's
https://mega.nz/#!IJ5VlSRC!HPWdi1sjAhsDm1PoCsp_UK2jkSigsjUXsUxo2egcytE
Click to expand...
Click to collapse
Thank you so much my friend. I will try it and report back.
Cheers
Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.
I just rebooted with the developer options turned off on Friday. I was on ph1 firmware. Saw joeyv (spelling?) Deodexed stock rom with an option for an Odin installation. Did the installation through Odin and was back to stock. Odin flashed the kernel and tarp combo and was back up and running with root. No information was lost. For anyone else having this problem.
Sent from my SM-G935T using Tapatalk
Thank you JohnMonsour for taking the time to write all that. I will save it for future use if needed. BUT ... thanks to Josezr I got it fixed.
I was able to boot into download mode like I stated, but I just needed the correct firm to flash. They all failed until I tried
N920TUVS4DPH2_N920TTMB4DPH2_TMB.zip ( Thank you Josezr ).
I just flashed that file and Odin completed and phone rebooted to OS. So ALL IS GOOD. My only question now is ... inside the developer
options section ( in settings ) I have turned Developer options back ON but ... all the options that can be set ON or OFF are in the OFF
position and I am not sure which should be turned on. Can anyone please give me a quick run down on how they should be set .. like this:
stay awake on
next ones set to,
on
off
off
off
on
off
ect............
=======================
Debugging
=======================
on
on
off
ect........
=======================
Networking
=======================
on
off
off
ect........
It would sure help me. Thanks again to all 3 of you guys for helping.
Cheers
This is crazy I just ran into my phone becoming locked yesterday. T mobile sent me a update and my phone of course was set to auto update and my phone would do nothing it was a FRP LOCK. All I did was download odin and used this site to walk me through it all files are provided thanks to [ROM] [STOCK] N920TUVU3DPG1 | 6.0.1 | Deodexed | KNOX Free | 7.22.2016 by jovy23. At the bottum of the page is the download and also instruction to use odin. This was a life saver. LINK/ http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270. Copy and past everything you need to do to get out of a FRP Lock situation is in this tutorial. Thanks again Jovy23.
JohnMonsour said:
Unfortunately I did the exact same thing as you one time. And unfortunately Odin wouldn't allow me to flash anything. But there was this tool we use to use all of the time for the s4 and it's called Samsung Kies. As in "keys". Basically as long as you can get in download mode it doesn't matter how you brick it.
You just soft bricked it but the bad thing is we can't flash unadulterated version of firmware with Odin. So if frp lock is on Odin is a no go. And when I say unadulterated I mean one that's not directly from Samsung not touched or changed in anyway.... which are hard to come by in many cases in my experience. When the recovery is changed it won't pass an Odin check usually if frp lock is on. Matter of a fact I don't think you can flash anything with fap lock on with Odin. Due to the fact that frp lock is basically saying bootloader locked.
When you turn off oem mode you unlock the checks put in place by the firmware and hardware during boot. Odin uses these checks also so when you try and flash it'll be a no go. Good news for you is this already happened to me and I figured why couldn't I just restore with heimdall. Well that's a no go to. So final solution was to try out kies that I had remembered using heavily with the s4.
1. Download Samsung Kies3. Link: http://www.samsung.com/pk/support/usefulsoftware/KIES/#none
2: Install and open kies.
3. Go to the the tools tab and select firmware upgrade and initialization.
4. It will ask for your model name. Type SM-N900T.
5. Now it will ask for the Serial Number of your device. It is located on the back of your phone toward the bottom. Type that in and hit enter.
6. Now a message pops up and says the device can be restored etc...... Hit OK.
7. Now a message says Now initializing latest version. Hit OK.
8. Now it will Prepare software for initialization.
9. A screen will come up that says "Please follow the steps below to proceed with emergency recovery.
A. Make sure that the device is turned off.
B. Switch the device to recovery mode and reconnect the cable.
- To switch to recovery mode, turn on the device by pressing the Power button while holding down the Volume control "▼" Button and the Home button, and then press Continue (the Volume control "▲") button.
10. When it detects you are in download mode it will take care of the rest.
Try not to make the same mistake again.
Click to expand...
Click to collapse
its so much wrong with this write up its not funny...for one his model number is sm-n920t second if he is in frp lock then he cant turn his phone off, i tried this method it doesnt work period
you can't turn your phone off?
Yeah actually you can hard reset it and then enter download mode....
Hold volume down the home button and power for like 10 seconds then when the screen turns black you quickly hold volume down, home, and power......
You might not be able to turn it off but you can still enter recovery and download mode.
You might not be able to get into recovery depending on how screwed up your phone is.
And kies3 version was the only one that would work with the above method, now kies has checks in place that checks your knox status and if you've tripped knox it won't work. I can rewrite the guide and link the proper kies if it's really necessary. But this is from 2016 so I am sure that I don't need a proper rewrite.
And at this point I'm pretty sure it might not even matter what version of kies is used it probably does all checks server-side. So this method is obsolete for an almost obsolete phone.
Sorry I didn't help you.

Please Help I broke my phone

Hi XDA forum,
So yesterday I tried to root my phone and disaster struck. Now the phone is stuck in a bootloop where it turns on and off and on again indefinitely. I can still boot to recovery mode however. I tried to use factory reset and then reboot but I run into the same problem.
I figured that I would need to put the stock Firmware back on, and went and downloaded this: [I cant post links yet but it was the SM-G930V from sammobile .com] Because Etched on the back of my phone is Samsung SM-G930V
However, when I try to download that using Odin (Prince Comsy Version) it fails and I get a message on my phone "unsupport dev_type"
That is definitely the model type that is etched on the back of my phone.
Any ideas on what I am doing wrong/how I can get my phone to work again?
I would REALLY appreciate any help.
EDIT: this is my first post here, if it is in the wrong place please let me know.
What model does your phone say it is in download mode? It's the end all source of truth.
The firmware you're flashing, is it the latest? The G930V can't flash back to older versions, so you either have to be flashing the same version or newer from sammobile
Beanvee7 said:
What model does your phone say it is in download mode? It's the end all source of truth.
The firmware you're flashing, is it the latest? The G930V can't flash back to older versions, so you either have to be flashing the same version or newer from sammobile
Click to expand...
Click to collapse
Thanks so much for the reply!
I was trying the latest version yes. Where exactly will the phone say what model it is in download mode? I haven't seen that anywhere and that might be the issue.
Download mode should be a blue screen with text and an arrow in the background, the phone info including model will be in the top left like https://imgur.com/lvqQmws
It should be in download mode if you're trying to flash anything.
If you're in recovery you're in the wrong place (iirc they use the same button combo, but recovery is volume up, while download mode is volume down)

Error Updating with Samsung SmartSwitch

My phone is screwed
I tried to flash a rom on my J327T and failed miserably. I was having trouble getting it to boot so I went to smart switch to do an emergency recovery and my usb dropped at the phone right in the middle! :crying:
Now it just says Unsupported device. Please tell me that I can just zero out the drive and input android code somehow and bring it back to life!?!?!? And If so, How? PLEASE!!!
yours truly,
Digitally Impaired
I had the same issue but i fixed it
huckfinn9 said:
My phone is screwed
I tried to flash a rom on my J327T and failed miserably. I was having trouble getting it to boot so I went to smart switch to do an emergency recovery and my usb dropped at the phone right in the middle! :crying:
Now it just says Unsupported device. Please tell me that I can just zero out the drive and input android code somehow and bring it back to life!?!?!? And If so, How? PLEASE!!!
yours truly,
Digitally Impaired
Click to expand...
Click to collapse
What u have to do is hold power volume down and home until the downlaod screen appears and it will get ur screen off the error screeb with smart switch being the only option and to download mode. U then flash a factory firmware with regular odin. Jist the ap. I then got my phone back and running. Now the bigger question is how to downgrade to the rev1 from rev2? I ask oh and it gkes into download mode from the screen ur currently stuck on after it restarts twice while holding said buttons. Now u got to tinker a little to get odin the state device added. Simetimes it would add on the error screeb sometimes on the download screen. Ill try to find a link to the firmware i ised that worked for me. Metro?
thank you
Thanks for the tip!!!
atmosphere0012 said:
What u have to do is hold power volume down and home until the downlaod screen appears and it will get ur screen off the error screeb with smart switch being the only option and to download mode. U then flash a factory firmware with regular odin. Jist the ap. I then got my phone back and running. Now the bigger question is how to downgrade to the rev1 from rev2? I ask oh and it gkes into download mode from the screen ur currently stuck on after it restarts twice while holding said buttons. Now u got to tinker a little to get odin the state device added. Simetimes it would add on the error screeb sometimes on the download screen. Ill try to find a link to the firmware i ised that worked for me. Metro?
Click to expand...
Click to collapse
For me, the best method to flash rom is using odin..not smart switch or anything else..

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

Categories

Resources