Database Users

[Q] galaxy s4 flashing CWM wont work "no Command"

1st time flashing my S4. i have experience flashing custom roms and anything on my S3 before and never encountered problems. phone specs are:
Model: I9505
Android Version: 4.4.2
Baseband Version: I9505XXUGNG8
Write Protection Enabled
Burst Mode Enabled
i have turned on debugging. no kies on background and installed USB drivers.
I used odin 3.07
tried to flash latest version of CWM recovery
flash was successful but when i try to go on recovery the screen says "No Command" and i only get the official recovery. i have tried other versions but the same results I get. Help please. This is the first time for the phone to be flashed.

The FAQ is for you too.

for anyone with the same problem i have a fix for it i have solved my problem. you have to uncheck the AUTO REBOOT from Odin then flash the recovery .tar file you will see that the flashing is complete remove the battery and the USB cable. wait 10 sec. put it back together then go to recovery mode immediately otherwise it wont work.

Failed modem flash bricked Note 4 SM-N910G

I was trying to flash a modem/bootloader for my phone after the initial flash of a new ROM and the Odin failed to flash the modem and my phone is now stuck in a
" Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try Again. "
However, Kies doesn't recognise my device (I use a custom ROM before the one I was trying to flash as well) and I cannot do anything to my phone right now. What do I do? I cannot even get it into recovery mode to restore my phone or try to flash the modem again.
I tried the Kies emergency recovery mode but my phone is not displayed there and it says my phone isn't compatible with Kies 3, so trying the normal samsung Kies right now.
Anyone with a recovery code for the Samsung N-910G?
Need some help please!
EDIT: Solved the problem by flashing the modem and bootloader again and works this time round.

nexezz said:
I was trying to flash a modem/bootloader for my phone after the initial flash of a new ROM and the Odin failed to flash the modem and my phone is now stuck in a
" Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try Again. "
However, Kies doesn't recognise my device (I use a custom ROM before the one I was trying to flash as well) and I cannot do anything to my phone right now. What do I do? I cannot even get it into recovery mode to restore my phone or try to flash the modem again.
I tried the Kies emergency recovery mode but my phone is not displayed there and it says my phone isn't compatible with Kies 3, so trying the normal samsung Kies right now.
Anyone with a recovery code for the Samsung N-910G?
Need some help please!
EDIT: Solved the problem by flashing the modem and bootloader again and works this time round.
Click to expand...
Click to collapse
Can you give me debrick img from yaou n910g. Pleas help me... My phone dead boot.

6.0.1 bootloader back to 5.1.1

Does anyone know if it is possible to downgrade back to 5.1.1 bootloader after flashing the 6.0.1 one?
With the Note 3 I lost the imei and baseband etc trying to downgrade certain bits, so I don't want the hassle if that is going to be the case with 6.0.1 and 5.1.1.

i tried flashing also 6.0.1 and ended bricking my phone. would love to see if you find a solution for that.

mrelie007 said:
i tried flashing also 6.0.1 and ended bricking my phone. would love to see if you find a solution for that.
Click to expand...
Click to collapse
Can you still get into download mode?
When I put bobcat rom on mine I didn't change the bootloader to the older one, I was stuck on the s6 edge+ bootscreen, I have to plug USB into pc and then hold the power+home+vol down for a few seconds and that rebooted into download mode where I managed to flash the correct bootloader. You can also then restart the phone and use power+home+vol up to get into recovery to restore a back up. Not sure why I had to plug in USB cable though but if I didn't I couldn't reboot at all and was stuck on the bootscreen.

hi yes i can go in download mode and i can go in twrp. but flashing a new rom always fails for me. stock firmwares as well. can u attach me ur bootloader plz so i can try it?

https://mega.nz/#!ScsAwbIC!hH4Djamv7FoeAUyDbHElKjaIlXLqvTZynPRqdJPwDas
This is the link to the bootloader I used (taken from bobcat thread)
Use download mode and put it in the BL part in odin.

can help me with bootloader 5.1.1
sm g928c

Please help!!!!!!

Today i was trying to install the Android Marshmallow 6.0.1 on my Galaxy S5 Snapdragon via Odin, i downloaded the firmware from Sammobile, i verified that the phone model was exactly the same as named on the firmware, i place the .md5 file in the AP slot and everything was ready to go! (The phone was already plugged and in Bootloader mode, and drivers were up to date) then when finishing the flash Odin FAILS to complete the flash and the phone is left with nothing than the Download mode, i panic and try to access recovery mode but realize that there´s no recovery....I proceed to install the recovery.tar into my phone and it works, i start the phone and Samsung logo comes up, finally it loads and does al the process after you flash a Samsung phone.
Everything works just fine!...except for one thing, THERE´S NO RECOVERY!!!. The phone works perfectly but when i try to enter recovery mode, it sends me to Odin mode as it displays a message saying that failed to boot into recovery.
Please help me i don´t know what to do.
Thanks!

Just flash a custom recovery like twrp or cwm

Already did...same problem, recovery won't boot

adavicco said:
Already did...same problem, recovery won't boot
Click to expand...
Click to collapse
You need to flash a pit file to complete the install correctly.

S8 Hardbricked?

Hey, so I wanted to install TWRP on my S8, I have flashed it via odin, and I have experienced a bootloop - I think no worries, I'll try to flash stock firmware - Well...
I did try so - apparently bootloader was "newer?" so I skipped BL section in odin, I did the rest - it flashed BOOT, and then failed at next stage...
Now my s8 won't boot even into download mode - and it says:
"An error has occured while updating the device software.
Use the emergency recovery function in the smart switch PC software" Thing is - the smart switch software doesn't recognise my device.
Am I hardbricked out of my S8 - or is there still hope?
Thank you very much in advance!
EDIT: nevermind, I CAN boot into download mode, I just wasn't quick enough to boot into it, my bad.
I am downloading a new stock firmware and I'll see if this one works.

RakoPL said:
Hey, so I wanted to install TWRP on my S8, I have flashed it via odin, and I have experienced a bootloop - I think no worries, I'll try to flash stock firmware - Well...
I did try so - apparently bootloader was "newer?" so I skipped BL section in odin, I did the rest - it flashed BOOT, and then failed at next stage...
Now my s8 won't boot even into download mode - and it says:
"An error has occured while updating the device software.
Use the emergency recovery function in the smart switch PC software" Thing is - the smart switch software doesn't recognise my device.
Am I hardbricked out of my S8 - or is there still hope?
Thank you very much in advance!
EDIT: nevermind, I CAN boot into download mode, I just wasn't quick enough to boot into it, my bad.
I am downloading a new stock firmware and I'll see if this one works.
Click to expand...
Click to collapse
What model s8 do you have. The snap dragon model US cannot be rooted above revision 3 and no twrp either

TheMadScientist said:
What model s8 do you have. The snap dragon model US cannot be rooted above revision 3 and no twrp either
Click to expand...
Click to collapse
As far as I remember it was g950f
Hey, so I have managed to fix the bootloop via just downloading a newer stock firmware for international model (g950f) and flashing that through odin - seeing as the phone now booted up I decided to bite the bullet again and downloaded latest twrp again - flashed it and this time it worked 100%, flashed magisk and now I am rooted, I guess that was a false alarm, but I got into a quite a panic mode when the previous stock firmware wouldn't flash.
It's solved now, so cheers!