Heya.
I am running Android Revolution 2.0.16, Kernel 2.6.32.29_BUZZ1.3.3_OCUV with radio Radio_12.35d.60.140fU_26.06.03.24_M2.
I've been running this for ~1.5 weeks and I think this started about 1 week ago, not sure. Sometimes randomly (sometimes when I'm playing and sometimes when the phone has been idle for few hours) the phone boots. I see the white background with the green HTC logo and after a while it asks for my Pin number. Sometimes this happens once/day and sometimes it happens three times in a row. With stock it never did this.
What could be the cause?
How could I fix this?
I'm interested in Android Revolution 2.1 but can't find it after the 3.0 and 4.0 came along. I'm not ready for unofficial Gingerbread yet and 3.0 is using 1.84 for Orange and I'm not completly sure if I should use it with my unbranded Finland located phone.
Thanks for your time!
Hi. This has nothing to do with the ROM you are running it is a physical problem with the phone and is quite a common fault on the Desire HD.
It is a problem with the placement of the SIM card underneath the cover. I just stuck a bit of selotape across the SIM card to keep it in place and mine has been fine since. Other than that flash back to default and send it back under the warranty.
I don't think it's about loose Sim card. I tried to move the sim card while the phone was on the finally removed the sim card. The phone didn't boot but I got a message that said that phone can't locate sim card and I must either restart or shut off the phone.
This isn't what I mean with the restarting. It just restarts, boots, without any error message. Like I would have pressed the power button and selected restart.
Its because of the kernel, like mine your cpu seems to be sensitive to undervolt, try leedroids kernel
Sent from my Desire HD using Tapatalk
So although all DHD have the same type of CPU, each specific CPU reacts differently to UC/OV? Strange, how widespread is this? Personally I've had no problems.
Had the same random boots with revolution 3.0 and 3.1, reverted back to stock 1.72 with the same(BUZZ) kernel and same setcpu settings as I used with revolution, and reboots are gone for me
Heya. Thanks for the replies. I was thinking going back to stock too but decided to try Revolution 3.2 and it seems to work. Atleast one day without boots, but we'll see how it's in the long run.
Related
I was able to boot into android perfectly fine until about a week ago where it would just hand at the boot screen. today i tried to fix it by formatting my sd card and doing a clean install. now i can boot into android perfectly fine, but if i leave my phone idle and let it sleep, after a couple of minutes a green led will turn on and my phone will not wake up and i am forced to reset my phone.
anyone know what the issue could be? i flashed a new rom today, but i doubt that has anything to do with this.
is my sd card bad?
viper786 said:
I was able to boot into android perfectly fine until about a week ago where it would just hand at the boot screen. today i tried to fix it by formatting my sd card and doing a clean install. now i can boot into android perfectly fine, but if i leave my phone idle and let it sleep, after a couple of minutes a green led will turn on and my phone will not wake up and i am forced to reset my phone.
anyone know what the issue could be? i flashed a new rom today, but i doubt that has anything to do with this.
is my sd card bad?
Click to expand...
Click to collapse
Do you have it overclocked in your startup.txt? That will cause this issue.
ahh yes, i overclocked it to 700mhz. so basically, i cant overclock at all without facing this issue?
Does anyone know if the Windows Mobile ROM on the phone affect how high one can go with an overclock? Like would using the stripped down ROM help to achieve a higher clock speed as opposed to using a loaded ROM like EnergyROM?
Yes, it seems the OC will crash android once it tries to sleep. One workaround some people have said works is add "htc_battery_smem.fake=1" to your startup.txt cmdline. Your phone will not crash anymore, however your battery life will be a little shorter due to the fact its not sleeping as deeply.
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.
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, I've had my DHD for a fair while now and installed mike1986's ARHD 5.x ROM when I first rooted my device. With the advent of ICS, I have been flashing the betas that have been out for the last few months, eventually got sick of the bugs, and flashed ARHD 7.0.2 earlier today. Ever since doing so my device randomly loses power when I use it - it is hard to pinpoint an exact cause, because the same thing can happen when I boot up a game or when the phone is sitting asleep in my pocket. I am also not sure if it is related to the new ROM or not, but I reflashed an older ICS beta to check, and sure enough the problem also exists on other ROMs now. It is also worth noting that the problem is absent when USB power cable is connected.
I've also tried different kernels and an update.zip that switches the OC daemon in ARHD back to the stock clock speed of 1ghz as it was suggested that perhaps my CPU doesn't like OC/UV. While running older ARHD and ICS ROMs my CPU usually hovered between 1.0 and 1.4ghz. I still get random power loss @ 1ghz.
Can anyone suggest a method/ROM/something to fix?
EDIT: Now, when I boot my DHD, HTC splash comes up, boot animation comes up, handset prompts me to enter PIN, goes to main home screen, and imediately loses power. Help!
Hi, I've got a similar problem. A week ago I installed RD-MIUI-ics 2.3.2_v4 [4.0.3] ROM. Since I use that ROM, my phone occasionally reboots for no reason. For example, when I play music on spotify and remove my headset without pausing the music first, it reboots. I wanted to post this on that thread but I am not allowed to post on the development page.
I did a full wipe before I installed the ROM the first time.
Any ideas?
I underclocked my CPU to 800mhz max and it hasn't crashed again... yet.
I have had my desire for nearly 2 years and had another android phone before that, and have been running custom roms for 90% of the time. My problems started (as far as I can remember) since I have been using Sandvold's ICS Rom since roughly beta 0.3.8.1 and recently nikez JB rom. The problem is that when I have my sim card in my phone it causes it to hang and freeze randomly and the only solution is to pull the battery and reboot. The freezes occur at different times, sometimes I can go for an hour, sometimes I can barely get passed booting before it freezes. Also half of the time the phone freezes then hot reboots (ie bypassing the splash screen and going straight to the boot animation) and stays hot rebooting until I pull the battery and restart. However, if I take my sim card out the phone functions brilliantly and doesn't freeze or hang at all.
I have tried searching but nothing sems to replicate my predicament.
Phone INFO:
Bravo PVT3 S-OFF
HBOOT-6.93.1002
Radio -5.17.05.23
SD - SanDisk mobile Ultra 16GB microSDHC
The title gives it away. Its probably the sim. Try a different sim to check.
via xda app
I do not have a spare vodafone sim to check it with, however, the sim card works fine in my other phone and only started playing up on my desire since I have been using ICS/JB, on GB it was running perfectly fine, which is the confusing part.
Delta1292 said:
I do not have a spare vodafone sim to check it with, however, the sim card works fine in my other phone and only started playing up on my desire since I have been using ICS/JB, on GB it was running perfectly fine, which is the confusing part.
Click to expand...
Click to collapse
Just one more proof that ICS/JB simply need a lot of more work to be done.
Simply go back to GB.