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
Related
Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
3vilrabbit said:
Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
Click to expand...
Click to collapse
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
CCallahan said:
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
Click to expand...
Click to collapse
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
3vilrabbit said:
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
Click to expand...
Click to collapse
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
CCallahan said:
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
Click to expand...
Click to collapse
I'm gonna bring it back to the shop and hopefully, if I put up a poker face if they ask me about rooting my device :angel:, they accept it and treat it with warranty
For some reason, I really don't know what I have being trying...my tablet miraculously is working again!
Thread can be closed...
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.
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'
I drop my phone one day and this nightmare started. When I power on my phone it then stuck on bootloop. I then start the phone in recovery mode and I got the error messages as below.
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /data (No such file or directory)
can't mount '/data' (No such file or directory)
E:failed to mount /data (No such file or directory)
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
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (No such file or directory)
Then I go on and try to flash with stock ROM using Odin. I am pretty sure I did the steps right as I follow online instruction and I flash my phone before. At the end my phone just stuck at bootup screen and when I try in recovery mode it shows the same error message as above.
Is anyone have any idea how to get this fix? I am suspected that my internal storage is corrupted but that's just my guess. Thanks in advanced!
*****I notice that when I start Odin it get through the "Get PIT for Mapping" step very quickly unlike what I saw on any other youtube video. Is it possible that my phone PIT is corrupted and need a new PIT file?
try downloading this and flashing via odin
http://forum.xda-developers.com/showthread.php?t=1975560
i just had a problem with trying to restore a stock rom using twrp and got stuck in a boot loop, even after wiping and installing another stock rom... then i flashed this one via odin and for some reason it worked and i'm back into my stock rom w/ root.
really hope this works for you & good luck.
NovaxxBite said:
try downloading this and flashing via odin
http://forum.xda-developers.com/showthread.php?t=1975560
i just had a problem with trying to restore a stock rom using twrp and got stuck in a boot loop, even after wiping and installing another stock rom... then i flashed this one via odin and for some reason it worked and i'm back into my stock rom w/ root.
really hope this works for you & good luck.
Click to expand...
Click to collapse
I did try flashing with Odin but it end up in a bootloop. I will look into the thread you provided and see if I miss something. At the meantime, I hope there will be another way to work around.
I search online and found someone having the similar issue to their phone but it is on HTC device.
http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
Therefore, I believe my internal storage partition is mess up or corrupted and need to repartition. In order to do that I believe I need the PIT file for my T-Mobile Note 2 is that right? If so can anyone provide me the PIT file for T-Mobile note 2? Or is there something I am missing still?
Anyone have any idea about this? Please I really need help on this.
jackgan said:
Anyone have any idea about this? Please I really need help on this.
Click to expand...
Click to collapse
What was the last official T-Mobile firmware that you had on your phone?
EdKeys said:
What was the last official T-Mobile firmware that you had on your phone?
Click to expand...
Click to collapse
I believe it is this version. I get the version detail from SamMobile.
Model SGH-T889
Model name GALAXY Note II
Country USA (T-Mobile)
Version Android 4.1.2
Changelist 935627
Build date Thu, 18 Apr 2013 14:07:55 +0000
Product code TMB
PDA T889UVBMD1
CSC T889TMBBMD1
I didn't update to Android 4.3 as some user said having battery problem with this version.
jackgan said:
I believe it is this version. I get the version detail from SamMobile.
Model SGH-T889
Model name GALAXY Note II
Country USA (T-Mobile)
Version Android 4.1.2
Changelist 935627
Build date Thu, 18 Apr 2013 14:07:55 +0000
Product code TMB
PDA T889UVBMD1
CSC T889TMBBMD1
I didn't update to Android 4.3 as some user said having battery problem with this version.
Click to expand...
Click to collapse
Try this with ODIN. If that doesn't work I have one more idea you can try.
http://www.mediafire.com/download/3aaao482ha133oq/root66_TMO_T889UVBMD1.tar.md5
EdKeys said:
Try this with ODIN. If that doesn't work I have one more idea you can try.
http://www.mediafire.com/download/3aaao482ha133oq/root66_TMO_T889UVBMD1.tar.md5
Click to expand...
Click to collapse
I tried with ODIN v3.07 and my phone went into boot loop. What's the other option you have?
EdKeys said:
Try this with ODIN. If that doesn't work I have one more idea you can try.
http://www.mediafire.com/download/3aaao482ha133oq/root66_TMO_T889UVBMD1.tar.md5
Click to expand...
Click to collapse
I haven't heard back from you for a while. I did tried your suggestion with ODIN but that doesn't work. Do you have any other option for me yet?
jackgan said:
I haven't heard back from you for a while. I did tried your suggestion with ODIN but that doesn't work. Do you have any other option for me yet?
Click to expand...
Click to collapse
Really sorry I missed your previous post. Have you tried to ODIN a custom recovery? Download this and flash with ODIN, then try to boot to recovery.
http://www.mediafire.com/download/05sczh30v7f96q8/Note2-CWM-6.0.4.3-SGH-T889.tar
If you can get to recovery, follow the instructions in my ROM thread for wiping. If you want to give my ROM a try, download the D edition. The wifi will work no matter what bootloader you currently have installed. You'll have to take out your sd card and get the ROM file on there with another device before you proceed.
http://forum.xda-developers.com/showthread.php?t=2631278
This is a T-mobile stock, rooted and debloated ROM. There is a link in the thread for the stock 4.3 modem to flash too in case you need that. Put that on your sd card too.
EdKeys said:
Really sorry I missed your previous post. Have you tried to ODIN a custom recovery? Download this and flash with ODIN, then try to boot to recovery.
http://www.mediafire.com/download/05sczh30v7f96q8/Note2-CWM-6.0.4.3-SGH-T889.tar
If you can get to recovery, follow the instructions in my ROM thread for wiping. If you want to give my ROM a try, download the D edition. The wifi will work no matter what bootloader you currently have installed. You'll have to take out your sd card and get the ROM file on there with another device before you proceed.
http://forum.xda-developers.com/showthread.php?t=2631278
This is a T-mobile stock, rooted and debloated ROM. There is a link in the thread for the stock 4.3 modem to flash too in case you need that. Put that on your sd card too.
Click to expand...
Click to collapse
I tried flash the CWM recovery with ODIN but my phone start bootlooping and cannot get into original recovery again. I believe my phone's motherboards is damage in some way that cause the internal storage fail to be detected. Do you think putting in a new motherboard will work? I search on ebay and it's like $80 for a new working motherboard.