My friend is running CM 7 on his Tmobile G2.
He was describing that yesterday was acting weird with market downloads.
Here is what he he emailed me on what happened.
the phone was acting normal throughout my day until the evening towards the night, i noticed it failed to finish downloading the update for google earth along with google maps. the phone was fine, and then i pulled it out of my pocket a few times and saw multiple times that it was randomly turned off. i would turn it back on and it would still give me the same issue. when i got home and plugged it in to charge, it would boot and then get to the main home screen telling me that google maps is downloading to update. however the update would be frozen, and a few seconds later the phone would freeze altogether, forcing me to turn it off by pulling out the battery. this happened about 4 times, and now has reached the point that it has become a brick and refuses to turn on or show the charging light
any suggestions on what might be wrong with the phone? Thanks in advance. Im running Cm7 on my phone and never experienced this issue.
same happend to me 3days ago, phone running then freezed... bootloop after batterypull... recovery worked for 2 times but had problems with flashing new rom/backing up -> errors with cache partition...
after 4hours of letting it stay off -> it wont turn on again und wont charge (no LED)
tried it with another dz battery+charger... no change... i wrote htc and they answered within 1hr that i have to send it in without battery...
i guess its a known problem (or why wouldnt they want to have me sending in charger+battery .. if its a power-on problem..)
there are semibrick threads here and in other forums.. but they all don't suffer from the power on problem... so i guess i did the right thing sending it in
edit: never had heat issues, never had random reboots, no overclock, no indication of an update from any app did any harm to my phone, running cm7 for 3 weeks without any problems, no hboot flash, no radio flash ... nothing that would indicate a risk of brick (according to guides & forum threads)... first htc that ever failed for me ;(
Thanks for the reply. I will forward it to my friend. I think he is going to try to exchange it at the store and if it all fails we are going to try HTC.
have any of you tried to boot into recovery? did you have eng-hboot on your devices? go to #g2root
its complete dead as in dead... no LED light, no turn on, no hboot mode (or what its called when you press vol+power key).... i dont have a g2 but a unbranded european dz.. hboot and radio was never touched by me
Similar thing happened to me. My phone kept frozing on me running cm7..was fine for a week though.
So I booted into recovery..wiped cache,factory reset flashed another rom got bunch of erros recovery thing rebooted stuck i n htc logo for like 20min yanked out battery rebooted and it never rebooted back. No hboot,no nothing.
My light indicator still worked though but no hboot or anything.. got a new one now have to send the old one back to tmobile but I'm scared that they're gonna charge me for removing void stickers.
Even though I checked twice that removing void sticker won't avoid warranty according to tmobile customer chat sevice..
So I'm thinking about swiping out the sticker that contains serial number and such on back of our phone with the old one and tell them the new one came without a void sticker lolol
Sorry I got way off topic rofl..
Sent from my HTC Vision using Tapatalk
We went to the store today and exchanged it for another g2. The guy didnt ask any questions and exchanged it happily for a new one.
This very same thing happened to me today. Updated to CM 7.0.3 from 7.0.1 and the phone was freezing when installing items from the market. Pulled the battery and the phone was stuck on the boot animation. Pulled the battery again, and now it will not start at all. No charging light, no nothing. Had more than 50% charge, and now it seems entirely unresponsive. I can't use the power w/ volume button technique either, because the phone does not respond.
Seems like somehow I have bricked the phone, or the phone just coincidentally died just after updating to CM 7.0.3? (seems unlikely)
just a short update on my case:
i got the mobile back from HTC repairs.
they exchanged my "mainboard" (changed IMEI) under warranty.
i don't know what emmc chip i had before cause it died so fast, but my usb deviceIDs changed completely and are now simmilar to the ones in the cm wiki.
my current emmc is now:
$ cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
SEM04G
Click to expand...
Click to collapse
might help ppl.
Related
Hello,
I have a strange problem with my HTC Artemis (O2 XDA branded, bought in Germany, no lock)
It behaves unstable and indeterministic.
Unstable means that it crashes/stucks or turns off.
Indeterministic means that it happens when i plugg it to charger, when i'm syncing, when a phone rings, when using applications/tomtom or just i arrive to work and i find the device off.
When it crashes or i find it off, the biggest problem is to boot the device. It takes me typically 10mins, when i'm always trying to press the power button, push the reset button or unplugg the battery for a while in random order until i bring it to work.
After first crach, the device also often crashes or stucks again during the boot process.
Once, the device was so dead, that it took me two days to bring it into bootloader mode and then i could at least flash the ROM.
All these was happening with ARTEMIS TOUCH 4.01 WWE - LITE NO CUBE.
Yesterday, i switched to ARTEMIS TOUCH 4.02 WWE - LITE NO CUBE (burned FW twice) without installing any other applications and the problems are still here
My personal feeling is that it is getting every week worser.
When i bought the device (eBay), there was original FW with Win Mobile 5 on it, i immediately flashed to ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device. So i flashed to 4.01 and this issue was away, but approx 2months ago, the above described behaviour has started and nowdays i'm fighting with it 2-3x a day.
so, can anybody help?
GiZMo
Similar here
I have a similar problem, what's really strange to me is, that as far as i can recall it started happening 2 months ago or so also!! weird huh...
my device simply reboots from time to time! even while i'm making a call.
the weird thing about these reboots is that when it comes back to live i do not have to enter my pin to enable the phone! everytime i perform a manual reboot (by software, using the pin or remove battery) i have to insert my pin to able to make a call...
i have upgraded from 3.01 full touch to 4.02 full touch about the time it started, i have now 4.02 vanilla touch but problem still occurs from time to time.
any ideas?
Im another one to join this boat!
Bought an MDA C 3, two days ago, bought of someone from gumtree.com.
Worked fine for the first hour, and then locked up - nothing on the screen, no LED. Only way to get it going was to remove battery and then press power button.
I upgraded the ROM from the original t-mob UK WM5 to mechles fine release: http://forum.xda-developers.com/showthread.php?t=371182
The lock-ups / crashes have now become rarer, on average every 4 hours (before was every 1 hour).
There is no pattern to them either, although I have saw the screen trun all corrupted just before it happens. The last one was caused when I pressed the 'start' button.
I'm on a T-Mob contract, and lost my Kaiser, got ripped of when I tryed to replace it by a tosser on here for $375 Thief on the loose thread, and was hoping my luck had changed when I bought this one!!
It is T-mob branded and I wonder if there isn't a fix on here, would T-Mob repair it under warranty??
same "issue" with no entering of PIN after reboot. But not always
GiZMoSK said:
ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device.
Click to expand...
Click to collapse
here i found a good description of that issue:
"
Originally Posted by lasertony
I've got the same problem as !Novy, but nobody seems to have noticed his question. Are there any other guys out there with this strange problem ? I have been using this rom for a while and sometimes, without any visual warning the phone freezes up. This is particularly ennoying because there is no way to check wether it is working or not. Every other function or software keeps working ! The phone is just not receiving any calls or sms. So you can miss an entire day of calls and sms without knowing... Only when trying to call somebody the dialer says 'Dialing...' and nothing happens. No connection.
A soft reset is needed to get the phone working again.
"
btw, now i'm again trying to turn the device on, it's again stuck. grrr
Hello,
i had a few weeks ago a similar strange behaviour.
After changing the sd-card I had problems to turn the device on. After a hard reset it began to boot but hang.
The I flashed back to original O2 ROM. Then I had a unpredictable behaviour. Somtimes no sound. Sometimes I cound not be called. Sometimes Error message "no sim card". After every reset i had an other error.
Hard reset and flashing was no solution. Removing battery for less than 4 hours has no effect.
Then I wanted to send it back for repair. I took of the battery. The next day I wanted to try a last time and surprise: The device works fine without an error. Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
regards
Andre
It is Happening to my device too!!
It stucks every 2-3 hours!Tried many of the cooked ROMs but nothing.Also tried all the radio roms for 1-2 days.still the same!
It stucks with no particular reason.SOmetimes in s2u2 sometimes when am receiving a call.... etc.
Had the pin problem too for 3-4 times!
I will try your sugestion ANDRE and we will see!
Also i will try flashing the original rom,cid unlock and then flash the cood rom twice!
Fingers crosed....
Andre1210 said:
Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
Click to expand...
Click to collapse
didn't help
happy u
now, i will try to flash back original german o2 rom
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
bricked or not?
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Vinnie1 said:
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
Click to expand...
Click to collapse
I thought it was a battery problem too, but I've 2 batteries and both are died in the same time? I think it's too strange...
My P3300 have this problem from when it is returned from assistence and with original firmware (without other applications).
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
GiZMoSK said:
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Click to expand...
Click to collapse
jahrami said:
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
Click to expand...
Click to collapse
but i cannot get into bootloader mode so no flashing from SD card or PC
bricked device
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
GiZMoSK said:
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
Click to expand...
Click to collapse
the good sign are the leds that means you have a very good chance...the guy made the piont...check the wiki
random crashes are often caused by hardware malfunction...sometimes the connection on the motherboard stuck,get broken or make a short-circuit...so check the hardware
I know most of the Desire users on here have upgraded but i am on a 24 month contact and require some help!!
My phone since new has been excellent apart from the boot loop problem which HTC fixed with a new motherboard, however today it's all gone to ****. Went to use it and switched on 3G while waiting for it i just put it down for a few seconds, went back to it and it had froze buttons didn't work, screen wouldn't move even long back press didn't kill it.
So (this is were i think i might have broke something) i pulled the battery out, popped it back thinking it just need to restart and it wouldn't turn on!!! thinking that the battery might be flat (it was low at the time) i plugged the charger in but it would do anything (No orange light) and quick google and i find a way to get it charging (Without the battery in, plug the charger in which makes the green and orange led flash then insert the battery) this made the orange led stay on and after a few hours the green led came and i thought OK it should work now.... but it doesn't :-(
Anyone got any ideas?
The phone is rooted/s-off and running Oxygen 2.3.1 so without some life in it to put a RUU on i don't really want to send it to HTC.
Thanks for any help you lot can provide.
James
Hi!
Got the same problem....my Desire won't turn on...
Were you able to fix yours?
I'm on S-Off, too...
THX
Are you able to boot into fastboot / hboot?
I don't know if it is the same problem but the HTC Desire I got can not be turned on for longer than a few seconds after booting into Android (GingerVillain 3.3) (With AC, on battery, USB.. doesn't matter).
The battery indicator is sometimes jumping from 100 to 0 percent and from 0 to 100 percent. Before this the phone had problems with incoming calls not showing up and the other side getting an "calling partner not available".
Aswell the OC/UV Beater daemon was constantly crashing.
Since the phone's recovery menu is still working fine, I tried a full wipe, formating everything, reinstalling the ROM but it didn't help to solve the problem, it just fixed the crashing OC/UV Beater daemon occurring before.
I am rather clueless what to do now. The phone worked fine for many many months with that problem suddenly appearing. It is the phone of my girlfriend, so I cannot tell you exactly what changed in that time. She is claiming that she did not alter anything and with the phone not working after a full wipe, it may be the truth
May the hardware be damaged in some kind? What would be possible steps I could try out next before defining it as scrap metal?
Flash 2.3.3 RUU and if problem persits, call HTC.
Do a full wipe and don't install the rom just leave as is...
I had the same problem... so I tried that and it worked so now I'm using cm7 nightly build #258 for the past 5 months or so and no problems since...
Sent from my HTC Desire CDMA running cm7 nightly build #258 using XDA App
It's usually very difficult to brick a phone. If you can get into your custom recovery then it still works. If not, then get into your hboot and install a custom recovery (if rooted) or RUU rom (if rooted will make it unrooted).
If your phone doesn't turn on, check wires, battery, plug, connector links between battery and phone (clean them). Hopefully you haven't had a sudden power surge which has blown up a component on your desire.
certifiednoob said:
Do a full wipe and don't install the rom just leave as is...
I had the same problem... so I tried that and it worked so now I'm using cm7 nightly build #258 for the past 5 months or so and no problems since...
Sent from my HTC Desire CDMA running cm7 nightly build #258 using XDA App
Click to expand...
Click to collapse
The OP wrote a full wipe did not fix his problem!
Hi everybody!
I have an almost 2 years old DHD which I think is completely bricked. It was working for approximately one years perfectly and then suddenly it stopped working. Whenever I tried to turn it on, it only vibrated once and did nothing more. Sometimes it turned on and these working periods were enough to restore to stock condition (It was rooted and had Eng S-OFF before.). I had brought it to service and they said they was not going to repair it as the device got water damaged. I'm pretty sure it was not! After a few weeks, it started working again. I was using it for 3 months then it bricked again and it's the situation today as well.
Previous week I looked into the development thread and saw all of these new amazing roms. So I took my DHD to see if it's working or not. The situation is the same. Everytime I power it on, the phone only vibrates once and nothing happens. I'm not able to get into hboot mode. At some very rare occassions the phone turns on and works flawlessly till reboot. When I connect it with USB, the computer doesn't recognize it. Battery is charged, I even tried another battery.
Does anybody know what happens with the phone? I'm open to any possible solutions to try. Please don't suggest to bring it to service or repair it, because I have another phone, just want to try to recover it and ask your ideas about the problem.
Thanks in advance!
Greetings,
Adam
So you say you cant enter in fastboot or recovery?
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
paescheh said:
So you say you cant enter in fastboot or recovery?
Click to expand...
Click to collapse
I cannot enter into hboot mode. Didn't try recovery, but assume it's the same.
waterbox said:
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
Click to expand...
Click to collapse
I also think it's a hardware problem. Will take a more careful look at the battery.
Sent from my CM10-powered GT-I9103
need help
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
goofed again said:
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
Click to expand...
Click to collapse
Wrong sub forum buddy, post in the One V Forum.
Its possible that there isn't "water damage", but there could be moisture getting into the phone causing it to act erratic. To cancel out that possibility, submerge it in a closed container full of rice for a few days
Sent from a satellite
Dear xda-developers,
about a month ago my phone started acting funny, sometimes my browser or youtube would close randomly.. well, if it happend i just thought “oh, i pressed home accidentaly” or “oh its just a bad coded app”..
just 15 or 20 days later, not only my browser or youtube were crashing down.. it took my launcher with it (resulting in htc-sense prompting LOADING... for 2 minutes).
well, so far it has been “just annoying” me but my phone remained "functional" but: update saved the day and fixed this problem :laugh:
untill yesterday: all apps started crashing (including PROCESS ANDROID.PHONE etc.), a reboot fixed the problem.
today, all apps crashed again.. reboot didnt fix it, and my phone got stuck on boot sometimes (sometimes on the "ONE X" rom screen, other times on the "HTC" screen).
so, what did i do? what everyone would.
i started my htc bootloader, clicked "factory reset" and i hoped that this would fix my problems
it booted, and rebooted, and rebooted, (bootloop for 3 times), and then finally: it booted normally..
all apps crash again!
this happens every time i start it.
now it doesnt even boot anymore (stuck on htc logo), so what do you guys think?
faulty ram? warranty ?
edit: now my screen stays black, phone doesnt respond to anything.
Dunno, it's a strange one. Drop into fastboot and run:
fastboot getvar version-main
Then look on htcruu.com for a matching RUU, this is the ENDEAVORU.
BenPope said:
Dunno, it's a strange one. Drop into fastboot and run:
fastboot getvar version-main
Then look on htcruu.com for a matching RUU, this is the ENDEAVORU.
Click to expand...
Click to collapse
cant get into bootloader, phone died.
it has been charged this morning so its not an empty battery.
i did NOT root, flash or unlock my phone.. i've only updated through "settings" in my htc.
(want to use it for a year before unlocking.. because warranty will be voided)
Try plugging in a mains charger, does the charge light come on within a few minutes?
Now plug into laptop USB, charge light? Anything in device manager?
BenPope said:
Try plugging in a mains charger, does the charge light come on within a few minutes?
Now plug into laptop USB, charge light? Anything in device manager?
Click to expand...
Click to collapse
This is so weird, charger LED will not turn on when connected to the charger.
i tried connecting it to my pc, same problem: but with an error:
"usb device not recognized" (yellow warning triangle near the error)
its completely dead, not responding to anything or any input.
before it died, i did try 3 factory resets with a full battery (and i didnt touch it)...
none of these factory resets fixed my problems.. :/ well atleast htc cant say "try factory reset" .
since the bootloader is bricked, the phone isnt even responding to charger and it wont "try" to turn on..
i think my phone is completely dead.. just have to send it back to htc (during christmas..! will take longer than
normal i guess).
the weird thing is, i havent done anything wrong to my phone.. havent flashed, havent updated the bootloader, havent rooted it or even installed another recovery or rom. (i've only dropped it once, the screen broke immediatly.. got it fixed by my phone-insurance company thats certified)
any other solutions? would htc let me pass the warranty and repair it for free? (its just 3 months old)
Dude that's one of the best and funniest starts to a post lol
'Dear xda developers'
In serious response though. HTC warranty is two years should be fine. They will ask for proof of purchase. If you havent got it they might still do it. Failing that and they don't. My normal advice is mail your regions ceo and complain then they'll do it most probably
Sent from my HTC One X using xda app-developers app
VitanyLTD said:
Dear xda-developers,
about a month ago my phone started acting funny, sometimes my browser or youtube would close randomly.. well, if it happend i just thought “oh, i pressed home accidentaly” or “oh its just a bad coded app”..
just 15 or 20 days later, not only my browser or youtube were crashing down.. it took my launcher with it (resulting in htc-sense prompting LOADING... for 2 minutes).
well, so far it has been “just annoying” me but my phone remained "functional" but: update saved the day and fixed this problem :laugh:
untill yesterday: all apps started crashing (including PROCESS ANDROID.PHONE etc.), a reboot fixed the problem.
today, all apps crashed again.. reboot didnt fix it, and my phone got stuck on boot sometimes (sometimes on the "ONE X" rom screen, other times on the "HTC" screen).
so, what did i do? what everyone would.
i started my htc bootloader, clicked "factory reset" and i hoped that this would fix my problems
it booted, and rebooted, and rebooted, (bootloop for 3 times), and then finally: it booted normally..
all apps crash again!
this happens every time i start it.
now it doesnt even boot anymore (stuck on htc logo), so what do you guys think?
faulty ram? warranty ?
edit: now my screen stays black, phone doesnt respond to anything.
Click to expand...
Click to collapse
Brick it to the store. Maybe warranty it out or insurance replacement.
Sent from a horny pink pony on my s3
gunz.jones said:
Brick it to the store. Maybe warranty it out or insurance replacement.
Sent from a horny pink pony on my s3
Click to expand...
Click to collapse
I send it in to get it fixed, it was the main board.
Hello there. I have to write this again becuase the last topic I wrote didnt get posted...
I have a big problem with my G3 and I have tried everything I could but nothing helped so I hope you can help me.
First of all my phone is only stock. I didnt try rooting it or installing custom roms on it.
Heres the whole story of what happened:
A week ago my phone started to act strangely. When I tried turning the wifi off it restarted or froze for a bit and then went on normaly as if nothing happened. I didnt even have to input my pin. Then one day I got home and the phone simply started reseting itself constantly. Always loaded up to the pin screen but I didnt even have time to input the pin and it reset it self again. This went on for like 15 reset before I lost patience and pulled the battery which didnt help at all since after being turned back on it went back to the reseting. I found online that it was probably a battery problem but I was impatient (shipping to my country is over 2 weeks and buying a battery in stores here costs twice the normal price of a genuine battery but only for a "fake" battery) so I factory reseted it via power button+volume down. After that it worked normally but I lost all my data.
The day after this I spilled ice tea on the phone. I opened it, cleaned it and let it dry out. Turned it on after an hour of drying and it worked but after maybe 2 hours it began freezing. When I tapped on the screen it didnt react, when I pressed the power button it took more then 10 seconds to react to it. It turned on, didnt react to touch and then in mere seconds it went dark and then turned off. I couldnt even unlock the screen. Tried pulling the battery but then it wouldnt even turn on. It stayed on the LG logo. I left it on the logo and on the charger and after an hour or so it turned on and worked normally so I took it apart and cleaned it once more even under the screws and such and it worked after that. Until today.
The freezing problem returned. I was playing a game on it and chatting via messenger when the phone stopped reacting. I had signal, wifi, I got new notifications and basically everything on it worked but the screen didnt react to touch and when pressing the power button it took over 10 seconds to light up the screen, then it went darker and then it shut down. Couldnt do anything. After I pulled the battery it would get stuck in a boot loop for maybe 10-15 minutes and then load but the phone couldnt be used. Just as before the screen turned on with a delay but no reaction to touch whatsoever.
I tried factory reset, downgrading to a lower android version (from 6 to 4) with LGUP and lg flash tool, and I bought a new battery. Nothing worked. I managed to get it to android 4 but that didnt help either. I though it was a problem with 6 because the problem started after the update, before that I didnt have a single problem with my phone.
Now its in a state where it doesnt work. The phone is running, apps are upgrading after the factory reset and all that but I cant do anything with it. Once in a while it will work normally as if nothing but that is rare.
Could you please help ? I love this phone and I dont want to have to sell it for spare parts.
EDIT: I left the phone running to see what would happen an after several hours an error message appeared saying "Process system isnt responding". After pressing ok it worked fine. How can I fix this. I googled it but all I found was a problem with sd card (none is inside), with battery (I have a new one) and with rooting (mines not rooted).