hi people, this is my first post, so please be nice!
i've had the galaxy s and it's been rooted for a while, with a custom MIUI rom installed (not sure which one it is... but it's NOT the 2.3.4 one in the development section, it's version 1.7.1). i want to switch roms now, since the battery life is terrible, though the rom is great.
i've been looking through the development section for a new rom to flash, but a lot of them require some change to the firmware, bootloader, etc. the problem is, i don't know what bootloader, firmware, etc version i have
i rooted this phone when it was on STOCK 2.1 eclair ( i know, old), and i did flash a 2.2 rom before flashing this version of MIUI (2.3.4).
do roms change the bootloader? i came from an HTC device, so i don't really have an idea on whats the deal with the Galaxy S. HTC devices were a LOT easier (IMO).
i did a google search, but it didn't really help... O_O
so, if anyone can point me in the right direction, i will be VERY grateful.
thanks
'Settings -> About Phone' will show you your current firmware, etc.
Bootloaders usually only change for major revisions. If you're on Froyo (2.2) and want to flash a Gingerbread (2.3) firmware, you would need to upgrade from Froyo to Gingerbread bootloaders. If you're flashing from 2.3.3 to 2.3.4, you won't need to upgrade bootloaders. Flashing is done using the program Odin or Heimdall (or using a flashable zip via recovery, such as Clockworkmod Recoevery). Heimdall has the "flash bootloaders" right there for you to tick/untick, if I recall correctly. Some firmware files (pit, tar, etc—the files you flash with Odin) have bootloaders, some do not. I can't recall if there's an option within Odin to specify whether to flash the bootloaders or not. Either way, if you flash to an AOSP Gingerbread firmware, it's likely the bootloaders will be included.
So basically, just grab Odin/Heimdall and the necessary firmware files, and you're good to go! But before you do that, verify that download mode (volume down + home + power) works. If it does not, you'll need to get it working before you start flashing—otherwise you risk bricking your device.
If you have anymore questions, feel free to ask. We're here to help.
upichie said:
'Settings -> About Phone' will show you your current firmware, etc.
Bootloaders usually only change for major revisions. If you're on Froyo (2.2) and want to flash a Gingerbread (2.3) firmware, you would need to upgrade from Froyo to Gingerbread bootloaders. If you're flashing from 2.3.3 to 2.3.4, you won't need to upgrade bootloaders. Flashing is done using the program Odin or Heimdall (or using a flashable zip via recovery, such as Clockworkmod Recoevery). Heimdall has the "flash bootloaders" right there for you to tick/untick, if I recall correctly. Some firmware files (pit, tar, etc—the files you flash with Odin) have bootloaders, some do not. I can't recall if there's an option within Odin to specify whether to flash the bootloaders or not. Either way, if you flash to an AOSP Gingerbread firmware, it's likely the bootloaders will be included.
So basically, just grab Odin/Heimdall and the necessary firmware files, and you're good to go! But before you do that, verify that download mode (volume down + home + power) works. If it does not, you'll need to get it working before you start flashing—otherwise you risk bricking your device.
If you have anymore questions, feel free to ask. We're here to help.
Click to expand...
Click to collapse
when i go to settings/about phone it shows this:
model number: GT-19000
android version: 2.3.4
baseband version: 19000XXJVK
kernel version: [email protected] #1
build number: MIUI 1.7.1
so how do i know what my bootloader version is?
thanks for your help, still confused though...
Okaham said:
when i go to settings/about phone it shows this:
model number: GT-19000
android version: 2.3.4
baseband version: 19000XXJVK
kernel version: [email protected] #1
build number: MIUI 1.7.1
so how do i know what my bootloader version is?
thanks for your help, still confused though...
Click to expand...
Click to collapse
Unfortunately, you won't be able to tell what bootloader you have. Since you're running 2.3.4, which is Gingerbread, I'd assume you have a Gingerbread bootloader—but if you flashed from Froyo to MIUI, it's likely you only have a Froyo bootloader.
If you're currently running MIUI, the best way to change to another custom ROM would be to flash (via Odin/Heimdall) to the latest AOSP Gingerbread firmware (including the bootloaders), and then flash via recovery (using a flashable zip) to the custom ROM of your choosing—unless they have a package to flash using Odin.
upichie said:
Unfortunately, you won't be able to tell what bootloader you have. Since you're running 2.3.4, which is Gingerbread, I'd assume you have a Gingerbread bootloader—but if you flashed from Froyo to MIUI, it's likely you only have a Froyo bootloader.
If you're currently running MIUI, the best way to change to another custom ROM would be to flash (via Odin/Heimdall) to the latest AOSP Gingerbread firmware (including the bootloaders), and then flash via recovery (using a flashable zip) to the custom ROM of your choosing—unless they have a package to flash using Odin.
Click to expand...
Click to collapse
i was on the stock 2.1 eclair galaxy s rom, and then i downloaded and flashed the baldoz rom, which used to be 2.2 (not sure if it still is). did that custom rom change my bootloader? so if i had the stock eclair 2.1 bootloader before, wouldn't i still have that bootloader right now? since you said MIUI doesn't change the bootloader?
Okaham said:
i was on the stock 2.1 eclair galaxy s rom, and then i downloaded and flashed the baldoz rom, which used to be 2.2 (not sure if it still is). did that custom rom change my bootloader? so if i had the stock eclair 2.1 bootloader before, wouldn't i still have that bootloader right now? since you said MIUI doesn't change the bootloader?
Click to expand...
Click to collapse
If you used a flashable zip to flash via CWM, your bootloaders wouldn't have been changed. If you flashed via Odin, they may have been, depending on whether or not bootloaders were included in the files. (Although, for the most part, I don't believe many custom ROMs would include bootloaders, if any at all.)
Either way, your current bootloaders shouldn't matter much. I would still advise upgrading to Gingerbread bootloaders, as per the custom ROMs requirement (which I'm assuming most up-to-date ROMs will require, or at the very least recommend. For example, CM7 can run off of Froyo bootloaders or Gingerbread bootloaders, but battery life is negatively affected if you're using Froyo bootloaders.)
upichie said:
If you used a flashable zip to flash via CWM, your bootloaders wouldn't have been changed. If you flashed via Odin, they may have been, depending on whether or not bootloaders were included in the files. (Although, for the most part, I don't believe many custom ROMs would include bootloaders, if any at all.)
Either way, your current bootloaders shouldn't matter much. I would still advise upgrading to Gingerbread bootloaders, as per the custom ROMs requirement (which I'm assuming most up-to-date ROMs will require, or at the very least recommend. For example, CM7 can run off of Froyo bootloaders or Gingerbread bootloaders, but battery life is negatively affected if you're using Froyo bootloaders.)
Click to expand...
Click to collapse
thank you so much!
and can you please give me the links or something on how to flash the gingerbread radio in ODIN?
THANK YOU
Okaham said:
thank you so much!
and can you please give me the links or something on how to flash the gingerbread radio in ODIN?
THANK YOU
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1139050
I googled it for you, and while I only skimmed that, it appears to be a very thorough tutorial.
Have fun! And thanks for the thanks.
upichie said:
http://forum.xda-developers.com/showthread.php?t=1139050
I googled it for you, and while I only skimmed that, it appears to be a very thorough tutorial.
Have fun! And thanks for the thanks.
Click to expand...
Click to collapse
thank you kind sir
this changes the bootloader to a 2.3 gingerbread one right?
Okaham said:
thank you kind sir
this changes the bootloader to a 2.3 gingerbread one right?
Click to expand...
Click to collapse
Assuming the files you use to flash (via Odin/Heimdall) include the bootloaders, but it's likely they will.
Hello,
I hope it's not the wrong section, but the others are I9000.
I want to flash an I9001. The phone is on 2.3.3 I though.
I've root the phone, now I can go to 2.3.6 by flashing a rom in recovery or do i need to go to 2.3.6 first?
Greetz,
ikkuh007 said:
Hello,
I hope it's not the wrong section, but the others are I9000.
I want to flash an I9001. The phone is on 2.3.3 I though.
I've root the phone, now I can go to 2.3.6 by flashing a rom in recovery or do i need to go to 2.3.6 first?
Greetz,
Click to expand...
Click to collapse
You need to flash (for example) KQ7 with Odin, this updates the whole base of the rom, most new roms are build on KQ7 base so I think that's the right one for you
btw this is the wrong section, i9000 Q&A is the right section
I think we go for broodrom.
But it's important to get first to 2.3.6 stock? Or can we flash the rom directly by odin?
As an ODIN stock ROM also includes modem binaries that we cannot flash over recovery, it is a good idea to get to the latest stock ROM with ODIN and then start with custom ROMs over FeaMod recovery (it's basically CWM). If you have already the latest stock ROM on your 9001, you can use whatever method you prefer.
I think recovery is quicker and easier to use as you don't need a pc near you.
And which last stock 2.3.6 we can flash the best? We live in Holland..., don't know it is important?
ikkuh007 said:
And which last stock 2.3.6 we can flash the best? We live in Holland..., don't know it is important?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1533029
broodplank1337 said:
http://forum.xda-developers.com/showthread.php?t=1533029
Click to expand...
Click to collapse
Thank you!
Just rooted my Samsung Galaxy S GT-I9000M (Bell) using Root Unlock. Have superuser and ROM Manager installed (recently found that ROM manager incompatible for flashing new ROM's) Error msg - E: failed to verify whole file signature
My understanding now is that I would be better rooting using CF-Root with a customized kernel for my Gingerbread 2.3.3 build (haven't found one yet but see several options for 2.3.5)
Question: Assuming that I can find and install an appropriate kernel via Odin, do I need to restore my phone to OEM (unrooted) before I can head down the path of a CF-Root or can I install a new kernel on my phone as it exists in its rooted condition?
Any info or direction would be greatly appreciated.
If you want to flash a new ROM anyways, you can just flash a kernel via Odin. You will have to wipe everything before the ROM flash.
Sent from my Gameboy Color
BlueFlame4 said:
If you want to flash a new ROM anyways, you can just flash a kernel via Odin. You will have to wipe everything before the ROM flash.
Sent from my Gameboy Color
Click to expand...
Click to collapse
Do I need a kernel specific to my firmware version? Or can I install say, a Gingerbread kernel of a different version like 2.3.5? I see several options for downloads for this one, but not for the 2.3.3 version that I have currently installed. There was one link I found for a 2.3.3 kernel but it was no longer available on megaupload.
If I can and do opt for another kernel, when you say wipe everything... that includes the partition as well?
Thanks much for the reply, I'm really just getting started with all the in's and out's of rooting.
Thusfar, it seems to be a bit intensive for this particular Galaxy model compared to the all the success stories I'm seeing on later phones and OS versions.
Eyes
Have tried following these instructions?
[HOWTO] Flashing CWRecovery to i9000m & upgrade to ICS AOSP 4.x ROM from any version
Worked for me, a while back.
I have tried to go back to a stock rom so warranty is valid, but not sure if all is okay
ANDROID VERSION 2.3.3
BASEBAND VERSION S5830XWKP7
KERNEL VERSION [email protected]#1
BUILD NUMBER GINGERBREAD.XWKPO
can somebody tell me if this is all stock? not sure about kernal, I want to take phone back to shop for repair. Any help very appreciated
If you flashed via ODIN then yes it's stock.
Boot into recovery check you have the stock recovery too.
nevis said:
If you flashed via ODIN then yes it's stock.
Boot into recovery check you have the stock recovery too.
Click to expand...
Click to collapse
Thanks,
Hi!. I recently flashed my froyo Ace to LeWa ROM but since I need to revert back and install the stock ROM in GB.Can anyone redirect me to the appropriate post please. Didn't do backup for original rom as I thought froyo is much outdated for a armv9. Thanks in advance.
tennoemi said:
Hi!. I recently flashed my froyo Ace to LeWa ROM but since I need to revert back and install the stock ROM in GB.Can anyone redirect me to the appropriate post please. Didn't do backup for original rom as I thought froyo is much outdated for a armv9. Thanks in advance.
Click to expand...
Click to collapse
Flash stock firmware through odin. READ, seriously, READ the stickies. It's all there.
hi guys
last year, i installed x-bean 3.0 on my i9000. i'll not bore you with the details, but i have a need to revert back to a stock rom. i've downloaded a couple of stock roms from sammobile and used odin v1.85 to restore them to the phone and wiped data/factory reset, but now the phone is in a boot loop at the samsung splash screen
not sure if i have to do something with the bootloader or the kernel? any ideas?
thanks
model number: gt-i9000
android version: 4.1.2
baseband version: i9000xxjvt
kernel version: 3.0.45-semaphore_jb_2.3.0
build number: x-bean 3.0
Hey,
Did you flash in dbsdata.rfs.tar? Going from unofficial to stock requires this file as well... Flash it in via Odin and it should stop the bootloops.
Sent from my GT-I9000
Soryuu said:
Hey,
Did you flash in dbsdata.rfs.tar? Going from unofficial to stock requires this file as well... Flash it in via Odin and it should stop the bootloops.
Sent from my GT-I9000
Click to expand...
Click to collapse
I have been meaning to ask... WTF is this sh*t? I have gone back to stock numerous times, but I have never heard of this file. Is it a specific requirement for some of the custom roms?
snapper.fishes said:
I have been meaning to ask... WTF is this sh*t? I have gone back to stock numerous times, but I have never heard of this file. Is it a specific requirement for some of the custom roms?
Click to expand...
Click to collapse
Its because the data partitions and so on (I think) in custom roms like CM, AOKP etc. are different from the stock roms. The data partitions from the unofficial roms are incompatible with the stock roms and so you get bootloops. dbsdata.rfs fixes that problems by fixing those partitions. Or something like that.
Sent from my GT-I9000