I installed speedmod kernel and perception 10.4 together in CWM. And i tried to restart the phone but it won't start. Screen doesn' t even light up. What do i do now ??? I have no warranty either.
If there is nothing that could be done is there a place to sell it for some bucks ??
You have a bricked bootloader which can be fixed through JTAG restoration. If you are interested just PM me. Same goes for anybody else in this situation...
Yes please. Let me know. I am dying to turn this on again. Thanks.
i am just wondering what exactly you did. by 10.4 do you mean the 2.3.3 perception beta that came out on the 10th of april or some other 10.4 version. if it was the perception 2 beta thats a 2.3.3 (or 2.3.4 cant remember) whereas speedmod kernal is for the original bootloaders and 2.1 and 2.2 you cant mix and match like that. and before you go and buy a jig from the guy above realize that your original 3 button combos arent the same as the ones from g12. try holding volume down the home soft key and power or volume up and power. if clock work (up and power) works then reflash g12 if download workd (android and shovel) plug it into computor and flash to stock using oden. if NONE of these things work buy the jug or buy a 301ohm resistor and build it yourself theres lots of tutorials
Perception 10.4 is the most stable version of FroYo perception.
Installing that after running GB without reinstalling the 2.1/2.2 bootloaders will brick. But if you never installed GB, or installed the 2.1/2.2 bootloaders first then your problem is elsewhere.
What were you running before you installed perception + speedmod? I'm guessing GB ROM of some flavor. If not, then it shouldn't be a bootloader issue.
Sent from my Captivate running GR-12
quarlow said:
Perception 10.4 is the most stable version of FroYo perception.
Installing that after running GB without reinstalling the 2.1/2.2 bootloaders will brick. But if you never installed GB, or installed the 2.1/2.2 bootloaders first then your problem is elsewhere.
What were you running before you installed perception + speedmod? I'm guessing GB ROM of some flavor. If not, then it shouldn't be a bootloader issue.
Sent from my Captivate running GR-12
Click to expand...
Click to collapse
Does perception have a froyo sbl.bin? Otherwise just flashing a froyo rom will not result in a hard brick at all. Gingerbread bootloaders are backward compatible as long they both match ... So if perception doesn't have any bootloaders at all and not just the froyo secondary bootloader it should be fine to flash from gingerbread. As long as you flash it from cwm 2.5 because cwm3 doesn't seem to want overwrite the kernel, but that won't even cause a hard brick just a bootloop, so you could odin a kernel after that and be golden.
the only thing that will cause a hard brick is either a plane old bad write/disconnection while the bootloaders are flashing. Which means, are you ready for a jaw dropper? odin one click is just as dangerous as flashing gingerbread!!!
Or now that there are new bootloaders the mixing if primary of froyo and secondary of gingerbread.
studacris said:
Does perception have a froyo sbl.bin? Otherwise just flashing a froyo rom will not result in a hard brick at all. Gingerbread bootloaders are backward compatible as long they both match ... So if perception doesn't have any bootloaders at all and not just the froyo secondary bootloader it should be fine to flash from gingerbread. As long as you flash it from cwm 2.5 because cwm3 doesn't seem to want overwrite the kernel, but that won't even cause a hard brick just a bootloop, so you could odin a kernel after that and be golden.
the only thing that will cause a hard brick is either a plane old bad write/disconnection while the bootloaders are flashing. Which means, are you ready for a jaw dropper? odin one click is just as dangerous as flashing gingerbread!!!
Or now that there are new bootloaders the mixing if primary of froyo and secondary of gingerbread.
Click to expand...
Click to collapse
DG has been known in the past to package sbl.bin's in his ROM's. I'd suspect a 2.1/2.2 sbl.bin was flashed with the 2.3 boot.bin. That will equal brick every time.
connexion2005 said:
You have a bricked bootloader which can be fixed through JTAG restoration. If you are interested just PM me. Same goes for anybody else in this situation...
Click to expand...
Click to collapse
He is the man. He fixed it for me. Unbricked it. You can trust him..
Related
I am running Cog 5B2. It has the captivate GB bootloaders. If i want to change to a i9000 GB rom say Apex do I need to change bootloaders or will the GB captivate ones work?
No you do not need to change bootloaders to go to any other gb rom. Plus I've read on here that the gb bootloaders are backwards compatible with froyo/eclair though I have not confirmed that yet myself.
So there really is no need to ever flash bootloaders again.
I wouldn't say never. But it is good to avoid flashing bootloaders if possible, if something goes wrong flashing bootloaders can result in an actual bricked phone.
On the other hand just flashing roms, kernels and modems sans bootloaders the worst you can likely do is get into soft brick situation or a bootloop which can be easily fixed.
Yup I flashed Serindipty7 right on top of cog 5.2 and then Mosaic V right on top of that no issues to report just make sure you wipe data factory reset before. I haven't flashed anything that has the talon kernel, but still no need to flash bootloaders
Sent from my phone on vacation
Keep it mind GB bootloaders are not backwards compatible with all of them. I know that CM7 does not work with GB bootloaders.
I prefer the I9000 gb bootloaders. They both work the same but The captivate ones have the same button combos which I've always thought were really stupid. The I9k's combos are just more intuitive and simplistic the way they should have always been if you ask me.
Vol up + power = recovery
Vol down + power = download
Nice
Clean
Simple
Well turns out going from Cog5b2 to OBSSESSION puts you in a bootloop. Reflashing Cog I guess for now.
vdubguy said:
Well turns out going from Cog5b2 to OBSSESSION puts you in a bootloop. Reflashing Cog I guess for now.
Click to expand...
Click to collapse
Try flashing to stick KF1 before flashing a new rom (there is a 1 click without bootloaders to minimize risk)
I haven't still figured out a reliable way to flash back to Stock Froyo on my 2 captivates which ended up being bricked. I was on Cezar's 897 GB bootloaders. Tried flashing back to Froyo KB1 from here but it failed using Odin3 1.3. I got a new phone, which now has stock KB2. Does anyone know how to flash stock Froyo reliably ?
prbassplayer said:
Try flashing to stick KF1 before flashing a new rom (there is a 1 click without bootloaders to minimize risk)
Click to expand...
Click to collapse
Really didn't know there was a 1 click without bootloaders. Time to hit up the search!
vdubguy said:
Well turns out going from Cog5b2 to OBSSESSION puts you in a bootloop. Reflashing Cog I guess for now.
Click to expand...
Click to collapse
I read someone have similar issue and I was also on cog5b2 and followed their instructions (which I'm going to paraphrase now) and worked perfectly. I'm now running Mosaic V with the KF1/i897 boot loaders...
OP on Mosaic V has link for xcal's 1.2 i9000 kernel.tar download that. Start at step 5 on that OP, use Odin 1.7 (linked as 'Files you will need' in the MV OP) to flash xcal's kernel, make sure to not auto reboot from Odin and when it's done flashing kernel, do a battery pull and then go to recovery mode, factory reset and then flash Obsession.
Sent from my GT-I9000 using XDA App
vdubguy said:
Really didn't know there was a 1 click without bootloaders. Time to hit up the search!
Click to expand...
Click to collapse
This is KF1 without Bootloaders
Madtowndave said:
I read someone have similar issue and I was also on cog5b2 and followed their instructions (which I'm going to paraphrase now) and worked perfectly. I'm now running Mosaic V with the KF1/i897 boot loaders...
OP on Mosaic V has link for xcal's 1.2 i9000 kernel.tar download that. Start at step 5 on that OP, use Odin 1.7 (linked as 'Files you will need' in the MV OP) to flash xcal's kernel, make sure to not auto reboot from Odin and when it's done flashing kernel, do a battery pull and then go to recovery mode, factory reset and then flash Obsession.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Cool Thanks everyone for the help. I may try Obsession again tomorrow. Gotta hit the sheets....and up early for work.
Srikar_NBK said:
I haven't still figured out a reliable way to flash back to Stock Froyo on my 2 captivates which ended up being bricked. I was on Cezar's 897 GB bootloaders. Tried flashing back to Froyo KB1 from here but it failed using Odin3 1.3. I got a new phone, which now has stock KB2. Does anyone know how to flash stock Froyo reliably ?
Click to expand...
Click to collapse
this is the recommended way to go back to stock that contains both main and secondary bootloaders http://forum.xda-developers.com/showthread.php?t=731989
also this one which contains no bootloaders http://forum.xda-developers.com/showthread.php?t=995143
CremeFraiche said:
this is the recommended way to go back to stock that contains both main and secondary bootloaders http://forum.xda-developers.com/showthread.php?t=731989
also this one which contains no bootloaders http://forum.xda-developers.com/showthread.php?t=995143
Click to expand...
Click to collapse
Yes, but aren't both of them methods to go back to Eclair and not Froyo ? My earlier Cappy got bricked bcoz I tried stocking back to Eclair, when it came with Froyo.
My question is how do you flash custom rom while on kf1 boots? Running cog 5 beta 2 with cwm4. Can I flash roms like I did before via cwm, even though I'm on cwm4, or should I flash a kernel with cwm 2 or cwm3 first, than flash rom thru that?. This question is for both froyo and GB/i9000 roms
Sent from my SAMSUNG-SGH-I897 using XDA App
Cdub3 said:
My question is how do you flash custom rom while on kf1 boots? Running cog 5 beta 2 with cwm4. Can I flash roms like I did before via cwm, even though I'm on cwm4, or should I flash a kernel with cwm 2 or cwm3 first, than flash rom thru that?. This question is for both froyo and GB/i9000 roms
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Well most roms have a Kernel that they recommend. Best I can figure if you want to flash a froyo rom go back down to stock eclair with one click (don't flash bootloaders) and flash rom of your choice. For GB just flash stock KF1 and flash gb rom? That's just me guessing though.
prbassplayer said:
Well most roms have a Kernel that they recommend. Best I can figure if you want to flash a froyo rom go back down to stock eclair with one click (don't flash bootloaders) and flash rom of your choice. For GB just flash stock KF1 and flash gb rom? That's just me guessing though.
Click to expand...
Click to collapse
Oneclick eclair contains bootloaders.
To simplify my question, are rom flashes compatible with cwm4, or do I need cwm2/or 3 to flash roms, whether froyo/GB?
Sent from my SAMSUNG-SGH-I897 using XDA App
Cdub3 said:
Oneclick eclair contains bootloaders.
To simplify my question, are rom flashes compatible with cwm4, or do I need cwm2/or 3 to flash roms, whether froyo/GB?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
JF6 is eclair is it not? If it is here is a JF6 odin with out bootloaders. If Jf6 is Froyo well my mistake. Still 2.2 stock would still work i think. Point is cmw version wont matter if you go back to stock and flash from there, and its usually a better idea to flash to stock anyways.
I'm new to the Captivate. Coming from Xperia x10, this phone is alien to me in regards to installing custom roms. I've been reading and apparently I need the 3 button fix because I can't get into Recovery mode without Rom manager. All the download links I've found are broken. Where can I get it? Is this even necessary? Has there been a more recent fix?
use adb and buy or make a usb jig for your phone to have incase. Its best to just avoid using the 3-button fix as it has broken a lot of cappys.
I will say flash a GB Rom for that u will need GB bootlaoders when u flash the GB Bootloaders it will fix ur 3 button combo, Gor flashing a GB rom you need the DL mode that can be achieved though ADB or a Jig.
But remember do not flash the 3 button fix over it.
xArtanis said:
I'm new to the Captivate. Coming from Xperia x10, this phone is alien to me in regards to installing custom roms. I've been reading and apparently I need the 3 button fix because I can't get into Recovery mode without Rom manager. All the download links I've found are broken. Where can I get it? Is this even necessary? Has there been a more recent fix?
Click to expand...
Click to collapse
Read well on each and every rom you want to use. IF you are inclined on flashing a GB rom with bootloaders I recommend this one. Run it as Admin put your phone in download mode. click start and you should be on 2.3.3 with bootloaders and 3button fix. Flashing bootloaders carries risk on hard bricking, and DO NOT flash the "3 button fix" if you are on GB bootloaders.
Just don't flash the 3 button lol its evol
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
xijar said:
Just don't flash the 3 button lol its evol
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
Click to expand...
Click to collapse
Its not evil its just outdated. It was used pre GB bootloaders. Its ment to fix the 3 button issue by JUST flashing a secondary bootloader. Now that we have GB bootloaders people think they need the "fix" and end up mismatching a GB primary bootloader and a eclair/froyo secondary bootloader creating a very expensive paper weight.
Meh can still jtag. Not too expensive and gets the phone going again. I understand why the fix breaks phones I just think its best to stay away from it since adb + jig work without it.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
xijar said:
Meh can still jtag. Not too expensive and gets the phone going again. I understand why the fix breaks phones I just think its best to stay away from it since adb + jig work without it.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
Click to expand...
Click to collapse
Ive read issues with ADB and CM7 based roms not working properly though. But I dislike AOSP roms on captivate, haven't had great experiences with them. But thats just personal observation. Although I quoted you my explanation was directed at OP sorry if that was confusing, just noticed it xD
xijar said:
Meh can still jtag. Not too expensive and gets the phone going again. I understand why the fix breaks phones I just think its best to stay away from it since adb + jig work without it.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
Click to expand...
Click to collapse
Adb doesn't work in all states such as a soft brick when you would need it.
And a jig only boots to download mode, meaning something that could have been fixed by a cwm flash is now a flash to stock using odin. And THEN the custom rom you could've flashed if your combos worked...
The aio toolbox has the 3 button fix, if you don't plan on flashing gingerbread any time soon then use that.
JUST DO NOT USE IT ONCE YOU'VE MADE THE JUMP TO GINGERBREAD. Unless first using odin one click jf6, that replaces both bootloaders with eclair ones, first.
Is risky applied this fix? If i have a jig, can i avoid try this fix rigth?
Darkuso said:
Is risky applied this fix? If i have a jig, can i avoid try this fix rigth?
Click to expand...
Click to collapse
Keel in mind you wont be able to reach recovery, jig only gets you in download mode. As ti risk flashy any type of bootloaders carries some risk for a hard brick. Id recommebd GB bootloaders and just forget about bootloaders. Just my 2 cents. But like always read read read =)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
studacris said:
Adb doesn't work in all states such as a soft brick when you would need it.
And a jig only boots to download mode, meaning something that could have been fixed by a cwm flash is now a flash to stock using odin. And THEN the custom rom you could've flashed if your combos worked...
The aio toolbox has the 3 button fix, if you don't plan on flashing gingerbread any time soon then use that.
JUST DO NOT USE IT ONCE YOU'VE MADE THE JUMP TO GINGERBREAD. Unless first using odin one click jf6, that replaces both bootloaders with eclair ones, first.
Click to expand...
Click to collapse
That's because THOSE gingerbread bootloaders are not for our phones. Tell whoever your ROM developer is to change his methods. He's causing bricks.
AdamOutler said:
That's because THOSE gingerbread bootloaders are not for our phones. Tell whoever your ROM developer is to change his methods. He's causing bricks.
Click to expand...
Click to collapse
So it won't brick with kf1 pbl mixed with a froyo (kb1) sbl?
studacris said:
So it won't brick with kf1 pbl mixed with a froyo (kb1) sbl?
Click to expand...
Click to collapse
Never mix bootloaders and never run bootloaders which are not for your phone. That's how you end up with a brick.
AdamOutler said:
Never mix bootloaders and never run bootloaders which are not for your phone. That's how you end up with a brick.
Click to expand...
Click to collapse
Good to know this, question: that is why u and ur team made andromeda3 in froyo? is safer stay with those bootloaders?
Andromeda is based off of the armani source code, which a gingerbread source has not been released for. So they haven't updated it.
But yes it is safer to never flash bootloaders as that is the only time you risk a brick. So if you never touch them you have a very tiny chance of ever bricking as it would be a hardware malfunction that would not allow you to flash out of a "soft brick" Such as a broken usb port...
Darkuso said:
Good to know this, question: that is why u and ur team made andromeda3 in froyo? is safer stay with those bootloaders?
Click to expand...
Click to collapse
Andromeda (in all its renditions up to and including 3) were based on Froyo because GB wasnt even a spec on the map for Galaxy S devices when it began life.
If we see some Armani source drop, we will work on a GB version, but we decided to stick true to the game and only work on armani source.
some of us have other projects we work on outside of a teamkomin build.
Pirateghost said:
Andromeda (in all its renditions up to and including 3) were based on Froyo because GB wasnt even a spec on the map for Galaxy S devices when it began life.
If we see some Armani source drop, we will work on a GB version, but we decided to stick true to the game and only work on armani source.
some of us have other projects we work on outside of a teamkomin build.
Click to expand...
Click to collapse
Right. Like my heimdall one-click project is designed to take the guesswork out of flashing for noobs. If you stick with one-clicks for your device, then you are using proper firmware which has been tested or at least pre-paired by someone for your device. It's not a Team project.
does this fix still exist? Every link I look on has a dead file link.
AIO toolbox has it. But I would recommend just flashingg I897 Gingerbread bootloaders.
I concur with prbassplayer. I know it's not the link you're asking about, but frankly, there have been a lot of hard bricks on here as a result of trying to use that 3-button fix. If you're planning on staying in the custom rom world, you'll probably be best off to just flash over to a set of Gingerbread bootloaders (depending on the rom you're going for), and not looking back, as the GB bootloaders will fix the 3-button issue as part of their installation.
my story is flash stock 2.1 rogers i896, then miui latest. Use to have the 3 button until I pooched the rom and had to reflash 2.1 and back to miui
I897 GB loaders work with MIUI. I am using them now. Also gives you the flexibility to flash the other GB roms later.
I'm looking to switch from Serendipity VII to Cyanogenmod 7.1 and I wanted to make sure I had the right steps laid out before I began. From what I've researched this is how it needs to go:
Go from Serendipty VII back to stock Ecliar/Froyo
Root
Begin CyanogenMod installation
My Questions are:
Do I need to take my phone back to stock before switching from Serendipity VII to Cyanogenmod 7.1?
If I do, how do I safely take my phone from Serendipity VII to stock?
I remember when Serendipity VII released a few people tried to take their phone back to stock and bricked because of bootloader issues. Any advice is appreciated. Thanks in advance.
First, what version of Android came on your phone? That's the version you should consider stock.
Second, any time you flash bootloaders, there's a chance for a hard brick. You can lower the chance by using a good cable (buy one if you need to, there only a couple of bucks on Amazon). Use a USB port on the back of the computer. Make sure your phone is on a stable surface. Make sure the battery door is on the phone. I like to use a fully charged laptop to flash bootloaders (no worries of a power failure). Last make sure you do not flash the 3 button fix. If you flash the fix while on GB bootloaders, you end up with a GB pbl, and a froyo sbl which means hard brick.
If you do hard brick, you will need JTAG service, or you will need to have UnbrickableMod applied.
My phone came with Eclair. So I'm assuming that's what I would need to go back to. I have a Macbook Pro so I'll be using Heimdall. I'll do some exploring now and find out if my GB bootloaders from Serendipity VII will work with CyanogenMod 7.1. Thanks for your help.
The I897 GB bootloaders will work with no problems. I believe S7 recommended I9000 GB bootloaders. Not sure how that will work on cm7. I know on MIUI it keeps you from being able to see anything on your extSD. Just fyi.
Also, it depends on your build number as to which stock you use. Before 1010, you can use jf6 no problem. After it would be recommended to use KB1 or KB2. If you use kb1 by ubershaximus with Heimdall, you can take out the bootloaders. With the kb2 by AdamOutler, i'm not sure you can as it's a1 click. Good luck and happy flashing.
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