Related
Hey
I have a problem, my phone keeps rebooting, i have rootet it with the Hero Rom, and yesterday everything worked perfectly, but when i wanted to use the camera i little while ago, the phone restarted. So i thought i would try andd do a phone reset, but when i did, the phone keeps restarting, it shows the HERO logo, and then kind of reboot, the screen goes black and its showing the HERO logo again. It keeps doing that until i take out the battery.
Can any1 help me with this problem? any suggestions will be appreciated, im kind of desperate
Per
omg i having the same problem...did you fix your phone yet?
I'm having this problem too Anyone have a solution? My HTC Magic just keeps showing the "htc" logo and refreshes every ~5 seconds. Tried taking battery and microSD out, no luck. The last app I used was Alarmania.
i wonder if i could download a different rom to a different sdcard an then load it up to my MT3G
Issue Solved!
I just called Rogers and spoke to a very helpful Rogers tech support rep. This is the solution he offered and it worked for me:
1. When the phone is off, press and hold the Home and Power button until the phone comes on.
2. You should see a little icon with an exclamation mark. Now press and hold the Home and Power button again.
3. You should see some instructions and some options. Use the trackball to select Factory reset. This will erase all your phone's data, but if you're in the cloud (ie your contacts are with Google), you should be fine, you'll just have to reconfigure everything (ie mail accounts, keyboard calibration, home screens, app downloads and preferences).
I hope that helps. I just spent a very unhappy 12 hours without my phone.
FYI: I have a non-rooted Rogers HTC Magic with no mods whatsoever. The problem started one random night when I wasn't using my phone, it just got stuck at the HTC logo like it was about to restart, and it just kept refreshing the logo.
dang my phone is rooted
Another 24 hours later and I have the same problem. My phone went into a perpetual restart last night, it just got stuck at the boot screen, so I had to do a factory reset again. Any advice on what I should do? The nightly factory reset is not a solution.
Spoke to someone on another forum with the same problem. This problem seems to happen when you use alarm clock apps. The problem happened to me whenever I was setting an alarm in Alarmania or Alarming. I'll try the phone without an alarm clock app and keep you guys updated.
I've been doing a lot of research on this the past week. I did not have this problem on my sapphire until after I rooted my phone. I've tried 3 different android custom roms. They all seem to work well at the beginning and then the random reboot occurs maybe a day or two into regular use.
Whats seems to be interesting is I've heard a lot of people in the US say it was after the 1.6 update. So I'm going to try using 1.5 again to see what happens.
I haven't even tried the HERO Rom. I had no interest in it I just wanted my phone to run faster. This could be an underlying problem in the android OS. It could also be the crappy HTC quality starting to come out .
this is the first thread that I've seen someone who didnt have a rooted phone with this issue. Could mean it IS a hardware thing.
Anyways I'll keep you guys posted. Its a crappy problem for sure.
try using another sd card,format a new sd to fat 32 ,copy paste the custom rom you want,boot into recovery mode,wipe data,wipe cache and flash the rom,that works for me.
kerdum said:
I've been doing a lot of research on this the past week. I did not have this problem on my sapphire until after I rooted my phone. I've tried 3 different android custom roms. They all seem to work well at the beginning and then the random reboot occurs maybe a day or two into regular use.
Whats seems to be interesting is I've heard a lot of people in the US say it was after the 1.6 update. So I'm going to try using 1.5 again to see what happens.
I haven't even tried the HERO Rom. I had no interest in it I just wanted my phone to run faster. This could be an underlying problem in the android OS. It could also be the crappy HTC quality starting to come out .
this is the first thread that I've seen someone who didnt have a rooted phone with this issue. Could mean it IS a hardware thing.
Anyways I'll keep you guys posted. Its a crappy problem for sure.
Click to expand...
Click to collapse
I can confirm this. I have a mytouch 3g, and with 1.5, the camera was working fine. As soon as I got the OTA 1.6 update, the camera would cause random rebooting.
I called T-Mobile USA and had a replacement phone sent to me. I got the phone, didn't install any apps, and waited until I got the OTA 1.6 update again, tested the camera several times, and got no reboots. I flashed dwang's 1.6 ROM and I am still reboot-free.
this prob anyone got fixed??
hi there,
it seems as if i had the same problem. i got an htc magic with android 1.5 (swiss edition), i guess, and after i installed alarmania and had it alarming, it rebooted. instead of showing me the home screen, it just shows a htc brand and makes a sound, and repeats this after maybe 30 seconds.
i tried taking out the battery for some minutes, didnt work. i tried to go to safe mode (pressing menu and power), but it fell into the same circle, as well as when i tried to do a factory reset. i also tried to take out the battery for 20 hours, but same reaction.
does anyone have an idea what to do? ill try to call htc tomorrow.
thx for your help,
aeronaut
ps: please excuse my bad english, but im swiss. this is the only forum where i found similar problems to mine.
aeronaut said:
hi there,
it seems as if i had the same problem. i got an htc magic with android 1.5 (swiss edition), i guess, and after i installed alarmania and had it alarming, it rebooted. instead of showing me the home screen, it just shows a htc brand and makes a sound, and repeats this after maybe 30 seconds.
i tried taking out the battery for some minutes, didnt work. i tried to go to safe mode (pressing menu and power), but it fell into the same circle, as well as when i tried to do a factory reset. i also tried to take out the battery for 20 hours, but same reaction.
does anyone have an idea what to do? ill try to call htc tomorrow.
thx for your help,
aeronaut
ps: please excuse my bad english, but im swiss. this is the only forum where i found similar problems to mine.
Click to expand...
Click to collapse
This won't help you at this point but there seems to be a trend happening. Could it be Alarmania!? My suggestion would be to not use that app as it seems to cause problems. As per the camera causing the same issue, I'm not sure if there is an update for your phones but I just recieved an update for mine (Rogers HTC Magic) and I also got stuck in a boot loop after installing the first update. I had to use a Mini SDcard adapter that I purchased at my nearest electronics dealer for ei. BestBuy. It came with a class 4 4gb SDcard and it fits on my keychain. Basically you can use this to put a new IMG on your SDcard and then reboot your phone into fastboot. The IMG will automatically install (just follow the instructions). One issue may be finding the new correct IMG that you need but I`m sure you won`t have too much of a problem finding it on an established forum such as XDA. Good luck
thx for your help, but im not able to "restart" my phone normally - as i said, not even the factory reset mode is working. any other idea without flashing the ROM?
flashing only
thank goodness I've made recovery image just before installing Alarmania - Alarms is the same
Alarmed Litle is one that worked but it crash every system start
I was having the same problem, but this, which I found on the "Canadian HTC Magic Gets Sense UI and 911 Fix" threat at androidguys.com
"If you're getting the never-ending boot screen, your phone is -not- bricked. you just haven't finished the second part. you NEED a micro-sd adapter. Turn the phone off (take out the battery), and have a micro-sd card adapter. while the phone is off, take out the sd card and plug it on your comp and delete SAPPIMG.zip from the memory card. Once that's deleted, you need to extract "HTC_Magic_Update_File2.zip" and move "SAPPIMG.zip to the memory card (it's got the same name as the first "SAPPIMG.zip" file, but the second one is supposed to be around 85mb, so don't confuse the two) after that, just repeat steps 3-8 from the first part and that should finish the update on the phone. (this part takes a while, so be patient)"
Cheers
Yes but it is only when "flashing phone was aborted".
It is not for "after instaling Alarmania" on a phone without
Sense UI.
Data WIPE not worked for me, only reflashing phone with my saved flash image (thank gooddess that I've backuped my phone beforehand) done the trick.
well, its funny, i understood the reset page on the htc homepage wrong - i called their hotline, and i was able to reset it. but some days after, i have the same prob. i dunno if it is caused by any other app i have installed during these days (i do not remember as well), but ill try to get a newer rom onto my magic
First of all, sorry if this thread is out of place, but I'm not sure where else to turn.
My HD2 worked terrifically with FroyoStone 3.2, Hastarin 7.6 up until last Wednesday (5 days) ago. Then I started to experience, and have not been able to fix, serious TS lag issues.
Symptoms: I hit the unlock button, swipe to unlock, and the touchscreen will be responsive if I KEEP using it...if I pause for up to 3 seconds, the screen is no longer responsive. I have to relock the phone, unlock, and then swipe again to get it to work.
The touchscreen works perfectly fine in Windows Mobile 6.5. (Energy 2361X)
Attempts to fix: I've formatted the SD Card inbetween trying all of the following items-
1) Switch to MDJ ROM with MDJ kernel
2) Switch to Bluetopia ROM (0.5, 0.6 & 0.6.1) with Hastarin 8.0 OR 8.1
3) Switch back to FroyoStone 3.2 with kernel that comes with it
4) Update Radio ROM
5) Update to new Energy WinMo ROM -- after running Task 29 first.
Today, I purchased a new SD Card, loaded it with a clean install of Android, still have issues.
Also tried:
1) Turning off all LED notifications
2) Disabling Auto brightness in WinMo and Android
3) Disabled Screen Auto-Rotate
Honestly, I'm all out of ideas, and I hope someone in the community has a way to help out. I find it so odd that the touchscreen works great right after a "wake-up" as long as I keep it constantly stimulated...then fails to respond if I let it sit for more than three seconds. Is this a polling issue?
All ideas are appreciated. Thank you
UPDATE:
Followed another thread that suggests using the exact same WinMo ROM as the Builder -- matched my ROM with cmylxgo's WinMo ROM (author of Bluetopia) after another Task 29...no fix.
More Information
UPDATE 2:
Also tried 32K clusters and 64K clusters when formatting the card. Problem exists with either size.
There are G-Scripts to disable the G-Sensor and then re-enable it without rebooting.
If you want to jump to the extreme and want to remove all the sensors entirely.
Code:
su
rm -rf /system/lib/hw/*.sensors.so
Terminal
Thanks for your quick reply.
Unfortunately, I'm not the best with working with Linux/Terminal commands -- I tried typing in your code, and it returned that there was no such file/folder as -rf, and then I removed that section, and it said that it could not find the system/...
So obviously, there's something I'm missing, or an error in the syntax, that I cannot debug.
Any help is appreciated.
Are you having any data freezes or are you on an area with poor to no signal? I get really bad system lag when I loose signal while my phone is trying to download. Ppp will freeze and the phone will be unresponsive till reboot. Only way I avoid this is to turn off data if I got into a building I know I will loose connection in.
Sent from my HTC HD2 using XDA App
Updates
Thank you for your reply --
I checked into the disconnects being an issue by enabling Airplane Mode and seeing if I still had the same results, and unfortunately I do. I tried by disabling the Wifi and Mobile network separately, and still same issues.
But, here's an update on the issues:
Installed TYTUNG's NexusHD2-FRG83 V1.6, and this thing is very, very lightweight. Great battery life, great data (went to sleep, woke up, and not only was my phone still on...but I didn't have to reset data to check email...nice). The issues still remain. These are the newest things I've tried:
1) Remove Boxwave screen protector
2) Run from Airplane Mode.
I did however notice something really, really important: when the screen freezes, if I simulate a multi-touch gesture (pinch to zoom, etc), sometimes it wakes up! This is not a guaranteed thing (like 60%), but definitely something to work with.
Also, I noticed that one time that the touchscreen stopped responding, I tried the multitouch, no help...but I stayed on it. Multitouch tapped like crazy for a solid 6 seconds...then tried to shut the screen off -- and that button didn't respond. It was as if I saturated some bus of some sort that it had to clear out before it could finally shut the screen off.
Finally, I've noticed that the screen just needs to shut off for the touchscreen to unfreeze -- not go into a full lock situation. So, if the screen goes black, and I hit the lock key immediately, it'll unfreeze the TS.
Thanks to everyone who is trying to think of an idea!
i seem to be having the same issues as you right after i wake the phone up to unlock it. locking the phone is a habit for me to try and save as much battery as possible and also to not press any buttons while in my pocket.
im running a cyanogen rom and i changed the setting to allow me to unlock the phone by pressing the center windows key. i noticed that when the phone will not allow me to unlock it i can press the menu key and unlock it but i cannot use the touchscreen at all until i relock and unlock.
sometimes i have to do this a few times before the touchscreen comes back. i was thinking it could be my sd card but this started to happen today. i have been using android on my hd2 daily for the past 12 days without any problems. its weird that it started all of a sudden.
so it seems we still dont have a fix for the touchscreen freeze yet, right ?
Same problem here
Hi, I am experiencing the same problem.
Tried few versions of Android, The same problem repeated itself.
So I had to return to WM6.5 - there it works good. Only I have to reset the phone twice a day :-(
Hope someone will find brilliant solution for the sad problem that prevents using Android...
i've had this phone for a few weeks and everything worked fine. I flashed chucky's rom, and ran CoreDroid Evo Supersonic from the SD card. it worked great. yesterday, the touchscreen stopped responding if i'd wake up the phone with the red button, but the others worked fine. Now, i have to try 10-20 times with any button for the touchscreen to work. The same thing happens in Windows Mobile. I just flashed to a different ROM, and the same problem occurs.
could this be a radio issue?
Well this is something that helped me, cant rly tell if my fix will work for you but try this. Drain your battery until the phone shut down on its own and then charge it fully. Do this few times and hope to god it help
i have absolutely no idea how that would work. i'm assuming you had the same problem as me?
Yes ofc it's a known problem, you can see many post about it. Touch screen wont wake up when you use end call button, its a hardware issue. Well the best solution to its to send it back for replacement, but I didn't have that option unfortunately.
but it won't wake up with any of the buttons i press, not just the end call button.
The other day I installed the new CM RC2 rom on my HTC Wildfire. Everything went fine for the couple of days until it went into sleep mode and I could not come out of it. I had to pop the battery and when still problems, I re-installed rom - again with flashed kernal 4.1 and up to date gapps.
Managed to get it working. But then same thing again. Overall I had to re-install 5 times yesterday alone!
Out of frustration I tried to re-install my CM RC1 from before with the kernal 4.1. And this was fine again for about an hour, then again, mobile went into sleep mode, and again was left with black screen. Again not able to come out of it.
Am at a loss as to how to get my mobile back up and running. If anybody can help, this would be most appreciated.
Thanks
Does this happen with all ROM's, or simply CM7? Also, what are your overclock values and SetCPU Profiles, if any?
Have only tried cm7 so far. and cpu was not touched. was left at default settings. Am not able now to even boot into recovery. Totally DEAD!
Probably a hardware issue. I doubt CM7 can have such far reaching implications as to make the phone dead. Anyhow, this issue looks uncannily similar to this
Thats worrying.
If I do manage some how to get it switched on, is there anything that you can suggest to stop this happening again?
Also keeping the battery out of the mobile for a 5 mins, SHOULD that help instead of just taking out and imediatley replacing?
Doesnt sound too good. If you manage to switch it on you could try setting your minimum cpu speed to 245mhz+ Although it sounds like you have more serious issues. If its still under warranty I would consider returning it
Thats what I feared.
Thing is, cause it is rooted, it is out of warranty. I dont think I have a leg to stand on.
Its worth a try, they may not even check/notice that its rooted
Well.......
I managed to get it switched on. And decided to try and install Wildpuzzle as I had that on the phone before with no problems. And so all was well......
....untill just now.
Mobile went into sleep mode, and when I pressed the power button to get into it, black screen. Wouldnt come out of sleep mode. So had to pop battery again and after 10 mins, re booted it.
This seems to be the norm now. If it gets a chance to drop off into sleep mode, then I am stuck.
I am starting to pull my hair out.
Have just read on another thread that should try turning off auto rotation and auto brightness.
Fingers crossed this will work.
If the problem occurs throughout various ROMs it could well be hardware related. Flash an RUU (this will get rid of all traces of root) and return it
Will do.
Thanks
cant access cm7 rc2
any ideas why i cannot access or see any file in the website download.cyanogenmod.com regarding cm7 rc2 for buzz/wildfire?
First off, Sprint S4, I had LiquidSmooth until it suddenly broke (apps gone, settings went wonky, lots of sudden glitches) so I've been trying to fix that. When I cleaned flash, it worked for a while, than it kept turning off and not getting out of the boot screen. I've tried with many roms and the stock one and it just wont cooperate with me. Also I'm having troubles charging the phone. It keeps malfunctioning when I plug it in but it charges, the original wall charger won't work for it when the cable is fine but it worked with a different cable and outlet. Something is VERY messed up and I'm not sure what to do anymore. I keep doing the three wipes and flash but it's now stuck. Is this a hardware issue? Radio issue? I don't know but I really need help.
It's really hard to explain. It acts out whenever it's charging and i made one rom boot up thought it didnt have wifi so I'll experiement getting liquid smooth on it again. I dont know why suddently the it's giving me usb problems and why roms just suddenly break
Liquidsmooth booted and now Im getting a "unfortunatly, contextprovider has stopped"
yup, did it again, at the boot screen the message wont go away and behind it is something requesting root
fought through it and just giving me problems. Going to instead of flashing "L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar" with ODIN ill flash "L720VPUFNG2_L720SPTFNG2_L720VPUFNG2_HOME.tar"
It booted and reflashing to liquidsmooth is stuck at boot
Ok, I "think" i got it. The clock stopped once and that made my heart skip a beat. As long as it doesnt take a **** again and shut itself off and refuse to propertly boot, it should be ok.
Also please excuse the typos, I've been at this for 2 days straight.
Would an APN flash do this?
WTF I saw a duplicate dialer, one went away, two clocks, one crashes, and home button doesnt work
Ok, one is native and one is GAPP and now titaniumbackup cant restore the proper ID,
Ok 2nd times the charm, home works but Titaniumbakup ID won't restore
Nvm. Home still doesnt work but it does in key test in custom recovery
Ok, im PRAYING this NANDroid backup holds