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.
failed to mount /efs (Invalid argument) Issue
Hi, First Off I should state i'm still a bit of a noob with all this stuff...I'm currently experiencing trouble with my Samsung galxey note 2 GT-N7105
Its stuck in a boot loop and When I go in to recovery It comes up In red writing E:failed to mount /efs (invailed argument) I DID have CWM recovery But for some reason Its gone and Only comes up with the stock android system recovery.
I've tried everything I can think of.. I've done a factory reset with no luck, I've tried re-installing CWM via odin , I installed a stock rom via odin no luck and when I try connecting it to kies It recognizes that its plugged in but just keeps Saying "connecting"
I'm really stuck here and out of my depth.
thanks in advance.
A Friend gave me his galaxy s3 since he recently upgraded to a note 4, so naturally i wanted to wipe everything on it and i figured the fastest way would be me doing a factory rest. . so the phone does its thing then reboots into recovery with the image of the android guy on his back with a red cation thingy above him.
i get the following messages below the blue option menu thing that you scroll with using the volume rocker. :
E: failed to mount /data (invalid argument)
cant mount '/data' (invalid argument)
E: failed to mount /data (invalid argument)
and others like it all saying it cannot mount /data
i tired using kies to have an emergency firmware update but ask me for a code.
would be installing a custom recovery and downloading a custom rom fix this or not ?
please help
Hey guys, so my girlfriend's S4 mini won't turn on and its stuck on the Samsung booting logo. I did a hard reset, but with no luck, wiping the cache didn't help either. I flashed a stock rom with but that also didn't work. When i enter recovery mode this is what I get:
did not match sized ' /system/csc/common/system/csc/others.xml ' (No data available)
E: failed to mount /cache (Invalid argument)
can't mount '/cache' (Invalid argument)
E: failed to mount /cache (Invalid argument)
E: Cab't mount /cache/recovery/last_recovery
E: failed to mount /data (Invalid argument)
E: Can't mount /data/log/recovery_log.txt
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
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: failed to mount /cache (Invalid argument)
Click to expand...
Click to collapse
mlakov said:
Hey guys, so my girlfriend's S4 mini won't turn on and its stuck on the Samsung booting logo. I did a hard reset, but with no luck, wiping the cache didn't help either. I flashed a stock rom with but that also didn't work. When i enter recovery mode this is what I get:
Click to expand...
Click to collapse
I have bad news for you. If none of those methods that you tried worked, it probably means you have a fried storage which is probably the cause of the Recovery not being able to mount the partitions as it cannot find any.
Sayrian said:
I have bad news for you. If none of those methods that you tried worked, it probably means you have a fried storage which is probably the cause of the Recovery not being able to mount the partitions as it cannot find any.
Click to expand...
Click to collapse
So i should replace the motherboard ?
mlakov said:
So i should replace the motherboard ?
Click to expand...
Click to collapse
That could be one solution, however, What problem are you encountering while flashing a stock OS?
Sayrian said:
That could be one solution, however, What problem are you encountering while flashing a stock OS?
Click to expand...
Click to collapse
I flash stock os without encountering problems, but the phone still doesnt turn on
mlakov said:
I flash stock os without encountering problems, but the phone still doesnt turn on
Click to expand...
Click to collapse
Have you tried to flash a custom recovery to see if that does the trick?
I flash a custom recovery but when i go in recovery mode it takes me to the stock recovery
Hi there !
I have an Ascend Mate(M1-U06) here which stopps booting, first it shows the Huawei logo, then a white android logo - thats all.
When i enter recovery mode it works, the phone shows me this line:
""""
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument)
""""
Flashing or wiping in this menu fails.
Meanwhile I'm familiar with adb/fastboot.
Drivers are installed(Win10), phone is recognised, bootloader is unlocked.
I tried flashing several images, I tried flashing TWRP, everything worked well but nothing changed.
After flashing TWRP 2.6.3.3 I enter recovery mode and there is still stock recovery mode(3e).
What am I doing wrong, did i forget something ?
Can i use every TWRP Version for the mate ?
Tried to flash stock rom without success.
any ideas
thanks in advance
VirtuAl