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...........
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.
It all started today when I rooted my stock 2.2 and installed Voodoo.
After I installed Voodoo, my phone wouldn't boot. So I Odin'ed a stock ROM.
The Problem is, I have no internal/external storage on the phone at all!
I've tried flashing milliions of times, but no dice. Anyone know how to fix this?
EDIT:
There was a time where it showed my internal storage and I used the File manager to go in and erase the Voodoo folder and stuff. But still nothing. And everytime I check the "Re-partition" option in Odin, I get an says that Data wipe failed. I'm really stuck here guys!
EDIT2:
Now it says:
"update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbate_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions"
If I selsect "format internal sd-card" I get the same error.
boot into recovery, clear cache, do a reset and then clear dalvik the reflash 2.1JFD make sure to check repartition box, after it is done then root and then flash a custom rom of your choice
oka1 said:
boot into recovery, clear cache, do a reset and then clear dalvik the reflash 2.1JFD make sure to check repartition box, after it is done then root and then flash a custom rom of your choice
Click to expand...
Click to collapse
If I'm not mistaken, CWM is the only one with that option. I don't have CWM installed.
AWESOME!
Seems to have worked... I got all my storage space back.
Only problem I have is, low application storage.
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.
Okay. Here's the thing. Let me try to break the story down:
I tried to flash the MIUI ROM. So basically, I followed the instructions to the best of my ability, but when it was time to flash the ROM itself, I got a Status 7, and installation aborted. When I rebooted, the screen was stuck on the Mi logo (which was peculiar since the installation aborted). It was taking a long time, so I assumed that, yep, bootloop.
So what I did was I flashed stock ROM using odin. Just the stock rom (ie, you have to repartition before flashing the miui rom). But one think I noticed before I flashed the ROM, was after I repartition through ODIN, the USB storage was 0.00b/0.00b. Several bootloops after, I finally got my phone working, but this time I can't access my USB storage. When I go to the task manager, it says 0.00b/0.00b. When I plug it in my PC, the only drive I see is the SD card (when there should be two, right?). PLUS, when I boot the phone and go to the media files (example, music app, gallery app etc.) it says I have no SD card inserted. When I do.
On screen, the notification says the USB storage is something, like unsupported and when I tap it, it says I have to format my USB storage. When I do tap format, it says that it's still checking the USB storage, and the notification comes up again. If it's imporatant, I also tried formatting the USB storage via CWM, but it says cannot mount /emmc. I ALSO can't find my phone on my PC now. The GT-I900 doesn't come up in my drives when I plg it in
I've tried flashing the stock PIT file, but to no avail. Please help. I just want a faster phone (hopefully via MIUI) or
Oh, and please bear with me. I'm a complete noob.
After re-partitioning, you need to wipe the partitions (/system /data (sdcard0). Make Backups and don't forget to flash a Rom/Kernel after wiping /system, because else your recovery will be lost.
I'll try to help you since I did installing MIUI v6 ROM by @blackra1n which also require resizing system partition.
pochic1996 said:
I tried to flash the MIUI ROM. So basically, I followed the instructions to the best of my ability, but when it was time to flash the ROM itself, I got a Status 7, and installation aborted.
Click to expand...
Click to collapse
Status 7 could be possible you were using older custom recovery when installing the ROM.
pochic1996 said:
So what I did was I flashed stock ROM using odin. Just the stock rom (ie, you have to repartition before flashing the miui rom).
Click to expand...
Click to collapse
So, you were repartition using PIT file then install MIUI— failed, then now go back to STOCK ROM (stock firmware?), right?
Did you do repartitioning again to stock PIT version before do flashing the stock ROM?
pochic1996 said:
On screen, the notification says the USB storage is something, like unsupported and when I tap it, it says I have to format my USB storage. When I do tap format, it says that it's still checking the USB storage, and the notification comes up again. If it's imporatant, I also tried formatting the USB storage via CWM, but it says cannot mount /emmc. I ALSO can't find my phone on my PC now. The GT-I900 doesn't come up in my drives when I plg it in
Click to expand...
Click to collapse
Please don't do something careless with /emmc as it might risking your EFS which may loosing your phone info such as IMEI, WIFI, and other radio related data. Please try to repeat the procedure back to flashing stock ROM:
1) Turn on your phone and boot to download mode (home+volume down+power). Connect your phone to PC through USB cable. Run Odin on your PC.
2) Press PIT button and select the stock PIT. Make sure the "repartition" checkbox is ticked on Odin.
3) Press PDA or AP and select your suitable recovery tar file. CWM or Philz recovery should be fine but avoid using the very older ones. Make sure the "reboot" checkbox is UNCHECKED because we don't want the phone reboot to system when flashing is done.
4) Press start button on Odin. Wait for awhile, then if Odin said it's all done, disconnect USB cable and reboot your phone to recovery mode (home+volume up+power). Optional but recommended, keep pressing until first Samsung logo appear, then release power button. Release two remaining buttons if recovery screen appear.
5) Assuming you're using CWM, go to "mount and storage" then choose "format /sdcard0" or "format /internal-sdcard". If prompted for file system format, choose "FAT32" if possible. If not in the list, just select "default".
6) Optional, to make sure the internal storage can be recognized by PC (Windows), still in CWM go to "mount and storage" then select "mount mass storage". Connect your phone to PC and see if Windows recognize your sdcard. If so, open properties dialog for this sdcard and check if it is formatted as FAT or FAT32. If not, right click on sdcard and choose "format". Quick format should be fine, leave all settings to its default.
7) Now, before installing the stock ROM, make sure to format phone's partitions. From CWM, select "mount and storage" then choose "format /data", "format /cache", and "format /system". Next, you may install the stock ROM or else.
It adviced to remove your external sdcard prior perform the steps above to avoid confusion and prevent your external sdcard reformatted accidentally. Also, I hope you were making backups for /efs partition.
Have a try, and good luck as you may need it! [emoji1]
Note:
As a reference, you may consider to read this thread: http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162