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

[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!!

[Q] Permanent Boot Loop

Greetings,
My internal sd card died slowly over time. It failed to mount on some occasions at first. After a few weeks I had massive app crashes.
Everything I did on the phone (installing apps, deleting files, even doing a factory reset) seemed to revert back after rebooting the phone. I mean I delete some files, and after reboot, the files came back from the dead. Same thing for factory reset.
Installing other roms made the situation even worse, and I had to revert back to stock 2.3 rom.
And since last week, the phone is on permanent bootloop. It won't go into download or recovery mode (it used to activate those modes with 3 button combo before).
I tried the USB JIG method. Built a 301k resistor, connected pins to the usb thingie. It did power the phone on, but failed to trigger the download mode. The phone still goes into a boot loop.
Anyone has any ideas? I don't know what more information I can provide about the issue.
Regards,

No download mode?
If your phone won’t enter download mode, you can try three things:
A USB jig. Don’t pin your hopes on this, they rarely succeed in this scenario.
‘Jump starting’ – You might need someone else to give you a hand for this. Take the battery out of your phone and wait 30 seconds. Now, press the button combination to enter download mode, and with this combination still depressed, get someone to put the battery back in. Hopefully this will jolt your phone into download mode.
Take out the phone battery, and re-insert it, but don’t turn the phone on. Now, plug in the charger while holding the volume down button. Keep holding volume down till you enter download mode.
If your phone won’t enter download mode, and will do nothing but get hot when you attempt to do anything to it (charge it, turn it on), then your motherboard is in need of replacement.
Your options
I’ve seen a lot of people, when their Odin flash fails, either:
Give up. Not a good option.
Flash a .pit file. That should be used as an absolute last resort. There’s a lot to try before getting to that stage! If a flash of a .pit file fails in Odin, your phone is well and truly unrecoverable, and you will need a motherboard (MB) replacement.
Quoted from a quite by Hopper8, try these steps. Can't really do anything since recovery/download mode is dead. If you can get into download mode, flash a .pit file (get all the files ready beforehand). Be quick, since you don't know when your device will die again.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!

FraggyDav said:
Greetings,
My internal sd card died slowly over time. It failed to mount on some occasions at first. After a few weeks I had massive app crashes.
Everything I did on the phone (installing apps, deleting files, even doing a factory reset) seemed to revert back after rebooting the phone. I mean I delete some files, and after reboot, the files came back from the dead. Same thing for factory reset.
Installing other roms made the situation even worse, and I had to revert back to stock 2.3 rom.
And since last week, the phone is on permanent bootloop. It won't go into download or recovery mode (it used to activate those modes with 3 button combo before).
I tried the USB JIG method. Built a 301k resistor, connected pins to the usb thingie. It did power the phone on, but failed to trigger the download mode. The phone still goes into a boot loop.
Anyone has any ideas? I don't know what more information I can provide about the issue.
Regards,
Click to expand...
Click to collapse
My little sister had the same problem.
But now the phone is complete dead.
Not booting after bootloop.
No customroms ever installed.

[Q] I think I actually bricked my M7

A day ago the battery got kinda low and I put it on charge. It started rebooting on its own while charging, I put it down to being low on battery and went along with my day. A few hours later I took it off charge and i was still rebooting itself after around 30 seconds being in the OS.
I thought it may be the ROM and did a wipe, after a wipe everything worked for 12 hours, it was even used outside and got real warm with no problems. Then I started uninstalling the apps that my old HTC Backup put back on and it did the same thing.
I did another wipe and just installed swiftkey (was NOT installed before) and then it started doing the exact same thing. I decided to try a different ROM in-case that would solve the problem, once I flashed a new ROM i restarted and it just took me into the bootloader and no further.
Recovery doesn't work, it just reboots. I tried plugging it in but all I get is it working for 10 seconds and then "USB Device not recognized". During the 10 seconds I still cant send ADB/Fastboot commands to it. I tried different PC's with and without USB 3.0 and 3 different cables. Before this ADB worked fine
All the drivers are correct, and I tried using HTC Sync drivers. (Even with the drivers uninstalled I get the error about it not being recognized)
Does anyone have any ideas? Or should I just sell it and move on?
Here is the screen with all the info on - https://dl.dropboxusercontent.com/u/6017469/P1010831.JPG

SeanBond said:
A day ago the battery got kinda low and I put it on charge. It started rebooting on its own while charging, I put it down to being low on battery and went along with my day. A few hours later I took it off charge and i was still rebooting itself after around 30 seconds being in the OS.
I thought it may be the ROM and did a wipe, after a wipe everything worked for 12 hours, it was even used outside and got real warm with no problems. Then I started uninstalling the apps that my old HTC Backup put back on and it did the same thing.
I did another wipe and just installed swiftkey (was NOT installed before) and then it started doing the exact same thing. I decided to try a different ROM in-case that would solve the problem, once I flashed a new ROM i restarted and it just took me into the bootloader and no further.
Recovery doesn't work, it just reboots. I tried plugging it in but all I get is it working for 10 seconds and then "USB Device not recognized". During the 10 seconds I still cant send ADB/Fastboot commands to it. I tried different PC's with and without USB 3.0 and 3 different cables. Before this ADB worked fine
All the drivers are correct, and I tried using HTC Sync drivers. (Even with the drivers uninstalled I get the error about it not being recognized)
Does anyone have any ideas? Or should I just sell it and move on?
Here is the screen with all the info on - https://dl.dropboxusercontent.com/u/6017469/P1010831.JPG
Click to expand...
Click to collapse
Damn, sorry. Pretty sure you're out of luck if you can't connect to PC and you can't get into recovery. I'd give it straight into support now and give an excuse like update failed, randomly started restarting etc.

What OS Are you running? 8.1? I would suggest using a Linux Live Disc or Windows 7. its much more reliable.
I am pretty sure you need hboot 1.56+ for windows 8 to work correctly in Fastboot

SeanBond said:
A day ago the battery got kinda low and I put it on charge. It started rebooting on its own while charging, I put it down to being low on battery and went along with my day. A few hours later I took it off charge and i was still rebooting itself after around 30 seconds being in the OS.
I thought it may be the ROM and did a wipe, after a wipe everything worked for 12 hours, it was even used outside and got real warm with no problems. Then I started uninstalling the apps that my old HTC Backup put back on and it did the same thing.
I did another wipe and just installed swiftkey (was NOT installed before) and then it started doing the exact same thing. I decided to try a different ROM in-case that would solve the problem, once I flashed a new ROM i restarted and it just took me into the bootloader and no further.
Recovery doesn't work, it just reboots. I tried plugging it in but all I get is it working for 10 seconds and then "USB Device not recognized". During the 10 seconds I still cant send ADB/Fastboot commands to it. I tried different PC's with and without USB 3.0 and 3 different cables. Before this ADB worked fine
All the drivers are correct, and I tried using HTC Sync drivers. (Even with the drivers uninstalled I get the error about it not being recognized)
Does anyone have any ideas? Or should I just sell it and move on?
Here is the screen with all the info on - https://dl.dropboxusercontent.com/u/6017469/P1010831.JPG
Click to expand...
Click to collapse
usually when it boots into the os, then reboots after 30sec or so, the radio is borked. the radio is the last thing to load in the os
if you can get into the bootloader as it shows in your pic, you need to select FASTBOOT. what you see in the pic is youre in HBOOT mode, and that will not connect to a pc that way. ADB will not work in the bootloader in any case, so dont even try that. You should have your recovery.img file ready, get into the bootloader as you show, and select FASTBOOT. then flash your recovery with command-- fastboot flash recovery recovery.img
however, if your radio is hosed, flashing a rom wont help you. You should probably do a RUU. Many RUU's work off fastboot mode, so get into that and start the RUU.exe