Related
Hi my P3300 ( artemis) has suddenly startet to freze and or turn it self off, only thing that helps is to take out and replace the battery, i have read all topics i could find with simmilar problems, and i was hopping it was my battery that was going old so i bought a new one, but it didnt help.
i have tried diffrent roms wont help,
i tried to "push" the battery closer to the conectors, no help and it's seems like its hard or software problem but not battery.
some times when i turn the device back on with out replacing battery it works but sometimes when i do like that it gets to HTC page showing rom info etc. then it fades out and i can see blackscreen but it "glows" and the phone is dead nothing works.
i chaged the screen a couple of months ago but the fault dosent seems to have with the screen to do.
It seems that it is a hardware issue. They replaced motherboard for me, it is working now.
hmmm i have no warenty left. and my phone does look used so i guess im screwd?
sorry for that..
an issue happened with me witha nokia mobile before and when i sent it to be fixed they told me there was a problem in the radio chip or something like that..
so try to install a different radio ROM ... that's all i can think of.
and sorry for your loss
i will try that, but the problem ocured before i change radio last time....
hmmm
I changed back to original HTC wm 6 (swedish) yesterday and the phone worked all day, and i thought i have solved my problem, but whilst driving my car for about 15 min and the phone was in placed in the a space in the middle of the dashboard under the stereo i found out when i toke it back up to call that it was dead......so i was wondering could it have something to do with heat or lost GSM coverage (thinking i have multiple faults on my artemis)
htc arte100 freezes on startup
can any one give solution for my arte100 it freezes on startup
how can i restore or put it on bootloader mode in order to upgrade it
thanks in advance
for the boot loader see the WIKI
if your device is unlock flash it with any rim you want.. if not get the original ROM for your mobile and then flash it..
for flashing try using RUU or the SD card flashing..
all can be found on the WIKI
totally dead
now i cant start it again its dead as it can be?! i tried to have it with out battery over night, with battery and usb cable over nigt, old and new battery, usb from pc or from orginal AC adapter or waths it called.
it dosent light the "loding battery led" or nothing, i tried with sim in sd card out, sim AND sd out or both in nothing work i have open it and blew away all dust still dead?!
something i forgott to try?! or is this expencive toy gonna be a toy for my 8 month old kid?
Artemis goes Dead
I'm having the same problem, and have worked the same solutions. I noticed this started when I also had my phone underneath the radio in my car.
Replace radio rom
Upgraded rom to 6.1
New Battery
Unlocked Phone
Last attempt was uploading active sync 4.5 since loading version 6.1
I've got no solution yet, just posting to let you know we are in the same situation.
I have read about similar problems in different forums, and the conclusion is that it's a hardware issue. When I sent it in for support, they replaced the motherboard. I guess, there is something smaller wrong but they just replace it all.
No way.
Replaced battery, took out SIM and SD, changed ROM (finally it was long enough at life), but still:
Display freezes, turns white - game over.
I give up.
Until a few days ago I was very happy with HTC and my Artemis.
Artemis 110 (T-Mobile Compact iii) Back from the Dead
Artemis 110 (T-Mobile Compact iii) Back from the Dead, Flash via Active Sync then via SD Artemis
Since the XDA site is so valuable, I’m trying to consolidate my efforts to make a legitimate contribution to the site. Hopefully this post can also be of help to others.
These are just notes on what I’ve been through so far with my Mobile Compact iii. Hopefully, someone more advanced than I, will read through and possibly troubleshoot the errors I may have overlooked.
Upon returning from Germany, I needed to re-flash my ROM with an English version. Version of choice was the Blue & Black cube with WM6, thanks to the developer(s).
BLACK & BLUE v5.0 ROM WM6.1 CE OS 19716 ( Build 19716.1.1.0 )
First I used the USPL to temp unlock the phone
http://forum.xda-developers.com/showthread.php?t=311403
I then loaded the Operating Version, and received many stalls and stops via the White Screen of Death. (I have some theories on the white screen of death, but do not have the knowledge to confirm) I suspect utilities are running in the background and are being loaded. Impatience at this point could quite possibly be my nemesis
Second, I loaded the unlock to permanently unlock the phone.
http://forum.xda-developers.com/showthread.php?t=400445
I re-flashed my ROM again the B&B cube. Still the phone seemed unstable, was shutting down and getting the white screen of death. I hard booted the phone many times, soft booted, battery out, and through no tangible reason of thought, the phone just did what it wanted to. Start, not start, and hung up at various points in the boot process, died in the middle of Wal-Mart.
I tried the over-clock on WM6, using WM5 over-clocking. Talk about unstable. I couldn’t find and over-clock for WM6, but now know it is an option in the Blue and Black Rom. Anyway my phone went out completely. To the point of not being able to get past the initial flash screen where the OS and IS version displayed and that was it. Left the phone overnight, nothing.
In a last attempt, I used the SD mini flash option found in WIKI.
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
I used my printer SD card reader and the adapter supplied with the SD mini card. Home PC recognized the storage device, right click and format, then did the rename file (NBH file to ARTEIMG.nbh) as found on the WIKI SD Flash page. I initially tried without the format, and only got to the Red Green Blue (RGB) screen. Since I received no indication of status, I started over, formatted the mini SD, extracted the file to the SD, renamed, to ARTEIMG.nbh and I also extracted the B&B Cube WM6 Rom to the SD mini, for I found a couple of post indicating the ROM also needed to be on the SD. I followed the instructions, did the Boot-loader. (Power Button, Voice Button, and Rest with Stylus, release stylus, continue holding Power and Voice until upload prompt on the phone). I received the Update SD image, and followed the instructions. Here I got the prompts indicating status of uploads. OS 1 started to load, OS 2 loaded, phone when to RGB screen. I left the phone alone for 30 minutes at the RBG screen.
After 30 minutes, I rebooted the phone, and the phone went through setup and auto-detected my current carrier SIM card. Has been working for the past hour and 20 minutes.
Since the phone is running at the moment, I will wait and see. Next step is to load the original WM5 T-mobile version via active sync. If downloaded from the t-mobile site, the ROM update isn’t broken down enough to rename the NNBH file..
I’m also waiting to load a new radio version, for I’ve read that may be the cause of some of my problems.
Another theory I have is that T-mobile sent out kill phone code to stop my phone.
Any feedback from the Pros is very appreciated.
I have the same problem: Link to other thread
Apparently there are many devices with the same (more or less) problem.
I hope someone is able to tell what is malfunctioning....
These Instructions are out of date, and may not work anymore.
-CarComp
EDIT POST ON 5-5-2010
INSTRUCTIONS ARE IN BOLD!!!!!!!
EDITS AND MY OPINIONS ARE IN ITALICS
Want google and not winmo but can't wade through all of the confusion offered up by the supergeeks of android linux? Well just do these steps. It took me an evening to figure out these steps, and could whip it up instantly now.
BTW - it REALLY helps to have a computer with an SDcard slot adapter that handles the micro-sd cards. I don't really recommend trying all this with a USB cable, b/c once you get to linux only, you will kinda be screwed cause it doesn't quite work the same like windows CE. Also that and you can't format through the phone, so just get an adapter ok? Stop right here if you don't have one and just order one or go to walmart and spend 10 bucks and get one. BTW, your micro sd card should have come with one when you bought it, so go look for it.
Ok how to get the super Eclair android into NAND and live a happy life....
1, CHARGE YOUR PHONE UP ALL THE WAY BEFORE ANYTHING. When done charging, unplug whatever is in your USB port for the rest of this procedure. Having phone plugged in while flashing = BAD
2, get hard spl on your phone.
3, Install Hyperdragon IOlite on your phone to get the radio(1.65.24.36) that I recommend, which will improve battery life and possibly other things that I don't know about. Get it here -> http://sakajati.com/blogs/2009/02/hyperdragon-iv-iolite-based-on-htc-iolite/
4, format your 1+ GB sdcard using fat32 only.
5, download polyrhythmics dark / light build for nand and sdcard.
put that SINGLE FILE (androidinstall.tgz) into a folder in the root of the SD-CARD called "andboot" - Get it here -> http://forum.xda-developers.com/showthread.php?t=600154
6, go to http://sourceforge.net/projects/androidhtc/files/ and download KAISIMG-PANEL2-320-TILT.NBH if you have an ATT tilt. If you have something else, download that NBH.
7, Rename that NBH file to "KAISimg.nbh". Put it in the root of your storage card.
8. Now you are ready to install to nand. Get out your stylus, hold down the camera and power button and press the reset button with the stylus. It should go to an updating screen. If you don't get a white screen with a progress bar, but instead it still shows tri color and says "serial" then you did something wrong. Start over from step 1. Once you get to 100%, wait 20 seconds or something (just for shihtz and giggles) and then pull out the battery.
9. Now, put it back in, press power and wait for android to start booting. You will know cause all this random looking text will go by. You have to be quick to do it, but press the middle button on the d-pad when it says 'press the middle button to enter setup' or soemthing like that. (EDIT: I've been told that you have to just hold the d-pad center button down. Either way, just get that button pushed when it says to push it).
You will be presented with some options. Make sure the little asterisk is on the "NAND" option.
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.
Crap your pants at the speed NAND offers. Install some live desktops (I like the starfield warp drive one from the google market.)
BTW: If you mess up your phone doing this, blah blah its not my fault blah blah you probably shouldn't be on these forums etc. Just make sure you have HardSPL and you will be fine. I've flashed hundreds of roms hundreds of times. Just that one little step will make your life easier.
EDIT:
RADIO DETAILS:
I've heard a LOT about using the latest radio or whatever version 1.71 or soemthing. I run radio 1.65 just fine. I never upgraded it through out all of the android builds. I operate like this.. If you weren't having cell quality issues, GPS lock issues, or any other radio issues in WINMO, then android will be fine too. I've added a step to the process to install a specific winMO rom that has the radio that I use. If you don't like the fact that I'm telling people to use an older radio, so be it. I'm just spreading the word for what works REALLY well for me.
EDIT: (My thoughts on the panel 1 2 3 and the 320 or 428 or whatever...) Picking the right panel is like playing the 'cups and ball' game. if you know which one the ball is under, you will win. Well for you TILT users, the ball is under #2. I don't know why, but it is. If 2 doesn't work, use 1. Doesn't get simpler than that. As for the resolutions, just use the 320. Ya, some apps fit better on the higher res, but our screens don't support them really well, and its all blurry. Think of it like this..... using 4xx instead of 320 is like asking 3 pixels to display as 1, vs. one pixel displaying as one pixel very clearly. Polyrhymic has done a great job supporting our screen's native 320 size, so just use it.
EDIT: (An issue i've noticed with booting and having your phone plugged in). Android just won't do it on nand. You can charge your phone from a dead point for say 20 mins, unplug it, then turn it on, boot android then plug it back in. You can't plug it in, and turn it on. It gets stuck in some sort of USB status loop.
EDIT: (When your phone just sits there on the A N D R O I D text and won't boot). Seems like this has been happening a lot, for me too. I've found there are two ways to stop this, one is preventative... Don't let your phone go totally dead. The second, when you reboot your phone, press and hold dpad center, then just count to 10 and go to the QUIT option. 9 times out of 10 it will boot right up.
IF YOU HAVE ANY PROBLEMS, JUST REPEAT THE PROCESS.. Don't skip the full charge and installation of Hyperdragon first.
for may people on here, the fear of flashing isn't the problem. it's the missing features such as bluetooth, speakerphone and in some builds even camera.
I would LOVE to go nand. I hate not knowing if the problem is with the build or with the sucky sdcard.
but I need to revert back to winmo for bluetooth headset. once that or speakerphone works I am ON IT.
Nice, couldn't have said it better myself, a few small points, press and HOLD the centre button on Dpad, a quick press will not do it, I'd mention the radio version too, but those are not major issues, and can be sorted easily enough
Good advice about the card reader and adaptor, those two saved my ass a few times in the early days of Nand flashing, I keep a good stock winmo kaisimg.nbh on a spare SD card, you only need a 128Mb one for a stock rom.
Yes there are install instructions on the build posts, but a lot of the info is now spread though some 2000+ posts, so having it all in easy terms helps a load.
I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!
added info about panel stuff to the instructions
It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))
my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...
Disturbed21 said:
It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))
Click to expand...
Click to collapse
agreed, currently no gps working map that can be rely such as garmin that can work on winmo.. 1 disadvantage of android.. need to be online to get route..
Kurt Cobain said:
I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!
Click to expand...
Click to collapse
320-428-480 là chỉ độ phân giải đó bạn.
320 is a resolution of 240X320 and the 480 is a resolution of 320X480
Mình biết được chừng đó thôi
Created another edit to the 1st post.
I'm not saying that android doesn't have its shortcomings, I'm just offering a quick means to get to NAND without trying to comprehend the whole thing in the traditional sense of reading 200 threads.
BTW my radio is 1.65.24.36
Maranevin, try flashing Hyperdragon IOlite first. Maybe a radio switch will prod your phone into the correct direction.
Errr, for newbs who don't know how to properly unlock their device isn't this dangerous? There IS a possibility of bricking your phone if you don't know what you're doing -- right?
Anyway, I would also mention that if you or your phone can't do 3G don't flash to NAND yet. The radio can't be instructed to use GSM only with the current poly build (and any other I have tried so far)
I totally agree with mnjm9b, the problem is not flash the phone, the problem is that there are many things that do not. In particular I am very happy with the performance of 2.1g polymod to date is the best I've worked.
carcomp thanks for the help, very good summary.
aikeru, if someone is flashing a phone, they probably know the risks. Its not my fault if they do something stupid. Is it autozone's fault if I buy specialty tools and ruin my engine changing a timing chain?
Anyways, I don't get the 3g thing. We have hardly any 2g or whatever is below 3g here in Mulberry Indiana and my android works fine.
Like I said, maybe i've found that magic mix of things that works really darn good.
BTW: major argument for using android.....
First of all, i'm not borg. I have yet to really get into bluetooth. I own two earpieces and the only good thing i've found is you can talk on the phone in freezing weather with you hands in your pockets. Bluetooth to mute car radios is cool, but I have a 20 year old car. I don't need bluetooth for file transfer cause i've got wifi, and SD CARD.
Second, as for the speakerphone, it never really was that loud anyways. I came from a hermes, which has a speaker like the voice of god, so i've never been impressed with the kaiser speakerphone.
Third, the camera... I have a nikon D60 with a speedlight for taking stills and lowlights, and a Kodak Z612 in my wife's purse most all the time for the past 3 years for video and spot shooting. All this data easily goes onto the micro sd card and into the phone.....
carcomp said:
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.[/B]
Click to expand...
Click to collapse
I've done all step above, just when i did this After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power. it started back to Step 9 when i had to 'press the middle button to enter setup'.
So, i skipped that step, and then later everytime i tried to press reset button, the phone is freeze, then i had to started over again...
In some cases, my OK button became to POWER button...
And at first time, WIFI was OK, then it showed Unable to start Wi-Fi
Any suggestion for my troubles?
Thank you!!
Great!!
Hi all, Great!! I am now running Android on my kaiser and I love it!!!
Just a couple of questions for people who can answer them:
- How to change phisycal keyboard layout? I mean, some keys that I have in blue aren't the same I have on my keyboard...
- Is there any means to connect to a pc to transfer contacts and files?
Thank you all!!
Gnatto
Maranevim said:
my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...
Click to expand...
Click to collapse
Same problem here. Someone please help. My device is now a worthless brick!!!!
Ok when this happens (its happened to me), first of all don't panick. If you've installed hardspl you are protected, and besides, just cause your phone won't boot android doesn't mean its bricked, it just means its not booting android.
There can be a multitude of things causing this, but the #1 reason I think is "Just because thats how it is"
First of all, don't boot your phone with it plugged in. Ever. Charge it first, then boot it, or charge it enough to make it through boot then plug it in when it reaches android.
Second, sometimes during boot, it just hangs where it says A N D R O I D, or some other text. You can get around this by resetting with stylus, then pressing the center dpad button, then just counting to 10 or 20 or some random number that makes you happy, then select quit. It should boot.
Thanks. Fortunately I unbricked it by putting the KAISDIAG.NBH file onto the SD card, then booted it. This unbricked it. I also put the the KAISIMG.NBH for the Android on here and it booted into the installer. My problem now is that when I click install to NAND, it says it has an error extracting from the SD card for the android installer. It then quits back to the main install screen. I think it is a permissions error since it says on the screen something about being read only. If anyone could help me, I would greatly appreciate it. Thanks.
Oh and btw, I never had usb plugged in since mine is broken.
Ok well you are on the right track. Before you do anything else though, flash a copy of windows Mobile. Either take your pick, or use hyperdragon. Its very complete ... radio / ext rom etc. Next, try reformatting your SD card using windows. Do a complete format, not a quick one. That might help. Now reflash using the link to kaisnbh that i posted.
Remember, installing windows mobile is your NAND reset. Its lot like an sdcard where you can just erase everything. You have to put something else there that is radically different. I may be wrong about this, but it seems to be the case more often than not.
You may be one of the special case people who have a weird phone that takes one of the other KAISimg.nbh files too, so don't discount that. Also since you have hardspl, and you are flashing from the sdcard, you phone is probably NOT going to brick, and even if it does screw up royally, if you can still get to tri color, you can fix it.
Ok. That's great to know. I'll try what you stated. Do I need to partition my SD card? Thanks again. I really appreciate the help.
So about a week ago or so I began, out of the blue, to have power button issues. The power button would turn my incredible on when it was off. It would wake it when it was asleep/screen off. After that it became hit and miss. When the screen was on it was highly unresponsive. Sometimes it took several presses to get it to turn off, sometimes I couldn't turn it off at all. Sometimes a tap would bring up the shut-down menu as if I had long-held it. Long holding it usually didn't work either. A few times I had to do a battery pull just to shut it off. I eventually downloaded quickboot and a screen lock widget just to get that functionality back. The last thing I remember downloading before this started happening was 'reddit is fun'. I uninstalled that after the problems, but to no avail.
Now lets go over what I was set up with. I have an amoled unit. I was at the time using CM7 Final and whatever kernel was included with it. Although I have used it a lot in the past, I didn't have setCPU installed or running this time. The only root-required thing I can remember running was autostarts. No changes were made to autostarts in the weeks leading up to the problem. I have used many roms; Frankenrom, Virtuous, Ruby, ShadowRom, IncDoes AOSP, The New Guy, Warm 2.2, Redemptive, SkyRaider, Evervolv, and several of the CM Nightlies. While using Redemptive my radio completely quit working across the board. Returning it to stock and then re-rooting fixed it. As far as I can remember I had only used SkyRaider, Evervolv, and the CM Nightlies up until I was using CM7 Final.
So after the problem started happening I decided easiest thing to do would be to try and flash a nightly over it. Tried that, didn't work. That was kind of a long shot, and I decided I might need a full wipe. Did the full wipe and installed the latest nightly. The problem persisted. I think I flashed the latest SkyRaider then, still had the problem. This was starting to seem kind of serious so I did another complete return to stock. I booted into the stock rom and used it for a bit, maybe a few hours, it seemed to work. Since things seemed back to normal I flashed the latest CM Nightly again. Seemed to work for a minute, then it was back to the same old problem.
Now around this point I, for reasons I can't remember, remove my 16 GB SD card and put the stock 2 GB one back in. I have SkyRaider on that and I flash it, it works perfectly. In fact it continues to work for a day or two. All this time my old 16 GB is sitting out on my desk. I eventually decide to clean it up, deleting a bunch of stuff I didn't need on there, and throwing it back in. After putting the 16 back in the problems creep back in. Here and there, then only working half of the time, then barely working at all.
About this time I come up with the idea that maybe something on the SD card, or the card itself, is causing this problem. Seems like a long shot, but I can't think of any other reason that would fit. I do not install apps to my SD card.
So I pull the SD card out. I was at work and I didn't have my old 2GB, so I just left the slot empty. It seemed to still be messed up, but over the course of the next hour or so it began to work correctly again.
Now I'm at home and I have deleted everything from my 16GB, and reformatted it completely. I'm about to flip it back in and see how things go.
The strange thing about this whole situation was that the problem didn't seem to just start and stop. It was as if it phased in and phased out over time, but always being caused by certain things. It seems organic if you know what I mean by that.
Feel free to tell me this is a really ridiculous idea. I think it might be. Is there something critical to the android system that could possibly be stored on the SD card?
Maybe its a hardware problem that's being affected by the weather in your area, because you can run android fine without an SD card. You would be surprised how the humidity affects electronics. This is just a crazy thought to a crazy problem lol
Wow, finally there is someone else out there with this problem.
Mine didnt have this problem till i flashed MIUI latest rom....but even after somehow making it into the recovery mode...i was able to restore my previous cm7 build...
BUT....the problem persists....
So I think I am going to pull out the 8gb sd card my friend gave me from his EVO 4g.
It annoying because sometimes i cant get into even hboot with power + volume down.
I know the volume buttons work because i can change volume on phone.
I can still see the power button still being pressed down, its not stuck or anything...it works 50/50
Can you give an update OP, please?
I also have an AMOLED Incredible..and dont want/can afford another phone...
have any of you opened up your phone to see if the button was still soldered to the board?
- i did and it is, same issue.
Hey all,
I've been using my HTC EVO 4G for quite some time now (nearly a year), and just recently it started acting up. As the title implies, my phone randomly shuts itself off and starts itself back up-- for reasons I cannot determine. Usually when it does it once, I find that it goes on a rampage and shuts itself off before the phone even starts up. It will continue to reset itself for 3 or 4 times before it starts working properly.
I've honestly no idea what could be wrong with it. When this first started happening, I was running Fresh ROM 4.2 (but I've already been running it for a while-- it couldn't have been the ROM), and the default kernel for Fresh. I decided to boot into recovery for an earlier version of the ROM, but to no avail.
Finally, I decided to get a whole new ROM (am currently running on Synergy) and kernel altogether (currently running on netarchy kernel), but again to no avail.
Of course, I did a complete data wipe upon installing Synergy, so it can't have anything to do with phone's software, can it? I'm assuming it must be something physical; and am seriously considering purchasing a whole new SD card. (About the SD card: whenever I try mounting my EVO as a disk drive, immediately after I select the 'Mount' option, a notification saying 'Preparing SD card' pops up, and fails to ever mount it. This, I believe, is due to the fact that I'm not on a .92 Hboot, but it is nevertheless worth noting.)
Has anyone else ever had this problem? Any help would be greatly appreciated.
Edit: The fact that I can't mount my phone as a disk drive is actually a problem in itself... I need to convert to Hboot .92, but my file system isn't FAT32 (at least, I'm assuming so, since it doesn't load my PB31I.zip IMG in Hboot) and I can't convert it if it doesn't connect to my computer... Guess I'll go back to Fresh.
Does your phone kind of heat up sometimes? Like in the front of the screen? My did and it turned out to be a physical problem. Bad charger port, sounds weird but thats what I was told. You might need to buy another one.
ruben1221 said:
Does your phone kind of heat up sometimes? Like in the front of the screen? My did and it turned out to be a physical problem. Bad charger port, sounds weird but thats what I was told. You might need to buy another one.
Click to expand...
Click to collapse
Yeah, I had originally thought it was an over-heating problem as well. It used to happen most of the time while I was driving-- with the sun hitting the phone directly. However, it's been doing it in-doors with A/C and virtually every other place . I just took notice of it in the car because that's when music was playing.
Ultimately, I might just consider transitioning to the Galaxy SII.
Thanks for reply. <3
I've been having same problem had my evo since day 1 and never any problems up unitl a few months ago.but now i definetly know i need a replacement mine phone gets super hot as well originally thought it was the rom but went back to stock all for nothing because the problem still remained
Is call power cycle the only way to fix it is to get a refurbish phone from sprint they know about it, they will do a test on it and order you another phone with the new 2.3.3 that cant be rooted, is not the sd card it is something on the hardware motherboard
My Evo likes to randomly lock up on me. The screen goes blank, and the phone is locked. The only thing i can do is pull the battery and power back up, which sometimes is right away, others i have to leave the battery out for a while. I cant seem to figure out what it is, i have tried different kernels with the same result. I am running MikG 3.11, and currently am running Chop Suey v9.2.6. Anyone else have this problem? Any help would be appreciated. Thanks.
I would try a different ROM/kernel combo and see if that helps fix the issue. Or you could just try a different kernel with MikG. Some setups don't always play nice together, and what works on one phone may not work with another.
Sent using my HTC EVO LTE and a magic wand
@FinZ28 - Sent from the EVO LTE, oooOOOOooo...shiny...
Anyway, on to the list of questions, some of which I have had issues with:
- Are you still using the original 8gb SD card that came with the phone?
- If not, what class/size is your card? (I have a 32gb, class 10, and it freezes/boot loops my phone all the time...did it 15mins ago)
- Are you downloading anything? (It takes the phone a long time to write large files. Many times, you can use the phone normally while it writes/downloads, but as soon as you turn off the phone, it won't turn on again until the file is finished downloading.)
- What are you doing with the phone (games, music, text, etc.)?
- How old is the phone?
- When was the last time you dropped it? (I know you did...We all have)
______________________________
HTC Evo 4g
No i am not using original card, i have a 32 gb class 10.
The phone is 2 years old, and i have dropped it once, been a while since i did that. It doesnt happen when i am doing
just one thing, happens when i am texting, on the web browser, gaming, watching vids. The screen goes black and is
unresponsive, but the buttons at the bottom are lit, only thing i can do is pull the battery, or if i am near a computer i can
use adb to reboot. Ive tried every kernel i can find but doesnt seem to help.
Yes, I have dealt with that problem also. My best advice, use a task killer. Might not be great advice, but that's the most that I can suggest, because it helped me out a lot. Luckily, I don't have to deal with those problems anymore (see my signature )
_____________________________
HTC EVO LTE
rlvaldez said:
No i am not using original card, i have a 32 gb class 10.
The phone is 2 years old, and i have dropped it once, been a while since i did that. It doesnt happen when i am doing
just one thing, happens when i am texting, on the web browser, gaming, watching vids. The screen goes black and is
unresponsive, but the buttons at the bottom are lit, only thing i can do is pull the battery, or if i am near a computer i can
use adb to reboot. Ive tried every kernel i can find but doesnt seem to help.
Click to expand...
Click to collapse
What was your Wiping, and Flashing process ? What Recovery are you using ? Are you running A2SD ?
rlvaldez said:
My Evo likes to randomly lock up on me. The screen goes blank, and the phone is locked. The only thing i can do is pull the battery and power back up, which sometimes is right away, others i have to leave the battery out for a while. I cant seem to figure out what it is, i have tried different kernels with the same result. I am running MikG 3.11, and currently am running Chop Suey v9.2.6. Anyone else have this problem? Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
sounds like a kernal issue man with the clocking settings, i would make sure your wiping correctly and use a different rom or kernal or even a combination. remember every phone is different. what may work for one htc evo 4g may not work for the next best of luck man