G1 Semi-Rebooting on its own !!! - G1 Q&A, Help & Troubleshooting

Hi,
I have JF 1.51 and its been running pretty well for a long time now. untill today when I was on the phone and it suddenly semi--rebooted, what I mean by that is it didnt go all the way back to the T-Mobile G1 screen, but only to the android screen and it doesnt stay their for a long time only for a couple of seconds and then the phone is operational again !! it only takes about 10-15 sec. from Android screen to fully operational with a network signal !
Happened three times already, and I havent installed any new apps that could have made this !
My only guess is overheating? I checked the bat. temp. the first time and it was around 42 C so i thought it could have overheated since I was charging and talking at the same time. But then the second time I was at 32 C when it started rebooting, but it was also charging.
So Any ideas ?

Weees said:
Hi,
I have JF 1.51 and its been running pretty well for a long time now. untill today when I was on the phone and it suddenly semi--rebooted, what I mean by that is it didnt go all the way back to the T-Mobile G1 screen, but only to the android screen and it doesnt stay their for a long time only for a couple of seconds and then the phone is operational again !! it only takes about 10-15 sec. from Android screen to fully operational with a network signal !
Happened three times already, and I havent installed any new apps that could have made this !
My only guess is overheating? I checked the bat. temp. the first time and it was around 42 C so i thought it could have overheated since I was charging and talking at the same time. But then the second time I was at 32 C when it started rebooting, but it was also charging.
So Any ideas ?
Click to expand...
Click to collapse
Sounds like a Kernal oops. Wipe and re-flash, you should be fine.

Ouch!! Cummon man.....their gotta be something else I can do besides a wipe!!
I just wiped and reflashed about a week ago because my SD got corrupted, and doing it all over again now......is really a pain in the ass

format your sd card then wipe and reflash. It should not corrupt your sd card. I suggest flashing the cyanogen recovery image 1.3.1 because it will make your life 10x simpler...
Good luck

format your sd card then wipe and reflash. It should not corrupt your sd card. I suggest flashing the cyanogen recovery image 1.3.1 because it will make your life 10x simpler...
Good luck

Thanx guys for the replies.......im reflashing now, the situation got out of hand the rebooting started happening more and more untill the phone got unusable. it reboots eveyr min now. So yea I got no other option.
Thanx again, and yea im trying with the Cyanogen image.

Related

phone shuts off!!! help..

Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on. I don't know if it is Cyanogen or some sort of app, as I download apps quiet frequently. I am going to go through my apps now and also reinstall Cyanogen 3.4 tonight and leave my phone on all night. I guess I will have to see in the morning..
Anyways, can someone help
I ve fot sometimes the same issue with dudes cupcake which use th cygnonen kernel...
I ll be glad to have a fix
Are you overclocking the processor? That might contribute to it shutting down.
I do overclock but why do i have to 'battery pull' to make it reboot?
Yes, same issue here.
Uhh, again...
Powered up, set to standby, waited 1 min, shut down.
EDIT: I'm on Rogers Cyanigenized.
Same issue here. Complete lockup with screen off, have to pull battery to boot again. Seems to happen every 6-12 hours for me.
My Phone:
Cyanogen 3.4
radio 2.22.19.26I
Haykuro's SPL
Kernel 2.6.27.24-cm by [email protected] )
NOT overclocked, and no clocking tools even installed. Persists after several clean wipe and reflash also.
This thread's timing is great... I was just about to reset back to rc29 and build back up. Thought I was going to have to replace my phone
Rastasia said:
I do overclock but why do i have to 'battery pull' to make it reboot?
Click to expand...
Click to collapse
This question should probably be in the Dream section and will probably get locked/moved but Pulling the battery reset the "overclock" until it boots back up. This would be why pulling the battery helps.
hey you don't havbe to pull battery just push end call start call and menu all at once it will reboot you phone
Ok, thanks to Jakob, we know, that android freezes, is doesn't shut down.
I now tested with and without overclock, it made no matter to me not to overclock, there's no difference.
But I experienced it didn't happen when it's connected to a charger..
mysterious..
This keeps hapening to me, first it was happening in Cyanogized Rogers rom, then in The Dudes 1.3 b 12, I'm flashing JAC1.62 right now, this never happened to me before I got my class 6 16gb and started using apps2sd
Just curious, does this happen to anyone without a2sd
i'm having the same problem
seems to happen in the builds using the Cyanogen kernel. I'm sure this issue will iron itself out in future releases so just sit tight.
I too am having the problem on the Cyanogen 3.4 build. Its definately a change in 3.4 as I didn't have this problem in any of the 3.3 betas. I'm doing Apps2SD as well.
One thing I have noticed as well is that networking has been acting flakier than normal.
I had this issue on the pre-cupcake radio but not as frequent, so maybe it's just an amplified version of the same problem? There was a thread about it before but I'm too lazy to search for it.
The hangs was the only reason I moved to virtududes rogers rom v3
I'm going to try and get this sorted out tomorrow. For some reason the OOM killer kicks in sometimes and kills a critical process like zygote.
atleast you don't have this problem!
I've reflashed,wiped,formatted and apps2sd2 or sdpsplit, so many times already... trying different ways for each. But same thing always happens... my memory card gets damaged then wiped all by itself.
Uninstall toggle Setting and use Reparing Ext partition with Cyonagen recovery seems to fix this issue
So happy I found this thread! I'm using Google Ion and having this issue since yesterday. So annoying. Anyone got a fix?
I`m having the same problem, the phone freeze, looks like is a hardware problem, i`m on CRC1
I have started to have this issue as well. I am currently running Cyan4.1.999. It happened yesterday while on a call, after a call, and also while the phone was on charge.
Solutions?

Help G1 is crashing constantly

Hi, I recently flashed my phone to cyanogens 3.6.8.1 all was well until yesterday when the phone screen displayed vertical lines like a grey color, the phone could receive calls but from t mobile customer service and it was booting up tho I couldn't see the screen. Then I took the sim card out and the screen returned to normal but was stuck in the splash screen. I reflashed and sometime the next day it happened again, this time I took out the sim card and it went back to normal
Any ideas
Jonnibravo said:
Hi, I recently flashed my phone to cyanogens 3.6.8.1 all was well until yesterday when the phone screen displayed vertical lines like a grey color, the phone could receive calls but from t mobile customer service and it was booting up tho I couldn't see the screen. Then I took the sim card out and the screen returned to normal but was stuck in the splash screen. I reflashed and sometime the next day it happened again, this time I took out the sim card and it went back to normal
Any ideas
Click to expand...
Click to collapse
Could you post a log of this? Could you also provide some more details about your set-up (a2sd? swap? comcache? spl/recovery?) and how did you get to this point (did you wipe before flash? did you run any back-up apps, what were you doing when it happened?)
Once we have that info we should be able to figure it out.
I started out with th jesus freak rom then I decieded to flash the cyanogens 3.6.8.1, I had trouble with the market because I hadn't wiped first, I did that and all was well for at least 5 days. I created an ext2 partition for apps2sd but I'm not sure if that worked. Then on the Saturday 6 days later I put fotmob on my phone so I could keep an eye on the opening premiership season put the phone in my pocket whilst at the football and 2 hours later the phone screen was dead, nobody could call me tho I know the phone was operating and booting only t mobile manage to get through, I tried a reboot, then took the sim card out and the screen went back to normal but was stuck on the splash screen. I tried fixing file ext but came as error asomething about the super block being unreadable tried manually but didn't work, tried backup still stuck, reflashed worked fine for. 20 hours then it happened again this time I wasn't doing anything with the phone no programs other than the usual running in the background, this time I removed the sim card and the phone went back to normal again for about 4 hours then it happened again this time removing the sim didn't work.straight away but eventually it came good again.
Its now 11 15 and its running fine again. I have noticed that I now only have one ringtone (dream theme) and one notification tone and I'm getting a few force closes tho I not sure what they are I will report them if and when I see them
you need to get audio resources and unzip to the sd card all the ringers. search xda for audio resources
The screen went dead again at 3pm this time after removing the sim card it stayed the same it was only after leaving the battery off it returned to normal again about 10 minutes later, I am also getting a vending core force close from time to time, please someone help me solve this issue.
P.s I've never actually seen the phone do this it happens when it is in my pocket when I get it out it happens also this time I have not installed any software and it is still happening
Jonnibravo said:
The screen went dead again at 3pm this time after removing the sim card it stayed the same it was only after leaving the battery off it returned to normal again about 10 minutes later, I am also getting a vending core force close from time to time, please someone help me solve this issue.
P.s I've never actually seen the phone do this it happens when it is in my pocket when I get it out it happens also this time I have not installed any software and it is still happening
Click to expand...
Click to collapse
Because you lost your ringtones, it sounds like your SD card is acting funny, I would format it using this guide (make only 2 partitions for the time being, fat32 and ext3).
See if that works...May be complete reflash with wipe wouldn't be a bad idea neither.
That's all I can suggest at this point, I'll need to see a log to be anymore specific, but try this out, sounds like you've got nothing to loose
Good luck.
Thanks for your reply I am very greatful, I have tried a different sd card without setting up partitions and it still happens. I think the latter is true and a complete reflash is definately the thing to do.
I think this may be a hardware issue because as I mentioned it only happens when it has been in my pocket for a while, perhaps it is overheating or something.
I'll try a complete reflash and let you know if it happens again.
Wipe, re-flash, reformat your sd (or take it out altogether, just to rule it out see what happens... This is all I can tell you....
good luck

Xperia constantly resetting...

Hey all,
I posted a while ago about my phone having died and only having red flashing lights...I managed to solve that- thanks for you help, but now have a completely different problem.
Since then about a week has passed and approximately every 36 hours the phone seems to crash. When I take out the battery and turn it on again it invariably hangs at the Ericsson logo screen. When I then leave it off for a period of time (between 2 and 12 hours) I either find it starts to work again, or that I'll have the red flashing lights and have to leave it for longer.
When it does start working, it always seem to have been hard reset and I have to go through the set up again.
It's possible heating the battery speeds up how long it takes to start working again (although I've tried it with 2 batteries so I'm not sure why that would work) - and I'm not sure if that is actually the case yet or not anyway.
- It's very frustrating to lose all of my contacts daily, but I don't want to give up on £250 worth of kit... any ideas?
Thanks so much
welbis said:
Hey all,
I posted a while ago about my phone having died and only having red flashing lights...I managed to solve that- thanks for you help, but now have a completely different problem.
Since then about a week has passed and approximately every 36 hours the phone seems to crash. When I take out the battery and turn it on again it invariably hangs at the Ericsson logo screen. When I then leave it off for a period of time (between 2 and 12 hours) I either find it starts to work again, or that I'll have the red flashing lights and have to leave it for longer.
When it does start working, it always seem to have been hard reset and I have to go through the set up again.
It's possible heating the battery speeds up how long it takes to start working again (although I've tried it with 2 batteries so I'm not sure why that would work) - and I'm not sure if that is actually the case yet or not anyway.
- It's very frustrating to lose all of my contacts daily, but I don't want to give up on £250 worth of kit... any ideas?
Thanks so much
Click to expand...
Click to collapse
LOL,
no idea why.
Installed any tweaking software??
Sadly no - and I've tried it with 2 different roms too
welbis said:
Sadly no - and I've tried it with 2 different roms too
Click to expand...
Click to collapse
Heh, don't know.
Maybe some other rom's installation messed up something....
hmm... I faced the same problem...
So.. I did have to send it for repair :S ....
maybe i have the same problem... many roms tried, many soft and hard-reset, but the lifetime cycle of the phone before to re-flash the device is at maximum 1-2 days... now i'm trying the tips about quickgps (maybe could be correlated) on the thread in this forum... but the most probably truth i think that could be an internal memory rom damage... if anyone find a soluzion about this problem via software i'm here...
I seem to be having the same problem.
A week ago i tested the latest roms with winmo 6.5.1, after several roms i settled with a rom with build 23081, enabled htc sense, played around abit and went to bed and put the phone to charge. when i woke and touched the screen, the phone immediately froze.
After removing battery it froze again in SE boot screen and after second removal of battery the phone hard reseted it self.
The phone has been freezing and flashing itself ever sense, sometimes the uptime is minutes sometimes over day.
Currently the phone has survived 3 days without a spontaneous flash, the only difference is that i didn't bother to enable htc sense last time it flashed. So i enabled htc sense once again and will see if the phone survives a day.
ristiisa said:
A week ago i tested the latest roms with winmo 6.5.1, after several roms i settled with a rom with build 23081, enabled htc sense, played around abit and went to bed and put the phone to charge. when i woke and touched the screen, the phone immediately froze.
After removing battery it froze again in SE boot screen and after second removal of battery the phone hard reseted it self.
The phone has been freezing and flashing itself ever sense, sometimes the uptime is minutes sometimes over day.
Currently the phone has survived 3 days without a spontaneous flash, the only difference is that i didn't bother to enable htc sense last time it flashed. So i enabled htc sense once again and will see if the phone survives a day.
Click to expand...
Click to collapse
i had approximatively also the same problem... i'm trying to understand what is the reason of this instable situation... gps location? memory? graphic instance that use HTC sense? is heavy to understand... if anyone could also find the right solution...
was having the same problem tried the method in this thread http://forum.xda-developers.com/showthread.php?t=540290 and it is working on my X1 so far
lebkom said:
was having the same problem tried the method in this thread http://forum.xda-developers.com/showthread.php?t=540290 and it is working on my X1 so far
Click to expand...
Click to collapse
Did the "task 29" do anything?
I tried the method suggested but no change besides hard reset. And the X1 froze about 12h after that...
ristiisa said:
Did the "task 29" do anything?
I tried the method suggested but no change besides hard reset. And the X1 froze about 12h after that...
Click to expand...
Click to collapse
ye mine did it again aswell this morning
i just tried hard reseting then install a stock rom then hardreset again and install a custom rom, will let you know if it works
Do you guys often use Opera Mobile?
Ahah!
Very encouraging to see other people had the same difficulties... and I suppose that it's just a question of making sure a fresh ROM flash works properly.
Sadly mine has reached the stage where it's no longer working for 'a day' before crashing... it's just pretty much dead.
Now I can bring up the tricolour screen if I'm plugged in, the ROM then begins to flash off the memory card, but crashes half way through every time.
I have tried this with 2 batteries, one of which (which I have used once and was working fine but only lasted 2 days before breaking) now does nothing whatsoever. The other lets me get half way through the flash every time.
- I can't send it back on the warranty until I reflash it myself (and I don't have a receipt anyway) so I'm going to go find a high street mobile fixing place and see if they can help.
hardresetting then flashing a stock rom (R3A generic) then hardresetting again then installing custom rom and hardresetting, definately fixed my phone, has been working for more than 2 days now it usually stops in less than 1 day.
FYI - high street phone guys managed to reflash the device for £15....it lasted 4 days but has just died again.

Help? Battery/Software/SD?

So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Sound's like Kernel panic. Wipe everything and install soemthing stable like cyanogens 4.2.15.1 or dwangs rom. Didn't know there was anything worng with SuperD's kernel though.
jaekim708 said:
So I've been lurking around this forum ever since the G1 first came out. Messed up on the rooting procedure once, got a replacement a few months ago.
Worked fine so far. A while ago, I flashed the latest SuperD rom. I am using an 8gig SD card. I've overcharged my battery several times by accident, so the health isn't exactly up to out-of-the-box standards.
I noticed the phone entered a random reboot when I turned the music on for a while. As time passed, the random reboots became more and more frequent. Since I couldn't keep the phone on for more than 20 seconds without a reboot, I decided to wipe and flash a new rom today.
I chose Pays 1.6 Rom and flashed that. Didn't wipe my ext4, just wiped and flashed. I figured ext4 wouldn't cause such a problem, so I ignored it for now. Problem not solved.
I turn the phone on, and in the few seconds, I noticed the following:
the apps all show up, meaning the phone reads the ext4 apps (right?.)
The sd card itself displays an error - I can't access music, pics, etc.
Phone service is fine, all apps are normal.
Buuuut there's still that random reboot issue. It reboots, enters a G1 screen, then reboots quicker. In other words, after I take the battery out and reboot, it might take maybe 1 minutes before it auto-reboots. I wait, then it reboots in maybe 30 seconds. And faster and faster, until it doesn't respond anymore and I have to take the battery out again.
I'm not sure what I do causes random reboots. Sometimes it's when I press a button while in the music app. Sometimes it's when I open the keyboard. Sometimes it's just when the screen goes to sleep. It's fairly random.
I can go into recovery (once I take the battery out once.) Fastboot also works.
Running the danger SPL and the second to latest radio (I believe a new one came out recently? Mine's the one with 26)
Help please? What part of my phone is broken?
I'll give additional information if asked. Not sure what parts are relevant.
Click to expand...
Click to collapse
Since the rom relies on apps to sd I would guess the ext is borked and maybe the fat32 as well. I would reformat the whole thing to fat 32 then reformat to ext2 or 3. Load Dwangs rom for testing (easier to get running just as a test).
So I wiped my SD (ext4, dalvik, fat32) and tried cyanogen. Then I tried Pays. Reboot problem's gone, but neither of them is reading my SD card.
I'm assuming its just a matter of backing up the SD and repartitioning? I'll try that next when I have time.
Thanks for the help guys! Lastly, any ideas on why this happened? It'd be hard to pinpoint the exact reason, but I'm assuming I'm not the only one who had this problem - how did other people get to the situation I'm in?
I wiped all of my SD, repartitioned, wiped the phone, flashed AOSP 1.6. w/ root and "expansion" pack.
Reboots are less frequent, but they still occur too often. They don't occur by themselves - its always when I'm using my phone.
It seems that it reboots more when its connected to my computer. The SD isn't mounted, but the simple fact that its connected seems to trigger reboots more frequently. Is this a coincidence or can a USB cord trigger reboots?
Help please
EDIT: The phone just made an audible cracking sound as it rebooted - like someone stepping on gravel. Hardware issue?

Help G1 problem

Hi,
Recently I have been having a problem with my G1.
When I have left my phone on stanby for a period of time and I press the menu key to turn on the screen the screen back light comes up but it's blank.
I have to press the end key periodically to get the screen to come on this can take anything from 5secs to 1min. I have reflashed and wiped several times and tried different themes but it still does it.
I am running cyanogen 4.2.15.1 with the enoch theme updated via cyanogen updater.
It does not do this all the time it did it more with Darkstar.
I have been told I should re-root but I am worried about doing this because I am on the new radio and have been told I cannot flash back.
What to do???
Then why don't you just change roms and see if the problem still consists :S
Jonnibravo said:
...worried about doing this because I am on the new radio and have been told I cannot flash back.
What to do???
Click to expand...
Click to collapse
DREAIMG.nbh will over-write you radio and spl, no worries there if you wanted to go that way but I think it's a little too extreme. What you need to do is a complete wipe and stable rom with no a2sd or swap. Once that's running for you - start adding stuff 1 at the time. Sooner or later you will pinpoint the problem.
Good luck.
borodin1 said:
DREAIMG.nbh will over-write you radio and spl, no worries there if you wanted to go that way but I think it's a little too extreme. What you need to do is a complete wipe and stable rom with no a2sd or swap. Once that's running for you - start adding stuff 1 at the time. Sooner or later you will pinpoint the problem.
Good luck.
Click to expand...
Click to collapse
Ok I reformatted the partition and set it back up using amon ra 1.5.2 swap 96 ext 512 then installed super d 1.10.2 and slowly added apps to my a2sd, did on Friday no problem till Thursday afternoon it once again I pressed menu and the screen stayed black after pressing the end key repeatedly it came back up about 30 seconds later.
2 theories here
Could it be because I am using a class 2 sd card or
Could it be related to a lock screen, before I used lockbot though I uninstalled it it still happened noww I am using lock screen 2.0 the day after it started happening.
Cyanogenmod has always done this on every version I've flashed. Try a different release.
goldenarmZ said:
Cyanogenmod has always done this on every version I've flashed. Try a different release.
Click to expand...
Click to collapse
I am on super d 1.10.2 not cyanogen, do you mean a rom that does not use cyanogen guts???
hey i've also got this problem but it's kind of different, 1 im not running cyanogen, 2 it might be a hardware issue with your's as it is one with mine. So far i think its the flex cable but not too sure. My screen would go black and whenever i try pressing the home or something the device would just completely shut off. I would remove the battery and have to try and boot it up at least a couple of times before it decides to work properly.Any ideas? i might get a new flex cable but im not sure if thats the real problem.
Jonnibravo said:
I am on super d 1.10.2 not cyanogen, do you mean a rom that does not use cyanogen guts???
Click to expand...
Click to collapse
Super-D does use few CM bits and pieces in his rom but that's should not be the problem.
Do you use any home replacement apps?
Do you use a task manager?
If so, make sure that your taks manager is not killing your home. Do make sure that it kills other memory intensive apps when not in use
If you use stock home then make sure to check "Keep Home in memory" in the "Spare Parts", see if that helps.
Sounds like either a memory leak somewhere (one of the apps) or a hardware problem. Let's hope for the first.
And yes.... please get rid of that class 2 card ASAP. New class 6 8 Gb card is around $15 and will last your thru few devices so its a money well spent.
Good luck.
I pretty certain it's not a hardware problem as there is no pattern to when it happens, I do have a habit of installing different home apps as I like to try them all that could be the problem.
]I give that a try
Try cleaning the cache . Maybe there are too many things running in the background .
how bout you do a full wipe and try out super cdsi v4 rom its just about the fastest rom out there

Categories

Resources