Related
I have seen a few threads about how to get into recovery mode with the captivate...but why is there no [HOW TO] thread on it? I stumbled across it tonight and flashed it with odin and man it is snappy and quick...no downsides yet besides the fact that the home button is basically just another back button. The GPS gets an IMMEDIATE fix on my EXACT location. I hope I dont sound like a moron asking this...but it has been bugging me lol
morganblackstone said:
I have seen a few threads about how to get into recovery mode with the captivate...but why is there no [HOW TO] thread on it? I stumbled across it tonight and flashed it with odin and man it is snappy and quick...no downsides yet besides the fact that the home button is basically just another back button. The GPS gets an IMMEDIATE fix on my EXACT location. I hope I dont sound like a moron asking this...but it has been bugging me lol
Click to expand...
Click to collapse
A number of us have already installed it and messed with it... it's got some okay improvements, not everyone has had the same GPS luck you've had though. On top of that some folks are still gun-shy from the JPC disaster
Zilch25 said:
A number of us have already installed it and messed with it... it's got some okay improvements, not everyone has had the same GPS luck you've had though. On top of that some folks are still gun-shy from the JPC disaster
Click to expand...
Click to collapse
+1 to JPC disaster! I will wait for a "final" 2.2 for at least the galaxy s before I try it
Kaik541 said:
+1 to JPC disaster! I will wait for a "final" 2.2 for at least the galaxy s before I try it
Click to expand...
Click to collapse
Well some people are claiming JPH is final... which if true- is tragic. It's snappy but rather bug-laden, just use it for a couple days, especially if you use exchange, you'll run into a rather huge bug pretty quick
Zilch25 said:
Well some people are claiming JPH is final... which if true- is tragic. It's snappy but rather bug-laden, just use it for a couple days, especially if you use exchange, you'll run into a rather huge bug pretty quick
Click to expand...
Click to collapse
I'll wait for word from Samsung before I flash a 2.2
unless somehow wes garner pulls a fast one and slides cyanogenmod out on us without the 2.2 source somehow
Kaik541 said:
I'll wait for word from Samsung before I flash a 2.2
unless somehow wes garner pulls a fast one and slides cyanogenmod out on us without the 2.2 source somehow
Click to expand...
Click to collapse
I'm more looking forward to the I9000 2.2 source than I am an official Captivate release =P They've so ineptly assembled Froyo i'd rather wait for Cyanogen or eugene to vanilla it
I have been messing with JPH for awhile, can't get good reception with it and can't seem to be able to flash a different modem.bin to it so I'm done with it for now.
irtehun said:
I have been messing with JPH for awhile, can't get good reception with it and can't seem to be able to flash a different modem.bin to it so I'm done with it for now.
Click to expand...
Click to collapse
You can flash the UGJH2 modem if you use the pit to map it Least that's how I did it
Zilch25 said:
I'm more looking forward to the I9000 2.2 source than I am an official Captivate release =P They've so ineptly assembled Froyo i'd rather wait for Cyanogen or eugene to vanilla it
Click to expand...
Click to collapse
what I like is the proof from xcalibur about how quickly you can take an i9000 kernel and make it work with the captivate (ideally that means the kernel can be built off the same source with just slightly modified config files and repointing the differences to the proper place).
that means we could arrive at a 2.2 kernel for the Captivate (unlikely, but possible) with just the 2.2 i9000 release
Zilch25 said:
You can flash the UGJH2 modem if you use the pit to map it Least that's how I did it
Click to expand...
Click to collapse
Which pit?
irtehun said:
Which pit?
Click to expand...
Click to collapse
zilch, correct me if I'm wrong, but 512.pit would be the one to use for modem mapping.
I think 803 is only required for flashing JPC (but yuck, stay away)
Kaik541 said:
zilch, correct me if I'm wrong, but 512.pit would be the one to use for modem mapping.
I think 803 is only required for flashing JPC (but yuck, stay away)
Click to expand...
Click to collapse
n/m found it.
irtehun said:
u talking the JH2 for the captivate? I'm not finding a UGJH2 only UCJH2
Click to expand...
Click to collapse
well there a UGJH2 modem for the i9000 which will give you HSUPA. UCJH2 is a captivate firmware with a non-HSUPA modem (but was designed for our hardware)... JH2 from the i9000 though is from a phone that uses the same frequency as ours though I believe, so it should work the same but with HSUPA enabled
irtehun said:
Which pit?
Click to expand...
Click to collapse
i believe with 2.2 you need 513
I used the 803 pit, but I don't think it ultimately matters, and yes you MUST use the UGJH2 modem. JG8 does NOT WORK, for some reason it isn't Froyo capable but the newer JH2 one is
513 pit shouldn't be necessary for any of the new Froyos, only 512 or 803, though I'm fairly certain they both work
Zilch25 said:
I used the 803 pit, but I don't think it ultimately matters, and yes you MUST use the UGJH2 modem. JG8 does NOT WORK, for some reason it isn't Froyo capable but the newer JH2 one is
Click to expand...
Click to collapse
Ok thanks will try that tomorrow. did u root it when u had it running?
whats the jpc disaster...? lol the only problem im having right now is trying to root the damn thing so i can nandroid it...and the whole home key issue...and the screen not shutting off in a call lol
irtehun said:
Ok thanks will try that tomorrow. did u root it when u had it running?
Click to expand...
Click to collapse
Yup, but in order to do so you have to flash in a Captivate kernel, use button combos to get into recovery, run the update.zip, and flash back to the JPH kernel before booting fully- it's a pain
morganblackstone said:
whats the jpc disaster...? lol the only problem im having right now is trying to root the damn thing so i can nandroid it...and the whole home key issue...and the screen not shutting off in a call lol
Click to expand...
Click to collapse
Home key and prox sensor (screen not turning off on call) can't be resolved, they're kernel issues. Don't bother pushing files, all you'll do is cause graphical errors and touch screen problems- trust me. I know.
Put the root update on your /sdcard, flash stock captivate kernel, use button combos, install update package, then reflash JPH kernel (search the I9000 boards, they've got a thread about rooting that has a JPH kernel in it).
morganblackstone said:
whats the jpc disaster...? lol the only problem im having right now is trying to root the damn thing so i can nandroid it...and the whole home key issue...and the screen not shutting off in a call lol
Click to expand...
Click to collapse
Zilch25 said:
Home key and prox sensor (screen not turning off on call) can't be resolved, they're kernel issues. Don't bother pushing files, all you'll do is cause graphical errors and touch screen problems- trust me. I know.
Put the root update on your /sdcard, flash stock captivate kernel, use button combos, install update package, then reflash JPH kernel (search the I9000 boards, they've got a thread about rooting that has a JPH kernel in it).
Click to expand...
Click to collapse
I also think the "JPC disaster" we're referring to was the forcing it to show up as a korean phone (and therefore unable to receive later updates) and the thrashing of the els (I think) folder which contained our unlock information. causing even carrier locked phones with the correct carrier SIM cards to be non-functional.
caught a lot of people off guard with an essentially unusable phone if they didn't have the unlock code already. basically it was a terrifying moment for a lot of i9000 users (I think even Zilch lost a phone in the process of playing with JPC?)
Im a little confused, hoping someone here can shed some light for me... what is the current firmware? can someone who knows give me a quick rundown of the versions and (if its not against forum rules) links to the firmwares? i gotta return my phone to stock but cant seem to find consistent information anywhere.
Thanks Electroz for your quick answer:
UGJG9 was the initial August 2.1 release.
UGJH2 was an updated 2.1 release.
UGJK4 was the initial December 2.2 release.
UGJL2 is the current 2.2 release.
New question: Which PIT files go with which firmwares? i got a 512, 513, and 803, not sure which ones should be used with which firmware, if anyone can clear this up for me i would greatly appreciate it.
UGJG9 was the initial August 2.1 release.
UGJH2 was an updated 2.1 release.
UGJK4 was the initial December 2.2 release.
UGJL2 is the current 2.2 release.
Any of these are considered stock firmwares and fine to have loaded for a return to Samsung.
Hope this helps!
Next question, is there a place i can get the latest firmware (not through kies), or is linking to the firmwares not allowed on this forum? doing a search for UGJL2 is not proving very successful. (or is there more i should be searching for aside from just 'UGJL2'?)
JK3 is another release and although popular was not official.
JK4 should NEVER be used. Samsung pulled it due to a very high failure rate it was causing with these phones.
pileot said:
Next question, is there a place i can get the latest firmware (not through kies), or is linking to the firmwares not allowed on this forum? doing a search for UGJL2 is not proving very successful. (or is there more i should be searching for aside from just 'UGJL2'?)
Click to expand...
Click to collapse
I'm not at my pc so I can't provide a direct link but you can go to samfirmware.com, register for an account avs d/l the firmwares you want.
derp
have an account there already, was thrown off because none of the files are listed for canada, confused me.
Downloading now, thanks!
pileot said:
derp
have an account there already, was thrown off because none of the files are listed for canada, confused me.
Downloading now, thanks!
Click to expand...
Click to collapse
yup... according to Samsung stock ROMs, Canada is a state of USA
ok new question, any idea which pit files are supposed to go with which firmwares?
Maybe slightly off topic but in need of help so-
I bricked my phone. Phone does not enter recovery or download. Called Bell. They are sending me a replacement. My phone was totally modded. I have two questions.
1) Can they find out that I had rooted the phone?
2) will they charge for me the replacement that they send in?
droilfade said:
Maybe slightly off topic but in need of help so-
I bricked my phone. Phone does not enter recovery or download. Called Bell. They are sending me a replacement. My phone was totally modded. I have two questions.
1) Can they find out that I had rooted the phone?
2) will they charge for me the replacement that they send in?
Click to expand...
Click to collapse
If your internal SD is dead, it's dead. No one's pulling any data off it; it's built into the motherboard.
No, they won't charge you anything. You should have actually gotten a 100$ credit for the 'inconvenience'.
pileot said:
ok new question, any idea which pit files are supposed to go with which firmwares?
Click to expand...
Click to collapse
Check the samfirmware.com site. They list the pit file next to firmware version. The canadian firmwares begin with i9000ug
seeARMS said:
If your internal SD is dead, it's dead. No one's pulling any data off it; it's built into the motherboard.
No, they won't charge you anything. You should have actually gotten a 100$ credit for the 'inconvenience'.
Click to expand...
Click to collapse
Thanks that relieves a lot of pressure. I'm not being charged for the period of repairs. I did ask about $100. The representative said there is nothing of that sort!!!! And I don't know if my internal SD is dead..Do you think its fried?
well for me flashing the GJL2 firmware with Odin revived it, so if your not worried about trying you might give it a shot.
I just realised...it shows the I9000 screen instead of the I9000m So they can find out even before they do anything.....
Electroz said:
UGJG9 was the initial August 2.1 release.
UGJH2 was an updated 2.1 release.
UGJK4 was the initial December 2.2 release.
UGJL2 is the current 2.2 release.
Any of these are considered stock firmwares and fine to have loaded for a return to Samsung.
Hope this helps!
Click to expand...
Click to collapse
Hey, if i load JH2 onto it, and I use pit 512, as it said, do I use odin 1.0, 1.3 or 1.8?? also, do I have to checl "re-partition"? please answer fast, it wuld be great help! thanks alot!
zumi78878 said:
Hey, if i load JH2 onto it, and I use pit 512, as it said, do I use odin 1.0, 1.3 or 1.8?? also, do I have to checl "re-partition"? please answer fast, it wuld be great help! thanks alot!
Click to expand...
Click to collapse
Use ODIN 1.3 and chcek repartition
pileot said:
ok new question, any idea which pit files are supposed to go with which firmwares?
Click to expand...
Click to collapse
The answer for JG8, JH2, JK3 and JL2 is PIT 512.
zumi78878 said:
Hey, if i load JH2 onto it, and I use pit 512, as it said, do I use odin 1.0, 1.3 or 1.8?? also, do I have to checl "re-partition"? please answer fast, it wuld be great help! thanks alot!
Click to expand...
Click to collapse
Also check this website before you do anything------http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+androidspin/feed+(AndroidSPIN+|+Your+No.1+source+for+Android+news.
droilfade said:
Use ODIN 1.3 and chcek repartition
Click to expand...
Click to collapse
another person told me to NOT check re-partition and check the bootloader option? btw, THIS IS FOR FLASHING THE ORIGINAL FIRMWARE FOR SENDING BACK TO BELL!
so again, if i use odin 1.3, would JH2 work(for sending back to bell)? and do i still need to check re-partition? and do i need to check update bootloader? or do i do both? or do i do one after another? thanks!
zumi78878 said:
another person told me to NOT check re-partition and check the bootloader option? btw, THIS IS FOR FLASHING THE ORIGINAL FIRMWARE FOR SENDING BACK TO BELL!
so again, if i use odin 1.3, would JH2 work(for sending back to bell)? and do i still need to check re-partition? and do i need to check update bootloader? or do i do both? or do i do one after another? thanks!
Click to expand...
Click to collapse
That is why check the link on top to know for sure!!
my device had stock JVK with CWM 3.
then i flashed with CWM darkcore 2.1
after that i stuck on the first screen and every few secends the device make a strange voice and reboot .
i tried to flash with ODIN JVB by FICETO and after i flashed that nothing happand. its the same.
what is the problem????
BTW sorry for my english :/
after that i stuck on the first screen and every few secends the device make a strange voice and reboot .
If you read the instructions thats the Voodoo Lagfix writing the file structure .
Once it reboots your phone is lagfixed .
You then FFFF it up a.
Flash stock rom via Odin with pit 512 and repartition checked .
http://www.samfirmware.com
The problem is you failed to read/follow instructions .
jje
JJEgan said:
after that i stuck on the first screen and every few secends the device make a strange voice and reboot .
If you read the instructions thats the Voodoo Lagfix writing the file structure .
Once it reboots your phone is lagfixed .
You then FFFF it up a.
Flash stock rom via Odin with pit 512 and repartition checked .
http://www.samfirmware.com
The problem is you failed to read/follow instructions .
jje
Click to expand...
Click to collapse
i didnt understood what you saying
what he means is that 'robot voice' is normal on voodoo kernels, the voice is stating that lagfix is being applied.
and also, the majority of darky's roms end up bricking peoples phones, so the way to fix this is to flash stock eclair (2.2) with PIT 512 and re-partition box checked in ODIN.
this will fix a bricked device 99% of the time.
EDIT: is darkcore kernel even compatible with JVA/B/K roms ???
if not, that is what fcuked up your phone !!
fly boy said:
i didnt understood what you saying
Click to expand...
Click to collapse
No neither did you understand what you where doing as you had not read the instructions faqs etc .
That is the problem .
jje
azzledazzle said:
... and also, the majority of darky's roms end up bricking peoples phones....
Click to expand...
Click to collapse
Azzledazzle,
Firstly this is untrue, I never had problems with darky roms.
Secondly a phone that is recoverable via the 3 button method using odin or whatever is not "bricked". A brick is a dead phone.
I think you should post a retraction as you have made 2 assertions, both inaccurate, one of which is unfair to darky.
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 jvk rooted, ADW launcher + gingerbread theme
mossy1963 said:
Azzlefazzle,
Firstly this is untrue, I never had problems with darky roms.
Secondly a phone that is recoverable via the 3 button method using odin or whatever is not "bricked". A brick is a dead phone.
I think you should post a retraction as you have made 2 assertions, both inaccurate, one of which is unfair to darky.
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 jvk rooted, ADW launcher + gingerbread theme
Click to expand...
Click to collapse
First of all 'MAJORITY OF DARKYS ROMS' meaning not all but a hell of a lot. Search button at the top if you dont believe me.
Secondly a brick is a state where the phone does not function, albeit it may be a temporary / part / semi brick, but its still a brick none the less.
Thirdly I WILL NOT retract or edit my post as everything i said is FACTUAL , please edit your post accordingly. No need for apologies.
fly boy said:
i didnt understood what you saying
Click to expand...
Click to collapse
Too bad..
azzledazzle said:
... 'MAJORITY OF DARKYS ROMS' meaning not all but a hell of a lot...
... a brick is a state where the phone does not function, albeit it may be a temporary / part / semi brick...
.
Click to expand...
Click to collapse
Excellent - so we've established that when you said "majority" you meant "minority" and when you said "brick" you meant a phone with any kind of defect - when the accepted definition is a phone that cannot be repaired without return to manufacturer.
Now all we have to do is work on your attitude to having your gross exaggerations / mistakes corrected and we'll call it a result eh?
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 jvk rooted, ADW launcher + gingerbread theme
how many threads have you seen with the title ' bricked , darky rom, bootloop, help '
a lot more than you see ' darkys rom is soooooo good', i am not dis-respecting him, i have used his roms from 5.1 - 9.0, but i started getting issues so i changed. Im not saying everyone has issues but A LOT do, whether this be the rom or the flasher. i dont know.
and by the term defect. that could mean a dint, a scratch, a bug, a glitch.
What i meant by brick is the phone not booting as it should, example: boot loops, Phone ! PC sign. not 3 button combo, corrupted bootloader.
Taking your phone to a SSC all they will do is JIG it and Flash a stock ROM, we do this at home.
We dont always have to take the phone to the manufacturer when we can do similar jobs to them to repair a *BRICK*
EDIT: http://en.wikipedia.org/wiki/Brick_(electronics)
so dont come over all smart arse with me, because im merely stating a fact that you dont agree with.
azzledazzle said:
EDIT: http://en.wikipedia.org/wiki/Brick_(electronics)
Click to expand...
Click to collapse
Thanks for the link confirming your mis-definition
so dont come over all smart arse with me...
Click to expand...
Click to collapse
I won't dignify this content with a response, good night
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 jvk rooted, ADW launcher + gingerbread theme
mossy1963 said:
Thanks for the link confirming your mis-definition
I won't dignify this content with a response, good night
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 jvk rooted, ADW launcher + gingerbread theme
Click to expand...
Click to collapse
haha. aww you ran out of ammunition have ya. ??
there was no mis-definition perhaps you have trouble reading as well as writing.
anyway. thanks for making yourself look even more noob-ish. Good night to you too
mossy1963 said:
Azzledazzle,
Firstly this is untrue, I never had problems with darky roms.
No its not untrue at all the majority of the help i broke my phone posts on here are Darky roms fact just read the damn forum .
Secondly a phone that is recoverable via the 3 button method using odin or whatever is not "bricked". A brick is a dead phone.
Brick is really the generic term used here for phones that wont boot rightly or wrongly.
I think you should post a retraction as you have made 2 assertions, both inaccurate, one of which is unfair to darky.
I calculate 2000 of my posts are in respect of broken Darky roms you need to read the help posts .
If Darkys that good why do his users never get any help here and why are you not on top of the problem answering the hundreds of Darky broke my phone posts .
jje
PS leave it all up to you now mate you can answer all the deadly broke my rom posts . I just hope and pray he does not move to SGS2.
jje
Click to expand...
Click to collapse
thanks for clearing that up jje i was starting to lose my rag a little back then.
some people just need to type a few words in a little search box and all will make sense, but instead they criticize people and accuse them of being wrong.
lets just hope thats the end of it
Hey,
I used Heimdall to flash KH3 as per the thread, including these steps:
" I'm on stock froyo, kb1, flashed to it using this: heimdall at&t stock firmware package. Can i flash UCKH3 that Adam linked in the OP over this? Is it enough to click on bottom left button (details), then write true in the Flash column to the IBL+PBL, SBL, PARAM rows to flash bootloaders too? Thanks for the answers!
yes. You should not have any problems." (http://forum.xda-developers.com/showthread.php?t=1238093&highlight=heimdall&page=2)
I wanted to double check that after changing those variables to 'true' and flashing I have the bootloaders already flashed. (I understand now that it lets you click 'flash bootloaders' after you flash once successfully, but I wanted to check to see if that is still necessary given the above method). No reason to risk flashing them again if I already got 'em.
Thanks for the help... would've replied directly in development forum but not enough posts
Yes you can, but I don't know if there is a way to root it with one-click yet. I need to release an early 2.3 version before they locked it down.
Btw.. I make Heimdall One-Click which is based on Heimdall by Benjamin Dobell.
It's also worth mentioning that you should flash, and only if it does not work, then flash again with bootloaders.
You really should have asked in the one-click thread.
AdamOutler said:
Yes you can, but I don't know if there is a way to root it with one-click yet. I need to release an early 2.3 version before they locked it down.
Btw.. I make Heimdall One-Click which is based on Heimdall by Benjamin Dobell.
It's also worth mentioning that you should flash, and only if it does not work, then flash again with bootloaders.
You really should have asked in the one-click thread.
Click to expand...
Click to collapse
The flash 'worked' but I'm not 100% sure whether I have the bootloaders.... all the parts seemed to flash correctly though...
The reason I asked in here is because I don't have my 10 posts yet, or else I would definitely have chosen to ask in the correct thread.
I don't really mind that it isn't rooted for now, but it doesn't seem to have an APN list at all so I've got no data. Otherwise, this is definitely the best stock I've ever used, decent battery life and relatively fast performance. Just got a replacement unit, so GPS finally worked for one day... until I flashed and had no data, lol.
Thanks for the help, btw. I probably will try to flash it again and see if that works, otherwise I will boot into windows and try Cog5 or one of the other KH3s with CWM recovery.
*EDIT* Didn't reflash (yet), but found the setting which lets you try the 'default' APN settings, so was able to get the regular cingular/att settings and connect from there. So I'm sticking with stock until a KH3 or newer kernel/rom with CWM+root that looks worthwhile comes out. **
Hello
I have captivate from at&T ( I897). I upgraded last year from eclair to froyo UCJI6 from some site.
Please can some one guide me step by step how to get latest gingerbread. I never had gingerbread on my phone. Upgrading from UCJI6 scares me.
Your help would mean a lot to me.
Thanks
Dillon
xoom11 said:
Hello
I have captivate from at&T ( I897). I upgraded last year from eclair to froyo UCJI6 from some site.
Please can some one guide me step by step how to get latest gingerbread. I never had gingerbread on my phone. Upgrading from UCJI6 scares me.
Your help would mean a lot to me.
Thanks
Dillon
Click to expand...
Click to collapse
Did you even try to use the search? or look at the stickies?
How to Flash Roms Sticky
List of Stock packages and 1 clicks Sticky
XDA Video
prbassplayer said:
Did you even try to use the search? or look at the stickies?
How to Flash Roms Sticky
List of Stock packages and 1 clicks Sticky
XDA Video
Click to expand...
Click to collapse
I looked at your post but it was confusing for me as i dont know much.
There were two download links..one was boot loader free ..other was different one.
Can you please send me the the right steps and link for downloading
thanks
Another resource is
MobileTechVideos <- good video guides.
That being said, modifiying your phone can lead to hard bricks. So above all read and understand everything. Most of the danger is flashing bootloaders (that's why you see packages with and without bootloaders, to limit the danger). If you corrupt one of the bootloaders or flash 2 different (none matching) bootloaders you need a Jtag or UnbrickableMod service. When flashing Gingerbread you NEED gingerbread bootloaders. Once flashed you are golden and don't have flash those ever again.
http://forum.xda-developers.com/archive/index.php/t-1276762.html
i checked above forum where u helped the guy with upgrading UCJI6 to GB.
He had issues while upgrading but eventually he was succesfull.
I could not find which method he used ..
please help me if possible
Read up on how to get in Download mode and how to use ODIN (or Heimdall if you are running a none windows machine). Download a Stock gingerbread rom with bootloaders and flash. The latest is KK4, but i've never used that specific package (though it should have bootloaders) I can speak for KJ3 on that thread.
Basics.
Open ODIN (1 click or not) as admind
Get in download mode (press vol up+voldown+connect to computer
If normal ODIN use the PDA slot and select the .rar.md5 package
Hit start
Let it finish and bootup
???
profit
I'm not responsible if anytthing should go wrong. If odin gets stuck or you do something wrong you will soft brick or possibly hardbrick your phone.
i am giving up.
Can not find any links and steps which are of great help for Upgrading to GB from UCJI6.
Some are going back to 2.1 before upgarding some not.
Dont know what to do
Going back to stock is-was only used for cwm flashes. You will use ODIN. 2 way different things. Follow my steps. Or read through the tons of threads here. It isn't that hard.
waymon31 said:
Really? the guy just asked a question and i can understand he doesnt want to ruin his investmet. we were all noobs once!!! no need to be rude i mean really how much did it cost you to answer his question?
Click to expand...
Click to collapse
he gave up because he couldnt find EXACT instructions on going from one particular FROYO build....because if he had done any actual research, he would know that it doesnt matter what version of FROYO he is on, he will need to flash the ODIN package with the bootloaders....its all covered in the vast damn posts that already cover this extensively. there was ZERO reason to fire up a new thread.
he has been linked to good info and has refused to take heed. reading and UNDERSTANDING is more important than holding hands around here.
Yes we were all noobs once and yes, you need to do your research but he's obviously nervous and not understanding what he's reading right now. Hopefully he'll calm down and understand the information he's been given. We're done here.