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
Related
so I was trying to flash the new miui 1.7.8 on my captivate and one of the step is to flash back to orig.
using odin 1.7 when I flash the phone its gone.
1- No power
2- PC doesnt recog the phone at all
3- charger not charging
so basically the phone wont come or wont charge.
tried one button to boot up in recovery but no luck...any idea?
maxximboy1 said:
so I was trying to flash the new miui 1.7.8 on my captivate and one of the step is to flash back to orig.
using odin 1.7 when I flash the phone its gone.
1- No power
2- PC doesnt recog the phone at all
3- charger not charging
so basically the phone wont come or wont charge.
tried one button to boot up in recovery but no luck...any idea?
Click to expand...
Click to collapse
What were you on before trying to flash? The newest Miui rom does not state nor is it required to flash back to stock using ODIN. What happened with ODIN when going back to stock? Did you not try using ODIN 1 click? Please give much clearer detail on your process if we want/try to help you.
i was on apex 8.x and thinking to go back to miui again. it said if you are on cm7 or miui then dont need to flash back to orig.
and since i was not, i use odin 1.7 and use cm7 initial kernel to flash my captivate. it flash successfully and when i tried to reboot phone there were no pwer and no charging.
thankx
maxximboy1 said:
i was on apex 8.x and thinking to go back to miui again. it said if you are on cm7 or miui then dont need to flash back to orig.
and since i was not, i use odin 1.7 and use cm7 initial kernel to flash my captivate. it flash successfully and when i tried to reboot phone there were no pwer and no charging.
thankx
Click to expand...
Click to collapse
Is apex 8 on 2.3 bootloaders? If so that could have been part of the issue. Miui runs 2.2 boatloaders so if you didn't flash to 2.1 or 2.2 before going back it's possibly why your phone is currently dead. Doesn't mean it's bricked. Search in the general forum for adamoutletter or someone close to that for a thread on recovering from hard bricks.
Glitch kernel let me OC to 1.4!
What .tar did you use with odin to flash back to stock? (don't say the one with the 3 button fix)
if it's a Hard brick, only option is jtag. Mobiletechvideos.com offers that service for $50 u.s. His username on here is connexion2005.
Sounds like Stud hit the nail on the head. You're not screwed, just not a happy person.
"Is apex 8 on 2.3 bootloaders? If so that could have been part of the issue. Miui runs 2.2 boatloaders so if you didn't flash to 2.1 or 2.2 before going back it's possibly why your phone is currently dead. Doesn't mean it's bricked. Search in the general forum for adamoutletter or someone close to that for a thread on recovering from hard bricks.
Glitch kernel let me OC to 1.4!"
===
tried but have no idea how to use usb or other way of jig....sorry not that technical
my phone is under warranty as of purchase date, what if i send to samsung will they know?
maxximboy1 said:
"Is apex 8 on 2.3 bootloaders? If so that could have been part of the issue. Miui runs 2.2 boatloaders so if you didn't flash to 2.1 or 2.2 before going back it's possibly why your phone is currently dead. Doesn't mean it's bricked. Search in the general forum for adamoutletter or someone close to that for a thread on recovering from hard bricks.
Glitch kernel let me OC to 1.4!"
===
tried but have no idea how to use usb or other way of jig....sorry not that technical
my phone is under warranty as of purchase date, what if i send to samsung will they know?
Click to expand...
Click to collapse
I'm not sure if Sammy'll know or not. Others maybe be able to lend you some advice as far as that goes. In all honesty, I'd avoid troubles and shoot connexion2005 a PM. I'm pretty sure he'll be able to fix it regardless of what's wrong with it. If it indeed is that you flashed over 2.3 BL, I'd say it's your best bet.
I mean Samsung might warranty, but I'm not sure, so I'm not going to say that they will or won't.
thax sending him msg
I used Odin3 to flash back to stock/master clear. Man it feels so ancient!!!
Anyway, I've read a few different tutorials and just wanted to know which one do ya'll suggest is the best one to get to Gingerbread 2.3.3.
Thanks.
This seems the easiest and at least I'll be on the official I897 bootloaders...
Opinions?
http://forum.xda-developers.com/showthread.php?t=1129821
I found this to be the easiest/fastest way: http://forum.xda-developers.com/showthread.php?t=1127249&highlight=odin+kf1
AtomicFusion, Cog 5, and the one you already found are all simple "one-click" setups. They also are all I897 bootloaders.
For I9000 Bootloaders the accepted method is double flash via Odin (once for "stock" bootloaders, then once more for a CWM capable kernel/recovery) then CWM in your choice ROM.
You can use either or and the phone will boot and run on any ROM. The thing is, from ppls reports you might wanna try to keep your bootloaders aligned with your ROM base. There seems to be a few quirks but they have been minor problems ie. some "system" apps FC'ing. Using alternatives off the market can get you around those.
xThe Enforcer said:
I used Odin3 to flash back to stock/master clear. Man it feels so ancient!!!
Anyway, I've read a few different tutorials and just wanted to know which one do ya'll suggest is the best one to get to Gingerbread 2.3.3.
Thanks.
Click to expand...
Click to collapse
I used the 1 click KF1 with optional fugu root (I did not use the root, i just flashed DG's Cog 5 kernel and used Cwm from there). Very simple and worked well (and i actually like i897's key combos) else u can just flash i9000's.
^ +1
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Decided that I want to go with the latest Mosaic ROM.
Seems like most of the devs are still on I9000 bootloaders so should I just follow their tutorial in the OP of the Mosaic thread?
Why haven't they switched to the I897 bootloaders? I9000 more stable or something?
Thanks...
Yes use our instructions.
We haven't switched because the captivate ones bork the music player we include that has lock screen controls and who knows what other issues down the road...
Plus the I9k ones have much better button combos...
studacris said:
Yes use our instructions.
We haven't switched because the captivate ones bork the music player we include that has lock screen controls and who knows what other issues down the road...
Plus the I9k ones have much better button combos...
Click to expand...
Click to collapse
Yeah, I was just searching the Mosaic thread and saw about the music player.
I just flashed to 2.3.3 with the I9000 bootloaders so I'm good to go now... Does the old Firefly theme work with the latest Mosaic? Thanks Studacris
Just read that the Firefly theme should work... Woohoo!
We have firefly theme for MVI so no need to worry about it, Once u are done with the flashing just check the OTA on the phone.
prbassplayer said:
(and i actually like i897's key combos)
Click to expand...
Click to collapse
What are the new GB BL i897 combo's?
They aren't any different than before.
Only the I9k boots have different combos.
rkkaranrk said:
We have firefly theme for MVI so no need to worry about it, Once u are done with the flashing just check the OTA on the phone.
Click to expand...
Click to collapse
Thanks. I went on the OTA app and it keeps saying, download unsuccessful... Hmn...
Palmetto_X said:
What are the new GB BL i897 combo's?
Click to expand...
Click to collapse
Like studacris said I897 key combos don't change just the I9000's. I9000's Recovery and down load is either Vol down+power or Vol up+power. I897's is Vol up down+power for recovery and Vol up down+usb for download mode. But its personal preference.
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.
I've used Serendipity 7, and a few other ROMS prior to that, such as Cognition etc. Somehow I ended up with GT-I9000 bootloader I think. I have to flash everything back to stock for ATT warranty exchange. When I first turn the phone on, it shows black i9000 galaxy S screen, than goes to ATT white world phone screen, than animations for att 3G and animation for a glowing S. Before it would show Black GT-I9000 and then, Serendipity7 logo. But I just flashed http://forum.xda-developers.com/showthread.php?t=1145149 thinking this stock exe will revert the bootloader as well.
My questions are how do I get rid of black I9000 screen upon boot up in favor of whatever att image is supposed to be there.
Also that stock ROM I flashed, is it stock ATT 2.3.3? Kernel version shows 2.6.35.7-I897UCKF1-CL273832 Build number GINGERBREAD.UCKF1 Model number SAMSUNG-SGH-I897 Baseband I897UCKF1 Firmware 2.3.3 I am just not sure about kernel version.
Also, I have another Cappy with Serendipity 7 and GT-I9000 black screen upon startup, which I assume is a bootloader... again. This here http://forum.xda-developers.com/showthread.php?t=1367586 says
So it seems like everyone who started experiencing charge death on BUILD 15 are running I9000 bootloaders. BUILD 15 includes kernel changes which fixes stuff for Captivate users (with Captivate bootloaders), so I hereby declare that I9000 bootloaders are unsupported and unrecommended.
Click to expand...
Click to collapse
So how do I flash ICS on it now? Need to get rid of that bootloader.
First of all, that stock ROM you posted clearly states "No bootloaders" in the title. You need to find a stock ROM that has bootloaders. Find one in this thread. Regarding the THS ICS, i9000 boots were never proven to actually be the source of the problem, as people with regular bootloaders were encountering the same issues. However, they still aren't recommended since any issues with them won't be addressed.
flash the captivate gingerbread bootloaders and captivate gingerbread stock KK4.
done.
you dont need to be on the stock you got the phone with. just an official ATT stock. KK4 gingerbread with kk4 gingerbread bootloaders is just fine.
for your second phone... any captivate / i9000 bootloader works for ICS.. what do you mean by it boots to blank screen? does it turn on at all? or is it only blank for a few seconds? how do you not know what you flashed on it?
TRusselo said:
flash the captivate gingerbread bootloaders and captivate gingerbread stock KK4.
done.
you dont need to be on the stock you got the phone with. just an official ATT stock. KK4 gingerbread with kk4 gingerbread bootloaders is just fine.
for your second phone... any captivate / i9000 bootloader works for ICS.. what do you mean by it boots to blank screen? does it turn on at all? or is it only blank for a few seconds? how do you not know what you flashed on it?
Click to expand...
Click to collapse
They are talking about the GT-i9000 splash screen that has a black background
oh right the ATT boot is white... my rogers captivate is black..
once again... gingerbread bootloaders for kk4. work with everything,
Ok ! thx guys, will search!
go search yourself?? wow now that is the right attitude!
just for that...
here...
heimdall one click kk4 : http://forum.xda-developers.com/showthread.php?t=1386924
odin kk4 package : http://forum.xda-developers.com/showthread.php?t=1357848&highlight=stock+kk4
password : sampro.pl
for anyone that searches - http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3 this is what I used to go back to stock everything.
TRusselo said:
go search yourself?? wow now that is the right attitude!
just for that...
here...
heimdall one click kk4 : http://forum.xda-developers.com/showthread.php?t=1386924
odin kk4 package : http://forum.xda-developers.com/showthread.php?t=1357848&highlight=stock+kk4
password : sampro.pl
Click to expand...
Click to collapse
LOL!! I was ahead of you I guess
Speaking of search, is anyone's search function missing, or is it just me?
sthodupunuri said:
Speaking of search, is anyone's search function missing, or is it just me?
Click to expand...
Click to collapse
Yes, a bunch of stuff is screwed up. Admins are saying that it's being worked on. But it's been like 48 hours already
sthodupunuri said:
Speaking of search, is anyone's search function missing, or is it just me?
Click to expand...
Click to collapse
Search function is down right now just saw it I'm the announcements
how to flash stock flash screen...please help!!!
guys i flashed 'GOOGLE nexus s' splah screen on my galaxy s gt i9000....by flashing some pda file by odin.....now when i restart my phone 'GOOGLE' comes written instead of 'GT I9000' black screen....how can i go back to my gt i9000 splash screen..... please help....and sorry for my bad english
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