Try to wait out the bootloop, if you manage to get your phone booted (may take up to 4 hours) download terminal from the market, and use the command: Reboot download, then reflash to stock using heimdal
If you are unable to get your phone into download mode, you will need Jtag or unbrickable mod. (I had this problem, My phone booted after 2 hours from powering it on. since this happened while flashing back to stock, I was unrooted, and had to wait a total of 7 hours, through 3 reboots to get my phone rooted and into download mode.) http://forum.xda-developers.com/showthread.php?t=1481526
does this mean a jig wont work on BOOTLOOPED Captivate?
1. Questions go in the Q&A
2. A jig should work on all but the Hard Brick
Okay dude, you've already posted several threads about your bootloop. You also PM'd me. I realize it's frustrating to be in a bootloop, but really nothing can be said until you get your jig and test it out. Jigs usually work where nothing else does, but there's a small chance it won't work. That post you quoted doesn't mention a jig at all, so I would assume they didn't use one. Oh, and as stated above, this belongs in Q&A (like most of the threads that get posted here...)
Related
Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(
Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.
Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions
Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.
I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.
If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.
Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.
After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.
Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.
Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.
I have spent the past 3 hours scouring over these forums before doing a post and I could find lots of great information if I could just get past the perpetual loop and access either the Recovery or Download Modes of my phone.
It is a Telus Samsung Galaxy Fascinate [SGH-T989D] and I have been tinkering with it for that past 24 hours to get it rooted and play with some of the ROMs out there.
I have gotten past the 3e Recovery Issues, resolved a Soft Brick and tested out 3 ROMs but now I am completely stuck and I think it is entirely my own fault but now I need some assistance in getting out of it.
This morning I threw on ICS_NBv9.2 and as it warned it went into a bit of a panic mode and has hit a perpetual Boot Loop. Now every post I have read says go into Download Mode and Odin back to Stock...I can't...it comes up with the Battery Image twice and then starts the boot up cycle all over again. The other option is to Flash the ROM again...problem is it continuously cycles through the Boot and never goes anywhere.
I have tried multiple Cables, reinstalled the USB Drivers, tried on 4 different Computers (2 Linux and 2 Windows) and well lets just say I am at the end of my rope.
Is there any known way to stop this kernel panic and let me get back to stock and put a functional ROM on the phone.
Thanks in Advance.
I may be able to help you...
Here are some solutions I can think of from the top of my head.
Try to see if your phone will connect to samsung kies on your computer via USB, there should be a way to restore it from there.
If you can't do this, then the next step would be to try and enter CWM Recovery mode (you should have this installed already, just look online how to enter into recovery mode). Next, mount your phone using recovery and put a stable rom (.zip) onto your phone. Factory reset, and wipe your phone, then flash the rom.
If you can't enter CWM Recovery, then the next step I can think of is to find a stable rom and flash it through ODIN.
If this isn't working either, then you just made yourself a very stylish paper weight! congrats.
There may stil be hope that if you call your carrier and tell them a sob story like, "my phone restarted on it's own and now it won't work properly." - and answer no if they ask you if you flashed, or downloaded 3rd party apps - then they might send you a free replacement.
Next time you want to flash your phone, remember... MAKE A BACKUP (nandroid) FIRST. That way if anything goes wrong, you can just restore it back the way it was.
Here is a site that may help you as well for rooting and making a backup for the t-989D (samsung galaxy s2 x - telus):
http://androidforums.com/galaxy-s2-...d-ultimate-root-optimization-guide-steps.html
Good luck,
J
Try This..
Remove Data Cable from Phone
Remove battery and re insert after 3-5 secs
now try to enter Downloading mode..
then insert data cable. and flash stock FW.
it should work..
The Paper Weight Theory
Thanks Input_Method and ranjan.
Unfortunately the reboot takes effect and cycles through before Kies, ODIN or anything else can take hold of the device.
I have tried the cable trick, Recovery Mode is a no go and it would appear to be an issue with CWM mismatch which is causing the reboot.
Hoping that a local "phone hacker" can help me out with a JTAG reboot this weekend but I am not overly optimistic.
Thanks again.
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
Well, Ive been flashing roms for a while now and I have an issue with my captivate.
Lets start in the beginning. I had my captivate on THS ICS rom and It was going great. But my captivate isn't that great anymore. The power button is broken, but I was able to go around that. (Sidenote: It turns on when I plug in the battery.) Anyway, I wanted to go back to stock because I did have the right bootloaders. (I couldnt get into download mode with the button combination. I thought it was the bootloaders fault. Im I wrong?) I wanted to switch to I9000 bootloaders but I had to start fresh. But before all that, I noticed that while I was on ICS rom, I was unable to go to download mode. I used to before, but it magically disappeared (I know it didnt, I know I did something to it but I don't quite remember when it happened.) So I was unable to flash a new rom, if I wanted to.
A couple of days ago, I bought a jig and it worked! It took me straight to download mode. So I decided to get my Captivate and make it go back to stock. So I opened Odin, it found my Cappy and I clicked start. But, it stopped at factoryfs.rfs. I waited a half hour and nothing. So I unplugged it and now it won't turn on. But it can still go into Download Mode and be seen by Odin but it just wont finish. I tried both odin one click and the regular odin. I looked everywhere for more than six hours and nothing came up. Please guys, if anyone knows what I can do to fix it, please reply.
I might have missed something, but just ask if you need any more info. Please help me.
Edit: I forgot to add this:
While I was on the ICS rom, I switched over to CM7 to see if the process of going back to stock would be easier. Thats when I tried to flash stock. It didnt work as well as I thought it would.
And I knew that I didnt have I9000 bootloaders because I installed the Icy Glitch kernel and each time I tried to have DIDDLE on it would go to deep sleep mode and I was unable to wake it back up.
As long as you can get to download mode you are fine. Try flashing a different stock from. Or using Hiemdell
I've tried both odin and Hiemdell. But with Hiemdell, it would always tell me that I dont have the drivers installed. So, it installs it for me. Even with the drivers installed, it keeps telling me that I dont have the proper drivers installed.
I have had this exact problem, where a bricked captivate can get into download mode but when restored to stock through a one-click, it freezes on the factoryfs.rfs. However, in my case after freezing at this stage, the phone was completely inoperable, and could not even enter download mode, so I am suprised yours could.
What works for me is to remove the battery, wait for a few seconds, put the battery back in, use the usb jig to enter download mode, and then WITHOUT the phone plugged into the pc, download and open this one-click file http://http://forum.xda-developers.com/showthread.php?t=731989.
Once the odin one click is open, plug the usb cable into the pc, and then into the phone. This one-click has never failed me. Hope this helps.
Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?
Juiceboy125 said:
Ok, now it passed. I don't know what I did but now its back up and running. But now it boots up into recovery. I can't select anything because my phone's power button is broken. What do I do?
Click to expand...
Click to collapse
Depending on the CWM recovery you're in, you can sometimes use the search capacitive key to do the same thing as the power button will do.
I had the same problem you had with Odin stopping on flashing a file, turns out I was using a third party USB cable. I switched to the USB cable provided by Samsung when I bought my cappy and problem solved. Hope that helps.
Sent from my SGH-I897 using XDA
Finally!
Well, I got my Cappy up and running again. While I was stuck in the CWM I just decided to install Gingerbread using a One click and it worked. Now I'm back to CM9. Thanks guys for the suggestions. I guess I just needed to wait and double check everything.
Hello XDA forum,
My name is Brandon. I have used this forum for the last couple years and have found invaluable information, and for that, I thankyou guys!
I have searched everywhere I can think of to find someone that has been able to solve my problem. Hopefully you all can help.
I have a TMOBILE GS2 T989. I have had my phone randomly go into boot loop a few times before (even though I have never had anything besides stock ROM on this phone), and have always been able to fix it with Odin. This time, my phone decided to get stuck into the boot loop cycle, and I tried to use Odin like usual to fix it, and I get to the download section and it only stays in the' download mode for 2-3 seconds and boot loops again. The computer only recognizes the phone for a couple seconds and odin says "removed" and "failed" when i push start in odin. Im not sure why this is happening or how to fix it. All the research I have done has said that if I can get into download mode, the phone is only soft bricked, not hard bricked. But I cant get odin to work for me this time.
Any help is appreciated in advance!
Thanks,
Brandon
bump