Samsung Galaxy S4 Mini Boot Loop (Stock ROM fail) - Galaxy S 4 Mini Q&A, Help & Troubleshooting

So I have a Galaxy S4 Mini (GT-i9091) stuck on boot loop.
On entering Recovery, I try "wipe data/factory reset" and get a failed message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TPA
Unable to open dst ' /system/app/VivaElFutbol_v1.03.apk' (No Such file or directory)
--Wiping data ...
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Flashing Stock ROM through ODIN gets a PASS (all threads completed, succeed 1 / failed 0), but on reboot it goes back to the Logo Boot Loop. I read elsewhere it may be a hardware issue rather than a software one. I'm looking for any advice or steps that I may be missing or is the phone doomed to be a shiny & fancy paperweight? Any info would be appreciated! :fingers-crossed:

Up? I have some problem
Enviado de meu SM-G800H usando Tapatalk

romTester14 said:
So I have a Galaxy S4 Mini (GT-i9091) stuck on boot loop.
On entering Recovery, I try "wipe data/factory reset" and get a failed message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TPA
Unable to open dst ' /system/app/VivaElFutbol_v1.03.apk' (No Such file or directory)
--Wiping data ...
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Flashing Stock ROM through ODIN gets a PASS (all threads completed, succeed 1 / failed 0), but on reboot it goes back to the Logo Boot Loop. I read elsewhere it may be a hardware issue rather than a software one. I'm looking for any advice or steps that I may be missing or is the phone doomed to be a shiny & fancy paperweight? Any info would be appreciated! :fingers-crossed:
Click to expand...
Click to collapse
Hi my friend!, I'm suffering now exactly the same problem as you...I can't erase that app and the phone goes back every time to the logo boot loop...Did you find any solution to your problem?? please any information would be useful...
Thanks,

really? nobody can help?
I am having same problem. any solution?

Hi there ..
I have the same problem for GT-i9192 with same problem message showed up after entering recovery menu :
Unable to open dst '/system/app/VivaElFutbol_v1.03apk' (No such file or directory)
did you fix this ?!
reply needed ^^

i am having the same problem but i cant even enter recovery mode
ODIN MODE
PRODUCT NAME: GT-i9195
CURRENT BINARY: CUSTOM
SYSTEM STATUS : CUSTOM
KNOX KERNEL LOCK : 0X0
KNOX WARRANTY VOID : 0X1
CSB-CONFIG-LSB : 0X30
BOOTLOADER AP SWREV : 2
WRITE PROTECTION : ENABLE

Related

Samsung S4 mini (GT-I9192) Boot loop

Hi, can anyone help me?
Samsung S4 Mini (GT-I9192) is stuck on boot logo, after unexpectedly turned off on normal android update. Tried so many tutorials but nothing works. Nothing!
Here goes all info I can think about it:
- Download Mode shows up exacly that:
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB:0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
- If I try to "wipe/datafactory reset", gives me error:
# MANUAL MODE #
-- Apling Multi-CSC...
Applied the CSC-code : ZT0
Sucessfully applied multi-CSC.
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/cache
Data wipe complete.
Can someone help me? Thanks!
i have same problem but in 9195
What recovery do you have?

Help need to unbrick my Samsung S4 mini DUOS (GT-i9192)

Hi, a few months ago I installed Kingroot on my Samsung S4 mini DUOS (GT-i9192)... Idk if it has something to do with it, but after a while my phone suddenly starts to reset without reason at all. I tried to unroot but it didn't let me to unistall, delete or overwrite any kind of app, archive or folder. I can't even do a full wipe or install a custom recovery.
Here is the problem when I start the recovery...
Android system recovery <3e>
KOT49H.I9192XXUCOA1
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : CAC
did not match sized '/system/csc/common/system/csc/languaje.xml'(no data available)
And when I tried to do a full wipe/factory reset...
-- Wiping data...
Formating /data...
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata
Formating /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/cache
Data wipe complete
Every help will be so appreciated... Thanks
PD: Sorry for my english is pretty basic...

How to Unbrick SM-A720F ?! (FRP = On) | E:failed to mount /efs | Combination not work

Hi everyone
I have some questions about Samsung SM-A720F
here is Samsung SM-A720F which has frp lock ! (FRP = On)
I know how to solve this problem, but it has another problem that doesn't let the device to become Ok.
First, the "System Status = Custom" in Downloading Mode , which usually flashing device with Official Firmware it should be changed to "Official
it's wired !!! I've tried 10 different Firmwares with correct binary (the phone's binary is 3 and firmware's binary is also 3)
but it doesn't changed to "Official" ( still System Status = custom :| )
note : i also tried combination files on this phone !
Second , after device flashing , it's just rebooted to recovery mode and shows the below error messages :
- E:failed to mount /efs (Invalid argument)
- E:failed to clear BCB message: failed to find /misc partition
- dm-verity verification failed...
As i know flashing the custom recovery on phone and adb commands solved my problem ! but frp lock is on and i can't flash the custom recovery !!!
note : phone not booted after flashing !
Does anyone know how to deal with this ?!
same problem
My phone also same problem
1) i try to solve from twrp but any rom flashing time - E:failed to mount /efs (Invalid argument)
2) i flash from odin its showing pass but till now mobile booting not complet.
3) i tryied from smart switch also s/n not correct.
please help me before i was used hadesh rom.
SM-A720f/ds
Android IR said:
Hi everyone
I have some questions about Samsung SM-A720F
here is Samsung SM-A720F which has frp lock ! (FRP = On)
I know how to solve this problem, but it has another problem that doesn't let the device to become Ok.
First, the "System Status = Custom" in Downloading Mode , which usually flashing device with Official Firmware it should be changed to "Official
it's wired !!! I've tried 10 different Firmwares with correct binary (the phone's binary is 3 and firmware's binary is also 3)
but it doesn't changed to "Official" ( still System Status = custom :| )
note : i also tried combination files on this phone !
Second , after device flashing , it's just rebooted to recovery mode and shows the below error messages :
- E:failed to mount /efs (Invalid argument)
- E:failed to clear BCB message: failed to find /misc partition
- dm-verity verification failed...
As i know flashing the custom recovery on phone and adb commands solved my problem ! but frp lock is on and i can't flash the custom recovery !!!
note : phone not booted after flashing !
Does anyone know how to deal with this ?!
Click to expand...
Click to collapse

A520F Can get into only recovery and download mode, stuck on samsung logo. ESF empty

Hello guys,
Long story short. Two days ago I tried to install lineageOS, managed to do it = no sim card error. Tried installing 15.1 same, did some wiping, erasing without knowledge or backups. Now installed latest [BALTIC] rom from sammobile, stuck on samsung logo during boot, in recovery mode it says some errors:
No support single-sku
E:Failed to mount /efs (Invalid argument) like 4x times
dm-verity verification failed...
E: Failed to clear BCB message: Failed to find /misc partition
I have no backups. Is it still possible to fix this phone? Or I screwed it up totally?
Thank you
Respectfully,
Tomas

S7 - failed to mount /efs (invalid argument) after OTA update

I have an S7 (Korea model, bought on EBay a year ago) which no longer boots after the latest OTA update - it freezes on the SK Telecom splash screen after the Samsung logo.
I started out hoping to restore data, but now I am just hopeful I can get a working phone again, but it doesn't seem likely from what I have read, as it appears my EFS is corrupt, and I have FRP lock enabled which prevents me from installing TWRP or other tools.
Here are the things I have tried:
1. Used Odin to flash the latest official firmware (SKC-G930SKSU3ETJ1-20201105091200) (BL, AP, CP HOME_CSC)
2. Wiped flash from Recovery
3. Wiped data/factory reset from Recovery
4. Tried to load TWRP via Odin, but blocked by FRP
5. Tried to use adb sideload twrp... from a PC but also blocked by FRP
I can get into recovery, but get the E:failed to mount /efs (invalid argument) error
I can get into download mode with:
PRODUCT NAME: SM-G930S
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 1 (0x0500)
AP SWREV: B:3 K:2 S:2
I didn't root this phone myself, but believe it was done by the eBay seller I got it from. The recovery screen appears to be original, so I'm not sure why I get a SYSTEM STATUS: Custom on the download screen, as I have original Samsung firmware.
Android Recovery
samsung/herolteskt/herolteskt
8.0.0/R16NW/G930SKSU3ETJ1
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Power off
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File Based OTA
E:failed to mount /efs (Invalid argument)
Supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity verification failed...
Is there a way out of this, or do I have a bricked phone?
Looks like it's bricked, so I guess I'll offer it for parts on eBay. Got her a new A11, not as nice as the S7 in some ways, but at least it's covered with a 2 year protection plan...

Categories

Resources