Hi, I'm trying to boot into OS after flashing by odin but I can't.
I dont have access to Android Recovery (power button + volume up). The only think I can do is to boot in Downloading Mode. Even if I flash other system I dont have access to Android Recovery, either TWRP.
Can someone please help me?
If I let it boot normally I get NO COMMAND SCREEN, and if I press Power + Volume Up I get a screen with the following script:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
.
.
_symlink] fail to mount /system as rw
Related
Hi all,
I recently tried to use the app 'Flashify' to upgrade my installed version of Clockwork Mod to the latest version.
Now whenever I try to boot my phone, it goes straight into recovery mode in which my phone freezes with the 'Recovery Booting...' message displayed on-screen.
I was able to put the phone into download mode and have been able to boot back into the Android OS by using Heimdall on my Mac (I don't have access to a Windows machine) and flashing the stock boot.img to the BOOT partition.
Even when I try to boot into the recovery mode (By pressing the HOME + Volume Up + Power buttons] it still freezes.
I would like to try out custom roms however, so how can I get the recovery function on my phone working again?
If you know how to use Heimdall, then flash again the recovery with it.
Use this command:
heimdall flash --recovery recovery.img --no-reboot
I never like those apps like Flashify, because when you do it manually, you know what you are doing.
Awesome! Thank you!
I am getting a couple of error messages though 'E: failed to mount /efs (Invalid arguments').
well after almost 2 days trying to find a solution to preload a system on my d801 i have managed to enter this recovery
android system recovery <3e>
LRX22G
volume up/down to move highlight:
enter button to select
reboot system now
apply update from adb
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recover logs
apply update from sdcard
[Recovery.cpp [main()] ########### factory reset s art ###########, Thu Jan 1 00:00:58 1970
i already tried to sideload with adb but the procedure stops at 48% and then i got an error on the recovery screen
failed to verify whole file signature
signature verification failed
installation aborted
device manager detects my phone as androidnet sooner single ADB interface
any help is very welcome, thanks a lot and regards!
PS: i have bootloop (an android man with his belly/chest open and an exclamation red triangle) also i don't have download mode (every time i plug the device holding volume up to my pc i got stuck on fastboot mode started)
Got a N7 2012 runing 5.1 - finally got fed up with it being so slow as almost unuseable so decided to install CM12 ... and am stuck in a boot loop.
I followed the instructions I found (I cant post the link) so I've listed them below:
Deploy ROM image
adb devices
adb push YOURROMZIP.zip /sdcard/
adb reboot bootloader
fastboot devices
fastboot oem unlock
cd Download
#or whenever you have downloaded files
fastboot flash recovery your_recovery_image.img
Choose Recovery
Now use your volume buttons to change selected item from the Menu and pick "Recovery mode"*and select it with Power button.
Right now ClockworkMod recovery should start!
Now with the same buttons navigate in recovery and select:
1. backup and restore
2. wipe data/factory reset
3. install zip from sdcard
4. choose zip from sdcard (you should find it in folder named "0", not in the root of sdcard!)
5. reboot system now
Cyanogen Mod should be installed!
did a full wipe at fastboot oem unlock .. then realised i'd have to re-push the ROM as I don't have an sdcard ... so I did that.
Managed to flash TWERP onto it (rather than CW) and got it to boot into Recovery Mode but ... the Recovery Mode and Restart Bootloader are in RED and don't do anything when I tap them.
When I try to power off and back on it gets stuck in the boot loop...
Google screen show with a padlock at the bottom, goes away and then shows up again
Teamwin logo shows up
says 'Running OpenRecovery script'
things then happen too quicly for me to track but it seems there are a list of red error messages like:
E: unable to mount data and could not find crypt footer
I'm running Ubuntu 14.04 and the device doesnt appear i the list when I type
adb devices
fastboot devices
Can anyone tell me what to do to get CM12 on the m/c and working???
btw, managed to break out of the bootloop but it will just start again when turned off and on.
Thanks in advance.
From what you said, you're not in recovery mode. You're in bootloader mode.
In bootloader mode device doesn't support touchscreen, you need to use volume up/down and power to select option.
To get out of bootloop and go to recovery:
1. Power down your device (hold power for few seconds)
2. Boot into recovery mode (hold Volume Down + Power)
3. Navigate to recovery (Using Vol up/down and selecting option by pressing power button)
[solved] Bricked? A3 2017, no download accesible, "failed to set up dirty target"
Hi!
I just bricked my A3 2017. After flashing a stockrom with ODIN no boot is possible any more. I cannot enter the download mode because I just get the blue screen with the android saying "no command".
Pressing Power + Vol-up + home leads to a message
"E: Failed setting up dirty target [hwr-symlink] failed to mount /system as rw"
Maybe the stockrom file was corrupt. Is there anything I can do to get into download mode again or to flash without odin?
I am coming from Lineage 16, so maybe the boot looder of stock 8 isn't running if you have installed Android 9 previously.
Any hints?
After many tries with vol-down and home I managed to get to the download screen sometimes. After that I tried to flash AP files from stockrom again but never succeeded. I don't know why I get past the blue "no command" screen in maybe 1 of 20 attempts with the same key combination (vol-down and home) only.
Today I tried to flash a recovery from here
https://desktop.firmware.mobi/device:141/firmware:15535
This was successful and I managed to boot into recovery. In recovery mode I booted into bootloader and the phone booted to normal stockrom I flashed at the beginning (before the nightmare begun).
Still, I don't know what happened but it seems to be some problem of rw-rights...
Anyway... Problem solved!
I attempted to flash stock SM-G935V CSC VZW obtained via Frija using ODIN 3.14.4. Slelected HOME CSC to try and preserve data. I know the phone memory was approaching capacity prior to black screen/flashing blue LED. The flash "Passed" and immediately after all I got was Recovery dowloading...... and then hung. Then after several attempts to get into recovery I watched Loading system file up to about 32% then erasing. It then progressed from the Samsung to the Verizon logo and stopped. Now, when I attempt to enter recovery All I get is the blue Recovery downloading.... Relative novice here. Can you direct me to a guide or offer direction please? Intuitively, it seems maybe the bootloader is corrupt - but I don't know enough to understand the sequence. Prior to the Flash, I was able to enter recovery and wipe cache one time but that did not get me past being stuck on the Samsung logo screen. I did transcribe the information below the recovery and the first item was #fail to open recovery_cause (no such file or directory) then #reboot recovery cause is [unknown] File Support OTA Supported API:3 #Manual mode v1.0.0 #removed AttIqi_ATT' (No such file or directory). I would like to get recovery with files intact if possible but will wipe if needed.