I have moved from froyo to gingerbread at last and despite having a few little issues I am happy with the end result, however, I did find some of the 'instructions' surrounding the process both on here and other sites to be extremely vague, one of the main points of issue was regards ensuring you have a specific version fully installed before you commit to a custom rom.
I understand this relates to the installation of newer bootloaders that are able to support the new gingerbread code as well as older froyo.
I then found a post that shows how to avoid the full installs and only update the bootloader section itself, this has been tried and tested and accepted as working.
I have found that some posters have only succeeded with version xxx, some say to only update to the latest yyy, understandable and easy to follow....
But does anyone know of a location for the bootloaders ONLY, to use via odin?
And as an aside to that, how to check the actual version of the bootloader?
From my HTC days, it came up on a screen during flashing etc, but I have not seen any like that on the SGS.
I have checked the usual places, but they only seem to contain kernels and modems, not the bootloaders.
Any help apprecated
Cheers
Here are the standalone bootloaders for Froyo and Gingerbread put together by Nitr8 : http://forum.xda-developers.com/showthread.php?t=1089989
I don't know of anyway to check your bootloader version but if your running GB fine you know your on a Gingerbread bootloader. Froyo works with GB bootloaders so the only reason you may want to change them is if your moving to a CM7 rom which requires the froyo one. This thread tends to explain everything quite well: http://forum.xda-developers.com/showthread.php?t=1011701
Hope this helps
Shrapnel2 said:
Here are the standalone bootloaders for Froyo and Gingerbread put together by Nitr8 : http://forum.xda-developers.com/showthread.php?t=1089989
I don't know of anyway to check your bootloader version but if your running GB fine you know your on a Gingerbread bootloader. Froyo works with GB bootloaders so the only reason you may want to change them is if your moving to a CM7 rom which requires the froyo one. This thread tends to explain everything quite well: http://forum.xda-developers.com/showthread.php?t=1011701
Hope this helps
Click to expand...
Click to collapse
Sure does, my reason to determine the bootloader version is as follows, I was looking to try out an alternate rom and it said you MUST have a JVO bootloader or the rom would have issues.... hence looking for versions as such.
I did have an issue and before I reported back, i thought to locate the JVO bootloader and install it first and see if the problems continued...
Cheers
Yeah, the easiest way to acquire specific bootloader is probably to download an entire rom, eg JVO including bootloaders
Related
I need some help understanding this version-ing info.
I have been looking through as many FAQ's as I could find, but no where can I find an explanation.
I would like to know what JPA/JP6/JP5 etc all mean? I think these are the version's of Froyo, but I'm unsure?
I'm looking to install the Doc Froyo ROM, and I've downloaded ADJP5 V8, however there are other versions there, and I have no idea which the newest one is, and therefore which one I should get. I see people talking about this JP(whatever), but I don't understand it..
On my I9000, I've got Eclair, and my PDA is I9000DTJG4, so is JG4 the version of Eclair that I'm running?
Thanks
Denno
Oh I also want to apply CF-Root v1.2 (http://forum.xda-developers.com/showthread.php?t=788108), (as it is a pre-requisite for Doc's ROM), but I have no idea which version I should download...
JPA, JP6 etc are all versions of froyo.
To my limited understanding, they are from different build branches, so you can't really tell which is the newest short of looking the build date
Anyway, JG4 is eclair, and should have the 2e recovery (which the CF-root gives) already. Just boot into recovery mode and see the top right hand corner, and if it does say that, you can skip the CF-root step, and just use clockwordmod.
(You still need to get it rooted though iirc, so if you haven't done that, look around for the eclair rooting threads).
As the title of the thread says, I read the guide to install JVK/JVA/JVB and it says that before flashing I must have my phone unlocked.
When it was only JVK in that thread, I didn't see this note so I flashed it. That was 2 weeks ago and I haven't had any issue with the Network.
I haven't unlocked my phone and I don't want to because I read the guide for unlocking and I can't use adb.
So, can I flash JVB now? Are there any issues that my phone can suffer? I asked in the thread this question but nobody answered me, so that's why I made a new thread.
I'm using a JVB based gingerbread rom without any issues and never unlocked it... In fact this is the first time I heard this...
Sent from my GT-I9000 using XDA App
Warning:
*These firmwares are for International I9000 Galaxy S version, your device must be unlocked before flashing these firmwares.
So, I'm waiting for other opinions...
AS they are unofficial firmwares i guess instruction might be for safety .
Official updates via Kies when 2.3 is released will not need unlocked phones .
jje
flash and see yourself !
I flashed a phone with no root or unlock from 2.1 to 2.3.3 works
I had a hard time trying to root 2.1 and got it boot looping so the last a tempt was a full flash of jvk work and saved the day.
I then was able to use cf-root 3.1 to get root and app from the market to unlock.
I'm ready to do it, but what issues can it cause? I heard something about a code at the first boot that you must enter but I don't know exactly.
Can I downgrade to 2.2.1 stock for example if I have problems?
Edit: I flashed JVB without having any issue. Thanks for the help anyway, I was pretty doubtful about what can happen. All the things work.
Cheers!
typo on the title, i meant New captivate user needs help LOL
Hey guys,
I've gotten myself a Rogers Captivate (SGH-I896) running Continuum v5.5.
Model number states GT-I9000 with baseband I9000TDVJP9, Build GINGERBREAD.XXJVO
I'm not a total noob since i have a Nexus S and used to own a t959 vibrant, but seems like the captivate is confusing the hell out of me lol. Here are a few questions i hope the community could help me out with
1. Boot up screen states GT-I9000, so i guess this means this was flashed with GB Bootloader? i'm assuming we dont have official Gingerbread on the captivate hence the need for the GB Bootloader (Please correct me if i'm wrong)
2. i have used ODIN on my vibrant many times. Now do i need to download a specific version for the captivate or is ODIN the same for all Galaxy S phones?(Please note that i have the AIO Vibrant Toolbox so ODIN version is the one that comes with it)
3. If i want to change ROMS, to lets say the Sensation ROM, can i flash it using CWR or do i have to change bootloaders first? and Can someone kindly tell me which ROM can i just flash on top of my current ROM.
4. If i want to start all over again and get back to stock, what are the steps i need to make. can i just put it on download mode and Odin back to stock the same way i used to do it on the vibrant? or do i have to change bootloaders first.
5. Lastly, is there a big difference between the AT&T and the Rogers Captivate? Am i able to flash all the custom ROMS here or do i have to find specific ones that will only work on my version?
You may have noticed that the bootloaders are my main cause of worry, coz i know that a mishap with those would cause a hard brick. Hope someone could give me a few minutes of their time to help a captivate noob get started on flashing these amazing ROMS on my captivate. Thank you!!
VibrantWind said:
typo on the title, i meant New captivate user needs help LOL
Hey guys,
I've gotten myself a Rogers Captivate (SGH-I896) running Continuum v5.5.
Model number states GT-I9000 with baseband I9000TDVJP9, Build GINGERBREAD.XXJVO
I'm not a total noob since i have a Nexus S and used to own a t959 vibrant, but seems like the captivate is confusing the hell out of me lol. Here are a few questions i hope the community could help me out with
1. Boot up screen states GT-I9000, so i guess this means this was flashed with GB Bootloader? i'm assuming we dont have official Gingerbread on the captivate hence the need for the GB Bootloader (Please correct me if i'm wrong)
2. i have used ODIN on my vibrant many times. Now do i need to download a specific version for the captivate or is ODIN the same for all Galaxy S phones?(Please note that i have the AIO Vibrant Toolbox so ODIN version is the one that comes with it)
3. If i want to change ROMS, to lets say the Sensation ROM, can i flash it using CWR or do i have to change bootloaders first? and Can someone kindly tell me which ROM can i just flash on top of my current ROM.
4. If i want to start all over again and get back to stock, what are the steps i need to make. can i just put it on download mode and Odin back to stock the same way i used to do it on the vibrant? or do i have to change bootloaders first.
5. Lastly, is there a big difference between the AT&T and the Rogers Captivate? Am i able to flash all the custom ROMS here or do i have to find specific ones that will only work on my version?
You may have noticed that the bootloaders are my main cause of worry, coz i know that a mishap with those would cause a hard brick. Hope someone could give me a few minutes of their time to help a captivate noob get started on flashing these amazing ROMS on my captivate. Thank you!!
Click to expand...
Click to collapse
1. Yes, You flashed the i9000 GB Bootloaders that are compatible with our phone. If you look on the forums there is a one-click for the kf1 bootloaders that are made for our phone and much harder to brick.
2. There is different odin oneclicks for the captivate and different files for odin. Not all galaxy s files are compatible with all the different galaxy s devices. Be sure to download captivate specific files. If they are not captivate specific make sure they are known to work with our device, the safest way to do this is to stick to files on the captivate forums.
3. I typically 1-click back to stock jf6 and follow steps to flash the new rom when I want to flash a new rom. Be sure not to use the old 3 button fix and I would be hesitant to do this without a jig ready if my 3 button didnt work out of the box.
4. Odin 1-click JF6(NOT the 3 button fix) should have the primary bootloaders, it has always reflashed the eclair/froyo bootloaders for me and seems to be the best way to restore factory settings, from there its easy to update using Kies or to flash a custom rom through CWM without even rooting. All you need is to install it with an update.zip you can find on the forums easily. Edit: If you are trying to get to stock for warranty exchange you'll have to find rogers specific stock roms which are on the captivate android development forums. AT&T Roms should work with rogers with proper APN settings though(at least thats my understanding. I am on AT&T and have an i897)
5. My understanding is the phones are the same hardware wise just the APN settings differ. I may be mistaken though and you may want another more informed Rogers user to respond to this question.
Thanks Xijar
Sent from my Google Nexus S using XDA Premium App
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.
So I was trying to root my i9000m and I read a forum post that advised me to update the soft key fw before doing so... little did I know I was on a custom fw already so it broke my soft key functionality. I've read a few posts that have instructions to fix the problem, by rooting the stock fw for the model and updating soft key fw before rooting again. problem is my phone was originally on FROYO and I can't locate the original file anywhere. can anybody point me to a file dl for the stock fw, or maybe someone has the file on their computer they would be willing to share? it's a bit frustrating not having the keys to go back, and i can't use certain apps due to not having a menu key..
If you don't find what you are looking for, try updating to a custom ROM that includes a Navigation Bar, as shown in the attached pic.
What's the ROM in the screenshot?
It's SlimBean 3.1 = Jelly Bean 4.1.2
With this ROM you can have up to 5 soft keys in the Navigation Bar.
This way you could care less about the phone's soft keys.
There are sites such as this one where you can find official Samsung roms
http://www.sammobile.com/firmware/?page=3&model=GT-I9000M&pcode=0&os=1&type=1#firmware
If you did manage to root your phone, you could also try this: http://forum.xda-developers.com/showthread.php?t=1832638
Thanks nyloncrack, I didn't know that there were roms that included a nav bar! I will try that, and Marshian I've gotten the firmwares from sammobile but apparently my original firmware for the i9000m (Canada) was 2.2.1, which I have found, but apparently not found the proper version of the rom that came stock with my phone. I believe it was 2.2.1 froyo. I am currently running 2.2.1 froyo.xwjsd which seems to not be the correct version.
There's a thread here with a couple of roms for the I9000m, other than that I'm afraid I can't really be of any use to you. Good luck though!
Marshian said:
There's a thread here with a couple of roms for the I9000m, other than that I'm afraid I can't really be of any use to you. Good luck though!
Click to expand...
Click to collapse
I got the jl2 rom and reflashed and it worked! I downloaded UGJL2/UGJL2/BMCJL2/Sbl (MultiCSC): reflashed with pda, phone, and csc checked and then updated the touchkey firmware and voila! I got them from the same link you posted, just before you posted it, bang on Marshian!
It was actually really simple once I wrapped my head around it, now I just need to update to a newer, faster custom rom! now let's see if I can't get this rooted and unlocked again without messing it up . any suggestions for a good, bug free rom? I haven't looked into it too much yet but i hear ice cream sandwich and jellybean are recommended for my device?
trickassfoo said:
I got the jl2 rom and reflashed and it worked! I downloaded UGJL2/UGJL2/BMCJL2/Sbl (MultiCSC): reflashed with pda, phone, and csc checked and then updated the touchkey firmware and voila! I got them from the same link you posted, just before you posted it, bang on Marshian!
It was actually really simple once I wrapped my head around it, now I just need to update to a newer, faster custom rom! now let's see if I can't get this rooted and unlocked again without messing it up . any suggestions for a good, bug free rom? I haven't looked into it too much yet but i hear ice cream sandwich and jellybean are recommended for my device?
Click to expand...
Click to collapse
Good to hear!
I've got the I9001 so I don't really know what kind of roms are available for you, but in my experience for my own phone ICS is currently the best trade-off in features and stability. JB is still quite new and not fully ported yet, while ICS is nearly bug-free. It could be different for your model, that's just my two cents. Either way, as long as you don't brick your phone you could always try out a couple of roms and see what you like best. The only downside is changing a major version requires a full wipe.
I used this to go from gb to ics.
[HOWTO] Flashing CWRecovery to i9000m & upgrade to ICS AOSP 4.x ROM from any version
This way your i9000m becomes a i9000 for searching out new ROMs.
For whichever ROMs (ICS or JB) you'll always need to flash the KG3 modem.
nyloncrack said:
I used this to go from gb to ics.
[HOWTO] Flashing CWRecovery to i9000m & upgrade to ICS AOSP 4.x ROM from any version
This way your i9000m becomes a i9000 for searching out new ROMs.
For whichever ROMs (ICS or JB) you'll always need to flash the KG3 modem.
Click to expand...
Click to collapse
I've tried using that guide before but the JVP link is invalid. i did a quick google search am i just looking for Gingerbread? because I have a file already on my computer titled "CF-Root-XX_OXA_JVP-v3.7-CWM3RFS.tar"
Yes, that will work.
Looking at my notes from back then I actually also used:
CF-Root-XX_OXA_JVT-v4.3-CWM3RFS, and
CF-Root-XX-_OXA_JVU_2.3.6-v4.3-CWM3RFS
They were just later versions of GB.
JVU was Samsung's appeasement to i9000 users when they were told ICS wasn't coming. Had a couple of ICS features; window dressing.
Remember to make a full backup before touching anything this time
I've been trying for hours but I cannot for the life of me get windows to recognize the device in download mode. It was working fine until i updated the rom, then intermittently, then i updated the rom again and it has stopped working. i've uninstalled the drivers, tried with debugging on and off, restarted windows, installed the newest version of kies, bought a new usb cable, to no avail. this is maddening. is there a better alternative to do this on my mac? I'm using a virtual system running windows but I'm positive that isn't the problem, since it was working great before on vmware, and parallels. any ideas? I'm about a half hour away from selling this device and going back to the iphone haha.
so basically my question now is how do I downgrade back to the original firmware, so I can put this nightmare behind me? I had it unlocked and rooted on gingerbread before... don't ask me how it took many many hours. now the device isn't even being recognized in kies. If I don't get this figured out soon i'm flipping this b*tch for an iphone 4, because I do appreciate the one touch jb/unlock. I've literally wasted days of my life trying to figure this out and it doesn't seem to be getting me anywhere. too bad because I really appreciate the android system and all its capabilities but I don't have the time to waste on stuff like this
Another Edit! So, after fussing and fiddling, I decided to try one more time, I swear, I was actually going to give up at this point if it hadn't worked. so basically I removed kies, loaded the driver i was using, which was 1.3.450.0 and it didn't work, so I loaded 1.5.5.0 and it connected! My guess is that after updating the rom the driver was outdated, but I figured kies would give me the most up to date driver, seems it didn't oh well, I'm almost afraid to load ics since I've worked so hard and wasted so much time up to this point, but i've come this far...
one more edit, the kg3 modem kept crashing odin on me so I had to stick with the jl2 that was flashed earlier.. which doesn't give me network access, I'll try to find another file but is there any reason odin should be crashing like that due to this particular file?
hahaha, shouldn't speak too soon, jl2 works after reboot, should I update my modem firmware now, and what is recommended for my system {2.3.4} kernel {2.6.35.7} and if i flash to ics will I need kg3? Thanks for all the help with this seemingly never ending process