My brothers phone was dropped (apparently hes a bit clumsy!) Whenever he was texting using the keyboard, it was making some very strange characters on the screen, whenever he would push 1 key, several would appear, etc.
't' ='d 's03' etc... stuff like that.. obviously thought a reboot would fix the issue. So when we rebooted the phone, it turned out that it couldnt get past the g1 screen and was stuck at the Triangle with the yellow exclamation point. Pushing ALT+L showed the recovery screen. We went through the appropriate options and held down back + home for 25+ secs to get it to reboot. It rebooted fine and worked for an hour or so, until the Voice Search just kept popping up as if he was asking it to, so we tried to reboot the phone again and do the recovery thing, this time it wouldn't get past the recovery after holding down home + back. I can't push back + home either to get it to restart, so I'm thinking the home key may be broken or stuck.
Any thoughts on this issue or has anyone else experience such? He'll more than likely be sending it in today since its still under warranty and has NOT been rooted.
Thanks!
same thing happened to my first g1..its a hardware issue send it in
Was hoping it wasn't a hardware thing, but so be it. Thanks for the heads up.
Related
I got a G1 from t-mobile and it was giving me problems. I had done a warrenty exchange and the new one they gave me was randomly typing numbers and letters by itself. for example 5u4i33333333333333 ect. I thought by trying to achieve hero rom that it would maybe fix the problem. Now I have trouble even getting the phone started because when i press the power button it blinks a white screen from the bootloader with the android guy on the skateboard. It just blinks even when i hold it. I got it once to get into recovery mode and when i try to go into bootloader. it wont load the rc29 file. Please if anyone has any ideas what i could do to get it back to the original g1 software. that would be great. thanks.
I have been running CM6 on my G1 for a while with no major issues. However, this morning when I woke up, the phone was not turning on. The screen comes up with the bootloader white screen and keeps turning off. I had installed Advanced Task Killer the previous night and I suspected that it must have done something to the system. So I decided to reinstall everything from scratch, starting from DREAIMG.nbh.
My G1 looked to me as the T-Mobile UK version, so i used the RC7 DREAIMG.nbh. It flashed okay and booted fine. And when the Google account setup screen showed up, I tried to type my account details but very strangely I could only type the letters e d f x only. All others keys don't show up or do anything. I booted many times but the keyboard doesn't work at all, except those four keys.
I then wanted to flash RC29 thinking that I flashed the wrong version earlier. But now when I press Camera + Power, nothing happens. So I cant go to the bootloader screen. It just boots normally to the setup screen. I can however get the recovery screen when I press Home + Power but then because the keyboard's Alt or W is not working, I cant do a wipe either.
I also checked if it is talking to ADB, but ADB does not see the G1 either in recovery screen or after it has booted up normally.
I have been reading all day all over this forum, as well as others but did not find any similar problem or a way forward. Can anyone suggest how to get it back to normal. I don't think its totally bricked because it boots up normally and it can also go into recovery mode.
I have a weird issue that just started a few days back. I was on rooted 1.1 when the "Do you want to shut-down?" window would randomly pop up. If I did nothing, the unit would completely power off. If I hit the power button quick enough, the screen would shut off (putting it into standby) and the unit would not power off. I could then press the power button, swipe to unlock, and continue where I was.
I thought maybe it was related to me modifying the db to disable the auto-update from 1.1 to 1.2. However, I updated to 1.2 yesterday evening and rooted it as well. Unfortunately, the "Do you want to shutdown?" window started popping up again all by itself.
It's almost as though the unit thinks the power button is being pressed (and held). I tried squeezing the case around the edges, wiggling the power button, cleaning the screen, etc. There doesn't appear to be any particular reason why this is happening. I'm going to try wiping the device and flashing 1.2 again, unrooted, and see if the issue persists.
Does this sound like a hardware issue that requires replacement?
Restore your nook to stock and go to B&N and get your nook exchanged.
It definitely seems like a hardware fault.
I had the same problem with my first NC. I would be reading, doing whatever and the screen would blur and shutdown menu would appear. If I did nothing (and even if I hit cancel) it would shutdown as if the power button was just being held.
I had used the autonooter with 1.1 at the time, though I believe it was pure coincidence since the problem persisted after completely restoring to stock. My advice would also be to restore to stock and exchange it.
I consider myself lucky because I tried multiple times to restore to stock but would get interrupted since I had this problem even on boot. It was common for the device to interrupt boot so many times (>8 times) because the power button would get "stuck" that it would attempt to reflash. The button never felt physically stuck though.
I finally reverted to stock successfully, took it to B&N, showed a manager, during which the NC failed to boot, shutdown automatically, etc. and I had it exchanged no problem.
2nd NC works great though.
Thanks for the input - I will restore to stock tonight and take it in tonight or tomorrow.
I called one store - their "guru" isn't in until Tuesday.
I called another nearby store and the guy on the phone sounded irritated, brushed it off as a registration issue, and finally made it very plain that they will simply mail it off to the repair center if I bring it in...
After going back to stock 1.2 without root, the power-off message issue mysteriously disappeared. I've used it for 2 days now and have yet to see the message pop up.
Is it possible that it's software-related??
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 ?
Hello forum,
I try not to post on forum for help unless I run out of options. I used to encounter loops before and managed to fix them but this one is really weird. So a bit of background : I was running stock ROM + TWRP recovery and everything seemed normal till one day when I encountered my first loop after opening up newly installed app ( although I don't think it relevant to this case ). But anyway, when I opened it, phone restarted itself immediately and kept doing it (didn't get pass the logo) for around 5 minutes when finally booted into the OS. After that everything seemed fine for...about a month when the same loops started to happen more and more often. They usually happen when phone has it screen turned off and I press power button to wake it up, it then gives me 3 seconds as If I would hold the power button and volume down button prompting me that it's about to restart itself. So I thought, that there has to be some junk apps that are fighting with each other causing these loops and I went for the recovery. But (stupid me) instead of wiping only the apps I got rid of the whole ROM with recovery ( ). So this time I flashed a custom ROM (ViperOne+9.0.0-fix) using ADB (adb push etc etc) and TWRP thinking that maybe the previous ROM was the issue. (I forgot to mention that even when there was no OS on the phone it was still looping.) After a while when the loops stopped, I got into the recovery and flashed ViperOne with no problems at all. Phone booted itself into the OS, everything seemed normal to the point where I left it for couple of minutes, pressed power button and it went into to eternal loop where it only stopped when the battery was drained. It was literally loopin the whole night (couldn't sleep). Now when I connect it to charge it doesn't go into charging but goes straight into the loop. I can get as far as the bootloader and selecting to go to recovery and after I press power button to select it, it goes into the loop. NOW..this might sound like there is a hardware issue (the power button) but I highly doubt it. Ill appreciate any kind of solutions. :silly: Thanks in advance.
// edit v 1.0
If I didnt make any sense here's video :
https://youtu.be/DhVFApSE3kg