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!

HTC HD2 Stuck on Android bootscreen.

Hi,
I've got an HTC HD2 here, with Android installed on it. (NAND, I believe.)
It was bought second-hand with Android pre-installed.
Because it was still linked to the google account of the previous owner, I had to restore the whole phone to factory settings. Since that didn't work, I've just decided to install another Rom.
After some messing around, I managed to install Clockworkrecovery. (It wouldn't boot for some mysterious reason) And then I installed an Android Rom. (Energy™ -.¸¸.·´¯ Sense 3.5 Runnymede)
After some time, the phone rebooted and got stuck on the Android boot screen.
I tried to install another Rom, but now they all get stuck on the boot screen. (I have tried another Runnymede rom, and RCMix3D)
Does anybody know how I can fix this?
I wiped my Dalvik Cache, I wiped my Cache partition, I wiped my data/factory reset. I am using the MAGLDR as boot thingie, but that's working perfectly.
I have formatted my SD-card with G-Parted, on my Ubuntu-PC. (First partition FAT32-750MB, Second partition EXT3 - 1GB and a Linux-Swap of 100MB)
For some strange reason, ClockworkRecovery cannot format my SD-card. (Well, it says it can, but as soon as I stick the card in my PC, the PC tells me it's corrupted. (Windows XP on my Father's PC tells me it has to be formatted, on my Ubuntu it doesn't show up as mountable)
Thank you in advance
P.S. I don't mind losing data, there's no personal data on it. Any solution (which doesn't involve buying a new phone) will do.

Quickest solution I would try is format the entire card to fat32, and see if your pc detects it. Once it does, put the rom on it, put in in the phone, boot into clockwork format data/cache/dalvik install the rom then reboot and see if it goes past the bootscreen (keep in mind first boot takes a while, but if it takes more than 2-3 minutes theres still a problem.
Do you know what partition layout of clockwork you installed by any chance? Some roms require specific layouts in order to work correctly.

Thank you for your reply.
Unfortanetly, that didn't work.
I have installed Clockworkmod like they say on jayceooi dot com. (I cannot past links yet, but here's the step-by-step guide:
Step by Step Guide
Power on your phone and don’t let go power button.
DFT MAGLDR Bootloader will be loaded.
Use volume down button to go down to 5. USB Flasher.
Then press call button to load USB Flasher mode.
Connect USB cable from PC to phone.
You should see Wait USB…USB.
At PC, right click on DAF.exe and select ‘Run as administrator’.
Click ‘Yes’ if User Access Control prompt up.
Follow onscreen instructions to install.
Phone will be rebooted after installation finished.
DFT MAGLDR Bootloader will be loaded then.
Disconnect USB cable from phone.
Use volume down button to go down to 8. AD Recovery.
Then press call button.
ClockworkMod Recovery will be loaded then.
That’s all.)
I used the 150MB-Partition one.

Didnt work how? Does the pc detect the sd card now after you formatted?
The directions you posted are right, so maybe try a different partition layout. The roms that you said you tried use different layouts than what you have and that may be a problem. Test a CM7 rom and see if it will boot, they tend to have less problems and are overall more stable than sense roms.
I recommend Typhoons rom: http://forum.xda-developers.com/showthread.php?t=933951
Try to install it and see if it boots. It uses the same partiton layout that you have now. If it boots, thats indication that you may need a different layout if you want to run a sense rom.

Well, I could re-format my sd-card and re-partition it, but it (Android) still got stock at the boot screen.
Using the Typhoon rom, I got the same problem. The Rom appears to be succesfully installed, but it didn't really boot.
I now tried to installed Windows Phone 7, this works fine. (I don't want to install WP7 however, I want to install android)
I tried the following too: (Post by a3r0n1)
http://forum.xda-developers.com/showpost.php?p=18868874&postcount=14
/
At the "Using "HD2 Toolkit" select "Magldr repartition" Make sure that you are using the recommended partition size for your rom!" part, I got an error that the file was too big when I tried to choose a partition of 300MB, I honestly have no idea what the partition size should be. (I want a sense-rom, I don't have a clear preference which)
I did install the Clockworkmod with 400MB with succes now.
However, still got the same problem. Android seems to get in a loop somewhere in the boot screen
EDIT:
I noticed that the Micro-SD card always corrupts after CWM installs the Android-Rom.
I think that may be the core of the issue here.
Does anybody know how I can install Android without CWM?

Are u repartitioning the phone? That might be the problem. Hope this helps
Sent from my Nexus One using XDA App

I manager to install an old Desire-based rom with Android 2.2 through a daf installation.
This one works fine but I still would like to install a Rom with Android 2.3 via a more regular way.
One problem I'm facing with this Rom is a very limited amount of internal storage. (about 55MB)
And I've got a big battery leak, the battery drains very fast. Much faster than my Desire HD. (The HTC HD2 we're talking about isn't mine, It's my mother's)
So does anyone know how I can install a regular Rom (preferably runnymede based) without CWM? Or does anyone know how I can resolve my problem?
@akaruna: I do not know how to partition the phone, I believe I didn't do that. Should I? I did partition the SD card. (CWM made unreadable cards for some obscure reasons, so I partitioned the SD card using gparted on Ubuntu)
Thanks in Advanced
Sjoerd

If you have limited internal storage then the main problem is the partition table is not correct. This is also why the roms you install are stuck on the bootscreen. When you install roms that require a bigger partition table than what you already have on your phone they will be stuck in a bootloop.
Go and download the HD2 NAND TOOLKIT: http://forum.xda-developers.com/showthread.php?t=1090783
Check out the video to familiarize yourself with the features, then repartition your MAGLDR with the correct partition table that the rom you want requires. Go into clockwork and install rom from zip.

Yes the tool kit is the best.

Yea the toolkit works wonders. Even though I still do it the original way ;p I do everything faster that way for some reason
Sent from my Nexus One using XDA App

Oh and yes, always read the thread from that certain Tom so that way u know exactly what partition table/size to use. Usually linked also.
Sent from my Nexus One??? (HD2) using XDA App

I tried it again with this rom: "[18Dec 2011] [CMR] Sensation xl Sense3.5/2.3.5 v2.7 BETA OC & marc1706 0.1.3 kernel" (I believe I'm still not allowed to post links)
I used the NAND toolkit this time for the System Partition Size.
The only thing I actually did was clicking 350MB as System Partition Size and then I clicked repartition. And then I followed the on-screen instructions, which involved clicking next and after some installing some drivers everything went fine. (With the HD2 in USB-flash mode of course, it also said the job was completed succesfully)
I wasn't able to choose a bigger size for some reason, it told me the 400MB was too big.
Still the same problem, the phone gets stuck at the Android boot-screen.
Does anybody have an idea? Thanks in advance (Again, I'm not scared of losing any data, if anyone has any solution at all: I'm more than happy to hear it)

I tried another DAF rom and got the following error:
"Error Description: Size is too big.
Info: .\RSPL\RSPL.cpp (800)"
So I tried repartitioning the System Partition Size (MAGLDR) to 400Mb.
However, It gave me the exact same error.
Does anyone know has any idea? (For example, how I can change the partitions in another way)
(Partitioning it at 360MB works fine)

Not sure what it is but the DAF file I use let me partition to 445...... those sense time are heavy and if the partition isn't right it will bootloop or not
Sent from my HTC HD2 using XDA App

" sense time " and do you have the sdcard partition at 1gb?
Sent from my HTC HD2 using XDA App

............ sense rom.........
Sent from my HTC HD2 using XDA App

hd2 stuck on startup all android rom

hi
i installed many rom on hd2 via clk cwm .zip from sd card many rom stuck on start up but some starts but after restarting or powering off the the same problem with all roms plz help to boost ur thanks meter

Make sure you perform "wipe data factory reset" in cwm, to ensure the files on the ext and android folder on fat32 are cleared before flashing the rom.
If possible try a different SD card and sim, they can both cause issues occasionally.
Any stability issues on winmo?

Just give us more info about that ..
Are you sure you are using correct system partition size?
Any SD-ext? Sense (big) roms?
Did you try complete reflash? (-> winmo -> hspl -> radio -> clk+cwm -> android)
You (We) can check your logcat, there should be answer for this issue.

i dont know about the system partition i think this is the problem some roms need
160/5 mb system partition how to do this partition

I had the same issue and I redownloaded and reinstalled CWR from this post:
http://forum.xda-developers.com/showthread.php?t=1044830
I used the 400mb file from the post.
Cheers

tauqeer512 said:
i dont know about the system partition i think this is the problem some roms need
160/5 mb system partition how to do this partition
Click to expand...
Click to collapse
any rom you flash will tell you in post 1 what size partition to use.
asbestos said:
I had the same issue and I redownloaded and reinstalled CWR from this post:
http://forum.xda-developers.com/showthread.php?t=1044830
I used the 400mb file from the post.
Cheers
Click to expand...
Click to collapse
thats a fine fix, however if you flash a smaller rom to that, you will waste the extra space. so flash a 250 meg rom to a 400 meg partition, you will lose 150 meg, it wont be used for apps or data, the system will just ignore it.

Every time u flash do TASK29,RADIO,MAGLDR,CWR ,FORMAT SD,PARTITION SD then put rom on it then flash it. Everytime i do not follow that procedure i stuck on boot

Always Task 29.

Cjovecje! said:
Every time u flash do TASK29,RADIO,MAGLDR,CWR ,FORMAT SD,PARTITION SD then put rom on it then flash it. Everytime i do not follow that procedure i stuck on boot
Click to expand...
Click to collapse
Hello guys,
I am experiencing the same problem with my HD2.
I have Tasked29, flashe MGLDR, CWR, formatted and partitioned SD, then placed ROM file and flashed. I reboot and the phone gets stuck on the HTC screen. The flashing of the ROM takes very little time. Before I had this problem, flashing a ROM would take longer than what it does now. It completes in about 10 seconds or less!
I can't figure out what's wrong. I had to re-install an old ENRGY Windows ROM; better than nothing! This ROM is working fine, even without the SD card.
I had been flashing CWR 4.0. I will flash 3.0.2.5 and see what happens.
Any one has any ideas please?

cubexe said:
Just give us more info about that ..
Are you sure you are using correct system partition size?
Any SD-ext? Sense (big) roms?
Did you try complete reflash? (-> winmo -> hspl -> radio -> clk+cwm -> android)
You (We) can check your logcat, there should be answer for this issue.
Click to expand...
Click to collapse
thanks for reply how can i make partition i have problem with my phone usb port board damage and could not connect to pc. help plz

tauqeer512 said:
thanks for reply how can i make partition i have problem with my phone usb port board damage and could not connect to pc. help plz
Click to expand...
Click to collapse
Follow this tutorial by kylew1212 to install cLK 1.5 . (don't forget to thank him)
After it installs, boot while holding the back button > Settings > Repartition NAND > *After you finish selecting your sizes* choose "COMMIT" .
Phone will reboot, then go to "Recovery" and flash your rom from there.

[Q] After installing BoyPPC V55 no other ROM can be installed

Well the title says it all, I've tried the ROMs past V55 and they all stuck on the logo screen. Tried now ICS ROM and doesn't go past logo. I've done Task 29 and cleared every cache and format the SD and put best radio version. Nothing. help....

Did you use the right partition size? That sounds like the problem to me.

Perhaps I don't really know how to partition. I've used the 400mb recovery and partitioned a 1024mb sd folder under the add-recovery->advanced->Partition SD Card
they demanded above 180, which does raise some eyebrows.

Hd2 toolkit is ur friend.
U can task 29
Repartition
Flash
Good luck
Sent from my nexus one using XDA App

[Q] Boot problem with all Roms

Hello everybody
Just to describe the problem I quote what I've written here:
http://forum.xda-developers.com/showthread.php?p=32054164&posted=1#post32054164
Hello everybody
I've got a little problem... after a system crash (don't ask me how that happened) I had to re-flash my ROM. Now, after the reboot the "H" was flashing on my screen and turning around 'n around 'n around... after 30 minutes I plugged out the battery and re-plugged it in. Since then I’m not able to boot into Android, I only get the “Android” Text and Logo on my screen but the “H” doesn’t appear anymore.
I tried to re-flash the Rom and also wipe my device (task29), re-flash clk (I got now the 5.0.2 ClK Recovery) and HBoot. But I’m not able to boot the device. I also tried to flash other CM7 Roms (Partition 160 MB, Cache 5MB) but it doesn’t work for me
Anyone got an idea?
**********************************
Click to expand...
Click to collapse
Originally Posted by plasmastrike View Post
I had this exact problem a while ago, Where every ROM I flashed was corrupted. My issue was caused by bad NAND blocks. the H boot screen in Hyperdroid ROM is the boot animation. The android test boot screen is the default boot screen in android. The reason you got that is probably because your bootanimation.zip got corrupted somehow, so it loaded the default one in android. bad NAND blocks can corrupt everything and it starts getting worse as you flash new ROM's and use because of its hardware limitations.
There are two ways of fixing this problem. One way requires you to use Mutty and was technical and mayby had a chance destroy your NAND, I don't remember because it was a while ago I was researching this.
The other solution which is what I recommend and did because it is a lot simpler and easier is to work around your corrupted block. You can do this a couple of ways:
Firstly, a way is to use CLK 1.5 to move a partition over the problem. For instance if you had a bad block around 25 put the first partition recovery partition to 30 MB. Then you can enjoy flashing ROM's again without the NAND problem. I have this solution working now.
Secondly, another simpler way is to use an Android SD ROM to bypass the corrupted block on you internal NAND now and forward into the future.
For more information about bad NAND blocks and to figure out if you have them and where they are go to:
http://forum.xda-developers.com/show....php?t=1189544 (Application)
http://en.wikipedia.org/wiki/Flash_memory#NAND_flash (Theory)
Click to expand...
Click to collapse
We'll thank you for your fast answer. I tried various sizes of the partitions but none worked for me. I now got a error msg in H Boot "A unrecoverable error occurred" and the phone shots down. Also I don't get any of the "bad block" errors in my recovery log when erazing and re-installing a ROM.
I hope you can help me out
Can I use a SD Rom and boot it via H Boot?
Edit 2: So now after flashing a ROM and rebooting with Clockwork Mod it starts himself, than shuts himself down after a few seconds with the HTC Logo, than boots into H Loader... and always the same error message: "A unrecoverable error occurred, rebooting to Bootloader"
Click to expand...
Click to collapse
I now reinstalled everything with the American Android starter Kit, installed CLK 1.4.0.1 & RUU 190 _ 5 image (190 system, 5 cache) and tried to flash a ROM.
ClK Fastboot stops saying:
fastboot_init()
udc_start()
-- suspend --
What can I do now?
Yes I already tried to wipe dalvik cache, format boot.... I think the problem must be somewhere else...
Please help me!!

Well it seems that I fixed the problem... I found a old Backup from a new flashed ROM in Clockwork Recovery. I flashed that and my phone did boot again.
Cannot understand what happend. Is it possible that moving the ROM files to flash on the sd card can corrupt them?

Blacklight-IT said:
Well it seems that I fixed the problem... I found a old Backup from a new flashed ROM in Clockwork Recovery. I flashed that and my phone did boot again.
Cannot understand what happend. Is it possible that moving the ROM files to flash on the sd card can corrupt them?
Click to expand...
Click to collapse
got the same problem only thing that helped me was to remove all and reinstall it again from the beginning with task29