Related
Hey all!
About a month ago I rooted my G1 for the 1st time via the 'one-click' recovery flasher method. I successfully rooted my G1 with the CyanogenMod 3.6.8.1 stable build, and then also successfully updated to 4.0.2 via the Cyanogen Updater. However, after about a week or so I made the fatal error of holding a glass of water and my G1 together and the inevitable happened... my beloved G1 in said glass of water! It was only about 80% in and only for a few seconds, and when I quickly took off the back cover etc it really didn't seem too soaked, water was in there but not a lot. It visibly seems fine (water hasn't got to the screen etc). After drying the best I could, I tried turning it on again, and managed just about to get it fully loaded before failing. Since then I think it basically goes into a boot loop: It goes on the G1 logo then after about 30 seconds a quick vibrate and again into the G1 logo (and repeat to infinity). I know there are certain things to try such as pressing home & power, or cam button & power etc but I don't think these work because as soon as I put my battery (and spare I've tried) into the phone it immediately powers on. This isn't normal is it? Surely you should have to press the power button? So because I don't have to press power to turn it on, I don't think these safe mode type boots work (I've even tried for example, holding down the home button then putting the battery in). I don't know if I am in a simple boot loop related to a rooting error, or if my mobile is simply knackered due to the water exposure!? It's been a couple of weeks now since the accident and I'm stumped
Any help, or suggestions would be gratefully appreciated!
cosmos
iamthecosmos said:
Hey all!
About a month ago I rooted my G1 for the 1st time via the 'one-click' recovery flasher method. I successfully rooted my G1 with the CyanogenMod 3.6.8.1 stable build, and then also successfully updated to 4.0.2 via the Cyanogen Updater. However, after about a week or so I made the fatal error of holding a glass of water and my G1 together and the inevitable happened... my beloved G1 in said glass of water! It was only about 80% in and only for a few seconds, and when I quickly took off the back cover etc it really didn't seem too soaked, water was in there but not a lot. It visibly seems fine (water hasn't got to the screen etc). After drying the best I could, I tried turning it on again, and managed just about to get it fully loaded before failing. Since then I think it basically goes into a boot loop: It goes on the G1 logo then after about 30 seconds a quick vibrate and again into the G1 logo (and repeat to infinity). I know there are certain things to try such as pressing home & power, or cam button & power etc but I don't think these work because as soon as I put my battery (and spare I've tried) into the phone it immediately powers on. This isn't normal is it? Surely you should have to press the power button? So because I don't have to press power to turn it on, I don't think these safe mode type boots work (I've even tried for example, holding down the home button then putting the battery in). I don't know if I am in a simple boot loop related to a rooting error, or if my mobile is simply knackered due to the water exposure!? It's been a couple of weeks now since the accident and I'm stumped
Any help, or suggestions would be gratefully appreciated!
cosmos
Click to expand...
Click to collapse
You might have tried to turn the phone on too soon. You should have let it dry out for 24 or 48 hours before turning it on. Then there are methods of putting the phone in a bowl of rice to dry it out and others. But you said that holding cam and power or home and power don't do anything right?
I forgot that my phone was plugged into my PC with the sd card mounted. I checked for update and it found one and started the download. The download just sat there at 0%. I realized my usb was connected and unmounted it (thinking that the update somehow was waiting for the SD card). No change, so I clicked Cancel on the upload screen. I then tried Check for Update and again and it said "no firmware". I rebooted and tried again. Still same message. I then tried "Resume update" instead of "Check for update". It said it found an update and would reboot the phone in 5 seconds. The phone then rebooted and it started to apply the update. This seemed very wrong to me because the updated certainly didn't have time to download. The update failed and it said it was rebooting my phone. The phone went off and now I can't get it to start back up. I press the power and get nothing. I pulled the battery and sim card. Still nothing. Any ideas?
Yikes, that's a sticky situation you've got yourself into. From reading around the forums it seems that the update was bricking phones anyway; however, from what you described it seems like that isn't your case. If you can't power on your phone, then there isn't a way to head back to stock or fix the update, that I know about. You might think about calling Samsung or AT&T and saying you tried applying the update, but now your phone won't power on.
richb500 said:
I forgot that my phone was plugged into my PC with the sd card mounted. I checked for update and it found one and started the download. The download just sat there at 0%. I realized my usb was connected and unmounted it (thinking that the update somehow was waiting for the SD card). No change, so I clicked Cancel on the upload screen. I then tried Check for Update and again and it said "no firmware". I rebooted and tried again. Still same message. I then tried "Resume update" instead of "Check for update". It said it found an update and would reboot the phone in 5 seconds. The phone then rebooted and it started to apply the update. This seemed very wrong to me because the updated certainly didn't have time to download. The update failed and it said it was rebooting my phone. The phone went off and now I can't get it to start back up. I press the power and get nothing. I pulled the battery and sim card. Still nothing. Any ideas?
Click to expand...
Click to collapse
try holding both volume keys and power button until you see something then release power.
If you bought your phone from an AT&T store and you have one close to you, I would take it in and show it to them. They replaced mine on the spot, took me less than 5 minutes.
ThisWasATriumph said:
try holding both volume keys and power button until you see something then release power.
Click to expand...
Click to collapse
I already tried that. I held them for 1 min. It just doesnt turn on. The battery was about 75%, so I know it's not dead.
hollowayXDA said:
If you bought your phone from an AT&T store and you have one close to you, I would take it in and show it to them. They replaced mine on the spot, took me less than 5 minutes.
Click to expand...
Click to collapse
I bought it from Best Buy. Also, it has been more than 30 day. I'm not even sure who to bring it to.
richb500 said:
I bought it from Best Buy. Also, it has been more than 30 day. I'm not even sure who to bring it to.
Click to expand...
Click to collapse
Check and see if there's a warranty center in your area. AT&T has one on the south side of Baltimore. You walk in, they test it real quick and if they can't fix it, they give you a new phone. Much quicker than exchanging it by mail if there's one close to you.
richb500 said:
I already tried that. I held them for 1 min. It just doesnt turn on. The battery was about 75%, so I know it's not dead.
Click to expand...
Click to collapse
Have you tried holding both vol up/down while plugging in usb to get into download mode?
hold the + and - volume buttons and plug the usb back in, if you get to download mode your not quite dead yet
must type faster next time......
PRS_Player said:
Have you tried holding both vol up/down while plugging in usb to get into download mode?
Click to expand...
Click to collapse
Yup. Nothing. Screen stays black. No sign of life.
Damn I was really close to messing mine up too then from the sound of it. I noticed my phone downloading some kind of update today too, well I immediately hit cancel, not knowing what it would do and wanting to come do some research here before accepting it. When I went back, I also hit Resume Update and it gave me the same "no firmware" error, then I hit check for update and it gave me an error message that said "You have not waited 24 hours since the last time you checked for an update, please wait 23...."
Guess I wont be trying to update tomorrow afterall
I had the same problem, but my phone completely downloaded the update. Couldn't power it on at all even if I pushed the + - volume button with power button. Took it to ATT and told them that it happened when I applied the update, and since I was over my 30 day update, they called some ATT replacement hotline and they are sending me one today.
ditto on a dead phone because of OTA my wifes not mine(glad it was hers)
stock captivate update stopped at 87% then went black, no power at all, not even the volume +- way
called att 2 day air on a replacement of course its a refurb but better than no phone at all....
oven
Well i am going to sound like nutcase but have you tried putting into the oven? I am being 100% serious. Look over in the i9000 forums and i think there were some people that were bricked beyond recognition and they did some crazyness such as putting it in the oven at 350 untill it was hot to the touch but not melting and it got their phones into download......just a thought and no i am not lying it worked for them!!!!
Best of luck guys
Remove the battery and put it again, without turning the phone on, press volume up + volume down, and then plug it to the USB connected to your computer.
JorgeC said:
Remove the battery and put it again, without turning the phone on, press volume up + volume down, and then plug it to the USB connected to your computer.
Click to expand...
Click to collapse
That didn't work either. I will receive a replacement phone tomorrow. I hate getting a refurb. My phone is in perfect condition. I hope the replacement one is too.
Here's something that I did discover. I don't think the phone is actually dead. I think it's stuck in some kind of loop, making it completely unresponsive. I had it sitting in my dest drawer today for several hours. When I took it out it was pretty warm - as if was clocking some pretty serious cpu or network traffic. Either way, it's a brick, but I think it a living brick, not a dead brick. In case you're wondering, my office was like a refridgerator today, so it wasn't from the warm room.
richb500 said:
That didn't work either. I will receive a replacement phone tomorrow. I hate getting a refurb. My phone is in perfect condition. I hope the replacement one is too.
Here's something that I did discover. I don't think the phone is actually dead. I think it's stuck in some kind of loop, making it completely unresponsive. I had it sitting in my dest drawer today for several hours. When I took it out it was pretty warm - as if was clocking some pretty serious cpu or network traffic. Either way, it's a brick, but I think it a living brick, not a dead brick. In case you're wondering, my office was like a refridgerator today, so it wasn't from the warm room.
Click to expand...
Click to collapse
I have received several refurbs over the years and all the phone appear to be brand new. I already exchanged my Captivate one. Not a scratch on them. Even though they say they are refurbs the device appears to be new product. You will not have a problem.
i got mine bricked too, it was perfectly fine before the update... it stopped at 50% and then it said update failed, phone rebooted, and then it never open its eyes again, its DEAD... omg, good job att! morons giving us wrong software...
richb500 said:
Yup. Nothing. Screen stays black. No sign of life.
Click to expand...
Click to collapse
I've had the same issue but I was able to fix it. Unfortunately, I don't remember the exact steps, you will have to try for a few times until you make it work.
When your phone is "dead":
1. Take out SIM+SD cards (keep your battery in)
2. USB connect to your PC
3. Start Odin3
4. VolUp+Power and wait until a few red colored lines will show up (if not then try for a few times until they show up), you should see something like this:
RST_STAT =0x1
PMIC_IRQ =0x3c
..... and so on.
5. When you see the red lines press VolUp+VolDown+Power
6. The red lines will go off/on in a few seconds but you keep holding VolUp+VolDown+Power
7. When red lines will go off for a second time just release Power, you should get back to download mode
8. Use Odin3 to re-flash
Good luck!
ice3186 said:
Well i am going to sound like nutcase but have you tried putting into the oven? I am being 100% serious. Look over in the i9000 forums and i think there were some people that were bricked beyond recognition and they did some crazyness such as putting it in the oven at 350 untill it was hot to the touch but not melting and it got their phones into download......just a thought and no i am not lying it worked for them!!!!
Best of luck guys
Click to expand...
Click to collapse
This sounds as crazy as out gets.
Well for some reason, I pulled out my phone, and my power key stopped working. I have had this happen before. What I did was use odin one click ji6 to flash back to stock 2.2. (I have a 1012 build so i didnt want to talk to risk of bricking.) I was on cyanogenmod when this last occured, but now I'm on legend 4 kk4, corn kernal v7.0A. The real problem is that the OS, Bootloader, or something thinks the power key is being held down, and so i cannot get into download mode without using ADB. I am scared that if i brick the phone, i wont be able to get into download mode. Also, i went to an amusement park a few days ago, and i went on a water ride, and my phone got a little wet, not too much, and the stickers for water marks are still white, but i do not have warranty. I am not sure if the key is broken, or if it is the OS. Also, when i put my battery in, it auto-reboots. So i cannot turn my phone off without removing the battery. Also, i cannot flash because my computer is at home. Any suggestions?
well i found out it was a hardware issue so i need to go get it fixed, but im not sure, it works, but it is like loose, it sometimes works, sometimes doesnt. anybody have any idea before i send it in?
I have the same problem, what I do is turn on volume rocker wake. To get into recovery I either use Rom manager, or hold the combo to get into recovery when you reinsert the battery into the phone. You have to hold it until the boot loader screen shows for the second time. Once in recovery, either search back or home will be used to select options, depending on the kennel. I read some where that if you take apart the phone and clean where the button makes contact it will fix it, but if I were you I would send it in
EDIT: just found this http://forum.xda-developers.com/showthread.php?t=1529320 it should help
Sent from my SGH-I897 using XDA
ya it isnt auto-rebooting, so I know its the plastic part of the key that is working. I actually tried volume rocker wake, and it didnt work out that well for me. I am actually on stock, ji6. I went to the att store and they told me to go get it fixed locally, so thats what im going to do. thanks for replying though
My friend dropped his Galaxy S in the toilet a few months ago. Gross and lol.
It now hangs on boot at the Galaxy S logo splash screen (see photo below).
It is possible to get the phone into download mode, using the 3 button combo. From there, today I flashed it using Odin (with Gingerbread) - although Odin reported that the phone flashed OK, it made no difference and still won't boot past the splash screen.
As you can see from the photo the screen seems to have a perminant red tinge.
Any suggestions guys? Thanks in advance.
UPDATE: After taking it apart, and putting it back together, the red screen problem is gone. But, it still won't boot past the first screen.
Hi,
the EXACT same thing happened to me last sunday. I grabbed the phone immediately from the water (eww), took out the battery, the SIM and the SD-card. Then i opened the phone (hard), and let it dry in some rice for three hours. The rice absorbs the liquid. after that i put it back together. Tried to start it, but it wouldn't boot. So i put the charger on it, then it did boot. Some glitches when touching the icons and sliding the screens, but it worked! The next day i telephoned my wife, she wasn't home, so i hung up. Then the phone hung. I rebooted it, and it became terribly slow (it took about 15 minutes to get to the Samsung boot animation). I turned it off again, and after that it wouldn't boot past the start-up screen anymore, just like your friends'. Also, the screen did not turn off anymore. So i gave up, turned it off, and started setting my mind on a new phone. It was late, so I went to sleep. I turned it on the next day just to see, and it booted again! It has been working fine eversince. So maybe your friend could try to take out the SIM, and SD-card, and turn off the phone for a while. You never know.
Good luck anyway!
J.
Thanks jkruijff. Its been a couple of months so I think its as dry as its going to get already.
My fathers HTC one keeps suddenly shutdding down in middle of boot! It suddenly happened and it is completely stock. I tried getting to recovery but it turna off a few seconds after!
It happened before but suddenly fixed for no reason!
kamranhaghighi said:
My fathers HTC one keeps suddenly shutdding down in middle of boot! It suddenly happened and it is completely stock. I tried getting to recovery but it turna off a few seconds after!
It happened before but suddenly fixed for no reason!
Click to expand...
Click to collapse
If it is completely stock, it seems to be a hardware problem. Either mainboard or a fault in power circuit. You should consider returning it for repair.
jotha said:
If it is completely stock, it seems to be a hardware problem. Either mainboard or a fault in power circuit. You should consider returning it for repair.
Click to expand...
Click to collapse
thanks for answers, after a little playing with it i don't have any idea how but it got to safe mod and was running ok, and when i rebooted it got stuck again, no idea how again it booted ok! this happened before but after a few seconds buttons blinked and a pop out said press and hold home button to restart and a count down for 3 seconds!
I guess the problem was with volume key/power button that got stuck !? because when i got into recovery and was fast enough to pres volume down the power button random ally worked ! after googling i got to phone but flashing bright light into sensors and covering it ! this is ridicules but worked few times and phone boots fine to OS with sensor covered! it turned off again after some time but i turned it on again with covering light sensor again and hasn't acted weird yet ! (my father also dropped hes phone and volume button place is damage a little)
this is the weirdest thing that ever happened to me why is it acting like that? he's phone is out of warranty so he can't do anything anyway!
kamranhaghighi said:
thanks for answers, after a little playing with it i don't have any idea how but it got to safe mod and was running ok, and when i rebooted it got stuck again, no idea how again it booted ok! this happened before but after a few seconds buttons blinked and a pop out said press and hold home button to restart and a count down for 3 seconds!
I guess the problem was with volume key/power button that got stuck !? because when i got into recovery and was fast enough to pres volume down the power button random ally worked ! after googling i got to phone but flashing bright light into sensors and covering it ! this is ridicules but worked few times and phone boots fine to OS with sensor covered! it turned off again after some time but i turned it on again with covering light sensor again and hasn't acted weird yet ! (my father also dropped hes phone and volume button place is damage a little)
this is the weirdest thing that ever happened to me why is it acting like that? he's phone is out of warranty so he can't do anything anyway!
Click to expand...
Click to collapse
As I said, it probably is defective. After the mentioned drop, something might be broken. The only way out will be repair service, warranty or not...
jotha said:
As I said, it probably is defective. After the mentioned drop, something might be broken. The only way out will be repair service, warranty or not...
Click to expand...
Click to collapse
ok thanks ! I guess i will try to revive it same way because i can't repair it here! I will see what revived it the next time
jotha said:
As I said, it probably is defective. After the mentioned drop, something might be broken. The only way out will be repair service, warranty or not...
Click to expand...
Click to collapse
It was just the power button its ok for now!