Related
Hello everybody,
I have a question regarding the actual situation of my phone since nobody on here seemed to had the same issue.
My diagnosis is that my phone is softbricked.
If I try to boot it normally the first Galaxy S logo appears but when the loading animation is supposed to begin, it doesn't. Additionally my phone vibrates one time with a logn vibration and after half a second with 3 short vibrations, looping on this situation.
Neither download mode or recovery mode button combo seems to work.
If I start with one of the two and release the keys as soon as the first logo appears it will be stuck at boot vibrating as above, if i don't release them, it just keeps rebooting.
Do you think I could get out of this with a download mode usb jig?
Thanks in advance
Soft brick......Yes to the jig.......try adb commands if you can get a connection..."adb reboot download"
Edit: Also have you read the many other attempts to try get to download... without battery but plugged in then combo, holding combo then putting battery in (no cable), finally cable and battery in then combo... i think there are a few more....
Also i hope you came across this
Telling us what you have done to your phone will help greatly!
What rom on /from, kernel, theme - what were you doing when it went tits-up?
Sent from my Galaxy S using XDA Premium App
try removing your battery for a few seconds. then hold down the vol down+power+menu then insert the battery while holding the 3 buttons to display the download mode.
update
Talon26 said:
Soft brick......Yes to the jig.......try adb commands if you can get a connection..."adb reboot download"
Edit: Also have you read the many other attempts to try get to download... without battery but plugged in then combo, holding combo then putting battery in (no cable), finally cable and battery in then combo... i think there are a few more....
Also i hope you came across this
Click to expand...
Click to collapse
hackfinn said:
try removing your battery for a few seconds. then hold down the vol down+power+menu then insert the battery while holding the 3 buttons to display the download mode.
Click to expand...
Click to collapse
I tried almost every combination I could find out on the net but nothing else happens, I've bought a jig on ebay and it should arrive in a couple of days. I will try and update ASAP.
woolf clubs said:
Telling us what you have done to your phone will help greatly!
What rom on /from, kernel, theme - what were you doing when it went tits-up?
Sent from my Galaxy S using XDA Premium App
Click to expand...
Click to collapse
I was on a stock 2.2 rooted room and I was following the guide to install cyanogenmod which is placed in the cyanogenmod wiki site...
after I flashed the speedmod kernel with hemdall, I got stuck in this situation.
Hi um I'm pretty new to Android phones, and my Captivate's stuck in a bootloop...
I had CyanogenMod 9 on it, based on ICS 4.0.4, which i still have the .zip for if necessary. But I think I did something stupid... in the recovery (which said something about CWMrecovery) mode, I absent-mindedly formatted the /system directory... derp....
Now basically the phone shows the AT&T logo, then shows some kind of recovery screen, it only flashes up for a short time but I can see in the background both an android, like stock recovery mode, and the logo from ROM manager (or something very similar). There is some text at the bottom but it's very small and only flashes up for a split second so I can't read it... and what's worse, it won't boot into recovery...
I'm not exactly sure how to even do it, but random combinations of the volume & power buttons and home.. screen-area-thing work eventually.. but it's just not working now, as i hold the buttons it either just keeps rebooting before it gets past the AT&T logo or ignoring it completely, showing the recovery screen then rebooting again anyway
Sorry it's kinda long.. I tried to be detailed XD
tl;dr CM9 rom Captivate, formatted /system, stuck in bootloop, recovery mode won't work
Any help would be much appreciated
Edit: Forgot to say, I've searched around already but I haven't found anyone else who's bootloop is caused by formatting /system -.-
re flash the rom. you erased the rom.
dont wipe dont format just flash the rom again. you should be back as if it never happened.
If your in a boot loop you might want to invest in a jig, only $6 on eBay
You also said recovery doesn't work? Have you tried putting it into download mode?
Sent from my SGH-I897 using Tapatalk 2
This might help you:
http://forum.cyanogenmod.com/topic/39685-stuck-on-boot-loop/
If not google Samsung captivate boot loop. Lots of info on how to fix out there. Sorry I don't work on many Samsung phones. Primarily HTC.
Sent from my Inspire 4G using XDA
jig will not help bootloop.
you are freaking out because of the bootloop and not holding the button combo for recovery long enough.
take out the battery. and replace
hold both volume buttons
then hold power
keep buttons held for 5 seconds AFTER screen comes on.
if your phone turns on and starts to boot, you have recovery and download.
TRusselo said:
jig will not help boot loop
Click to expand...
Click to collapse
You sure? Fixed my phone from boot loop!
Sent from my SGH-I897 using Tapatalk 2
TRusselo said:
jig will not help bootloop.
you are freaking out because of the bootloop and not holding the button combo for recovery long enough.
take out the battery. and replace
hold both volume buttons
then hold power
keep buttons held for 5 seconds AFTER screen comes on.
if your phone turns on and starts to boot, you have recovery and download.
Click to expand...
Click to collapse
Tried that, isn't working :\ it just ignores it, shows the recovery screen realy quick then reboots again...
I've had this happen on my captivate...only option is to flash back to a stock ROM and work your way back up to CM9 or whatever you were trying to flash originally. To do this your gonna have to get into download mode. A jiff is your best friend in this situation as suggested by several others. however if the button combo for download mode works for you, that is best. Try unplugging the battery, wait for like 10 seconds and plug back in. Have a PC running, and make sure you have the drivers installed. have the USB cable plugged into your computer, and while holding both the volume buttons down, plug the cable into your phone as well. This should put you into download mode and your good to go.
Sent from my SGH-I897 using XDA
thanks cmilldrummin (and everyone else)
I got my phone into download mode fine... but i don't think I have the drivers :s (googling still, but can't find them so far)
Also I got it into recovery mode earlier, re-flashed the same custom ROM but when I tried to load it it just kept loading with the blue android on a skateboard until the battery ran out (It was the same one, CM9)
Is the like actual android system openable in download mode? so I could re-write the /system folder? if not I guess I'll just try to re-flash a stock rom then upgrade.. *crosses fingers*
Best way is to flash back to stock and start fresh.
Sent from my Serendipity VII flashed Captivate using xda premium
Np Dolei, but yea back to stock is best, gives you a nice clean slate, with no glitches or errors
Sent from my SGH-I897 using XDA
TRusselo is right. The other posts here are taking the sledgehammer approach for a simple fix. If you cannot get into recovery mode - you're doing it wrong, try again. reflash your rom from recovery and all done.
Dolei said:
Hi um I'm pretty new to Android phones, and my Captivate's stuck in a bootloop...
I had CyanogenMod 9 on it, based on ICS 4.0.4, which i still have the .zip for if necessary. But I think I did something stupid... in the recovery (which said something about CWMrecovery) mode, I absent-mindedly formatted the /system directory... derp....
Now basically the phone shows the AT&T logo, then shows some kind of recovery screen, it only flashes up for a short time but I can see in the background both an android, like stock recovery mode, and the logo from ROM manager (or something very similar). There is some text at the bottom but it's very small and only flashes up for a split second so I can't read it... and what's worse, it won't boot into recovery...
I'm not exactly sure how to even do it, but random combinations of the volume & power buttons and home.. screen-area-thing work eventually.. but it's just not working now, as i hold the buttons it either just keeps rebooting before it gets past the AT&T logo or ignoring it completely, showing the recovery screen then rebooting again anyway
Sorry it's kinda long.. I tried to be detailed XD
tl;dr CM9 rom Captivate, formatted /system, stuck in bootloop, recovery mode won't work
Any help would be much appreciated
Edit: Forgot to say, I've searched around already but I haven't found anyone else who's bootloop is caused by formatting /system -.-
Click to expand...
Click to collapse
TRusselo said:
re flash the rom. you erased the rom.
dont wipe dont format just flash the rom again. you should be back as if it never happened.
Click to expand...
Click to collapse
TRusselo said:
jig will not help bootloop.
you are freaking out because of the bootloop and not holding the button combo for recovery long enough.
take out the battery. and replace
hold both volume buttons
then hold power
keep buttons held for 5 seconds AFTER screen comes on.
if your phone turns on and starts to boot, you have recovery and download.
Click to expand...
Click to collapse
Try doing this, this has worked for me since I can't get into recovery with the traditional button combo method of holding all three buttons at the same time.
Turn the phone off. Hold the power button, vol up, vol down. Once the ATT boot screen comes on, let go of the power button. Keep holding the volume buttons and voila, you're in recovery.
Agree. Definitely go back to stock if possible first.
Sent from my Inspire 4G using XDA
I currently have The Collective's AoCP build 3 Jelly Bean ROM on my Captivate. I need to go back to the Cyanogen 10 builds because it looks like they've fixed the lag issue. I came upon a really bad accident on my way to work and needed to call 911 ASAP. I unlocked my phone and hit the phone button and it must have taken 20 seconds for the dial pad to come up. I've gotta try something else...
My question is this. I can't get into recovery by turning the phone off and using the 2 or 3 button salute. I've tried volume up - power, volume down - power, and volume up&down - power. No dice. I've learned there is a 3buttonfix that I can download and install, but I read about it first and it says if you're running this bootloader or that bootloader don't use this fix because you WILL hard brick your device. I have no idea what bootloader I'm running and if I can't use this fix, what do I do to fix the issue? For future reference, how do I tell what boot loader I'm running?
The reason I want to MAKE SURE the 3 button salute works is I want to flash from AoCP to CM10 and if something goes wrong, I need to be able to do that. I can hold the power button down now, and choose reboot, then boot into recovery, and that works, but if I soft brick my device, that function won't do me any good.
Any guidance you pros out there have for me would be greatly appreciated. Thanks in advance!
Don't use the 3 button fix. You are correct in that it will hard brick your phone. If adb works, you can use that to reboot into recovery. I think you can do that with a terminal emulator too ("su" first to get root access, then "reboot recovery").
There's not a way to tell which bootloader your on. If you want to know 100% without a doubt your on the latest, flash the kk4 stock ROM. Downside to that is you would have to start over on cm10 or any other aokp. Making a nandroid first will make it less painful.
Also, that dialer lag will happen with any ICS-JB ROM on this phone. It's pretty much unavoidable at this point. Have you ever done the recovery combination before? If not, then you may be doing it wrong. Hold down the volume buttons, and press the power button only until the screen turns on. Hold the volume keys down until you hit recovery.
Oh, duh, you're on AOcP. You should have a recovery option in your power menu under reboot.
Oh said:
I do have a recovery option int he power menu. But what if I soft brick my device? I have a rigged jig somewhere, but that wasn't reliable for me. Not because it doesn't work, but because I made it very, um, frugally.
So there is no way to know what boot loaders I'm on? Darn... I didn't do the original flashing. MobileTechVideos.com did the flashing after I hard bricked it where my jig no longer even worked.
Thanks all for your input, and anything else you may suggest.
Click to expand...
Click to collapse
If you're on AOCP you have GB bootloaders.
Sent from my SGH-I897 using Tapatalk 2
spagman72 said:
If you're on AOCP you have GB bootloaders.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
THANK you very much for that info. Do you know of anyway for me to be able to boot into recovery mode using a key combination? I tried what was mentioned above (holding volume up-down after pressing the power until it boots into recovery, but it just goes right to the AoCP boot animation).
Maybe your holding the buttons too long when you try the button combo.
Snevey said:
THANK you very much for that info. Do you know of anyway for me to be able to boot into recovery mode using a key combination? I tried what was mentioned above (holding volume up-down after pressing the power until it boots into recovery, but it just goes right to the AoCP boot animation).
Click to expand...
Click to collapse
You may have already tried this in your many attempts but I'll still throw in my two cents.
Starting with power off hold all three buttons at the same time. First you should see the att splash screen and then your kernel splash screen. Then the phone should turn off. Keep holding the buttons til you see the att screen again and then release them all. That should get you into recovery. At least that is exactly how I get there besides of course the power menu.
Sent from my SGH-I897 using xda app-developers app
Wait are you missing download mode also?
Sent from a jelly bean
Yes, I do appear to be missing download mode as well... What have I done? The phone runs just fine with AOCP The Collective, except it's just getting too laggy for me and I want to check out CM10's newest releases. BUT, I don't want to be flashing ROM's until I can boot into Recovery. I can REBOOT my phone from my Power menu once the phone boots up, but I can not get any button combination to work to boot me into recovery.
Regarding download mode... I can not enter download mode either. I power down, take battery out, remove SIM, place battery in phone hold volume up/down and insert usb cable. Just displays the battery charging meter...
When your phone turns on, do you have a white AT&T screen or is it a black gt-i9000 screen?
Sent from a jelly bean
korockinout13 said:
When your phone turns on, do you have a white AT&T screen or is it a black gt-i9000 screen?
Sent from a jelly bean
Click to expand...
Click to collapse
I do get the white AT&T screen... It comes on, then flash to a black screen and then back to the same white at&t screen, then to The Collective boot animation. This wouldn't be a problem for me, but I do want to play with some other ROM's, but I don't want to without this working...
I believe you can reboot in recovery using adb with the command : "reboot recovery"
Sent from my SGH-I897 using Tapatalk 2
spagman72 said:
I believe you can reboot in recovery using adb with the command : "reboot recovery"
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
I KNOW I can, but I can only do that if I am able to boot into a rom. What if something gets hosed?
Snevey said:
I KNOW I can, but I can only do that if I am able to boot into a rom. What if something gets hosed?
Click to expand...
Click to collapse
Find that jig you rigged up and see if that gets you into download mode. If so I suggest using a one-click back to kk4 and I'd get the one with boot loaders for good measure. Then see if you can do any of the button combos
Sent from my SGH-I897 using xda app-developers app
m1batt1 said:
Find that jig you rigged up and see if that gets you into download mode. If so I suggest using a one-click back to kk4 and I'd get the one with boot loaders for good measure. Then see if you can do any of the button combos
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion... I downloaded a 1 click to KK4 and used my jig, which worked. Got really lucky, as something happened at the SET PIT table during the ODIN process and I had to start over. Luckily it didn't brick, but on the next boot I got the icon of a phone and a computer with a triangle in between those icons. I ran ODIN again after booting into download mode, and it took. I'm not running KK4 and I can do the 3 finger salute, so now I'm going to start over with rooting and moving to Jelly Bean. What a way to get the recovery back...
Thanks again for everyone's assistance.
Snevey said:
Thanks for the suggestion... I downloaded a 1 click to KK4 and used my jig, which worked. Got really lucky, as something happened at the SET PIT table during the ODIN process and I had to start over. Luckily it didn't brick, but on the next boot I got the icon of a phone and a computer with a triangle in between those icons. I ran ODIN again after booting into download mode, and it took. I'm not running KK4 and I can do the 3 finger salute, so now I'm going to start over with rooting and moving to Jelly Bean. What a way to get the recovery back...
Thanks again for everyone's assistance.
Click to expand...
Click to collapse
Glad that got you up and running. Sometimes it's unavoidable to flash back to stock like that but I suggest you keep that one click handy in case something else strange happens.
I bricked my tablet after I tried to change my font using font installer by jrummy?
It asked me to restart for changes to occur so I figured if I restarted on my own it would work the same way so I hit cancel. I restarted about 1 minute after I hit cancel.
My tablet will boot up to the AT&T "Rethink possible" screen (after the animation).
It will get stuck there with a pattern of light vibrations between a couple seconds each.
Currently running the stock AT&T ics rom posted in the android dev section for i957.
I've tried to boot into recovery but the Samsung screen doesn't come up until I let go of the buttons therefore leading it to reboot again.
Also tried to go into the emergency download mode ( power, up, down) but it didn't work either.
I appreciate all and any advice, please and thank you!
My device is rooted if that wasn't already implied, I will provide any other details if needed, please help!!
Thanks again!
Are you sure you can't get into recovery mode? Hold power and volume up buttons, etc. Does Odin recognize the device?
Do you have a custom recovery, and if so which one, or is it stock.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
keep trying to get into download mode or recovery. should be possible. the font change will not affect recovery.
I was also performing a backup with titanium backup when I restarted does that make a difference?
I have clockwork mod recovery.
From experience, I can only go into recovery if the Samsung logo pops up for a milli second and I let go.
I actually haven't tried to see if Odin recognizes my device but I assumed if I couldn't go into download mode it wouldn't.
MzzSarahx3 said:
I was also performing a backup with titanium backup when I restarted does that make a difference?
I have clockwork mod recovery.
From experience, I can only go into recovery if the Samsung logo pops up for a milli second and I let go.
I actually haven't tried to see if Odin recognizes my device but I assumed if I couldn't go into download mode it wouldn't.
Click to expand...
Click to collapse
Were you restoring apps from a honeycomb Rom? That will cause a soft brick.
Sent from my SAMSUNG-SGH-I727 using xda premium
If you can get into recovery do a factory reset. That should get you out of a soft brick. You'll have to re-install your apps though.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
I never use tibu anymore
Sent from my SAMSUNG-SGH-I727 using xda premium
Didnt see if you worked your way out of this or not. You may have to hold 3 finger salute (power, up, down) for up to 16 seconds. My guess is that covers the 8 seconds to reboot through any hang up plus up to 8 more to boot to menu.
Still no luck, the computer is not detecting my tablet.
I also wasn't restoring, I was just backing up my data. I'm letting it charge for now, anyone know what else I should do?
I really can't enter recovery OR download.
**** UPDATE****
Okay guys I finally fixed it. Will post details if anyone is still interested.
I'd be interested in the details.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
How did you do?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
I couldn't go into download mode until I did some weird trick with the buttons.
I had to hold the 3 buttons ( power, vol up, vol down) for a couple seconds.. like 6 seconds
THEN hold power and vol up for 2 secs
THEN back to power, vol up, vol down.
I did it by accident cuz I was frustrated but it ended up working so all is good
Thanks for all the help guys!!
I am in the Same Boat!
MzzSarahx3 said:
Still no luck, the computer is not detecting my tablet.
I also wasn't restoring, I was just backing up my data. I'm letting it charge for now, anyone know what else I should do?
I really can't enter recovery OR download.
**** UPDATE****
Okay guys I finally fixed it. Will post details if anyone is still interested.
Click to expand...
Click to collapse
Please Post the fix as I am having the same exact issue as you were! Thanks
The fix has already been posted. :good:
Is there any hope for me?
Running stock 4.0.4 on my unrooted GT N7000. Phone was plugged in and charging (nearly full 89%) when I tried to use swipepad to launch my goole reader app. Everything froze while still in swipepad and was unresponsive for about five minutes while I waiting for a crash report. Crash report never came so I tried the power button. No response, still showing the frozen swipepad screen. Took the battery out and put it back in again, hit the power button and it shows the galaxy note launch screen (Galaxy Note GT N7000 in white on the black screen). It stays there with no change (this is a bootloop, right?).
I've tried going into recovery mode (vol down, home and power) and nothing happens, it just goes into the bootloop. Tried to get into odin mode (vol up, home and power) and I can get to the warning screen where you can select either boot as normal, or download mode. Boot as normal leads to bootloop, download mode gets immediately frozen.
I've also tried the "take battery out, hold volume, home and power while replacing battery" process with no luck
What happened? What did I do? What do I do?
I'm dying here.
As far as I can tell, all solutions I've seen have involved access to recovery mode....
Unmarked Door said:
Is there any hope for me?
Running stock 4.0.4 on my unrooted GT N7000. Phone was plugged in and charging (nearly full 89%) when I tried to use swipepad to launch my goole reader app. Everything froze while still in swipepad and was unresponsive for about five minutes while I waiting for a crash report. Crash report never came so I tried the power button. No response, still showing the frozen swipepad screen. Took the battery out and put it back in again, hit the power button and it shows the galaxy note launch screen (Galaxy Note GT N7000 in white on the black screen). It stays there with no change (this is a bootloop, right?).
I've tried going into recovery mode (vol down, home and power) and nothing happens, it just goes into the bootloop. Tried to get into odin mode (vol up, home and power) and I can get to the warning screen where you can select either boot as normal, or download mode. Boot as normal leads to bootloop, download mode gets immediately frozen.
I've also tried the "take battery out, hold volume, home and power while replacing battery" process with no luck
What happened? What did I do? What do I do?
I'm dying here.
As far as I can tell, all solutions I've seen have involved access to recovery mode....
Click to expand...
Click to collapse
You are not in a bootloop (which is when the bootanimation repeats over and over) you are stuck in the splash screen. Anyway, that is not important. As you are running the stock ICS firmware which has the brick bug, I would suggest you flash the rom again in ODIN PC. Find your firmware and follow the tutorial in here:
http://forum.xda-developers.com/showthread.php?t=1329360
DO NOT TRY TO WIPE ANYTHING IN STOCK RECOVERY.
glevitan said:
You are not in a bootloop (which is when the bootanimation repeats over and over) you are stuck in the splash screen. Anyway, that is not important. As you are running the stock ICS firmware which has the brick bug, I would suggest you flash the rom again in ODIN PC. Find your firmware and follow the tutorial in here:
http://forum.xda-developers.com/showthread.php?t=1329360
DO NOT TRY TO WIPE ANYTHING IN STOCK RECOVERY.
Click to expand...
Click to collapse
Thanks for clearing that up (re the bootloop vs stuck in the splash screen), but looking through the tutorials, even with Odin installed on the PC, I'll need to get access to the recovery mode.
I can't boot into recovery mode. What then? Is there any way to flash a rom without recovery mode access?
From what I know you need recovery or download mode to flash a ROM you may want to order a USB jig and see if you can get it to down load mode that way other then that you may be bricked
Sent from my GT-N7000 using XDA Premium HD app
ttibbetts83 said:
From what I know you need recovery or download mode to flash a ROM you may want to order a USB jig and see if you can get it to down load mode that way other then that you may be bricked
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
My USB port is tempermental. OTG has been out of commission for a while.
So basically, through no fault of my own and without any recourse my phone is dead.
That's just great.
So, is this Google's fault, or Samsung's?
If you have not modified the phone be it kernel,rooted it, or custom ROMs then it would be a Samsung issue in my opinion anyways
sent from the darkness
ttibbetts83 said:
If you have not modified the phone be it kernel,rooted it, or custom ROMs then it would be a Samsung issue in my opinion anyways
sent from the darkness
Click to expand...
Click to collapse
Hmph.
Well thanks again.
I guess a terminal diagnosis is still a diagnosis.
Gutted.