Galaxy S8 will not boot into TWERP "No Command" - Samsung Galaxy S8 Questions and Answers

Sorry if this in the wrong forum. I'm trying to flash Lineage onto this S8 (G950FXX, dreamltexx). I turned on the Developer options and OEM unlock is toggled on. Underneath it says "Bootloader is already unlocked". USB debugging is toggled on. I used Odin 3.14.1 load twerp-3.4.0-0-dreamlte.img.tar and got a "PASS". I put a copy of SR5-SuperSU-v2.82-SR5-20171001224502.zip in the Download folder on the phone. I disconnected the S8 from my PC turned it off and attempted to boot into TWERP by holding down Vol_Up+Home+Power. It fails every time and I get the collapsed android with the exclamation mark and "No Command", then after a few seconds the Android Recovery screen appears with its 10 options. At the bottom of this screen the last error message says "#fail to open recovery_cause(No such file or directory)# I haven't installed any new drivers for the S8. I just plugged it into the Win10 PC and it seemed to find it. I don't know where to look for drivers if that is the problem.
I tried using adb and fastboot "./adb devices" seems to find the phone and report its ID number followed by the word "device". "./adb reboot-recovery" doesn't boot into TWERP I just get a reboot into Android. "./fastboot flash recovery twrp-3.4.0-0-dreamlte.img" just gives <waiting for any device >. I'm at a loss. Any assistance would be greatly appreciated.

Related

no recovery, locked boot loader, fastboot only, qualcom recovery not working

was on CM13/TWRP, suddenly my phone rebooted while i was talking, i looked at it and it had a linux logo on it....waited a bit, didn't go away, so i held power until it turned off.....then it wouldn't turn on.....so i tried recovery, nope. tried fast boot, that worked.. tried to reflash TWRP from fastboot command, failed because device is not unlocked.
can't run oem unlock because i can't get in the OS to developer mode to enable it.....
so i've been trying to do the qualcom recovery, windows 10 laptop, tried all the versions of the qualcom recovery/drivers i can find...... the recovery tool keeps giving me a red error on line 4. either that or it flat out crashes the whole program.
whats my next step? i'm attempting to run it on a windows 7 computer now thinking that may make a difference.
anyone have any thoughts?

G928G locked on recovery after failed update

Hello everyone!
A friend asked me if I could try to solve his cell´s problem.
The phone is a SM-G928G and when it boots you get the "installing system update" blue screen, then it shows a yellow triangle with an exclamation mark in the middle and then it boots into the stock recovery.
I can´t boot into download mode, either with the "reboot to bootloader" option or via the buttons (vol-, home, pwr). Anything I tried gets the same result. I tried to ADB sideload a different ROM or recovery but I always get the "wrong footer" message.
If you know a way to make it work I´d be very grateful.
Thanks

Samsung s8 fail to open recovery_cause no such file or directory

Hi, I've got a soft bricked S8. I've tried to flash stock firmware but with one, O2 it stuck on erasing at 32% and with another stopped at 24% with no command. When it boots into recovery, I get a whole list of messages at the bottom of the screen. The first one is, "#fail to open recovery_cause(No such file or directory)#" I've googled for hours and not really got anywhere. Recovery doesn't work. It's there but buttons are unresponsive sometimes. Download mode works and shows FRP lock ON and OEM lock ON. I am sure this has something to do with it but it's outside of my knowledge range. I've attached a picture of the recovery screen. Any ideas would be appreciated.
I'm new to these threads so I can't work out how to attach a .jpg of the recovery faults. Any advice would be appreciated
Same issue here
I know this is an old thread, but did you find a solution?
On an unlocked J6, after flashing the stock rom, although I can open recovery, I get the same message. The options I tried (both reboot options, both wipe options, power off) work. I went ahead and installed twrp through odin, which passed, but when I boot into recovery, it boots into samsung recovery (with the same message) and not twrp.
I'm guessing the twrp problem is related to the error message.

Moto E4 xt1762 stuck on m logo

Hi, so a friend give me this phone with this problem and I'm trying to solve it. The fastboot menu works, bootloader is locked, and the options there are start, factory mode, meta mode and recovery mode. The only one that works is recovery mode, the other 3 get stuck in the m logo and at the bottom says powered by android (no animation or anything). Recovery mode says no command, but by pressing power+vol. up you can acces it. However, when i do that, it only shows at the bottom "supported api: 3". No options or menu, so i don't know what to do. It has usb debugging off and oem locked, and when connected to the pc, fastboot devices and adb devices commands don't recognised the phone.
Any suggestions?
v5tge said:
Hi, .
Any suggestions?
Click to expand...
Click to collapse
Option A=Try installing dm disabling dm verity via fast book it that doesn't work restore boot.img and then try again.
Option B: (Data is lost but success is assured)
You can try downloading with
https://mega.nz/folder/LKgzUYwI#BGxxvjc5K3UaLOsCUqjwRg
Instructions here:https://forum.xda-developers.com/moto-e4/development/stock-stock-rom-moto-e4-mediatek-sku-t3804870

H918 "Your device is corrupt" attempting to re-lock

I've been attempting to re-load factory firmware on this device, but when I hold volume-up and plug in a USB cable, it would flash the "download" screen for a part of a second then jump to the "Cannot verify the firmware" screen, then go straight to twrp rather than download mode.
So, I rebooted to fastboot mode, and did a "fastboot flashing lock" hoping that it would stop trying to verify the firmware and just get straight into download mode for LGUP. This seems to be where my biggest mistake was.
So, now, I get a quick flash of download mode, then straight into "Your device is corrupt." How can I prevent the "Your device is corrupt" and get back to the "Download" mode where LGUP will actually see it and work with it?
Thanks!
Got into fastboot. Unfortunately, I haven't checked "Enable OEM Unlock" in Developer options, and it won't boot to anything anymore.

Categories

Resources