I don't know if this goes into the Q&A or just the Dream forum, so I'm gonna try here in Q&A.
This is about my friend's G1 phone which I've looked at and can't figure out what is wrong with it.
Here is the issue, after not a specified amount of time the screen on his G1 will turn off, and it doesn't shut off regular, this is at times the system is in use, and when the screen shuts off, it's slow and you can see the pixels fade away. When this happens the phone is still active, I was in the recovery menu's terminal and was able to type reboot while the screen was off.
Which then speaking of recovery, it happens no matter what mode the phone is in. The only way to get the screen back on is to take out the battery or do the reset combination, but sometimes the screen doesn't turn back on when the phone starts up, it's random.
It's not a corrupted memory card, I've tried it with mine and without one.
It's not the signals like other threads mention, tried it in different areas and as mentioned it happens in the different phone modes (normal, recovery, spl)
I've even tried re-flashing everything (Radio, Recovery, SPL, ROM) when the screen would stay on for those few seconds or minutes, but nothing fixes it.
The Radio that it has is the newest version required by Haykuro's SPL. Recovery is cyanogen's 1.3.1 recovery. It has everything that my phone has on it. The ROM he was using was JF's 1.51, so I tried the one I'm using, JustAnotherCrowd's JACHero 2.63.
When plugged in to my computer, ADB doesn't even recognize the device plugged in. Which there is nothing wrong with my computer or ADB because I use it all the time with my phone.
USB mounting works on that phone though.
Another thing is that when booting up and if the screen actually turns on, the G1 logo which is that first screen to appear doesn't on his phone, it's just blank during then until the actual ROM's loading screen comes up.
Related
Hi All
I have been trying to root my G1. I downgraded it to RC29.
Then, it started behaving very weird.
When I boot up, I cant do anything from the home screen. Even if I try to open the app drawer, it immediately closes it. I cant open the dialer. I cant even go to another home screen. It immediately comes to the default one. I cant even power it off. I can only pull the battery off. But in that case, when I try starting it again, it goes into the screen with triangle and exclamatory mark. When this happens, there is nothing much I can do. So, I just leave it for a long time like a day. Then, if I try starting it, it boots, but again same problem as before.
I tried reflashing the ROM many times, but no use. After the reflashing, it has same problem again.
Try flashing a different rom. Sounds like you have a very unstable rom.
I have used the one cyanogen suggests in his instructions. It is the DREAMIMG.nbh and downloaded from android-dls.com
I have downloaded it couple of times and reflashed. So, its not that the file got corrupted during download.
Do you have suggestions about any other ROM?
Now, I think it is not a problem with the ROM
It is as if the Home button is stuck. That is why, it always comes back to home screen, and boots up into recovery since home+power is recovery mode.
Once in a while it randomly goes into the recent apps window confirming that it is a home button issue.
Any work around?
Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD
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.
[Q] Bricked? Stuck on either white AT&T screen or grey, frozen battery screen, no USB
While trying to install Cognition v2.2b3 via Clockworkmod (from stock at&t 2.1 froyo) something happened mid-install and my phone ended up rebooting, and I have not been able to turn it on since.
-When attempting to power on normally, phone shows white AT&T screen and hangs there
-When attaching USB, phone shows battery screen but battery is all grey and rotating progress icon is frozen. Does not appear to be charging.
-Computer does not recognize phone in any state. Latest USB drivers are installed and I have had no issues connecting via USB previously.
-Cannot get into download or recovery mode using any volume/power button combination or through adb. Also tried attaching USB with ODIN running while attempting button combinations, inserting/removing battery etc, still nothing.
Has anyone else experienced this? Anything else I should try?
Louros said:
While trying to install Cognition v2.2b3 via Clockworkmod (from stock at&t 2.1 froyo) something happened mid-install and my phone ended up rebooting, and I have not been able to turn it on since.
-When attempting to power on normally, phone shows white AT&T screen and hangs there
-When attaching USB, phone shows battery screen but battery is all grey and rotating progress icon is frozen. Does not appear to be charging.
-Computer does not recognize phone in any state. Latest USB drivers are installed and I have had no issues connecting via USB previously.
-Cannot get into download or recovery mode using any volume/power button combination or through adb. Also tried attaching USB with ODIN running while attempting button combinations, inserting/removing battery etc, still nothing.
Has anyone else experienced this? Anything else I should try?
Click to expand...
Click to collapse
Go into Download mode, hold both volume buttons down and plug your phone into USB. If it doesn't work than pull the battery and try again.
If that doesn't work keep trying until it does. I'm serious, it took me like 40 tries last night to flash stock with the 1 click and then finally get cognition running (that only took one flash)
Odin is a piece of crap, it works maybe every 10th time for me. I've never used the rom manager to install roms, always use clockwork recovery. Less to go wrong if your in recovery mode I suppose.
But literally just keep trying until it works o.0
Hi. I've experienced exactly the same this night. Try this: forum.xda-developers.com/showthread.php?t=775911 it helped instantaneously.
BTW, you really need to wait at least 10 secs after removing battery.
I have the exact same problem.
My battery screen shows up with nothing but a flash loading icon and a grey battery. When I simply turn my phone on its stuck in ATT boot screen. I tried the instructions many times trying to get into download mode but right when i put it in the battery while holding down up/down/power it simply just shows the "frozen battery charging" screen again.
HELPP
My phone has be working fine until it ran out of battery and now doesn't boot properly. I have fully charged the battery overnight but it still not functioning. It appears to boot, vibrates several times in a sequence(buzz---------------------buz-buzz-buzz). Sometimes it repeats this in a loop. I get the login screen briefly and can unlock, but the apps are frozen, or will open then screen goes black and I can't turn on the display. The nav buttons stay lighted. I've removed the battery several times but same result. Sometimes when I hold down the display button I get the
I rooted the phone weeks ago and running stock froyo -- no other changes and no recent changes so this doesn't make any sense other than a hardware failure.. possibly the internal SD. Any suggestions are appreciated.
Something like that happened to my friend's vibrant. His phone was completely stock - no root, no custom rom. One day it just decided to start going in to boot loops for no apparent reason. Battery pulls didn't help. He tried doing a factory reset from recovery and ended up in even worse shape.. The phone would boot into some debug screen and just die there. We figured it was probably some hardware problem, took it back to T-mo and got a replacement.
All of the buzzing was different things force closing, I would flash back to stock. And see if it still does it. Also this is not development related so I will move it over the Q&A
I was able to disable gps when the phone had a brief moment of clarity. Once I did that it stopped having spasms, so possibly a bad gps??
Did a factory reset and the phone is back to normal