Can't update to JM6 - Galaxy S I9000 Q&A, Help & Troubleshooting

I've tried flashing the experimental (with EXT2 instead of RFS) and the stock JM6 and both aren't working.
I've tried both .803 and .512 pit files and nothing will work!
I'm coming from JPC.
When I flash the stock JM6 It boots (after 2 SGS logos) and just stays black and vibrates as if a FC has happened.
Anyone have any ideas?

Related

[Q] Phone doesn't boot after installing Busybox

First of all, I have used the search option and only thing I found was for Samsung Vibrant with stock firmware, so I thought of starting a new thread.
I had Froyo XWJPA when I decided to install Busybox (for some tool to change the system fonts, isn't relevant anymore). Used the BusyBox app from the Market, it said that everything was fine, I restart, and the phone just ends up restaring in an endless loop.
So I tried to reflash the firmware, first downgrading to XWJM8, and then upgrading to XWJPA again. But after flashing to JM8 the screen goes blank after displaying the animated bootsplash, and never goes past that black screen. Reflashed with JM8 and ZSJPD and the results are the same.
So, is my phone bricked beyond user repair or I still can do something before sending it back to Samsung? Any help would be much appreciated, thanks in advance.
No your phone is not bricked.
Try this.
Flash jpk with pit 512 and re-partition ticked.
When the phone start go to recovery. Do a factory reset. Wipe the cache and format the internal sdcard.
Restart your phone.
It should work now.
Then flash jpo with no pit and re-partition unticked.
Do the same process in recovery.
You should have a clean working sgs now.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram

[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]Bell 9000M stuck at boot screen

Bought this phone last week, recovery & download worked with 3 button.
Rooted, flashed Darky, Voodoo Lagfixed in recovery, worked great.
Tried Doc Kitchen, worked great.
Voodoo lagfix in recovery, booted once, crashed, now stuck at Galaxy S screen.
No recovery, do have download mode. Power on, Galaxy screen, reboot, galaxy screen.....
This doesn't seem to be the same symptoms as SD failure, seems the only thing left to do is try to flash via Odin...
Downloading UGJL2 from SamFirmware, concern is;
If Lagfix is enabled, most Odin guides say this is an issue? Or should I just select and flash?
Thanks.
And Samfirmware.com gave me a .rar file?
Contents:
factoryfs.rfs
cache.rfs
modem.bin
param.ifs
sbl.bin
zimage file?
I had similar problem. However, I was trying to flash to JH2 because i wanted to unlock my phone, but ended up with boot loop and no recovery mode.
I fixed this problem by trying to flash JH2 firmware and it came back to live. The first time flashed it, the phone went into recovery. However, there was a msg something about Media cant be found. So i flashed it with JH2 again with re-partition not checked and no .pit file. In addition, I used Odin 1.7 instead of 1.3. and the phone is all good now.
I think the problem might be with Odin v1.3. you can give a try but no guarantee..
OK.
Stupidity = Off
Flashed UGJL2, JH2, JG8 using Odin 1.7, Pass!
Still no recovery, still in a bootloop.
flash jpc from samfirmware with pit 512 and repartitioning checked, that worked for me,
using .tar or pda et all?
End thread.
JK4 flash for replacement status nets 3e recovery and a failed SD.
Cheers.

[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

[Q] Can't boot :-P

So it all started on ICS when i couldn't boot because i had replaced a system file...
I flashed back to JVU, which when it was going to reboot just got black. I waited and pulled out battery... Then when i pressed power, nothing happened. Tried recovery. No reaction. Only download mode works. I flashed Darkyy Resurrection 9.3 (JS8] Which had exactly the same problem. Now i have flashed JVU once again, still don't work, same problem. What to do?
Samsung galaxy s said:
So it all started on ICS when i couldn't boot because i had replaced a system file...
I flashed back to JVU, which when it was going to reboot just got black. I waited and pulled out battery... Then when i pressed power, nothing happened. Tried recovery. No reaction. Only download mode works. I flashed Darkyy Resurrection 9.3 (JS8] Which had exactly the same problem. Now i have flashed JVU once again, still don't work, same problem. What to do?
Click to expand...
Click to collapse
Did you ticked repartition when you flashed back from ICS to JVU?
As mentioned, if download mode works, a flash through ODIN using stock ROM with a pit file and repartition checked should fix most problems like this.

Categories

Resources