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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
[Q&A] [k3gxx] CWM based recovery 6.0.4.7 for Samsung Galaxy S5 SM-G900H ( Exynos 3G)
Q&A for [k3gxx] CWM based recovery 6.0.4.7 for Samsung Galaxy S5 SM-G900H ( Exynos 3G)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [k3gxx] CWM based recovery 6.0.4.7 for Samsung Galaxy S5 SM-G900H ( Exynos 3G). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
A big thanks.
Thank you bro for the effort. Can't really relate to the amount of effort you put in for free.
scumpicule said:
ClockworkMod Recovery 6.0.4.7 for Samsung Galaxy S5 SM-G900H 3G (Exynos)
Warning: This operation involves risk. I or XDA can not be held responsible for any problems encountered.
Credits & Thanks go to Chenglu & Theandroidsoul
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Note: Install this Recovery will get your Knox counter 0x1
Requirements
Have installed the drivers / drivers for your phone - >> HERE
Have downloaded and unzipped the file - >> Odin307.zip
Download file - >> g900h-cwm-recovery-6.0.4.7.tar - COPY Miror
Make sure you have a charged battery (75% minimum)
Installation procedure:
Turn off your phone.
Simultaneously press the buttons: Volume Down + Home + Power. Then press again the power button to start the Download mode.
On your computer, launch Odin in administrator mode.
Connect your phone to your computer via the USB cable. In ODIN, box ID: COM turns blue proof that your phone is correctly detected.
Click on PDA and select the "g900h-cwm-recovery-6.0.4.7.tar" file you downloaded on your computer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check the boxes that only Auto Reboot and F. Reset Time are checked.
Start the installation of ClockworkMod Recovery by clicking the Start button and wait a few moments.
At the end of the installation, you can disconnect your phone from your computer.
Procedures to enter the recovery of S5:
With physical keys :
Phone turned off, press the following buttons simultaneously until you see the Samsung logo: Vol Up + Home + Power
Installing the Quick Boot Reboot application :
On the Google Play Store - >> Link to the application (ROOT Required)
Open the application, grant root privileges, then click "recovery"!
Performing a ADB command :
Install first the drivers, then download / uncompress the file ADB files.zip
Make sure you have USB debugging enabled
Connect your phone via USB, and confirm the message pop-up window that appears
Then from the folder where you previously extracted the contents of ADB.files.zip file, double click "Boot into Recovery Mode.bat"
This file performs the following ADB command:
Code:
adb reboot recovery
Your feedback is welcome
Click to expand...
Click to collapse
failed to mount
cwm failed to mount system,data,cache...etc
am i doin anything wrong ?
model is G900H
---------- Post added at 06:56 PM ---------- Previous post was at 06:51 PM ----------
Just restarted recovery from advanced menu and everything is working now thanks for this recovery
failes to mount
it says cant mount /cache/recovry/command,cant mount /cache/recovery/log...etc what shud i do ?
there is a lot of problem for me to install custom recovery for my Samsung galaxy s5 SMG900H working on lollipop 5.0
some body please help me. .
Sent from my Venue7 3740 LTE using XDA Free mobile app
Hello, I have a Tmobile Samsung S5 and I am able to get into Download Mode and I have used Odin v3.09 to try to and flash Odin Flashable Full Stock from the oldest version to the latest and everytime it just boots to the Samsung S5 logo screen with the words Recovery Booting on the top upper left of the phone. The phone is also unable to get into Recovery. I tried flashing other recovers such as TWRP via Odin but I get an error stating "recovery is not seandroid enforcing"
I am beating my head up against the wall here trying to get it to boot up.
Title was meant to say CAN'T
shanghei said:
Hello, I have a Tmobile Samsung S5 and I am able to get into Download Mode and I have used Odin v3.09 to try to and flash Odin Flashable Full Stock from the oldest version to the latest and everytime it just boots to the Samsung S5 logo screen with the words Recovery Booting on the top upper left of the phone. The phone is also unable to get into Recovery. I tried flashing other recovers such as TWRP via Odin but I get an error stating "recovery is not seandroid enforcing"
I am beating my head up against the wall here trying to get it to boot up.
Title was meant to say CAN'T
Click to expand...
Click to collapse
You might not be able to get into recovery mode but when you're soft bricked you can get into download mode.
Press the key combination to get into Download Mode and keep holding them until your phone gets to the Download Mode screen.
You'll then have to redo it and if it still doesn't work then you're probably flashing a bad firmware.
Your phone may reboot a few times during this process, as it's happened to me before and I just ended up holding until about 3 or 4 reboots.
I did flash in odin in download mode using the correct firmware. I also used kies to no avail.
shanghei said:
I did flash in odin in download mode using the correct firmware. I also used kies to no avail.
Click to expand...
Click to collapse
Make sure it's definitely the right firmware, and try using a different version of Odin perhaps?
CainK said:
Make sure it's definitely the right firmware, and try using a different version of Odin perhaps?
Click to expand...
Click to collapse
I used Odin Version 3.07 and 3.09 to flash the following firmware files, odin finishes with a green PASS!
It is a Tmobile S5 sm-g900t
G900TUVU1CNK2_G900TTMB1CNK2_G900TUVU1CNK2_HOME.tar.md5
Everytime its done flashing it goes to a screen that says on the top Left in blue text "recovery rebooting......." and it just sits there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Samsung sm-g900m nao entra em modo recovery .
I have the same problem.
my screen this loop. when I try the recovery appears the same message. When I try the way downloads is stuck in the robot android more not connect the USB
Edited
______________________________________________________
Tried with odin
cant find any IMG or any ZIP after selecting AP in browsing
_____________________________________________________
hello
mine is s7 edge model (SM-G935FD) indian variant
with latest security patch i,e (1 dec 2017)
is it the same procedure ?
kinda scared to try old might end up bricking up my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
beinglazy said:
Edited
______________________________________________________
Tried with odin
cant find any IMG or any ZIP after selecting AP in browsing
_____________________________________________________
hello
mine is s7 edge model (SM-G935FD) indian variant
with latest security patch i,e (1 dec 2017)
is it the same procedure ?
kinda scared to try old might end up bricking up my phone View attachment 4386430
Click to expand...
Click to collapse
With AP you need to flash .tar or .tar.md5 files
Same procedure to root as long as your root method hasn't been noted as being outdated
turbolukex5 said:
With AP you need to flash .tar or .tar.md5 files
Same procedure to root as long as your root method hasn't been noted as being outdated
Click to expand...
Click to collapse
i tried this method didnt work
https://www.youtube.com/watchv=GRRX...5rshb2ieiej5kbhq4l5pw03c010c.1515693111002897
twrp = https://dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
odin says "<OSM> All threads completed. (succeed 1 / failed 0)"
and after auto reboot in lock screen it asked me to reset the device but i didnt
but when it try to go in recovery by prssing vol up+ home + power
it goes to something saying "Installing update" and after few seconds says " no command" and it goes to stock recovery
beinglazy said:
i tried this method didnt work
https://www.youtube.com/watchv=GRRX...5rshb2ieiej5kbhq4l5pw03c010c.1515693111002897
twrp = https://dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
odin says "<OSM> All threads completed. (succeed 1 / failed 0)"
and after auto reboot in lock screen it asked me to reset the device but i didnt
but when it try to go in recovery by prssing vol up+ home + power
it goes to something saying "Installing update" and after few seconds says " no command" and it goes to stock recovery
Click to expand...
Click to collapse
Follow tutorial in this thread instead
https://www.google.co.uk/amp/s/foru...-official-twrp-hero2lte-3-0-0-0-t3334084/amp/
I'm having the same problem, i've tried all methods I can find including the ones suggested on here but not one will work
Bholwell said:
I'm having the same problem, i've tried all methods I can find including the ones suggested on here but not one will work
Click to expand...
Click to collapse
hey this method worked for me
https://forum.xda-developers.com/showpost.php?p=75169863&postcount=2139
I bought this device from a fleamarket and have the following issues :
It was (still is) FRP locked (Android 5.1.1) so I flashed the Combination ROM (COMBINATION_FA51_G928FXXU4ARA1.zip ), realizing, adb commands from "FRP_Techeligible.bat" wont work:
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
The Combination ROM worked just fine.
My fault, the combination ROM was for 7.x.x.
But why doesnt it work anymore ? Bootloader incompatibilities ?
I started ODIN.
So I went for the 7.0 Stock ROM (Vodafone), ending up with the "modem.bin FAIL!" in Odin.
Also I have no idea if its vodafone branded.
I renamed "hidden.img" to "hidden.img.tar" and flashed it seperately. But it did not help.
It goes to recovery and says "No Support SINGLE-SKU", Supported API:3, dm-veritfy error... failed code: 0x02"
Flashing the Combination ROM failed afterwards.
In Recovery I do now see Android 7.0 (G928FXXS5CRH1), but I get the 0x02 Verity Error on top of it.
Wiping doesnt help anymore it seems.
It will only boot into recovery and I can still enter download mode.
So I wanted to try Android 6.0.1 ROM...but it fails after "cache.img."
SYSTEM REV. CHECK FAIL- DEVICE:1, BINARY:0
So I wanted to try Android 7.0.0 ROM again...but it fails at once.
SYSTEM REV. CHECK FAIL- DEVICE:5, BINARY:4
After rebooting (device:5 binary4) I can flash the 7.0.0 ROM again, until it comes to the "modem.bin FAIL! message again...
What have I done ? :crying:
I googled for hours today and read into so many "ideas" and "solutions"...but none of them helped.
Wish I would have stayed in the Combination ROM.:silly:
Knox is still 0x0
Is there any chance to revive this device ?
Like, flash TWRP...or a custom ROM...but how, if I can only get Download Mode and Recovery and get a:
Custom Binary(RECOVERY) Blocked By FRP Lock
Kies and "Smart Switch" Software wont recognize the device.
adb wont enlist it. (anymore). Worked with combination ROM.
Odin recognizes it on com port, starts flashing, then fails.
also read using ODIN with mixed 6.x.x and 7.x.x files coudl get me "back" the old bootloader...but I gave up now and dont want to waste another day, if its useless.
I did now flash the "4 part firmware" (AP, BL, CP, CSC) G928FXXS5CRH1 (unbranded).
The download I did via the tool "samfirm" use chk32 and decrypt on downloading !
"SM-G928F_1_20180828170540_5avji4munw_fac"
ODIN worked and the phone is back booting to "An blabla attempt..." aka. FRP lock.
Booting into Recovery it now says :
"Installing system" followed by "No command"
then shows :
7.0 (G928FXXS5CRH1)
Successfully verify for dmverity hash tree
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-adb still does not enlist it as device
-A reboot from "Download Mode" ends up in the Recovery Mode once
On the next reboot its back to "normal"
-Kies says please use SmartSwitch...and SmartSwitch says "USB file transfer not allowed"
So I guess its time for the 7.x.x combination ROM again...jesus...it fails in ODIN and ends up in
"E:failed to mount /cache...recovery"...blaaahhh
on boot....
Flashing "7.0 (G928FXXS5CRH1)" in 4 parts again. So, deadend ?
As I could NOT enter Recovery anymore, I couldnt wipe cache and do a factory reset....
But no, I cant flash the COMBINATION ROM anymore..........................ODIN keeps failing.
Ok, I decied to try to downgrade from 7.0 to 6.0.1, so I can use the FRP bypass again.
But where would I find a debranded 6.01 for SM-G928F in 4 parts (BL, AP, CP, CSC)
I found a ROM, takes ages to download...good night...more tomorrow...
Update :
After much googling, stumbling across tons of trojan tools by indian people, many videos that always wants you to buy a "Box" from amazon...I tried the non adviced downgrading to Android 6.0.1.
It only worked with a 4 part flash file + ODIN (I didnt even use the PIT file, as it was supposed to be) and Im now at :
6.0.1/MMB29K.G928FXXXS3BQA7 (it flashes just fine with and without the PIT file)
No verity error, no Knox triggered.
The next step was to flash the modem of 7.0 (AP), to be able to get connected to the network again.
It worked as well.
The phone still had FRP lock, so I used the "call method" to get into a SMS, send a link, open link, surf to google account manager 6 and frp.apk, done.
Hello All,
Will try to put all details to be able to get the right advise.
Recently was trying to root my N935s unlocked phone. The "Developer options → OEM unlocking" was enabled and USB bugging was enabled. However the process failed and threw me in an unrecoverable phone state.
Seeking help and advice to get back a working phone.
=========================================
Supporting information screenshots
Screenshots of the phone info "Pre" rooting attempt as is in stock condition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current State of Download Mode screens (after the rooting failure and boot loop has occurred)
==============================================================
Chronology of events (starting from an untampered stock phone)
1. Installed TWRP via flashing "AP" only using ODIN and was able to boot in TWRP recovery.
2. Made a complete backup of all partitions (including EFS) on external microSD card. Have it available - however somehow it is not helping.
3. Installed Magisk Apk 25.2 on the phone. Intention was to patch stock boot.img file and re-flash it to gain root by using Magisk,
4. Downloaded the below firmware files using Frija, by inputting the phone model N935S and CSC code as "SKC". Chose the latest file proposed by Frija in Auto mode.
5. Extracted boot.img from the stock AP file (from above screenshot) and transferred to phone for patching. Patched only the boot.img file.
6. After patching flashed the patched boot only (renamed and converted to TAR using 7zip) as "boot.tar" file in AP using ODIN - flashed it along with CP/BL/CSC files as from the above image.
a. This was the mistake point as the instructions were to transfer the whole AP file to the phone - get it patched inside the phone and then flash the whole AP file along with others. Somehow I totally missed it.7. Restarted the phone and the phone went in a bootloop or a stuck state of being only on the black Samsung Logo screen.
8. The recovery and download mode is available by using the button combinations.
====================
My attempts to restore
1. I first booted in TWRP recovery and restored from the stock backup I had taken - hoping that it would fix everything back to normal. The restoration was completed successfully - however there is no success to go beyond logo screen.
2. Went into download mode - using ODIN, flashed all the files from above screenshot (point no.4) - the flashing is completed successfully however there problem remains.
Not sure what can I do now to be able to get back a working phone.
Can someone please share a solution to a similar situation where the Magisk installation has rendered a phone bricked.
Thanks.
Was able to find excellent online phone restoration and recovery expert help and guidance - hence I was able to recover the phone.
It is now downgraded to Android 8, have lost the original serial number in he process - which is unrecoverable, however still got a working phone.
Thread closed.