Database Develop

[Q] am I screwed?

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

[Q] what is going on with my captivate?

so i have a captivate that ive had for a little while now. and of course ive flashed a few different gingerbread roms like usual.
anyways i wanted to try a froyo from so i used the odin 1 click stock tool to flash back to jf6,
that worked, but for some reason it wont allow me to master clear.
also my phone keeps switching between showing service, and a blue circle with a cross out sign....
(no internet access)
if i flash a rom over it, it starts acting like normal again
any idea whats wrong or whati can do?
thanks!

USB Debugging is need to do master clear. Did you turn on debugging?

speedy_11 said:
USB Debugging is need to do master clear. Did you turn on debugging?
Click to expand...
Click to collapse
yeah it was enabled.

The_Zodiac said:
so i have a captivate that ive had for a little while now. and of course ive flashed a few different gingerbread roms like usual.
anyways i wanted to try a froyo from so i used the odin 1 click stock tool to flash back to jf6,
that worked, but for some reason it wont allow me to master clear.
also my phone keeps switching between showing service, and a blue circle with a cross out sign....
(no internet access)
if i flash a rom over it, it starts acting like normal again
any idea whats wrong or whati can do?
thanks!
Click to expand...
Click to collapse
This happened on one of my old cappies that i got replaced. It was a 1008 build. It's an error in the efs folder. Did you make a backup of your efs folder before you started flashing?
If you didn't here's a method that worked for me that might get you back to normal. What i did was use Kies mini to upgrade to stock 2.2 then make sure the botton combos were working (vol up+dwn/plug usb to get to download mode, and vol up+vol dwn + power to get to recovery.) If those are working, now flash back to stock using Odin 1 click.
This wokred for me. hope it helps.
If you have your original efs folder, use Root Explorer to place the original folder ni place of the current one while on stock 2.1, then reboot to see if it worked.

What Gingerbread Roms did you "play" around with, I'm guessing you used the I9000 bootloaders also?

jack man said:
This happened on one of my old cappies that i got replaced. It was a 1008 build. It's an error in the efs folder. Did you make a backup of your efs folder before you started flashing?
If you didn't here's a method that worked for me that might get you back to normal. What i did was use Kies mini to upgrade to stock 2.2 then make sure the botton combos were working (vol up+dwn/plug usb to get to download mode, and vol up+vol dwn + power to get to recovery.) If those are working, now flash back to stock using Odin 1 click.
This wokred for me. hope it helps.
If you have your original efs folder, use Root Explorer to place the original folder ni place of the current one while on stock 2.1, then reboot to see if it worked.
Click to expand...
Click to collapse
im not sure what build because its a replacement from att and they didnt put the build number on the sticker.
i did backup the efs folder so i can try that.
melbourne408 said:
What Gingerbread Roms did you "play" around with, I'm guessing you used the I9000 bootloaders also?
Click to expand...
Click to collapse
a few apex, dvlevs, obsession. and yes i loaded gb bootloaders.
does jf6 flash you back to eclair bootloaders?

The_Zodiac said:
im not sure what build because its a replacement from att and they didnt put the build number on the sticker.
i did backup the efs folder so i can try that.
a few apex, dvlevs, obsession. and yes i loaded gb bootloaders.
does jf6 flash you back to eclair bootloaders?
Click to expand...
Click to collapse
Your going to want to flash back to eclair (imho) or froyo if you'd rather, but it will have to be done through odin without a 1 click method. If you know what I'm talking about all good. If not lemme know and I'll help ya to the links, cleaning the kitchen atm but its all good
Sent From My Swaggin 1.6 Son Of A Glitch

^^^^Wtf are you talking about? Odin one click to jf6 (eclair) includes both bootloaders... Thus replacing the I9k ones...
Op if everything works after you rom it and you have no plans to go to stock does it matter?
It could just be how the phone acts with the jf6 modem as its a signal problem...
And what exactly are you doing when trying to master clear and what happens?

studacris said:
^^^^Wtf are you talking about? Odin one click to jf6 (eclair) includes both bootloaders... Thus replacing the I9k ones...
Op if everything works after you rom it and you have no plans to go to stock does it matter?
It could just be how the phone acts with the jf6 modem as its a signal problem...
And what exactly are you doing when trying to master clear and what happens?
Click to expand...
Click to collapse
my concern if my phone stops working for whatever reason and i sen it in under warranty it will have to be stock att froyo.
(i get to that by flashing stock eclair then by using mini kies)

The_Zodiac said:
my concern if my phone stops working for whatever reason and i sen it in under warranty it will have to be stock att froyo.
(i get to that by flashing stock eclair then by using mini kies)
Click to expand...
Click to collapse
Couple things for the Master Clear
1. Make sure to shut down Odin then restart it without the phone connected
2. If that doesn't work restart your PC
3. If all else fails, root, install ROM Manager, get into CWM and do a factory reset
Like Studacris said, Odin to JF6 flashes the proper bootloaders, so you dont need to worry there. I've done it TONS of times
Edit** Are you using this Odin?
http://www.mediafire.com/?0w2y31maz8mdom4 If not, I would HIGHLY recommend using it

studacris said:
^^^^Wtf are you talking about? Odin one click to jf6 (eclair) includes both bootloaders... Thus replacing the I9k ones...
Op if everything works after you rom it and you have no plans to go to stock does it matter?
It could just be how the phone acts with the jf6 modem as its a signal problem...
And what exactly are you doing when trying to master clear and what happens?
Click to expand...
Click to collapse
Dam, bad correlation on my part. Didn't want anything going wrong with bootloaders, my self learned fault on being incoherent and half asleep, just didn't want any brick brick brickety brick bricks-as my dad laughs to me all the time. Thanks for the correction.
Sent From My Swaggin 1.6 Son Of A Glitch

I'll try to follow up on what Studa was going for.
The_Zodiac said:
my concern if my phone stops working for whatever reason and i sen it in under warranty it will have to be stock att froyo.
(i get to that by flashing stock eclair then by using mini kies)
Click to expand...
Click to collapse
Ok, but that would be a good thing, you can just use the signal problem as an added reason for sending it in. If you can flash stock and it boots, all is well. Anything else just goes in your favor of why you deserve a new one.
Plus, if the phone stops working to the point it does not boot they will have no real way of telling what was running before, nor will they waste the time to find out. It will get tossed into the re-write pile, and go thru the paces for becoming a referb.

You do realize that the phone has to be regularly on to do a master clear and not be in download mode right?

dsilvan55 said:
You do realize that the phone has to be regularly on to do a master clear and not be in download mode right?
Click to expand...
Click to collapse
yes i do...

Reflash the stock jf6 with no sim card
Sent from my GT-I9000 using XDA App

3 button fix?

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.

[Q] Flashing to Stock Question

I am wondering if it is possible to flash back to a stock rom without hooking up to a computer, is there a stock rom that can be installed right from CWM using a zip on the SD Card?

Only one i remember is a kb1 rom by ou812bkewl.

Thanks, I found that here: http://forum.xda-developers.com/showthread.php?t=963403. This isn't true stock as it was modified but hopefully it does enough to serve it's purpose.

Yeah, but all true"stock"packages are going to be for a flash utility (Odin/Heimdall for the captivate).

check out MOBILE ODIN

Mobile ODIN sounds super promising! That old rom originally suggested did not pan out, won't flash with the newer versions of CWM.

studacris said:
check out MOBILE ODIN
Click to expand...
Click to collapse
Dude, totally forgot about that. Is there an emoticon for "duh?"

Mobile Odin's saying my device is not supported.....I'm going to jump off a cliff lol. What I'm trying to do is flash any other ROM than what I have now. I flashed the RC1.0.1 Captivate ROM and now whenever I try to flash a different ROM it fails assertions. I'm guessing this is the same reason mobile ODIN is saying my device is not supported. I'm not going to be around a computer that I have set-up for ODIN for a few days, looks like I'm waiting. Thanks for trying to help me out folks

Mobile Odin requires you to be Rooted. And this flashes the firmware files, not cwm.zips files. (Not sure what u tried and why it said u weren't supported.)

I believe he's talking about the ICSSGS RC 1.0.1. From demonwave(which is rooted). If so, he's stuck if he doesn't have a computer. I had this on my Dev captivate and i couldn't flash from ics to cm7.
I think part of the not supported problem is the screen density, part is the build.prop. Just my $.02.

mrhaley30705 said:
I believe he's talking about the ICSSGS RC 1.0.1. From demonwave(which is rooted). If so, he's stuck if he doesn't have a computer. I had this on my Dev captivate and i couldn't flash from ics to cm7.
I think part of the not supported problem is the screen density, part is the build.prop. Just my $.02.
Click to expand...
Click to collapse
Ok, gotcha. So how did u get off of ICS ?? Flash stock kf1 ??

oooppss off day today...don't mind this misplaced post

4-2ndtwin said:
Ok, gotcha. So how did u get off of ICS ?? Flash stock kf1 ??
Click to expand...
Click to collapse
Yeah. Only way possible for me.

That's exactly my problem.
Sent from my I9000 using XDA App

[Q] ICS ROMS and Bootloaders

I hate to even have to ask this, and I can't search the forum for the answer that I know already exists because of my laptop being out of commission (which is where my actually question comes in), but I have the Froyo bootloader on my phone as far as I know, running MIUI 1.10.14 and was wondering if it'd be possible to flash an ICS ROM over this set-up.
Most threads I've browsed through mention ODIN One-Clicking the Gingerbread bootloader as necessary part of the process to flashing an ICS ROM, but like I mentioned, I can't search too deeply as I am, and was wondering if GB BLs are mandatory or just recommended.
Thanks in advance.
Sent from Premium Captivity

Need to have Gingerbread Bootloaders.

Absolutely no way around it?
Sent from Premium Captivity

Unfortunately, no. You have to use a computer to flash bootloaders.

Read the team Hacksungs forum. I believe some people are running froyo bootloaders, but I don't think it's recommended.
Sent from my SGH-I897 using xda premium

To clear up the confusion, the answer is yes and no. Yes I know, more confusing. It all depends on what ROM you are going to. Onecosmic's ICS REQUIRES GB bootloaders, while Teamhacksung's doesn't require them, but CAN be used with either. Also, some features in Glitch V14 require or benefit from GB bootloaders. But it may be a good idea to get GB's since that way you can use anything and never have to worry about switching again

^this 10char

Im not positive but i think you may be able to flash bootloaders from the mobile odin app but its probably easier and safer to flash bootloaders from a computer

Have to do it from computer... Mobile ODIN will not do that for you

Ahh, that may be how I just bricked my cappy then. It may have still had froyo bootloaders on it, and I flashed ICY Glitch from within CWM; and after that I rebooted and the phone wouldn't boot and I had to use my jig to get to download mode, but no computer will recognize it in download mode now do you think that going from froyo to icy glitch could have caused it not to be recognizeable now? I'm praying there is a way to reflash it somehow.

jnthnmc01 said:
Ahh, that may be how I just bricked my cappy then. It may have still had froyo bootloaders on it, and I flashed ICY Glitch from within CWM; and after that I rebooted and the phone wouldn't boot and I had to use my jig to get to download mode, but no computer will recognize it in download mode now do you think that going from froyo to icy glitch could have caused it not to be recognizeable now? I'm praying there is a way to reflash it somehow.
Click to expand...
Click to collapse
This post has nothing to do with bootloaders really. Your phone is fine. If you are on froyo bootloaders, the kernel bootscreen will be a black screen. Why can't you use recovery?
Sent from my CM9 ICS i897 Captivate

That is a great question, i dont know why button recoveries wont work. Only my jig gets me to download mode, but no device recognition.
Sent from my SGH-I897 using xda premium

jnthnmc01 said:
That is a great question, i dont know why button recoveries wont work. Only my jig gets me to download mode, but no device recognition.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Try another version of Odin and drivers, I believe that the Odin v1.3 is use for Froyo bl, and the latest version is use for GB bl because when i've got GB bl on my phone, i cannot use the Odin 1.3 anymore