Related
My Captivate is one of the unlucky phones that download mode is deactivated. I've searched the forums only to see bricks everywhere when people are rooting with this problem. Is there a safe way to flash or an adb fix that allows you to enable without the risk of bricking my phone? I purchased my phone used and cannot warranty my phone due to this so I don't have room for error. I'm tired of my stock ROM lag and bloatware. Its been interesting adjusting to this stock ROM after using Cyanogenmod for so long on my old phone. Ideas anyone?
Sent from my SAMSUNG-SGH-I897 using XDA App
Coldskiesfullofblue said:
My Captivate is one of the unlucky phones that download mode is deactivated. I've searched the forums only to see bricks everywhere when people are rooting with this problem. Is there a safe way to flash or an adb fix that allows you to enable without the risk of bricking my phone? I purchased my phone used and cannot warranty my phone due to this so I don't have room for error. I'm tired of my stock ROM lag and bloatware. Its been interesting adjusting to this stock ROM after using Cyanogenmod for so long on my old phone. Ideas anyone?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
You could flash this to get you back to stock with the 3 button fix.
http://forum.xda-developers.com/showthread.php?t=818439
then you can flash away.
xisruno said:
You could flash this to get you back to stock with the 3 button fix.
http://forum.xda-developers.com/showthread.php?t=818439
then you can flash away.
Click to expand...
Click to collapse
I am stock. My 3 button doesn't work. If I root and something messes up, I cannot get into download or recovery mode to fix it.
I can't even get into download mode via adb. I'm just at a loss.
Coldskiesfullofblue said:
I am stock. My 3 button doesn't work. If I root and something messes up, I cannot get into download or recovery mode to fix it.
I can't even get into download mode via adb. I'm just at a loss.
Click to expand...
Click to collapse
Right but if you flash the stock from that link, it includes the 3 button fix and you will be all set
chipsa964 said:
Right but if you flash the stock from that link, it includes the 3 button fix and you will be all set
Click to expand...
Click to collapse
I know I would be if I could get into download mode in order to do so. It is a requirement to flash this, that's my problem.
I hold the volume buttons and insert the USB and nothing happens but the phone charges and the battery is displayed on the screen.
I've loaded all of the software and tried to do this on two computers. One runs Windows 7 64bit and the other runs Windows Vista 32bit. I don't think it's a driver issue, I can adb into the phone but I am also denied permission when I try to use commands like adb reboot download on both computers.
I don't know what's going on but it's a lot more complicated than I've dealt with. I can't find anyone having the problems in the forums or anything.
This happened to me too when I went to stock using the odin that DG posted a while back. What's weird though is that I was able to get into dl mode no problem. I've flashed my phone just fine 3 times up until today when I went to flash the most recent cog. I used that odin to flash back to stock. At that point, I could no longer get into dl mode.. dunno. But, I had already rooted since going to stock. So, I just proceeded to flash. Weird. I'll follow this thread to see what the fix is.
Coldskiesfullofblue said:
I know I would be if I could get into download mode in order to do so. It is a requirement to flash this, that's my problem.
I hold the volume buttons and insert the USB and nothing happens but the phone charges and the battery is displayed on the screen.
I've loaded all of the software and tried to do this on two computers. One runs Windows 7 64bit and the other runs Windows Vista 32bit. I don't think it's a driver issue, I can adb into the phone but I am also denied permission when I try to use commands like adb reboot download on both computers.
I don't know what's going on but it's a lot more complicated than I've dealt with. I can't find anyone having the problems in the forums or anything.
Click to expand...
Click to collapse
I see now. Are you familiar with ADB? You can just use the adb reboot download command while your phone is plugged in and it will reboot into download mode. You have to have Android SDK installed and all your Samsung USB drivers installed as well.
Edit: Sorry, I missed the part where you couldn't do adb reboot download. Have you tried the one-click root?
chipsa964 said:
I see now. Are you familiar with ADB? You can just use the adb reboot download command while your phone is plugged in and it will reboot into download mode. You have to have Android SDK installed and all your Samsung USB drivers installed as well.
Edit: Sorry, I missed the part where you couldn't do adb reboot download. Have you tried the one-click root?
Click to expand...
Click to collapse
Shouldn't I be able to get into recovery/ download mode before I even think about altering the phone? A simple error could cause a problem I could easily fix in recovery. Without recovery my phone would be bricked. Should I worry about this?
Sent from my SAMSUNG-SGH-I897 using XDA App
Coldskiesfullofblue said:
Shouldn't I be able to get into recovery/ download mode before I even think about altering the phone? A simple error could cause a problem I could easily fix in recovery. Without recovery my phone would be bricked. Should I worry about this?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Well, I can relate because I don't have a 3-button phone either. What I did was first root my phone with the 1-click posted in the forum, that way, you can use adb and get into download mode. Then flash the Stock with 3-button fix, then flash whatever cog rom you want. I have used that method and everything has worked fine for me, but of course, follow those instructions at your own risk.
chipsa964 said:
Well, I can relate because I don't have a 3-button phone either. What I did was first root my phone with the 1-click posted in the forum, that way, you can use adb and get into download mode. Then flash the Stock with 3-button fix, then flash whatever cog rom you want. I have used that method and everything has worked fine for me, but of course, follow those instructions at your own risk.
Click to expand...
Click to collapse
Thanks, I didn't even think about needing SU to be able to get into download mode.
I used 1 click root, did the 3 button fix, and flashed clockwork with Rom Manager. I've got it going now. Thanks a lot.
Coldskiesfullofblue said:
Thanks, I didn't even think about needing SU to be able to get into download mode.
I used 1 click root, did the 3 button fix, and flashed clockwork with Rom Manager. I've got it going now. Thanks a lot.
Click to expand...
Click to collapse
Great!
10 char
So I put Andromeda on my phone a few weeks ago. It went fine, no problems, liked it. So I went to put it on my wife's phone. I was able to get it rooted. Into download mode, and Odin on it. But I couldn't get it into recovery. Vol up/dn/pwr just booted the phone normally. Vol up/dn does work to change the volume settings normally so it's not a bad button. So I thought, I had mine on stock 2.2 when I did everything. So I hooked hers up to Kies and put 2.2 on it. Rooted it. Now I cant' get the phone into download or recovery mode. Vol up/dn, plug in usb not working, it just goes into battery charge mode. We got our phones the same time so they're both same hardware rev. Any ideas?
TIA,
Scott
This should probably go in the q&a section. But did you try the three button fix. Search the forums for it.
Sent from my GT-I9000 using XDA App
slevy951 said:
So I put Andromeda on my phone a few weeks ago. It went fine, no problems, liked it. So I went to put it on my wife's phone. I was able to get it rooted. Into download mode, and Odin on it. But I couldn't get it into recovery. Vol up/dn/pwr just booted the phone normally. Vol up/dn does work to change the volume settings normally so it's not a bad button. So I thought, I had mine on stock 2.2 when I did everything. So I hooked hers up to Kies and put 2.2 on it. Rooted it. Now I cant' get the phone into download or recovery mode. Vol up/dn, plug in usb not working, it just goes into battery charge mode. We got our phones the same time so they're both same hardware rev. Any ideas?
TIA,
Scott
Click to expand...
Click to collapse
I donot know whats causing the problem (dont have the knowledge) but i can suggest buying a usb jig (costs only 8$ including shipping) which is pretty cheap and useful considering if you change roms frequently.
U just plug in the usb and the phone goes into download mode and you good to go.
If u wana buy just google mobile tech videos and buy it from their website (the guy john selling it is a rom reviwer on xda so its a safe site to buy) or on ebay. hope this helps
Sent from my GT-I9000 using XDA App
so its back to stock 2.2 ?
try using rom manager to boot into recovery.
note with 2.2 stock it has 3e recovery. to install cwm you must root and replace with 3e hacked recovery
use rom manager to boot into recovery. from cwm you can tell the phone to reboot into download.
or if you still have a custom rom, you use the advanced power menu (power button menu) to select download or recovery. no button tricks needed.
Trusselo said:
so its back to stock 2.2 ?
try using rom manager to boot into recovery.
note with 2.2 stock it has 3e recovery. to install cwm you must root and replace with 3e hacked recovery
use rom manager to boot into recovery. from cwm you can tell the phone to reboot into download.
or if you still have a custom rom, you use the advanced power menu (power button menu) to select download or recovery. no button tricks needed.
Click to expand...
Click to collapse
3e recovery can be a bit of a pain, it is easier to Odin one click to 2.1 with the 3 button fix and go on with that.
The other solution would be to go with Team Komin's Ursa Minor kernel. There's a video posted on the forum (and youtube) by AdamOutler (I think that's his name) on how to do it - very clear and easy to follow.
@ Trusselo, I don't mean to go against your suggestion. I went through the 3e recovery myself and it can be a pain for a newbie so I'm giving him/them a second opinion/suggestion
the 3e instructions are written like crap. i asked the OP to change it but no.,...
its actually super easy if you have root explorer. (google *cough cough*)
use root explorer to mount RW then drop the file over the old one.
done
@ bwolf_56 Oh and no offece to you but he cant get into download mode to flash the Ursa kernel from odin... so...
Trusselo said:
the 3e instructions are written like crap.
its actually super easy.
use root explorer to mount RW then drop the file over the old one.
done
Click to expand...
Click to collapse
Yup, they're. I had to go through the replies to find the actual good way to do it and even then it wasn't so clear.
Once you know how root explorer works, then go ahead and use the 3e recovery but I wouldn't suggest that to some1 new to all of this I mean, you don't wanna replace the wrong file either (or even worst, delete system files).
Either way, It's up to you OP - both solution works great. I hope we helped
EDIT: lolol - I guess w/o dl mode, my way doesn't work so well You can try one of the 3 ways to get in dl mode, the one that works best for me is:
1. Turn off phone, remove battery, sim card
2. hold down both volume button
3. plug the usb in (while holding both volume still)
4. A nice triangle with a Android holding a shovel should show up
If that doesn't work. My apologize and go ahead with the 3e recovery that Trusselo suggested. You can pm me for clear instruction (and probably Trusselo as well)
Thanks all for suggestions....
so its back to stock 2.2 ?
Yes. And I believe I got it rooted with Superoneclick because it has superuser on it.
it is easier to Odin one click to 2.1 with the 3 button fix and go on with that
Exactly what I'm trying to do. But can't get into download mode or 3-button recovery mode. Neither are working. I didn't try the abd server method. Looked a bit scary, but may try it this eve.
use root explorer to mount RW then drop the file over the old one
Forgive me. Root explorer from market, right? 'mount RW' ? Drop what file over what old file?
use rom manager to boot into recovery. from cwm you can tell the phone to reboot into download.
So mount the SD and copy cwm to it and rename to update.zip. Get Rom manager from market and that will get me to cwm to get to download mode to use Odin to go back to 2.1. Then root again and install rom manager again to get into recovery to load the Andromeda? Is that close?
odin one click isnt 3 button fix
3 button fix is a flash you use with the NON one click odin
root explorer is from the market... (can also be *found* on google [for testing purposes])
3e recovery fix is a file you must replace. xda search it!
rom manager will download and copy the update.zip for you! so you dont need to do it frist. its the first button in the app! Rom manager also has a button. "boot into recovery" use it to boot into recovery...
so flash to 2.1 with 3button fix (regular odin) 2.1 no 3e recovery forget that.
root
install rom manager to get cwm
cwm flash your new rom
delete rom manager.
sounds like you need to do more searching and reading...
Trusselo said:
odin one click isnt 3 button fix
3 button fix is a flash you use with the NON one click odin
root explorer is from the market... (can also be *found* on google [for testing purposes])
3e recovery fix is a file you must replace. xda search it!
rom manager will download and copy the update.zip for you! so you dont need to do it frist. its the first button in the app! Rom manager also has a button. "boot into recovery" use it to boot into recovery...
so flash to 2.1 with 3button fix (regular odin) 2.1 no 3e recovery forget that.
root
install rom manager to get cwm
cwm flash your new rom
delete rom manager.
sounds like you need to do more searching and reading...
Click to expand...
Click to collapse
Little question here, why would you delete ROM manager after?
@ OP - Please read some more before trying what has been suggested here. Trusselo gave you a good rundown which isn't too hard to do (there are also vid on it). A little reading could save your android, that coming from a guy that is usually hasty to act (notice how I bricked my 1st cappy )
most custom roms have CWM built into the kernel. rom manager and the update.zip with cwm are no longer needed with one of the cwm kernels.
and custom roms usually have the advanced power menu. boot to recovery/download easy peisy
rom manager only confuses people if you have both. took me a couple weeks to learn that..
bricked my first one too, kinda, (coulda fixed it) but couldn't wait and had it only days, easy exchange with in-store dummies.. lol
So I looked at Rom Manager on my phone.
Since the wife's on stock 2.2 and rooted. Seems that I can just d/l Rom Manager on her's. Copy the new rom to the SD. And use Rom Manager to flash it.
Can it be that simple?
And yes, I've been doing alot of reading. But, some of you guys talk a different language.....
Thanks again.
Scott
For future reference, this is not Dev-related and should have been posted in the related sticky in Q&A.
Miami_Son said:
For future reference, this is not Dev-related and should have been posted in the related sticky in Q&A.
Click to expand...
Click to collapse
Ya, wasn't real sure where to put it. Apologies. If you want to move it.....
Scott
Moved to proper forum.
slevy951 said:
So I looked at Rom Manager on my phone.
Since the wife's on stock 2.2 and rooted. Seems that I can just d/l Rom Manager on her's. Copy the new rom to the SD. And use Rom Manager to flash it.
Can it be that simple?
And yes, I've been doing alot of reading. But, some of you guys talk a different language.....
Thanks again.
Scott
Click to expand...
Click to collapse
No, it's not that simple, on 2.2 with the 3e recovery you will get a signing error when trying to flash and it won't work. Follow the suggestions and just use odin with the 3 button fix to get to 2.1
To get into download did you try removing battery from captivate, start Odin, plug USB cable to PC and captivate, hold both volume keys, and reinstall battery? On Stock that's the only way I can get into download. There is a thread on here with more detail but that's how I do it.
Sent from my SAMSUNG-SGH-I897 using XDA App
talbtimber said:
To get into download did you try removing battery from captivate, start Odin, plug USB cable to PC and captivate, hold both volume keys, and reinstall battery? On Stock that's the only way I can get into download. There is a thread on here with more detail but that's how I do it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yep, tried that one.
Spent a couple hours on this last night. I isntalled Rom Manager. That will get the phone into recovery. But, since it's 3e, doesn't do me any good. Signature errors. No matter what I do, can't get the phone into download mode. Last night I even tried with adb. The phone just reboots normally with the adb reboot download command.
I know your gonna say there is the 3e fix, keep reading. I found it. But, really didn't understand it. And I don't want to brick the phone. I think the wife is going to be staying on stock 2.2 at this point. I don't know what else to do.
Thanks to all.
Scott
Try and make or buy a jig?
Buiding a JIG is quite simple and cheap, you should try it.
Also, you can pm me for 3e recovery. I'll give you a nice rundown - It's quite easy, just not well explained on the thread
Hi there,
I noticed I can't get in download mode anymore. Whatever I try it won't show the yellow triangular download sign. It just boots into cyanogen.
I have tried the 3 button trick but recovery nor download works. That's when I had the idea to apply the 3-button fix. adb reboot recovery brings me in the cwm recovery mode. adb reboot download just reboots the phone. I even tried the 300k ohm jig which always seemed to work as a failsafe. That also just boots the phone into cm.
I have checked with my brother who also runs CM nightly 101 and for him the download mode works fine so it is my phone, not CM.
The phone works fine now, is rooted too so I wondered if there's any way to fix this by rewriting the bootloaders. I want to have this fixed as a failsafe is flashing ever fails or if one of the nightlies gets corrupted.
Is there anyone who can confirm the download mode is in the primary bootloader (boot.bin from a stock rom) and is it safe to just flash_image that to the boot partition or will that be a guarantee to brick. The idea is that I still have root console access so I have to fix it from there.
Any help is appreciated.
Christiaan
Galaxy S
CyanogenMod 7 Nightly #101
Their is a chance that whenever u tried to go into download mode your phone was connected into charging and phone doesn't go into download mode when charging , please reply and tell Me that did I helped!
Sent from my GT-I9000 using XDA Premium App
BHuvan goyal said:
Their is a chance that whenever u tried to go into download mode your phone was connected into charging and phone doesn't go into download mode when charging , please reply and tell Me that did I helped!
Click to expand...
Click to collapse
Thanks for the quick reply.
Tried the tricks with and without pc-usb/charger and it made no difference. The 300k ohm jig trick can't be done with power or computer connected since you have to use the usb connection on the phone for it. It usually was my ever working failsafe.
I also tried the quickboot app without any luck. It seems it is responding to the download command but the code isn't there anymore.
Hey try going into download mode by touch controls although I haven't ever used cyanogen but i assume as every custom rom has this feature cyanogen must also have this! The download mode option in quick network options when u press the power button for 2 seconds ! Although it isn't safe but you cab try this and then if it goes into download mode then their must a way to go into download mode manually!
Sent from my GT-I9000 using XDA Premium App
BHuvan goyal said:
Hey try going into download mode by touch controls although I haven't ever used cyanogen but i assume as every custom rom has this feature cyanogen must also have this! The download mode option in quick network options when u press the power button for 2 seconds ! Although it isn't safe but you cab try this and then if it goes into download mode then their must a way to go into download mode manually!
Click to expand...
Click to collapse
Holding the power button for two seconds indeed brings up the profile/reboot/shutdown options. Selecting reboot only gives two additional options, reboot and recovery which do as they say. I can boot cwm recovery but from there I can't go into download mode either.
Try downloading terminal emulator and then reboot download or ADB reboot download
Nitro_123 said:
Try downloading terminal emulator and then reboot download or ADB reboot download
Click to expand...
Click to collapse
Tried it from the terminal with reboot download. Also tried adb reboot download long before that. It just reboots and starts. I have the feeling the piece of bootblock that's holding the download mode isn't there anymore.
There is an option in recovery to boot into download mode, Have you tried that ?
It sounds to me like that part of the bootloader is corrupt / missing.
Does the phone still work normally ? can you still continue to use it daily without the download mode option ?
azzledazzle said:
There is an option in recovery to boot into download mode, Have you tried that ?
It sounds to me like that part of the bootloader is corrupt / missing.
Does the phone still work normally ? can you still continue to use it daily without the download mode option ?
Click to expand...
Click to collapse
The phone works fine otherwise. I just want to fix this before it stops working fine and I need the download mode.
Recovery boots into CWM-based Recovery v4.0.1.5 which I got with CM7 with no option to return to the stock recovery or download mode as far as I can see. Also zipped updates from sd-card install fine from CWM recovery mode. If I just knew where to find a cwm ready zipped bootloader that will fix this.
cvdveer said:
The phone works fine otherwise. I just want to fix this before it stops working fine and I need the download mode.
Recovery boots into CWM-based Recovery v4.0.1.5 which I got with CM7 with no option to return to the stock recovery or download mode as far as I can see. Also zipped updates from sd-card install fine from CWM recovery mode. If I just knew where to find a cwm ready zipped bootloader that will fix this.
Click to expand...
Click to collapse
Thats a good idea, I think that should be made, Would save a lot of hassle...
In my recovery under 'advanced features' the option is there to reboot into android or reboot into download..
In order to go from CM7 - Stock, do you need re-partition with all 3 files ? or can you flash it through recovery ?
If so, flash it to stock and sell it to someone who has no idea about Custom ROMs / Hacking. (like me 12 months ago )
EDIT: is this issue not kernel related by any chance ?
azzledazzle said:
Thats a good idea, I think that should be made, Would save a lot of hassle...
In my recovery under 'advanced features' the option is there to reboot into android or reboot into download..
In order to go from CM7 - Stock, do you need re-partition with all 3 files ? or can you flash it through recovery ?
If so, flash it to stock and sell it to someone who has no idea about Custom ROMs / Hacking. (like me 12 months ago )
EDIT: is this issue not kernel related by any chance ?
Click to expand...
Click to collapse
Well I have no clue to make any package and I don't dare to flash_image some random boot.bin.
My recovery -> advanced only has reboot recovery which brings it back into recovery.
I'm afraid bringing it back to stock also needs odin/heimdall, that brings me back to the initial problem.
Selling it gives me the money for half a new phone. As long as its working fine I'd like to stick with it. My worst case scenario so far is that I'm stuck with CM7 nightly #101 for the coming 1.5 year which is annoying but far better than the slow stock samsung hands out.
The issue can't be directly kernel or CM7 related. My brother has CM7 #101 running and download mode works fine with him. (And no I can't secretly swap phones ) He doesn't know how to work with odin so I arranged everything for him. Exactly the same steps as I did my own phone. Perhaps a glitch in flashing or something.
cvdveer said:
Well I have no clue to make any package and I don't dare to flash_image some random boot.bin.
My recovery -> advanced only has reboot recovery which brings it back into recovery.
I'm afraid bringing it back to stock also needs odin/heimdall, that brings me back to the initial problem.
Selling it gives me the money for half a new phone. As long as its working fine I'd like to stick with it. My worst case scenario so far is that I'm stuck with CM7 nightly #101 for the coming 1.5 year which is annoying but far better than the slow stock samsung hands out.
The issue can't be directly kernel or CM7 related. My brother has CM7 #101 running and download mode works fine with him. (And no I can't secretly swap phones ) He doesn't know how to work with odin so I arranged everything for him. Exactly the same steps as I did my own phone. Perhaps a glitch in flashing or something.
Click to expand...
Click to collapse
Hmmm... tricky one to fix..
I have no more ideas i think flashing bootloaders through recovery would work like you said, But unless its a tried and tested method i wouldnt recommend it at all.
Have you posted this issue in the CM thread ? perhaps you could PM one of the Devs for assistance, or whether the whole 'flashing bootloader in recovery' idea would work at all.
You have nothing to lose by asking them.
Hope you get a solution... But until them im out of ideas.
Keep us updated if you get a fix.
Good luck man !!
EDIT: one more idea, Sounds risky but.... What if you made a nandroid backup on your brothers phone and restore it on yours ?? Thats if nandroid does back up bootloaders im not sure
azzledazzle said:
Hmmm... tricky one to fix..
I have no more ideas i think flashing bootloaders through recovery would work like you said, But unless its a tried and tested method i wouldnt recommend it at all.
Have you posted this issue in the CM thread ? perhaps you could PM one of the Devs for assistance, or whether the whole 'flashing bootloader in recovery' idea would work at all.
You have nothing to lose by asking them.
Hope you get a solution... But until them im out of ideas.
Keep us updated if you get a fix.
Good luck man !!
EDIT: one more idea, Sounds risky but.... What if you made a nandroid backup on your brothers phone and restore it on yours ?? Thats if nandroid does back up bootloaders im not sure
Click to expand...
Click to collapse
Thanks for thinking with me. I'll give the nandroid solution a go if there are no other replies within a reasonable time.
I'll post the same question in the CM forum but contacting the CM devs could be hard. They don't give any official support to nightlies and I can't say I'm convinced it has anything to do with CM at all. Though they do have the knowledge to answer the question or build a package to repair it. But you're right there's nothing to lose in asking.
Ofcourse I searched the forum before posting and found out I seem to be the only one ever with this problem. The solution could be as rare so I'll keep you posted if I make any progress beside here. That's what the whole idea behind this forum is for right?
True man !!
And if you get a solution or a dev to make a flashable bootloader. It could help other people in future
Good luck. Keep us posted
http://forum.xda-developers.com/showthread.php?t=1236273
Nitro_123 said:
http://forum.xda-developers.com/showthread.php?t=1236273
Click to expand...
Click to collapse
Interesting but that project still needs a bricked i9000 to tear apart. I don't have a captivate. Well if it ever becomes really bricked I'll consider donating mine.
And I'm okay with handling computers (yes I consider the phone a small computer about 400 times faster than my first pc) but when actual soldering is involved I give up.
fixable?
i have a samsung here the S GT I 9000 and i tryed to use odin on it and now this pops up every time i try to up load an os
--installing package...
finding package...
opening package...
verifying update package...
installing update...
successfully install update...
--copy media files...
successfully copied media files..
formatting /data...
E:format_volume: rfs format failed on / dev/block/mmcblk0p2
formatting /dbdata...
formatting /cache..
deleting meta data
data wipe fail.
-- appling multi-csc...
installing multi-csc..
cant access to '/system/csc/bmc/system/' . sucessfully applied multi-CSC
Help!
Hi! If it still doesn't work, try downloading ROM Manager from the market and install the latest CWM. It sounds like your bootloader got modified/locked.
Erahgon said:
Hi! If it still doesn't work, try downloading ROM Manager from the market and install the latest CWM. It sounds like your bootloader got modified/locked.
Click to expand...
Click to collapse
Errr talking to me or adonai? Sounds like two seperate problems for two seperate topics.
cvdveer said:
Interesting but that project still needs a bricked i9000 to tear apart. I don't have a captivate. Well if it ever becomes really bricked I'll consider donating mine.
And I'm okay with handling computers (yes I consider the phone a small computer about 400 times faster than my first pc) but when actual soldering is involved I give up.
Click to expand...
Click to collapse
I REALLY liked your answer
BTW , same here
Hello fellow captivate users, I need some help here!
I've just brought a 'bricked' at&t captivate off of trademe here in NZ (it's like ebay) and I'm having a little trouble recovering it.
With the help of a homemade JIG I was able to force DOWNLOAD mode, and have tried using ODIN to flash various all-in-one firmwares. However, it seems no matter which I use the phone always ends up in some sort of bootloop, either with just the at&t logo looping, the at&t plus either a samsung s i897 or i9000 screen looping or just the samsung screen looping (depending on one-click used).
So far I've tried these oneclicks-
I897UCJF6 with bootloaders
I897UCKK4 with bootloaders
Plus various other packages that use odin to flash the different parts of the filesystem etc...
I've also used different ports and cables on the computer (although download mode and connection to pc do not SEEM to be a problem)
I'm sure I'm missing something here, but I'm also sure I'm following each firmwares instructions to the 'T'!
I've flashed other android devices in the past with no issues, is there something the samsung requires that I'm missing or messing up? (It's probably the latter )
Any help would be greatly appreciated
Cheers XDA Gurus
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with. Apex even has a Heimdall package that will put cwm on your computer.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
odin likes to lock up. if odin locks up durring bootloaders... well its the only REAL way to permanently brick a cappy... until you unbrick it..
do you need the jig? is the button combo not working? both volume + plug in usb to PC
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/showthread.php?t=1386924
heimdall is like odin but open source (more features and more stable), but it uses different drivers that it will install itself, but that usb port will be your heimdall port, all others will work with odin, unless you install the heimdall drivers on other ports too.
or...
try flashing a custom rom using the guide in my sig. it will quickly give you a custom kernel with cwm recovery, you can mount usb to pc from recovery menu, then transfer a rom to flash.
give that a shot...
Wow, quick replies guys, thanks.
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with
Click to expand...
Click to collapse
I should have mentioned - I did try one Heimdall oneclick, but had same bootloop result.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
Click to expand...
Click to collapse
I figured that, just wanted to make sure the bootloaders weren't at fault - I'll make sure I use the non-bootloader oneclicks from now on.
do you need the jig? is the button combo not working? both volume + plug in usb to PC
Click to expand...
Click to collapse
Originally the jig was needed (the phone arrived bootlooping at&t with no button combos working). But since my original stock flash (I897UCJF6) this hasn't been needed.
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
Click to expand...
Click to collapse
Cool, so cable/ports are ok
Code:
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/show....php?t=1386924
Thanks, I'll give this a shot first. If no go I'll try using the cwm method from your sig. How does the sd need to be formated/partitioned for captivate - guess I'll just use a single fat32 parition to start.
To sum up, now that I've got stock GB bootloaders, I'll quit using oneclicks with bl's included. USB cables and ports are fine. I'll try the KK4 heimdall package that was linked, if still no go I'll flash a custom rom and use clockwork to install changes from then on.
Thanks again
I must be messing up - having trouble getting into recovery.
Here's what I did;
The links here: http://forum.xda-developers.com/showthread.php?t=1386924 are dead, so I went straight to method 2.
Downloaded speedmod kernel from here: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Used odin to flash (kernel selected under pda), this seems to have worked as I now have the samsung i897 screen show up after the at&t. BUT when I try to enter recovery via three button method I get nothing.
How long should I hold the 3 buttons down for? (How many bootloops?)
Should I let go of them at th at&t splash, the samsung s i897 splash or at the blank screen?
All of this was done after my last odin oneclick attempt (which was a KK4, re-part, bootloaders included flash from here on xda)
**edit
I've also tried using the heimdall package (i897-Speedmod-K13E-GBbootloaders-One-Click.jar) to install the kernel with no luck getting into recovery.
For button combo to get into recovery--release when u see 1st att screen.
Or
Have u tried Adb (Android Debug Bridge) to get into recovery ??
Sent by XDA Premium App
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Yep, no adb on bootloop. Still no joy getting into recovery - it's a stubborn wee device! Gona try some different kernels today.
Am I right that there's no kernels available that will boot straight to cwm without button combos? (I'm thinking my power button may be iffy coz I have no problems getting into download mode)
Sent from my FUSIONideos using XDA
TRusselo said:
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Click to expand...
Click to collapse
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Its pretty handy, you can push a framework-res you are messing with without having to make a zip, and if you broke it and it loops, you can push the original back, reboot and you're back in business
*removed double post
studacris said:
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Click to expand...
Click to collapse
How exactly? adb doesn't see the captivate because it's only connected for a second before it reboots,adb just tells me device not found or something to that affect.
You have to hit enter at the Right moment, it takes practice
Lol, lucky I've got plenty of patience then!
Strangely if I 1-click back to stock eclair (maybe froyo not in front of PC at mo, and I know I shouldn't be messing with bootloaders but ehhh) I am able to get into what I assume is samsungs recovery mode, but I have to hold button combo for maybe 3 or 4 bootloops. Sticky button(s) maybe?
Am I able to use adb from there to get an update.zip to internal sdcard?
How come if the Odin oneclick seems to work I still end up in bootloops? Something not doing its job right? Partitions not working or kernel or system or bootloaders? Looking through adb shell the system looks intact-but still looping away!
Also am I right in assuming that because it gets to download mode it is eventually fixable?
Sent from my FUSIONideos using XDA
Just an update - from the stock eclair recovery I'm unable to push to the internal SD, get a permission error. Unable to remount that either, comes back with a fairly generic remount not allowed error.
Looking through the forums most people seem to have trouble getting into download mode rather than recovery - doesn't seem any cwm kernel will let me into recovery. Phone is model 1007 if that helps.
Is it possible the internal SD is stuffed? Can't see why all oneclicks end in loop - shouldn't they be overwriting the entire internals?
Gona format a microSD from my tablet and see if that will help, should I leave it fat or use Ubuntu to ext4 it for stock Samsung?
Sent from my FUSIONideos using XDA
If a Internal or External SD card is fried, then no amount of formatting and flashing will help it.
Is there any way to tell if the internal is cooked though? Odin and heimdall both seem happy to flash to the phone, but I've yet to find a package that doesn't end with a bootloop.
There must be some hardware issue though, seems unusual that aside from stock eclair I'm unable to enter recovery. According to the guy I got it from, it simply died while he attempted to update firmware, but the fact that I'm able to flash from download mode would suggest that's not the issue.
I guess there's no way to tell if hardware is cooked other than to send to samsung, is it common for people to get stuck with bootloops from stock flashes? Should I give up and see what samsung would charge to fix (if they will/can) or keep attempting different oneclicks (without bootloaders of course )
How about a non one click?
I've heard some peoples phones bootloop with one clicks, but work fine with .tar packages and the full Odin flashing utility.
Worth a shot. Got to wait a few days for my net to reset though, hit my limit for the month and it's painfully slooow - damn NZ's overpriced adsl!
Sent from my FUSIONideos using XDA
Still not working unfortunately. Using packages with odin3 gets me the same results, bootloops and no access to recovery. I also downloaded the aio captivate package and used the heimdall that came with that to flash stock eclair, which ended with a kernel panic screen - though am able to access recovery. Recovery doesn't see my fat32 microsd though so unable to flash from there.
I don't know my adb shell commands well enough to try and mount or format internal sd and I get permission denied when trying to push update.zip to internal sd via adb.
Unless anyone has any other ideas I'm stumped for now.
When my internal sd got messed up from cognadaian bacon (ooooold dg ROM) i reformated it with my computer and it then let me Load another rom on it... don't remeber if fat 32 or not ....mabey someone else might know
Edit: mabey designgears remembers what fix it when cognadian bacon porked it
Sent from my SGH-I897 using xda premium
I have searched for the last 24 hours on this site for any mention of this problem and found nothing. I apologize if it has been covered elsewhere and would appreciate a link if I should be there instead of here. I am new to this forum.
I have an AT&T Captivate that I bought used for my wife. It was rooted and running some version of non-official Gingerbread when I got it (so it had been messed around with).
I have never been able to get into RECOVERY mode having tried every conceivable button and timing sequence at least 1 million times (3-button neutered?). I also have Android SDK installed on my PC and can send the "adb reboot recovery" command but it locks up at the AT&T screen and won't go any further so the PC is talking to the phone but the phone refuses to obey. Yes I have tried different USB ports and cables, un/reinstalling drivers, etc. The weird thing is that I can get into DL mode easily with the batt out, vol+/-,USB cable trick.
I originally took the phone all the way back to a stock Froyo ROM via Odin which appeared to work fine (but still no recovery mode) and then flashed to GB 2.3.5 with Kernel 2.6.35.7-I897UCKK4-CL614489 via "kh3_heimdall_cwm-One-Click_GB_2_3_5.jar"
Phone works OK now but I still can't get into RECOVERY mode. Unless I am mistaken, there are no ROMS available later than GB that can be flashed via Odin- all of the later ROMs need to be installed from recovery mode. The point of all this is that I want to try upgrading to ICS or JB but can't figure out how to do it without a way to get into recovery mode.
So the question is: How can I get recovery mode to work?
And: How can I update the ROM with no way to get into Recovery mode? Is it even possible?
Returning the phone is obviously out of the question as it is "obsolete" and I am not the original owner.
Thank you for any helpful insights.
captivated hippo said:
I have searched for the last 24 hours on this site for any mention of this problem and found nothing. I apologize if it has been covered elsewhere and would appreciate a link if I should be there instead of here. I am new to this forum.
I have an AT&T Captivate that I bought used for my wife. It was rooted and running some version of non-official Gingerbread when I got it (so it had been messed around with).
I have never been able to get into RECOVERY mode having tried every conceivable button and timing sequence at least 1 million times (3-button neutered?). I also have Android SDK installed on my PC and can send the "adb reboot recovery" command but it locks up at the AT&T screen and won't go any further so the PC is talking to the phone but the phone refuses to obey. Yes I have tried different USB ports and cables, un/reinstalling drivers, etc. The weird thing is that I can get into DL mode easily with the batt out, vol+/-,USB cable trick.
I originally took the phone all the way back to a stock Froyo ROM via Odin which appeared to work fine (but still no recovery mode) and then flashed to GB 2.3.5 with Kernel 2.6.35.7-I897UCKK4-CL614489 via "kh3_heimdall_cwm-One-Click_GB_2_3_5.jar"
Phone works OK now but I still can't get into RECOVERY mode. Unless I am mistaken, there are no ROMS available later than GB that can be flashed via Odin- all of the later ROMs need to be installed from recovery mode. The point of all this is that I want to try upgrading to ICS or JB but can't figure out how to do it without a way to get into recovery mode.
So the question is: How can I get recovery mode to work?
And: How can I update the ROM with no way to get into Recovery mode? Is it even possible?
Returning the phone is obviously out of the question as it is "obsolete" and I am not the original owner.
Thank you for any helpful insights.
Click to expand...
Click to collapse
Since you have no problems getting into download mode I suggest you start by going to this link... http://forum.xda-developers.com/showthread.php?t=1300843 Go to the third post and download the Odin one click of KK4 with bootloaders.
After you do the one-click back to stock go to this link... http://forum.xda-developers.com/showthread.php?t=1294477&highlight=corn+kernel and get the odin flashable version of 7.06 or 7.0A and if you don't already have Odin you'll of course need that too. Get yourself back into download mode and flash that kernel and it should give you back your recovery via the 3 button combo.
Worked! (eventually...sort of...)
m1batt1 said:
Since you have no problems getting into download mode I suggest you start by going to this link... http://forum.xda-developers.com/showthread.php?t=1300843 Go to the third post and download the Odin one click of KK4 with bootloaders.
After you do the one-click back to stock go to this link... http://forum.xda-developers.com/showthread.php?t=1294477&highlight=corn+kernel and get the odin flashable version of 7.06 or 7.0A and if you don't already have Odin you'll of course need that too. Get yourself back into download mode and flash that kernel and it should give you back your recovery via the 3 button combo.
Click to expand...
Click to collapse
m1batt1,
Thank you sooo much! It ALMOST worked!
- DL'ed Odin 1-click KK4 w/BL's as suggested, ran it, it failed and semi-bricked my phone... (phone--/!\---comp). Doh!
-Figured you were on the right track so DL'ed "I897UCKK4 Odin One Click - Stock, CONTAINS Bootloaders, Re-partition, Full Wipe" from 4-2ndtwin's post further down the same thread.
-after much anxiety and messing about to get it to connect, it successfully flashed!
-For the FIRST TIME EVER, I can get into recovery mode!
-followed up with corn kernel 7.06 as suggested with no problems
-now that the phone works as advertised, time for JB!
The funny thing is, I went back to stock ROMs several times and recovery never worked until now... go figure...
^
...then it had to be that KK4 one click in that 3rd post that fixed the prob.
Sent from my SGH-I897 using xda premium
I'm glad it got you back up and running! Now get your JB flash on! There are plenty to choose from for our "ancient" captivates.
One word of advice though. Coming from the point you're at now any JB ROM you flash will likely knock you into a boot loop on the first flashing attempt. Nothing is wrong just three button into recovery and flash again.
Sent from my SGH-I897 using xda app-developers app
And back up the efs folder, just in case.
It contains the vital IMEI info. :thumbup:
Sent from my SGH-I897 using xda premium
Thanks a million guys! Slim bean 2.9 up and running!
It Works!
Got to Slim Bean 2.9 through Cyanogen 9.1 and installed the Slim_GApps.
4-2ndtwin: Thanks for the suggestion to back up the efs folder. I hadn't done that before and now I am feeling VERY lucky that my phone still works at all! It lowered my stress level appreciably plus it was good practice using SDK.
m1batt1: Thanks for the heads up on the double flashing of JB ROM! It saved considerable unnecessary panic (although it was still somewhat unnerving)!
Consider both your thank you buttons righteously whacked! :good: