Database Users

[Q] HD2 Nand ROM issue - freeze's on first reboot

Hi there
i've had a search through the forums and google, but havent come up with anything...
the isue is, after flashing a new CWM NAND ROM on my HD2, the rom will load perfectly the first time. however the issue is when i try to reboot the phone... it loads through cwm, but hangs on loading the rom...
this has happened on several different rom's, and after several task29/mgldr/cwm re-flashes...
Any ideas?
Cheers
Gav

fatmcgav said:
Hi there
i've had a search through the forums and google, but havent come up with anything...
the isue is, after flashing a new CWM NAND ROM on my HD2, the rom will load perfectly the first time. however the issue is when i try to reboot the phone... it loads through cwm, but hangs on loading the rom...
this has happened on several different rom's, and after several task29/mgldr/cwm re-flashes...
Any ideas?
Cheers
Gav
Click to expand...
Click to collapse
Have you tried doing absolutely nothing after first boot, other than skipping through the setup wizard? What I'm wondering is what you may be installing / doing that could be causing this.
One thing that could help is to run logcat with the phone connected during bootup and you could see what is causing it.

Digital Outcast said:
Have you tried doing absolutely nothing after first boot, other than skipping through the setup wizard? What I'm wondering is what you may be installing / doing that could be causing this.
One thing that could help is to run logcat with the phone connected during bootup and you could see what is causing it.
Click to expand...
Click to collapse
hi there
cheers for the suggestion. i tried a re-flash and skipping the setup wizard, but still the same issue.
attached is a logcat capture.
any help appreciated.
cheers
gav

fatmcgav said:
hi there
cheers for the suggestion. i tried a re-flash and skipping the setup wizard, but still the same issue.
attached is a logcat capture.
any help appreciated.
cheers
gav
Click to expand...
Click to collapse
Yeah, looking at your log, you are definitely in a boot loop. Android keeps restarting after what looks like initializing the audio... looks like some files are missing.
What ROM are you using? Have you applied anything (updates) else at all through CWM other than the ROM? Does the ROM you are using require an SD-EXT partition? Is your SD card in the phone?

Digital Outcast said:
Yeah, looking at your log, you are definitely in a boot loop. Android keeps restarting after what looks like initializing the audio... looks like some files are missing.
What ROM are you using? Have you applied anything (updates) else at all through CWM other than the ROM? Does the ROM you are using require an SD-EXT partition? Is your SD card in the phone?
Click to expand...
Click to collapse
hi
i've been trying "skink_Clean_Desire_v1.1_update_signed" and "NexusHD2-Gingerbread_V2.2_NAND_update"...
SD was partioned and formatted using cwm, with a 1Gb ext partition... SD card is present as am flashing using cwm zip from sd...
cheers
gav

fatmcgav said:
hi
i've been trying "skink_Clean_Desire_v1.1_update_signed" and "NexusHD2-Gingerbread_V2.2_NAND_update"...
SD was partioned and formatted using cwm, with a 1Gb ext partition... SD card is present as am flashing using cwm zip from sd...
cheers
gav
Click to expand...
Click to collapse
Which version of CWM are you using? Is it 1.13? Whatever it is, what size did you flash (the partition layout) for your system partition?

Digital Outcast said:
Which version of CWM are you using? Is it 1.13? Whatever it is, what size did you flash (the partition layout) for your system partition?
Click to expand...
Click to collapse
I'm using the latest versions of Magldr and CWM. I flashed a 250Mb system partition.
Gav

Are you sure that is a large enough partition? Is that what the ROM developer recommends?

Digital Outcast said:
Are you sure that is a large enough partition? Is that what the ROM developer recommends?
Click to expand...
Click to collapse
250 is the recommended size on the cwm thread...
not been able to confirm from the 2 rom threads though...
however i have got a mdj rom whuch flashed succesfully on this size...

fatmcgav said:
250 is the recommended size on the cwm thread...
not been able to confirm from the 2 rom threads though...
however i have got a mdj rom whuch flashed succesfully on this size...
Click to expand...
Click to collapse
just use the "daf" folder that comes with the build once you unzip it.
it has the CWR setting configuration all done ready for the build
just flash it.

My issue is: When phone loads android from NAND (sometimes it freezes in GO GO GO) I can use it some unpredictable time. FE. When I switching Mobile Network on it(after 1-2 it freezes). I even upgraded radio to 2.15. No changes still freezes. Second point is, when I turn off radio module and starting using dev. (FE while playing Angry Birds) it freezes again, with the noise on spekers. In my case I detaching battery and waiting for a while (because if you put battery again after a second) it freezes on GOGOGO again. WTF with device. Maybe it is a physical problem?
Dev is TMOUS HD2 16gb.
ps. When I used Android via SD same freeze always happened only with Angry Birds. In WinMo I didnt recognize such issues. Oooh. One more thing. When I tried to go back to WM 6.5 off.ROM. nothing happened after upgrade. I think my device will always live with Android till the end of the days. Thank you in advance!

I Need Some Advice

Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.

webmanya said:
Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.
Click to expand...
Click to collapse
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers

silverwind said:
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers
Click to expand...
Click to collapse
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.

webmanya said:
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.
Click to expand...
Click to collapse
In fact, I still can use Imilka's, Rafdroid and few other Nandroid ROM
But, I dont want to make it worse knowing that there is some badblock(because I want to sell it)
So, I am back with Winmo and SD Android. It is much safer for me
Cheers

Girlfriends kills android roms everytime!

Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)

joostnl said:
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
Click to expand...
Click to collapse
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.

Buy her an iphone, then she can't pull the battery! :-D
Sent from my HD2 using XDA App

malybru said:
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Click to expand...
Click to collapse
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)

Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again

lol, hahaha

joostnl said:
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Click to expand...
Click to collapse
ive seen a few posts where people have struggled with getting past boot logo, think it was fine after using a different partition in recovery but as your device is for the sd build am not quite sure how that works as Ive never had sd android or if having sd requires clockwork mod recovery? if so try different partition as i said earlier if not hang on till someone has the answer
johnerz said:
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
Click to expand...
Click to collapse
haha great answer, my girlfriend doesn't touch my hd2 or she gets alot more than a double dose with the tazer method, HD2 is not the solution for a women... you take the hd2 of her and buy her a iphone surly they are women material.

Ignore Post

Problems almost always occur after a few weeks or months of use for me, just reflash the ROM, and you'll good to go.
removing the battery is not recommended, it can corrupt files on the sd-card. Try to boot without sd-card and see if it helps. If your ROM does boot, it means the SD card is corrupted, you can try to backup the SD card and restore it after completely wiping the sd-card.
If your rom doesn't boot, than it meant there's something else going on, maybe corrupted flash, so reflash and try again. This will delete all your data, so be careful

if your girlfriend is not an daily flasher also might i suggest using a daf build. All the configuration is done for you. if you are using a sd build from magldr than make sure you change the name of the build than edit the startup txt like this "rel_path=whatever you name the build(example: "rel_path=MIUIROM nand_boot=1") the 1 for magldr 0 for windows 6.5. the reason for me saying this is all android builds create a folder android when they boot up with all your info like data and cache is in there. So its best to separate the two just in case you want to boot up more than two builds from sd.

Same here.
could be a bad block in your NAND memory. you can check this with cLK and fastboot.
see this post: http://forum.xda-developers.com/showpost.php?p=13600733&postcount=9
i checked mine and there was a bad block in the userdata. i think that is wy my phone was freezing.
now i have flashed cLK and untill now its working great!

Boot freeze

I've tried 3 different roms:
http://forum.xda-developers.com/showthread.php?t=926507
http://forum.xda-developers.com/showthread.php?t=1010498
http://forum.xda-developers.com/showthread.php?t=1010498
I have done everything as described in the instructions. Every time the bootscreen freeze. Coredroid was in boot loop. I have waited up to 1 hour and nothing happens. What is wrong?

I have exactly the same problem.. Tried three different ROMs with three different Radio's.

Partition layout?

Marvlesz said:
Partition layout?
Click to expand...
Click to collapse
No idea tbh, not experienced with NAND on HD2

henninghh990 said:
No idea tbh, not experienced with NAND on HD2
Click to expand...
Click to collapse
I've tried formating it with both 200 and 350MB as system partition.

sorry if this is a stupid question, but are you sure you've rooted it correctly?
I remeber having the same bootloop issue, when i went through the steps once again it worked..i think i just had missed something little...
are you using clk or magldr?

JimWest7997 said:
sorry if this is a stupid question, but are you sure you've rooted it correctly?
I remeber having the same bootloop issue, when i went through the steps once again it worked..i think i just had missed something little...
are you using clk or magldr?
Click to expand...
Click to collapse
I did the following:
Installed HSPL 2.08
Installed MAGLDR
Use the DAF.exe with MAGLDR on the phone
Then I went to AD Recovery and wipe full data and Dalvik
Then I installed ROM via SD card.

I did the following:
Ran task29.exe
Installed Radio Leo 2.15.50.14
Installed MAGLDR
DAF.exe
Then I installed ROM via SD card in CWM.

Im sorry but it sounds right, what you did. all i can advice you to try ist start ALL over, first by rooting (http://forum.xda-developers.com/showthread.php?t=833953)
and then just follow the instructions given on the coredroid download, they are very detailed and unless you miss a step by accident (which was what i did) it should work.
and dont forget to give the first boot some time, it may take up to 15 minutes (sometimes even longer) but dont worry its just the first one!
good luck, and if you try please post the results, hd2 has left me down woth a few rooms a couple of times but in the end it always worked, even if it took many reflashes!!

JimWest7997 said:
Im sorry but it sounds right, what you did. all i can advice you to try ist start ALL over, first by rooting (http://forum.xda-developers.com/showthread.php?t=833953)
and then just follow the instructions given on the coredroid download, they are very detailed and unless you miss a step by accident (which was what i did) it should work.
and dont forget to give the first boot some time, it may take up to 15 minutes (sometimes even longer) but dont worry its just the first one!
good luck, and if you try please post the results, hd2 has left me down woth a few rooms a couple of times but in the end it always worked, even if it took many reflashes!!
Click to expand...
Click to collapse
That link, it links to an app. How am I going to install the app when I cant boot Android?

I have tried task29 and hard reset without any luck.

Flash stock WM 6.5, then try again
Sent from my HD2 using xda premium

z3nful said:
Flash stock WM 6.5, then try again
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
tried it twice...

what's the cwm log say? From advanced options you can have it put recovery.log on your sdcard, or you can use adb when in cwm to check it.
Sent from my HD2 using xda premium

this might happen if you try to extract the rom and repackage in windows os...especially the kernel...
by any chance did u do this?

gdsbalaji said:
this might happen if you try to extract the rom and repackage in windows os...especially the kernel...
by any change did u do this?
Click to expand...
Click to collapse
did not repackage the rom.

May be bad blocks in memory....install rom thru cmr....Goto adv select report...mount SD...open the report file in notepad....u shouldn't see more than one bad block...else there is problem
Sent from my HTC HD2 using XDA App

freeze after data recovery using clockworkmode
I have a freeze problem with my wildfire, a little help would be appreciated.
I installed cyanogenmod 7 and everything was working fine untill I restord all data (for cotacts and apps) using clockworkmode. After data recovery the phone freezes on boot.
Can someone tell me if I did something wrong or a method to get pass the freeze?.
I downgraded back to stock ROM but I really want to use Cyanogenmod.

dotro said:
I have a freeze problem with my wildfire, a little help would be appreciated.
I installed cyanogenmod 7 and everything was working fine untill I restord all data (for cotacts and apps) using clockworkmode. After data recovery the phone freezes on boot.
Can someone tell me if I did something wrong or a method to get pass the freeze?.
I downgraded back to stock ROM but I really want to use Cyanogenmod.
Click to expand...
Click to collapse
you are aware this is the HD2 thread not the wildfire thread?
please check before posting in future

[Q] HTC HD2 from android 2.3.6 to 2.3.7 upgrade

Hi there,
I have the NexusHD2-Gingerbread_V3.1a_NAND_(Android-2.3.6) on my HTC HD2 and I downloaded the TyphooN_CM7_v3.6.8-MAGLDR ROM but there was a slight problem, everything went well up until the moment when the phone boot up which it stayed on the android figure for ever, i have waited maybe 20+ minutes for it to load/boot but there was nothing. I re-flash twice but still nothing was happening, also rebooted the phone couple of times but it kept locking at the boot up android figure screen. Do you have any ideas why or any other suggestions? Please if you could help that would be most appreciated.
MAGLDR Ver. 1.13
ClockMod 3.2
Thanks
Chris
email: [email protected]

crosis001 said:
Hi there,
I have the NexusHD2-Gingerbread_V3.1a_NAND_(Android-2.3.6) on my HTC HD2 and I downloaded the TyphooN_CM7_v3.6.8-MAGLDR ROM but there was a slight problem, everything went well up until the moment when the phone boot up which it stayed on the android figure for ever, i have waited maybe 20+ minutes for it to load/boot but there was nothing. I re-flash twice but still nothing was happening, also rebooted the phone couple of times but it kept locking at the boot up android figure screen. Do you have any ideas why or any other suggestions? Please if you could help that would be most appreciated.
MAGLDR Ver. 1.13
ClockMod 3.2
Thanks
Chris
email: [email protected]
Click to expand...
Click to collapse
Which cwm partition size did you use ? system/cahce.
If you used the right knows, that means that you have bad blocks. That can affect a lot of thing. Increasing Misc partition helps.

It is not an upgrade it is a clean installation of the nw rkm. I formatted the old system 2.3.6 and I installed the 2.3.7 ftom scratch on the internal memory of the phone. I haven't touched the sd whatsoever. The proccess was exactly the same as I did with the 2.3.6 version of android. Hmm don't know why is acting like this, please help, thanks
Sent from my Nexus One using XDA App

crosis001 said:
It is not an upgrade it is a clean installation of the nw rkm. I formatted the old system 2.3.6 and I installed the 2.3.7 ftom scratch on the internal memory of the phone. I haven't touched the sd whatsoever. The proccess was exactly the same as I did with the 2.3.6 version of android. Hmm don't know why is acting like this, please help, thanks
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Pm me your teamviewer Id. I will help you.

Right now on the phone i have the 2.3.6, am not going to do the attempt for the phone tongiht, is getting late for this now , as for teamviewer how would you help me? everything takes place on the phone. If you want we can do this on the weeknd at some point. do you have msn or skype so we can arrange the meeting? lol
Thanks for your effort bud

Try redoing the partition as the other poster said. Tytung's NexusHD2 uses a 135MB partition with 2MB of cache. Typhoon's uses a 150MB partition with 5MB of cache. If you didn't change the partition size and are still using the one for Tytung's when going to Typhoon, this is probably the cause of the boot up issue you are seeing.

Ok, you mean to make the partitions on the sd card right? And the rom will install on the sd and not on the phone then? So I have to format the sd?
Sent from my Nexus One using XDA App