Back story: OTA update to 4.3 killed USB on this phone, so there is no USB access to it - at all. I don't have a Windows computer, so I never downloaded ODIN to root the phone. It is completely stock, other than the unlock code obtained from T-Mobile.
I just switched from T-Mobile to AT&T, and for some reason had no data connection on the phone, even with the correct APN settings. I decided to try a factory reset. I went through the system settings menu and found the "Reset to factory settings" menu item, selected it, acknowledged the warning, input my PIN and let it go to work.
A few minutes later, it had rebooted into recovery. Sicne it was there, I took the opportunity to use the boot-loader's reset function and wiped the cache while I was at it. That was a mistake.
Now, the phone won't boot past the pulsing Samsung logo. I can get back to the recovery, and it pops up these errors - first, the droid on his back with the red triangle over him flashes "No command", and then it dumps me to the recovery menu with this scrolled at the bottom of the screen:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC
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_log.txt
It's obviously soft bricked. I can't use ODIN to flash anything. But, since I'm at the recovery screen, it is giving me the option of loading an update from external storage - what should I put on the SD card to load in order to fix it? Can I fix it without ODIN?
edit to add:
I've already tried the stock UVUEMJC firmware from DocHoliday77's thread, but it threw a bunch of errors across the screen that I didn't catch in time and rebooted to the same point.
Try @saranhai's StockMod Rom. Put it on the External SD and flash it. If that fails, please post the error log.
On another note. can you try in Recovery and manually mount /Data Partition ?
Perseus71 said:
Try @saranhai's StockMod Rom. Put it on the External SD and flash it. If that fails, please post the error log.
On another note. can you try in Recovery and manually mount /Data Partition ?
Click to expand...
Click to collapse
Stuck @ work today, and I didn't bring it with me. I'll give that a shot when I get home tonight. I don't recall seeing a "mount" option in recovery - it's the stock Samsung recovery, I'm not sure I made that clear in the OP.
My Nexus 5 arrived last night, so this is becoming a project for me. I just want to know if I can make it work, but without USB access to it, that is probably a non-starter.
If you have Stock Rom, there isn't anything you could flash that way. At the most you could flash a Stock firmware via KIES.
Related
Hello all
I was updating my gf phone from rooted UVALJ4 or UVALH2 (Cant remember now, but it was an old Firmware) to root66 T999_UVUENC2 via Odin 3.09 on my Win 7 pc but after the odin install (which passed) I rebooted the phone and I got stuck on the Samsung logo on the start up screen. After about 10 mins I pulled the battery and tried to enter the Recovery mode, but nothing appears. Just a black screen.
So i Odin flashed the TWRP 2.6.3.1 to try to get to a recovery, but that didnt work. Still no Recovery.
I then used odin to flash the stock tmobile UVUENC2 4.3 firmware and it still gets stuck on the Samsung screen.
Next I tried to unbrick it via http://forum.xda-developers.com/showthread.php?t=2439367 using "SGH-T999 4.3 only Debrick Image" and reflashed the stock 4.3 rom, but that didnt work. :crying:
What can I try next? WHat should I do? I can still access download mode, thats about it.
Please help if you can.
Thx
I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx
synplex said:
I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx
Click to expand...
Click to collapse
Never Mind Used Unified Android Toolkit to fix recovery and flash stock rom.
Thank god for that toolkit.
...time to donate
:victory:
Mod Please delete Thread.
Thx
In the future, try a factory reset, almost all boot hangs are solved with this. Happens because of incompatible data between versions, which would make sense condidering the jump you made. Kind of makes sense with the error message too, but I'm not 100% certain there.
Be careful with the toolkit. There is no support for it and it has bricked phones in the past.
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
ericmerl said:
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
Click to expand...
Click to collapse
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Stock ROMs
Larry2999 said:
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
ericmerl said:
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
Click to expand...
Click to collapse
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
ericmerl said:
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
Click to expand...
Click to collapse
To follow up again, I was able to re-flash TWRP using Odin. Once that was done, the phone no longer tried to boot straight to recovery. I was able to three finger into TWRP, though it took a super long time for it to boot.
Here's the console log taken from TWRP once it boots:
Code:
E:Could not mount /data and unable to find crypto folder.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
Running boot script...
Finished running boot script.
E:Unable to mount '/cache'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E:Unable to mount '/data'
Ok here is the story about a year ago I rooted my AT&T GS3 installing CWM and Cyanogenmod. I hadn't had an issue until mid-september. For some reason one of the updates caused certain phone functions to quit working, specifically my mobile data. I searched around on the internet and found out that it had probably affected my modem files, and was told to flash back to stock and that that should solve it. I found a stock firmware file and flashed it with odin. When my phone rebooted it boots to the point of the samsung emblem with the oscillating blue background and just sits there. I tried flashing different versions of the firmware to the same result. I later learned I probably flashed just the modem which I found while trying to solve the problem. When I boot into stock recovery i receive the following message:
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)
Anything will help because I am currently without a phone so.... thanks
Edit 1: The Firmware I attempted to flash came from samsung-updates.com though I am not sure of what build and can't check since it won't boot all the way
What firmware build are you on?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I cannot tell what build, I got it from samsung-updates.com in a zip titled ATT-I747UCDLK3-201211116120549
I would download it again in case it was somehow corrupted. The build is in the filename, LK3, which appears to be 4.1.1. I would say to try 4.1.2 instead, but it appears that wasn't released by AT&T either.
Or if you want you can try flashing the root66 firmware instead. It's LK3 too, only pre-rooted. It's in this thread: http://forum.xda-developers.com/showthread.php?t=1739426
Either way, redownload and try flashing again. Then boot recovery and factory reset. (Will wipe internal sd)
If it still won't mount /data, try flashing Twrp recovery and factory reset. (Will not wipe internal sd unless you choose advanced > Format /data.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thank you so much! I ended up having to flash twrp but when I did what you said it booted just fine. Now the only question remaining is do I try to go back to cyanogenmod?
Since you have TWRP working, copy CM11 to your phone, boot to twrp, and flash CM11. If CM11 does't boot, try wiping data, cache, and dalvik.
Just remember, anytime you go between different based roms, such as TW and CM, you have to factory reset or it'll hang during boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I am trying to dowload photos to my computer, but it will not boot up to the appropriate stage in order to dowload photos. Phone seems to be stuck in a boot loop. it will start to boot up and then randomly shut off at different stages. Sometimes it gets to the at&t logo, while other times it may get to the samsung galaxy sIII image, etc. i tried going to the recovery mode, and not sure which option to choose, then an error at the bottom appears and saying invalid data error. Is there any way to fix this?
I am trying to recover old info/pics that are on the phone
thanks
Do you invalid data partition when you try to get into recovery mode?
Was the phone ever dropped?
audit13 said:
Do you invalid data partition when you try to get into recovery mode?
Was the phone ever dropped?
Click to expand...
Click to collapse
yes the phone has been dropped. sometimes the phone will start to boot up just by plugging in the battery. In recovery mode, i can see all the options like, wipe partions, update, etc . then the andorid guy is like on the floor sideways . under the andorid guy, it says E: failed to mount/data (invalid argument). can't mount/data (invalid argument) , can't mount /data/log./log_recovery.txxt
Sounds like the memory chip may be damaged. Once thing to try and get it going would be to try and flash TWRP, boot into TWRP, mount data, and try to recover your data. Can't think of any other way to try and recovery data.
Doing wipe data option doesnt delete files in /sdcard, only your apps. You can use odin to get your phone working, but using odin will usually delete everything.
One day after I charged my note 2 phone (SGH-T889), unplugged charger and started playing an app game for 5 mins. The phone suddenly crashed and began to restart nonstop but couldn't get passed the welcome screen animation. Eventually, it kept restarted and stuck in the logo screen.
I tried all the factory reset, wipe cache in recovery mode (holding the 3 buttons), taking out SD card, or all the basic stuff. The phone is not rooted at all. I even tried to install firmware through ADB (with digital signed software) but still failed to do so (even with some software to sign the zip file) because i got signature verification error. I also see failed to mount efs and system error. Also I wouldn't be able to get into recovery mode unless i hook up the usb, otherwise it will continuously fail to reboot in the logo screen.
I would like some guidance to reformat/ flash the whole phone with files linked or attached. Any official firmware version is fine for me. I only just learned ADB but I know nothing about odin. I don't want to root the phone if possible. Any help would be greatly appreciated. Thank you very much!
The stock ROM for your phone can be found here: http://www.sammobile.com/firmwares/database/SPH-L720T/
The stock ROM from sammobile is flashed via Odin as Odin is Samsung's official flashing method.
This the forum for the phone is here: http://forum.xda-developers.com/showthread.php?t=2621862
audit13 said:
The stock ROM for your phone can be found here: http://www.sammobile.com/firmwares/database/SPH-L720T/
The stock ROM from sammobile is flashed via Odin as Odin is Samsung's official flashing method.
This the forum for the phone is here: http://forum.xda-developers.com/showthread.php?t=2621862
Click to expand...
Click to collapse
I typed the wrong phone. I typed s4 instead of the note 2 model. Sorry.
Ok i flashed my note 2 with odin v3.11.2 with T889UVUCOH4_T889TMBCOH4_HOME.tar.mp5 in the AP tab in ordin. However, I get stuck in the green robot where there is a percentage bar after reboot. It gets stuck there then just reboot with the same thing happening. What do I do? Thanks.
I was using this odin tutorial http://odindownloader.com/tutorials/use-odin-downloader
aznsaiyan1029 said:
Ok i flashed my note 2 with odin v3.11.2 with T889UVUCOH4_T889TMBCOH4_HOME.tar.mp5 in the AP tab in ordin. However, I get stuck in the green robot where there is a percentage bar after reboot. It gets stuck there then just reboot with the same thing happening. What do I do? Thanks.
I was using this odin tutorial http://odindownloader.com/tutorials/use-odin-downloader
Click to expand...
Click to collapse
Ok Eventually it goes to recovery mode cwm.... Now i get even more E error. Pretty much fail to mount data, system, recover/ log, cache, etc..... even more errors T_T
Open Odin, uncheck everything except f reset time, flash rom, when you see the word reset in the status window, remove cable from the phone, remove battery, replace battery, boot into recovery, wipe, and reboot.
audit13 said:
Open Odin, uncheck everything except f reset time, flash rom, when you see the word reset in the status window, remove cable from the phone, remove battery, replace battery, boot into recovery, wipe, and reboot.
Click to expand...
Click to collapse
Doesn't work after i put back battery in. In fact, i had trouble going to cwm after that. When I try to go to cwm, it goes to the green robot for a split second and jump back to logo screem in loop.
What happens when you put the battery back in? Does it flash stock without errors? Cwm should not be in the phone after flashing stock.
aznsaiyan1029 said:
Doesn't work after i put back battery in. In fact, i had trouble going to cwm after that. When I try to go to cwm, it goes to the green robot for a split second and jump back to logo screem in loop.
Click to expand...
Click to collapse
and pretty much i have errors like these.
E:failed to mount /efs (No such file or directory)
E:failed to mount /system (No such file or directory)
# Manual mode #
-- Appling Multi-CSC...
E:failed to mount /system (No such file or directory)
E:Can't mount /system (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_recovery
E:failed to mount /data (No such file or directory)
E:Can't mount /data/log/recovery_log.txt
E:failed to mount /system (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
(a few more such errors)
audit13 said:
What happens when you put the battery back in? Does it flash stock without errors? Cwm should not be in the phone after flashing stock.
Click to expand...
Click to collapse
stuck in logo and when i try to wipe and factory reset liek u told me with holding vol up, power button, and home button, i go back to samsung logo loop
When booting to recovery, let the power button go as soon as the phone starts to boot but keep holding the home and volume up buttons.
audit13 said:
When booting to recovery, let the power button go as soon as the phone starts to boot but keep holding the home and volume up buttons.
Click to expand...
Click to collapse
I get only e: fail to mount efs and system ( didn't get fail to mount system the 1st time) now instead from the recovery screen. Wiped and got stuck in the sam sung start up animation, but then it becomes the same old logo reboot loop.
aznsaiyan1029 said:
I get only e: fail to mount efs and system ( didn't get fail to mount system the 1st time) now instead from the recovery screen. Wiped and got stuck in the sam sung start up animation, but then it becomes the same old logo reboot loop.
Click to expand...
Click to collapse
Ok this is what happened when I did the whole process again precisely as you told me. After I flashed with odin with (T889UVUCOH4_T889TMBCOH4_HOME.tar.md5), my phone is still in the download mode screen but everything is done downloading already. I unpluged usb, battery, micro SD card. When I try to reboot in recovery (I did your let go of the power button the moment the logo poped up), I am unable to do that, except I get reboot non stop and sometime I can see the green robot with the percentage bar screen. Eventually after multiple logo reboot loop, it just stuck at the screen and not do a thing.
Pretty much nothing I can do when I unplugged the phone from the USB, but when I plugged back the phone to the USB i can go to recovery mode somehow and I get all the e fail to mount errors for everything like i posted previously.
Also tried to install cwm through odin, but after odin said it pass and restarted with or without taking out the battery, I cant even go to recovery mode anymore....
omg my phone does the same thing except I cant flash at all keeps saying complete (write) operation failed. someone did resovle this please pm me or reply....
only thing that manages to connect with my phone but never complete is cwm4_fixed_for_cm7-odin.tar
I see the blue bar its complete but nothing ever happens
Sounds like there is a hardware problem with the phone. There could be a few causes but the failure to mount partitions means the memory may be damaged.
audit13 said:
Sounds like there is a hardware problem with the phone. There could be a few causes but the failure to mount partitions means the memory may be damaged.
Click to expand...
Click to collapse
it connects only to that? so what to do @audit13
I would look around to see if I could find a cheap note 2 with a smashed screen and working motherboard to switch the parts.
If you don't want to do that, maybe ask a cell shop for a repair estimate?
The phone is not worth too much so I would not spend a lot of money fixing it.
omg are you serious so thers nothing I can do? can I show you the pictures or something what is cwm4_fixed_for_cm-7-odin.tar? why is that only working ...im broke lol!!and a noob
Did you try flashing a stock ROM with a pit file?
audit13 said:
Did you try flashing a stock ROM with a pit file?
Click to expand...
Click to collapse
can u upload correct pit file cause all the pits file I have fails...but no I have not tried together let me try and upload pic