[Q] Android reboots after 1-2 minutes - HD2 Android Q&A, Help & Troubleshooting and Genera

My HD2 was running fine on several versions of Android, currently mccm v1 SE with 2.12.50.04 Radio on top of Stock WinMo with SPD whatever thing.
I have a 2GB and an 8gb microSD. the 8gb holds my stable mccm v1 SE and the 2GB is for testing other builds.
I wanted to speed booting to Android, so downloaded chuckydroidROM and Excellor boot loader (v2.1).
I installed the boot loader and it ran fine with my HyperDroid 1.6 build.
But then, after about 3 minutes. The phone reboots to T-Mob welcome screen. It doesn't load WinMo either, unless I reboot manually with the battery or reset button.
I've been looking and looking on the forum and can't find someone with similar circumstances.
I've tried my stable 8gb microSD card with the mccm v1 SE build on it and I get the same thing.
what I've tried:
-"hard" reset (Up/Down volume button reset) = same + lost SPD mobile
-Changed radio to 2.15.50.04 (yeah, no good) = same + no signal
-installed chuckydroidROM = same
- uninstalled EBL = same
- reinstalled EBL = same
- stomped and yelled = same.
Any help? either a thread that I missed in my search or some other things to try?
Thanks guys.

Hmm sounds strange.
But I think you have to start from the beginning.
At first, what version of HSPL do you have installed?
Maybe just try another one, mine is currently 2.08.
Then you should do a task29 before you flash the WM-ROM again.
I recommend also flashing the 2.14 radio.
After finishing these steps prepare your SD. Format it with the formatting tool found here: http://forum.xda-developers.com/showthread.php?t=748961
I would do this 2 or three times.
Then do a fresh install of your android build. Just set up as normal.
If you want to, you could try to restore your data.img. If you do that, it has to be a build from the same developer.
Try and report back.
Cheers

thanks for the reply. I updated to 2.14 and went with a stock 2.2 build (Nexus One). It hasn't crashed since, but I'm afraid to go back to my mccm build. I also am kind of worried that it had something to do with Excellor on the device. Of course I can't resist trying again
I'll try my original build again. I do know that I formatted the SD card well before installing this build, so that might be it. I didn't have the program though, so thanks for the link. Also I didn't look into task29, so I'll read up and find out if that might help.
I am running 2.08 too and was then. I did reflash it though.... but I don't think that was when it started working again.
I didn't know that data files may be portable if from the same dev. that's nice to know. Thanks again for the help, it's a lot easier to work through fixes with the help of a few other brains.

Cheers
- J

Sent the phone in. got it back in five days. Fixed. It must have been heat. I'm running all day now. Thanks for the help.
Sent from my HTC HD2 using XDA App

Related

[Q] Android keep rebooting

Hi,
I have tried flashing different roms from different cooks.
So far, I am able to get Energy, Mattc to work.
Hyperdroid and Froyostone will have auto reboot back to wm.
Since my phone is able to boot to the other 2 roms, I believe what I did was correct.
Is it due to Radio rom incompatibilities? or just my luck?
i have tried radio 2.12.50.02 and 2.10.50.08
the symptoms is that it will boot up after i run clrcad and haret.
once sense is about to boot up, it reboots to WM.
i am using latest Energy wm rom.
any advice will be greatly appreciated.
thanks
jack
Are you using an extended battery? Currently the kernel can only read out temperature from the stock battery
Use the kernel in this thread, works great for me:
[Kernel][Overclocking][Undervolting][Extbatts] [email protected] #139 (r10)
It's in the Android Development section
Sry, seems i'm nt allowed to put links on because I'm a "new" user.
thanks for your reply...
I am using stock battery.
i only have problem with Hyperdroid and Froyostone.
i have reformated the SD card...and reloaded.
no use. i have loaded back mattc...without reformating
it works.
thanks
jack

Robot Voice, Music Speed Faster Than Should Be...

Hi I recently updated my android from mattfroyo sept 29... to oct 1 nexus one... mattfroyo was perfect but i wanted to try something new... when i updated to nexus one everything went to sh*t... i have robot voice on both builds now...and cant figure out why... i restored phone, formatted sd card, tried different roms...and nothing works... i feel like i ruined my phone... now no android workkkks =(... i have 2.12.50_2 radio... runing miri hd2 v19... tried elegancia miri... and elegancia gtx... plz help
I get this from time to time. In your case I would remove the SD card and format it.
Reflash you WM rom and reinstall the radio. Go right back to the beginning.
i will give it a try thanks...
I had this exact same thing happen, and I fixed it by re flashing my radio. After that the problem was solved. Good luck with it.
Damn I tried everything! Flashed new rom new radio formated sd and downloaded new fresh froyo builds and there is still this fast sound...what for a rom, radio and android build are you using when it´s working on yours?

[Q] HD2 will not boot. Help needed

I got myself a HD2 the other day, and since i am a androidfan i wanted to get my HD into a droid rom.
This ended in a mobile not wanting to boot, got to the boot screen where i se the android sign and then it reboots. This goes on forever...
HSPL works (have tried different versions) so i can keep trying different roms, but all ends up rebooting the phone. Doesnt matter if i tryWindows 6.5, android or windows7 roms.
But another problem is that i dont know which Rom was my "original" rom, and i formatted the original sd card...
Hope one of you clebver guys have an answer and solution i can try out.
Here are som info that shows in the boot screen now:
R 2.15.50.14
G 15.42.50.50.11U
D 3.14.04666
How did you exactly try go get yourself 'into a Droid ROM'? From SD card or nand? What bootloader do you have? 2.08.Hspl or 2.08.0000? Just go in to Bootloader and flash a custom WinMo ROM or MAGLDR if you want to flash Android from NAND.
Sent from my HTC Vision using XDA App
I have 2.08Hspl bootloader now.
Have tried with Magldr with no luck. Have tried both Sd and Nand version
Still no luck
LordPalo said:
I have 2.08Hspl bootloader now.
Have tried with Magldr with no luck. Have tried both Sd and Nand version
Still no luck
Click to expand...
Click to collapse
I've tried several ROMs & each time they boot up wonderfully, whenever i encounter a problem..its usually cuz i either skipped a required step or didnt fully understand how to get that particular ROM working...So my advice 2 u is to follow the dev's instructions properly in order 2 minimize errors...feel free 2 try d build contained in my sig...With normal usage, i still squeeze out @least 30hrs+ out of my device(calls, msgs, wifi, data, sync, really low back-light, apps, games, etc)
Aaaahh!
Found the solution to my problem.
It was one of the battery contacts that was bent out.
Bent it back into place, and now the phone boots like a Dream
Let the android testing begin
I only suggested that to somebody else today and All! Haha.
Sent from my HTC Vision using XDA App
If you want NAND version, you need hspl 2.08, magldr, and cwm in order to flash rom.

[Q] No screen input from android / wm

Hey guys, I need some quick suggestions if anyone has it. Currently I have a non working phone.
I have been running an ICS NAND rom on my hd2 for a while now, havnt had any issues (a few niggles with the rom, nothing major) so I thought today I would update to the latest version.
I used the hd2toolkit to resize the partition to the biggest size it would allow, then used ad recovery to flash the new .zip to the nand. This is where my problems started, whenever i booted it just showed the boot animation, (I waited over an hour and pulled the battery out and re booted / reflashed a few times).
I found with a differnet rom i tried, pulling out the SD car would allow it to get to the welcome screen, but no screen input was accepted. I thought this was a bit weird but pushed on. I tried a different rom and it stated after flashing that it was optimising applications and looked like it was stuck in a boot loop. I did some reading up about it and found that task29 should help. I ran this but then all the phone would do is show the green HTC on the white background, it wouldnt let me to get into magdlr menu.
I then decided to to a full restore and go back to the wm rom from th HTC site (The australia telstra version), this seemed to flash on fine, but now I can not slide or click buttons in wm, no screen input is accepted. Which is strange as it was doing this in an android rom, as I mentioned previously.
Any ideas on how I can get touch working / get a NAND android rom to work again.
Thanks in advance guys
First verify that you have hspl installed by powering on while holding vol down button to get to bootloader screen
Go back to the hd2 nand toolkit
1.task29
2. Select either cLK repartition or Magldr repartition and select size for your rom (not the maximum size). 200 mb is fine for ics using sdext partition.
3.Select magldr update recovery or cLK install recovery depending on your selection above.
4. Reboot phone by pressing power and holding to get to magldr or power and home button to get to cwm recovery.
5. Install ICS from sd card as before
Thanks for the help, I had to flash a different radio version to get magdlr to boot.
I now have android running of my NAND, but the screen is non-responsive now, as it was yesterday.
I doubt it is hardware related, because I have never had an issue before yesterday when I wanted to change the android version, any ideas how I could get it working?
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
htccraze said:
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
Click to expand...
Click to collapse
I have tried two different android roms and the stock wm image from htc's site, all of which the screen doesn't work on. I will have a try with a cyanogen ROM and see if that makes a difference. Thanks
http://forum.xda-developers.com/showthread.php?t=769026
I just tried this rom and still no deal. This is very weird as I haven't had any issues with the screen at all, the phone is still in new physical condition.
Does anyone want to have a stab in the dark, as I really need to use it as a GPS tomorrow and any help would be appreciated.
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
htccraze said:
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
Click to expand...
Click to collapse
When installing a new rom, I have resized the magdlr partition, then copied the .zip to the sd card, then in ad recovery installed the zip through there. This has worked fine in the past. I followed the videos you have linked and I'm pretty sure I'm doing everything right and yes ive used task29 several times. In AD Recovery every time it states that installation has been successful. I have also formatted my SD card many times.
The ROM you linked, I can find download links on the page, not sure if I'm just missing them.
I just tried an SD card rom, its doing the same thing, no touch input is accepted.
Does NAND roms and SD roms not working imply that it could well be hardware? I just dont understand as it stopped working when I was reflashing yesterday and it was not dropped or roughly handled in anyway during this process.
I am now going to investigate MTTY (for bad blocks) and try reflashing back to original WM again. Please post more suggestions if anyone has them.
Another update: I just restored to default using the method listed below.
http://www.jayceooi.com/2011/08/15/how-to-restore-stock-rom-on-htc-hd2-video/
It took around 40-ish minutes and still no input from the screen, this is seriously frustrating.
WM boots fine and everything, but still no input is accepted.
I'm sorry to say but if your having the same problem with all that then it sounds like the digitizer stopped working. Maybe someone else knows something I don't so I would wait to see if they could help out.
Sent from my HTC HD2 using XDA
Thanks mate, I am not sure why it would have just stopped last night. Appreciate all the help! I'll see if anyone else has any suggestions.
It's not a problem. I do have to admit that it does seem pretty odd the timing of it. Hopefully it's a not the digitizer and someone would be able to point out what might be the cause of everything.
Sent from my HTC HD2 using XDA
This may seem a little crazy, but after having a search online about my issue, it seems that a ribbon going to the screen / digitizer is behind the power button on the HD2s, which apparently can get loose and after a sharp press of the button it started accepting screen input again!
The issue for me now is that when the power button it will stop accepting input again, untill I press it firmly again. I think I may need to open up the phone and check all the connections now.

Location kills my device (on multiple OSs)

So I was using WP7 and whenever I turned on any navigation app (including Bing, which accesses location) the device would freeze and reboot.
I thought it was a WP7 issue and reinstalled Android, and to my surprise, as soon as I tried to use a location-based service (Waze in this case) my device froze and rebooted.
So I'm guessing my GPS Antenna is pooched. Any idea how to better diagnose and/or fix this problem?
That's strange, definitely something up with the inner contents of your phone, try flashing a different Android rom and see if the problem persists? It would help if you told us specifically which wp7 and Android roms you flashed.
Regards,
Sent from my NexusHD2 using xda premium
I'm pretty sure it's HW issue because the symptoms are identical to the sound it makes when it freezes.
The WP7 Rom was Pdaimatejam, current Android ROM is IceCreamTosti v0.11 with Dorinmax Kernel.
Mate switch back to WM 6.5 and do a clean install
Before that try a task 29 or changing your radio
If nothing works, well then your radio must be pooched
Reverting to WM 6.5 does solve a few lame problems
P.S. please can I use your sign ? I <3 IT
Nitro_123 said:
Mate switch back to WM 6.5 and do a clean install
Before that try a task 29 or changing your radio
If nothing works, well then your radio must be pooched
Reverting to WM 6.5 does solve a few lame problems
P.S. please can I use your sign ? I <3 IT
Click to expand...
Click to collapse
I'll try it as a last resort, although I DID do a Task29 already.
Thanks for the tip.
You can use my sig, sure
Ah, well. It's my birthday this week and I've been eyeing the HTC One X, what a better opportunity to upgrade
Update: Full Task29 (No Radio) + Installed WM6.5. To make sure, I started Google Maps and checked that it works, it got some satellites and actually worked!! (gave it about 5 minutes to make sure).
Then I Installed CLK over it + Recovery Wipe + Installed Android over it, now testing Waze.
So far so good. I'll have to give it a driving test, but so far looks like it's at least a little better.
Thanks for the tip again!

Categories

Resources