Hi all--apparently I "softbricked" (or "soft bricked") my unlocked at&t s3 (SGH-I747) that I rooted since, after I factory reset and cache wiped my 4.1.1, I get passes on Odin whenever I try to install 4.1.1 again, which is all I wanted to do so I could try to upgrade to 4.3, but I never got that far. I just can't get 4.1.1 working again after a factory reset cache wipe.
What happens, now, is that my phone just can't get past the pulsing blue samsung logo after rebooting into any new 4.1.1 firmware I load with Odin (and I tried a few options--both stock SGH-I747 4.1.1 and the one here), or root66, but my phone just gets stuck on the pulsing blue samsung logo and stops there every time. Kies can't connect to my phone any longer, either, and it won't recognize my phone for a firmware reset, and my computer will no longer recognize my phone nor successfully install drivers for it when it's trying to boot (when I connect my phone in recovery or download mode, however, my computer will install a driver to let the computer see the phone, but I can't actually do anything with the phone after that--and Kies doesn't connect after the computer installs these drivers, either).
So, in sum: I can successfully flash 4.1.1 stock/alternatives with Odin ("pass!") but that doesn't get me past the pulsing blue samsung icon. I think I've tried to flash a new boot partition during this process, but I'm not sure. Any advice would be much appreciated, since I've been working on trying to fix my phone for a day and a half now without any luck
Slight update: I installed CWM Recovery (PhilZ Touch) and wiped again but after loading the 4.1.1 stock/alternative (above link) my phone--still--won't get past the pulsing blue samsung logo still.
Additional info.: when I boot in recovery mode after flashing the above root66 rom, I get the following errors:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
Also, I just noticed when I try to factory reset again it says this:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17
Data wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
etc.
Thanks for taking the time to read this. I appreciate it very much. I honestly can't do anything until I get help here.
Pfhyde said:
Hi all--apparently I "softbricked" (or "soft bricked") my unlocked at&t s3 (SGH-I747) that I rooted myself, later, since I get passes on Odin whenever I try to install new firmwares, so I don't have the same problem those trying to roll back to 4.1.1 after failing to get 4.3 going, since in my case, I just can't get 4.1.1 working again after a factory reset cache wipe. I wanted to put a stock 4.1.1 on so I could try to update to 4.3, but I never got far enough to even try that.
What happens, now, is that my phone just can't get past the pulsing blue samsung logo after rebooting into any new 4.1.1 firmware I load with Odin (and I tried a few options--both stock SGH-I747 4.1.1 and the one here), or root66, but my phone just gets stuck on the pulsing blue samsung logo and stops there every time. Kies can't connect to my phone any longer, either, and it won't recognize my phone for a firmware reset, and my computer will no longer recognize my phone nor successfully install drivers for it when it's trying to boot (when I connect my phone in recovery or download mode, however, my computer will install a driver to let the computer see the phone, but I can't actually do anything with the phone after that--and Kies doesn't connect after the computer installs these drivers, either).
So, in sum: I can successfully flash 4.1.1 stock/alternatives with Odin ("pass!") but that doesn't get me past the pulsing blue samsung icon. I think I've tried to flash a new boot partition during this process, but I'm not sure. Any advice would be much appreciated, since I've been working on trying to fix my phone for a day and a half now without any luck
Slight update: I installed CWM Recovery (PhilZ Touch) and wiped again but after loading the 4.1.1 stock/alternative (above link) my phone--still--won't get past the pulsing blue samsung logo still.
Additional info.: when I boot in recovery mode after flashing the above root66 rom, I get the following errors:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
Also, I just noticed when I try to factory reset again it says this:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17
Data wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
etc.
Thanks for taking the time to read this. I appreciate it very much. I honestly can't do anything until I get help here.
Click to expand...
Click to collapse
If you're just looking to get back to stock 4.3, you can use this:
http://forum.xda-developers.com/showthread.php?t=2496425
You'll need the Heimdall suite:
http://glassechidna.com.au/heimdall/
Once the drivers and all are there, use the Flash tab in Heimdall and attach each file appropriately.
I had to do this same process recently so feel free to hit me up if you have an issue.
mstrswrd06 said:
If you're just looking to get back to stock 4.3, you can use this:
http://forum.xda-developers.com/showthread.php?t=2496425
You'll need the Heimdall suite:
http://glassechidna.com.au/heimdall/
Once the drivers and all are there, use the Flash tab in Heimdall and attach each file appropriately.
I had to do this same process recently so feel free to hit me up if you have an issue.
Click to expand...
Click to collapse
Well, I haven't ever had 4.3 on my phone, so there's nothing to 'get back' to. I was wanting to upgrade to 4.3, but then my factory reset/cache wipe made my phone unbootable after installing 4.1.1 firmware roms. If you think I should just try to install 4.3 in the state my phone's in now, then okay--but that seems to possibly introduce other problems, from what I've been reading elsewhere.
Did you get the stock 4.1.1 firmware from sammobile.com?
audit13 said:
Did you get the stock 4.1.1 firmware from sammobile.com?
Click to expand...
Click to collapse
Yes, as it turns out I did that already--I recognized the site immediately. I downloaded the default at&t rom again and will try flashing it (again) in the morning, but I doubt anything new will happen.
Try flashing 4.1.1 again in Odin, uncheck everything except F. Reset. When you see reset in the status windows, remove the USB cable, remove, the battery, replace the battery, go into recovery, perform a full wipe, then reboot. Do a full wipe before you first boot the newly-installed OS may fix the issue.
audit13 said:
Try flashing 4.1.1 again in Odin, uncheck everything except F. Reset. When you see reset in the status windows, remove the USB cable, remove, the battery, replace the battery, go into recovery, perform a full wipe, then reboot. Do a full wipe before you first boot the newly-installed OS may fix the issue.
Click to expand...
Click to collapse
First, when I go into recovery after flashing 4.1.1 default for at&t (though my phone is unlocked and was rooted--don't know if the root is still there after all that's happened) it says right away
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
#Manual MODE#
--Appling Multi-SCSC...
Applied the CSC-code:ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E: etc.
Then, when I try to wipe it gives me an error:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
Data wipe complete.
Then rebooting freezes on pulsing blue samsung logo--again
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
audit13 said:
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
Click to expand...
Click to collapse
It says
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Sorry for my belated responses, but I work late on the weekends in NZ.
audit13 said:
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
Click to expand...
Click to collapse
Strange--I just booted up in recovery mode and wiped again; this time I got no errors, so I rebooted and--it works now in 4.1.1. Why it never wiped altogether before, when I didn't do anything different, is confusing; but there you have it. Now I'll venture into trying to get 4.2 or something.
Thanks all for your patience and help, even though in the end it worked on a fluke.
Glad you got your phone working. You do not have the 4.3 bootloader and, if I were you, I would not install the ATT 4.3 OTA update. This will install the 4.3 bootloader which makes it more difficult to get back to stock.
Pfhyde said:
Strange--I just booted up in recovery mode and wiped again; this time I got no errors, so I rebooted and--it works now in 4.1.1. Why it never wiped altogether before, when I didn't do anything different, is confusing; but there you have it. Now I'll venture into trying to get 4.2 or something.
Thanks all for your patience and help, even though in the end it worked on a fluke.
Click to expand...
Click to collapse
Some people have no problems at all, but CWM has a history of not wiping properly. That's why I don't using it anymore. There always came a point when it just would not wipe properly.
my S4 Mini is stuck in a bootloop
i can get to recovery screen which is CWM 6.0.4.8 but no commands work they all produce the following errors
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
i therefore cannot wipe or reformat the caches, or do factory reset, or load ROM from a ZIP file.
i can also get into Download mode and i have used Odin to flash a number of different ROMS; stock ROM for my Carrier, Stock ROM for unlocked UK and Cyanongenmod. In each case it looked to by uploading correctly and Odin reported success but it did not fix bootloop
i also tried to upload different versions of CWM but although Odin reported upload successful the version of CWM I have never changed and the error remained.
i tried briefly with Heimdall but could never seem to find the files i needed in the format that Heimdall requires
ADB seems to talk to the phone but i'm not sure what i'm doing with it.
Fastboot will not "see" the phone.
can someone suggest how i can proceed. i don't care about keeping any data on the phone i just want a working phone back
thanks in advance
Glen
Harani said:
my S4 Mini is stuck in a bootloop
i can get to recovery screen which is CWM 6.0.4.8 but no commands work they all produce the following errors
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
i therefore cannot wipe or reformat the caches, or do factory reset, or load ROM from a ZIP file.
i can also get into Download mode and i have used Odin to flash a number of different ROMS; stock ROM for my Carrier, Stock ROM for unlocked UK and Cyanongenmod. In each case it looked to by uploading correctly and Odin reported success but it did not fix bootloop
i also tried to upload different versions of CWM but although Odin reported upload successful the version of CWM I have never changed and the error remained.
i tried briefly with Heimdall but could never seem to find the files i needed in the format that Heimdall requires
ADB seems to talk to the phone but i'm not sure what i'm doing with it.
Fastboot will not "see" the phone.
can someone suggest how i can proceed. i don't care about keeping any data on the phone i just want a working phone back
thanks in advance
Glen
Click to expand...
Click to collapse
Did you tried to install an other recovery via odin? I had a similar issue with twrp 2.8.7.0 dont know why, but I flashed the newest twrp with Odin and then all works fine after that.
Try to use a new recovery, cwm 6.0.5.1 for example.
http://forum.xda-developers.com/showthread.php?t=2364980
I have same exact problems............. i have an opened thread and i have found this thread by google but no resolution... this phone it's dead ?
Try twrp 3 if it doesn't work try stock rom
erkin98 said:
Try twrp 3 if it doesn't work try stock rom
Click to expand...
Click to collapse
Hi, I try almost all recovery found here:
- CWM-6.0.5.1-serranoveltexx
- TWRP-2.6.3.0-serranoltexx
- TWRP-2.8.4.0-serranoveltexx
- twrp-2.8.6.0-serranolteusc
- TWRP-2.8.7.1-serranoveltexx
- twrp-3.1.1-0-serranolteusc
Use those method:
https://forum.xda-developers.com/showthread.php?t=2751224
https://forum.xda-developers.com/showthread.php?t=2678420
http://forum.xda-developers.com/show....php?t=2364980
No one work!! Can enter in Download Mode, but not in Recovery Mode, always say: "Command not found"
In Download Mode says this:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 1
WRITE PROTECTION: Enable
Anybody here can help me? Thx!!
EDIT: I Always flash using Heimdall under Linux, try flash stock ROM with Odin, and flash 2 Recovery with Odin, same problem!!
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?
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
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...