Database Users

Can't flash any ROMs

Hey all, I've been running Ic3ROM 2.6 or 2.7 (can't remember now) for a while. Upgraded to that from the two previous versions of Ic3ROM.
Right now I cannot flash ANY ROM. I always end up having to restore my nand backup.
I've tried flashing DarchDroid 2.5, 2.6, 2.6.something, and 2.7. I've tried flashing Ic3ROM 2.9. Every time I do it flashes fine but when I boot I get stuck on the black HTC loading screen for 30+ minutes. Sometimes I'll hear the phone vibrate and see it start that loading screen over, too.
This is very frustrating as I'm such a fan of trying out different ROMs and the latest darchdroid looks fantastic (love AOSP).
Any ideas? I've tried wiping, wiping battery stats, rotate settings, dalvik, even my SD card.

remove your SD card from your phone after you flash, see if it boots then.

Thanks, will try that tonight. Hadn't even thought of it.
(Waiting on a call back about a major job interview so won't do it today at work, heh.)

No luck. I got impatient and tried your suggestion, Kcarpenter, and had no luck.
Thinking I'll just have to struggle with the RUU tonight. The only reason I'm so adamant about flashing a new ROM is that my phone reboots randomly when I hang up or when I try to answer a call. Occasionally just for fun it reboots when I look at it.

Is_907 said:
The only reason I'm so adamant about flashing a new ROM is that my phone reboots randomly when I hang up or when I try to answer a call
Click to expand...
Click to collapse
Here, try the OC kernel fix for those issues......http://forum.xda-developers.com/showthread.php?t=705074

Is_907 said:
I've tried flashing DarchDroid 2.5, 2.6, 2.6.something, and 2.7. I've tried flashing Ic3ROM 2.9. Every time I do it flashes fine but when I boot I get stuck on the black HTC loading screen for 30+ minutes. Sometimes I'll hear the phone vibrate and see it start that loading screen over, too.
Click to expand...
Click to collapse
Does your dalvik debug monitor (ddms.bat) output anything when this keeps happening? If so could you post that for us?

smolck said:
Here, try the OC kernel fix for those issues......http://forum.xda-developers.com/showthread.php?t=705074
Click to expand...
Click to collapse
That's not exactly the problem I'm having... no FC, just reboots.
But I'll try this anyway when I get home. Can't hurt, right?

Can you run adb logcat when it's booting? If you can post it on pastebin, we can probably help you out a bit more.

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 worked fine now has stopped

Have had Android working and booting fine for the week, battery went flat last night , now android wont boot, goes to the grnn HTC icon n then stops, I have waited half an hour still with nothing, as ive said its not the first time its been booted. I have searched on here but they all seem to be new installs that are having problems. Any idea ?

TommyHD2 said:
Have had Android working and booting fine for the week, battery went flat last night , now android wont boot, goes to the grnn HTC icon n then stops, I have waited half an hour still with nothing, as ive said its not the first time its been booted. I have searched on here but they all seem to be new installs that are having problems. Any idea ?
Click to expand...
Click to collapse
I am getting same issue. Android was very nice, fast boot and so on. But since tomorrow, when booting to Android it stays on startup screen with green htc.

TommyHD2 said:
Have had Android working and booting fine for the week, battery went flat last night , now android wont boot, goes to the grnn HTC icon n then stops, I have waited half an hour still with nothing, as ive said its not the first time its been booted. I have searched on here but they all seem to be new installs that are having problems. Any idea ?
Click to expand...
Click to collapse
Sounds like possible data corruption if system did not shutoff gracefully. Not a good idea to let low battery shut off system... you should shut it off manually. I have had this happen on WM where the phone get into a weird state and data get corrupted.
I would backup the data.img file, let Android create a new one to see if it boots properly. Then restore the original data.img file and see if it boots with that one.

hidnface said:
I am getting same issue. Android was very nice, fast boot and so on. But since tomorrow, when booting to Android it stays on startup screen with green htc.
Click to expand...
Click to collapse
Which build are you using?

Same Here!
Battery went flat, tried booting android a few times but didnt succeed. So rebooted the phone to find..
The android boot screen repeats itself. Over and over. Was fine yesterday.
Going to try backing up the data.img and restoring it after it rebuilds as mentioned above.
UPDATE :
After backing up the data.img file, and letting it rebuild, one hour later, still not booted.. So restarted the phone, put the old data.img back, started up haret.exe, and its now stuck on the Green HTC logo.. and isnt moving.. at all.
This isnt my first boot.. usually it boots within a couple of minutes.

jmmmmm said:
Which build are you using?
Click to expand...
Click to collapse
Latest Android build. FroyoStone version3.2

Android not rebooting after flat battery
Hi TommyHD2,
I have just had the same problem, actually a couple of times. What I did was to delete all the new entries that had been made on my micro SD card and only leaving the original 8 files that are in the FroyoStone 3.2.7z Android folder and of course I did not delete the media folder that is also included in the build. Well twice now I have done this with a successful reboot of Android whilst not losing any of the settings that I had made ie. Wallpaper, shortcuts etc even apps (unless they are on the card).....Obviously this will now be a case of trial and error to establish which of the deleted files it is that cause a conflict in the reboot. I am also new to this but reading this someone may be able to idntify the problem easily. Other than that it runs superb....EVERYTHING works....well battery drain but I think that is even solved now thanks to XDA.....I will let you know in about four hours
Good luck
HTC HD2
Radio - 2.15.50
FroyoStone 3.2.7z

scirroco said:
................
FroyoStone 3.2.7z
Click to expand...
Click to collapse
.7z is the file extension (like .rar, .zip, .doc) and not the version.

Froyostone version confusion
HI Hidnface,
I don't know what sort of smile that is ....sarcastic or friendly but thanks all the same. Bit dumb of me but then I am still learning.
By the way I found that when you boot into Anroid you are left with a folder calle Android_Secure....I dont know what thois does but this is the one I delete to enable successful reboot.
Thanks mate.

have you guys tryed doing a logcat of it booting? whats it erroring at? is it looping?
search adb logcat. android is verry easy to debug since you can watch processes in a comand line...

[Q] HD2 Random Reboot Issue with Android in Nand

Hello everybody,
I came from a nrg on a leo512.
I have installed MAGLDR 1.11 in order to use Android in my NAND.
But I've some random reboot from my device and most of them are when I'm standby mode when I woke up the morning the phone asks me for the pin code...
It's strange when I boot I saw in first for 1-2 sec NRG bootscreen before MAGLDR...
That's why I'm wondering If you think my HD2 NAND is clean ?
Should I make a task29 ? I heard that tools earses all the data...
All your helps are welcome !
Regards

ditto
I have this problem also..
Norwegian HD2..
I have tried quite a few radios.. plowing through all the available radios as we speak.. if i get a reboot i flash a new radio in hope of figuring out the problem.. the weird thing is i dont get this while using WP7... i get reboots in all other OS.. a quick fix for the SIM lock annoyance is to disable PIN code but does not fix the problem itself.. anyone have any thoughts on what this may be?

Sammy88 said:
It's strange when I boot I saw in first for 1-2 sec NRG bootscreen before MAGLDR...
Click to expand...
Click to collapse
This is normal.
The custom ROM you were using has flashed a custom boot screen. As MAGLDR is installed AFTER this in the chain (Boot1->Magldr->Radio & NAND), it does not alter the screen. You can actually install a custom boot screen to replace this. Check Here for some.
As for the reboots, check the sticky link in my sig. There is a FAQ in there which may offer some help.
Also try post 2 of THIS

looks promising
Cptrucker said:
I have this problem also..
Norwegian HD2..
I have tried quite a few radios.. plowing through all the available radios as we speak.. if i get a reboot i flash a new radio in hope of figuring out the problem.. the weird thing is i dont get this while using WP7... i get reboots in all other OS.. a quick fix for the SIM lock annoyance is to disable PIN code but does not fix the problem itself.. anyone have any thoughts on what this may be?
Click to expand...
Click to collapse
Update: Ended up on 2.11.50.20 and its been 20 hours since i flashed the radio.. still no reboot... looks promising, ill update if the situation changes...
Update: 2.11.50.20 was no success, 2.15.50.04 seems to be the best radio in my case.. about 60 hours between reboots has been quite consistent
lately.. i wonder what causes this. ideas and\or sollutions are recieved with gratitude. Disabled the SIM lock so its nothing to worry about but it stil gives me headache.

Although the posts above me may be right, it seems that after I disabled over clocking on my hd2, the issue was no longer present.
As always, remember what your mommy taught you; it's proper to say "please and thank you".

The solution to this problem, can be found HERE.

Esaj2 said:
The solution to this problem, can be found HERE.
Click to expand...
Click to collapse
I tried this solution, but it didn't resolve anything. I'm using mdj's cyanogen mod 2.6 with the latest radio and magdlr 1.13. I' m not using set CPU anymore. I was using it to underclock the phone and I was still getting restarts. The phone's temperature did not seem excessive either. This is a great phone but these restarts are making it almost useless. I'm at a lost here.

viscious said:
I tried this solution, but it didn't resolve anything. I'm using mdj's cyanogen mod 2.6 with the latest radio and magdlr 1.13. I' m not using set CPU anymore. I was using it to underclock the phone and I was still getting restarts. The phone's temperature did not seem excessive either. This is a great phone but these restarts are making it almost useless. I'm at a lost here.
Click to expand...
Click to collapse
Like I said, it works for some of us. I haven't had any rebooting issues, after I turned of the automatic network selection. Some Norwegians fixed this issue, by turning of the 3G. You could try removing the sim-card and leaving the phone at sleep mode for few hours, in order to see, if your phone is still suffering from the random reboots. If so, the problem is somewhere else and I can't help you with it, because I haven't had such issues.

I resloved the issue by sending the phone back to HTC and having the mainboard replaced. Now the phone is working exactly as it should.
Sent from my HTC HD2 using XDA Premium App

[Q] Android Boot Time - is mine slow?

Some details:
HD2 512.
Typhoon 3.5.6.
MAGLDR 1.13.
Recovery 4.0.0.0.
Some things I know:
CM7 takes a while to load anyway.
I believe having lots of media (I have 7GB MP3's) can lengthen boot times. (~Theory is crapped all over with my SGS2 but some people have mentioned this fact).
The problem here is not at the loading stage where the bootanim kicks in, it's the stage before with the static logo after GO GO GO.
My SGS2 literally loads and is ready to use in 10 seconds to OS and 30 seconds to functionality after media scan/widgets etc.
So what's my HD2 doing at the static logo screen? It basically doubles the entire loading time but from my little knowledge, nothing actually happens until the bootanimation? I don't like waiting up to 2 minutes to be using my phone.
I hear CLK has a faster boot option. In anyone's opinion, have they sorted data out enough to come away from MAGLDR?
Thanks in anticipation of any responses.

dkl_uk said:
Some details:
HD2 512.
Typhoon 3.5.6.
MAGLDR 1.13.
Recovery 4.0.0.0.
Some things I know:
CM7 takes a while to load anyway.
I believe having lots of media (I have 7GB MP3's) can lengthen boot times. (~Theory is crapped all over with my SGS2 but some people have mentioned this fact).
The problem here is not at the loading stage where the bootanim kicks in, it's the stage before with the static logo after GO GO GO.
My SGS2 literally loads and is ready to use in 10 seconds to OS and 30 seconds to functionality after media scan/widgets etc.
So what's my HD2 doing at the static logo screen? It basically doubles the entire loading time but from my little knowledge, nothing actually happens until the bootanimation? I don't like waiting up to 2 minutes to be using my phone.
I hear CLK has a faster boot option. In anyone's opinion, have they sorted data out enough to come away from MAGLDR?
Thanks in anticipation of any responses.
Click to expand...
Click to collapse
Don't remember stuck with GO GO GO for long in my Mag days. I am now on cLK, and from the second boot onward, my phone is usable within 45 seconds - this is with a lot of apps, most of with run all the time right from boot.

I am using MAGLDR with Tytung's Nexus HD2 v2.9 build and it takes about 45-50 seconds to load. Much faster than when I was using Cmylxgo's TMOUS Froyo build which took a little over 2 minutes to load for comparison.

ph03n!x said:
Don't remember stuck with GO GO GO for long in my Mag days. I am now on cLK, and from the second boot onward, my phone is usable within 45 seconds - this is with a lot of apps, most of with run all the time right from boot.
Click to expand...
Click to collapse
It's not stuck at GO GO GO, it's stuck at the static boot image for a while, then the animated boot logo begins. Maybe it's the fact the phone looks like it's doing nothing while it's showing the static boot logo but like I mentioned above the SGS has the same amount of media and also it has the same apps as the HD2 and it's usable in under 30 seconds.
Thanks for the response anyway.

dkl_uk said:
It's not stuck at GO GO GO, it's stuck at the static boot image for a while, then the animated boot logo begins. Maybe it's the fact the phone looks like it's doing nothing while it's showing the static boot logo but like I mentioned above the SGS has the same amount of media and also it has the same apps as the HD2 and it's usable in under 30 seconds.
Thanks for the response anyway.
Click to expand...
Click to collapse
If you want to experiment, try Tytung's Mag kernel - get it from his thread and flash it. Mind you, ensure it also has the wifi drivers (bcm4329.ko), else wifi may not work. In my experience, Tytung's implementation of his Kernel boot faster.
Also, CWM 4.0.0.0 is not supposed to be stable (has something with backup/ recovery). Get the latest, or go with 3.2.0.0

I had the same problem when I was using that rom.
I tried to find the prob using logcat, and I saw a lot of errors being thrown at me, and also quite a few a2sd zipalign's, so I removed a2sd scripts from init.d, it started booting faster; but I still had the other errors.

ph03n!x said:
If you want to experiment, try Tytung's Mag kernel - get it from his thread and flash it. Mind you, ensure it also has the wifi drivers (bcm4329.ko), else wifi may not work. In my experience, Tytung's implementation of his Kernel boot faster.
Also, CWM 4.0.0.0 is not supposed to be stable (has something with backup/ recovery). Get the latest, or go with 3.2.0.0
Click to expand...
Click to collapse
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
Moon2 said:
I had the same problem when I was using that rom.
I tried to find the prob using logcat, and I saw a lot of errors being thrown at me, and also quite a few a2sd zipalign's, so I removed a2sd scripts from init.d, it started booting faster; but I still had the other errors.
Click to expand...
Click to collapse
I actually have live logcat bootanimation and I am pretty sure i've seen a lot of errors too. It goes too fast to debug anything, and i've not taken the next step which is of course to do what you did and actually read the logcat, but these errors take milliseconds during the boot phase and I don't believe it's this bit that is the issue - it's the bit where the static logo shows and I don't truly know what the phone is doing at that stage.
Thanks for your helps also guys

dkl_uk said:
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
Click to expand...
Click to collapse
The Mag and the cLK version of the kernel are here- use the one that says 2.3.4 only, even if you or on 2.3.5
I use this in cLK, and know for sure that the required Wifi drivers are in it. Note that the cLK version has cedesmith's data wrapper b5, but the b4 wrapper works better for me. This is in case you choose cLK, and are having data issues after flashing the kernel.
http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3

ph03n!x said:
The Mag and the cLK version of the kernel are here- use the one that says 2.3.4 only, even if you or on 2.3.5
I use this in cLK, and know for sure that the required Wifi drivers are in it. Note that the cLK version has cedesmith's data wrapper b5, but the b4 wrapper works better for me. This is in case you choose cLK, and are having data issues after flashing the kernel.
http://forum.xda-developers.com/showpost.php?p=10429937&postcount=3
Click to expand...
Click to collapse
That's literally the post I came across once I did a search based on what you'd already told me. Thanks for confirming further.

Timed my boot - was 35secs on the watch and 33secs according to logcat. To put things in perspective, I have trillian (5 accounts), gtalk, gmail, 3 email accounts, google+, current widget, CallRecorder, CSipSimple, ClockSync, DSP Manager, Easy Filter, Swype and Where's My Droid loading at boot - in addition to whatever Android loads (Maps, Calendar, Settings...)

dkl_uk said:
Thanks for the heads up. I obtained that version of CWM through the HD2 Toolkit, and so far I haven't had any issues using it for the last few months.
Assuming I find the Kernel you've pointed me to, would it not be in CWM flashable mode and therefore i'd just be overwriting the zImage and not actually flashing a new ROM - therefore keeping my current /system (and bcm4329.ko)? Apologies if that was literally the most noob statement you've ever seen.
I actually have live logcat bootanimation and I am pretty sure i've seen a lot of errors too. It goes too fast to debug anything, and i've not taken the next step which is of course to do what you did and actually read the logcat, but these errors take milliseconds during the boot phase and I don't believe it's this bit that is the issue - it's the bit where the static logo shows and I don't truly know what the phone is doing at that stage.
Thanks for your helps also guys
Click to expand...
Click to collapse
You have to use the following command to get logcat to make a file of it.
adb logcat > anyfilename.txt

ph03n!x said:
Timed my boot - was 35secs on the watch and 33secs according to logcat. To put things in perspective, I have trillian (5 accounts), gtalk, gmail, 3 email accounts, google+, current widget, CallRecorder, CSipSimple, ClockSync, DSP Manager, Easy Filter, Swype and Where's My Droid loading at boot - in addition to whatever Android loads (Maps, Calendar, Settings...)
Click to expand...
Click to collapse
At what point are you timing this boot from? Power on? GO GO GO? Splash screen?
If I were to time my boot from the animated boot screen then i'd say possibly 30 seconds too, it's just that for another 30 seconds it's sat on the static boot animation.
Also my launcher screen takes an awful amount of time to parse. You can definitely tell the HD2 is ageing when you compare it with the SGS2. I know it's in a class of its own but still, i'm beginning to lose faith in the longevity of my HD2.

I am on the same boat, I use aMAGLDR 1.13 + MIUI Rom and the boot process is very very slow.
I just timed it:
1. From T-mobile Stick together to go go go: 9 secs.
2. A static splash screen, black background and green HTC logo: 1min 52 secs.
3. From MIUI globe animation kicked in to locked screen: 29 secs.
So basically I have no idea why step 2 takes such a long time. Is there anyway to see any error msg during this stage?
I tried to remove SIM card and/or SD card, it is about the same, so I guess there is something happening in the NAND...
Thanks!