Database Develop

[Q] bootloop after 2.2.1

Hello,
Bit of a droid noob here. I forced my Galaxy S to update to 2.2.1 today through Kies. It wouldn't work at first so I had to erase the M off of the model number in the registry to make it work (I think thats where my problem started).
Now my phone just reboots at the samsung screen or if it is plugged into USB it shows a star on the screen. I am able to get into download mode and use Odin, but even after flashing with a stock ROM from samfirmwares it still boot loops.
Help.
Thanks.
Oh, I think I am in the wrong forum. Q and A would be more appropriate. Sorry...

Okay, been messing around a bit more. Tried to load a different 2.2.1 ROM and now it turns on and flashes the Galaxy S screen and turns off. Not sure if it is getting better or worse.

did you had any lagfix activated while updating? if so, try to a factory reset through recovery mode.

No, I had no mods. It was a stock Bell rom updated through Kies. I managed to boot into recovery mode and it said something about can't mount sd card.

Encrypted1024 said:
No, I had no mods. It was a stock Bell rom updated through Kies. I managed to boot into recovery mode and it said something about can't mount sd card.
Click to expand...
Click to collapse
I've just encountered this problem myself (I guess misery loves company Lets see if we can resolve this.
What was the 2.2.1 ROM that you flashed that allowed you to get back into recovery?
What's the specific error msg you're getting when you're in recovery?

Well, I have flashed so many ROMs today trying to fix it, what I can tell you is this: JL2 gives the best results. It gets to the S screen with JL2. I think JL2 lets you get to recovery mode, if not then JH2. Speedmod seems to format the sdcard but doesn't seem to fix the issue.
I am getting this error from recovery mode:
E:Can't/b mount /devlock/stl10
Some people say they have fixed this with various flashes and reflashes and repartition combos. I have had no luck so far.
Apparently there is a way to restore the partiation, but I am not there yet.

Oh, the 2.2.1 ROM I tried was JPU_Complete_Flash_by_Virnik

Most likely the internal SD is dead and you'll have to send the phone in for repairs...
Mine just died (again) too. Same problem.

I just got my i9000m back from repair today... Updated to the official Bell for fun and then tried to go back to jh2 for recovery 2e and now my phone continuously loops at the first GalaxyS screen. I tried to flash many other versions with same results... Tried odin 1.7 and that didn't help. Tried various combinations of re-partition and different versions and nothing is working. Any idea?

WOW! I am back up and running. This appears to be a data partition issue.
Can't say exactly what I did but here it goes. I may have done these things more than once today so you may have to run through this procedure a couple of times.
- Flashed JH2 with repartition and pit 512. (Stuck in bootloop)
- Flashed JL2 with Repartition and pit 512. (Boot to S Screen now)
- Flashed with SpeedMod 12
- Boot to recovery mode
- Format every partition
- Flash to JH2 with repartion and 512 pit. (Back to boot loop)
**** Heres where it was different***
- Flash to JL2 without repartion or pit
Booted up and working.
I know, sounds sketchy, but I must have reflashed my phone with 10 different firmwares today.
After I got it booted up I flashed it with Darky's 7.6 ROM. It gave an error at first about the data parittion but it repaired itself after running lagfix and changing to ext partition.
I may recomend to flash with Darky 7.6 and apply lagfix to rebuild the partitions and see if it fixes this issue right away.

P.S. I was using Odin 1.7 all day and switched to 1.3 in the end. I was using 1.3 when I got it working. Just thought I would add that.

Encrypted1024 said:
WOW! I am back up and running. This appears to be a data partition issue.
Can't say exactly what I did but here it goes. I may have done these things more than once today so you may have to run through this procedure a couple of times.
- Flashed JH2 with repartition and pit 512. (Stuck in bootloop)
- Flashed JL2 with Repartition and pit 512. (Boot to S Screen now)
- Flashed with SpeedMod 12
- Boot to recovery mode
- Format every partition
- Flash to JH2 with repartion and 512 pit. (Back to boot loop)
**** Heres where it was different***
- Flash to JL2 without repartion or pit
Booted up and working.
I know, sounds sketchy, but I must have reflashed my phone with 10 different firmwares today.
After I got it booted up I flashed it with Darky's 7.6 ROM. It gave an error at first about the data parittion but it repaired itself after running lagfix and changing to ext partition.
I may recomend to flash with Darky 7.6 and apply lagfix to rebuild the partitions and see if it fixes this issue right away.
Click to expand...
Click to collapse
Encrypted, you are the man! I followed everything you posted and now I'm back up and running!

Encrypted1024 said:
I am getting this error from recovery mode:
E:Can't/b mount /devlock/stl10
Click to expand...
Click to collapse
Ahh.. That's where we differ. I'm glad you recovered from your error (too bad it happened to begin with). I'm getting the "E:Can't mount /dev/block/mmcblk0" error msg which I am fairly certain means I'm toast. Nothing working so far. I think I'll be testing the new return & $100 credit policy today.

I have seen similar posts where the steps I used helped with your error too. I would give them a try just to see.

Encrypted1024 said:
WOW! I am back up and running. This appears to be a data partition issue.
Can't say exactly what I did but here it goes. I may have done these things more than once today so you may have to run through this procedure a couple of times.
- Flashed JH2 with repartition and pit 512. (Stuck in bootloop)
- Flashed JL2 with Repartition and pit 512. (Boot to S Screen now)
- Flashed with SpeedMod 12
- Boot to recovery mode
- Format every partition
- Flash to JH2 with repartion and 512 pit. (Back to boot loop)
**** Heres where it was different***
- Flash to JL2 without repartion or pit
Booted up and working.
I know, sounds sketchy, but I must have reflashed my phone with 10 different firmwares today.
After I got it booted up I flashed it with Darky's 7.6 ROM. It gave an error at first about the data parittion but it repaired itself after running lagfix and changing to ext partition.
I may recomend to flash with Darky 7.6 and apply lagfix to rebuild the partitions and see if it fixes this issue right away.
Click to expand...
Click to collapse
This worked for me, there was some talk earlier of a bounty, so I donated 5 bucks (it's all I have right now) to childsplay charity through text in your name

gtg2 said:
Ahh.. That's where we differ. I'm glad you recovered from your error (too bad it happened to begin with). I'm getting the "E:Can't mount /dev/block/mmcblk0" error msg which I am fairly certain means I'm toast. Nothing working so far. I think I'll be testing the new return & $100 credit policy today.
Click to expand...
Click to collapse
On the phone I sent out I was able to get both errors depending on the firmware/kernel. Wish JL2 was out then.
Sent from my GT-I9000 using XDA App

sr3yas said:
This worked for me, there was some talk earlier of a bounty, so I donated 5 bucks (it's all I have right now) to childsplay charity through text in your name
Click to expand...
Click to collapse
Awesome! Thanks!

I was having similar issue and your post helped Thanks!
Encrypted1024 said:
WOW! I am back up and running. This appears to be a data partition issue.
Can't say exactly what I did but here it goes. I may have done these things more than once today so you may have to run through this procedure a couple of times.
- Flashed JH2 with repartition and pit 512. (Stuck in bootloop)
- Flashed JL2 with Repartition and pit 512. (Boot to S Screen now)
- Flashed with SpeedMod 12
- Boot to recovery mode
- Format every partition
- Flash to JH2 with repartion and 512 pit. (Back to boot loop)
**** Heres where it was different***
- Flash to JL2 without repartion or pit
Booted up and working.
I know, sounds sketchy, but I must have reflashed my phone with 10 different firmwares today.
After I got it booted up I flashed it with Darky's 7.6 ROM. It gave an error at first about the data parittion but it repaired itself after running lagfix and changing to ext partition.
I may recomend to flash with Darky 7.6 and apply lagfix to rebuild the partitions and see if it fixes this issue right away.
Click to expand...
Click to collapse

When flashing with Odin do you have checked Repartition? Do that and it should work.
Sent from my GT-I9000 using XDA App

Encrypted1024 said:
WOW! I am back up and running. This appears to be a data partition issue.
Can't say exactly what I did but here it goes. I may have done these things more than once today so you may have to run through this procedure a couple of times.
- Flashed JH2 with repartition and pit 512. (Stuck in bootloop)
- Flashed JL2 with Repartition and pit 512. (Boot to S Screen now)
- Flashed with SpeedMod 12
- Boot to recovery mode
- Format every partition
- Flash to JH2 with repartion and 512 pit. (Back to boot loop)
**** Heres where it was different***
- Flash to JL2 without repartion or pit
Booted up and working.
I know, sounds sketchy, but I must have reflashed my phone with 10 different firmwares today.
After I got it booted up I flashed it with Darky's 7.6 ROM. It gave an error at first about the data parittion but it repaired itself after running lagfix and changing to ext partition.
I may recomend to flash with Darky 7.6 and apply lagfix to rebuild the partitions and see if it fixes this issue right away.
Click to expand...
Click to collapse
This works! You are THE man!

[Q] Cant flash custom firmware all of a sudden

Hello, sorry if this has been posted before but the search function is awful.
I have a UK i9000 (SGS) on Vodafone
I had my phone working great with some custom rom, Tayutama edition was my favourite. I dropped the phone on top of my computer, it went haywire and started resetting every few minutes. It would do it if you flicked it or jolted it so I assumed that it was probably a connector in the battery. It was not something I could fix so I prepared to phone so I could send it back as a warranty job. With a lot of work, I managed to return it to a stock firmware 2.1 (via ODIN), I have sucessfully updated it (via ODIN) to XXJPY and I am using kernel 2.6.32.9 hardcore_speedmod-k12r-500hz #6. My Phone is rooted with ch root.
I can get into clockworkmod recovery fine (by installing ROM Manager), i can install a custom rom no problem (it flashes correctly), but it refuses to boot after the flash process is complete. It just gets stuck at the 2nd boot screen (whether this is custom or the standard SGS gleam logo). It does this with various custom rom's and I was wondering what the problem might be. As I said, I could flash custom roms at my leisure until i dropped the phone, now it wont work. I am sure that it is not the phone that is phsyically broken as this sounds likely, but probably my flashing root.
To get the phone working, after flashing a problem rom, I must always use ODIN to flash JM6 with 512 pit and the XX CSC. Then I can flash JPY with ODIN (using an all in one package, so no CSC/modem etc), then root, speedmod kernel etc.
Anyone got any suggestions as to why?

do you have lagfix enabled on your speedmod kernel ? that can cause issues..
also how long are you letting it boot for ?? after a flash my phone can take upto 15mins to get past the boot screen.

last few times i had it disabled i think.
I did a full wipe of the SD card and the internal SD card, then flashed from download with odin successfully. Therefore the lagfix cant have been enabled as I understand it. I have disabled it the proper way (cant remember how) and still unsucessful.
In my experience it normally takes between 3-5 mins for the first boot, I had left it well over 2 hours once (to prove to myself that it was not my lack of patience) with out any change. I have tried taking out the battery, re-inserting it and booting again (for another 2 hours) and no success.
Is there a foolproof way to ensure the lagfix is disabled? Last time I tried a custom rom, I was coming from a totally stock firmware phone. No lagfix applied, no custom kernel, only rooted to allow clockwork recovery to install, should I try it again without rooting the phone, IE just using clockworkmod's update.zip at recovery?
miles

http://www.multiupload.com/PUSOOBQ8K5 download that and flash it with odin using the pit included and CHECK REPARTITION.. then when thats done flash JPY thru odin and then you could flash speedmod kernel thru odin..
when all that is done it will leave you with CWM and in there you can root / unroot You will be un rooted as default, also you can enable lagfix / disable lagfix you will have lagfix disabled by default too.
you are right about lagfix being removed when going back to stock.
so when all that is done your phone will be stock except the kernel, if all that works you should be good to start again..
just one more thing, when you are flashing a rom thru CWM you are choosing install update from sd card >> chose update from sd card right ??? you dont need to be rooted to flash speedmod kernel

[Q] Boot loop

Hi guys,
I have browsed the forum and have tried several of the remedies here but still no luck. I have been running Darkyy's 9.0.2 rom for a few weeks now, with a 500hz- speedmod kernel (don't remember what flavour, but was flashed via CWM). It has been running great since I flashed.
The problem arose when I went into settings to simply change the lock screen. I selected another lockscreen and my phone rebooted. Then it gave me quite a few FC errors,so I decided to boot into recovery and 'restore' a previous save. Now my phone just shows the samsung logo and reboots.
I am able to get into download mode but not recovery. This will be the fourth time I have to send it away. Is there another option or is this still my only option?
Any thing specific I should try to flash.
If it helps I am on the BEll network (gt-i9000M)

try to flash JPY base stock ROM with Odin......
try without repartition and pit (1 file PDA, no pit file from samfirmware.com)....
Then flash the latest speedmod kernel.....
Now it should work (maybe! XD)!!

Thanks for your reply, I tried your suggestion but still the same problem. I also tried all of the suggestions on this link. I finally was able to get into the recovery console by flashing JPY (no part, no pit), then immediately flash JL2 (with bootloader, no flash, no pit) but I got the dreaded 'no such directory'...again. So I am SOL but have to take it back today.

Did you tried flashing with 3 files + pit + repartition?
With this method it should work...
Remember: no bootloader update!
Sent from my GT-I9000 using XDA App

Did you ever upgrade to the official Bell JL2? If not, I'd probably do that through Odin and have it update the bootloader. I had gone from JH2 to different cooked roms and would always run into corruption/fc problems a week later. And eventually the phone would just not boot into the OS. The last time it happened, even flashing to another cooked ROM would not work. The official bell JL2 has an bootloader update that seemed to have fixed the issues I was having.
Booted official JL2 and remembered how much I hated lag After that, flashed a 2e kernel through Odin then seeARM's cooked JL2 through clockwork. Been running that for 3 weeks now without any issues.

Hi Guys,
I should probably write down what I flash when I flash it. I honestly do not remember what I flashed. I went through all the threads I could find and tried everything. So to answer your question, I cannot say for sure if I did that or not. But I ended up sending the phone away. It was weird, I asked my fiance to take my phone in while I was at work. She called me later that day and told me that her phone did the same thing so she sent hers back the same day....weird.

[Q] Samsung Galaxy S blank screen while booting

I have checked other similar threads before posting, but I couldn't find anything helpful.
I had a stock 2.1 Eclair then updated to FroYo through Kies a couple of days ago (firmware JPA). Then I applied the voodoo lagfix through Odin and everything was working fine. Today I tried to install CF-Root using Odin. It went fine and my phone rebooted but then it went into a blank screen after the booting animation/sound.
I CAN boot into both recovery and download modes but I'm a little bit confused on what to do now. Should I flash a new firmware or is there any thing else that I could do to fix this. And if I have to flash a new firmware, which version do you recommend (I prefer stock 2.2.1 Samsung firmware, preferably ones for the Middle East so they would have Arabic support).
Thanks in advance

Just a little update. I flashed a new firmware (XWJPA), it went fine and rebooted then came up with the recovery menu with an error message that the /dev/block/stl10 can't be mounted. I tried to wipe stored data (not internal SD card) and rebooted it. Now it goes into the same blank screen but keeps vibrating randomly!!
Any suggestions?

your dbdata is corrupted. i think JM5 or JM8 contains it...
i had this problem recently,, i flashed darkys 9.2 resurrection thru odin (that contains dbdata) and that fixed my problem...

azzledazzle said:
your dbdata is corrupted. i think JM5 or JM8 contains it...
i had this problem recently,, i flashed darkys 9.2 resurrection thru odin (that contains dbdata) and that fixed my problem...
Click to expand...
Click to collapse
Can anyone confirm which one has dbdata, JM5 or JM8? I currently have a very slow internet connection and downloading both would take a lot of time.
Also could anyone explain the reason it got corrupted?
Thanks for your help

I flashed JM5 and now my phone boots fine again. Later I tried to flash JS5 but I got the same problem again! What am I doing wrong? And which is the latest stable firmware that I should flash to?

Don't tick repartition in odin when you upgrade to JS5

Thanks for the quick reply. The update went fine

Stuck on main screen after root, keeps rebooting.

I have been through a mess of attempts to root my phone and put it into 2e recovery so I could install custom mods, and ended up with nothing but an old version because I had to flash it on to be able to use it.
I'll try to explain the process.. first I had 2.2 firmware with JPC, was rooted already with superuser and then I tried to flash it into 2e recovery but when it finished the phone booted up, got in the main screen where you swipe the screen to unlock but got stuck there after a couple seconds, started vibrating randomly and shut down.
After that happened I flashed an original i9000 tar on it and it came back to life, unrooted and in JP6.
The first time I tried to flash it into 2e I forgot to run odin as an admin, so I thought that was my mistake so I went ahead and tried it again with a JP6 version and ran odin as admin, but the same exact thing happened... gets stuck in the same place so I flashed the original again.
I'm on a EU Galaxy S I9000 JP6 Froyo.
Anyone have an idea what I'm doing wrong?

SmokeyFish said:
I have been through a mess of attempts to root my phone and put it into 2e recovery so I could install custom mods, and ended up with nothing but an old version because I had to flash it on to be able to use it.
I'll try to explain the process.. first I had 2.2 firmware with JPC, was rooted already with superuser and then I tried to flash it into 2e recovery but when it finished the phone booted up, got in the main screen where you swipe the screen to unlock but got stuck there after a couple seconds, started vibrating randomly and shut down.
After that happened I flashed an original i9000 tar on it and it came back to life, unrooted and in JP6.
The first time I tried to flash it into 2e I forgot to run odin as an admin, so I thought that was my mistake so I went ahead and tried it again with a JP6 version and ran odin as admin, but the same exact thing happened... gets stuck in the same place so I flashed the original again.
I'm on a EU Galaxy S I9000 JP6 Froyo.
Anyone have an idea what I'm doing wrong?
Click to expand...
Click to collapse
do you want to stay on 2.2.1 or want to switch to GB...
if you can still get into dowloadmode (vol down / home / power)
froyo XXJPU : http://dl.dropbox.com/u/19506141/Stock - stock modems/I9000XXJPU (2.2.1).exe
GB XWJVH : http://dl.dropbox.com/u/19506141/Stock - stock modems/GT_I9000_XWJVH_XXJVO_NEEJV3_Sbl.exe
flas with odin : http://dl.dropbox.com/u/19506141/flash en drivers/Odin_+_pit.exe
PIT512 file is included, both firmwares come with safe bootloaders.
flash files with repatition checked.
and if you need them samsung drivers for PC :
http://dl.dropbox.com/u/19506141/flash en drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe

for rooting your phone you can use
froyo : http://dl.dropbox.com/u/19506141/speedmod-kernel-k13e-500hz.tar
GB JVH :http://dl.dropbox.com/u/19506141/Gingerbread-GT-I9000-XWJVH-stock-kernel+hacks.tar
flash in PDA using odin.Do NOT check repartition....

Thanks for the reply..
I don't want to make any mistakes, as im quite new to this phone and hacking/updating/putting new **** on it, so can you be a little more clear on the steps to take? I'm obviously going to upgrade to GB...
I can get into download mode fine, do I flash the 512 PIT file and the PDA_XWJVH_Sbl.tar.md5 file together? also just to make absolutely sure because I heard the partition thing can brick my phone, should it be checked for this particular flash?

SmokeyFish said:
Thanks for the reply..
I don't want to make any mistakes, as im quite new to this phone and hacking/updating/putting new **** on it, so can you be a little more clear on the steps to take? I'm obviously going to upgrade to GB...
I can get into download mode fine, do I flash the 512 PIT file and the PDA_XWJVH_Sbl.tar.md5 file together? also just to make absolutely sure because I heard the partition thing can brick my phone, should it be checked for this particular flash?
Click to expand...
Click to collapse
You should only use the repartition option when flashing a 3 file firmware. You can get them from samfirmware.com. The JVB firmware has all 3 files so I would download it.
Once downloaded open Odin and stick the files in the required fields. Insert your .pit file and select repart.
Once you have booted in to JVB you can then flash JVH using Odin in the PDA field with NO repartition.
Once booted into JVH I would use CF Root kernal to get root access

Go to insanity thread and check out the link to Ezbase rom, its a cinge! Noob too!
Sent from my GT-I9000 using XDA App

slaphead20 said:
Go to insanity thread and check out the link to Ezbase rom, its a cinge! Noob too!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
yes i second that,,got me ouy of trouble a few times