Hi All
I have samsung A5 2017. When i start my phone it shows no command and it continues to restart after 1 minute.
When i try to open recovery mode i get error "fail to open recovery_cause(No such file or directory)". I have also tried combination of key power and volume up but not getting recovery mode. I think it has been deleted or something else. I am also unable to load firmware.
I also tried to install twrp with odin 3.13 but get error unable to install frp locked.
Please tell me solution how can i get back recovery mode so that i can install firmware.
Please help me for this.
Hey there,
I have a similar issue and I can see your post dates back to 2020. Have you ever found a way?
I'm very curious about solving the issue on mine (I can't reboot at all, can't even access the reboot after getting the "no command" message. If you have any clue on how you accessed reboot mode and can be kind enough to share, this would be really appreciated )
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.
Related
So I'm trying to fix this phone for my friend and this was the information he gave me:
-tried to install a beta custom rom (forgot the name sorry)
-installed it but went haywire according to him
-he said he was able to get it back to stock
-tried rooting and installing another rom but thats where he messed up
The phone now only boots into recovery mode without pressing any buttons. If I pull the battery, it also just boots into recovery mode. I can't seem to get into download mode either.
Now heres the real problem. I am able to scroll up/down but I cannot select any of the options with the power button. So what can I do about this?
It says android system recovery <3e> and has some error messages related to mounting sd cards.
Hello.
How it happened
I rooted my HTC One S, then flashed CyanogenMod on it. Used it for a few months, very happy with it. Then I tried to update - automatically, not manually (that was mistake number 1). The phone was then stuck in a bootloop into recovery. (Off>Recovery>Off>Recovery). I didnt know what to do, so I pressed 'Reset phone', or something like that. Since then, the problem has gotten much worse. Now there's a different bootloop: Off>HTC opening screen. That's it. Im desperately trying to access recovery mode, to flash a new ROM to fix the situation.
What did I try
1. Power + VolumeDown does nothing.
2. Installed the HTC One S toolkit. When pressing 'boot into recovery', it says 'device not found'.
3. Tried to boot into recovery from ABD tools, but it says device not found. I tried putting screenshots here, but XDA forum new user limitation doesnt let me. Anyway, if you add this to the imgur url, youll see the screenshots (sorry about this inconvenienace):
/SblBm3M
/6HEvZDk
TL;DR
Phone is stuck in a bootloop. Cant access recovery. Is there any way to fix this situation?
Thank you very much in advance for your time to help me out.
Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls
Hi all!
Im in a bit of an unknown scary situation for me
S6 edge, updated to nougat, rooted with the twrp Magisk method. All went fine.
Went to update the SUperSU binary from the app, and selected the twrp method.
Phone went into recovery, and started the flash. Now its been stuck for ages on "skipping MD5 check, no MD5 file found"
Buttons dont do anything (power button just shuts down the screen, and combination buttons takes screenshots), the lock screen and swype work, and the progress bar is blue and moving.....
What do I do? No idea how to restart, or exit recovery...
All the threads I checked, talk about failed rom installs, and re flashing the rom or the recovery, but I cant even get out of recovery to restart the phone or go into download mode
Any help will be greatly appreciated!
Update!
After the panic of being stuck without a phone, and waiting for the phone to run out of battery, I kept googling and found out that I can restart twrp by holding Power and Vol Down for about 10 seconds.
It rebooted back into twrp menu, I restarted into system, and all seems ok!
From what I have understood so far, magisk does not need SuperSU, is that correct?
PHEW!
Leaving this here, in case it helps someone in the future!
Hi, my S3 got an encryption issue today, it tells me to reset the phone, so I clicked it and the phone rebooted to TWRP recovery. Everything seemed to be ok, but I got the mount data issue, after that the phone just reboots and I get the encryption unsuccessful message again. There wouldn't be a problem if the volume up button would work, I could normally access TWRP and try to fix it there. Unfortunately it doesn't work, so I can't boot into recovery mode, and to use adb I guess I'd need to to access the phone, what I'm not able to do due to the encryption failure.
Anybody got a solution how I can boot into recovery mode, or fix the issue on other way?
Thanks in advance.