I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
fxdstudios said:
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
Click to expand...
Click to collapse
Hi. I am not sure , but you can try to formar the SD card, because with the phone seems to be O.K. I am formatting always with Panasonic sd formatter , before flashing.
fxdstudios said:
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
Click to expand...
Click to collapse
Hi,
It sounds like your CWM partition is too small .
Are you sure you are flashing the correct CWM size according to your ROM's [OP]?
Try using KSUBEDI's TOOLKIT (Don't forget to thank him).
It's a simple way of partitioning your CWM.
yes i make sure CWM is correct partition size
Yes I always make sure I use the recommended partitioning in the op of the rom I choose.
I have formatted my SD-card with the panasonic tool
as far as the toolkit. It may be something I did wrong but this started with my phone after my FIRST USE of the toolkit.......PROBABLY NOT THE TOOLKIT although I would love to know what I did to my phone.
I just flashed another HD2 about 10 minutes ago and no issues at all.
The only thing I can think of is possibly nand corruption but then again all things I try to do complete 100% except booting nand.
yes i make sure CWM is correct partition size
Yes I always make sure I use the recommended partitioning in the op of the rom I choose.
I have formatted my SD-card with the panasonic tool
as far as the toolkit. It may be something I did wrong but this started with my phone after my FIRST USE of the toolkit.......PROBABLY NOT THE TOOLKIT although I would love to know what I did to my phone.
I just flashed another HD2 about 10 minutes ago and no issues at all.
The only thing I can think of is possibly nand corruption but then again all things I try to do complete 100% except booting nand.
fxdstudios said:
Yes I always make sure I use the recommended partitioning in the op of the rom I choose.
I have formatted my SD-card with the panasonic tool
as far as the toolkit. It may be something I did wrong but this started with my phone after my FIRST USE of the toolkit.......PROBABLY NOT THE TOOLKIT although I would love to know what I did to my phone.
I just flashed another HD2 about 10 minutes ago and no issues at all.
The only thing I can think of is possibly nand corruption but then again all things I try to do complete 100% except booting nand.
Click to expand...
Click to collapse
Hi,
Did you transfer the ROM by cable or card reader?
Corruption can occur with cable(USB)transfers.
card reader in my laptop.
Like I said I have done this numerous times. Close to 100 times I would guess. I do two hd2s for friends today. no issues with either. although mine is still giving the error no matter what I do.
First time I have seen this error and I do not care about my data or backups or anything of the sort.
I have done EVERYTHING to try and rectify this issue I am having to no avail.
I am stumped at this point
bump I am unsure of what to try now
Did you find a solution????
I also have the invaild boot image header error.
This used to be my phone, but i have handed it down to an employee.
He has caused a fault where it force closes with android.process.media, especially when i go to market.
I thought i would update the rom and hopefully "delete/overwrite" the problem.
One thing i did was a backup with ROM manager and upgraded that to 4.
This phone will boot into the existing ROM - Nightlys typhoon 3.2.8, but if i try to go into recovery I get the error.
Anyone found the answer????
fxdstudios said:
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
Click to expand...
Click to collapse
well i dont think that 135 is the exact partition ....135 is used for nexus hd2 but for typhoon rom or hyperdroid rom u must use 150 mb systeme partition with 5 mb cach ...try from the start with task29 to clear everything and flash angain i'm sure it will work
Are you still having this? I seem to be having the same problem now. If I restore a backup it will give me "invalid boot image header". If I put a new ROM over my backup it works fine. I have task 29d. Loaded cLK, CWM, and then a new ROM. Backed this up and then immediately restored it and got the same error when trying to boot. I can get into recovery fine. I have tried different cLK partition layouts too. ):
I did it too, this is the problem and the fix
http://forum.xda-developers.com/showthread.php?t=1040564
Related
Someone please help me!! Before all i problems my phone kept freezing in boot and i tried everything by cleaning my sd, ad hard reset and changing builds and the same boot freeze kept happening. So after getting tired of that and having to hard reset everyday i eventually flashed TMOUS stock rom then after tried to do the magldr 113 isntall. I got magldr installed on my phone and then i choose the ad recovery. When i do i get this message "no boot source". I tried looking up on these forums and can't find anything to fix my problems. Someone please help me with a step-by-step guide. I don't want to own an hd2 running the crummy wm6.5 :/ I NEED ANDROID
download hd2 toolkit. afterward install magldr update recovery, follow the prompts to install and your done. in a nutshell...you were missing clockwork recovery. let me know if this helps
danielfc741 said:
Someone please help me!! Before all i problems my phone kept freezing in boot and i tried everything by cleaning my sd, ad hard reset and changing builds and the same boot freeze kept happening. So after getting tired of that and having to hard reset everyday i eventually flashed TMOUS stock rom then after tried to do the magldr 113 isntall. I got magldr installed on my phone and then i choose the ad recovery. When i do i get this message "no boot source". I tried looking up on these forums and can't find anything to fix my problems. Someone please help me with a step-by-step guide. I don't want to own an hd2 running the crummy wm6.5 :/ I NEED ANDROID
Click to expand...
Click to collapse
do this...depending on the recommended recovery size (typically 5-150-5 for non sense versions) download a recovery from here ..then restart you phone...go into magldr...go to flasher...once the usb is linked to pc run daf.exe from the recovery (extracted folder)...u will then have recovery installed
gdsbalaji said:
do this...depending on the recommended recovery size (typically 5-150-5 for non sense versions) download a recovery from here ..then restart you phone...go into magldr...go to flasher...once the usb is linked to pc run daf.exe from the recovery (extracted folder)...u will then have recovery installed
Click to expand...
Click to collapse
YOU SIR ARE GREAT!!! thanks so much!!!!! i can now use android! im glad it works.
Welcome...glad it worked
Sent from my HTC HD2 using XDA App
gdsbalaji said:
do this...depending on the recommended recovery size (typically 5-150-5 for non sense versions) download a recovery from here ..then restart you phone...go into magldr...go to flasher...once the usb is linked to pc run daf.exe from the recovery (extracted folder)...u will then have recovery installed
Click to expand...
Click to collapse
Great ! I will try it out as well. I have been getting this error for the last few times. I am not sure why this happened.
I installed a WP7 rom and then went back to android (hopeless battery drain with my SD card ... not sure if I can ever do something about that). I could not get back to AD recovery.
Thanks again !
gprash said:
Great ! I will try it out as well. I have been getting this error for the last few times. I am not sure why this happened.
I installed a WP7 rom and then went back to android (hopeless battery drain with my SD card ... not sure if I can ever do something about that). I could not get back to AD recovery.
Thanks again !
Click to expand...
Click to collapse
If you loaded WP7 it may have locked your SD Card - need to format in a Nokia phone. Or reduced the usable size to 200mb - this can be fixed with a partitioning tool from PC
when go back and forth between WP7 and Android the nand is overwritten ... thats why you loose your AD recovery.
REMEMBER - if you ever try WP7 and come back to Android dont forget youll need to task 29 (to clean out that nasty M$ dirt!), flash magLDR, flash recovery ( i usually stick with a 200 mb partition, as i usually run Hyperdroid, AND that way there are no worries about bad blocks), and then the rom.
although its not NECESSARY its recommended buuuut to avoid weird restarts, FCs, and any other random glitches that may occur down the short road ITS NECESSARY! :-D
good luck
hello everyone! I just installed android on my HTC HD2 successfully but when the phone reboot, shows me the MAGLDR says me that android booting from start and I have to setup android everytime I reboot the phone from the start. someone help me passing this step. thankyou in advance
Yellow XDA!
I've got this thing when trying to get a new Sense 3.0 rom. I've been looking for a good one and found that one. (Please point me to your favorite sense 3.0 ROM)
When installing, I've had some trouble with partitioning SDCard, installing a ROM (status 0 error, aborting installation)
I'm using 2.08 HSPL, MagLDR 1.13, CWM v4 & Radio 2.15.50.XX
I'm able to install a ROM (tried http://forum.xda-developers.com/showthread.php?t=733649)
But when I reboot after installing (in CWM), when it should load, it doesn't go past the Android loading screen
So It boots, MagLDR shows up, no errors, gogogo thingy, then it freezes (splash screen I guess)
I've been looking for some solutions but haven't found anything that works.
Tried other radios, CWM versions, ROMs...
I've got no idea what to do
Any help is appreciated.
Syntax1993
Tmous or regular? If regular, do you have the 1gb ext partition set? Also, that rom will take a while to set up since it requires a lot of stuff to be unpacked onto the SD card.
I've not used that rom but I know some of the big ones take tens of minutes for first boot
samsamuel said:
Tmous or regular? If regular, do you have the 1gb ext partition set? Also, that rom will take a while to set up since it requires a lot of stuff to be unpacked onto the SD card.
I've not used that rom but I know some of the big ones take tens of minutes for first boot
Click to expand...
Click to collapse
I used the EU version. I did indeed (try to) partition the SDCard but when clicking advanced, partition, 1024, 0, It told me to wait, and wait, and wait, and wait, and when after like half an hour, I pulled out the SDCard, it's 1GB smaller in Windows so it should be done.
Installing works fine.
I'll try starting the ROM again & look if it works after a couple of hours.
Doesn't work. It ran all night, didn't get past the Android screen.
I ran into a similar problem. I downloaded a file from the forum called Wipe_it_CWR.zip before installing the new rom and that resolved my issue
You mean just installing it via CWM before the ROM right? Nothing else special?
Trying it now. So far, it seems like it won't work.
EDIT: Nope sorry. It's really weird.
Hi there,
I haven't flashed a new Android ROM in a while on my good old HD2.
Things got changed...
I have magldr installed, and I also just installed CWM and seems to work fine too.
And I partitioned my SD card with a 1GB ext4 partition.
When I flashed a ROM in CWM, and I want to boot it, it keeps being stuck in the bootscreen of the ROM after magldr loaded it.
And yes, I have been waiting like 30 minutes, because I know the first boot takes a while, but not 30 minutes...
I have this issue with every Android ROM, and I am wondering what the problem could be, because I'm already struggling with this for lots of hours, but still haven't find any solution.
Windows Phone 7 via DAF.exe seems to work fine though, so my guess it that there is something wrong in partitions? but I am not sure at all.
I hope anyone could help me, I would really appreciate it.
Thanks in advance!
Joshoon
joshoon said:
Hi there,
I haven't flashed a new Android ROM in a while on my good old HD2.
Things got changed...
I have magldr installed, and I also just installed CWM and seems to work fine too.
And I partitioned my SD card with a 1GB ext4 partition.
When I flashed a ROM in CWM, and I want to boot it, it keeps being stuck in the bootscreen of the ROM after magldr loaded it.
And yes, I have been waiting like 30 minutes, because I know the first boot takes a while, but not 30 minutes...
I have this issue with every Android ROM, and I am wondering what the problem could be, because I'm already struggling with this for lots of hours, but still haven't find any solution.
Windows Phone 7 via DAF.exe seems to work fine though, so my guess it that there is something wrong in partitions? but I am not sure at all.
I hope anyone could help me, I would really appreciate it.
Thanks in advance!
Joshoon
Click to expand...
Click to collapse
I wrote a guide about all this is you're interested. Check it out and if you have questions let me know.
Sent from my HD2 using xda premium
did you flashed the correct CWM partition layout ? like for example
150MB System/5MB Cache after that u flash the rom ..
kylew1212 said:
I wrote a guide about all this is you're interested. Check it out and if you have questions let me know.
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
But still I am wondering what I'm doing wrong in my progress.
_JaSoN_ said:
did you flashed the correct CWM partition layout ? like for example
150MB System/5MB Cache after that u flash the rom ..
Click to expand...
Click to collapse
Well I am not sure about that actually :O
I also tried a magldr partition of 445MB.
And I used the Recovery_400M.
But CWM looks to work fine.
I tried again.
Want to flash this ROM: http://forum.xda-developers.com/showthread.php?t=1275119
I made a 1GB ext4 partition before.
With HD2 ToolKit I made a 175MB System partition, and a 8MB cache size.
Guess what?
It seems that it's booting now
Still waiting till it's fully booted, but I'll keep you updated.
Thanks kylew1212, you made me understand the 5/175/8 formats.
By knowing this I actually succeeded now
joshoon said:
I tried again.
Want to flash this ROM: http://forum.xda-developers.com/showthread.php?t=1275119
I made a 1GB ext4 partition before.
With HD2 ToolKit I made a 175MB System partition, and a 8MB cache size.
Guess what?
It seems that it's booting now
Still waiting till it's fully booted, but I'll keep you updated.
Thanks kylew1212, you made me understand the 5/175/8 formats.
By knowing this I actually succeeded now
Click to expand...
Click to collapse
you also could have used this
EXT4 MGLDR Recovery for EU: cant post links
MD5: 41C21AF0968304C0DC3DA28B87FD2BC6
u flash this and after that u flash the rom
_JaSoN_ said:
you also could have used this
EXT4 MGLDR Recovery for EU: cant post links
MD5: 41C21AF0968304C0DC3DA28B87FD2BC6
u flash this and after that u flash the rom
Click to expand...
Click to collapse
I installed this http://forum.xda-developers.com/showthread.php?t=898913
You can do it yourself,open the recovery folder,right klick on flash.cfg,open with editor.Now you can change the values of "boot yboot", "system ya", "cache ya" how it is on the Discription for the rom you would to flash.Now you must save it.
That´s all !!
Plainy said:
You can do it yourself,open the recovery folder,right klick on flash.cfg,open with editor.Now you can change the values of "boot yboot", "system ya", "cache ya" how it is on the Discription for the rom you would to flash.Now you must save it.
That´s all !!
Click to expand...
Click to collapse
But for what is this?
Because I got the ROM fully working now with the way I described before.
I also get stuck on bootscreen with every rom that i flash with CWM.
Until i flashed a new kernel today i didnt have that problem (using ThypooN CM7). When it got stuck i did a task 29 to try and fix it.
Maybe i am missing something, this is what i do using HD2 Toolkit:
task 29
flash 2.15.50.14 radio (at first i didnt do that but i makes no difference)
install MAGLDR
install CWM
flash rom with CWM
I am using a 150/5 patiton for the ROM (recomemded in the OP), i also tried 160/10 but again it doesnt work.
CWM installs the zip normally. When i try to boot the rom it just gets stuck at bootscreen. I tried leaving it for 20 min and it still doesnt work.
I even installed wm6.5 and did the whole process of installing MAGLDR again to see if that helps but the same thing happens.
I also tried using cLK and got stuck again with every rom.
cLK, MAGLDR and CWM all work just fine, that is why i have no idea why the rom gets stuck at bootscreen.
It seems to me that the CWM doesnt install the rom corectly. The only rom that does work is AmeriCan Android becouse i doesnt need CWM.
Is there anything i can do to fix it?
Thanks
cicnabru said:
I also get stuck on bootscreen with every rom that i flash with CWM.
Until i flashed a new kernel today i didnt have that problem (using ThypooN CM7). When it got stuck i did a task 29 to try and fix it.
Maybe i am missing something, this is what i do using HD2 Toolkit:
task 29
flash 2.15.50.14 radio (at first i didnt do that but i makes no difference)
install MAGLDR
install CWM
flash rom with CWM
I am using a 150/5 patiton for the ROM (recomemded in the OP), i also tried 160/10 but again it doesnt work.
CWM installs the zip normally. When i try to boot the rom it just gets stuck at bootscreen. I tried leaving it for 20 min and it still doesnt work.
I even installed wm6.5 and did the whole process of installing MAGLDR again to see if that helps but the same thing happens.
I also tried using cLK and got stuck again with every rom.
cLK, MAGLDR and CWM all work just fine, that is why i have no idea why the rom gets stuck at bootscreen.
It seems to me that the CWM doesnt install the rom corectly. The only rom that does work is AmeriCan Android becouse i doesnt need CWM.
Is there anything i can do to fix it?
Thanks
Click to expand...
Click to collapse
I'm not sure what's going on. I've flashed many roms with cwm. Never a problem. However if you think cwm is your problem try another recovery, there are a few more available now. I've started using team win recovery project (twrp)
One other thing. It is not necessary to reflash the radio everytime. Once it is installed it does not uninstall unless you change to a different radio.
Sent from my HD2 using xda premium
I also flashed many roms with CWM and i never had a problem before.
Now i tried twrp with clk (clean install with task 29) and it flashes the rom normally. After i reboot i get the bootscreen, then i should get the boot animation and all i get is a black screen (the backlight is on). Few seconds later the phone vibrates like it booted but the screen is still black. If i restart the phone the same thing happens again.
I guess i'll have to use wp7
Thanks anyway
---------- Post added at 01:56 PM ---------- Previous post was at 01:14 PM ----------
I finally got it to work
It was the last thing i tried before flashing wp7. In wp7 OP it says that you have to install wm6.5, let it boot and then install MAGLDR. The important thing here is that you dont use task 29.
I installed wm6.5, let it boot, then install MAGLDR and CWM (without task 29) and now it works perfectly
cicnabru said:
I also flashed many roms with CWM and i never had a problem before.
Now i tried twrp with clk (clean install with task 29) and it flashes the rom normally. After i reboot i get the bootscreen, then i should get the boot animation and all i get is a black screen (the backlight is on). Few seconds later the phone vibrates like it booted but the screen is still black. If i restart the phone the same thing happens again.
I guess i'll have to use wp7
Thanks anyway
---------- Post added at 01:56 PM ---------- Previous post was at 01:14 PM ----------
I finally got it to work
It was the last thing i tried before flashing wp7. In wp7 OP it says that you have to install wm6.5, let it boot and then install MAGLDR. The important thing here is that you dont use task 29.
I installed wm6.5, let it boot, then install MAGLDR and CWM (without task 29) and now it works perfectly
Click to expand...
Click to collapse
Thanks for letting me know that. Other people are having trouble as well. I will update my guide to include this.
Sent from my HD2 using xda premium
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.
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