Database Develop

help rooted samsung captivate wont fully boot

Hi,
I want to say that everyone is very helpful in this forum and you all rock. I'm having some problems with my rooted samsung captivate. I installed the I9000 Full rom, and it was running fine for a few days then I notice it was very sluggish, so I did a factory restore, but data and apps didn't delete. So I then when in to recovery (R2) and deleted cache and all user data files, then it did a factory restore, and it went in boot up pass the att and samsung S i9000 screen and when to the lock screen, but once I unlock the phone, its just in the black screen, when I click and hold on to the home button it goes to recent, no recnet application and under Task Manager, I have 0 active applications. It won't load any programs or apps. I tried restoring the phone by holding the down volume key and power on button, it goes to R2 recovery and then reinstall package, but it can't find the package. I have it on the memory card, but I guess I deleted it from the internal memory when I did a factory restore. Am I screw, or can someone guide me through this and fix my fone. Thanks in advance. XDA Rules.

Odin one click back to stock, assuming you can get into download mode. Also do a master clear just to be sure. A fresh start might be just what your Captivate needs.
Sent from my SAMSUNG-SGH-I897 using XDA App

The same thing happened to me yesterday. Phone was on, battery fully charged. I got on my flight and left it on (forgot I guess) and when I got off the flight, the screen was black. I'll also add, that over the past 3 days the phone was starting to get extremely sluggish (for no reason that I can think of). But back to the rest of the story...
I couldn't get it to turn on, so I pulled the battery and tried again. This time I got the AT&T logo and the Samsung animation. Once the animation was completed the screen goes black.
The phone is still on. How do I know? If I touch any of the bottom buttons they light up.... and stay lit up until I do a battery pull.
Deleted/cleared everything, same behaviour.
I tried reflashing JI6, it works but fails to reinstall the packages, otherwise same behaviour.
I tried reflashing JF6, same behaviour.
The flashes always succeed, but always end up in failure.
Now for the interesting part. I went into recovery mode on JI6. I try to format the internal /sdcard, I get a message that it cannot mount /sdcard /dev... not found.
So to recap, phone not working, recovery mode available, download mode available. adb doesn't seem to be working, but if someone can tell me how to access the phone with "adb shell" while in recovery mode, I might be able to diagnose why /dev... is not mounting... Or at least how I could fix it using adb.
Any help would be appreciated. I'm traveling and needless to say, this is a huge inconvenience, I'm lucky I had my backup phone to at least be able to get online and be able to make calls.

HI,
thanks for quick response. I can get to the recovery mode, where the android holding the shovel. But when I load Odin one click, it don't seem to detect and do anything. o success 0 failed. I installed the samsung captivate windows 7 drivers, the funny thing is when I plug my brink phone in the usb port, it say unrecongize usb. Any other suggestions. Thanks

hksmr2 said:
HI,
thanks for quick response. I can get to the recovery mode, where the android holding the shovel. But when I load Odin one click, it don't seem to detect and do anything. o success 0 failed. I installed the samsung captivate windows 7 drivers, the funny thing is when I plug my brink phone in the usb port, it say unrecongize usb. Any other suggestions. Thanks
Click to expand...
Click to collapse
the shovel is NOT recovery mode, it is download mode.
have ODIN running BEFORE you get your phone in download mode

goofed up, t-mobile rom on a bell phone. help

I've got a major problem. The Bell Galaxy suddenly did an internal SD corruption after running great for a month on Doc's ROM (no lagfixes). Started with FCs and finally no SD available, all within an hour. I could still get to download mode but of course nothing will correct the SD. Stupid me tried the "froyo that won't brick" routine but mistakenly chose to repartition. Now I have a shiny t-mobile 2.2 "Vibrant" with a corrupted SD and can't install anything. And no way to get it into download mode. Plugging in the USB briefly shows up on ADB or Odin but within a few seconds it will shut down. Unplug USB and it reboots.
Before this happened I got the stock JH2 back on it and I should have left it like that for warranty. But now the bootup with 2.2 shows Vibrant instead of the usual GT-I9000M and that will get me denied.
I could try the resistor jig method for download mode but the one thing that worries me is that whenever I plug USB cable the phone shuts down. It seems to be charging at that point but there is no indication on screen.
Is there any hope in hell of getting this back to even a bricked JH2? Can I somehow brick it so bad that nothing shows up? If it shuts down by plugging in USB can I rig it so no power is on USB and still be able to communicate?
I did nothing to cause the SD corruption but the store will deny warranty I'm sure because of what now shows on screen.

And just more FYI.
The only mode I could it into is something I haven't seen before "Power reset or unknown upload mode". Nobody seems to have an answer to this one. That is the only mode that won't shut down by plugging in USB. Odin sees it at this point but won't do anything.
Also, if I do factory reset from the OS I end up in 2e recovery mode with the same can't mount SD errors and of course I can't do anything from there. Plugging in USB shuts the phone down.

solved
solved. what a piece of crap this phone.

Flash gone wrong

Hi,
I've flashed multiple times before without an issue until today.
First, here's my background information:
Samsung Captivate (ATT)
Was running Continuum 5.4.1 but it felt laggy so I attempted to flash MIUI 1.5.13.
Here's what I did:
I wiped my phone using the Odin One click tool, then flashed CM7's kernel and then performed formats of the cache, system, and data, then installed MIUI RC2. After this step the phone should have restarted, then I planned to shut it down and reboot into recovery and flash 1.5.13 onto it.
My problem(s):
-Boot into recovery/download mode using key combinations is not working.
-The ADB console reports device not found when I try to run adb shell.
-The phone is undetected in Droidexplorer.
-When I attempt to download an app to boot to recovery with the phone says there is no space even though nothing has been installed other then MIUI.
What I would like to do:
Get back to stock with download/recovery modes working.
On a side note: MIUI works, but in a very limited way. I can navigate through it, but it won't allow the installation of applications due to there not being room on the phone (as said before).
Thanks!
Update - my phone was being identified as a Nexus S, so without those drivers my phone could not be debugged via USB. I now have the drivers and can perform ADB commands, however rebooting into recovery and into download mode both result in the phone restarting without going to the download or recovery mode.

Try using ODIN and repartitioning. I have good videos on standard ODIN and Heimdall on YouTube just search them. If you can not get out of this contact me, I have been able to partition debrick in the past and it's actually considered by me far more annoying than standard bootloader JTAG in certain situations. Let's hope yours is easier to bail out of!

First of all thanks for the reply and direction.
Secondly:
After working on this all last night I was able to get the phone recognized by Odin and my computer, now I am stuck at one of two screens depending on what I do.
If the phone is powered off then plugged in, the battery charging screen appears but there is no animation and after unplugging it the battery charging image remains.
If I power the phone on it hangs on the Samsung boot screen.
Repartitioning does sound like the proper direction for me to take, but, when I use Odin it freezes while setting up the connection to the phone.

when the phone is powered off try holding both vol keys and plugging in the cable. That could possibly get you to download mode. If not try vol down/pwr at the same time since you are now on GB bootloaders the keys are a bit different. Let me know what happens and good luck

maybe you should try to build a jig and use it to get into the download mode first. or you can buy it on ebay, just search for "micro usb jig".

I've tried every volume and power combination possible to no avail, I can't get into download mode. I've given in and am exchanging my phone. Thanks for the help anyway guys!

[Q] Bootloop, can't get phone to stay in Download mode to reflash

Hi all
I reflashed an old i9000 with CM10.1 for my wife recently, and everything seemed to be working fine. Then it started behaving a bit funny and this week it started rebooting at random. I thought "no worries, I'll just do a fresh flash with stock GB".
However, before I could even give that a go the phone started acting even weirder. As soon as I put the battery in it powers on (without me even pushing the button) but it resets every time it hits the Samsung splash screen. Earlier today I could get it to go into CWM recovery and after clearing cache I actually got it to boot up. But by the time I had downloaded the stock GB files the phone was just constantly resetting at the Samsung logo and now I can't even get it to load CWM recovery using the 3-button method.
I can get it to enter Download mode, and it shows up in Odin just fine. But within 5 seconds it resets itself again so I can't actually perform a flash.
Any suggestions? Or is the phone just plain busted?

mrfurion said:
Hi all
I reflashed an old i9000 with CM10.1 for my wife recently, and everything seemed to be working fine. Then it started behaving a bit funny and this week it started rebooting at random. I thought "no worries, I'll just do a fresh flash with stock GB".
However, before I could even give that a go the phone started acting even weirder. As soon as I put the battery in it powers on (without me even pushing the button) but it resets every time it hits the Samsung splash screen. Earlier today I could get it to go into CWM recovery and after clearing cache I actually got it to boot up. But by the time I had downloaded the stock GB files the phone was just constantly resetting at the Samsung logo and now I can't even get it to load CWM recovery using the 3-button method.
I can get it to enter Download mode, and it shows up in Odin just fine. But within 5 seconds it resets itself again so I can't actually perform a flash.
Any suggestions? Or is the phone just plain busted?
Click to expand...
Click to collapse
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.

Thanks for reporting howto ...:good: good to know
mrfurion said:
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Click to expand...
Click to collapse

mrfurion said:
I'm just going to answer my own question as I've solved the problem but it may benefit someone else to know how.
It got to the point where the phone wasn't even booting to the Samsung splash screen, but I could still get Download mode to show up for 5 seconds (not long enough to flash). Then in a moment of desperation I got the original Samsung microUSB cable and plugged that in, and booted into Download mode again. This time Download mode stuck! And I was able to flash a clean GB ROM which is now working fine.
So the take-out from my experience is this: sometimes you really do have to use the original Samsung USB cable.
Weird.
Click to expand...
Click to collapse
I have a similar issue where I'm trying to flash my stock ROM on my Epic4gTouch. When it opens up the download mode error I start to flash and all seems to work before it reboots. Every 5 seconds. I tried the original cable and it did not help. Any ideas??

NerdsBestAdvice said:
I have a similar issue where I'm trying to flash my stock ROM on my Epic4gTouch. When it opens up the download mode error I start to flash and all seems to work before it reboots. Every 5 seconds. I tried the original cable and it did not help. Any ideas??
Click to expand...
Click to collapse
put the cable and press button power the phone go mode charging at this time make the phone in download mode
its ok for me:good:

[Q] Cannot Enter Recovery Mode

Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.

Bump

Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.

NoDze said:
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
Click to expand...
Click to collapse
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?

xda_fanboy said:
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
Click to expand...
Click to collapse
Don't give up yet. Try smartflash and flash stock, or whatever. Seriously. Just keep on trying. I had a Samsung Captivate a year back and something similar happened where I woke up one beautiful morning, tried to unlock my phone: no response. I thought I had an SOD, so I pulled the battery out, reinserted: bootloop. Entered recovery, can't flash anything, unable to mount system/data partitions. Turns out my internal memory/ROM got fried. Yay. But until then, I tried every possible option. Wow, this turned out to be a bit depressing. Just try more stuff. After you've tried everything, and I mean everything, declare the phone dead.

I think i have a similar problem. Just woke up to find my phone to be dead. Tried the usual methods, nothing. Best it could do was from time to time show me a battery sign with a red triangle and a whtie exclamation mark in it. Then sometimes i manage to get into the recovery mode, there i tried practically everything. Used restore, it shows that restore was a success, but when i reboot my phone i get into an endless circle of bootloader icon appearing and dissappearing,
EDIT: somehow from the countless attempt it fired up.

Make sure to have the right bootloader before nvflashing unbrick roms....

xda_fanboy said:
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Click to expand...
Click to collapse
Try to flash a new recovery image in apx mode.
And edit the /dev/block/mmcblk0p3 partition your self.
seek=6144 count=75 bs=1 / boot-recovery

Thanks for the added input and encouragement folks.
Just reporting an update:
Having been unsuccessful more times than I could count, I decided to physically disassemble the phone (normally Engineering fix #2, but performed out of order on this occasion). I have zero idea why it should have made a difference, as all I did was take it apart and then put it back together, but the phone has groaned back to life.
Of course, then sausage-fingers here managed to tear the digitizer cable when doing the final reassambly... /facepalm
Anyhow, I have a replacement on order, so I'm hopeful that when I receive that in a few days I'm back to a fully functional Optimus 2x!!