Database Develop

boot screen

hello my galaxy is developed a fault . i charged it overnight but when i went to power up in the morning it will not go past the S the screen goes black nothing else ...bricked big time kies will not pick it up on usb ...

So you see the connecting dots that make the S on the boot screen or is it all black before you see that?
Sent from my GT-I9000 using XDA App

Did the same thing to mine. Twice now in fact
The first time, factory reset fixed it though I had to re-install everything (thank you titanium backup).
That was caused by un-installing the one-time lag fix app, figuring I didn't need it once it had made the changes. Apparently I did.
The second time (the next day), I achieved the same result trying to re-install the default calendar app (which I over-zealously un-installed removing the samsung bloatware). Factory reset didn't fix that one, currently about to try my first firmware install (going for 2.2 while I am it, 'cos hey, phone doesn't work anyway, right?).
Both times, boots up to S logo, but sits on that animation for a bout 30 seconds, then screen goes black (button menu and back buttons light up if you press them, so the phone is still "on").

cruisewd said:
Did the same thing to mine. Twice now in fact
The first time, factory reset fixed it though I had to re-install everything (thank you titanium backup).
That was caused by un-installing the one-time lag fix app, figuring I didn't need it once it had made the changes. Apparently I did.
The second time (the next day), I achieved the same result trying to re-install the default calendar app (which I over-zealously un-installed removing the samsung bloatware). Factory reset didn't fix that one, currently about to try my first firmware install (going for 2.2 while I am it, 'cos hey, phone doesn't work anyway, right?).
Both times, boots up to S logo, but sits on that animation for a bout 30 seconds, then screen goes black (button menu and back buttons light up if you press them, so the phone is still "on").
Click to expand...
Click to collapse
I am also experiencing the same issue..
appears to a common problem if it occured to more than 3 units already.
Please visit my post "[Q] Bell Vibrant will not go Pass the Galaxy S logo once powered on" in the General section

Lag fixes tend to break this
Sent from my GT-I9000 using Tapatalk

GUNG said:
hello my galaxy is developed a fault . i charged it overnight but when i went to power up in the morning it will not go past the S the screen goes black nothing else ...bricked big time kies will not pick it up on usb ...
Click to expand...
Click to collapse
use the three buttons combo and go into recovery mode , using volume button for up/down select factory reset and this should fix it.. but all ur contacts and stuff on the device will be lost.. only the stuff on the internal sd card will not be lost

[Q] Phone on Doc's ROM suddenly locks up and upon reset apps go crazy.

Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.

This is not a reason to start a new thread in the Development forums.
Support and Q&A for custom roms should take place in their appropriate threads. Use a bit of common sense, courtesy, and patience -- people will help you.
Please read the rules of posting new threads again here: http://forum.xda-developers.com/showthread.php?t=788800

anoneemooz said:
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
Click to expand...
Click to collapse
1) Lock ups most likely due to removing drm file from system apps.
2) Your using lagfix (I assume) and when you pull battery data corruption is very likely on some configs.
3) Read rules before posting.

[Q] SGS on DOC rom suddenly hangs, then upon battery pull and reboot..apps go crazy.

Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.

[Q] infinite boot and many other problems

I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.

so no one has any idea what i'm doing wrong? or has experienced similar problems?

Try to reinstall the drivers in kies.
If that don't work do download
Them from android development site.
It should work.
Try the phone in all mode you can to get the drivers to install right.
Then you can try to fix it with kies or odin.
**DamianGTO Steam kernel. 349MB Ram. 256HZ. ext2. js3 base**

Another approach
I too cannot get odin or kies (or usb mass storage) recognized on the PC. I tried for a long time and gave up.
Are you rooted or can you access the root dir? If not can you access the external SD card or market so that you can root?
Do you have clockwork mod or similar?
I can only base my experience never using odin or a pc...
If you can get into recovery mode and start using (if you do not have it already)clockworks mod (and/or steam recovery - which I highly recommend as it can access the removable sd card which is useful to load stuff on to when things go sideways see why in my post http://forum.xda-developers.com/showthread.php?t=929020 ).
Then you can flash whatever you want from the root directory or with steam from the external SD car (root dir there) no odin or pc required (directly).
Then I'd start with stock or at least a custom rom that is based on your carriers stock and go from there.
G

wastedkila said:
I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.
Click to expand...
Click to collapse
Hey!
I've had the EXACT same problem as you. did you try to put your phone into DOWNLOAD MODE (Close phone, then hold volume down, then home, then power) to see if it connects to odin? Also, before you do anything, make sure you turn on odin first and then select all the files you want. After thats done, then put your phone into download mode, then connect the phone to your computer thru the USB.

Sliding won't work anymore

Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web

If you already have Rom Manager, just click Reboot into Recovery..

inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone

Sbf back to stock?

taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem