I have a G1 that was replaced under warranty earlier in the year. I rooted it as I had my preordered G1 that it replaced and it has always acted weird. I'll get freezes during use, it will randomly reboot, it will lock up when sleeping.
It seems as though i can do a fix_permissions or mess with some setting and it will be fine for a while, then crash. This usually happens when my wife is trying to call me and she's furious that my phone is dead - again. The weird thing is that I would update the software, the phone would act like **** for a few days, then calm down and work as it should - but still screw up once every two or three days.
It has been really pissing me off lately, I tried to completely blow it out and go totally back to square one with the DREAIMG.nbh. It never once crashed during the 12 hours I was running RC29. I rooted it and as soon as I installed the Cyanogen recovery image, it started acting weird.
I did the usual steps of run telnetd, reflash recovery, then reboot. That was fine. When I went to flash DRC83 and flash CM 4.2.8.1, it started hanging at weird times inside of the recovery console.
Once was when I chose "Flash from update.zip" by mistake, it hung.
Another time I went to flash DRC83 and it hung before it started writing.
Then it would finish DRC83 and hang at the main menu.
Random reboots.
Finally I got DRC83 and 4.2.8.1 installed and it rebooted to Cyanogen's ROM like it should. I was high-fiveing myself and everything (no, I wasn't) but it was short lived; it hung after the 3rd app installed from the Market.
WTF? Do I have a phone that just doesn't want to flash? It seems whatever it is that doesn't like my phone lives inside the recovery partition as well.
My phone says this at the tricolor screen:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
This phone came with RC31 on it if I remember, I think it was a month or two in to when they all came with RC31.
I would like to re-root the phone since I like getting all the cool updates being pulled from the newer builds. If it can't happen, I'm just going to OTA the damn thing and use it unrooted but reliable and get less crap from the wife.
when flashing the cyan rom you use the 1.6 image from HTC,which can no longer be found there.You should be doing this:
1.Wipe
2.Install 1.6 APD...Blah devphone..blah
3.install cyan right after without rebooting
4.now reboot
5.should goto rec mode
6.reboot once more
That's pretty much what I had done except using the 1.6 image with the radio and recovery partitions removed, from the cyanogen wiki. The problems seem to start with the new Recovery partition.
I just received the 1.6 OTA overnight and I'm going to let it run for a few days to make sure that the phone itself isn't defective in some way.
It may be that there is some component in the phone that is of borderline quality and just can't handle something in the Cyanogen ROM but works with OTA software otherwise.
Ok, I received the 1.6 OTA and after that, the phone started acting ****ty. Not nearly as bad as what it was doing when Rooted but for sure acting the same way. I had about 12 hours before the phone locked up in the Market, then froze while asleep, then rebooted when I hung up on a call. Apparently the 1.6 ROM just hits the phone harder than 1.5 did.
I have put in a request for a warranty exchange and should hopefully have a new phone this coming week. I'll let it run unrooted for a few days to make sure it's OK, then I'll root it.
Your radio version is out of date from what I see.
That was the RC29 radio, it is now at 2.22.19.26I with the 1.6 OTA.
It is pretty remarkable that a phone that had NO problem with the 1.5 OTA and occasional screwup with the 1.6 OTA would totally crap itself when running Cyanogen's 1.6. I guess he's right when he says that it can cause problems. It certainly made a phone with marginal HW problems go over the edge.
Related
Hello. you may flame me if you like, but at least leave me with a link which can help me.
I rooted about a week ago. I tried CyanogenMod but I had some issues with receiving calls. Eventually i decided to use nandroid to flash black to my old ROM (before root)
but now It's stuck on ANDROID screen. I can see the animation stopping, blinking, and starting over.
adb is not working, but i'm guessing that's normal, I didn't try it in the booting stage before rooting.
The good news (i hope) is that some updates stayed, namely the SPL and radio updates. Of course, they might be the ones creating the issue.
DREA110 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO-2.22.19.26I
What can I do?
Did you wipe before you loaded Cyanogens rom? You shouldn't be missing calls with his roms. And try loading RC29 and start over.
Yes I did, several times. Every time I installed. Also an important remark is that I have a European (Austrian/German) G1.
The problem I was facing is a known bug. But the G1 hardly feels like a phone if this isn't working properly.
I figured staying on the normal OS wouldn't be so bad waiting for the CyanogenMod to fix that.
I will try what you said, thank you.
kalin12351 said:
Yes I did, several times. Every time I installed. Also an important remark is that I have a European (Austrian/German) G1.
The problem I was facing is a known bug. But the G1 hardly feels like a phone if this isn't working properly.
I figured staying on the normal OS wouldn't be so bad waiting for the CyanogenMod to fix that.
I will try what you said, thank you.
Click to expand...
Click to collapse
If you are having problems with that specific rom just load an older cyanogen rom.
I was thinking just that
After seeing CyanogenMod and Recovery it's really hard to go back.
i feel like such an idiot. All I had to do was wipe. I was just about to do the RC29 update and I said hey, let's wipe. I don't know why my former unrooted Android needed wiping, but it worked.
Cool, glad your problem is solved now. Put [SOLVED] at the begining of the thread if you don't mind.
i will try to be as detailed as possible. im coming from the kaiser community so go easy on me
when i had recieved the phone it would turn on go past the tmobile g1 screen and go into the recovery console. the console read. JF 1.41.
after reading around the best option i got was reverting everything back to factory settings.....and so i did. i installed the factory spl went back to rc29....then updated to rc 30 and installed the new cupcake.
everything was fine except for i couldnt get the phone activated given im an AT&T user.
this morning i finally recieved the unlock code from tmobile and when i turn the phone on with the att simcard, it gave me the triangle with the exclamation screen.
so i hit alt +l then alt w and after a reboot it would bring me back to the same screen. Also this recovery screen is diff from the jf 1.41 (im guessing this is the factory console).
now im out of ideas as to how to get this phone back in order. i would love flashing the DREAIMG.NBH but sadly my phone refuses to go in bootloader.
ive been trying to hold camera+ power and its jsut loads up the tmobile g1 screen.
any and all advice/helps are appreciated.
-thank you
so this is totally weird. i leave the phone unplugged with the battery out for about 3 hours. came back to work on it....turned it on and well it loaded and got me to the home screen ( no sim card ).
so i powered off the phone and inserted the AT&T simcard turn it on and it shows me the same screen again with the triangle and exclamation point.
how do u explain that ?!
pressed power for 3 seconds and then let go and held down the back key. it flashed the bootloader tricolor screen and then said ""everything will be reset to factory defaults .press send to reset"" and when i did that there was no change........nothing happened. ended up pulling the battery out..
Same problem..
I have very similar problem.. but mine takes much more than 3 hrs to come back.. and even then , the task manger keeps popping up from time to time in the home screen ,, so i guessed my home button was stuck or something...
After i found your "problem Sovled" post in another theread on 11th oct ..i thought i better take your suggestion before taking phone apart..
I was on 1.5 version and 2.22.19.26I radio. also i do not know whether i'm in RC29,30,33 ..
i'm really confused about all this radio,firmware ,recovery things....
Please Guide me ..
well first you need to get in your ph to find out if u have rc29. if you are able to get to home screen just hit menu - setting - about phone - all the way down it'll tell you what you are running.
i followed this guide to help me flash it to the cyanogenmod rom
http://forum.xda-developers.com/showthread.php?t=563679
hopefully it helps. but if you are able to get into bootloader unlike me then jsut flash the rc29 hopefully it will solve your problem.
my home key acted like it was stuck but now everything is working fine.
Thanks for Replying so quickly ..
I managed to go to the bootloader screen(tricolor) ..actually it went without even pressing the camera button(any idea why??) after leaving the phone without battery for about 5 hours.. and i flashed the Dreaimg-RC29 file .
Since then i'm Stuck in recovery mode again.. but this time the recovery utility is different (yellow letters)..i.e hopefully RC29 is succefully installed.
I wanted to complete doing your suggested guide before asking any more questions, but now i unable to so what shud i do now?
IS the task manger popping up involuntarily sometimes for you in the cM builds?
Can it be that you had a hardware button issue, which somehow rectified itself when going to Cyanogen..
I really appreciate your taking time to answer my questions ..
well sounds like jsut what had happened to me.
make sure you have tmobile simcard on you with a dataplan.
you're going to have to leave your phone off without the battery or just turned off for a while. from here on out it was trial and error. i kept trying to turn the phone on hoping it would go past the recovery screen once it did i activated the phone and finally completed the root process.
as for the cyanogen mod rom i think you are right. though on my initial flash i had a bunch of force closing apps but it all fixed itself upon a restart. ever since then i haven't seen the recovery mode every time i boot it.
PS: that reocvery mode that you see is the stock recovery meaning yes u have flashed RC29 sucessfully.
so i jsut flashed to CM 4.2.3.1. and well im back to square one. im booting into the recovery by default. obviously confirming my doubts about the hardware problem.
im going to try and leave the phone off for a while and see if i can get it to load up. usually that solves my problem.
Oh..
Thats depressing.. Anyways... Lets do it together then I have kept my phone unsed for about 16hrs now.. hope it works ..
Have you tried the HTC Diagonistic program for g1 (DREADIAG.nbh) ?.. I am yet to try it out as i cannot go to the bootloader..
http://www.megaupload.com/?d=7NRX7H40
which version of cyanogen were you using before this happened?
i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.
mtkhalid said:
i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.
Click to expand...
Click to collapse
Did you update from 4.1.9999 straight into 4.2.3.1? If so, that's the problem (maybe).. I suggest you install the HTC 1.6 ADP Rom (link in the cyanogen 4.2.3.1 post) then upgrade to 4.2.3.1. Make sure everything is updated.... rom, recovery & spl (before you upgrade SPL make sure you have the most recent radio version first! or you'll brick the phone). then give it a try and see what happens...
you are right. the first time i just flashed the new rom. the second time around i followed the guide except for i flashed the latest cyanogen rom.
I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..
Still waiting for your answer
SaiSantoshD said:
I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..
Click to expand...
Click to collapse
how did you flash the RC29? after pressing the power button
did it give you any errors? once its flashed, reboot by pressing home and back (or w/e the SPL tells you to)
it should boot into the rom
Home button problem (repaired/solved)
Firstly, thanks for responding ..
I had flashed RC29 when it had gone to the tricolor bootloader screen on its own
but after that it would not go anywhere other than recovery(exclamantion mark)
Now good news
4 hours back i opened the phone again(third time) , and took a safety pin and started scraping(gently) the non shiny parts of the connector ( daughter board to main board) .
I think it was previously shorted near that area , so by scraping removed the shorted metal joints .. and now the phone booted up to RC29 (just like that) and i even installed the cyanogen mod ..
Many thanks to u all .. hope this Comes UP in google search for people with similar problems(and there are many)...
KEYwords: Home button stuck on recovery no booting
Ah wow didnt think of that lol.. glad to see you got it to work
Hi all,
I was trying to update to CM 4.2.3, so first I wiped, then installed the regular ole android 1.6 image from Google, it goes to reboot and all seems fine. However, in the boot process it gets past the "T-Mobile G1" screen and then it just stayed at the flashing Android screen for several hours, I finally gave up on it and pulled the battery. Now if I boot normally it will go to G1 screen then to flashing android then NOTHING, the screen is still on but its all black. If I try booting with power+home I get a picture of an exclamation point in a triangle and a phone laying next to it. If I boot with power+camera it says
"DREA100 PVT 32B
HBOOT-0.95.3000
CPLD-4
RADIO-2.22.19.26I
Oct 20 2008
Serial0"
and there's 3 androids at the bottom on skateboard.
I don't what to do, except call Tmo and hope theyll send me a new one. I'm without phone so feeling particularly helpless
EDIT: I did alt-w at the screen with the exclamation point and the phone, it did something, now I'm running 1.6. PHEW, that was a close one
Note, you are never bricked if you can get to the fastboot or recovery screen.
evilkorn said:
Note, you are never bricked if you can get to the fastboot or recovery screen.
Click to expand...
Click to collapse
good to know, thx
i kept searching around for what exactly a bricked phone looks like, but now i know
Take a picture of your initial G1 screen and you're all set
u may have lost root , jus re downgrade then updgrade back
maek_it_happen said:
u may have lost root , jus re downgrade then updgrade back
Click to expand...
Click to collapse
i did, but i got it back. now running cm 4.2.3 and loving it!
so I got a new (new to me was used) g1 today from a friend at work and everytime I turn the phone off with the power button it only starts in boot loader without pushing the camera button it does it on its own if I take the battery out and wait a minute or two then it will boot and run normally
history of the phone
not sure if this was a problem with previous owner he said that for the 3 months he owned it he never turned it off and so never saw the problem (thats crazy that he kept it charged all the time for 3 months)
phone was off when I got it running the latest ota firmware
I turned it on into bootloader and downgraded to rc29
downloaded telnet never got it to connect
while playing with telnet noticed the problem of booting into bootloader
downloaded flashrec.apk and put 1.4 cyanogen recovery on
made nandroid back up
did hard spl from the g1 faq
put on ota-tmobile cupcake with root
put expansion on for ota-tmobile cupcake with root
bump I will be back tomorrow afternoon to see if any one knows thanks everyone
All,
I received a replacement N1 yesterday from HTC as my previous one developed an earpiece issue. After unlocking the bootloader for the first time, it seems that the phone is overheating and randomly rebooting. I reflashed to stock, with the only exception being the unlocked bootloader using a guide found on this forum.
This was my first experience unlocking the bootloader and trying to flash a rom. I've attached a logcat to see if any info can be provided.
Thanks.
EDIT:
N1 - 1 day old HTC refurb
2.2.1
FRG83
Baseband - 32.41.00.32U_5.08.00.04
Kernel - 2.6.32.9-27240-gbca5320
Is the phone actually getting hot?
This is why I don't get why people get a phone and IMMEDIATELY start loading custom ROMs and such on it.. Use it stock for a few days to make sure it's good.
No it's not getting overly hot. My original N1 got much hotter.
Its my fault for not waiting, I do realize this.
I did wait 6 hours or so, but I know it wasn't enough. Got a bit anxious to load CM6.1.
I had first accidentally loaded Insecure boot which made the rebooting much more common, but went back to stock, and loaded superboot. Everything was fine for a little while, then the rebooting started again.
Just trying to see if I can figure out the issue before giving HTC a call.
etacv said:
No it's not getting overly hot. My original N1 got much hotter.
Its my fault for not waiting, I do realize this.
I did wait 6 hours or so, but I know it wasn't enough. Got a bit anxious to load CM6.1.
I had first accidentally loaded Insecure boot which made the rebooting much more common, but went back to stock, and loaded superboot. Everything was fine for a little while, then the rebooting started again.
Just trying to see if I can figure out the issue before giving HTC a call.
Click to expand...
Click to collapse
when i got my nexus back in early january, i dont think that i waited more than a hour before i unlocked the bootloader anyways, your phone seems fine. iy could just be the stock rom you flashed or kernel panics(i doubt). flash cyanogenmod and see if you still get the reboots. unlocking the bootloader doesnt have anything to do with a phone overheating and rebooting. besides, what is overheating? how hot does it get? ive gotten mine to 49C(120F) before
Well that's the thing, it really hasn't gotten that hot. I was just assuming it could be related as it was rebooting after sitting on the charger for a while or trying to download multiple apps from the Market. I was able to get as far as downloading ROM Manager and was part way through the CM6.1 download when the reboots from hell came back.
I used the Signed Passion FRG83 images to reflash.
I'm now attempting to format the SD card to see if it changes anything.
etacv said:
Well that's the thing, it really hasn't gotten that hot. I was just assuming it could be related as it was rebooting after sitting on the charger for a while or trying to download multiple apps from the Market. I was able to get as far as downloading ROM Manager and was part way through the CM6.1 download when the reboots from hell came back.
I used the Signed Passion FRG83 images to reflash.
I'm now attempting to format the SD card to see if it changes anything.
Click to expand...
Click to collapse
it sounds like youre stressing the phone(kernel). try to download 1 thing at a time for now. are you overclocked by chance?
I am not. The phone is bone stock at the moment.
Hm, it looks like i'm on FRG83 not 83D. The SD card is having some issues unmounting and i'm not receiving the OTA update to 83D
Yes - it is overheating!
My original phone did not have the problem. Every replacement phone I got from HTC crashes after 5 minutes or less on every application that made my original phone warm to the touch.
Applications that cause this:
RoboDefense
Tower Raiders
Speed Pi (run multiple times)
Curling
I am trying to get HTC to send me a 3rd replacement!
So as an update I formatted the SD card, and it seemed to have helped for a while.
I had the phone in the charger last night and was speaking on the phone for about 10-15 minutes until it started rebooting again. This time it was stuck on the X so i had to remove the battery.
Not sure what's going on...
So looking through the logcat's i've noticed these lines as failed:
E/Zygote ( 58): setreuid() failed. errno: 17
W/DevicePolicyManagerService( 78): failed parsing /data/system/device_policies.xml java.io.FileNotFoundException: /data/system/device_policies.xml (No such file or directory)
D/SntpClient( 78): request time failed: java.net.UnknownHostException: north-america.pool.ntp.org
I'm not sure if it means anything.
The firmware was downgraded to FRG33 and OTA updated to FRG83D
Will probably be sending this back and hoping the unlocked bootloader won't make it cost a fortune to repair...