Related
Hi Guys.
I have a Galaxy S on bell's network, running JPK.
I looked at my phone last night and there was an orange "!" caution icon in the notification area. Said something about the internal sdcard not unmounting properly. So I rebooted the phone and now its booting to a black screen.
I have Ryan's OCLF from the market installed. I'm not sure if this is what is causing the problem (may be confused about ext2?)
I can boot into recovery, but no access to su from there. I can get into download mode. I tried re-flashing JPK, which flashed ok but I still have the same problem.
The error I'm seeing in recovery is:
E:Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
I tried flash sdcard from recovery but didnt work.
Can anyone help me get my phone back? I heard flashing stock 2.1 Bell firmware may fix my issue, but I don't have that firmware. Please help!
This should help.
http://forum.xda-developers.com/showthread.php?t=739091
this will work for you
this is the erro that comes up
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
this is the way you fix the problem.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine
You might be better off sticking to the i9000 forums in the future, given that your Bell Vibrant resembles our T-Mobile Vibrant in name only. It's far more similar to the international i9000.
alcangel64, will this work with the GT-i9000? I also see the caution about don't do it if you've flashed JP3.. should I ignore that warning?
alcangel64 said:
this will work for you
this is the erro that comes up
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
this is the way you fix the problem.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine
Click to expand...
Click to collapse
while in recovery mode, if you have adb installed u can adb reboot download and it'll take u to download mode. Then you'll be able to restore through odin. But I warn u, if it has something to do with the filesystem (ext2, ext4) ur in for a long ride. Other day I spent all day trying to get my phone to boot after flashing like 20+ times in odin due to an error in my filesystem
I think the title is bit misleading. It was likely not JPK that broke but rather the EXT2 loopback created by the lag fix. You might consider changing the title of the thread to something else.
If you get it working again, I wouldn't suggest applying the OCLF again. When the internal SD mounted improperly, it was likely corrupted. This can happen at anytime since the EXT2 is not journaled like Samsung's RFS or EXT4. You might be able to fix the file system corruption if you can run fsck on it through ADB.
Selecting the repartition option in ODIN may get you past any file corruption issues with the SD but it will wipe your internal SD. So, just restore from backup.
I agree. I think it was the lagfix, ultimately. I think the problem now is that I can't reflash because none of these PDA firmwares know anything about ext2.
Are there any releases with ext2 enabled right in the firmware? That might let me re-mount /sdcard at least, or at least remove the symbolic links?
epakrat75 said:
I think the title is bit misleading. It was likely not JPK that broke but rather the EXT2 loopback created by the lag fix. You might consider changing the title of the thread to something else.
If you get it working again, I wouldn't suggest applying the OCLF again. When the internal SD mounted improperly, it was likely corrupted. This can happen at anytime since the EXT2 is not journaled like Samsung's RFS or EXT4. You might be able to fix the file system corruption if you can run fsck on it through ADB.
Selecting the repartition option in ODIN may get you past any file corruption issues with the SD but it will wipe your internal SD. So, just restore from backup.
Click to expand...
Click to collapse
What did you do to fix it? Problem is I can't su in recovery mode. If I could I could at least remove the ext2 symbolic links and continue.
jroid said:
while in recovery mode, if you have adb installed u can adb reboot download and it'll take u to download mode. Then you'll be able to restore through odin. But I warn u, if it has something to do with the filesystem (ext2, ext4) ur in for a long ride. Other day I spent all day trying to get my phone to boot after flashing like 20+ times in odin due to an error in my filesystem
Click to expand...
Click to collapse
moophone said:
Are there any releases with ext2 enabled right in the firmware? That might let me re-mount /sdcard at least, or at least remove the symbolic links?
Click to expand...
Click to collapse
The stock 2.1 / 2.2 kernel should already support EXT2 however it won't mount a corrupted / damaged partition. You should try flashing back to 2.1 with the repartition option checked through ODIN. Once the internal SD is formatted by the repartition, it should then finally mount. It will also return everything back to RFS.
What kernel exactly? I tried flashing i9000_Kernel.tar, and then I9000XXJPH_KERNEL.tar from JPH. I tried JPC. I don't have a stock Bell kernel but none of those did anything.
Could you refer me to a specific kernel that will restore the /sdcard partition?
Thanks,
Greg
epakrat75 said:
The stock 2.1 / 2.2 kernel should already support EXT2 however it won't mount a corrupted / damaged partition. You should try flashing back to 2.1 with the repartition option checked through ODIN. Once the internal SD is formatted by the repartition, it should then finally mount. It will also return everything back to RFS.
Click to expand...
Click to collapse
moophone said:
What kernel exactly? I tried flashing i9000_Kernel.tar, and then I9000XXJPH_KERNEL.tar from JPH. I tried JPC. I don't have a stock Bell kernel but none of those did anything.
Could you refer me to a specific kernel that will restore the /sdcard partition?
Thanks,
Greg
Click to expand...
Click to collapse
After about 30 tries I was able to boot my phone with UGJH2. The funy part is for it to work and boot OK .. I have to leave my external SD card in it. It will error saying that it can't mount it once booted and both my internal 16G sd or my external 8G sd can't be mounted. All the rest of the phone works perfectly. If there was just a way for format or repartition the internal SD card from in the OS or ADB it would be fine. At least my phone now works until I can get a replacement phone from bell.
I tried to remove the external SDcard and the phone crashed. If I leave it in there , it works fine ??
Having this problem after flashing jp6 on my Bell i9000m. It worked great for like 2 days but suddenly it stopped working and i can't boot anymore. I did apply a lagfix but i removed it soon after because i did not see any speed improvements. Downloading the roms suggested in this thread right now... hope it works
Flashing again doesn't help*
I've flashed back to stock rom and used wipe factory and cache, but it still doesn't fix the issue.
I've read something about using adb to fix it, however adb doesn't even reconize my damn phone. Odin does on the other hand.
If adb reconize your phone, you should be able to push some files,and follow some other procedures to fix the internal sd card then flash it again with odin.
The other solution is changing your internal sd card, don't know how though people have sent back their device to their carrier or went to phone shop, i heard it costs one guy around 80$ to change it.
Soooooooo ... here's what happened.
I was trying to condense my internal and external sdcards from my computer. Once i backed everything up, I formatted one of the drives through windows. Problem is, it COMPLETELY formatted it, including the partition for app data. The phone booted, but with 0Mb for apps, and would freeze up and give me the black screen with lit buttons.
Then I go into DL mode, flash the stock firmware and during the reboot, it gets stuck in recovery with this error:
-- Movi_check Start...!!
checksum confirmation need check_sum[1301305579]
MBR_ChkSum in header : 5.0
MBR checksum : E9A2186CA7912EE54F5EFCB478D44960
MBR Checksum Error
Movinand Checksum Confirmation Fail
lfs pass open fail
--movi_checking undone!...
update media. please wait
E: Can't mount /dev/block/stl10
(Invalid argument)
E: copy_dbdata_media:Can't mount DBDATA:
copy default media content failed
I can Get into clockwork, but it won't flash bionix1.7, I get a line 81 error. I can't mount the sd while in recovery any more. I can't get into DL mode again. whenever I try to reboot, it throws me into recovery with that error ... I'm completely lost right now and any help would be GREATLY appreciated.
dav3wash said:
Soooooooo ... here's what happened.
I was trying to condense my internal and external sdcards from my computer. Once i backed everything up, I formatted one of the drives through windows. Problem is, it COMPLETELY formatted it, including the partition for app data. The phone booted, but with 0Mb for apps, and would freeze up and give me the black screen with lit buttons.
Then I go into DL mode, flash the stock firmware and during the reboot, it gets stuck in recovery with this error:
-- Movi_check Start...!!
checksum confirmation need check_sum[1301305579]
MBR_ChkSum in header : 5.0
MBR checksum : E9A2186CA7912EE54F5EFCB478D44960
MBR Checksum Error
Movinand Checksum Confirmation Fail
lfs pass open fail
--movi_checking undone!...
update media. please wait
E: Can't mount /dev/block/stl10
(Invalid argument)
E: copy_dbdata_media:Can't mount DBDATA:
copy default media content failed
I can Get into clockwork, but it won't flash bionix1.7, I get a line 81 error. I can't mount the sd while in recovery any more. I can't get into DL mode again. whenever I try to reboot, it throws me into recovery with that error ... I'm completely lost right now and any help would be GREATLY appreciated.
Click to expand...
Click to collapse
try booting in dl mode from your pc. Install the android SDK and USB drivers for samsung. The SDK can be found by googling and search the forum for the USB drivers. They in the command line type "<PathToSDK>\tools\adb.exe reboot download. That should get you into download mode. Then flash the stock image and make sure the "Re-Partition" is checked.
I think this should work.
MonkySlap said:
try booting in dl mode from your pc. Install the android SDK and USB drivers for samsung. The SDK can be found by googling and search the forum for the USB drivers. They in the command line type "<PathToSDK>\tools\adb.exe reboot download. That should get you into download mode. Then flash the stock image and make sure the "Re-Partition" is checked.
I think this should work.
Click to expand...
Click to collapse
tried that, it didn't work either. It still takes me into recovery even though i put adb reboot download. I think I'm just going to have Asurion replace it again
Boot into Clockwork recovery and post the results of:
adb shell mount
silow said:
Boot into Clockwork recovery and post the results of:
adb shell mount
Click to expand...
Click to collapse
Once i go into clockwork, my computer no longer recognizes clockwork.
Idk if its the same thing, but here's what it says outside of clockwork
I would try and reformat your partitions through clockwork. I dont know if you might of reformated the partions NTFS or what.
MonkySlap said:
I would try and reformat your partitions through clockwork. I dont know if you might of reformated the partions NTFS or what.
Click to expand...
Click to collapse
Looks like this at least let me get into dl mode ... flashing stock now, we'll see what happens
Good to hear. I bet when you reformated in windows, it formated the internal sdcard as NTFS which Android cant read.
Just to put it out there if you press the menu button from recovery i believe its the same as DL mode .
got it!
First off, thanks for all the tips guys.
I had to flash Eugene's Froyo that doesnt brick with re-partition checked (no other rom would work) which brought me back, and then i downgraded from there.
Just in case anybody else gets that!
did it get rid of the mbr checksum error? I still have it but can flash whatever.
My phone did the whole failed encryption bull shhhh. Figured that the issue is either located in the Vibrants DATA Partition or the SDCARD Partition (internal memory). I have attempted to ODIN back to stock but when it goes through the wipe data factory reset stage at the very end, the Data Partition fails.
I'd like to know of a way to manually get into the phone and format this partition clean. Then maybe odin will work.
Can it be done with ADB?
I got an old REcovery put back on trying things out from step one when I first got the phone a year ago.
Boot and Data partitions wont format. Boot just fails and I doubt thats where the issue is. But Data gives me this error:
Formatting DATA:...
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Done.
So anyone got any pearls of wisdom here? Or is this thing truly bricked?
nFiniti said:
My phone did the whole failed encryption bull shhhh. Figured that the issue is either located in the Vibrants DATA Partition or the SDCARD Partition (internal memory). I have attempted to ODIN back to stock but when it goes through the wipe data factory reset stage at the very end, the Data Partition fails.
I'd like to know of a way to manually get into the phone and format this partition clean. Then maybe odin will work.
Can it be done with ADB?
I got an old REcovery put back on trying things out from step one when I first got the phone a year ago.
Boot and Data partitions wont format. Boot just fails and I doubt thats where the issue is. But Data gives me this error:
Formatting DATA:...
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Done.
So anyone got any pearls of wisdom here? Or is this thing truly bricked?
Click to expand...
Click to collapse
Read this, http://forum.xda-developers.com/showthread.php?t=1580902 . There is no known fix just a work around, good luck. That bug made me go back to GB ROMS, it's ICS related unfortunately.
Sent from my T959 using XDA Premium App
iTz KeeFy is correct. There is no "fix" for the ICS bug. Only a work around that requires the use of your external sdcard.
Odin >> Heimdall >> JTAG will not fix it.
Hey guys, wondering if you could help me. I'm running Jelly Blast V-3.5, with Rafaels Kernel 2.6.35-7 on my S5380i. I've been trying to increase the internal storage on my device by partitioning my 32gb card in CWM with a 1gb ext. I've tried every solution I've found on this forum but I simply cannot get it to mount. Link2sd yields 'invalid argument' no matter where I point it, and when trying to format/mount the ext. in CWM it just says 'apps 2 sd partition not found'.
Here's a list of the things I've tried which have failed to solve this:
Partitioning in minitool, with various sizes and exts, and setting the partition as active.
Flashing conrod script, doesnt seem to be effective.
Script to mount sd-ext at boot, followed iamareebjamal's guide found here http://forum.xda-developers.com/showthread.php?t=1971689
S2E
Mount2SD
I'm completely at a loss, and with the internal storage of the S5380i being what it is, it would be great if anyone could offer me any advice.
Thanks!
do one thing , I'm recovery check if sd-ext is mounted
it used to happen to me that when I flashed new roms I had to mount sd-ext from mounts and storage
so mount it then reboot your phone
go to link2sd and create mount script as ext4
if problem persists , go in storage info of link2sd so see if the partition is mounted
if not you will have to enable auto mount at boot ( if option present in rom ) or mount using terminal emulator
Sent from my GT-S5670 using xda premium
soham jambhekar said:
do one thing , I'm recovery check if sd-ext is mounted
it used to happen to me that when I flashed new roms I had to mount sd-ext from mounts and storage
so mount it then reboot your phone
go to link2sd and create mount script as ext4
if problem persists , go in storage info of link2sd so see if the partition is mounted
if not you will have to enable auto mount at boot ( if option present in rom ) or mount using terminal emulator
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Thanks for responding.
Attempted to mount in CWM but just receive an error. It's as if the partition isn't there at all. Re-partioned the card but still, no luck.
My rom doesn't have the auto mount at boot option, so it looks I'll have to mount with terminal emulator. Could you run me through the process, or point me towards a guide? Cheers
what error did you get in cwm while mounting ?
yry this line in terminal
mount -o rw /dev/block/
mmcblk0p2 /sd-ext
also is mount2sd file present in your /etc /init.d folder ?
Sent from my GT-S5670 using xda premium
The error in CWM when attempting to mount is: 'Error mounting /sd-ext!'
'mount -o rw /dev/block/mmcblk0p2 /sd-ext' in Terminal Emulator yields the following line: 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
The mount2sd file is not currently present in my init.d folder as I restored my phone from a backup, though when it has been there, the error in CWM is still the same.
The only difference I have noticed is that when partitioning with MiniTool, Link2SD will say that the partition is not mounted, but when partitioning with CWM it will say that the partition is not found.
galaimo said:
The error in CWM when attempting to mount is: 'Error mounting /sd-ext!'
'mount -o rw /dev/block/mmcblk0p2 /sd-ext' in Terminal Emulator yields the following line: 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
The mount2sd file is not currently present in my init.d folder as I restored my phone from a backup, though when it has been there, the error in CWM is still the same.
The only difference I have noticed is that when partitioning with MiniTool, Link2SD will say that the partition is not mounted, but when partitioning with CWM it will say that the partition is not found.
Click to expand...
Click to collapse
Did you format ext2 in the secind partition? Normally when you format with cwm, first partition is fat32 and the second partition is ext2. Try to format all available space to 1 partition and using cwm format the card to two part. May be partitioning before makes cwm recognize the wrong part and gives error.
:: Today is the first day of what's left of your life. ::
ChelebiTech said:
Did you format ext2 in the secind partition? Normally when you format with cwm, first partition is fat32 and the second partition is ext2. Try to format all available space to 1 partition and using cwm format the card to two part. May be partitioning before makes cwm recognize the wrong part and gives error.
Click to expand...
Click to collapse
Ensured all the space on card was unallocated and partitioned in CWM recovery.
Attempted to mount /sd-ext again and still receive the following error: 'Error mounting sd-ext!'
Attempted to format /sd-ext and receive the following error: 'No apps2sd partition found. Skipping format of /sd-ext'
Tried so many different ways/combinations of partitions now. Do you think it could be a kernel or rom issue?
galaimo said:
Ensured all the space on card was unallocated and partitioned in CWM recovery.
Attempted to mount /sd-ext again and still receive the following error: 'Error mounting sd-ext!'
Attempted to format /sd-ext and receive the following error: 'No apps2sd partition found. Skipping format of /sd-ext'
Tried so many different ways/combinations of partitions now. Do you think it could be a kernel or rom issue?
Click to expand...
Click to collapse
Make sure you have backed up all your files in your sdcard they will all be deleted and recreated with two partition.
In CWM enter Advanced --> use Partition SD Card
Set your second (ext2/3/4) partition size then set swap to zero (0).
ChelebiTech said:
Make sure you have backed up all your files in your sdcard they will all be deleted and recreated with two partition.
In CWM enter Advanced --> use Partition SD Card
Set your second (ext2/3/4) partition size then set swap to zero (0).
Click to expand...
Click to collapse
This is exactly what I've done, countless times. It simply will not mount. Really struggling to understand this problem.
galaimo said:
This is exactly what I've done, countless times. It simply will not mount. Really struggling to understand this problem.
Click to expand...
Click to collapse
Using a card reader enter your sd card to a computer and test if card has a problem or partitions are correctly created. If your answer is yes you may have a misconfig on your phone. Make sure u have the latest busybox available, have rooted your phone correctly, vs...
Or create your partitions in computer and try...
Ps: I created my partition in Stock Rom. So it must NOT depends on kernel or rom...
ChelebiTech said:
Using a card reader enter your sd card to a computer and test if card has a problem or partitions are correctly created. If your answer is yes you may have a misconfig on your phone. Make sure u have the latest busybox available, have rooted your phone correctly, vs...
Or create your partitions in computer and try...
Ps: I created my partition in Stock Rom. So it must NOT depends on kernel or rom...
Click to expand...
Click to collapse
Partitioned with CWM again. Plugged in to laptop and in MiniTool and this is the result:
galaimo said:
Partitioned with CWM again. Plugged in to laptop and in MiniTool and this is the result:
Click to expand...
Click to collapse
That unallocated space is your problem. Try to create an ext2/3 partion with mini tool. And if minitool gives error than you probably have a defected sd.
And one more suggestion try the cwm in rafaels kernel thread.
Edit: Sorry for cwm use http://forum.xda-developers.com/showthread.php?p=23715776
:: Today is the first day of what's left of your life. ::
ChelebiTech said:
That unallocated space is your problem. Try to create an ext2/3 partion with mini tool. And if minitool gives error than you probably have a defected sd.
And one more suggestion try the cwm in rafaels kernel thread.
Edit: Sorry for cwm use http://forum.xda-developers.com/showthread.php?p=23715776
Click to expand...
Click to collapse
Thanks for taking the time to talk me through this.
Turns out my SD card is defective, swapped for another card and I've now increased my internal storage!
I'll be sending the other one back.
Thank you again for your time :good:
ChelebiTech said:
That unallocated space is your problem. Try to create an ext2/3 partion with mini tool. And if minitool gives error than you probably have a defected sd.
And one more suggestion try the cwm in rafaels kernel thread.
Edit: Sorry for cwm use http://forum.xda-developers.com/showthread.php?p=23715776
:: Today is the first day of what's left of your life. ::
Click to expand...
Click to collapse
Thanks for the link! seems like my CWM wasn't detecting sd-ext.. this fixed!! feared my sd card was ruined.. really thanks a lot!
Hi there!
I have been using the latest CM11 nightly for a while and decided to go for Link2SD, but I simply cannot mount my sd-ext partition from recovery. I have partitioned my SD-card of size 16GB with MiniTool Partition Wizard, and created an EXT3 partition of size 2GB. The partitions appear perfectly on the software, but whenever I try to mount /sd-ext from recovery, I get an error of "Error mounting /sd-ext!". Could anyone please help me out here? Quite a n00b here about sd-ext really.
I never tried mounting the sd-ext from recovery, but it works just fine after boot. What would you do with mounted sd-ext in recovery?
Well, I want to use Link2SD and have been always receiving an error message while creating the mount script, which goes something like:
"Mount script error
Mount script cannot be created.
mount: Invalid argument"
Also, upon looking into the Storage info, I find that SD Card 2nd Part. is not mounted. This is why I'm trying to mount my sd-ext from the CWM recovery, so that I can eradicate the error. Am I going in the wrong track?
I don't know, ext partition should work out of the box. What I did was partition sd card, boot, install link2sd, create mount script, reboot once again, done.
The only time link2sd won't create mount script for me is when the internal memory is full. Maybe your internal memory is full?
Not really, my internal memory is at least 50% free. Either way, I'll try reflashing the kernel and make a fresh install, and see if the problem persists. Thanks for responding and helping regardless!
psychoticdemon said:
Not really, my internal memory is at least 50% free. Either way, I'll try reflashing the kernel and make a fresh install, and see if the problem persists. Thanks for responding and helping regardless!
Click to expand...
Click to collapse
u say u created an ext3 partition?? so u must hav selected the same when creating mount scripts in link2sd right?? then it shud work...
it if did not work try with ext4 partition as i am using the same with ext4 partition for a year now...
psychoticdemon said:
Well, I want to use Link2SD and have been always receiving an error message while creating the mount script, which goes something like:
"Mount script error
Mount script cannot be created.
mount: Invalid argument"
Also, upon looking into the Storage info, I find that SD Card 2nd Part. is not mounted. This is why I'm trying to mount my sd-ext from the CWM recovery, so that I can eradicate the error. Am I going in the wrong track?
Click to expand...
Click to collapse
Reboot then, dude. recreate mount script again, reboot, let see what happen next
Alright, I finally got Link2SD working and apparently, as it turned out, it's more comfortable with ext4 than ext3. Creating a mount script always failed when I tried with ext3, but with ext4, it worked like a charm. Anyway, thanks for all the advice, guys. Gonna tag this as solved right away.