[Q] Mobile Network Unavailable After Installing Gingerbread - HD2 Android Q&A, Help & Troubleshooting and Genera

Last night I installed Gingerbread 2.3.1 on my HTC HD2.. Followed the directions exactly and was able to boot Android and customize and had no problems. Tonight, suddenly my buttons at the bottom (home button, start menu, back, etc) started flashing -- side note: if anyone knows why this happens and how that can be stopped please let me know!! --, I figured I would just restart my phone. Well, when I restarted, suddenly I had no service when I booted Android.
I have rebooted my phone in the different methods (reboot, recovery, and bootloader), tried powering it off and then turning it back on, tried putting it on airplane mode (dunno why) and then back off, took out the battery and sim and waited for 20 min and then put it back in... Nothing has had any luck.
When I boot Windows Mobile, I have a phone signal, but for some reason when I'm booting Android, it isn't there.
Anyone else have a similar problem or can suggest how to fix this? I really want to be able to continue using Android but that's not going to happen if it continues to have this problem...

Flash official windows again, then try NAND Gingerbread 2.3.4 Its great ROM and all works.

sultans said:
Last night I installed Gingerbread 2.3.1 on my HTC HD2.. Followed the directions exactly and was able to boot Android and customize and had no problems. Tonight, suddenly my buttons at the bottom (home button, start menu, back, etc) started flashing -- side note: if anyone knows why this happens and how that can be stopped please let me know!! --, I figured I would just restart my phone. Well, when I restarted, suddenly I had no service when I booted Android.
I have rebooted my phone in the different methods (reboot, recovery, and bootloader), tried powering it off and then turning it back on, tried putting it on airplane mode (dunno why) and then back off, took out the battery and sim and waited for 20 min and then put it back in... Nothing has had any luck.
When I boot Windows Mobile, I have a phone signal, but for some reason when I'm booting Android, it isn't there.
Anyone else have a similar problem or can suggest how to fix this? I really want to be able to continue using Android but that's not going to happen if it continues to have this problem...
Click to expand...
Click to collapse
try a different rom, the flashing buttons was common on early builds of gingerbread
i take it you are using an sd version rather than nand ?

Try switching to 2G only and see if your signal is back.

Richy99 said:
try a different rom, the flashing buttons was common on early builds of gingerbread
i take it you are using an sd version rather than nand ?
Click to expand...
Click to collapse
Yes, I'm using SD version... To be honest, I didn't really know the difference, but from what I was told NAND basically erases Windows, right? If that's correct, I was afraid of the installation not going right and being stuck without a working phone.

michie said:
Try switching to 2G only and see if your signal is back.
Click to expand...
Click to collapse
I tried going to my settings to switch to 2G, but at first it was greyed out, so I couldn't even select it. Then I clicked Access Point Networks and went back and suddenly it was available to be clicked. I clicked it and went to another screen and for some reason decided to go back to check it and it had been unclicked and greyed out again....

Seems it's a problem related to your rom and not a hardware problem because it works on wm.
Im not familiar with SD roms, maybe you should try a different SD rom or a NAND rom and see if the problem is solved.
Hope u get it sorted !

Since it seems I just need to try a different rom, can anyone suggest a link? I think I want to try SD again just because if I'm having these problems I don't want to completely wipe Windows and not have something to resort back to if I run into something again..

bluur said:
Flash official windows again, then try NAND Gingerbread 2.3.4 Its great ROM and all works.
Click to expand...
Click to collapse
Honestly I don't want to NAND it because I don't want to completely wipe Windows in case I have a problem again... (this is all assuming I understand NAND correctly)... Right now I have a problem so I was able to go back to Windows Mobile. Do you have any suggestions for another SD rom?

Not quite true. You can always go back to Winmo from Android Nand if you are unhappy with it. I used to think the same way but since taking the plunge I've always found it easy to reinstall Winmo in order to use my tomtom navigator
ROM wise there are various fantastic offerings with Android Nand. Some are even spotting the new sense 3. You can try either CoreDroid or LeoRC Mix.
For now head over to the Nand section and read the stickies at the top. There are ample and easy guides on how to prepare your HD2 for a Nand Rom and how you can return to Winmo if you don't like it. If you follow the instructions properly, trust me nothing will go wrong.
Sent from my Desire using XDA App

I'll give it a try, thanks!

Related

Hd2 bootloader screwed

After I did a task 29 weeks ago, my hd 2 started to act strangely
I frequently stuck at the white htc screen (w/o version numbers) after reset
must take battery out and put it back and try again until it boots
today, I tried like 20 times it still won't boot, so I try to flash a newer ROM, it didnt boot either, so I use SD to flash back to stock, overwriting everything, but the problem persists, I cannot boot into stock ROM. So I HSPL-ed, reflash radio and ROM, still the same. Now I totally cannot boot into WM, always stuck at white screen, can enter tri-color screen or hard reset but booting cannot be done.
I booted in 3 times today, but it hangs after a few minutes and after pull out battery/soft reset, same problem again....
Any solutions, or I just have to flash back to stock and send for warranty.
still no reply/solutions?
my soft reset button gonna spoil alrdy, booted 4th time jz now, but hangs after 1 minute
Try doing a task 29 make sure u get the correct radio for ur phone and after task 29 reflash if u do a search u will find task 29 info
Sent from my T-Mobile myTouch 3G Slide using XDA App
Sounds like u may have the wrong radio
Sent from my T-Mobile myTouch 3G Slide using XDA App
bgolden84 said:
Sounds like u may have the wrong radio
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
i use a 2.12.50.02_2 radio and all the rom i flashed requires 2.XX.50.XX radio
task-ed 29 again, still the same....... on energy/chucky/stock, use radio 2.07.50/2.08.50/2.12.50
also, I stated that I flashed back to stock the problem still persists, so the main cause is not ROM/Radio
PS: Now I flashed ChuckyROM (which changes the bootscreen), and I am stuck at the new bootscreen (STILL WITHOUT VERSION) again.
another successful boot, but auto reboot 30 seconds later
FFFFFFFFUUUUUUUUUUUUUUUUUUUUUUUUUUU
Start from the bare minimum and setup the ideal conditions for the phone to boot - keep things cool, remove sd card, full batt, etc. You could try the stripped down winmo rom that is used for loading Android (haret) quickly. It only has the essentials to load into windows.
My GF's HD2 seems have similar probs to the common freezing hd2.
I thought that this was an interesting quote from another thread.
sirphunkee said:
cambxo, have you checked the battery connection pins? People have experienced symptoms similar to yours (resetting and never getting past the boot screen) when one or more of the little gold pins gets bent. Can't guarantee that's the issue, but it's worth a look.
Click to expand...
Click to collapse
followed by -
ndeguiera said:
holy cow it worked! thanks bro!!!!!!!
Click to expand...
Click to collapse
I love threads like that. heh. We'll fix this. Now that Android is getting more refined, eventually you could use it as a troubleshooting tool. It would help differentiate NAND problems from CPU/Batt/Heat problems.
thanks, it partially fixed my phone, i straighten the gold pin and allow the battery to cool for a few minutes(by removing and re-applying) before each boot,now it is able to boot into winmo.
After I did a task 29 weeks ago, my hd 2 started to act strangely
I frequently stuck at the white htc screen (w/o version numbers) after reset
must take battery out and put it back and try again until it boots
today, I tried like 20 times it still won't boot, so I try to flash a newer ROM, it didnt boot either, so I use SD to flash back to stock, overwriting everything, but the problem persists, I cannot boot into stock ROM. So I HSPL-ed, reflash radio and ROM, still the same. Now I totally cannot boot into WM, always stuck at white screen, can enter tri-color screen or hard reset but booting cannot be done.
I booted in 3 times today, but it hangs after a few minutes and after pull out battery/soft reset, same problem again....
Any solutions, or I just have to flash back to stock and send for warranty.
--------------------------------------------------------------------------------
hello . i had the same problem with that n i found out that it was the SDcard that causing problem . u must have doing the task29 without taking out the memory card like me .
so farmat the sd card put it back n my hd2 back to live,

[Q] android stop working

Okay this is my first ever thread so pls dont bash on where its posted. So the problem is, is that my android on hd2 would stop working after I reboot my phone. Idk why but it just hangs at the boot screen, which is white and has HTC on it. This has happened with every android rom I use and I can't even find answers when I google the problem. I'm using the htc energy rom and a 32gb sd card.
Strange i have exaclty the same! i updated to MccM HD 3Beta two days ago. Ill try another now and see what happpen
Questions belong in the Q&A Forum
No bashing just a friendly bit of advise for future reference.
Mark.
I've been going through different android roms and everytime I reboot into the wm energy rom I can't boot back into android. At this point I'm afraid to turn of my hd2, but I need to so I can recalibrate my battery stat.
nomura808 said:
I've been going through different android roms and everytime I reboot into the wm energy rom I can't boot back into android. At this point I'm afraid to turn of my hd2, but I need to so I can recalibrate my battery stat.
Click to expand...
Click to collapse
what do you mean can't boot back to android???
Yea u need to provide more details so we can help u.
Sent from my HTC HD2 using XDA App
I’m using HTC HD2 T-mobile v and also I have the same problem,
What kind of details will help u?
=P
Android was smoothly worked before the problem.
And I feel it was not stable with the SD card, for example i put some files on it by using the USB and after I check them from the phone not all are there.
And the problem began when the android said "save remove for SD card"
After second it shakes. I remove the battery to reboot it and it is just can't complete booting to android. It is stop at HTC white start screen.
For me the same,
I use a Android rom and when I launch Android, it doesn't leave the HTC screen. I kept it running all night long, but it didn't work. All my contact and text messages are in Android and now I can't reach them anymore, what should I do?
Rushedby said:
For me the same,
I use a Android rom and when I launch Android, it doesn't leave the HTC screen. I kept it running all night long, but it didn't work. All my contact and text messages are in Android and now I can't reach them anymore, what should I do?
Click to expand...
Click to collapse
i make a temporary Solution =P
i replace all the "SDcard/Android" files except "data.img"
because "data.img" contain all data we build
try it and give me ur feed back ^_^
I have problem booting to andriod too, since yesterday morning, i was using android, the screen was freeze, so i restarted the phone and reboot to android. So as usual, i went to the android folder and trying to boot to android, then i got this error message "The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannt be found. If the proble persists, try reinstalling or restoring this file." I have no idea why this happened all in a sudden. so I've tried many times and restarted my phone to see if it would help, but it didn't. then I thought maybe the android wasn't updated, so I went back to the forum and found the updated version, but mine was discontiuned. I downloaded a new build and I erased everything on my SD card and gave it a try, but the same thing still happen. I still got that error message. would anyone know why? I'm desparated to go back to android.

Quick boot question

I'm sure this has been covered before, but I'm not having luck digging through thousands of threads to find my answer. Its quick and easy for someone who knows more then I do.
I have a T-Mobile US HD2. I've flashed a custom rom of windows (latest version of Core) and I'm trying to run the latest version of Core Droid.
I've been able to install and boot up into Android just fine.....just once though. After the install process when it boots into Android, if I shut off the phone, restart it....blah blah blah it will automatically go back into Windows....and then I have to delete all the Android files and start new.
I've tried using this boot loader http://forum.xda-developers.com/showthread.php?t=733752
My options are set to have Android as the default, 30 second delay to let me have a chance to get into Windows incase I ever wanted too, and I have /android set as the Android folder. When I orignally copied all the files to my flash card, I put them in a folder on root called Android. As well, I've done all this on a freshly formatted SD card.
I've tried this several times with a few different WinMO Roms. I've tried a couple different distros of Android but without any better luck. Core seems to be the only one I can actually get to boot.
Please, any help would be great. I know I'm just missing something quick and simple here, but since this is something that I don't know much about I'm kind of stuck
EDIT :
I should also add that I've tried installing the boot loader both before and after my Android install. It doesn't make a difference either way.
Why do you have to delete Android and start again? Booting back into Windows is correct, of course, but you've not explained what actually goes wrong.
Sent from my HTC HD2 using XDA App
It seems like Droid wants to go through the whole install process again. It will sit there and do absolutely nothing (I left it sitting overnight on the black HTC screen that shows up when first putting on droid).... The only way I can get back into droid is if I format the SD card and start from scratch. Then if I turn off the phone or reboot it I have to do everything all over again.
I'm trying to just boot into Droid when I turn on my phone without having to worry about Windows. I don't mind a dual boot option. I just don't want to use Windows anymore
The only thing I can suggest is trying a different Android build. Just get one running and then reset your phone to make sure you can restart Android again. Worry about the bootloader later.
Sent from my HTC HD2 using XDA App
johncmolyneux said:
The only thing I can suggest is trying a different Android build. Just get one running and then reset your phone to make sure you can restart Android again. Worry about the bootloader later.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
It seems to be working OK now. I re-flashed Windows and did everything from scratch. Set up the boot loader again and things seem to be ok.
What would you suggest as far as what build to use. I know this is kinda a touchy subject, but can you give me me pros/cons of the big ones?
I've NEVER used Android before so I'm pretty new to this
Dude, there is plenty of threads, even recent ones that already exhaust that question to the full, all you need to do is read them.

[Q]Is there anyway to go from HSPL3 to HSPL2.08?

Ive been trying to get my HD2 to not freeze up on me and ive read every where that HSPL2.08 is recommended. I tried searching for a guide on how but all I get is the HSPL/HSPL2 guide
Hspl is hspl2.08 its just the actual number of the hspl
Sent from my HTC HD2
ok ive tried every guide out there but nothing is working. How can I start from scratch??? I want my HD2 to go to where I just got it out from the box. I cant get it to boot, sometimes when I finally do get it to boot android I cant do anything like browse the internet or play games cause it will freeze. I think if I had just a clean start I can get everything to work again. Ive been trying to fix this problem all weekend and today is my last day off until I go back to work. Can anybody help
Just try another build of Android?
If you do want to go back to stock, what phone do you have? The T-mobile one or the European?
I have the T-Mobile one, Its so bizarre. I finally got it to go back to winmo 6.5 but it still freezes, I thought for sure if I got it back to the original OS it wouldnt freeze. Did I do something wrong when switching OS'?
In what way does it freeze?
sometimes when it does the "123 GO GO GO" also if it happens to get past the GO GO GO it will freeze on the HTC boot screen, and I guess if I do to much within android it will freeze. I cant really use any apps or else it just freezes. Like right now I was just editing stuff on the home screen and it froze
I actually have this problem with my HD2 sort of. I dug it out today after a few weeks sitting in my drawer as I thought its time had past. I don't really think there's s fix for it. Maybe restore to stock and send it to HTC for repair? I don't have warranty so I just bought a Desire Z.
Sent from my HTC Vision using XDA App
Thats weird because I had my HD2 back when MAGLDR first came out and I had Android running on nand. I think I even used MAGLDR 1.11 and installed a ZIP MIUI Android with CWM and I never had this problem. Then my screen broke and I reverted it to stock (Turns out I had no insurance) and now I want android again and I keep freezing. Point is before I went back to stock my phone was fine
Carliz89 said:
Thats weird because I had my HD2 back when MAGLDR first came out and I had Android running on nand. I think I even used MAGLDR 1.11 and installed a ZIP MIUI Android with CWM and I never had this problem. Then my screen broke and I reverted it to stock (Turns out I had no insurance) and now I want android again and I keep freezing. Point is before I went back to stock my phone was fine
Click to expand...
Click to collapse
Mate,
Have u tried flashing via cLK? using this method can show you whether there is badblock (cluster) in the NAND. I used this method and I found why I couldnt flash/boot Android anymore. Too many badblocks in the NAND. But luckily, I still can go back to WInmo and use it without problem, sofar and I am selling it now
Cheers...
is Clk the clockwork thing or the AD Recovery? Because ive tried it using a NAND and the Zip way. I think theres something wrong with my NAND or something because it was working 100% 2 months ago
AD recovery is the clockwork mod. Clk replaces the magldr. It does the same thing except its only for Android it won't boot wp7.
Sent from my HTC HD2
Im still getting a crazy amount of freezing from my phone. I cant do anything with it, or else it will freeze. Ive tried a bunch of android builds and its all the same. It even freezes on the T-Mobile Stick Together screen. How can I start from scratch Theres no point in having a smart phone if you cant use it. Its been like this for 2 weeks and its driving me CRAZY

[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.

Categories

Resources