I keep getting this error I think I might have wiped something I shouldn't have. I can still access SS(SafeStrap) but every install attempt ends with that error...please if anyone has advice on this or knows its bricked let me know so I can either switch to an old phone or go upgrade. I was having an issue with usb connection months ago while on the hyper drive rom so I decided to update to 21 from 20. When I updated the WiFi didn't work so I thought I'd go back to stock recovery, guessing the recovery file I had didn't work and now all I get is this mounting error. also system is not checked under mount through SS:crying:
Related
***************SOLVED*******************
Hey, hoping some android gurus can help me out here.
I had the latest version of Obsydian on my phone and have not had any issues. Yesterday, my battery on the phone died, and when it started up again I was getting forcecloses all over the place. Tried reinstalling the rom and go errors, tried a different rom and got errors. So I ODINed the Voodoo RFS fix, followed by stock+Voodoo-Froyo-T959-UVJL5.tar , and didn't get anywhere.
I thought there might have been something wrong with the data on the phone so i tried clearing and formatting everything through Clockwork recovery. Then I tried the partition SD Card through clockwork recovery. I assumed it was the EXT-SD it was formatting so i chose 128mb ext, 32 swap, and left the rest for fat32. However, I'm starting to think it might have been the internal SD card.
I tried ODINing back to stock stock using this guide: http://androidspin.com/2010/08/09/h...droidSPIN+|+Your+No.1+source+for+Android+news.)
I get the phone in ODIN and it flashes, no errors in ODIN, but when the phone leaves download mode and goes to installation it gives a few errors:
Code:
MBR Checksum Error
Movinand Checksum Confirmation Fail
Then it continues installing, and I get another error:
Code:
Wiping data
Formatting Data
[B]Data Wipe Fail[/B]
Formatting Cache
It still acts like it completely finishes the installation, reboots, I get the Tmobile boot and then Galaxy S, and then I get a black screen with all 4 of the lights/buttons on the bottom of the screen on. It can sit like this for 30 minutes, it doesn't do anything.
I still have access to download mode, and I still have access to recovery, however it's no longer ClockworkMod recovery, it's the stock recovery, and it seems to only work for a few moments before going to a triangle with an exclamation point and the android logo.
Any ideas on what I can do to make this phone functional again, or acceptable for a warranty return?
I appreciate any help.
Welcome to the club
Check out my post http://http://forum.xda-developers.com/showthread.php?t=887837
Post #3 it might help if it does let me know so we know for sure if it works
Yes welcome to the club!!! glad you could join us!
Anyways here is what I have learned/done, my only working rom currently is the eugene froyo, can use the phone and data BUT cant download anything or install anything. You can adb push apks into the rom though. Heres the link for it
Use Odin, pit=512, pda=eugene..tar Run this to get semi working rom
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
Once here I have access to my Sd card, this is where I placed the clockwork recovery on as an "update.zip" Link to this is posted below
http://forum.xda-developers.com/showthread.php?t=734164
Boot into recovery, note this will take you to stock recovery. REINSTALL update, may have to do this twice but itll get you to the Clockwork recovery....
After this I tried to install two different roms and both times I get some sort of data error, and installation aborted....hopefully this will help a few people
Yeah a bit more google searching for "vibrant mbr checksum" brought me to the same conclusion, that I needed to ODIN the eugene's froyo - it's flashing right now. Will see where that gets me.
It's my belief that using the SD partition in CWM is what caused the MBR issues and the Data Wipe Fail, as others said they messed with a partition in either CWM or something else prior to this happening
And that's a no go. It just reboots back into the stock recovery every time after odining it, with some new errors.
update media. please wait.
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:copu_dbdata_meda:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
Click to expand...
Click to collapse
I take it back - i did the wrong one apparently.
Had to use the files located on the link you sent, inside of the Eugene_2E_JK2_Froyo.zip file. Apparently there are a few different download files on the first post of that link. This one took longer than all the others I'd tried ODINing, about 5-6 minutes, compared to 2-3 for the others. I had also updated my Odin3 to v1.7, from the v1.3 I was using before.
When it booted up, it gave me an issue with my external SD card, said it was formatted incorrectly, so i formatted it from the phone - it says I have 13gb memory and 1.86 on the ext-SD.
Was able to download and install ROM manager from the market. Attempting to install Nero v3 now.
*** SOLVED ***
I've succesfully installed a rom other than Eugene's froyo, and did not receive any installation errors! Got Nero V3 up and running, very happy.
Note that the MBR checksum error still appeared but did not affect installation at all. Thanks everyone for their help - hopefully this helps the others.
Hello all,
I'm having a problem getting my phone to boot up when I tried flashing back to stock with Odin 1.37 using .512 pit and SGH-T959UVKA6. I have done it successfully in the past, but the mistake i made this go round is I accidentally checked "re-partition" and it gets stuck on the following error in Android System Recovery 3e:
update media, please wait
E: Can't mount /dev/block/st110
(invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet. Please use UI menu for format and reboot actions.
copy default media content failed.
Can anyone advise if they have fixed this error in the past? I really need to get this phone back to TMO for under warranty repair and am kind of scared of being screwed here.
Bigbass12 said:
Hello all,
I'm having a problem getting my phone to boot up when I tried flashing back to stock with Odin 1.37 using .512 pit and SGH-T959UVKA6. I have done it successfully in the past, but the mistake i made this go round is I accidentally checked "re-partition" and it gets stuck on the following error in Android System Recovery 3e:
update media, please wait
E: Can't mount /dev/block/st110
(invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet. Please use UI menu for format and reboot actions.
copy default media content failed.
Can anyone advise if they have fixed this error in the past? I really need to get this phone back to TMO for under warranty repair and am kind of scared of being screwed here.
Click to expand...
Click to collapse
Nothing to big happened. I check repartition every time I never have any problems.
If it shows u anything ur good.
Boot into download mode and odin back again.
Sent from my SGH-T959 using XDA App
Hmm....
I would agree with you except the following:
1. Tried to flash same without checking repartition...failed x3.
2. tried to flash to JI6 with same pit file...failed.
3. tried to change pit file to 513 and tried again with KA6...failed.
4. tried to go back to 512 and JI6...failed.
I have tried several times variants of all those combos...all failed.
Per the following post I am trying this fix:
http://forum.xda-developers.com/showthread.php?t=734475
hopefully going back to JFD will fix this....
****NOTE: When I say "Failed" I mean I get the same message that I got when I first received the error.....
Success
Wow the post really did it! Gotta love XDA...quick someone teach me how to thank around here...lol
I have a GT-I9100M from Bell in Canada. My phone is broke and I've spent the last 24 hours trying to fix it with no avail
I was running the stock ICS rom from Bell. I rooted the phone and removed all the Bell bloatware and that was it.
Yesterday I came across a Rom that had the S3 version of Touchwiz so I decided to try it out - Salman ICS ROM for Galaxy S2 i9100! [TouchWiz UX][S Voice][GS3 ROM]
The rom installed perfectly and when it restarted, it stopped at the Samsung Galaxy boot screen. I attempted to go into recovery mode and it couldn't.
It would go into download mode. So I tried to flash the stock bell ICS rom - I9100MUGLD3_I9100MBMCLD3_BMC_www.samsdroid.com. It flashed with no issues but when it rebooted - back to the boot screen I go.
I flashed a CF kernal so that I could get into CWM and attempt to wipe it. It kept hanging on formatting /data.
I came across this guide - http://forum.xda-developers.com/showthread.php?t=1449771 and followed the steps and got no where.
Is my phone completely dead and if it is not - how do I get it back in working condition?
Help!!:crying:
When you flashed Bell's stock ROM from the guide thread, could you reach the recovery mode screen? I had the same problem and I simply did a factory reset after I flashed the stock ROM.
After I tried to flash my stock firmware with ODIN
I get stuck at Android System Recovery <3e>
and get these errors:
E: failed to mount /cache (no such file or directory)
E: Cant mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Cant open /cache/recovery/recovery_kernel_log
E:failed to mount /efs (No such file or Directory)
E:failed to mount /cache (no such file or directory)
E:cant mount /cache/recovery log
E:cant open /cache/recovery log
and as you can imagine the list goes on..... and when I hit reboot system now - it just freezes at the Samsung i9100 boot screen.
AAARRGGG
I did some more reading and someone suggested trying a Frankenstein rom KK5 as it does a complete wipe of the data partition on the phone. When I tried this, it does stuck on datafs.
I believe that my phone is broken
kmacsouris said:
I did some more reading and someone suggested trying a Frankenstein rom KK5 as it does a complete wipe of the data partition on the phone. When I tried this, it does stuck on datafs.
I believe that my phone is broken
Click to expand...
Click to collapse
looks like you have hit the eMMC brick, you could try to flash a pit file, and flashing it with repartition activated... This its the only thing you could try, before sending it off for repair
Best regards
Sendt fra min GT-I9300 med Tapatalk2
try to find a Stock ICS which does a full wipe. Usually the first edition of stock ICS
of each region does that.
Dear friend i understand your fear and i wan t to share with you my research, my trouble came for downgrading from ics to GB and now i have the red letters with the e cant mount **** , so i found that installing this rom (XXKH3) with the Phone Bootloader Update filed checked could fix it.
The original post is in spanish so if you need it it is here.
Scroll down until ERROR: E: Can't mount cache
http://www.taringa.net/posts/celulares/14623579/samsung-galaxy-S2---downgrade-ICS-a-Gingerbread.html
But on this post the link to XXKH3 is broken so i found this other link on english with the link working
http://www.theandroidsoul.com/how-to-install-xxkh3-on-samsung-galaxy-s-2-ii-i9100/
I'll try this thing in a couple hours when the download finish due to my 1.5 mb internet and i'll let you know any new,
Good luck
I recently upgraded phones and I'm looking to sell my old gs3. But I had put a costom Rom on it awhile back but during the process at one point I ran into the same problem with the logo screen but I fixed it (I completely forget how) and that was that untill recently when I attempted to return the phone to stock by updating it to 4.3 with kies and that was fine it wasn't until I ran a master reboot that the logo problem resurfaced at that point I tryed to use Odin to flash stock firmware which after doing further research was a terrible idea to do with 4.3 but that's where I'm at my phone does not boot up past the Samsung logo luckily I can still access the dowload mode. I am thinking that I'm going to try flashing a root66 stock 4.3 is that a good idea. Any help would be much appreciated, thank you
Update:I tryed flashing the root 66. I did the newest 4.3 tmobile download i could find which is what fixed it when this happened about a year ago but this time it did nothing. Also when i boot into recovery mode at the bottom under where it says Seccessfully applied multi-CSC it says in red lettering
E:failed to mount /data (Invalid argumen
t)
can't mount '/data'(invalid argument)
E:failed to mount /data (Invalid argumen
t)
E:Can't mount /data/log/recovery_log.txt
imfukked said:
I recently upgraded phones and I'm looking to sell my old gs3. But I had put a costom Rom on it awhile back but during the process at one point I ran into the same problem with the logo screen but I fixed it (I completely forget how) and that was that untill recently when I attempted to return the phone to stock by updating it to 4.3 with kies and that was fine it wasn't until I ran a master reboot that the logo problem resurfaced at that point I tryed to use Odin to flash stock firmware which after doing further research was a terrible idea to do with 4.3 but that's where I'm at my phone does not boot up past the Samsung logo luckily I can still access the dowload mode. I am thinking that I'm going to try flashing a root66 stock 4.3 is that a good idea. Any help would be much appreciated, thank you
Update:I tryed flashing the root 66. I did the newest 4.3 tmobile download i could find which is what fixed it when this happened about a year ago but this time it did nothing. Also when i boot into recovery mode at the bottom under where it says Seccessfully applied multi-CSC it says in red lettering
E:failed to mount /data (Invalid argumen
t)
can't mount '/data'(invalid argument)
E:failed to mount /data (Invalid argumen
t)
E:Can't mount /data/log/recovery_log.txt
Click to expand...
Click to collapse
Hmm . Did you have the device encrypted or anything along those lines?
I'm good dude. I figured it out.
imfukked said:
I'm good dude. I figured it out.
Click to expand...
Click to collapse
Good deal. Care to share in case others run across this issue?
stuck booting at logo screen
hello, my s3 did the same thing keis wouldnt even recognize my phone after rooting and trying to go back to stock rom, found when installing using odin, i installed tar file in boot img i had to download a zip unpack it and istalled kernal tar and bingo solved my problem, hope it helped..
Hey guys,
Wondering if anyone knows how to fix this?
(Failed to mount oem invalid argument) This popped up a while ago after flashing something I shouldn't have in twrp. It doesn't go away, even after flashing different versions. Everything still functions fine, ROMs and Gapps and Magisk still flash no problems. Should I just ignore this or is it something I should address?