I9000 bootloader flash help - Galaxy S I9000 Q&A, Help & Troubleshooting

I want to take and flash a i9000 from froyo to gingerbread. And i need to know if i can flash a stock 2.3.5 at the same time as the bootloader in odin. So put bootloader in bootloader slot pda in pda slot pit in pit spot and csc in csc slot and flash it. If it wont work like that than please tell me how to do it.
Sent from my GT-I9000 using XDA

Just flash a ROM that already has boot.bin and sbl.bin and you're good to go.
Flashing a separate bootloader in Odin seems to be the #1 cause of bricked phones.
I flashed a phone for someone tonight and went from the Bell's Froyo release (KC1) to Gingerbread 2.3.6 (JW1) and used Bell's modem and config data (PHONE and CSC).

I am pretty sure you can found some tutorials in the development section (here for instance)

Dont risk ur phone, use a rom with boot!
Sent from my GT-I9000 using XDA

Related

Another XWJS5 (new) in Samfirmware

Does anybody know the difference between the two XWJS5 firmwares?
Difference...
Yes. The previous one is for Heimdall and the new one is for Odin.
As I saw.
I have heard that the new one contains a bootloader update.
I don't know if its true tho.
/qsec
temilla said:
Does anybody know the difference between the two XWJS5 firmwares?
Click to expand...
Click to collapse
Previous JS5 was an update flash (1 file), this one is a FULL Rom (3 file, 242mb). The same difference between JS3 and XEN JS3.
Anyway it shouldn't be 803 .pit. To recover from experimental partitioning I use JS3-full (which is tagged as 803) with 512.pit since 803 doesn't work for me.
matticala said:
Anyway it shouldn't be 803 .pit. To recover from experimental partitioning I use JS3-full (which is tagged as 803) with 512.pit since 803 doesn't work for me.
Click to expand...
Click to collapse
Thanks for that ! I'm trying to install these JS5 since yesterday with .pit 803 without success : mount problem at reboot after odin success, formating in recovery doesn't work and updating couldn't been done by new rom (vibrate loop reboot).
Changing to 512 .pit seems to solve this problem : my phone just restarts on JS5 now !
matticala said:
Anyway it shouldn't be 803 .pit. To recover from experimental partitioning I use JS3-full (which is tagged as 803) with 512.pit since 803 doesn't work for me.
Click to expand...
Click to collapse
OT- that's interesting as I flashed js3 with 803 unsuccessfully but it works with 512.
Sent from my GT-I9000 using XDA App
Content of I9000 XEN I9000XWJS5.rar:
Code:
GT-I9000-CSC-XENJS3.tar.md5
I9000XWJS5-REV03-ALL-low-CL869633.tar.md5
MODEM_I9000XXJPY.tar.md5
Confirmed there are a bootloader and a Sbl file, even though those are likely the same of those included in the previous XEN JS3. I'll make a checksum to verify
UPDATE: there is no update in this new XEN JS5, md5sum for boot.bin is identical to the one bundled within XEN JS3
MarkyG82 said:
OT- that's interesting as I flashed js3 with 803 unsuccessfully but it works with 512.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
guys please let me understand.... so why you are speaking about .512 and .803 .pit?
Using odin with last rom js5 from samsungfirmware I have to select just one file in pda tab, whitout .pit file.
what's wrong in my flashing way?
Be careful on updating. Double check the bootloader and Sbl.bin. We don't want the sgs to be locked, like the galaxy tab.
Sent from my GT-I9000 using XDA App
userinit said:
guys please let me understand.... so why you are speaking about .512 and .803 .pit?
Using odin with last rom js5 from samsungfirmware I have to select just one file in pda tab, whitout .pit file.
what's wrong in my flashing way?
Click to expand...
Click to collapse
.pit file is used to flash the full rom (phone + modem + csc) with re-partition flagged, basically the pit file tells odin where to write the filesystems.
Whenever you have just one file (phone), you don't need either pit or re-partition flag. This last XEN JS5 is a FULL rom.
g00ndu said:
Be careful on updating. Double check the bootloader and Sbl.bin. We don't want the sgs to be locked, like the galaxy tab.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
doublechecked boot.bin (where identical), not sbl.bin though
g00ndu said:
Be careful on updating. Double check the bootloader and Sbl.bin. We don't want the sgs to be locked, like the galaxy tab.
Click to expand...
Click to collapse
You're right !
I still have my DL mode after flashing these files ...
Wendigogo said:
You're right !
I still have my DL mode after flashing these files ...
Click to expand...
Click to collapse
Was Auto Reboot selected? Does Odin show a green success after completition?
Official thread
matticala said:
Was Auto Reboot selected? Does Odin show a green success after completition?
Click to expand...
Click to collapse
Yes for the two questions !
Wendigogo said:
You're right !
I still have my DL mode after flashing these files ...
Click to expand...
Click to collapse
Just for clarify it, Samsung's 'locked' bootloader on Galaxy Tab is not the problem about download mode... The signed bootloader also allow flashing the device later... The problem is just about the files what you can use... With Samsung's signed bootloader you can flash in the future just also signed kernels, you basically you willl not able to flash custom ROM-s in the future... You can flash firmwares with Odin, you can flash Samsung beta firmwares also, just simply could not flash custom ROM-s... This could be big problem or verly small also based on your usage habit. While I use 2.2.1 I simply not use custom ROM-s, but of course before I used... Nowadays 'signed' situations could not break my life with i9000, but with Galaxy Tab it could ... at least in the near future, as it's ROM not as good as the current i9000 versions...
Hi,
eboIa said:
Just for clarify it, Samsung's 'locked' bootloader on Galaxy Tab is not the problem about download mode... The signed bootloader also allow flashing the device later... The problem is just about the files what you can use... With Samsung's signed bootloader you can flash in the future just also signed kernels, you basically you willl not able to flash custom ROM-s in the future... You can flash firmwares with Odin, you can flash Samsung beta firmwares also, just simply could not flash custom ROM-s...
Click to expand...
Click to collapse
Thanks for explaining this ! But I couldn't understand why you couldn't donwgrade to a non-locked bootloader with Odin ? Don't have access to it ? But without access to it it couldn't be modified with latest Samsung FW via Odin ?
Hi
Still not patched to fixed.
for me it is interesting too why it is so messy about downgrade, could someone just wipe bootloader and force flash older back?
when i flash this i cant get the swedish keyboard in my phone
any ideas on this ist this the european ver i reverted back to I9000XWJM5 i kies tells me there is no update
Sorry one is not hiedemell both are odin one is full 3 file package which requires 803 pit file and other is single pda file flashable without pit or repartition from any previous stock rom
Sent from my GT-I9000 using XDA App

SGS Back to life using a jig.. now what?

I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Best option for bell users is darkys rom. For further info check darky's rom info
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
repartition yes? .pit universal?
Jason123420 said:
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
Click to expand...
Click to collapse
So the stock JL2 that I have is a .tar and .dll
I have a 512.pit from a beta 2.2 , are they different?
Did I mention boot problems too? Hanging @ Samsung, no splash ani.
I guess the .pit means yes on repartition?
Thanks
Just use the stock firmware and .pit from samfirmware.com and when Odin is open do not tick off repartirion... just put the .pit in it's spot and the tar in th's PDA part and flash
Sent from my GT-I9000 using XDA App
Now I'm no pro... I just flashed a rom once and got stuck in a boot loop and this is what worked for me
Sent from my GT-I9000 using XDA App
Recovery back but can't mount /dev/block/stl10
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Sorry man like I said I'm no pro... ide flash stock jl2 back and send it back to Samsung for repair maybe they will do something for your warranty
Sent from my GT-I9000 using XDA App
Lyon huntington said:
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Click to expand...
Click to collapse
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
It's Alive! - Can't mount /dev/block/stl10 fixed.
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
tsinc said:
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
Click to expand...
Click to collapse
Yes, do this. For repartition to work the .tar has to have dbdata.rfs, otherwise it won't work.
Then flash a speedmod kernel with odin for root/cwm and flash you're favourite custom rom
unlock&root owngrade or speedmod kernel? suggestions?
Forgot to mention that all this started after I got the phone back from Bell service after SD card failure.
I know mod methods changed with the latest firmware, as I had used the update.zip method that is now unavailable.
My phone went in unlocked and rooted
the phone came back re-locked (old code doesn't work? wtf?),
and it was unrooted w/3e recovery
Can the phone unlock code change?
Will downgrading to 2.1 make unlocking easier?
or is unlocking just as simple after a speedmod kernel with odin for root/cwm
Which is better?
downgrade the firmware to 2.1 and root using the old update.zip method or speedmod kernel?
Which kernel? (link please )
cheers
Lyon huntington said:
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
Click to expand...
Click to collapse
All you did was flash UGJL2 with no repartition and it brought your phone back?
Kops said:
All you did was flash UGJL2 with no repartition and it brought your phone back?
Click to expand...
Click to collapse
You know what....I've been trying various combinations of CSC/MODEM/PIT and everything to get this phone running again.
All I did was select a FULL UGJL2, and thats IT. NO pit, NO repartition, and it worked
The best way to revive your I9000m is to first flash JPC (a three file ROM) with 512 PIT and repartition ticked. The phone will still be in a boot loop. Then flash the JL2 PDA without repartition or PIT. The best way to go back to stock! Has always worked for me. I9000m's are not the same as other I9000's and do not flash repartition and the PDA in the same flash! Good luck!

Bell SGS bricked or saveable?

Hi,
This is my first time experimenting with flashing custom roms. I was trying to flash a custom rom onto my perfectly working newly rooted sgs (using odin), but the first rom i tried has gotten my phone to boot loop and now I don't know what to do with it. I can get to the download screen just fine and recovery mode but don't knwo what to do. Please help, I really can't afford a new phone/ don't know if samsung will let me replace it now.
Oh, the rom was the XXJVK Gingerbread which is near the top of the forums right now, if that helps at all.
I really just need my phone to be usable, I didn't expect to mess it up. Thanks again to anyone with information.
I assume you were running jl2. The problem might be because of bootloader issue.
When you were flashing gingerbread did you use pit file and repartition?
I am not a pro but If you download JL2 and flash it, should be good to go. Try not to repartition and flash without using pit file.
I did use the .pit and repartition. I'm guessing this was a no no? I'll look for jl2 and try flashing that. Might you direct me to the right download?
http://www.multiupload.com/6GRS1OWRJW
I have no idea if it will work or not. Same thing happened to me also when I was trying to flash darkys rom and I was able to open the phone after I flashed with bells original rom. Give it a try. If its a boot loop I assume its a firmware problem. You should be able to fix it. The problem might be the repartirion and pit file. I am not sure about it. Hope this helps.
Just try flashing again with boot loader update ticked in odin. I'm pretty sure that repartition and pit do nothing to the bootloader. If that doesn't work I'll add more after I shower, I stink!
Sent from my GT - I9000 running Darky's 9.5 w/ DamianGTO's Ultimate Kernel using XDA Premium App.
A bootloop = ****ed framework and/or /system/ (rom)
Flashing bootloaders will not fix the problem, they are not related at all. And if a bootloader flash fails your phone will actually be bricked.
Just flash a stock rom with odin. I recommend jl2 if you want to go official stock, js8 for fastest froyo stock or jvk for the latest leaked beta. Tick update bootloaders for jvk or jl2 flash because jvk requires jvk bootloaders and jl2 because it supposedly fixes corruption problems. Remember bootloaders are overwritten every time you flash them and us risky.
Sent from my GT-I9000 using XDA Premium App
Thanks a million guys, I did flash the stock jl2 (no .pit or partition, nor bootloader update) and the phone booted. It fed me a gajillion force closes, but i managed to connect to kies and updated it that way, so now I have a perfetly working phone again. I'll probably experiment with a few more things now that I know how to fix this.
Again, Thanks guys!

[Q] Can i Combine '(FROYO)' with a '(Gingerbread)' ? (Xchange PDA)

I have a rom that is just 1 file:
FROYO:
NEE.tar (PDA)
and another rom is 4 files:
Gingerbread:
CSC-XXJV1.tar
PDA-XWJVB.tar
PHONE-XXJVK.tar
pit512.pit
I want to mix this 2 ROM and the result is something like this:
CSC-XXJV1.tar
NEE.tar <-- It's from FROYO
PHONE-XXJVK.tar
pit512.pit
IS THAT WORK ?!
I risked and try that.
result => It's worked HoHaa
Vogie said:
I risked and try that.
result => It's worked HoHaa
Click to expand...
Click to collapse
It worked because CSC files, Modems (Phone) and .pit settings are totally firmware agnostic. All three work with both Froyo and Gingerbread interchangeably.
The pit file simply tells Odin how to set up the partitions. The CSC is the localization info and the Modem is the radio. Both the CSC and the Modem can be flashed via Recovery after install, so there was no real need to flash them at the same time, but it didn't appear to hurt. Likely what happened is they just flashed over the modem and CSC installed by the PDA file.
However, you may want to check in About to confirm the JVK modem is what you ended up with.
Thanks for info @rschenck
I went to downgrade boot loader to FroYo (from Gingerbread). and after that I understood that boot.bin and slb.bin is in PDA file.
I have this files:
boot.bin, slb.bin from JPU ROM
PDA_XWJS8_NEE
CSC_EZbase-XXJV1
PHONE_EZbase-XXJVK
I flashed by ODIN 1.7 and heimdall but it's failed (softbreak)
after that i backed to XWJS8 and i couldn't downgrade boot loader
What's wrong here ?! Do boot.bin and sld.bin is different in different ROMS ? what i need to repartition?
I'm confused sorry
Vogie said:
Thanks for info @rschenck
I went to downgrade boot loader to FroYo (from Gingerbread). and after that I understood that boot.bin and slb.bin is in PDA file.
I have this files:
boot.bin, slb.bin from JPU ROM
PDA_XWJS8_NEE
CSC_EZbase-XXJV1
PHONE_EZbase-XXJVK
I flashed by ODIN 1.7 and heimdall but it's failed (softbreak)
after that i backed to XWJS8 and i couldn't downgrade boot loader
What's wrong here ?! Do boot.bin and sld.bin is different in different ROMS ? what i need to repartition?
I'm confused sorry
Click to expand...
Click to collapse
You are over complicating your life to an amazing degree...if all you need are the froyo bootloaders there are much easier ways.
Just search in Google for ezbase and android soul...on that website are excellent instructions for flashing ezbase via odin. From there you can flash anything you want.
Don't try to invent the wheel messing with bin files.
Sent from my GT-I9000 using XDA Premium App
COME ON!!!!
There is a lot of FROYO ROMs and I know that! but I want to try everythings!
and if you not in mood to help, please Don't disapointed me :\
1. anyway, I just want to know is different between boot.bin and slb.bin in all FroYo ROMs?
2.for repartition What's need in put in ODIN ? (just pda, or pda,csc,phone) ?
3.is boot.bin and sld.bin dangerous ?
Thanks again for respond.

Need clever people

Not sure how I messed up my Bell Vibrant.
I rooted it but was stuck with 3E recovery.
So I tried to flash speedmod via Odin.
The phone went into bootloop.
So I tried Flashing Darky Rom through Odin, pit file, re-partition the works
Then it went into Recovery on reboot where I saw that the SD card wasn't mounting.
So I tried to flash dbdata.rfs.tar but this changed nothing, just the same bootloop, no mounting of the SD card again.
So what can I do? Could my flashing attempts have actually caused a hardware problem?
I have Download mode fine and via Odin everything installs but can't get past the failure to mount the SD card.
Any ideas?
Thanks!
No a flash with Odin can never cause a hardware problem.
Have you unmounted the sd card while flashing?
Bad topic subject :-/
I don't think I unmounted intentionally. Is there anywhere I can simply use Odin to clean install a whole new OS which will remount the SD Card?
I've been using Odin for a while and been flashing Roms with CWM with lots of phones. This is the wife's phone and I decided to trick it out for her for Valentines day. And I bricked it! I feel like such an ass, she's been understanding so far, but if I don't get it sorted I'm in the doghouse
http://forum.xda-developers.com/showthread.php?t=1102881
I usually get firmware from here and its always work great. The stock bell Canada one is under North America 2.3.3 ugkg3. Use a 512 pit file and repartition aswell. If this works you can always upgrade the pda with jw1 2.3.6 and root later but sounds like you just want to get it working first.
Sent from my GT-I9000 using xda premium
Thanks so much. I'll check it out and report back.
vanisleryan - thanks so much. I really appreciate it. It's all running fine again.
What is the safest way to root and overcome the 3E recovery block so I can just put roms on the SD card and flash from recovery mode?
Thanks again
Rooting depends on what firmware you used. You need to find the appropriate kernel and flash it in odin as a pda.
Sent from my GT-I9000 using xda premium
I have a bell Canada galaxy s also and I'm running jw1 2.3.6 as my pda, kg3 as my phone, and kg3 as my csc. You can mix and match the files so if you download the jw1 firmware from the link I gave you, just use the pda file and use the phone and csc files from the kg3 firmware. After that is installed download the file at the bottom of the first post in this link. http://forum.xda-developers.com/showthread.php?t=1112908
You want the one for jw1, one has a "bm" on it one doesn't, you want the one that doesn't. It does not need to be extracted. Flash in odin as pda. Then you will be rooted. I don't know if that kernel contains the cwm apk, you may need to do a search for it. As you will need cwm to install custom roms. Pretty sure it's in that thread somewhere. Just do a search.
Sent from my GT-I9000 using xda premium

Categories

Resources