Related
Hi guys,
Can anyone tell me how to remove a bootloader or switch it to another bootloader?
I accidently flashed GT-I9000 bootloader onto my captivate and now my phone thinks that it's GT-I9000.
In bootup, a screen of "Galaxy GT-I9000 Samsung" stays on for 5 sec, and then AT&T logo&animation shows up after that.
Below is the full explanation how I ended up with this situation. It's kinda long, so if you know the solution to this problem right away, I guess you don't need to read all of it.
Anyways, thanks in advance!
So Here's what happened. I was upgrading my (rooted/froyo) captivate to gingerbread (continuum v5.4.1) In the instruction, it suggested to return to stock so I did that and my phone went back to eclair.
Then there was another optional suggestion saying that "only if you don't have bootloaders - install JVB bootloaders" and that's where my problem began.
I downloaded the 'galaxys-bootloader-JVB.tar.md5' and flashed it in Odin and my phone now thinks that it's GT-I9000. For a moment, I thought my phone was bricked, but I managed to turn it back to 2.1.
but still whenever I turn on my phone the 'Galaxy S GT-I9000 Samsung' screen shows up for like 8 seconds and then move onto AT&T screen.
Phone still operates and runs on eclair, but funny thing is every time I want to use "download mode" I have to press 'Volume down key + power, which is for Vibrant or Fascinate, instead of holding both volume up + down keys, which is for Captivate.
Same thing for "recovery mode" I have to press down VOL down + power button. This clearly shows that the phone thinks it's Vibrant, not Captivate.
Please Please Please can anybody tell me how to revert it?
samzoferrari said:
Hi guys,
Can anyone tell me how to remove a bootloader or switch it to another bootloader?
I accidently flashed GT-I9000 bootloader onto my captivate and now my phone thinks that it's GT-I9000.
In bootup, a screen of "Galaxy GT-I9000 Samsung" stays on for 5 sec, and then AT&T logo&animation shows up after that.
Below is the full explanation how I ended up with this situation. It's kinda long, so if you know the solution to this problem right away, I guess you don't need to read all of it.
Anyways, thanks in advance!
So Here's what happened. I was upgrading my (rooted/froyo) captivate to gingerbread (continuum v5.4.1) In the instruction, it suggested to return to stock so I did that and my phone went back to eclair.
Then there was another optional suggestion saying that "only if you don't have bootloaders - install JVB bootloaders" and that's where my problem began.
I downloaded the 'galaxys-bootloader-JVB.tar.md5' and flashed it in Odin and my phone now thinks that it's GT-I9000. For a moment, I thought my phone was bricked, but I managed to turn it back to 2.1.
but still whenever I turn on my phone the 'Galaxy S GT-I9000 Samsung' screen shows up for like 8 seconds and then move onto AT&T screen.
Phone still operates and runs on eclair, but funny thing is every time I want to use "download mode" I have to press 'Volume down key + power, which is for Vibrant or Fascinate, instead of holding both volume up + down keys, which is for Captivate.
Same thing for "recovery mode" I have to press down VOL down + power button. This clearly shows that the phone thinks it's Vibrant, not Captivate.
Please Please Please can anybody tell me how to revert it?
Click to expand...
Click to collapse
Odin3 one click back to stock. Your fine that's just the kernel bootloader. If you want continuum it will have the GT-I9000 bootloader, but there are other roms and kernels without it. The odd button combinations you have to use are part of the kernel as well. Flash stock then I suggest flashing Cognition after if it will not revert to stock kernel. You can flash froyo over eclair without having to update bootloaders. Also if your running a AT&T Captivate you should be having that boot animation before the GT-I9000 anyways. Sorry if this doesn't help your problem.
thanx! i guess that's not a major issue right? as long as there's no problem using the phone, i'm cool with that although it takes extra 4 ~ 5 sec to boot up. Anyways, thanks for your reply.
First, the new button combos are not part of the kernel. They are part if the secondary bootloader. If you think you are going to flash another gingerbread rom in the future, just leave it as is. They are compatible with 2.1/2.2 roms, with the exception of Cognition. DO NOT FLASH COGNITION UNTIL YOU ARE 150% CERTAIN YOU HAVE FROYO/ECLAIR BOOTLOADERS. The reason is, cog adds a secondary bootloader(sbl.bin) to its flash. If you try mixing aGB primary bootloader with a froyo secondary, you will have a permanent, can't recover, $500 paperweight, brick. Also, do not try to use the odin with 3 button fix, for the same reason above.
mrhaley30705 said:
First, the new button combos are not part of the kernel. They are part if the secondary bootloader. If you think you are going to flash another gingerbread rom in the future, just leave it as is. They are compatible with 2.1/2.2 roms, with the exception of Cognition. DO NOT FLASH COGNITION UNTIL YOU ARE 150% CERTAIN YOU HAVE FROYO/ECLAIR BOOTLOADERS. The reason is, cog adds a secondary bootloader(sbl.bin) to its flash. If you try mixing aGB primary bootloader with a froyo secondary, you will have a permanent, can't recover, $500 paperweight, brick. Also, do not try to use the odin with 3 button fix, for the same reason above.
Click to expand...
Click to collapse
Secondary as in the 3rd animation because I highly doubt that.You should have an AT&T screen, then your galaxy s bootloader, then your rom bootloader. the rom bootloader animation is changable and does not include the power button volume up combo. I'm not a developer, but based on my experience you CAN use odin with 3 button fix over contiuum and then flash cognition after. I highly doubt there will be a brick. For example, you want the new cm7 build. You can flash odin 3 button, flash cmw through rom manager or a zip with 2e recovery. Then flash cognition. you are at the 2.2 bootloader now. You can now begin to work towards the 2.3.4 without any issues. And there are different requirements for different gingerbread roms. some are 2.3.3 and some are 2.3.4 and you CAN NOT flash between the two.
samzoferrari said:
thanx! i guess that's not a major issue right? as long as there's no problem using the phone, i'm cool with that although it takes extra 4 ~ 5 sec to boot up. Anyways, thanks for your reply.
Click to expand...
Click to collapse
It's no big deal don't let this guy make you think your about to brick if your not 150% sure. There are also different bricks and this could cause a soft which is also recoverable by odin.
thanx! i guess that's not a major issue right? as long as there's no problem using the phone, i'm cool with that although it takes extra 4 ~ 5 sec to boot up. Anyways, thanks for your reply.
Click to expand...
Click to collapse
Just for safety's sake, though, it would probably be good to read through this before moving forward:
The Definitive Guide to Bricking
jmtheiss said:
Just for safety's sake, though, it would probably be good to read through this before moving forward:
The Definitive Guide to Bricking
Click to expand...
Click to collapse
That guide knows a lot more then I do. I suggest reading that aswell! I was speaking strictly based on experience.
If you attempt to flash the 3 button fix with gb bootloaders, you will brick. Go ask any one in gb rom forum. If you reflash froyo bootloaders, to replace gb bootloaders, before you flash 3 button, you should be ok. But if you choose to believe the other guy, and your still under warranty, tell att that your phone stopped working when you tried to update with kies.
EsotericSYN said:
Secondary as in the 3rd animation because I highly doubt that.You should have an AT&T screen, then your galaxy s bootloader, then your rom bootloader. the rom bootloader animation is changable and does not include the power button volume up combo. I'm not a developer, but based on my experience you CAN use odin with 3 button fix over contiuum and then flash cognition after. I highly doubt there will be a brick. For example, you want the new cm7 build. You can flash odin 3 button, flash cmw through rom manager or a zip with 2e recovery. Then flash cognition. you are at the 2.2 bootloader now. You can now begin to work towards the 2.3.4 without any issues. And there are different requirements for different gingerbread roms. some are 2.3.3 and some are 2.3.4 and you CAN NOT flash between the two.
Click to expand...
Click to collapse
Cm7 doesn't use gb bootloaders
Please don't double post.
Miami_Son said:
Please don't double post.
Click to expand...
Click to collapse
I apologize. The tone conveyed by the person I was responding to simply infuriated me. I do know better, just lost it for a second.
Flashing a New rom from Mosaic II
mrhaley30705 said:
Cm7 doesn't use gb bootloaders
Click to expand...
Click to collapse
So not to dig up an old post, but I guess I will...
I am running
Mosaic II
Kernel 2.6.35.7-I9000XWJVB-CL118186
2.3.3
So basically in the same boat as the OP. Running GB boot loaders for the I9000, I'm ready for a new ROM and for the first time I'm worried about a perma brick.
I am wanting to load up CyanogenMod 7
http://forum.xda-developers.com/showthread.php?t=978150
What do I need to do abt the boot loaders, can I leave them and just flash with ClockworkMod Recovery?
Thanks!
JP
Don't **** with the bootloaders. flash back and keep them stock. It's risky and unneeded. Flashing them for ANY ROM is retarded. The developers who require this are retarded. RETARDED.
The only reason to upgrade bootloaders is for the unofficial 2.3 upgrade... Which is likely laziness on Samsung's part. Do not go flashing a SBL without a PBL ever. This is bad practice and can only lead to several bricks when a SBL is released without a matching PBL. The developers who require flashing a SBL without a PBL are retarded. RETARDED.
Yep. I said it, we have retarded developers here in the forums who should be stripped of their recognized tag.
OK on the subject but not so much.... Is there a code or system manager (like sgs tools) that indicates what BL you have installed?
Or does the kernel spell that out for you? ex. Kernel version 2.6.35.7-i9000xxjvr-clCL425308 Would this indicate a i9000 BL?
I notice on the rom I use, people are asking constantly which BL is the right one!
I understand both have their + & - but there must be a way of finding which one is installed, through the phone
tomween1 said:
OK on the subject but not so much.... Is there a code or system manager (like sgs tools) that indicates what BL you have installed?
Or does the kernel spell that out for you? ex. Kernel version 2.6.35.7-i9000xxjvr-clCL425308 Would this indicate a i9000 BL?
I notice on the rom I use, people are asking constantly which BL is the right one!
I understand both have their + & - but there must be a way of finding which one is installed, through the phone
Click to expand...
Click to collapse
Hold Vol - and Power for about 10 seconds. If you reboot to download, you have the I9000 GB bootloaders. That's at least one variable eliminated.
If, after doing that, you realize you're on a Gingerbread rom without issues and the button combo does nothing, you have the i897 GB bootloaders.
jmtheiss said:
Hold Vol - and Power for about 10 seconds. If you reboot to download, you have the I9000 GB bootloaders. That's at least one variable eliminated.
If, after doing that, you realize you're on a Gingerbread rom without issues and the button combo does nothing, you have the i897 GB bootloaders.
Click to expand...
Click to collapse
Sorry should have stipulated.... other then the step you've mentioned.
I was looking to see if anyone has created a script or app that can tell you this
Hello,
I have a unlocked and rooted Captivate. Recently in installed OCLF Lag Fix and did "OneClickLagFix V2+". It is safe to update to android 2.2 from 2.1? If yes, then what is the best way?
Thanks in advance.
Just disable lagfix and flash any custom 2.2 ROM you want inside CWM.
Sent from my SAMSUNG-SGH-I897
Reamer09 said:
Just disable lagfix and flash any custom 2.2 ROM you want inside CWM.
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
Thansk for the reply. I will do it tomorrow. I am new to android, I hope all goes well. Will update my results.
OCLF is so 2k10
*If you're not on Gingerbread, you should be shot*
Don't forget to remove the ext2 tools after disabling lagfix.
cappysw10 said:
OCLF is so 2k10
*If you're not on Gingerbread, you should be shot*
Click to expand...
Click to collapse
The only time my phone has ever been on lagfix is when the ROM I flash comes with it. I really don't see any difference at all in performance with or without it. The only reason I'm not on GB is because I had TONS of problems with apps working and got fed up with it. If my signature still says KF1 then its old. I'm on XDA app so I can't tell.
Hello All, Finally I updated my Captiavte with Andriod 2.2 few days ago. I was not able to do that before because of some issues."
I un-lagfix my mobile and used Odin3 v1.0 to flash "I897UCKB1-homeBinary.tar ROM...
I feel now that my mobile is slower then before... But got some new features.
Can anyone tell me difference between "I897UCKB1-homeBinary.tar" and ''I896UXJL1-stock"?
hno866 said:
Hello All, Finally I updated my Captiavte with Andriod 2.2 few days ago. I was not able to do that before because of some issues."
I un-lagfix my mobile and used Odin3 v1.0 to flash "I897UCKB1-homeBinary.tar ROM...
I feel now that my mobile is slower then before... But got some new features.
Can anyone tell me difference between "I897UCKB1-homeBinary.tar" and ''I896UXJL1-stock"?
Click to expand...
Click to collapse
Look at the first
4 letters. I896 is a canadian Captivate. No idea what jl1 is (2.1 or 2.2).
Hello All,
I applied lagfix on my android 2.2 OS and wow!!! speed is now 200% increased!!!!
Is 2.3 available for captivate ?
Many flavors of 2.3, just be sure to read the installation instructions and understand GB bootloaders before trying.
2.1 to 2.2 to Black Screen to Semi brick to Working Captivate...
Hello All,
I had some heck of the experiences in last 2 weeks which I would like to share.
-> I had successfully updated my captivate from Android 2.1 to 2.2. Using "I897UCKB1-homeBinary.tar" ROM from BriefMobile site. After this update my three button combo for entering recovery mode stopped working. I could only go into downloading and recovery mode by using Android SDK.
-> And as written in my earlier post, I felt that speed is slow so i "lagfix"-ed it. This gave very good results and all was working fine...
-> Until one day... I was installing blik calendar widget after downloading it from site(I don't remember link now)... This installation never ended, it was continuing even after 15 mins so I used Task Killer to kill the installation... After that it became very slow... I restarted the mobile and what the hell!!!! mobile was stuck at boot screen... Mobile was stuck at "S" logo.
-> I tried all the combos I could find on net to enter into downloading mode but none work. Computer was not recognizing captivate while it was stuck as S logo.
-> After few days I used USB JIG method to bring my captivate into downloading mode.
-> Tried to flash earlier installed ROM "I897UCKB1" via Odin 3. It was successful but now after boot animation I was getting black screen. Lights on button were glowing on pressing and mobile was vibrating but ... It was in useless state.
-> Tried to flash "I896UXJI2" ROM, same condition as above.
-> Then I tried to Flash "I897UCJF6-final-OCD-REV0.zip" downloaded from xda... with repartition option checked. It stucked in between and i had to remove battery.
-> Now mobile was in Semi Brick state.
-> All this time mobile was "lagfix"
-> Then somehow I got back my captivate using :
http://forum.xda-developers.com/showpost.php?p=7614957&postcount=6
-> Now captivate is working find but still 3 button combo is not working...
Which ROM should I use now to upgrade to for 2.2?
Is custom ROM better? Cognition !!!
Should I install ClockworkMod Recovery?
Which ROM should I use now to upgrade to for 2.2?
Is custom ROM better? Cognition !!!
Should I install ClockworkMod Recovery?
Click to expand...
Click to collapse
First, if you are at stock 2.1 eclair, you can use the 3-button odin one-click. As long as you have the eclair/froyo bootloaders, that will work properly. But for the love of all that is sacred and captivatible, make 100000000% sure you have the proper bootloaders first. Flash back to stock eclair if necessary to make sure of this. I cannot stress this enough. If you do not have the eclair/froyo bootloaders in place before using the 3-button fix, you will murder your phone. It will die, and you will most likely have to pay real money to get it fixed. Make sure you have the eclair/froyo bootloaders before using the 3-button fix.
(Sorry. I just wanted to make sure that you avoid an all-too-common issue on the board.)
What may be a better option for you would be to upgrade to Gingerbread. Part of that upgrade process will flash the GB bootloaders, which will automatically have your button combinations fixed.
In either case, there is some level of bootloader flashing involved, which does mean some level of risk - make sure to read up on it thoroughly before you do anything.
And custom roms, in my opinion, are always better than stock. Clockworkmod Recovery is something you'll definitely want to have (and is usually included in the kernels that you'll flash along with custom rom upgrades).
hno866 said:
Hello All,
I applied lagfix on my android 2.2 OS and wow!!! speed is now 200% increased!!!!
Is 2.3 available for captivate ?
Click to expand...
Click to collapse
There are several roms that I897 GB based right now.
Like Atomic Fusion 1.5 and Cog v2, both are awesome roms.
Both will be developed even further, when source comes out! (The Official 2.3 update from ATT)
I am in desperate need of help you guys! I screwed up so hard that I don't even know where to begin...
THE SITUATION:
-Right now when I go to turn on my phone, it will only stay on the current SAMSUNG GALAXY S I9000 screen (the very first screen when booting your phone) and it keeps flashing in and out.
Before trying to use Odin to put back the original Kernal on my phone, it was just stuck as the SAMSUNG GALAXY S I9000 screen, still wouldn't start. <I followed this website step by step>
http://www.samsunggalaxysforum.com/...-to-a-stock-rom-after-installing-darky's-rom/
BEFORE ALL OF THIS EVER HAPPENED:
I finally rooted my phone and manage to download Clockworkmod recovery on my phone and then used it to flash Darky's 10.2 custom ROM. Everything turned out great except at the beginning of the boot, the screen turned all rainbow coloured, completely distorted, and it continued to do that. I then tried to go back to Recovery mode to do the Voodoo lagfix but I couldn't even get into the recovery mode anymore, it either wouldn't let me, or it did but the screen didn't go to it properly (more likely the first one). I read somewhere that if you reflash your phone again, it should make all the tweeks go away. So I tried that from the Darky's tools menu and ever since then, I've been stuck with the Boot Screen this whole time...
I already bricked my phone once, and that was before the Flashing Boot Screen.
I really need help you guys, I would at least like to have my phone back to the original basis, at least! Your help would be greatly appreciated!
THANK YOU
P.S. (i'm not that great at all this phone tweeking, but I've succeeded in doing it up until yesterday)
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
gfacer said:
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
Click to expand...
Click to collapse
Yes, I can get into download mode! (thank you for reading my post).
If it's not too much to ask, could you maybe find the ROM that would be good for me to flash, considering my situation?
I want to be sure that it's what the top tech guys would recommend
A link would be appreciated
thank you again!
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
gfacer said:
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
Click to expand...
Click to collapse
So in essence all I have to do is flash the Darky ROM V10.2 with Odin using the Download mode on my phone and it should be okay?
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well...I did everything you said. The ROM is on there alright, it flashed and everything (And I know this because now when the boot screen STILL FLASHES, the darkcore & darky's rom logo are on it too).
THIS TIME AROUND:
The stock recovery seems to work...
any ideas??
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Alright I'll try and reflash the same one using a different version of odin the. I'll let you know what happened
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
tried ezodin, flashed it, and i still get the exact same thing I've exhausted every single possibility there is!!!
I really need help on this, my warranty is not gonna do anything because i have the phone rooted..
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
gfacer said:
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
okay that could be useful data potentially (let's hope it won't have to be).
If you didn't see my reply from the other thread, here it is:
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Ok, so just to be 100% on this
-I should flash Darky's 9.2 froyo onto my phone,
-then I should flash regular GB onto my phone (Not sure about the bootloader part though, if you could clarify that)(Also where would I get JUST a stock GB ROM?)
-then I can flash a custom GB ROM?
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
roma17 said:
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
Click to expand...
Click to collapse
I think you are right but other than trying again and again, which I've done before -though now I know why I had too - I am out of suggestions. Good Luck and if I have a brainwave I'll let you know.
Sent from my GT-I9000M using XDA Premium App
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
gfacer said:
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
Click to expand...
Click to collapse
Okay, basically at this point, I just want my phone to work I've tried what you said. I remember that before rooting my phone initially I was running Froyo 2.2.1. So I found the ROM for that ( http://www.samfirmware.com/WEBPROTECT-i9000.htm ) Just like you said. I downloaded from the *Provider Samsung Galaxy S i9000 heading and picked the I9000BOJS5 ## from February 2011 because I think somewhere around there I updated my phone to Froyo. Flashed it, did everything, still no luck.
I've had a recent hunch though. When the bootscreen boots up, it keeps saying i9000 only, when before it used to say i9000M at least for a little bit (yes my phone is i9000m). Is there a stock froyo rom that's specifically designed to go with the i9000m model? Or are they just all the same?
Never give up
-Thank you so much
1st I'm a total noob!
So, I recently got a I897 with FROYO 2.2 on it from AT&T as an upgrade. It's my first Android (and my 1st smartphone for that matter)
I bricked it a couple of times, bought a jig then managed to successfully follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1127249
AND I got it rooted via the same post's instructions.
Now my phone shows:
SAMSUNG-SGH-I897
2.3.3
I897UCKF1
2.6.35.7-I897UCKF11-CL2373832
GINGERBREAD.UCKF1
What I don't know is am I running GB on the FROYO boot loaders?
And, should I update the boot loaders as described in this post:
http://forum.xda-developers.com/showthread.php?t=1129821
???
I'm wanting to upgrade the Kernel to KJ3 or maybe KK1...
Advice?
Thank You In Advance For Your Response!
My guess is (and it's just a guess) that since you're running a Gingerbread rom, you have Gingerbread bootloaders.
V V V Froyo bootloaders will boot into gingerbread. The kernel splash will be broken and recovery is unaccessable.
That being said, leave the bootloaders alone. At this point, there are really no reasons to touch them again except in extreme circumstances (warranty return, some future update that has new bootloaders like ICS).
^^^Froyo bootloaders will boot into gingerbread. The kernel splash will be broken and recovery is unaccessable.
Op, When you boot up do you get a weird screen that looks like white noise? If so you have froyo bootloaders, if all looks ok then they are gingerbread.
My guess is that the one click you used included the boot loaders. Don't remember ever seeing a one click without them.
Sent from my SAMSUNG-SGH-I897 using XDA App
When I boot up I get the AT&T screen, followed by a lock screen that tells me there's no sim card installed... (This phone is for playing with... I bought another just like it from EBAY already 2.3.3 and rooted to use )
Then it scans everything and acts just as you would expect... No White noise or other visible glitches.
studacris said:
^^^Froyo bootloaders will boot into gingerbread. The kernel splash will be broken and recovery is unaccessable.
Op, When you boot up do you get a weird screen that looks like white noise? If so you have froyo bootloaders, if all looks ok then they are gingerbread.
Click to expand...
Click to collapse
So I should be good to upgrade to kj3 just using Odin3v1.85 and the boog_Kj3_kernel3.tar?
If I do that will I need to re-root? and will the Fugu Root (zImage-root.tar) work on this kernel as well??
THANKS AGAIN for all the answers!
Yup to both
studacris said:
Yup to both
Click to expand...
Click to collapse
COOL!! The object here is to use the "Test" phone to find the upgrade(s) I like best. Then, once I know everything works I'll upgrade my "in-use" phone and start playing with the test phone again!
I've already found that the boot mode jig and Titanium Backup Pro are my FRIENDS!
Thanks for answering all my noobie questions Y'all!
How can you find wich Gingerbread bootloader your using I9000 or I897.
Easy...does the very first screen when you boot say at&t world phone or gt-I9000?
To get into recovery do you press all 3 buttons or just volume up and power?
If the first options are what you have that is the captivate boots.
The second options are I9000.
Also if you PAY ATTENTION TO WHAT YOU FLASH you should know...
MidniteMarauder said:
My guess is that the one click you used included the boot loaders. Don't remember ever seeing a one click without them.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
My kf1 thread (see sig) didn't have bootloaders. Also, jmtheiss made one or two Heimdall one clicks without then. Just fyi.
Is there a commend to display which bootloaders I'm running? I've seen people say you can tell by which screens appear when booting or which buttons you have to press to get into recovery but I am looking for something more definitive or precise. Thx.
That is the only method, so you're best bet is that way -_-
b-eock said:
That is the only method, so you're best bet is that way -_-
Click to expand...
Click to collapse
Which metod? My Captivate does not show the Galaxy X screen when it boots up and to go into recovery mode I have to push both the volume up and volume down buttons and the power buttons. Which bootloader does that mean I'm running?
I897. Now which ROM are you running?
Sent from my SGH-I897 using xda premium
Here's the checklist:
First boot screen:
Black with "Galaxy S I9000" logo = i9000 bootloaders
White AT&T World Phone logo = i897 bootloaders
On a Gingerbread rom? You're using Gingerbread bootloaders
On an ICS rom? You're using Gingerbread bootloaders
On a Froyo rom? You could be on GB or Froyo/Eclair bootloaders. You'll have to remember whether you've ever flashed the GB bootloaders.
Or, you can just flash the GB bootloaders (i9000 or i897) and know for sure.
So, according to both of you my bootloaders are I897 (I didn't know I897 had anything to do with bootloaders!). I am running Doc's Master ICS V5 Final. I realize that theoretically you have to be using GB bootloaders to run ICS but I thought you could use the wrong bootloaders and just have a buggy phone. My broadband version starts with I9000 though. Is that unrelated to my "I897" bootloaders? Thanks for helping me learn!
The i9000 part you see is your modem which is required when using AOSP ROM (CM7, CM9, MIUI) Unless you want to use Nexus S modems. So yes you have I897 bootloaders. What ROM were you on before you flashed any ICS ROM?
@jmtheiss you don't have to have GB bootloaders to run ICS... Many people are too scared to flash them and don't want to.
Good to know. I thought that there might be a chance it was similar to the cm7 requirements.
I never knew CM7 required GB BL's....
lol scared to flash bootloaders... i flashed bootloaders 3 times on my two cappies the other day without palm sweat like i used to back in the day... lol running i9000 bootloaders with custom boot image now on both cappies. no more sleep death with Deep idle and liveOC!!
oh hey if going to ICS (which you will now or later) probably best to flash i9000 GB bootloaders. custom boot image link in my sig.
If I recall, from 2.2 I ran gb cyanogen rom for a few minutes then upgraded to ics and never looked back.
Sent from my SGH-I897 using xda premium
TRusselo said:
lol scared to flash bootloaders... i flashed bootloaders 3 times on my two cappies the other day without palm sweat like i used to back in the day... lol running i9000 bootloaders with custom boot image now on both cappies. no more sleep death with Deep idle and liveOC!!
oh hey if going to ICS (which you will now or later) probably best to flash i9000 GB bootloaders. custom boot image link in my sig.
Click to expand...
Click to collapse
i have read that flashing bootloaders is risky and can hard brick your phone? is this a common myth that people are scared of or is the process reversible? i am having a lot of random shut offs especially with wifi on. i clean and wiped everything and using GB bootloaders but it seems the issue persists. i am desperately trying to find a fix, i am running doc masters v6 rom. do you have any advice and if the i9000 bootloaders may fix my issue?
Its no myth. only way to hard brick is if the bootloaders are missing or corrupted.
he was just saying that people stress it too much. I too have flashed boots plenty of times with no issues at all. hell, we all used to use Odin one click, some even recommended it between every ROM flash (way back in the day), which contains boots.
My captivate is 17 months old and going strong, just make sure you've got a good connection by flashing a nobootloader package a couple times, then if that goes good, flash the bootloaders and you should be fine.
I felt same way about doing my first flashing. Now it is a walk in park!! I load a different ROM about every other day. Do your backups!!!
Sent from my SGH-I897 using XDA
You're using the normal gingerbread bootloaders for captivate, please correct me if I am wrong here.
Sent from my SGH-I897 using XDA