I have a Samsung Galaxy Core 2 (SM-G355M). I received this device from a person close to the family to try to solve a Loop problem in the Samsung logo. I tried to install 5 different Roms with the Odin3 3.10.6 program (Recommended for Android KitKat 4.4.2 systems), but I was unsuccessful after the device was restarted by Odin.
The device's recovery screen practically does not exist. There are no options to access when I enter recovery mode (by pressing the Volume up + Power + Home keys). I tried to install a custom recovery (TWRP and CWM), but I don't have access to them after Odin restarts the device.
As I mentioned before, the device's recovery screen practically does not exist because there are no options on the Hard Reset screen, but it displays a message when I press the volume button up as soon as the Android logo appears. https://ibb.co/FmBtv10 (Error Image). The error '' E: failed to mount / efs (invalid argument) '' appears.
I cannot access the device and retrieve it via ADB using commands because the USB debugging mode cannot be accessed (The phone does not start, so I cannot activate it). I am not aware of the history of this device, I just know that it is accepting any ROM or recovery feature through Odin and presents the error mentioned earlier on the Recovery screen.
I made another topic here in that same FORUM presenting my problem. I followed some steps taken by a FORUM member, but none of the procedures worked. There I explain a little better the procedures that I did and that did not work.
Samsung Galaxy Core 2 (SM-G355M) - Recovery mode does not work.
Helo! I'm new here at FORUM. In a desperate attempt I decided to create an account here and try to solve my problem with a Samsung device. It all started when I received a Samsung Galaxy Core 2 device to fix. It is stuck on the Samsung screen...
forum.xda-developers.com
I researched a little about this error found in recovery mode. Some solutions involved downloading the EFS file. IMG according to the device model and install via Odin. I found only for the model SM-G355H. During the process, Odin had an error loading the files, so I think it didn't work.
Problem summary:
1 - Device does not accept any of the official ROMS (After the cell phone is restarted by Odin it goes back to the Samsung screen).
2 - Cellphone showing error in recovery mode '' E: failed to mount / efs (invalid argument) ''
Some notes: I do not have access to the system using ABD because the debug mode cannot be activated (This ends up limiting things a lot). Options on the recovery screen do not appear and cannot be accessed (Only displays the error message right after pressing the volume button). All basic procedures were done (Download the most updated version of Samsung Drivers - 100% battery - Good quality cable - Odin 3.10.6 to install KitKat Android systems).
All possible solutions are welcome.
Related
Hey guys
my phone asus zenfone 5 T001 WW
it was bricked after i tried to install zenmotion (stuck in usb logo)
i tried to search how to resolve this problem
what i was done is tried to flash firmware
i tried 78 firmware and failed stuck on 54%
i tried 87 firmware and still same stuck on 54%
i tried to downgrade to 5.2.2.2 and failed because cant downgrade from android 5.0 bla bla bla i dont know what the meaning of the report
and i tried to write in command promt fastboot boot.img (i forgot this file from what firmware)
and now i can boot my phone BUT i cant go to bootloader/fastboot mode (by pressing power+volume up) when i press that button, i go to home screen
and every reboot my phone always go to recovery mode (picture android down and there "!"
so please help me to resolve this problem
im sory for my bad english
thanks a lot
and every i restart the phone was go to recovery mode
when i choose "to bootloader menu" my phone go to homesceen not to bootloader
i tried to put firmware 5.2.2.2.2 in internal memory
i press update
and erorr for the result :
finding update package...
E:unknown volume for path [@cache/recovery/block.map]
E:can't mount @/cache/recovery/block.map
E:install of @@/cache/recovery/block.map failed with status 2
Instalation aborted
E: cant open /tmp/update-script.log
E:instalation failed with status 2
E:can't open /tmp/update-script.log
Last try
i can go to homescreen, i go to setting-about and i found my firmware is T00F-WW-3.24.40.87
i tried to insert firmware T00F-WW-3.24.40.87 in internal memory (i was rename it before, so my phone was detected there was an update)
the phone was restart to upgrade, and i found error like this
http://i1092.photobucket.com/albums/i415/saliskjaer/P_20160324_211729_zps0nuaftyr.jpg
it show thats android system recovery is ASUS_T00F-WW-user-2.21.40.30-20141208_43
and when i tried with other firmware, there were still appear like that
i was tried firmware T00F-WW-3.24.40.78 and T00F-WW-5.2.2.2
when i press restart
i found like this
http://i1092.photobucket.com/albums/i415/saliskjaer/P_20160324_211811_zpsiekdfuqy.jpg
and when i press power vol up
the screen was like this
http://i1092.photobucket.com/albums/i415/saliskjaer/P_20160324_211829_zpsslqzunm6.jpg
it show thats android system recovery is LRX21V.ASUS_T00F-WW-user-3.24.40.78_201
this make me confused
when i choose reboot to bootloader, the HH not go to bootloader but go to homescreen
please anyone who can resolve this problem
thanks before
I have and Idol 3 4.7 6039A (Mexico) and was rooted using kingroot, Unrooted and installed and OTA directly from phone and
the on recovery this error popped up:
Installation aborted.
E?unknown volume for path [@/cache/recovery/block.map]
E?erasing upade package errno=2
E?unknown volume for path [@/cache/recovery/block.map]
The phone now worn enter to android OS, I already did a Wipe/Factory reset & Wipe cache but it will just continue to boot into recovery, When I put in into download mode and use mobile upgrade from alcatel it will try to install a driver and fail thus making the mobile upgrade program say "No avaible device detected".
What do I do? Is my phone gone for good? Help please!
Turns out I lacked the ADB drivers, Close and delete thread please.
I had stock rom installed when I was facing "cant connect to camera issue", which itself was a hardware issue-solved by changing the camera in service center. Now, when I wanted to update my phone to cm13 or lineage or even to install supersu and twrp, I'm unable to do so with error, "signature verification failed". My device is not rooted, getting detected in adb, fastboot mode. Tried installing cwm/twrp recovery in fastboot mode but my phone restarts again with stock recovery not with twrp or cwm. A thread said I should restart phone from fastboot directly into recovery..when I tried the same with vol up+ vol down + power button, yu followed by a blank screen appears and nothing happens. I searched various posts from xda, but cant seem to find a solution. Hope one of you guys could help me out. Thanks.
I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.
When you are in recovery, is the tab detected via adb from pc?
bukaida said:
I was trying a new ROM after installing mobile odin (pro) and superSu. However after failed installation the tab is restarting in recovery mode only ( screen shot attached). It is neither detected by odin nor can I install any apk as it is not booting further. I have wiped all data and caches and also have the recovery image (cwm and one supplied by mobile odin) but both are showing signature verification failed due to stock <3e>. So if somehow I can bypass the signature verification , I can load the backup. In short--
1. Tab not detected in PC ( via ODIN) , which was perfectly detected earlier. So no method via PC possible.
2. Tab not going beyond recovery mode, so no APK installation is possible.
3. It can read from SD card in recovery mode , but every image ( I know they are good, as used them earlier) is showing " Signature verification failed" and aborting.
4. I have a working CWM image but cannot install it due to reason 3 ( probably <3e> is the culprit).
I have searched the forum as far as I could but found all solutions are either PC based or APK based.
Click to expand...
Click to collapse
Signature verification fails because you are on stock recovery. Also have you tried booting in to download mode then plugging the USB cable to your tablet, then pressing volume up to start the download mode, then plugging the other end to your PC while odin is running? It should get detected
Power+ Vol up and Power + Vol down both are going to recovery mode. Plus getting an error 'logo_espresso7.jpg' draw failed at initial screen. Is there any <3e> compatable recovery without signature verification failed that can be run from sd card directly?
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
The Tab is not detected in ADB server either.
bukaida said:
Ps: This happened when I tried to install "crdroid-5.1.1-20151103-p3110" via mobile ODIN pro.
Click to expand...
Click to collapse
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.
john99ap said:
The rom was meant to be installed with twrp or other custom recovery and not via mobile odin.
Click to expand...
Click to collapse
Yeah, the fault is mine, lack of knowledge. But what now? Can I recover my Tab ?
please help.
[Solved Problem]
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.
bukaida said:
The problem is solved. I finally could figure out that the culprit was the external volume down key ( not letting me go to download mode). So I opened the back cover as the last option and press the soft points corresponding to volume down and power together with two tooth-peaks. And voila , it issued the warning screen, and pressed up and it went to download mode. Connected with odin, flashed and load cwm recovery . Now that <3e> kernel is also gone.
Ps. It was weird about the Vol key behavior as it was working fine in both side in recovery mode during selection.
Click to expand...
Click to collapse
if you want to install the latest roms, you should update to the latest common twrp from android-andi http://andi34.github.io/recoveries_tab2.html
cwm recovery is outdated and causing issues with the latest roms
Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?
bukaida said:
Is twrp safe to run from mobile odin? Will it automatically overwrite installed cwm?
Click to expand...
Click to collapse
install twrp as zip with your current cwm. its the easiest way. twrp will replace cwm, yes.
I'm on a G900W8 with the latest software update and I just tried to install the latest TWRP through Odin using download mode (vol up, home and power) and while it seemed like it worked it didn't actually and now I cannot get into download mode whatsoever. It just says "installing system update" which fails after a few seconds and sends me to "no command" screen.
If I hit vol up and power to get into the next menu it says
Code:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API:3
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
E:Failed to clear BCB message: failed to find /misc partition
The phone boots and I can use adb commands to "apply update from ADB" in the recovery menu but I can't figure out how I can use this to fix anything. I have tried factory reset which worked but it did not fix my issue I still cannot access download mode or figure out any way to install TWRP or even get my regular recovery working again..
Does Odin still detect it when it reaches the no command screen? I had the same thing happen to a Samsung tablet but Odin still detected it after the 'installing system update' message and I was able to do a stock firmware flash.
Beanvee7 said:
Does Odin still detect it when it reaches the no command screen? I had the same thing happen to a Samsung tablet but Odin still detected it after the 'installing system update' message and I was able to do a stock firmware flash.
Click to expand...
Click to collapse
No it doesn't unfortunately my PC recognizes it but it says the device has malfunctioned and is not recognized. If I boot it up Odin will recognize it fine but I cannot install anything that way since the actual system is running at that point.
Try to find and flash popper combination rom
maybe this site help https://www.mobileheadlines.net/samsung-galaxy-s7-combination-rom/
I have same problem like you
I flash combination rom
lets its boot up
go do download mode again
and flash proper firmware
jaqjacek said:
Try to find and flash popper combination rom
maybe this site help https://www.mobileheadlines.net/samsung-galaxy-s7-combination-rom/
I have same problem like you
I flash combination rom
lets its boot up
go do download mode again
and flash proper firmware
Click to expand...
Click to collapse
OK but how do you flash that without being able to use Odin in download mode?
On my S7 to go to download mode is combination Vol Down + home + power.
Vol up is for recovery
jaqjacek said:
On my S7 to go to download mode is combination Vol Down + home + power.
Vol up is for recovery
Click to expand...
Click to collapse
Oh man I'm an idiot lol. I'll try this tonight... Thanks
Similar problm
Cordtus said:
I'm on a G900W8 with the latest software update and I just tried to install the latest TWRP through Odin using download mode (vol up, home and power) and while it seemed like it worked it didn't actually and now I cannot get into download mode whatsoever. It just says "installing system update" which fails after a few seconds and sends me to "no command" screen.
If I hit vol up and power to get into the next menu it says
Code:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
Block-Based OTA
Supported API:3
# MANUAL MODE v1.0.0#
Similar problem but upto Block-based OTA showing ..
Click to expand...
Click to collapse
Similar problem but upto Block-based OTA showing i flashed stock formware after factory reset still showing above problem my device if galaxy j4 sm-j400f
And also when i boot it stuck on samsung logo for long time..