Database Develop

Boot-loop or bricked G1?

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?

[Q] stuck at "dual core" but now can't even fastboot?!

I bought one of the refurb'd bionic's a couple months ago. I've rooted and masked the wifi tether, but nothing else, no custom ROMs or anything. phone's been working great for the past seveal weeks since those changes were made, several reboots, etc. no problems until last weekend.
I randomly found my phone stuck on the "dual core" screen one morning. it must have rebooted overnight and been that way for several hours as it was quite hot. I did a battery pull and tried to turn it back on, got nothing. plug it in to the charger, nothing, no leds, nothing. several battery pulls later, still nothing. try to enter fastboot/bootloader by pressing power + volume up/done, nothing. plug it into the computer, nothing.
I'm sorta fearing its been hard bricked (though I have no idea why... i wasn't loading ROMs), except, the other day, after leaving the battery out all night, I was able to get it to turn on, it booted up to the home screen, but before it was usable, rebooted and was stuck on "dual core" again. messing with it some more, I eventually got to the bootloader screen. I wish I had siezed that moment, but i didn't. Messed with it some more yesterday, saw the 'dual core' screen again, but couldn't get it into fastboot. its very hit or miss and I can't do it consistantly, but on rare occasion, it does seem to want to come back to life.
any advice on what happened? where to go from here? and if it can get it back into fastboot? I'm hoping i can and rsdlite will recognize it and I'll try loading 902 fxz back on it, but sure could use some advice to save this phone... no insurance and it was a refurb thats been rooted, I don't think verizon will be too much help.
THanks
-Rob

Try this
Little known hidden key (actually button) sequence: press and hold both volume up & down then hold the power button ten seconds (five should work, but ten always gets it). You should boot into fastboot mode, then flash 902 using a USB cable. You do NOT need to delete data! Check the batch file and REM out or remove any line that says it will. Worst case, Motofail after that will give you access to your latest CWM backup, assuming you have one, just restore that once you have root.

What he said and also you may need to charge your battery.
Sent from my DROID BIONIC using Tapatalk 2

It could just be a dying phone, I came across an Atrix basically in the same situation. The radio in it had died, so the only way to boot the phone was to skip booting the radio, but if you hit the phone application it would crash the phone.

[Q] [HELP] Something is SERIOUSLY wrong with my Moto G(boot loop)

So. My Moto G is completely un modded, not rooted, and is exactly stock how I bought it and haven't changed any of the software. My Moto G has been getting slower in the past couple of months with everything going slower than usual. I bought my phone in February 2014.
Yesterday while I was at school, in my pocket I had my phone. I felt random vibrations in timed cycles. So I pulled out my phone and had a lol at it randomly rebooted but came back to the home screen. As I started to use it just to send a couple of messages it rebooted again but this time after the reboot animations they just went on and on, what I've found out to be called a boot loop.
So I went home did some research and figured I would have to factory reset. I couldn't get into the phone therefore I had to do it externally. I got the the menu thing ( I think it's called fast boot menu ) and I wanted to select newer bootup or power up just to see if that would possibly stop the boot loop. I selected it and got into my phone, into setting and factory erased my phone.
Well I factory erased my phone and re installed the apps I on,y essentially use or NEED such a social media, within this time there was no unusual activity. Shortly after my phone randomly rebooted ( after downloading the apps ) and turned off, and then went in to the former boot loop! I was furious!
Well here I am, left it overnight for charge and it's been looping for 10 hours. I tried going back into the fast boot menu, the first time I got into it this morning I selected recovery in hope to reset it, however the screen said no command with the android and the exclamation point. The second time I got into the menu I tried 'Factory' and it just rebooted and back into the cycle.
At one point I did get into my phone however shortly after that guess what happened, it turned off and rebooted. And back into the vicious cycle.
I am led to believe it's the power button that's causing the problem ( correct me if I am wrong ) as when I did manage to get I to the phone I did try pressing the power button to investigate this and on some occasions in did lock the phone but in several others it displayed the power off popup and then turned off shortly after indicating that I was holding the button down which I definitely wasn't doing.
So where would I go from this? Do I call Motorola, try flashing a stock ROM ( it's completely stock ATM , I don't know how to do this so if I have to do this can you please explain briefly ) or try going back into the fast boot and go into recovery and try and get rid of no command ( if I can, and how ? ).
Please any help would be very appreciated!
Thanks in advance.
PS you don't think it's the back cover that's doing it because it took that off last night '

kevlarpatel said:
Do I call Motorola, try flashing a stock ROM
Click to expand...
Click to collapse
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.

doppelhelix said:
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.
Click to expand...
Click to collapse
Hi, I had a look online and came across a forum post saying it was a jammed or sticky power button and the poster stated to hit the power button side of the phone on a desk a couple times and it will go back to normal. I'm glad to say it did work after I hit it a couple times, as fast as ever now due to the reset!
I was wondering if I call Motorola would they give me a free new moto g out of it, as I see it as an opportunity to do so, or will they just prompt me to send it so they can repair it under warranty? Is it worth calling ?

[Q] ATT Moto X 2014 Freezing Constantly

Hello all,
I got this phone about a month and a half ago, and since I got it I've noticed a lot of freezing and crashing (more so after the 5.1 update).
Some examples:
-I try unlocking the phone from active display and the screen goes black. The only way to get out of it is to hold the power button to restart.
-Sometimes the phone freezes on the lock screen randomly, and when I pick up the phone to look at it, the time is wrong and I can't physically unlock the phone, only turn the screen on and off, leading to me having to hold the power button down to shut off and restart.
-When on some apps, like twitter for example, the phone freezes, and I cannot do anything except turn off the screen by pressing the power button. When I try waking the phone, it stays black or sometimes theres a flash of the screen I was on before, and then it goes black again. Only thing I can do here is hold the power button down until "Power Off" shows up on the screen, and I press that to shut the phone off.
Today I cleared the cache, and since then the phone has froze once, causing me to do a hard reset. What should I try next? Any idea what the problem could be?
Thank you for the help.

I have pretty much the exact same thing going on. It started last night... I first noticed I had some charging issues where the phone wasn't charging very quickly after the battery died (after a day of heavy use). I let it sit for awhile, then it booted up, and it showed the motorola splash screen. It gets all the way to the lock screen, although I'm unable to unlock the phone. The screen goes dark. It appears to still be getting texts and the like- although this screen blackness issue makes it so I can't unlock the phone. The one thing I can do is hold down the power button and turn it off. I've tried loading fastboot and doing a factory reset, although nothing appears to happen and it boots the same way. The other thing about it is that it appears to be running hot- way hot. Any ideas? I'm running stock rom, Verizon network, just updated to 5.1 when it came out last week.

Boot loop on initial flash screen

On rooted ZV6. I was using the phone as usual. I went to open an app (Weather Channel, though I don't believe that matters) and the phone froze. It did the self-restart, however it sits at the very first LG flash screen, turns off for a second, then starts again. Continual boot loop.
I've popped the battery, tried a different battery, tried with the SD in and out, all with the same results. I tried holding down volume down and power, it gives me the booting into recovery screen, then goes back into the boot loop.
I've seen the talk about the ZV9 OTA, but there was no sign of an update in progress when the system crapped out initially.
If I'm reading the code under the back cover right, the phone was made back in May, which makes me worry that it's the known faulty hardware issue. Does anyone have any ideas I can try before going through the hell of riding Sprint for a replacement? I would be forever in your debt for something to save my phone. Thanks in advance for any advice.
EDIT: After screwing around with holding down volume buttons at random times, it will sometimes get to the Sprint Spark animation, but no boot sound, then as I was typing this edit, it magically booted proper, and powered down, and is boot looping again. What the hell.