Hello all,
BIG problem here.
A few hours I update the MildWild oxygen rom from 4.6 to 4.6.5. For a few hours everything went totally amazing. But a few minutes ago I turned on wi-fi, but he didn't connect. So I went to MySettings app, but he didn't response. Nothing worked anymore. Only screen of and on, but then I hadn't also the lockscreen. Then the screen turned off, and I couldn't get it on
Pulled the battery out, and put in back in, but my phone didn't restart. Now I plugged in the charger, even the light of charging isn't turning on.
What the hell is the problem with my Desire? He can't be broken in a second if everything worked super well a few seconds before that all?
Tried a different battery but also then he isn't doing a ****... This whole problem came just out of the blue, that's what makes it really awkward to me.
I hope you can help me, I don't want to leave my lovely Desire.
Greets Ramon.
After all sort of things trying, I thought... let's take the sd card out. And luckily he turned on, feels like heaven...
Sd card back in, phone worked also. Don't know what the problem could have been, but my Desire works again.
I hope this maybe could help some other people who had/have/ gonna have this problem!
Close thread please :good:
Hello,
This morning suddenly, the same problem happened... Turned the screen on, swiped to unlock, but during the swipe the phone hang.This time no fear, because I knew what I had to do: take out the SD card.
Too bad, this doesn't work this time. The problem is exactly the same as last time, but know even without the SD card, the phone don't boot, don't charge. Couldn't get into bootloader also. The day before yesterday I flashed Mildwild REDUX V1, but this worked good.
What could it be?
Thanks in advance!
Greets Ramon
Edit: The last time this happened, when the phone finally booted, I directly got a message called something like "android.....com stopped unexpectedly". So that was the reason the phone stopped. Now it would be the same problem I think, but I can't turn the phone on. I just called with HTC, and because I'm out of the warrenty period, I will have to pay the repair (if needed) I think it's not broken, it's probably the same problem as last time...
The phone 'works' again... But it's in a bootloop, and going to recovery results into a bootloop also so I can't access the recovery. So I flashed the recovery again using ADB, but still I get the bootloop! What should I do?
Related
So, I left my Artemis in my RAM Aqua Box waterproof phone case attached to my motorcycle while I ran into the store.
I came out, started the bike and started the ride home. That was when I noticed the white screen and my tunes had stopped playing. I've seen it happen before (while turning off the phone in camera mode, etc), but a simple soft reset always fixed it. Not this time...
For two days now I've flashed it back to factory, installed my latest ROM (twice), reconfigured all my settings, etc, only to have the phone seize up by fading to the White Screen Of Death. The only fix is to remove the battery and let it sit for a bit. I have found however I can get the phone to run longer if I put it in the freezer for 15 mins, then it runs as it should until it warms up.
Sometimes it will work for half a day, other times it will fade out even before the soft reset boots up again. It really doesn't like being plugged in to charge or sync.
Now for some more background info. It did get deathly hot in the case I have because it has a clear face, is sealed, and it was sunny. Also, I started the bike when the phone was plugged in. I've heard this is bad for the charging circuit, but I'm leaning to the overheating as being the seminal event of the start of my sorrows because I've started the bike/truck many times with the phone plugged in. Did my luck run out?
What have I done, and how do I fix it?
i have had a white screen problem on my phone to it would go like this when just left on or when wanting to flash it in boot mode i have taken both sim card and memory card out and i have found that the memory care is curupted and works fine now will have to formate the memory card in order for it to work properly in the phone again
htc artimis 02 orbit
Yes, you can remove your memory card.
Just had similar problem. Possible reason: ROM update. Possible solution - ROM changed again (different) and hard reset. Hopefully everything will be ok. Until now (9 hours) - it is!
SCREEN
Hello
sorry i speak english a little.My TC P3300 have a problem on screen.I replace the lcd screen because the old make a hole white every 5 s.With the new its the same.What happen
thanks
I have the same Problem I started getting the White screen when i try and access anything it hangs and then goes white screen I removed the sd 2gb and left the sim in and id stil did the same thing but now i put the 4gb out of my laptop and now it seems to work but i still get the power on problem sumtimes
Im running wm 6.5 Arte_WM65_23009_WWE_Fixed_IE_b1
Any sugeustions? help plz
i have same problem
Even I was facing the same problem. I did hard reset couple if times and didn't find a solution. So finally I gave the phone to the service center and it seems now it's been fixed. I will ask the service guys about the actual problem and would post it here.
It may help someone.
Now I am going to try android on my phone, wish me luck.
Regards,
Rajesh
rajeshrr said:
Even I was facing the same problem. I did hard reset couple if times and didn't find a solution. So finally I gave the phone to the service center and it seems now it's been fixed. I will ask the service guys about the actual problem and would post it here.
It may help someone.
Now I am going to try android on my phone, wish me luck.
Regards,
Rajesh
Click to expand...
Click to collapse
Did U ask the service guy abt the screen problem
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.
So I have this weird issue with my HTC ONE M7 for a few days now. It would turn off by its own when I was using it but I'd just turn it on and it will work again. I thought it may have something to do with a bad app or the rom might be acting up. Anyway I ignored it since turning it on was a minor inconvenience and I needed my phone functional. Today whilst using GPS, the phone suddenly went dead on me. Every time I boot it up, it passes the initial HTC screen but then doesn't boot into android. The screen goes black and the phone turns off by itself. I went it recovery, wiped dalvik and cache thinking it was an app causing a boot issue but that didn't help. The problem continued. I already had a backup so I went ahead and tried restoring it. It worked the first time. But the phone still won't boot. It would turn off automatically. Then I tried reflashing it with the backup. This time the phone would just turn off as soon as the restore process started. I finally got tired of it and decided to reflash with a new rom. The flash went fine. But lo and behold the same issue again. Boot animation and then black screen with the phone completely turned off.
I thought it might be the battery so I plugged it in to my laptop USB. It booted but when i was setting up android, it would just shut down again. Then I connected it to the wall socket thinking the phone will get more juice. This time around I was able to set it up. With the phone connected to the wall socket all was working splendidly. Please note that during all this time the phone was at 100% and there were no drastic falls in the battery levels.
As soon as I disconnect the phone from power, any power intensive operation shuts it down. I have been in recovery mode for 2 hours now and the battery hasn't even dropped by 3%.
So the question is, What the hell is going on? Is it the battery, is it phone's hardware or is it a software issue? Any help would be greatly appreciated. Cuz if it's something that can't be fixed, I have to start thinking about getting a new phone then. THANKS so much for bearing with me! Cheers!!
supratentorial said:
So I have this weird issue with my HTC ONE M7 for a few days now. It would turn off by its own when I was using it but I'd just turn it on and it will work again. I thought it may have something to do with a bad app or the rom might be acting up. Anyway I ignored it since turning it on was a minor inconvenience and I needed my phone functional. Today whilst using GPS, the phone suddenly went dead on me. Every time I boot it up, it passes the initial HTC screen but then doesn't boot into android. The screen goes black and the phone turns off by itself. I went it recovery, wiped dalvik and cache thinking it was an app causing a boot issue but that didn't help. The problem continued. I already had a backup so I went ahead and tried restoring it. It worked the first time. But the phone still won't boot. It would turn off automatically. Then I tried reflashing it with the backup. This time the phone would just turn off as soon as the restore process started. I finally got tired of it and decided to reflash with a new rom. The flash went fine. But lo and behold the same issue again. Boot animation and then black screen with the phone completely turned off.
I thought it might be the battery so I plugged it in to my laptop USB. It booted but when i was setting up android, it would just shut down again. Then I connected it to the wall socket thinking the phone will get more juice. This time around I was able to set it up. With the phone connected to the wall socket all was working splendidly. Please note that during all this time the phone was at 100% and there were no drastic falls in the battery levels.
As soon as I disconnect the phone from power, any power intensive operation shuts it down. I have been in recovery mode for 2 hours now and the battery hasn't even dropped by 3%.
So the question is, What the hell is going on? Is it the battery, is it phone's hardware or is it a software issue? Any help would be greatly appreciated. Cuz if it's something that can't be fixed, I have to start thinking about getting a new phone then. THANKS so much for bearing with me! Cheers!!
Click to expand...
Click to collapse
if you are s-off i would suggest doing an RUU and starting fresh. Its hard to pin point a problem without having the device handy and trying some things. The RUU will let us know if its a software problem or if its going to be hardware related.
Hey thank you so much for replying. I am s-off. But would going back to stock re S-On my phone? And how do I do RUU? Thanks again.
supratentorial said:
Hey thank you so much for replying. I am s-off. But would going back to stock re S-On my phone? And how do I do RUU? Thanks again.
Click to expand...
Click to collapse
Do not s-on! Just run the ruu eye dottat made
Installed RUU. The problem is still there. The phone can stay on for hours in recovery without a charger but as soon i want too boot into android it shuts down. It only boots up if it's connected to a charger and that too a wall socket not a usb hub cuz it goes some way into the boot process and shuts down half way. I am pulling my hair out here. Dunno if it's the battery or the mother board.
supratentorial said:
Installed RUU. The problem is still there. The phone can stay on for hours in recovery without a charger but as soon i want too boot into android it shuts down. It only boots up if it's connected to a charger and that too a wall socket not a usb hub cuz it goes some way into the boot process and shuts down half way. I am pulling my hair out here. Dunno if it's the battery or the mother board.
Click to expand...
Click to collapse
If ruu still has issues. It is motherboard or battery. From the symptoms, it sounds like battery as the phone needs to have some juice to fully boot the phone before being able to run off the charger.
Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)
1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)
2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.
3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.
4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.
5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.
6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.
7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.
8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.
9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.
10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.
11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.
Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?
Now, My question to you guys, WHAT SORCERY IS THIS?
Help me out people. Expert help needed. TIA
*sigh*
It's a faulty battery mate. The phone stayed in the factory reset screen because the battery usage was basically insignificant. When you tried to go to recovery mode, the phone used more battery and boom, dead phone Happened to me too, new battery solved it.
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).