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.
ok i flashed with odin back to stock but now my internal storage is at 0 ..any ideas?
{FIXED}
This is what i did
1. Flash Odin Stock http://forum.xda-developers.com/showthread.php?t=782204
2. Root Phone Via One click root http://forum.androidcentral.com/fasc...-how-root.html
3. Remove Voodoo & Replace Files http://forum.xda-developers.com/showthread.php?t=804784
4. After step 3 do not restart just yet While in clockwork after you install Stock.zip go to "WIPE DATA" then "Restart"
It should work now. it did for me... *THANK THE HEAVENS* and the devs on here. i didnt have to do that long ass process that was stated earlier even though it was much
Did you wipe and format your sd card. Cause that's where the voodoo file is located. Delete and redo Odin.
also if u flashed with Odin back to stock u must do the disable lagfix. First off, I take it u flashed voodoo, before u flashed back to stock with Odin did u disable the lagfix?
Sent from my SCH-I500 using XDA App
i thought i wiped it... so if i didnt how do i get rid of it..i tried the adb push but it kept telling me premission denied even though i could get into adb shell
HELP*** lol
Install v0.2, it fixes the internal storage problem.
OK here is what I would do. I would do the root explorer thing and add the folder disable_lagfix in sdcard>voodoo. Add the folder there and turn off the phone, then power up the phone. The phone will acknowledge the disable lagfix you installed. Give it some time . Then once the phone reboots, check your internal memory.
i cant download and install anything because of the damn 0 internal
can you get into your sd card at all?
i reformated it now i put the update.zip back on the root for clock work but now i cant boot into clockwork via normal recovery using update.zip gives me a failed signature error
oik i see odin has a option for re partition next to auto boot..should i do that?
I'm having the same problems as you. Hope someone can figure this out. I went thru with odin restore after voodoo messed things up now I am stuck.
geez i keep gettin a E: cant mount /dv/block/mmcblk0p1 (invalid argument)
Idk what the hell you are talking about. Take out your sd card completely. Put another sd card in there format it to your phone. Do Odin on your phone. Odin clockwork recovery. Apply update DI01. Then root it. Now put back your 16gb sd, format it first before hand. Then flash voodoo.
dialect129 said:
geez i keep gettin a E: cant mount /dv/block/mmcblk0p1 (invalid argument)
Click to expand...
Click to collapse
Your mbr doesn't seem to be back to stock. You can try getting into the OS and doing a privacy wipe, but if your mbr is still the voodoo mbr it won't work.
In that case you should basically try re-installing voodoo like new, then walk through the uninstall process again. You need to remove the /sdcard/Voodoo/disable_lagfix file in order to re-install voodoo.
If you get this error in stock recovery each time, the problem is still there.
namebrandon said:
Your mbr doesn't seem to be back to stock. You can try getting into the OS and doing a privacy wipe, but if your mbr is still the voodoo mbr it won't work.
In that case you should basically try re-installing voodoo like new, then walk through the uninstall process again. You need to remove the /sdcard/Voodoo/disable_lagfix file in order to re-install voodoo.
If you get this error in stock recovery each time, the problem is still there.
Click to expand...
Click to collapse
Well right now update.zip fails so we can't get back to clockwork to try to re-install voodoo
yeah i've gone back to stock numerous times i dont have voodoo onthe phoen anymore no way it could be wiped phone wiped cache wipe sd card but still no goo even put a new sd card in
Does anyone know if it is safe to try to restore thru odin with phone boot loader update checked. Just was wondering if that might solve it.
nemesis2all said:
Well right now update.zip fails so we can't get back to clockwork to try to re-install voodoo
Click to expand...
Click to collapse
Have you tried going into cwm recovery manually?
meaning how? i've done cm2recovery.tar through odin but still no luck
Hi all
I was being foolish. was using the worng PIT file and trying to go straight to JI6. What fixed it was - using the right PIT and the JFD.tar for the PDA.
Mods - if this thread needs to be deleted, please do so.
Thanks.
Hi all
I think I am into some big trouble with my vibrant. I had Bionix-v installed and was very happy, then I messed around with Dragon kernel 2.8, then Dragon kernel 3.1.2, followed by DOW 14.
wanted to get back to bionix-v after a fresh install, so decided to ODIN back to stock. Then ran into trouble with ODIN - wont assign a com. Unistalled the samsung drivers and reinstalled, did not work. Tried a different laptop and it worked eventually.
ODINed back to JI6, (Re-partition was selected by default and I managed to overlook it ) but then got error:
E:Can't mount /dev/block/st110(File exists)
Error mounting /datadata/!
Skipping format...
E:Can't mount /dev/block/st110(File exists)
Can't mount /datadata/!
Tried to do restore from an image on my internal sd through clockword mod recovery: again got the same error.
E:Can't mount /dev/block/st110(File exists)
Error mounting /datadata/!
Skipping format...
E:Can't mount /dev/block/st110(File exists)
Can't mount /datadata/!
Looked on web - "eugene's froyo that does not brick"
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
I have not used sdk or adb before and am not confident either.
Sorry for making it such a long post but I wanted to make sure that I give all the details.
Can someone advise me further?
Freaking out in NYC.
Menn, I'v got the same problem.
Can anybody help please??
try repartition with another .pit-file. Solved the problem for me.
Odin back to jfd
Tried to go from CM7 #11 to Simply Honey 3.5 Revolution, but when that didn't work, I ended up Odin-flashing stock KB1... and now I get this when booting:
Android system recovery <3e>
System Recovery Utils
- for BML -
reboot system now
reinstall packages
delete all user data
delete cache\
format internal sd-card
update media, please wait
E:Can't mount dev/block/stl10
(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.
Click to expand...
Click to collapse
Got the same error message when attempting to format the internal sd-card, and more importantly, when putting the device into download mode, it's no longer detected by Odin...
EDIT: Fixed! At least in the sense that I was able to flash back to stock JFD, by choosing the 512 PIT instead of the 803 PIT, and by physically disconnecting/reconnecting the micro USB cable while Odin was open. Whew! A frightening lesson, but it's reinforced the importance of flashing back to stock before switching ROMs.
EDIT #2: On the other hand, when I root JFD, then install ROM Manager from the Market, then flash CWM 2.5.1.2, reboot into CWM recovery through ROM Manager (instead of 3-button), then try to flash a ROM, it seems to hang/freeze at "finding update package"... but rebooting into recovery by 3-button fixed this, thankfully.
glad you got it resolved, but next time, remember to review/look over standard procedures in the noob bible. Your problems were because of your actions....... operator error...........
Hello everyone.
I was trying to ODIN my Vibrant back to stock JFD (not my first time... plenty of success in the past) from the ICS Passion rom....
After the flash, i get the following message:
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.
Click to expand...
Click to collapse
PLEASE HELP!!
I've did quite a bit of searching around the web, as well as on XDA. I've tried reflashing, using different USB ports, restarting... all the lot.
suggestions or an I looking at a perma-brick?
I can access recovery and download mode with the button combinations.
TIA!!
Nevermind...
Fixed.
did a clear cache, clear all user data, format internal SD card
then flashed with a freshly downloaded JFD tar and pit file.