Related
So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.
akashastrega said:
So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.
Click to expand...
Click to collapse
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.
peter petrelli said:
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.
Click to expand...
Click to collapse
I had at least 80 percent battery. I cannot get into the tri-color screen. Tried holding camera and soft reset, tried comm, camera, power, tried talking sweet to it...it just goes to splash screen each time. HELP!!!
This is a G3 wiza200 IPL/SPL 2.26 and it IS unlocked.
Thanks in advance
If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.
peter petrelli said:
If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.
Click to expand...
Click to collapse
Yeah, I know...in theory it SHOULD, it's not, hence the freaking out. I am attempting to charge it on the main plug, but it begins to charge then dies. I did have a loose usb port, which I thought got fixed, as my phone charged fine last night, and sync'd fine today. I'm not a pro, but not a noob either...so I am getting frustrated because trying the things I do know, aren't producing the results they should.
**The splash screen is one I made, independent of an OS...after any rom change, I flash my custom splash screen...it has always worked...however, it is making me think that it is the ONLY thing on the MDA, and any signs of a rom were somehow killed by my kids flashing the phone with a very incomplete kitchen rom.**
I will try again. Any help that can be offered would be MUCH appreciated.
PS---I LOVE Heroes!!
When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.
peter petrelli said:
When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.
Click to expand...
Click to collapse
I can get brief and random orange lights (my phone was not 100% but at least 80% when I first began)...it takes a lot of sweet talking though to get it to connect to charge. I tried a backup battery as well. Pushing the camera and soft reset either produces my custom splash, or nothing at all (no boot whatsoever). I am truly stumped.
EDIT
I am not aware of the SD card method. I do have an SD, but if I need a special program, I do not have it.
The fact that no light remains on when you connect usb or mains plug makes me think that the usb socket is loose again. In which case I'm doubtful that you can flash via bootloader mode.
The fact that you cant get into bootoader mode suggests that it was somehow corrupted when the flashing process was interrupted. This could be unrecoverable.
From here I'd suggest you investigate the sd card method. I've never relied on this method so this is uncharted territory for both of us.
Read this thread here and here. I think we're running out of options...
Semi success, I got into the quad colored boot (white bottom)...but cannot get it to recognize the usb. I am getting an error message about an unrecognized device, so I will try to fix active sync first...any suggestions for me now that I am at least in a bootloader screen
thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.
peter petrelli said:
thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.
Click to expand...
Click to collapse
it shows usb in the corner, however it is not producing any charging light, nor does my pc recognize the usb. So...I don't know if this will matter, but as I said...I have the RGB + white bootscreen with usb in the corner...is there still a chance????
yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck
peter petrelli said:
yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck
Click to expand...
Click to collapse
wcescomm.exe is NOT showing in Task Mgr...I will try to flash anyway. I killed the firewall and the sd had been removed already. Any other suggestions??
EDIT
ruu error 260 update error
It cannot connect, please check to make sure it is cradled blah blah blah
Thats ok. I forgot that the previous flashing attempts would have killed it off anyway.
So I get ruu error 260
I have rebooted my pc, deleted any connections in active sync (leaving only guest)...
UgggH
It is NOT recognizing the usb
the usb port is as tight today as it was last night after my hubby repaired it...I'm backed to stumped
EDIT**
I had to reboot MDA, now I have lost the little corner usb...but I still have the quad bootscreen
This is progress at least, 1 hour ago we didnt even have bootloader mode. Perhaps you could try flashing another rom, but I think if error 260 keeps appearing then something is wrong with the USB socket.
somehow i lost bootloader again...
this is driving me insane!!!
am trying again, will update momentarily.
************EDIT*****************
Finally got it back into bootloader, but it will not read the usb. keep getting that stupid error message that it doesn't recognize the device, and if I try to flash it with a stock rom, I get error 260.
I have closed the wcescomm.exe
I have killed my firewall
I have rebooted my phone, my pc...everything a few times
I have deleted any connections in active sync
I have unticked allow usb in active sync
WHAT AM I MISSING???
The usb port on the phone does not feel loose again...could it have got fried somehow? I feel as if I can get the damned usb to be recognized, I can save my precious MDA.
Please...any other suggestions, brainstorms, whatever???
THANK YOU
I had a little problem with theloons kitchen doing the same thing to me last week where it would give me the 260 error. I'll upload a ROM flashing file for you to try. Probably the best thing to do right now would be to take the nk.nbf file from an official ROM and stick it in this file and then run the RUU in it. After that you should be ok again to try your luck at cooking with theloons kitchen again although you may want to wait 'til the kids are at school or something before you try it.
When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck
mestrini said:
When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck
Click to expand...
Click to collapse
absolutely right while in bootloader mode it wont charge,but to charge or verify status of usb connectivity,while in bootloader mode push power off button,it'll go in sleep mode but lights will show charging if usb cable is charging
usb cable might be charging but mini usb port of the phone has many connectors I think 9 connectors,I'm not sure,may be the connector for making connectivity relation with phone and pc is damaged.
try with another usb cable if possible,if the connectivity with usb is established than method in the link provided by 'mestrini' is a good option,good luck
Hey everyone, First time poster here and it seems my captivate is bricked. I'm fairly new to android but I caught on with ROM/kernel/etc.. flashing and all seemed to be going well. I saw the new 3.5 update for precision and wanted to update from 3.0. I did my usual thing and restored to stock with ODIN instead of flashing over. Rooted all over again, downloaded ROM manager and flashed clockwork recovery. I selected the ROM when I was in CWrecovery and rebooted.. but for some reason the phone never gets past the boot screen. The ATT logo shows up, then the suckerpunch logo (as suckerpunch is included in the precision ROM) and then the precision logo.. but it just keeps starting over from there. I thought I did a clean flash but something went wrong obviously.
Ive tried the three button combo and anything that has been stated before on here about the three button combo timing and whatever. So it seems that I cant get in recovery or download by using the traditional methods.
I'm guessing my phone is soft-bricked, which should be relatively easy to fix, but I can't get into any mode at all. Ive seen plenty of threads with people having boot loop issues but they seem to have been solved my some combination of buttons used or the ODIN usb download mode technique. Ive seen mention of using adb commands to get into download mode, but I think I have to have usb debugging enabled which I can't enable, clearly.
Any help would be appreciated, especially since in the meantime I'll have to use my old 903sh.
CCDillon said:
Hey everyone, First time poster here and it seems my captivate is bricked. I'm fairly new to android but I caught on with ROM/kernel/etc.. flashing and all seemed to be going well. I saw the new 3.5 update for precision and wanted to update from 3.0. I did my usual thing and restored to stock with ODIN instead of flashing over. Rooted all over again, downloaded ROM manager and flashed clockwork recovery. I selected the ROM when I was in CWrecovery and rebooted.. but for some reason the phone never gets past the boot screen. The ATT logo shows up, then the suckerpunch logo (as suckerpunch is included in the precision ROM) and then the precision logo.. but it just keeps starting over from there. I thought I did a clean flash but something went wrong obviously.
Ive tried the three button combo and anything that has been stated before on here about the three button combo timing and whatever. So it seems that I cant get in recovery or download by using the traditional methods.
I'm guessing my phone is soft-bricked, which should be relatively easy to fix, but I can't get into any mode at all. Ive seen plenty of threads with people having boot loop issues but they seem to have been solved my some combination of buttons used or the ODIN usb download mode technique. Ive seen mention of using adb commands to get into download mode, but I think I have to have usb debugging enabled which I can't enable, clearly.
Any help would be appreciated, especially since in the meantime I'll have to use my old 903sh.
Click to expand...
Click to collapse
Can you describe exactly which three button methods have you performed? The one that always seems to work to get to download mode is hold both volume up and down and plug in USB cable to the computer and you should be able to get into download mode (of course after taking out the battery, shutting off your phone first). You should have ODIN open before this, then after that just press start on ODIN.
I believe people with captivates who have problems with 3 button combos have batch 1008. Please tell if you can't use the method above then we can check your batch.
koreancanuck said:
Can you describe exactly which three button methods have you performed? The one that always seems to work to get to download mode is hold both volume up and down and plug in USB cable to the computer and you should be able to get into download mode (of course after taking out the battery, shutting off your phone first). You should have ODIN open before this, then after that just press start on ODIN.
I believe people with captivates who have problems with 3 button combos have batch 1008. Please tell if you can't use the method above then we can check your batch.
Click to expand...
Click to collapse
I appreciate the fast response.
Ive tried the above method and it didn't work. Ive also tried plenty of others like holding the power button with the two volume buttons (to try recovery) Ive also held the buttons down for certain amounts of time to see if my timing is just off, and pretty much a few other generic three button combos that are performed when this sort of thing happens. Instead of getting into download mode, it of course just shows the battery charging.
If the phone is plugged in while it is doing its rebooting cycle then ODIN actually detects it, but I still wouldn't be able to do anything I'm sure.
Ive read through many posts about this but I just cant find anything to work at all, maybe buying a jig would be the final solution. :/
EDIT: If it helps, before flashing my captivate for the very first time a month back, i was told to check to see if I could enter into download mode and recovery safely, which I could and this was on stock rom. Ive been able to get into download/recovery with other ROMs as well, idk what's up now though
CCDillon said:
I appreciate the fast response.
Ive tried the above method and it didn't work. Ive also tried plenty of others like holding the power button with the two volume buttons (to try recovery) Ive also held the buttons down for certain amounts of time to see if my timing is just off, and pretty much a few other generic three button combos that are performed when this sort of thing happens. Instead of getting into download mode, it of course just shows the battery charging.
If the phone is plugged in while it is doing its rebooting cycle then ODIN actually detects it, but I still wouldn't be able to do anything I'm sure.
Ive read through many posts about this but I just cant find anything to work at all, maybe buying a jig would be the final solution. :/
EDIT: If it helps, before flashing my captivate for the very first time a month back, i was told to check to see if I could enter into download mode and recovery safely, which I could and this was on stock rom. Ive been able to get into download/recovery with other ROMs as well, idk what's up now though
Click to expand...
Click to collapse
If you could get into download before, I don't know why you wouldn't be able to do it now. The fact that you can see the battery charging icon indicates that you should easily be able to get into download mode. Can you double check your methods and if neither work, you could always go for JIG.
you may need to buy this to get into download mode:
http://cgi.ebay.com/ws/eBayISAPI.dl...69977&ssPageName=STRK:MESELX:IT#ht_623wt_1139
just to clearify and add one more thing to try...
you are experiencing a boot-loop not brick..
ive heard of boot loop problems sometimes getting into download mode by:
remove battery
plug in usb
hold volume buttons
put in battery
(slight change on usual method)
EDIT: you may also want to try the AIO captivate toolbox in the Dev section, it can try to put your phone into download mode
I had this happen before. I did what Tresselo said and it worked.
Sent from my SAMSUNG-SGH-I897 using XDA App
plug in your usb cable. let the phone reboot and see if the comp recognizes the phone at any point during your boot loop. if it does - your in luck, sort of... I had this problem as well with the same ROM. idk if its the ROM or just me screwing up (probably me screwing up) anyhow, type this command into a command prompt (must have the android sdk and adb installed) get into the tools folder where ever that may be at for me its C:\android\tools
from this dir type this: adb reboot download - do this as soon as the comp recognizes your phone - should work.... IF the comp is seeing the phone. If its not you WILL need a JIG which can be made fairly easy.
Try adb if you haven't already. Instructions are in the stickies in the Dev section.
Sent from my Captivate using XDA App
Thanks for all the replies guys, got a good community here. Sadly no suggestions have worked at all.
jgc121 said:
plug in your usb cable. let the phone reboot and see if the comp recognizes the phone at any point during your boot loop. if it does - your in luck, sort of... I had this problem as well with the same ROM. idk if its the ROM or just me screwing up (probably me screwing up) anyhow, type this command into a command prompt (must have the android sdk and adb installed) get into the tools folder where ever that may be at for me its C:\android\tools
from this dir type this: adb reboot download - do this as soon as the comp recognizes your phone - should work.... IF the comp is seeing the phone. If its not you WILL need a JIG which can be made fairly easy.
Click to expand...
Click to collapse
I downloaded the android SDK and installed all the necessary components, as soon as I hit the right directory (for me C:\Program Files\Android\android-sdk-windows\platform-tools>adb reboot download) and I get "error: device not found". So adb seems to be running right and I may just have to get my timing right, but as of trying a good ten times I'm not having any luck.
When booting up my cap while plugged into the computer, the noise that signals a usb connection sounds and when going into device manager and looking at usb connections, its says samsung android device. Seems like I could get into download, but I guess I'll just keep trying to time it exactly right even though Ive hit the command near the connection noise every time.
I'm not losing hope, but I went ahead and ordered the jig off of ebay that mengbo posted, I'm really hoping that the jig could solve my problem for good. From your perspective guys, would the jig DEFINITELY work? Or is it just a kinda one shot, hope for the best thing?
The JIG is a pretty sure thing seeing as how you are just in a boot loop.
CCDillon, Im in the same boat as you. Same thing happened to me. I have tried a jig and it did not work for me. Hopefully it works for you. I have tried ADB also and it could not find the device. I really hope there is something out there that can help us.
aw man, that's not good at all.. hope you can find a way. Did you make a jig and were you using the same ROM?
Hopefully its just mine and the jig works for you. I didnt mean to scare you. I made a jig at first, and it kept booting the phone. Thought I didnt make it correctly so I got one off of ebay, thinking it had to work. That one did the same thing. Thought maybe it was a faulty jig and the guy I got it from ('mengbo' on this forum) sent me another one to see if that was it. The new jig he sent (that worked on his phone) did the same thing. So, something else is going on.
I was going from Phoenix 4.5 to Supernova ROM and it gave me the same error you got. Now it Boots the ATT screen then loops the Phoenix ROM logo over and over. 1 vibrate followed by 2 more
I'm hoping the JIG works for mine, otherwise I'm not sure what to do. I admit it does scare me a bit to see that you've tried all these different things with no result. I was scanning the precision thread and it seems one of the avid users/posters got caught in a boot loop and it looks like they have gotten out of it, I sent a PM so maybe I can see what that user did, though part of me is thinking that the three button method worked for him but for some reason not for me. This is very frustrating and I'll keep an update on everything, the JIG should be here in about 3 days or so.
Also, you think it may have something to do with how many times our phones have been flashed? Ive looked up to see if flashing is bad for the phones "health" but it seems flashing won't really hurt anything, nor have I really flashed too much. Btw, my phone acts the same you described as well, with the random vibrating and everything.
My mind just seems to be jumping to any random possibility, it just sucks not having a working phone.
Hope SOMETHING works for you
Seriously - you guys are all worked up over a boot loop. the JIG will put you into dl mode just fine... only time it has high chance of NOT working is if you only see black screen - no power up at all.... you can make a JIG by getting 3 - 100k ohm resistors and a 1k ohm resistor from radio shack for about $1.25... its simple.
I removed my 3 button combo accidentally by flashing att 1 click, theres an att 1 click with 3 button fix, flash that when you can get into download mode.
If you can connect with adb use it to go to download, if not, you need a jig... it works, I have been down your path!
jgc121 said:
Seriously - you guys are all worked up over a boot loop. the JIG will put you into dl mode just fine... only time it has high chance of NOT working is if you only see black screen - no power up at all.... you can make a JIG by getting 3 - 100k ohm resistors and a 1k ohm resistor from radio shack for about $1.25... its simple.
Click to expand...
Click to collapse
+1. Learn how to make the JIG you need HERE...
Or buy one from me HERE... < Shameless plug.
I was in the same situation as you guys after i had a bad flash and the loop on the bootanimation. I bought a jig online and it worked. The trick is to take out your microsd, and simcard and leave out the battery for 15 seconds. Then put back ONLY the battery in, and plug in the jig. It should turn back on and be put into download mode then flash with one click odin.
odin one click WITH 3 button fix....... saftey first.
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.
I've got an 896 Rogers Captivate that has been draining my sanity for hours now.
I managed to get it to download mode exactly ONCE out of ... literally eight hours of hold buttons, remove battery, replace battery, hold buttons, remove battery, etc etc.
I reached download mode by using the three button technique Volume Up + Volume Down + Power.
Once there I idiotically said "I can get here again.." and removed the battery.
I got this phone from a family member and managed to get it to download mode, but every other time I hold buttons (any buttons) it does exactly this:
If plugged into the computer it shows the loading daisy (which doesn't animate). I can hold any combination of the volume buttons and power button and it will flash black and return to the daisy.
If not plugged in, it shows the model number and 'Samsung'. Behavior is the same. Holding volume up, or down and the power button will flash black after eight seconds and then show the model and 'Samsung'.
I haven't tried Odin (although I've downloaded it and a rom thusly), a Jig, or any of the other brute force approaches to reaching download mode simply because I know that if I reached there once, I should be able to reach there again. Computers aren't sentient (although I swear this phone enjoys tormenting me).
Does any body have any insight to why I would be going through this?
Why won't it reach download mode again?
Just fyi: I have literally tried every button combination I can suss from the countless threads I've scoured and scanned.
Thanks in advance for any insight anyone can provide.
Just to make sure, as I didn't see it in the post, you did do v+/v- and insert the usb cord from a powered off state, right?
Also, check the captivate connection issues thread in my signature if you haven't already.
Different reaction
Hey thank you! Your list is handy!
I'm shocked I hadn't stumbled upon it already, or your signature for that matter..
Seriously can't understand how this is the first time I've seen it.
I've tried the [FROM A POWERED-DOWN STATE - BATTERY REMOVED] procedures but none of them got me into download mode.
Thanks all the same.
I'll try the battery charging list next.
Quick (and possibly stupid) question : Does it matter if it's an official Samsung USB cable?
As I noted in my initial post, I managed to get into download mode earlier today (little Android digging my grave with the same cable I've been struggling with for the past six hours.
Luck!
omigodomigodomigodomigodomigodomigod
okay, so I managed to get into d/l mode by plugging to power (outlet usb) and then applying three buttons.
So:
Battery Out
Plugged into USB
Battery In
Hold VolUp+VolDown+Power
Android man digging my grave showed up.
It should be noted that this same process was conducted several times against my PC upon which the technique worked several hours (and several hundred attempts, and half a season of StarTrek TNG) ago.
...now what (lol!)
I guess I'll fire up Kies and conduct a few more hours of scouring!
well you COULD go about flashing roms and kernels and modems to your hearts delight. But I would advise against that. I'd recommend first backing up EVERYTHING. Especially your /efs (you'll need to be rooted) folder if your considering flashing a rom. Once you do that you're free to flash. Just be sure to read the OP of the rom to make sure you meet the requirements for the rom or kernel, such as if you have the right boot loaders. As long as you read, you really can't go wrong with the captivate.
Sent from my SGH-I897 using XDA App
I'm not entirely sure how the phone reached this state but according to all the stuff I've read, if the phone is in this state it's recoverable using Kies.
However Kies doesn't seem to care that I've got this phone plugged in.
Frankly, there's nothing to back up, and if flashing out with Odin is the only way to establish a working Captivate then I suppose i've got some files to download.
Does anybody have any insight regarding Kies and getting it to play nice nice?
Do you have Samsung drivers installed?
Personally, I have only got Kies to work when the phone was actually on.
Sent from my SGH-I897 using XDA App
If your in download mode, I suggest just flashing back to stock using heimdal.
(I don't use odin 1-click stocks because my first attempt at using it corrupted my bootloaders. My phone would power on, go through the AT&T screen for hours. I also could not enter recovery or download using 6 different methods including a jig. I lost hope and accidentally left my phone on when I went to bed. I wake up next morning and it booted up. I used terminal emulator from the market and used the command Reboot Download. I worked, then I flashed back to stock using hiemdal. I am not completely sure why I shared this story but w.e )