Database Users

Can get S5 SM-G900T out of soft brick mode.

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

J5 - SM-J500M/DS - Custom binary still blocked by FRP after flash (Odin, Z3X)

Hello everyone. :good:
I will try to be brief...
I have a J5 model SM-J500M/DS with Custom binary blocked by FRP (lock: on)
The problem is:
After flash firmware using both Odin/Z3X Pro, the message screen "Custom binary blocked by FRP" still there.
1 - I tried all versions of stock roms from: sammobile (android 5.1, 6.0), SamFirm (last firmware).
2 - I tried separated firmware repair files (BL, CP, CSC, etc..)
3 - KIES and Smart Switch same alert that SM-J500M does not have support for initialization emergency:
Is there another way to turn FRP off? :crying:
Take a look the screens below:
Thank you :good:
{
"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"
}
This is the log screen on both Odin and Z3X:
Using repair firmware with separated files
Using stock rom from Sammobile
Z3X with individual files
Z3X with stock from Sammobile

leodavi3d said:
Hello everyone. :good:
I will try to be brief...
I have a J5 model SM-J500M/DS with Custom binary blocked by FRP (lock: on)
The problem is:
After flash firmware using both Odin/Z3X Pro, the message screen "Custom binary blocked by FRP" still there.
1 - I tried all versions of stock roms from: sammobile (android 5.1, 6.0), SamFirm (last firmware).
2 - I tried separated firmware repair files (BL, CP, CSC, etc..)
3 - KIES and Smart Switch same alert that SM-J500M does not have support for initialization emergency:
Is there another way to turn FRP off? :crying:
Take a look the screens below:
Thank you :good:
This is the log screen on both Odin and Z3X:
Using repair firmware with separated files
Using stock rom from Sammobile
Z3X with individual files
Z3X with stock from Sammobile
Click to expand...
Click to collapse
Just solved this kind of problem yesterday download lastest Odin and lastest rom which is available for ur device .u have to uninstall Kies and smart switch they would be a trouble while working with Odin so u should uninstall them first then press volume down +power button +home button it would take u to download mode then connect ur device to PC.if Odin detects ur device then press AP in Odin and load the rom to Odin then start flashing .if the phone got into a boot loop repeat the process again and re flash the rom .it would work I had a sm-j500f which I solved with the same process .I hope it would work for u too

mjhonny14377 said:
Just solved this kind of problem yesterday download lastest Odin and lastest rom which is available for ur device .u have to uninstall Kies and smart switch they would be a trouble while working with Odin so u should uninstall them first then press volume down +power button +home button it would take u to download mode then connect ur device to PC.if Odin detects ur device then press AP in Odin and load the rom to Odin then start flashing .if the phone got into a boot loop repeat the process again and re flash the rom .it would work I had a sm-j500f which I solved with the same process .I hope it would work for u too
Click to expand...
Click to collapse
Sure mate, KIES was the last attempt...After to try with ODIN and Z3X pro.
I uninstalled KIES but.... Both programs ODIN and Z3X pro have success instalation but FRP block still there...

Why dont u turn off frp in stock first then onpy procced to switch rom? I unlock my frp easily using few method i found in youtube. I hope it help you.. good day mate

Odin Stock Firm Flash fails after cache.img

So, first of all
I'll state everything that have happened so far.
First, I got a phone with a sm-g935fd model carrier locked (smart from ph). then i decided to have it unlocked after reading and following the thread "Honestly free Sim unlock". I followed the instructions specifically to flash the combination firmware G935FXXU2ARA1 and have it unlocked and it succeeded. then now that i already have it open lined, i decided to proceed and flash the latest stock firmware from my country specifically the 1/31/18 release G935FXXS2DRAB for PHilippines OPEN LINE.
First thing i did when i'm still in the combi firmware was to activate developer options and turn on usb debugging. i also had hoped to turn on OEM unlock but the option wasn't there. Still, i proceeded flashing it via Odin v3.13.1 but ended up failing right after cache.img showed up. after failing, i reflashed to the combination firm (i do this everytime i fail, sort of like my way to recover to a working firm). I tried to seek help and after listening to advices, i tried these: first, i tried flashing the same latest stock but this time using a pit file i extracted from that very stock firm. Still, it failed at cache.img. too. I then tried to flash the same latest stock firm but this time, i modified the csc by extracting its contents and recompressing them all except cache.img to a tar file using 7.zip. I then proceeded to flash this stock firmware while using the csc.tar file without cache.img in it. Still, it ended up failing but this time after hidden.img.
After this, i have thought to flash it the same way as the most recent flash(csc without cache.img) but this time using the pit file again from this latest stock but i ended up hesitating and deciding to research things first before proceeding. After skimming through forums, i've read frp lock issues but when i'm doing all the flashing i've stated above, in the download mode it says FRP LOCK: OFF. I then also tried to flash other firmwares specifically the first released 6.0.1 stock firm (smart carrier) and the latest stock firmware 7.0 1/31/18 (smart carrier).
The first one truly send chills down my spines since i ended up having a bootloader exception and i can't access download mode. but after researching a bit, i pressed and sometimes hold the home button in desperation and when the logo appeared i used the combo buttons for download mode then managed to reflash the combi firm. I then learned that i shouldve followed the warning of not flashing a lower numbered bootloader. then after that, i tried the latest stock firm from smart(the carrier i was locked first) Still, it ended up failing at cache.img. As of now, I feel like a bit hopeless since the only stock firmwares for my country that might work are the latest stock firmwares since they are the only ones having 2xxxx bootloader.
I just can't seem to flash an original firmware from this combination firm. Could anyone possibly offer me some advice?
{
"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"
}

I had the same issue as you, with this exact combination binary. I couldn't get any other stock firmware and I got the same bootloader exception where I freaked out. No other combination binary seemed to work. So I decided to try the latest XSA Stock for Australia and it worked. So I recommend that you try that. But I still can't boot down or anything else. No other combination I have run into works. Hope this helps you out.

E: failed to mount /efs (invalid argument)

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.

Note Fan Edition N935S - Stuck on looping Start Logo Screen

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.