At completely random places (both in recovery and rom) my G1 locks solid with the screen on and will not respond to any key
I can use Fastboot, recovery (Amon 1.7) and any ROM e.g. Super E (the latest I have tried is Froyo by Laszlo. I have not made any alterations to the ROM's
I have wiped everything (lots of times) including system
I have updated to Hboot0013d and radio to 2.22.27.08
Have bought a new Samsung SD card, partitioned and tried that
Any suggestions on where to with troubleshooting ?
TIA
Have you dropped it or gotten it wet at all? Have you tried any other ROM?
Thanks for the reply
Dropped - almost certainly, wet never
Tried several ROM's including the defanged DRC83 - all the same issue
matt.pope.universal said:
Have you dropped it or gotten it wet at all? Have you tried any other ROM?
Click to expand...
Click to collapse
Try Froyo Melt or Dream Team ROM.
Update you radio to 2.22.28.25.
If anything, it might be hardware issues.
Related
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.
Hi all, I'm new to android, and after trying several different builds am ready to give up trying (even tho I LOVE android) due to the problems I keep having.
When I boot into android, it works fine for a while (varying from 5 minutes to over a day) then I get a frozen screen, which stays frozen even after re-booting into Windows. Sometimes this stays frozen for HOURS and makes the phone unusable.
The last attempt was with Hyperdroid v1.6 and it worked fine for 15 minutes, (yes I turned off the auto -rotate display) then it froze up.
If anyone has any ideas/pointers/advice, it would be MAHOOSIVELY appreciated
Please post some more information including your radio and rom versions.
When I have problems I always start from a clean slate including a task29, flash the latest radio, rom and download a new build to a formatted sd card. Try builds that use different kernels.
Beyond that you can start swapping kernels different kernels into your build.
i think I've sorted it thanks polo735, after reading your post I finally researched task29, ran it and reinstalled everything and it seems (touch wood) to be stable now Happy Days!!!! Many thanks
Hi! When running ROMs that are "newer" such as 2.2 ROMs they crash/freeze for no apparent reason. With or without an SD card in, everything wiped, newly updated recovery etc etc.
However! When i run a ROM like Kimera 1.8 Cupcake ROM it all floats on perfectly.
I cant see any rhyme nor reason behind the problems im experiencing. Any thoughts? It's really killing me :/
Could you define "crash/freeze" a bit more specific please? Does the phone boot up as normal?
If it just hangs on randomly when using the phone normally, it might be a ROM specific problem (not neccesary 2.2), maybe some app who can't handle 2.2 just yet, or you configured it badly (overclocking?).
As riemervdzee says, more information required.
What ROM are you trying? What radio? What CPU settings if available?
I tried SenseHero (2.1), Froyos and currently running Fusion!ROM 2.2 and they all run perfectly on my G2 Touch (Hero)
It boots up perfectly but then either reboots after random use or just freezes in the sense that i use some app or scroll through the app list or try to make a call and it simply freezes up and is unusable until i remove the battery and reboot.
I am running FROYO_2.2.1_Special_Edition_RC1_update1 and as far as i can think of i haven't configured it anything specific. Is there perhaps a way to reset every setting such as CPU setting etc that might be wonky?
Im running 63.18.55.06PU_6.35.15.14 Radio!
lol i love you're definition of "newer roms" when you've only used 1 rom.
first i'd recommend trying some others. i'm not saying the one you tried is bad at all but it may just not agree with your phone for some reason.
Having said that - if I were you i'd check exactly what you're wiping - it sounds to be that you haven't cleared the dalvik cache or something (i.e. you've not done a full wipe before flashing a new rom).
My new bie guide has the process for flashing a new rom (part 2 i think).
I've run a myriad of roms, im just stating that this is the one im currently running and experiencing problems with.
kloggeboll said:
I've run a myriad of roms, im just stating that this is the one im currently running and experiencing problems with.
Click to expand...
Click to collapse
What exactly is the problem of running an other 2.2 ROM? It could be a ROM specific problem, which frankly occurs at your phone (egh, sometimes happens ).
If you are sure you wiped data, dalvik, cache and ext2 (if any) I really suggest you move to another ROM and see if that one works OK.
I experience exactly the same problem with every 2.1 and 2.2 ROM so i doubt its ROM specific. I've wiped everything. Im quite clueless in this case what the problem might be!
Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.
Guys,
I'm kindly asking to share your thoughs on any of the questions. It is very important for me since I don't know whether it is my fault or the phone was already damaged.
The rom I tried to flash was a stock rom and the flashing process hasn't been interrupted.
Thank you!
had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.
az_registration said:
Hello All,
I have an HTC HD2 (TMOUS) that hangs once it gets warm. I got it a couple of days ago. The first thing I tried to do was to update the rom (there was an old stock rom) to the latest version from t-mobile. But when I tried to do that the update process failed at 8% with "error[262] update error". I tried to flash it again, but got the same result.
I tried both the approaches: to flash via usb and via SD card, but the results were the same. Flashing via SD card gave me "RSA fail" error. I have found some related info, but that is not the case since I could flash the radio later. Also I've noticed that after a couple of iterations the phone were vibrating 7 times during the rom update process. Some guys are telling that it could be a motherboard issue (http://forum.xda-developers.com/showthread.php?t=797179 and http://forum.xda-developers.com/showthread.php?t=826119).
Today I tried to update rom again and got it successfull. But the phone has hanged on botting. Taking into account that the phone has been turned off for the whole night I decided to try to put it into a cool place. I put it to the balcony for 5 minutes and the turned it on again. It has loaded successfully and I was able to test wifi and to make a couple of calls. But after some time when it has got warm it hanged.
I have found that some guys had the same problem but couldn't fix it (http://forum.xda-developers.com/showthread.php?t=701349).
It seems to me now that this is a hardware issue (maybe with the internal flash memory module).
Was anybody able to fix the isssue?
Could this problem be caused by my attempts to flash?
Thanks in advance.
Click to expand...
Click to collapse
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.
Thank you for your replies!
T-Macgnolia said:
Before you go trying to replace the mother board or any hardware such as that. I suggest you run a task 29 on your HD2 and reflash the stock ROM. A task 29 totally wipes the current ROM on the HD2 so if it is a problem from you trying so many timez to flash the ROM this will clear that up. Here is a link to the task 29 thread so you can learn more and decide if you want to do it or not.
Click to expand...
Click to collapse
Yes, that's a useful tool, but I'm afraid that I might damage the existing rom and will not be able to flash it agian. Also it requires to flash HSPL before which also potentially might brick the device ( I mean the flashing process).
sike222 said:
had this issue and indeed it was the motherboard so i had to send it back to htc.
good luck.
Click to expand...
Click to collapse
So it was a factory defect, wasn't it?
If I did something wrong during the stock rom flashing process, could be the reason of the problem?
Thank you.
After reading forums it seems to me that the issue appears mostly for T-Mobile US version..
If it is a hardware problem, does anybody know what part of hardware is damaged?
Thanks!
I have been searching all over for answers, but have not found any solid solutions. There was another case similar to mine, HERE but I really don't think things are quite the same. I am new to flashing with HD2, but am very seasoned with the Samsung Vibrant.
I had the phone app crashing and robot voice for a while. I have done all of the supposed fixes but nothing has worked yet. I bought my HD2 second hand, (like the big screen and more RAM better than on my TMO vibrant), but when I got it it was in great condition, completely stock. So I wanted to put android on it because MinMo is (for my concerns) unusable. SO, here is what I have done.
Started with a TMO(US) HD2 Stock
-Flashed New Radio from 2.14.50.02 to 2.15.50.14
-Flashed HD2O WM 6.5 ROM (Phone Worked fine, but decided WinMo sucks)
-Flashed MagLDR
-Flashed CWM
-FLashed BOYPPC SHIFT PDA sense&HOneycomb (FAST!)
But then whenever I tried to make phone calls I get the robot voice and three seconds later, crash. (the process phone in com.android.phone is not responding...)
-The first fix I tried was HERE for the Low volume fix. No Dice...
-Then I Tried this Volume Fix HERE, but did not fix problem.
-I tried disabling the contact sync, seen in another thread, and still nothing.
-Went into Rom Manager, Flashed Clockwork recovery, then used it to "fix Permissions"
-During the permission fixing, I received a normal clear phone call with no FC.
-Then after call it said that it was done with permissions, and asked me to restart.
-After the reboot it would just constantly Force Close every five seconds, and it was not showing any network signal.
So Then I:
-Flashed a new Radio. -2.06.50.04 -TMO US
-Still Not working
-Went back to the MAGLDR and did an AD Hardreset, and tried flashing HYPERDROID.
-Still nothing.
-Reset again and Reflashed BOYPPC SHIFT, (liked it better, I know, a lot of flashes...)
-Now getting network signal, and able to get into the phone program, but as soon as I try to make a call, same problems occur with Robovoice and FC.
Sorry so thorough, but I always feel like more info is better than too little!
I had looked at another thread that said something about wearing out the radio from flashing, but on my vibrant I have flashed over 30 ROMs and 10 or more Kernals, and it still works good, so, I dunno. Kinda stuck.
Got my finger ready for the thanks button for ANY help offered.
Also noticed that now, no sounds are playing at all. Speaker driver error? It worked ok the first time I loaded this rom.
Just installed CMYLXGO's Desire Rom Yesterday and the phone works.
Now running CMY's gingersense streak, which is also a Sense ROM, and it works too. Is there any reason that anyone can think of as to why my phone will only work with sense themes?
i'm having a very similar issue.... i've tried a few roms and i get the same thing. calls go out for a few sec then force close. ppl tell me they can't call me sometimes because of this. i even task 29'd and reflashed everything. radio, magldr, cwm and now hyperdroids latest... still get force close and an unusable phone....
wtf
2.15.50.14
The above is the recommended radio that was a good start. Now the next thing to go under settings --> sound --> Feedback. I forget which one it is that causes the phone to crash/give robot voice but that is most likely what is causing the issue for you guys. I believe non sense builds also have these options if I recall correctly. I use sense builds myself. Also be sure to restart phone after you uncheck the settings under feedback. Phone should work after that and no robot voice.
I dont have robot voice and i'm running that radio. hyperdroid was running fine until recently and i have this problem. i can't get calls it causes the phone app to crash and sometimes calls crash a little bit in.... i've task 29'd and redone a clean install with old known working hyperdroid WITH NOTHING INSTALLED still does it, tried new hyperdroid; same thing...
antiparadigm said:
Just installed CMYLXGO's Desire Rom Yesterday and the phone works.
Now running CMY's gingersense streak, which is also a Sense ROM, and it works too. Is there any reason that anyone can think of as to why my phone will only work with sense themes?
Click to expand...
Click to collapse
you can try cyanogenmod and miui by starting over again but remember to do task29 to be sure that you dont leave any traces of previous installations !
!!
good luck and regards !! !