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.
Related
Hi everybody, i am new to this forum, i recently tried to root my galaxy s3 sgh-I747 but my pc got frozen and the proces stoped in the middle. So when i turned on the s3 it didn't turn on. So i used a tutorial to try to get my phone working and i use the sgh-I747 4.1.1 software version. When the cell phone reboot it did turned on buy a message saying android had stopped working come out. so i tried reseting the s3 to factory but some errors come out.
Now when i go to Android system recovery it sais
"E: failed to mount /data (invalid argument)
can't mount 'data' (Invalid argument)
# MANUAL MODE #
-- Appling 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)"
And when i turn it on normally it loops at the samsung logo.
How can i fix it?
Provide me detailed info due to I'm new at this
Agus361 said:
Hi everybody, i am new to this forum, i recently tried to root my galaxy s3 sgh-I747 but my pc got frozen and the proces stoped in the middle. So when i turned on the s3 it didn't turn on. So i used a tutorial to try to get my phone working and i use the sgh-I747 4.1.1 software version. When the cell phone reboot it did turned on buy a message saying android had stopped working come out. so i tried reseting the s3 to factory but some errors come out.
Now when i go to Android system recovery it sais
"E: failed to mount /data (invalid argument)
can't mount 'data' (Invalid argument)
# MANUAL MODE #
-- Appling 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)"
And when i turn it on normally it loops at the samsung logo.
How can i fix it?
Provide me detailed info due to I'm new at this
Click to expand...
Click to collapse
Your phone model is the AT&T SGH-I747 correct?
First we need to know which version was your phone running before you had this issue happen 4.1.1, 4.1.2 or 4.3 ?
since you say you were trying to root we can assume your phone was all stock right?
What were you using to get it working again Kies, Odin, CWM, TWRP??? and what were the associated files you used?
theramsey3 said:
Your phone model is the AT&T SGH-I747 correct?
First we need to know which version was your phone running before you had this issue happen 4.1.1, 4.1.2 or 4.3 ?
since you say you were trying to root we can assume your phone was all stock right?
What were you using to get it working again Kies, Odin, CWM, TWRP??? and what were the associated files you used?
Click to expand...
Click to collapse
Yes, my phone model is AT&T SGH-I747.
I was running the 4.1.2 before this happened.
Yes it was with warranty and the samsung software.
I used odin, and i used a phile called "I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5".
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.
Tried updating my phone today. Rooted SGH-i317 on 4.2.2
Thought i had the correct file but now it appears i dont
getting E:failed to mount /system (invalid argument)\
#manual mode#
-- appling Multi-csc...
E:failed to mount /system (invalid argument)
can't mount '/system'(invalid argument)
E:fialed to mount /system (invalid argument)
it looks like i may have used an N7100 file to flash and thats when s*** hit the fan.
at the top of recovery mode i have
Android system revoery <3e>
KOT49H.N7100XXUFND3
end result would obviously like to be back to a working phone and up to date on 4.4.2. Any help is greatly appreciated. I have tried flashing a few files in odin without success. A lot of the files are nowhere to be found at this point, online, and would appreciate any input. Thanks guys.
i was SUCCESSFULLY able to get back to a stable working version, 4.1.1 i cannot attach of the file i had to flash with Odin, but if you search for KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar you will DEFINITELY find it. . Basically went back into download mode, selected this file with odin under AP, then plugged in and hit start. Flashed, worked, success. now to update to 4.4..
Long history: I was using Ivan_Meler CM 13.1 ROM for ~ 3 months, which was very stable. Last week I downgraded from build 10 to build 9 with only dirty flash and everything was working fine, just some occasionally FC. Then one night I left my phone ran on very low battery and when I woke up I found my GT-N7100 stuck on Samsung boot logo.
I'm still able to access ODIN download mode. When I get into recovery mode (CWM Philz Touch v6.26.6), I immediately get this messages:
E: could not mount /data to setup /data/media path!
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
What I've tried so far:
1. Restore Nandroid backup (KOT49H.N7100UBUFNK1) using CWM
->>>>> got E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p13
2. Flash, using both adb sideload and ODIN:
Stock ROM 4.3 (N7100UBUEMK4_N7100ZTOEMK3_ZTO) and 4.4 (N7100UBUFNK1_N7100ZTOFNK1_ZTO), downloaded from Sammobile
->>>> got "NAND write fail" on ODIN and
->>>> on adb sideload the file loads 100% but I got "error:closed" and after "failed to write data 'protocol fault (no status)' "
3. Flash only the hidden.img of the stock ROM's mentioned above, I got "PASS" on ODIN but after phone gets stuck on boot Samsung logo
Tried this guide, using stock 4.1.2 (N7100XXDLJ2_OXA_FACTORY) with and without re-partition
->>>> got "NAND write fail" as well.
So I have ran out of options can anybody please help :crying::crying::crying: I really like my Note 2 and I don't have money to buy a new phone right now.
SDS for 99%
Try flashing the latest stock rom using a different USB cables, different versions of Windows, and different USB ports. If none of these work, the memory chip may be damaged.
So, I've got a Galaxy Tab S 10" (SM-T800X), its the retail demo version and I've been trying to remove the retail demo firmware, I can't factory reset the device because the option is greyed out. So far I've had no luck, I've tried using Odin to install a stock ROM but that doesn't do anything. I've tried going through recovery mode to wipe the device and it says that MDM doesn't allow factory reset. Tried running Odin a few times in case it just wasn't working the first time. I've now encountered a new problem where its stuck on the Samsung logo when I try to turn it on, even after running it through Odin, and whenever I boot it into recovery mode I get the message
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_lot.txt
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/emmc_checksum_log.txt
I'm at a loss as to what I should do here, I don't use android and have never rooted a device so I've just been reading what I've found on the internet to attempt to solve it.
Anyone got any ideas what I should do now?
crotmate said:
So, I've got a Galaxy Tab S 10" (SM-T800X), its the retail demo version and I've been trying to remove the retail demo firmware, I can't factory reset the device because the option is greyed out. So far I've had no luck, I've tried using Odin to install a stock ROM but that doesn't do anything. I've tried going through recovery mode to wipe the device and it says that MDM doesn't allow factory reset. Tried running Odin a few times in case it just wasn't working the first time. I've now encountered a new problem where its stuck on the Samsung logo when I try to turn it on, even after running it through Odin, and whenever I boot it into recovery mode I get the message
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_lot.txt
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/emmc_checksum_log.txt
I'm at a loss as to what I should do here, I don't use android and have never rooted a device so I've just been reading what I've found on the internet to attempt to solve it.
Anyone got any ideas what I should do now?
Click to expand...
Click to collapse
You need to install TWRP. Factory reset within TWRP, reboot to Download mode then install the stock firmware with odin.