so my dilemma is as follows.. i was running continuum 4.1 on my captivate. i decided i wanted to try one of the new gingerbread roms, so my first step was to use odinoneclick 1.0 to get to complete stock and go from there. my luck, odin froze on me at sbl.bin... so i am soft bricked but i can use the vol up/down plug usb method to get to download mode. because i have only used one click before, and not a full odin like 1.7, i am having trouble figuring out exactly what i need, and what steps are necessary to safely get me back to stock using odin 1.7 so i can then load GB bootloaders and stop messing with BL's from now on.. so i suppose my main question is should i first flash eclair before trying to flash GB bootloaders/rom? my other question being, if so, what files do i need, and do i need to place a pit file and repartition? sorry if this is a noob question, i just dont want to screw it up any further and wasnt sure if specific steps must be taken when you are soft bricked.. thanks very much in advance!
No need to flash Eclair. Just flash the KF1 file in this post and then XCal's reorient for GB and you'll be good to go. Just don't boot into the OS after flashing XCal's kernel else you'll get bootloops since it was designed for I9000 based ROMs rather then I897. Just reboot back into recovery after flashign XCal's Kernel and then flash whatever GB ROM you want.
http://forum.xda-developers.com/showthread.php?t=1126704
I personally prefer to flash my phone using Heimdall on my laptop running Kubuntu as it's generally more stable/successful, and it's easier to choose which files you want to flash if you only want to flash specific files (Like the bootloaders).
Also KH3 is out and it looks like it might have updated bootloaders, but it's not a full ROM from what I was able to grab. It's missing the param.lfs, dbdata.rfs, and the pit file. Also has an added SS_DL.dll which I'm not sure what the purpose of that file is since it's a Windows file...
http://forum.xda-developers.com/showthread.php?t=1232703
Moved to Q&A.....
NO QUESTIONS IN DEVELOPMENT PLEASE!!!!!
conantroutman said:
Moved to Q&A.....
NO QUESTIONS IN DEVELOPMENT PLEASE!!!!!
Click to expand...
Click to collapse
my apologies! my intention was to post in q&a but i was at work sneaking on the pc i must have been clicking too fast..
and kyuta... thank you for the suggestion! so is it safe to just use the whole odin package in the link you provided just to get a clean install, and then move on to a rom/kernel of choice at a later time?
im getting a big red FAIL on every attempt at flashing KF1 file with odin 1.3 and 1.7 im not sure which route to take at this point. do i need to flash the pit file with the bootloaders?
dartdc97 said:
im getting a big red FAIL on every attempt at flashing KF1 file with odin 1.3 and 1.7 im not sure which route to take at this point. do i need to flash the pit file with the bootloaders?
Click to expand...
Click to collapse
just make sure u hav right file downloaded...and right click on odin and click run as administrator...try changing the usb ports....and try changing the usb cable...and see if u hav proper driver installed ....
check all these which i hav mentioned...
then u shd be able to go back to either eclair(jf6) or gingerbread(kf1) stock
killer_raj said:
just make sure u hav right file downloaded...and right click on odin and click run as administrator...try changing the usb ports....and try changing the usb cable...and see if u hav proper driver installed ....
check all these which i hav mentioned...
then u shd be able to go back to either eclair(jf6) or gingerbread(kf1) stock
Click to expand...
Click to collapse
Just to add this this: Try using XP service pack 2 mode if you are using Windows 7 x 64.
Related
Help.
I have been running Frost just fine for about 24 hours now. Have rebooted a few times for media scanning reasons without incident. Just now I rebooted and am stuck in a boot loop. So I long held the power key and boot loop again. Then pulled the battery and tried again and I get the same thing. Google logo and then the frosty Team Whiskey a few times and then it vibrates and starts all over. What should I do from here. Its the first time Ive had a problem flashing and Im thinking I have to use Odin now....or can I get into recovery somehow and boot from there? ( sorry if I posted this in the wrong section. In my nervousness I posted here instead of Q&A)
edit: Read, read, and read some more. Odin-ed to stock successfully....and then did it again to be safe. Now to start the root/ flash process all over. It's almost like an addiction. This time I think I'll stick with one rom for a while.
just ODIN back to something. Learn it. Love it. It's simple.
Ok. Any way I can use my nandroid backups? If no.....would I be best to go back to stock and then to my rom of choice? or just odin to my rom of choice
GoodVibrant-ions said:
Ok. Any way I can use my nandroid backups? If no.....would I be best to go back to stock and then to my rom of choice? or just odin to my rom of choice
Click to expand...
Click to collapse
Since frost uses ext 4 for partitions, I recommend odin to jfd stock with repartition checked. it has all the fs files you would need. Then flash back to whichever rom you want. there are tutorials on how to use odin, or you can use heimdall, same thing but open source and you need to unzip the tar that the rom comes in to get the individual files inside.
wildklymr said:
Since frost uses ext 4 for partitions, I recommend odin to jfd stock with repartition checked. it has all the fs files you would need. Then flash back to whichever rom you want. there are tutorials on how to use odin, or you can use heimdall, same thing but open source and you need to unzip the tar that the rom comes in to get the individual files inside.
Click to expand...
Click to collapse
Ok...looks like I have some reading to do. I knew I was gonna have to do this sooner or later so I guess it's good I learn it now.
When you say I have to unzip the tar that the rom comes in.....does that just apply to heimdall....or heimdall and odin both?
GoodVibrant-ions said:
Ok...looks like I have some reading to do. I knew I was gonna have to do this sooner or later so I guess it's good I learn it now.
When you say I have to unzip the tar that the rom comes in.....does that just apply to heimdall....or heimdall and odin both?
Click to expand...
Click to collapse
Just heimdall. If you use odin, just load the whole tar the rom is in into the pda field.
I just odin back to Eugenes Froyo that doesn't brick w partitions set, I wonder if im doing it right, or if my phone would work better if I odin'd back to JFD stock, never had any problems though, and ive been in some bad soft bricks (e: cant mount, bootloop, etc..)
Sent from my SGH-T959 using XDA Premium App
gfropr said:
I just odin back to Eugenes Froyo that doesn't brick w partitions set, I wonder if im doing it right, or if my phone would work better if I odin'd back to JFD stock, never had any problems though, and ive been in some bad soft bricks (e: cant mount, bootloop, etc..)
Click to expand...
Click to collapse
I've heard of this also but I don't want to mess anything up worse than it already is. Would Eugenes froyo no brick be ok since I'm coming from frost?
My best advice would be odin back to stock, it's a fresh clean start, don't be intimidated, odin is very ready to use, go to the Bible and get the 512 file, JFD stock file, and Odin program. If I could do it without a hitch, you can too, it takes about 2 minutes to odin, go for it! lol
Sent from my Vibrant w/ Bionix V 1.3 and Launcher Pro Plus
negerhab said:
My best advice would be odin back to stock, it's a fresh clean start, don't be intimidated, odin is very ready to use, go to the Bible and get the 512 file, JFD stock file, and Odin program. If I could do it without a hitch, you can too, it takes about 2 minutes to odin, go for it!
Click to expand...
Click to collapse
Thanks man. I appreciate the reply.....wish I would have saw it earlier. It might have saved me a little bit of time. I am writing this from my phone after odin-ing to stock and then odin-ing to eugenes jk2 froyo. After that it was cake to flash back to bionix 1.3. You're right though....its intimidating to use odin when you have never done it but now that I have I will use it anytime I switch between roms. Plus I feel like I now have a clean install of bionix. But mainly I'm glad the panic is over and my phone is back to lightning speed operation.
Sent from my SGH-T959 using XDA App
Hi. I was running CM7 fine and then flashed MIUI last night and now i can't change the kernel or modem no matter how many times i try and flash in clockwork or clear caches or factory reset. I've lost cell network completely. Wifi works interestingly. Any ideas?
Anyone got any ideas how to fix this so I can actually flash new modems and krnels? They show as successfully flashing in CWM but About Phone doesnt change!
Would love to avoid going to sto ck via Odin if I can.
Th an ks
TheMathMan said:
Anyone got any ideas how to fix this so I can actually flash new modems and krnels? They show as successfully flashing in CWM but About Phone doesnt change!
Would love to avoid going to sto ck via Odin if I can.
Th an ks
Click to expand...
Click to collapse
what modem and kernel are you trying to flash. you need the update .zip to be designed for gingerbread, different scripting for gb. so the kernel shouldn't be a problem unless you are trying to revert to 2.2.
im not sure if gingerbread is weird but maybe you can extract the zimage and modem.bin you are trying to flash and archive them in .tar files and odin flash. as long as you are not flashing anything with boot.bin or sbl.bin it shouldn't break the ability to odin back to stock.
A word of caution: If u get on GB kernel, and go to recovery, and try to use these kernel zips to flash back, they won't work. I realized this the hard way last night.
diablo009 said:
A word of caution: If u get on GB kernel, and go to recovery, and try to use these kernel zips to flash back, they won't work. I realized this the hard way last night.
Click to expand...
Click to collapse
if you read any cm7 or other gingerbread thread they say you need 3 button recovery/download. this is one reason why! i think there should be a generic froyo kernel in the proper type of update file to revert. but maybe they are trying to scare away newbs till they complete cm7 or atleast have a release candidate.
Sorted in the end.
I just formatted every partition in Mounts and Storage first before a reflash.
Sent from my Armani S i9010 (CM7)
I was going through the below tutorial everything seem to go find until i restarted. Then it froze and has been frozen for a while im trying to wait an hour its been about 20 minutes.
Any thoughts ideas on where to start to get my device rolling or is it done for. thanks for any device you can provide.
the unlockr .com/
2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab]
did you use CWM from Rom Manager?
This is NOT optimized for the SGT.. nor is it encouraged.
Anyhow, have you tried to check if your computer can detect your tab, through Kies or Odin?
Sef_P1000 said:
did you use CWM from Rom Manager?
This is NOT optimized for the SGT.. nor is it encouraged.
Anyhow, have you tried to check if your computer can detect your tab, through Kies or Odin?
Click to expand...
Click to collapse
Yes I did use CWM from Rom Manager
Kies says connecting but doesn't ever connect
Odin3 says 0:[COM6]
so what can I do?
what you can do , is go grab the stock gingerbread and flash it via odin and then take the root file and u'll have both gingerbread and also the cwm ...
follow chainfire steps and u'll do it in 4mins
k0sh said:
what you can do , is go grab the stock gingerbread and flash it via odin and then take the root file and u'll have both gingerbread and also the cwm ...
follow chainfire steps and u'll do it in 4mins
Click to expand...
Click to collapse
t
What do you mean do you have instructions somewhere? please post thanks for your help
iamahero said:
t
What do you mean do you have instructions somewhere? please post thanks for your help
Click to expand...
Click to collapse
he was pertaining to this thread..
http://forum.xda-developers.com/showthread.php?t=1073854
noxxious said:
he was pertaining to this thread..
http://forum.xda-developers.com/showthread.php?t=1073854
Click to expand...
Click to collapse
You the dude
Sent From (I'm In Luv With My Tab)
similar problem....also stuck on boot
but I got there a different way. (FIXED)
Let me start off by saying I am stupid I have a tmobile tab and it was running awesome on overcome 2.0.0 rc1 with ext4 conversion and OC kernel and then I saw the honeycomb alpha had been released for cdma, which of course I dont have (gsm), and decided to try the rom with the oc gsm kernel, which didnt work.
then I dun goofed. Instead of going back to overcome in cwm, I flashed the damn experimental honeycomb package again, kernel and all and then loaded the tab.....dumb...weird colors and then nothing....screen just goes black and no matter what I cannot see cwm screen. And now odin no longer recognizes the tab.
heimdall works and I flashed back kernal from :[OC/UV][7th Jun][Kernel] koxudaxi kernel [GSM][2.2&2.3][KernelPatch]
which gives me cwm, but it keeps giving me an error that i cant mount sd card
I have tried flashing the safe gingerbread stock with pit file (still stuck on boot logo)
then tried flashing rotostock tmobile rom ( but no pit file and when it boots it still shows the gingerbread bootlogo)....do i flash with P1_add_hidden.pit added?
Any and all help will be much appreciated. please don't be too mean. I know i shouldn't have done what i did
[UPDATE]
So I figured it out. I reinstalled samsung usb driver from within odin folder, and odin suddenly started working. went back to stock GB and then on to Overcome 2.0.0 Gold w/ ext4 and oc'd to 1.4
I had to reinstall the hiemdall driver too after reinstalling samsung driver, but now they both work again....... so stoked
NOW WITH CUSTOM BOOTSPLASHES! MORE TO COME SOON...
All you guys, PM me any images you want as boot splashes, and I'll see what I can do...
SAFE TO FLASH, IF PROCEDURE FOLLOWED PROPERLY AND NOT INTERRUPTED
SOLVE YOUR RECOVERY AND RAINBOW PROBLEMS ON GINGERBREAD ROMS
WORKS ACROSS FROYO AND GINGERBREAD ROMS BASED ON SAMSUNG GALAXY S I9000 OR SGS-T959.
ALSO WORKING PERFECTLY WITH CYANOGENMOD AND MIUI​When we got Gingerbread ROMs, we also faced the issue of not being able to see the Recovery on the GB Kernels and having to see our screens go funny which were safely called Rainbows! Well, no more !! Flash these Gingerbread Bootloaders and there you go, no issues on Gingerbread except GPS!!
If You can ODIN to JFD, and can see the Download Mode, You can do this.
PLEASE MAKE SURE YOU'RE RESPONSIBLE FOR ANY USER ERROR. I HAVE THESE FILES WORKING 100% ONLY ON A SGS-T959 VIBRANT. FLASHING BOOTLOADERS IS RISKY IF YOU DON'T KNOW WHAT YOU'RE DOING. HOWEVER, BASIC KNOWLEDGE AND COMMON SENSE MAKES IT SURE YOU WON'T GO WRONG WHILE DOING IT.[/CENTER]
This is a small attempt to create bootloader only flashables similar to EZ Boot on the Galaxy S forums, however for our T959 Vibrant... These bootloaders will only have the Vibrant Boot logo and not the I9000 logo, hence maintaining the original look of your phones...
Both the tar packages contain sbl.bin, boot.bin and param.lfs files and have md5 checksums to maintain file integrity when flashing with ODIN. They're working 100% for me... I flashed them atleast 5 times alternatively between them on 3 different ROMs before uploading. So yes, I know the packages are correct.
Gingerbread Bootloaders - No Rainbow - Fully visible Recovery on all ROMs]
Benefits - No more rainbows on Gingerbread 2.3 ROMs like Simply Honey GB, LiDroid, Asgard, etc.
Convenient Key Maps for entering Recovery and Download Modes. (I personally like these mappings over the Standard Vibrant Mapping as you can enter download mode directly without needing to turn off phone or remove battery etc...)
For Recovery - Lower Volume Key + Power Button
For Download - Upper Volume Key + Power Button
Froyo Bootloader - Revert to Vibrant
Benefits - Original bootloaders to revert to stock for Vibrant based ROMs. Also, for MIUI and CM7...
Key Maps
For Recovery - Both Volume Keys + Power Button
For Download - Both Volume Keys and Connect USB Cable
How to DO
ODIN Guide
Please follow this step by step, else I won't be responsible for any DAMAGE.
1. Enter Download mode on your phone.
2. Open ODIN on your computer.
3. Plug in USB and check if ODIN recognizes the phone.
4. Remove all ticks from ODIN, except PDA.
5. Select PDA and browse to the bootloader TAR package file you wish to flash.
6. Click on Flash.
7. If ODIN says PASS, long press power for 10 seconds and it'll reboot, else, repeat 2-6 again...
Avoid exiting download mode if you think the flashing wasn't correct. If however, the peogress window did not start flashing any file, you might just manage to safely reboot and re-enter download mode.
Please note, you do not need to use the PIT file since it will be used automatically from the native partition on the phone.
ODIN shall automatically verify the integrity of the tar package using the included md5 hash. However, for personal prudence, I'd suggest you do that before hand.
CUSTOM GINGERBREAD BOOTLOADERS DOWNLOAD LINK
1. Green Android Logo
- Mediafire Download Link
- MultiUpload Download Link
MD5 Sum - ab17ca277adbc3cd355d7f31ff89bee9
2. Rainbow in my Eye
- Mediafire Download Link
- MultiUpload Download Link
MD5 Sum - 42f2c260b6aa272592dd1f0f3cd77f0c
GINGERBREAD BOOTLOADER DOWNLOAD LINK
- MultiUpload Download Link
- Mediafire Download Link
MD5 Sum - b34df5c2db723eacc534013a011885ad
JFD ODIN File - For use after installing Gingerbread Bootloaders
http://www.multiupload.com/HRYJKFLKFQ "Thanks to laylovj"
MD5: 977E2136996E7138945447A8245D6776
If you have Gingerbread Bootloaders installed and you end up ODINing to stock (JFD), you will notice it changes the bootsplash to I9000. You can either reflash a GB bootloader again, or simply use the ODIN package above to do so.
VIBRANT STOCK (FROYO) BOOTLOADER DOWNLOAD LINK
- MultiUpload Download Link
- Mediafire Download Link
MD5 Sum - 754ecbd8e76d4f81bec49240031f3262
Video
The video here shows Galaxy S i9000 after ODIN. That is because I forgot to include the corrected param.lfs in the packages... However, its been included in the above packges.
Donation Link
I don't demand any donation, but if you think I helped, you may buy me a crate of beer, or contribute to my SGS II kitty by hitting the donation button under my Username. Thanks !!
Frequent questions / Additional Information
Reserved by OP:
DISCLAIMER: IT IS UNSAFE IF YOU ARE A NOOB! TAKE OFFENCE AND DON'T FLASH IT, RATHER THAN FLASH AND BRICK YOUR PHONE
Definition of a Noob
A person who does something to his phone not knowing what he did or what would happen next.
Definition of a DumbHead
All qualities of a Noob + I did not read the OP or FAQs.
FAQs:
1. Is it unsafe?
Flashing a bootloader incorrectly technically bricks your phone. So its like having a single shot at what you're doing, you either keep doing it right and shuffle between the bootloaders, or you do it wrong just once, and you might have a dead phone.
2. What ROMs can I use with the GB Bootloader?
You can use any ROM - 2.1, 2.2 or 2.3 without needing to alter affect your bootloaders as they are backward compatible. However, DO NOT FLASH OR ODIN the following packages
- ODIN Packages containing only an Sbl.bin
- ODIN Packages containing only a boot.bin
If the package contains both, it would technically upgrade/downgrade your bootloader, hence being safe if they are the correct files.
3. Should I flash this before/after flashing a new ROM
You can flash this at anytime, before or after, both are safe.
4. Will it affect performance?
Bootloaders are not known to alter performance. However, on Gingerbread ROMs ported from I9000, they have helped solve the presence of the Rainbow screens, and also allow you to view recovery directly from the phone.
5. Will my 3 button combi work?
If you have the Gingerbread Bootloaders, no. Use the combinations mentioned in the OP to enter both recovery and download mode.
6. Which .pit should I use?
The phone itself has its native .pit partition to take care of any such issues. So not using a .pit file will not affect/harm you. I suggest you not to use one. However, if you do use one, use this - s1_odin_20100512.pit
It is the same we use for ODIN to JFD or Eugene's Froyo that does not brick.
7. What to do when an Official Vibrant update for Gingerbread arrives?
Safest option - Return to Stock Vibrant Froyo bootloaders as in the OP. They will return you to factory bootloaders and any Gingerbread upgrades containing either an sbl.bin or boot.bin or both shall flash just fine. You may choose not to do this, if you're aware of what you're doing.
8. Can I ODIN to stock JFD like I always did?
The JFD Odin packages that I have seen don't contain sbl.bin or boot.bin ! Hence, till that's the case, its safe to ODIN to stock. Please check your ODIN tar packages using 7zip or WinRAR or any other Archive utility for absence/presence of the mentioned files. If they do appear, they should be present together. Else, if they don't appear, you are safe to ODIN to stock.
9. Whatever I flash, I end up in Recovery! What should I do?
Flash stock Vibrant bootloaders, then ODIN to stock JFD. You should be good to go here onwards... I only had this issue when I tried changing bootloaders over MIUI/CM7. Couldn't replicate on Samsung ROMs...
Interesting.
I will wait for someone to flash this.
Great Job Scorp!! Check your pm.
Planning to post a video so that people gain confidence in what's going on really...
adyscorpius said:
Planning to post a video so that people gain confidence in what's going on really...
Click to expand...
Click to collapse
I have all the confidence in the world in you scorp. Take your time man. This is good ****!
is the Gingerbread Bootloader come from samsung officecal ?
paranoia_gu said:
is the Gingerbread Bootloader come from samsung officecal ?
Click to expand...
Click to collapse
Its Official Samsung I9000 Bootloader masked with the Vibrant boot image...
adyscorpius said:
Its Official Samsung I9000 Bootloader masked with the Vibrant boot image...
Click to expand...
Click to collapse
Very nice scorp! You just took a lot the guess work out of the process. Very simple and I feel best thing that could have happened for our phones. Awesome man!
jcc332006 said:
Very nice scorp! You just took a lot the guess work out of the process. Very simple and I feel best thing that could have happened for our phones. Awesome man!
Click to expand...
Click to collapse
Thanks man... Hope people start using it... It's not really that much of an issue really... I've replaced bootloaders over a 100 times over the last week with no issues... And that when I have the phone in India, so if its dead, I cant even get it replaced from T Mobile or the insurance... Lol
adyscorpius said:
Thanks man... Hope people start using it... It's not really that much of an issue really... I've replaced bootloaders over a 100 times over the last week with no issues... And that when I have the phone in India, so if its dead, I cant even get it replaced from T Mobile or the insurance... Lol
Click to expand...
Click to collapse
Man I just flashed and it works like a charm. So dam simple now. Booted up so fast and rainbow is history!
**** yeah!! No more double rainbooows! Thanks waffle dude!
Sent from my GT-I9000 using XDA Premium App
My friend wants to know if she can flash the gb bootloader via sgs kernel flasher or cwm app on simply honey?? She has no CPU.
Sent from my GT-I9000 using XDA Premium App
kooksta said:
My friend wants to know if she can flash the gb bootloader via sgs kernel flasher or cwm app on simply honey?? She has no CPU.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Nopes buddy, don't try that as of now... However I'm planning to upload one for the CwM App soon... Wait for a couple of days... I want to make sure its 100% safe before I release it publically. Till then, you can ask her to just borrow your PC or any other PC to flash it... Just need ODIN and the drivers...
Guess I'll try it out as soon as I flash Simple Honey (downloading it right now).
EDIT: Sweet, worked great, and no more rainbow! Also love the easy way to get into recovery and download. Thanks.
Longcat14 said:
Guess I'll try it out as soon as I flash Simple Honey (downloading it right now).
EDIT: Sweet, worked great, and no more rainbow! Also love the easy way to get into recovery and download. Thanks.
Click to expand...
Click to collapse
Enjoy your phone..
can i use the GB bootloader with a 2.2.1 rom.
paranoia_gu said:
can i use the GB bootloader with a 2.2.1 rom.
Click to expand...
Click to collapse
Yes its backward compatible for Froyo so both 2.2 and 2.2.1 would work...
I flashed gb bootloaders a while ago if I flash froyo ones will my phone brick
Hey guys... ok i have been looking and cant seem to find how to rectify this issue... i am really stuck and would appreciate any help possible..
Ok so i had stock 2.2 on my captivate, n tried to install a gingerbread rom using mobiletechvideos easy step guide using this link
http://www.youtube.com/watch?v=UOyx5JQ_8_I
... in doing that the first step of installing the bootloaders through odin, i inserted the pda files but it freezes at setup connection... now i think its soft bricked as i can still put it in download mode.. the thing is i have tried one click odin to revert back to 2.1 or 2.2 but it stops at set pit file... and then do not turn off target... its been here for over 25 mins n nothing... i have kept trying a couple of times and sometimes it wud just say fail.. Guys again i am sorry if this in the wrong place or has been brought up before.. i tried looking and was not able to find anything..
Thanks
Well your first issue there he says flash to stock 2.1 jf6 you where on 2.2 Unless your phone is a newer build 2.1 is always better to flash then 2.2. What build is your phone?
Reboot your computer, swap usb ports to one that is in the back attached to the motherboard (if already back there swap to a different one in the back) or port #1 on a laptop. Right click odin and run as administrator.
Thanks for the responses..
Yeah i know it said do it on 2.1, i figured it cud have worked on 2.2 i guess i was wrong... n in terms of switching port, odin still recognizes the port as i get the yellow screen but it doesn't move from there...???
It doesn't matter what's on the phone 2.1, or 2.2. **** you can be in a custom rom (I made the jump from firefly). If you are using odin its the same, if it will write 2.1 over anything why wouldn't do it for 2.3.3? No Difference.. The only way 2.2 would matter is if you weren't using odin then you would have to get around 3e recovery. But download mode is underneath the firmware does not matter what is on it odin will overwrite it.
And odin can be super touchy with the usb ports. And although it sees it the flash fails if odin is on the rag and didn't take any midol.
studacris said:
It doesn't matter what's on the phone 2.1, or 2.2. **** you can be in a custom rom (I made the jump from firefly). If you are using odin its the same, if it will write 2.1 over anything why wouldn't do it for 2.3.3? No Difference.. The only way 2.2 would matter is if you weren't using odin then you would have to get around 3e recovery. But download mode is underneath the firmware does not matter what is on it odin will overwrite it.
And odin can be super touchy with the usb ports. And although it sees it the flash fails if odin is on the rag and didn't take any midol.
Click to expand...
Click to collapse
again thanks for your help studacris... so basically if odin can read it but nothing happens i am screwed... i really need to know if there is absolutely anything else i can do to fix this as this is my only means of communication.. i am lost without my cappy...
Are you sure you are using a Motherboard usb port and that you are running on Admin? If odin is being stupid you can look in to Heimdall
prbassplayer said:
Are you sure you are using a Motherboard usb port and that you are running on Admin? If odin is being stupid you can look in to Heimdall
Click to expand...
Click to collapse
yeah i am sure i am using it on the motherboard port and running it on admin.. It basically freezes on differnt areas and doesnt completely reflash to stock on odin3 one-click downloader...
So there is nothing else i cud do with odin rite??
rheanjd said:
yeah i am sure i am using it on the motherboard port and running it on admin.. It basically freezes on differnt areas and doesnt completely reflash to stock on odin3 one-click downloader...
So there is nothing else i cud do with odin rite??
Click to expand...
Click to collapse
Try a different version of odin. If that dont work then use Heimdall
You can go to samfirmware.com-US SGS download wich ever version u want (id use JF6) download and decompress. Each .md5 file you need to decompress as well and get out the individual file in them. Here is a good how too with heimdall from mobiltechvideos. Hope this helps
prbassplayer said:
You can go to samfirmware.com-US SGS download wich ever version u want (id use JF6) download and decompress. Each .md5 file you need to decompress as well and get out the individual file in them. Here is a good how too with heimdall from mobiltechvideos. Hope this helps
Click to expand...
Click to collapse
Thanks.. i was hoping odin wud have come through but i guess i will have to try heimdall...
Ok guys i have downloaded heimdall and right now trying to install the jf6 2.1 rom... the thing is i am on load package and tyring to put the firmware package... this might be a stupid question but i am inserting the zipped file but it keeps saying - Tar header contained an invalid file size... Do i need to extract the files and then do this..???
rheanjd said:
Ok guys i have downloaded heimdall and right now trying to install the jf6 2.1 rom... the thing is i am on load package and tyring to put the firmware package... this might be a stupid question but i am inserting the zipped file but it keeps saying - Tar header contained an invalid file size... Do i need to extract the files and then do this..???
Click to expand...
Click to collapse
Wich Heimdall you using? I suggest 1.1.1 in wich you choose each file u want to flash individually.
i had downlaoded 1.3.0 will try this thanks..
ok so i have inserted factory fs, kernel,param,cache,database data,modem and clicked start, it took two seconds and then stated failed to retrieve config descriptor...??
also i haven't added anything in the pit or primary and secondary and recovery files
rheanjd said:
ok so i have inserted factory fs, kernel,param,cache,database data,modem and clicked start, it took two seconds and then stated failed to retrieve config descriptor...??
also i haven't added anything in the pit or primary and secondary and recovery files
Click to expand...
Click to collapse
Im not sure about your error but the Jf6 from samfirmware has FactoryFS, Param.lfs, Cache, Database Data, Modem and Recovery(Zimage). Maybe you put a file in the wrong place?
Thanks but istn't the zimage supposed to be for the kernel... i haven't inserted anything into the recovery field...
i am rite now left clueless
No your right. Its the kernel I had a brain fart. Well I honestly Do not know whats wrong, Im assuming you ran Heimdall as Admin... Well **** man any way you have access to another machine? Im out of ideas maybe someone else can help. =/
Hey thanks i really appreciate the help ...
guys if anyone else can help me out it would be really appreciated... the phone is all i got and i really need it to work today... i am just restarting my computer and will try again hopefully it will work otherwise i am out of options...
Ok restarted and giving the same issue...
"Failed to retrieve config descriptor"
what the hell is that???