Related
It seems no matter what I do, Odin gets stuck in the middle of flashing back to stock. Sometimes its at 20%, others its at 80 or 90%. It just stops and sits there (Ive let it sit for over 20 minutes in the same place). So I take out the battery and wait a minute and try it again. The next time it will stop in a different place and never finish.
What now?
Have you made sure your phone is in debug mode first, and that your sd card isn't mounted? This was happening to me when I rushed on flashing one night, and forgot to change it.
Well I cant boot the phone... and I have seen the solid yellow screen, and the solid blue screen now while trying to flash Odin.
There is no way for me to boot the phone and make sure if the phone is in debug mode.
Sorry, I'm not a developer or programmer, all I know is the dumb obvious stuff because I've messed it up a couple times myself. The only other dumb maybe not as obvious thing I can think of is trying another USB port on the computer, one directly off the motherboard. Sometimes USB hubs or alternate ports seem to have difficulty providing enough power for extended times during flashes.
Thanks guys. Somehow, it meraculiously just finally finished. I let it sit there at the 80% for over 30 minutes and then it finally just finished and rebooted.
Im scared to actually flash something else now lol
AdamNimrod said:
Thanks guys. Somehow, it meraculiously just finally finished. I let it sit there at the 80% for over 30 minutes and then it finally just finished and rebooted.
Im scared to actually flash something else now lol
Click to expand...
Click to collapse
I can understand, but if you do want to try something else some time, just skip the flash to stock. It's really not necessary and, as you can see, can be dangerous.
Hmm...I was having the same problem using one-click on my laptop (non-one-click Odin worked fine). I tried my desktop and it finished successfully on the first try (both computers are running Windows 7 64-bit with the same drivers and same USB cable).
I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.
so no one has any idea what i'm doing wrong? or has experienced similar problems?
Try to reinstall the drivers in kies.
If that don't work do download
Them from android development site.
It should work.
Try the phone in all mode you can to get the drivers to install right.
Then you can try to fix it with kies or odin.
**DamianGTO Steam kernel. 349MB Ram. 256HZ. ext2. js3 base**
Another approach
I too cannot get odin or kies (or usb mass storage) recognized on the PC. I tried for a long time and gave up.
Are you rooted or can you access the root dir? If not can you access the external SD card or market so that you can root?
Do you have clockwork mod or similar?
I can only base my experience never using odin or a pc...
If you can get into recovery mode and start using (if you do not have it already)clockworks mod (and/or steam recovery - which I highly recommend as it can access the removable sd card which is useful to load stuff on to when things go sideways see why in my post http://forum.xda-developers.com/showthread.php?t=929020 ).
Then you can flash whatever you want from the root directory or with steam from the external SD car (root dir there) no odin or pc required (directly).
Then I'd start with stock or at least a custom rom that is based on your carriers stock and go from there.
G
wastedkila said:
I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.
Click to expand...
Click to collapse
Hey!
I've had the EXACT same problem as you. did you try to put your phone into DOWNLOAD MODE (Close phone, then hold volume down, then home, then power) to see if it connects to odin? Also, before you do anything, make sure you turn on odin first and then select all the files you want. After thats done, then put your phone into download mode, then connect the phone to your computer thru the USB.
After much searching and work on fixing my bricked captivate, i broke down and bought a jig from mobiletechvideos.com. It works perfectly as intended, except for the fact that my pc is not recognizing the phone after it enters download mode. As a side note, i may have royally screwed up when i did something in clockwork recovery, where now i cant even get past the ATT World phone boot screen. Im afraid i may have deleted anything that can mount the phone to the pc. I have already installed the proper drivers, I think. Anything i can do to fix this?
So it shows the world phone screen a bunch of times? Plug it into an outlet see if the green battery comes up, just wait for it, the Gray battery will do a short of loop a few times... Once its at the green battery try to turn the phone on, be patient too, if you get the phone on, go to settings> privacy then factory data reset, make sure you backup to external or computer first
Your welcome
Now you say/press thanks
Teaching manners one person at a time
Thats not gonna work... nothing i know of can be done to it. it doesn't move past the att screen. No animation, not sound. Just ATT World Phone. i can get into download mode, but cant connect to computer. Thats the problem right there.
Try restarting your computer? I've had similar issues on a yucky iPhone, and I've read about other Captivate users with it as well, and a restart helped resolve the problem.
Go under your drivers and uninstall them and reinstall them it helped when I finally had got mine "back to his construction job" (lol download mode) it should then work
Sent from my SAMSUNG-SGH-I897 using XDA App
Ive already tried another PC and Uninstalling and reinstalling the drivers to no avail.
It just like the phone isn't even there. It will charge, but wont mount to the PC.
Not trying to insult your intelligence or anything (I might actually be insulting my own) but you have Odin open, right?
Just trying to think of anything lol
Yeah, but it wouldnt matter anyway if the computer doesnt know its there.
Try cleaning the mini usb port. Or switch the usb cord connector the samsung factory one tends to break the data + and -.
As for not getting past the at&t screen. The kernel you installed cannot read the system partition probably corrupted or the kernel you installed cannot read ext4.
If you cannot get it to be recognized send it back to your carrier for repair, should be under warranty.
Thats what im doing now. Thanks for the help, though.
Palen222 said:
After much searching and work on fixing my bricked captivate, i broke down and bought a jig from mobiletechvideos.com. It works perfectly as intended, except for the fact that my pc is not recognizing the phone after it enters download mode. As a side note, i may have royally screwed up when i did something in clockwork recovery, where now i cant even get past the ATT World phone boot screen. Im afraid i may have deleted anything that can mount the phone to the pc. I have already installed the proper drivers, I think. Anything i can do to fix this?
Click to expand...
Click to collapse
You sure you have the proper drivers installed for your phone? The links for them are on the odin forum in captivate development
Sent from my SAMSUNG-SGH-I897 using XDA App
Alright I am stuck. I've spent three days searching all the forums I can find, trying everything I find, and none of it has worked.
I was running the Decrap ROM on my phone no problem up until the OTA update started coming through. It failed the couple of times it tried to install. Then the Revolt ROM 1.0 came out. Made a backup, and flashed that one over the Decrap ROM, no problems. Revolt 1.1 is released, I flashed back to stock, then flashed 1.1 over it. It was running fine for a few days, except for two FC on the phone. Then I got a call from my girlfriend, tried to answer it, and the phone FC but was still ringing. I tried opening the dialer to call back, and it kept force closing. I rebooted the phone, and my real problems started.
The phone now goes through this process...Vibrate > LG splash screen > blank screen > Vibrate > LG splash screen > blank > repeat.
The only way to make it stop is taking the battery out. Every time I plug it into the wall or computer (with or without a battery) the process starts automatically. I cannot get into any sort of recovery no matter how long I hold the volume and power keys. I tried taking the battery out, SIM card, and SD card. I plugged it into the wall with and without a battery, let it charge overnight, no luck. I tried the SDK method with fast boot but I cannot get my computer to recognize the device because it keeps trying to restart itself.
The only thing I have not tried is the LGNPST method because I read of problems people were having even after recovering their phone, and I figured that if the SDK method would not work because my computer did not recognize the device neither would this.
Does anyone have any other suggestions? Or am I going to have to bite the bullet and pay for a replacement?
Thanks!
Sent you a pm
Sent from my VS910 4G using XDA Premium App
I have not had the exact problem you do, I can get the phone to charge. But I have also had repeated problems with not being able to boot my Revolution. This has happened consistently no matter which ROM I've used. I've factory reset and tried Decrap and Revolt both. I can reboot my phone fine, but if I ever turn it off overnight, I go back to a blank screen after boot in the morning.
It seems a number of non-root users have this problem. You might be able to go in for a replacement, see:
https://www.youtube.com/watch?v=IOGM__SQB6Y
I'm not sure if having a low battery contributes to the problem, but I do know that Clockwork works better with a full battery.
Have you tried plugging it in without the SIM and SD card?
Charging without Battery
http://forum.xda-developers.com/showthread.php?t=1211935&highlight=can't+boot+to+clockwork
Well, this morning, I ended up in exactly your positions, despite having a full battery.
I tried the suggestion of plugging the phone in without the battery and letting the bottom lights flash on and off about five times. Then I put the battery back in and it booted to the charger.
still can't get to Clockwork though, if you find a solution, please post.
Update: I ended up getting back to Clockwork. Can't say exactly what did it, but what seemed to work was:
1. Charging the battery fully overnight
2. Removing the battery and holding the power button down for 30 seconds
3. Leaving the battery out for some time, about an hour I guess
4. With the battery still removed, plugging the phone in and allowing the bottom lights to flash about 10 times
5. Replacing the battery, holding down the power button and volume down.
After a full day of not being able to get into Clockwork, I was able to get in and do a factory reset.
Returning Revolution to Verizon
FYI, I took my rooted, non bootable phone into a Verizon store, and they ordered a replacement. Didn't try anything special and they didn't ask about or look for rooting on the phone.
I am having a similar but not identical problem. After trying to downgrade with LGNPST, my phone just sits at the initial LG logo. Well, it comes up, then blinks and vibrates and then comes back. It will sit there forever. I have been unable to get the hard reset menu to come up.
The phone is detected under Windows, but it tries to install a new device driver "LGE CDMA USB MODEM" for which I do not have drivers for. It does not show up as a device in LGNPST.
Any ideas?
nesterbation said:
I am having a similar but not identical problem. After trying to downgrade with LGNPST, my phone just sits at the initial LG logo. Well, it comes up, then blinks and vibrates and then comes back. It will sit there forever. I have been unable to get the hard reset menu to come up.
The phone is detected under Windows, but it tries to install a new device driver "LGE CDMA USB MODEM" for which I do not have drivers for. It does not show up as a device in LGNPST.
Any ideas?
Click to expand...
Click to collapse
Try pulling battery, put battery back in, press and hold volume up, press and hold power button, hold both thru the lg screen. Hopefully it will boot into a download mode that is recognized in lgnpst.
Sent from my VS910 4G using xda premium
Didn't seem to do anything different. Still prompting for those USB modem drivers.
nesterbation said:
Didn't seem to do anything different. Still prompting for those USB modem drivers.
Click to expand...
Click to collapse
You are downgrading correct? If so the drivers you downloaded from the downgrade instructions delete those. Go to LGs website download those drivers and then retry again. That's what I did yesterday when it wouldn't recognize my phone in the program. Let me know if it works.
I've Revolted have you?
When this happened to me I contacted Verizon about the issue. Apparently I was not the first person this had happened to. I found on a couple of other forums that non root users had the same problem. Sounds like it may be an issue with the phone in general.
Sent from my VS910 4G using xda premium
Hello,
I haven't used my Cappy in a few weeks since I upgraded to the Infuse, so I decided I would let someone use it instead of letting it waste away in my desk. I had a MIUI Rom loaded when I was using it, but it was outdated and I wanted to clear out everything so I went to load the newest rom, but my power button wasnt working to wake up the screen. I thought this was a software issue because nothing physical had happened to the phone as far as I know. I was able to get it loaded through Rom Manager, but it was still having issues. I tried loading a different kernal thinking that might help, but it didnt.
I decided to cut my losses, go back to stock and see what I can do with warranty since its a relatively recently replaced phone. After dealing with getting drivers loaded on my Win7x64 machine which I never had any issues with before, I tried using ODINs 1click, but it would reboot my phone and just go through the normal boot process. I tried again, same results. Tried the "hold volume buttons and plug in usb cable" method that has worked in the past to get into download mode, but it would just reboot and reboot until I let go and then sit at the battery charging screen. It went into revocery one time, but since my power button doesnt work, there wasnt anything I could do. I tried several methods of getting into download mode, nothing worked.
Im headed to Radio Shack to pick up whats needed to make a jig, but I dont have high hopes of that working out. I am able to boot the phone and it works, at least until the screen timesout. Will a jig work or is something else wrong with it?
Thanks
adamofthestoffels said:
Hello,
I haven't used my Cappy in a few weeks since I upgraded to the Infuse, so I decided I would let someone use it instead of letting it waste away in my desk. I had a MIUI Rom loaded when I was using it, but it was outdated and I wanted to clear out everything so I went to load the newest rom, but my power button wasnt working to wake up the screen. I thought this was a software issue because nothing physical had happened to the phone as far as I know. I was able to get it loaded through Rom Manager, but it was still having issues. I tried loading a different kernal thinking that might help, but it didnt.
I decided to cut my losses, go back to stock and see what I can do with warranty since its a relatively recently replaced phone. After dealing with getting drivers loaded on my Win7x64 machine which I never had any issues with before, I tried using ODINs 1click, but it would reboot my phone and just go through the normal boot process. I tried again, same results. Tried the "hold volume buttons and plug in usb cable" method that has worked in the past to get into download mode, but it would just reboot and reboot until I let go and then sit at the battery charging screen. It went into revocery one time, but since my power button doesnt work, there wasnt anything I could do. I tried several methods of getting into download mode, nothing worked.
Im headed to Radio Shack to pick up whats needed to make a jig, but I dont have high hopes of that working out. I am able to boot the phone and it works, at least until the screen timesout. Will a jig work or is something else wrong with it?
Thanks
Click to expand...
Click to collapse
dont think taht the software is the issue..but still cant be sure as teh phone is not in my hand..
so anyways u r gettin the stuff to make the jig..so after taht flash any new gb rom with gb bootloaders..and still ur power button doesnt work then its hardware issue for sure..
but thats a small issue...if u know how to open the phone..then open the phone and check the connector soldering near the power button..
but if u cant do that by urself..then give it to a pro.and u r done..shdnt cost u much
You have to drop the battery out and replace it in order to use the 3 buttons on some builds, especially earlier builds.