Hi,
I've been checking around the forums, and I've seen similar instances, but they seem to all be with the Canadian version which is why I thought I would ask before doing anything else.
I have the Galaxy S i9000 european version. Was rooted, and had lagfix (Voodoo) and was using stock ROM.
Using ROM manager I flashed the clockwork mod recovery. Booted into recovery everything went well. (was just testing that it works).
So now I click reboot and it gives me the static galaxy s screen, then the moving S. Waits for about a min or two, then screen goes black.
So i tried going to recovery mode, that works, but its the samsung 2e recovery mode not the clockwork recovery mod.
So now I'm not sure how to continue. Before I put on the voodoo fix, I did a backup using CWM. its on the internal SD card though. So I though if there was some way to access CW recovery mode perhaps I could restore my backup (assuming that my internal SD card isn't toast like from what I understand most people in Canada are experiencing). I haven't tried flashing with ODIN or adb as I don't want to screw things up more. I can however confirm that I put the phone in download mode, connected to PC, and ODIN did recognize it as 0:[COM15]
Just for reference, I've downloaded I9000XXJF3 (I'm 99% sure that is the version it shipped with) from Samfirmware, which contains a few .tar files. (no pit files) Just in case I have to flash with ODIN (never used it before), please let me know if I do need a pit file.
Sorry for the long winded thread, just wanted to provide all info.
Follow up: I attempted to flash I9000XXJF3 with ODIN with PIT512 and re-partition enabled. Flash seemed ok. Phone rebooted as expected, except it went into 2e recovery. So I selected reboot, and now it did its normal boot got to the moving galaxy s screen and then black again. Any suggestions before I try to take it in for service?
Related
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
I've been trying to reflash my Bell Galaxy S from not booting up without success. I have tried Odin and Heimdall no less then 10 times with different suggestions in this forum. And I went from getting the "Can't mount /dev/block/mmcblk0p1" when the phone first loop boot to not booting at all after first Odin, then to "Can't mount /dev/block/stl10" - "Can't mount /dev/block/mmcblk0p1" after another Odin.
After many Odin and Heimdall flashes now all I got is just a round inanimated "sun-ray" with the usb cable plugged-in or the Samsung splash screen without the usb cable.
I don't want to proceed further because I think the solutions I got from other posts are not specific enough for my situation.
I have read in many posts that you MUST disable lagfix before flashing with Odin or Heimdall. This I did not do because my phone started to loop-boot with the lagfix enabled.
Someone even mentioned here you can't flash your Galaxy too many times as every flash is registered in the phone, or you will void your warranty.....
My phone: Bell Samsung Galaxy S GT-I9000M. Updated from Eclair to Froyo via Kies. I do not know the exact Froyo version but my mental image of the "About phone" info screen seems to agree with UGJK3. Rooted and lagfix enabled while running Froyo.
Firmware packages I have tried back and forth so far:
s1_odin_20100803.pit
DBdata.rfs.tar (and I followed this post: http://forum.xda-developers.com/showthread.php?t=953339)
I9000UGJH2
I9000UGJK3
I9000UGJL2 (last thing I did on Odin and flash with re-partition)
And I did check the re-partition box in some cases when flashing with Odin.
Hope I can get more help here so that I don't damage the phone any further.....
Did you unlagfix before the update? My guess (but I'm no expert) would be that your partitions are still in ext4 which isn't recognized by stock firmware. Could try flashing the an appropriate kernel for your rom which supports the format.
Also, when I have problems after flashing I usually flash back to my previous known working configuration. In this case it would be some eclair rom, and the kernel which supports your lagfix.
odin
find your stock rom from ramad, flash with odin 3 files with repartition and pit.
http://forum.xda-developers.com/showthread.php?t=1102881
no problem to flash in odin with ext4 system.
its important to open odin and insert the files before you connect the phone, also take out the battery before you enter download mode can do the trick.
Removing lagfix isn't mandatory if you are using
re-partition option, since it's setting up all partitions and formatting 'em also. I have many times flashed with Odin without removing lagfix and never had any problems regarding it..
Sent from my GT-I9000 using xda premium
Thanks for everyone's suggestions.
I only applied lagfix after I updated from eclair to froyo. There was no further update after that. So my last working firmware should be a froyo. The bootloop was not caused by any software update process. I dropped the phone and the battery came off. I rebooted the phone (most icons missing from home screen after this boot) but the camera application gave me an error msg when I used it so I rebooted it again. It started to bootloop after this reboot.
I couldn't get the phone in the download mode without the phone battery. And if I get to download mode with the battery, plug the usb, then remove the batter, the phone turned off. so not having the phone battery is not an option to me.
So I did too more reflashes, screen shots attached:
(1) UGJG8
(2) UGKG3
The phone still looped with the circular bars.
I'm wondering if I should check the Phone Bootloader Update box at Odin. Or should I tried Darky Resurrection Edition rom?
nwsk said:
Did you unlagfix before the update? My guess (but I'm no expert) would be that your partitions are still in ext4 which isn't recognized by stock firmware. Could try flashing the an appropriate kernel for your rom which supports the format.
Also, when I have problems after flashing I usually flash back to my previous known working configuration. In this case it would be some eclair rom, and the kernel which supports your lagfix.
Click to expand...
Click to collapse
I took your suggestion and flashed a rom that supports ext4. I flashed it with Darky's Resurrection 10.2. Now I got a boot menu after the reboot. But I got "failed to mount /sdcard (file exists)"
Any idea? thanks.
I have a I-9000M from Bell. By mistake, I flashed to stock of Galaxy Vibrant (T-mobile). I think I found the right flash, I get into download mode and download the flash using Odin. However, when rebooting the phone gets into recovery mode. When I try to format the internal SD it gives a mount error. When I try to boot it remains stuck at the flashing "S".
I was on KG3 before trying to load the Vibrant software.
Any ideas how I can get the phone to reboot?
Thx,
Mike
Here is my situation:
Flying to Europe long-haul tomorrow and I have no phone. I was about to swap phones with someone, so I cleared the data (factory reset) and formatted the sdcard , I didn't think this would delete my whole ROM and recovery image, just some nude pictures I needed to remove.
I was stuck on the boot logo (samsung .Galaxy S.. GT-I9000), which would flicker every now and again as it restarted.
I used to have Slim ICS 4.2 and Clockwork 5.x (I think), but I just want to have a working phone for my travels.
Now I have the yellow triangle working. With ODIN I have even managed to get a simple recovery, but it still boot loops, albeit with an fancier animation and optus logo.
Odin settings:
PIT: s1_odin_20100512.pit and
PDA: JW6_JV6_JW1.tar
re-partition: yes
auto-reboot: yes
f. reset time: yes
odin3 v1.85
So is there an odin compatible ROM around that will actually work for a blank sdcard? It's an Australian GT-I9000 from optus.
I think I'm close to getting this thing working, but having a flight tomorrow I don't have the time to search for roms.
I now have a working phone after flashing JVT from here http://forum.xda-developers.com/showthread.php?t=1583026
Can't wait to get this samsung junk off it and get back to Slim ICS.
Odin on a Semaphore kernel from the dev thread onto your phone (.tar file). Preferably use version 1.2.6 from the ICS thread. Boot into recovery mode and use the format SD card option there. Stick with 2 GB and 0 MB allocated to swap. After that finishes mount the SD card from CWM and copy a ROM onto the phone, then flash it. CM9 or 10 should be fine. Alternatively you can Odin a stock ROM back onto the phone.
Sent from my Nexus 7 using Tapatalk 2
Hey
You need to un-check the repartion in odin3...dat creats bootloops..
That would have been the issue...
Cheers
If my post helped, dont forget to hit the thanks button..
reflash stock froyo it will surely help you just make sure u put correct files on their correct places
so i have been running Paranoid android for a while, and wanted to try this out:
http://forum.xda-developers.com/showthread.php?t=2051904
flashed the latest cm10.1 kernel, and then formated cache, dalvic, battery stats, etc.
then i managed to reboot before i had flashed the new rom and got stuck in bootloop. could not access CWM any more
after this i downloaded odin after a few forum reads, and flashed different versions of CWM to see if i could get back in to flash the rom.
the latest one i have in it is this:
http://fs1.d-h.st/download/00033/pQK/GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar
as it was recommended in some un-brick thread. still no access to CWM
after this i flashed a stock rom, as i could not find any .md5 or .tar roms to use with odin, and i got at least a samsung logo on hte screen, before i got back to boot screen and was stuck there again.
CWM still not working, or showing up in any way.
out of obvious options i now tried flashing the pit file trough odin from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
and after this the samsung boot logo did not show up anymore. only boot loop
i am now going to try and download the older ginger bread rom and flash it trough odin, but i got no idea if it will make any difference.
otherwise phone goes to download mode just fine, and i got working drivers in windows trough kies.
im quite new to this, and dont really know what would work from here. ill end up hard bricking the phone if i don't get some help, and the trash can will be my n7000 next home.
any advice is welcome
--------------------------------------------------------------------
EDIT:
flashing official rom again after the pit file acrually gave me a working phone again. also i now got 50 gb of drop box storrage for free, so thats nice