Database Develop

[Q] MIUI to Darkys problem

I think I've made a fairly large mistake going from MIUI to Darkys.
I was on MIUI v3 (based on CM7) for a short while, but wanted to try something else. I chose to try Darky's v10.1.
I opened ODIN, and chose to flash a 512 pit along with Ficeto's JVH rom (in accordance to this guide). After doing this, my phone is stuck in a bootloop of showing Samsung Galaxy S GT-i9000 screen.
I can still access Download Mode, and my Recovery Menu is very limited (restart, wipe/factory reset, wipe cache partition). I've tried all of those but am not sure what to do to get my phone back on its feet again.
Any help is greatly appreciated!

Download any stock firmware or EZBase.

I have a stock Froyo ROM (Full UGJH2 including SBL) that I tried flashing with a 512 pit but it is still stuck in a boot loop. Actually, now it is showing the Galaxy S GT-i9000 white lettering, then turning off completely.
I fear that I have forgotten to disable the lagfix before flashing with ODIN, however, I never applied one...unless it is applied by default, and has to be specifically removed.
After flashing Ficeto's JVH I get this info in Recovery 3E...
Reboot system now
Apple Update from SD card
wipe data/factory reset
wipe cache partition
-- Copying media files...
E:failed to mount /sdcard (file exists)
E:copy_dbdata_media: Can't mount /sdcard
your storage not prepared yet, please use UI menu
for format and reboot actions
--Wiping data...
Formatting /data...
E:format_volume:rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed
Click to expand...
Click to collapse

Your probably best to go to the Ezbase thread(just search it), download the 3 files for either 2.0(Froyo) or 3.0(GB) depending on what you want, the Ezodin and Ezpit, flash using the guide there and start fresh. Let me know if it works!

Thanks for the recommendation! I've made some progress in Flashing EZbase 2.2.
When I try to reboot the phone however, I am still stuck in a boot loop of white Galaxy S GT-i9000 letters.
I now have access to an advanced recover menu ClockworkMod Recovery v2.5.1.0 SOK ULFK. I've checked my lagfix options, all of them say ENABLE LAGFIX: Convert to xxxxxxxxxx. I'm assuming this at least means that none are currently ENABLED, as I don't have the option to disable any of them. I'm looking at an option called CONVERT, where I can choose to convert my filesystem....Should I select one of the following?
Convert to EXT4
Convert to JFS
Convert to EXT2
Convert to RFS
When I try to access Install ZIP from SD Card it tells me E:Can't mount /dev/block/mmcblk0p1 and E:Can't mount /mnt/sdcard . Is this the source of my problems?

Well, I've been flashing various combinations of pits and roms for the past 3 or 4 hours. I'm not exactly sure what did the trick, I was not able to mount or format my internal SD at all. But, after several attempts at the EZBase ROM, followed by trying to flash to 2.1, finally worked. I got into my UI in 2.1, poked around for a second, and then flashed to Ficeto's JVH which worked.
I've now wiped the device and installed Darky's 10.1 JVH successfully. I wish I had a more detailed answer to how I did it exactly, it was quite a crap-shoot

Nice to see you got it going, don't know why EZbase didn't work straight away.

[Q] My i9000 "gets stuck" while booting, flashing doesn't help

Dear all, I tried now for two full days to resurrect my i9000, with no success so far. I hope one of you can give me a hint where my problem/error lies.
A bit of background: The phone was bought without a contract (no branding) and with android 2.2 (or 2.1?) installed. Afterwards I upgraded to ginger bread with kies, all worked fine for months.
The day before yesterday (after I installed and updated some apps) the phone was quite slow, so I wanted to reboot it. The booting was looped for a couple of times, and as it made it finally to boot, it was almost not reacting anymore. I uninstalled the apps I recently installed and then the phone froze. Now the phone wasn't able to exit the boot loop anymore. I searched this and other forums and learned about recovery mode, download mode, flashing and bootloaders and all these things. And indeed, in the recovery mode, there was an error:
Code:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet, please UI menu for format and reboot actions
Media files copy failed.
Finally I convinced myself, that simply - for what ever reason - android needs to be reinstalled. Long story short: I tried different versions (from 2.1 to 2.3.6) with bootloader, with 1 or 3 files, with different versions of Odin3 (1.7, 1.82, 1.85), with or without repartitioning (pit files 214 [EDIT:I meant 512!] and 803, the later succeded as well, but gave me error messages in the recovery mode). All with the same outcome: Now the phone boots up to the blinking S logo ("splash screen"?), and stays there forever (2h+), while the S is not stuck, but blinks and turns b/w in circles. I let it do this over the last night (connected to my laptop, so it would not decharge) and the next morning it was off, so I guess at some point after 2 hrs it gave up. I found a couple of comparable posts, but my situation I found no where... (not really a boot "loop", neither gets it stuck, but can't complete booting plus wiping and/or flashing, no matter which version, seems not to help).
If any one kept on reading until here and knows something that might help (and/or that I have overlooked so far) I would be more than grateful for a hint!
Thanks a lot!

try flashing the 2.3.5 JVT Firmware with 512.pit and repart. I do not know any firmware which uses those strange .pit files you used(except one or two very old Fimrwares which are using the 803.pit file).. If the phone doesn't boot after doing that you can try formatting your SD in recovery. According to that Errormessage you get in Recovery it could be possible that something is wrong with yout internal Memory. Formatting the internal Memory could solve your problem. After doing both your Galaxy might boot again. If not it could be an Hardwareissue too. In this case just flash the latest official Firmware and send it to samsung and let them repair ist Attantion: All Files like pictures, videos or whatever on your Internal-Memory will be deleted if you format your internal memory!(that apps are deleted after flashing schould be known by everyone )

Detailed method given here
Detailed method given here
http://forum.xda-developers.com/showthread.php?t=846913
use the tutorial to boot to stock firmware, this should put your phone back in business....

no success
Thank you two for your fast answer!
Unfortunately it didn't do the trick
As I wrote 214 I meant the "normal" 512 pit file (d'oh!), sorry for that, orangerot.
I noticed something strange: I left the phone turned off for some hours today, and after the reboot there was again the boot loop I had in the very beginning (until the white Logo), and going to recovery mode there was an error:
Code:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media: Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
I tried a wipe that led me to the following:
Code:
-- Wiping data...
Formatting /data...
E:format_volume rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
asking google for that I found a thread (in german) on handy-faq.de (samsung_i9000_galaxy_s_forum/225311-geraet_gewiped_bootschleife), in which the contributors came to the conclusion the only way would be (and was in the end) the samsung repair service.
Interesting is, that after a reboot I was again at the same position as before (glowing S) and no error message in the recovery mode. From this starting point I tried again to flash (with JVT, 512.pit through Odin3 v1.85, as you suggested), with no visible change of behaviour: still booting only until the glowing S, no error in recovery mode, wiping doesn't help but finishes without error.
If anyone has some additional idea I would appreciate to hear about, otherwise I guess I try to flash an official Android version (any idea how to find out which is the most recent official version updatable from kies?), and bring it to the samsung partner.
Thanks a lot!

I have had athat happen before, try flashing darky's resurrection edition via odin. It worked for me.
Here: http://www.darkyrom.com/community/index.php?threads/odin-darkys-resurrection-edition-10-1-gt-i9000-only-for-now.3237/

still not recovered
Thank you, B1-P,
but unfortunately it didn't work. Odin quitted with green "pass" and "succeed", but after the first reboot afterwards it ended in recovery mode with following errors:
Code:
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Deleting Meta Data
Data wipe failed.

boronian said:
Thank you, B1-P,
but unfortunately it didn't work. Odin quitted with green "pass" and "succeed", but after the first reboot afterwards it ended in recovery mode with following errors:
Code:
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Deleting Meta Data
Data wipe failed.
Click to expand...
Click to collapse
Ahh man...
Okay, there are a couple of more things you can do,
1. Try darky resurrection rom V9.2 (I think your issues maybe due to some lagfix problems/mounting filesystem incorrectly etc.) Try the 9.2 in odin, make sure that you have checked the "Repartition" as ON and have a PDA and a PIT file selected.
http://www.darkyrom.com/community/index.php?threads/odin-rom-darkys-resurrection-edition-9-2.895/
2. And if the Darky rom 9.2 does not work, then this thread is your best shot (you will need at least some linux experience for this to be helpful):
http://forum.xda-developers.com/showthread.php?t=845708
If all that doesn't work, then I don't know what will.... I'm sorry.. I don't know what else you could do. Try a repair centre as a last resort I guess.

Did you try to format your internal sd? Wiping and formatting are two diffrent things.. And in your logs I only see that you are wiping your data.. So just try formatting your internal sd. i think you will find it under "mounts and storages" in cwm. I've read before that this may help to solve this problem. if this does not help it could be that your internal sd is broken. In this case you have to send it to the samsung repairservice. but make sure you flash the official JVI firmware to remove the clockworkmod, so they cannot see that you have flashed your mobile cause if the recognize it they may refuse tu repair your mobile

Try darky resurrection rom V9.2
[...]
And if the Darky rom 9.2 does not work, then this thread is your best shot (you will need at least some linux experience for this to be helpful)
Click to expand...
Click to collapse
After I installed Darky's resurrection 10.1 I had troubles to get in recovery mode... and loads of errors the few times I managed... last attempts didn't bring me to the modified but the "original" recovery menu. I think I don't dare to try Darky's ROM 9.2 after this experience. And for messing around with EXT4 and Linux I don't feel ready at all, thanks though for the link! Now I am back on a stock version and again the old picture.
Did you try to format your internal sd?
Click to expand...
Click to collapse
I thought when I use the pit file and check the repartition box it will reformat the internal sd?? If not... this cwm... I didn't quite get what exactly it is. Isn't it an android app? How can I use it, when I am not able to boot?
And then: is JVI and JV1 the same? If not where is the difference?
Thanks again! (And sorry if my questions are silly)

No, repart only reparts the system partition off the phone. the internal and external SD are not going to be formatted while reparting. If it would behave like that all your photos, videos, folders and so one would have been deleted. Apps are deleted because they are saved on the system-partition.
CWM is a recovery which has some more features than the stockrecovery. You get it with flashing a CustomRom(they usually all have CWM) or an CustomKernel(e.g. CF-Root, Semaphore etc.).
You can acces CWM by holding Vol-up+homebutton+powerbutton at boot and release them when the Galaxy GT-I9000 screen appears. Its just like getting into the Downloadmode but instead of pressing vol- you have to press vol+. Once you are in CWM you navigate to mounts and storages(with vol-up/vol-down you can go up/down and with the powerbutton you select an option) and format your internal sd there. After that everything may be fine again If not you have to send it to the samsung-repair-service after flashing the official JVI-firmware to delete CWM and so on. JVI and JV1 are not the same.. JVI ist the last official firmware(2.3.3) while JV1 is a leaked, unoffical firmware. So you have to flash JVI befor sending you phone to samsung while JVI ist the last official firmware.

back to life
Dear orangerot, dear B-1P
thanks for your patience!
Then I knew the cwm, I just didn't know it was called that way.
last attempts didn't bring me to the modified but the "original" recovery menu.
Click to expand...
Click to collapse
So the "modified" recovery menu I talked about was the cwm. In the last attempt with Darky's Rom I couldn't get back to that cwm... maybe I released the 3 buttons at the wrong time? Don't know.
However, in the mean time I gave the phone to a service partner of Samsung, and they sent it to Samsung. Today I got it back and everything works again. Unfortunately they didn't give any details on what they did (except for new installation of the OS, which didn't help for me...).
So for me this problem is solved (for now...)
Cheers!

[I9000] CM7.1RC update failed -> back to XXJPK failed - help!

I've been on CM7.1RC for a while, recently apps kept crashing for no reason. I have a lot of apps tried disabling some things with autostarts but there were too many apps and too many triggers and all to hard.
So tried wipe cache and wipe dalvik cache, phone took a long time to reboot, was OK for a while but then same thing reoccurred.
So I decided to reinstall CM to the latest daily following wiki instructions, but I did something in the wrong order and got stuck in a bootloop before I had put the zips on the internal SDCard.
So I though, I'll go back to XXJPK using ODIN and restart from there. Again, bootloop. I have download mode and recovery 3e working, recovery 3e brings up error message:
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.
pease use UI menu for format and reboot actions.
copy default media content failed​
I tried to reformat the internal SDCARD using the recovery 3e options and re-ODIN XXJPK but no joy.
Suggestions?

I am getting the same bootloop described in this thread
http://forum.xda-developers.com/showthread.php?t=1466838
but flashing with the stock XXJPK I originally used did not get it out of the bootloop. Any other pointers?

[Q] Failed to mount /sdcard (No such file or directory)

I have a Samsung I987 Captivate. It was running SlimRom 4.2.2 and running fine. It started acting up by showing that the battery was dead. I plugged it into the charger and it immediately said it was half charged. I rebooted it and that s when it all went to hell. I got into clockworkmod and cleared dalvak and cache. At this point I rebooted but it still wasn't acting right. At this point I don't know what happened so I couldn't get into clockworkmod but I could get into download mode with a jig. I used Adam's I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click.jar file which did it's thing and upon a reboot showed this on the screen and that is where it's at. The phone boots to the boot screen and then reboots. I have tryed searching on XDA and Google and haven't come up with a fix other than maybe a jtag at which point the phone isn't worth fixing.
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
-- Copying media files
E:Failed to mount /sdcard (No such file or directory)
E:copy_dbdata_media:Can't mount /sdcard your storage not prepared yet. please use UI menu for format and reboot actions.
media files copy failed.
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Data wipe failed.
--Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'ATT'
Successfully applied multi-CSC

superdog404 said:
I have a Samsung I987 Captivate. It was running SlimRom 4.2.2 and running fine. It started acting up by showing that the battery was dead. I plugged it into the charger and it immediately said it was half charged. I rebooted it and that s when it all went to hell. I got into clockworkmod and cleared dalvak and cache. At this point I rebooted but it still wasn't acting right. At this point I don't know what happened so I couldn't get into clockworkmod but I could get into download mode with a jig. I used Adam's I897UCKK4 Stock, Wipe, with options to install Bootloaders, Param,and Re-partition-One-Click.jar file which did it's thing and upon a reboot showed this on the screen and that is where it's at. The phone boots to the boot screen and then reboots. I have tryed searching on XDA and Google and haven't come up with a fix other than maybe a jtag at which point the phone isn't worth fixing.
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
-- Copying media files
E:Failed to mount /sdcard (No such file or directory)
E:copy_dbdata_media:Can't mount /sdcard your storage not prepared yet. please use UI menu for format and reboot actions.
media files copy failed.
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Data wipe failed.
--Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'ATT'
Successfully applied multi-CSC
Click to expand...
Click to collapse
I know that you aren't on ICS and I know that you didn't get the encryption unsuccessful issue that ICS had, but it sounds like your internal SD has died which is similar to what happens with the EU bug. So have a look here http://forum.xda-developers.com/showthread.php?t=1447303 and see if what others experienced after the EU bug isn't the same as what you're experiencing now.

Thank you m1batt1- That is similar to what I have and yes, your right about the ics. The thing that they are doing over on the thread going into cwm is something I can't do. The idea of swapping to the ext sdcard would be fine if I could figure out how to do it. I'll keep looking and trying.

superdog404 said:
Thank you m1batt1- That is similar to what I have and yes, your right about the ics. The thing that they are doing over on the thread going into cwm is something I can't do. The idea of swapping to the ext sdcard would be fine if I could figure out how to do it. I'll keep looking and trying.
Click to expand...
Click to collapse
I'm currently having this problem, where you able to solve it?

luishawk said:
I'm currently having this problem, where you able to solve it?
Click to expand...
Click to collapse
No, actually I turned it in to AT&T for the rebate credit card. I haven't heard anything from them at this point. I got it to a point where it would boot up to the ATT screen. As stock as I could get it.

[Q] Reinstalling stock firmware - stuck in boot loop

I had my rooted Galaxy S running well on CyanogenMod 10.1, but wanted to unroot so as to use my bank's app. While flashing Android 2.3.6 with Odin 1.87, I got various error messages and the phone boot looped. I tried to follow the instructions here , but the stock ROM I9000XXJVU_I9000OXAJVU_OXA.zip doesn't seem to be available now. Installing Semaphore CWM went OK, but of course the stock ROM has overwritten that. The stock recovery says:
E: failed to mount /dbdata (Invalid argument)
Copying media files...
E:failed to mount /dbdata (File exists)
E:cope_dbdatamedia:Can't mount /dbdata
your storage not prepared yet. Please use UI menu for format and reboot actions.
What stock ROM should I use that will deal with this? Or is there another solution?

Amphibian59 said:
I had my rooted Galaxy S running well on CyanogenMod 10.1, but wanted to unroot so as to use my bank's app. While flashing Android 2.3.6 with Odin 1.87, I got various error messages and the phone boot looped. I tried to follow the instructions here , but the stock ROM I9000XXJVU_I9000OXAJVU_OXA.zip doesn't seem to be available now. Installing Semaphore CWM went OK, but of course the stock ROM has overwritten that. The stock recovery says:
E: failed to mount /dbdata (Invalid argument)
Copying media files...
E:failed to mount /dbdata (File exists)
E:cope_dbdatamedia:Can't mount /dbdata
your storage not prepared yet. Please use UI menu for format and reboot actions.
What stock ROM should I use that will deal with this? Or is there another solution?
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=1640906

Amphibian59 said:
I had my rooted Galaxy S running well on CyanogenMod 10.1, but wanted to unroot so as to use my bank's app. While flashing Android 2.3.6 with Odin 1.87, I got various error messages and the phone boot looped. I tried to follow the instructions here , but the stock ROM I9000XXJVU_I9000OXAJVU_OXA.zip doesn't seem to be available now. Installing Semaphore CWM went OK, but of course the stock ROM has overwritten that. The stock recovery says:
E: failed to mount /dbdata (Invalid argument)
Copying media files...
E:failed to mount /dbdata (File exists)
E:cope_dbdatamedia:Can't mount /dbdata
your storage not prepared yet. Please use UI menu for format and reboot actions.
What stock ROM should I use that will deal with this? Or is there another solution?
Click to expand...
Click to collapse
You should factory reset and wipe cache and dalvik cache partitions. If else fails, try flashing a different stock ROM.

gsstudios said:
You should factory reset and wipe cache and dalvik cache partitions. If else fails, try flashing a different stock ROM.
Click to expand...
Click to collapse
Thanks guys. Meanwhile I managed to track down the XXJVU ROM and now have the phone up and running again on Cyanogenmod 10.2.1. But despite wiping cache and Dalvik cache, and factory resetting, it is still rooted! There is no Superuser app but #Superuser is still in the settings menu, and my bank's app reports that it won't work because the phone is rooted. Very odd. I suppose I'll have to try a different stock ROM, but why doesn't root disappear when flashing a stock ROM?