Database Users

Android bootloop, windows reinstalled now AndroidSD does not work!

Hi, this is a funny situation I'm in because 99% of the time I find solutions to my own problems searching this thread but I'm in a unusual situation and I'm looking for suggestions.
I was running MDJ cynogenmod 7 v.2.2 under CWM and MAGDLR 1.11 with no problem, however because some apps did not work in gingerbread I decided to go back to froyo, which I tried MDJ revolution also on MAGDLR under CWM, and got stuck on a bootloop. I blamed my partitioned (Fat/EXT4) SD card and formatted it (FAT)only and re-flashed REVOLUTION via CWM, still got bootloop so i went over CWM, and flashed it via USB Flasher to be stuck in bootloop again, just before i started crying about my dead HD2 I figured to flash windows 6.5 again and thankfully it worked. But after 5 minutes of using windows I needed android so I downloaded a SD version and tried to run it via Heret, and this is where the situation comes because I already tried many versions of android SD and none bootup. Yea it sounds like my SD but I have already formatted, any suggestions would be appreciated.

ralphsancho said:
Hi, this is a funny situation I'm in because 99% of the time I find solutions to my own problems searching this thread but I'm in a unusual situation and I'm looking for suggestions.
I was running MDJ cynogenmod 7 v.2.2 under CWM and MAGDLR 1.11 with no problem, however because some apps did not work in gingerbread I decided to go back to froyo, which I tried MDJ revolution also on MAGDLR under CWM, and got stuck on a bootloop. I blamed my partitioned (Fat/EXT4) SD card and formatted it (FAT)only and re-flashed REVOLUTION via CWM, still got bootloop so i went over CWM, and flashed it via USB Flasher to be stuck in bootloop again, just before i started crying about my dead HD2 I figured to flash windows 6.5 again and thankfully it worked. But after 5 minutes of using windows I needed android so I downloaded a SD version and tried to run it via Heret, and this is where the situation comes because I already tried many versions of android SD and none bootup. Yea it sounds like my SD but I have already formatted, any suggestions would be appreciated.
Click to expand...
Click to collapse
this might sound a bit daft but have you checked the radio version after flashing the winmo rom?

despy1989 said:
this might sound a bit daft but have you checked the radio version after flashing the winmo rom?
Click to expand...
Click to collapse
yes i have the same radio i always had 2.10.50.26

Just wondering, did you have the correct partition size for system?

Use "SD Card Formatter" and set it to FULL and ERASE ON.

thank you!
thanks for your quick help
after running windows for one day I decided to give MAGDLR another try and just like that it worked perfectly and flashed a very old MDJ Revolution build. it seems that after I formatted SD to FAT only I stupidly tried to flash a APP2SD nand build, which [i think] caused the problem [idk if this was it but my guess is that ap2sd builds only work if you have a [FAT]/[EXT] formatted SD Card (i thought it was kind of optional)]
as for running android via SD, no luck via windows, no luck via MAGDLR, but I have it via nand so I am very very happy
Thread closed

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!

[Q] Magldr no boot source

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

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

[Q] No screen input from android / wm

Hey guys, I need some quick suggestions if anyone has it. Currently I have a non working phone.
I have been running an ICS NAND rom on my hd2 for a while now, havnt had any issues (a few niggles with the rom, nothing major) so I thought today I would update to the latest version.
I used the hd2toolkit to resize the partition to the biggest size it would allow, then used ad recovery to flash the new .zip to the nand. This is where my problems started, whenever i booted it just showed the boot animation, (I waited over an hour and pulled the battery out and re booted / reflashed a few times).
I found with a differnet rom i tried, pulling out the SD car would allow it to get to the welcome screen, but no screen input was accepted. I thought this was a bit weird but pushed on. I tried a different rom and it stated after flashing that it was optimising applications and looked like it was stuck in a boot loop. I did some reading up about it and found that task29 should help. I ran this but then all the phone would do is show the green HTC on the white background, it wouldnt let me to get into magdlr menu.
I then decided to to a full restore and go back to the wm rom from th HTC site (The australia telstra version), this seemed to flash on fine, but now I can not slide or click buttons in wm, no screen input is accepted. Which is strange as it was doing this in an android rom, as I mentioned previously.
Any ideas on how I can get touch working / get a NAND android rom to work again.
Thanks in advance guys

First verify that you have hspl installed by powering on while holding vol down button to get to bootloader screen
Go back to the hd2 nand toolkit
1.task29
2. Select either cLK repartition or Magldr repartition and select size for your rom (not the maximum size). 200 mb is fine for ics using sdext partition.
3.Select magldr update recovery or cLK install recovery depending on your selection above.
4. Reboot phone by pressing power and holding to get to magldr or power and home button to get to cwm recovery.
5. Install ICS from sd card as before

Thanks for the help, I had to flash a different radio version to get magdlr to boot.
I now have android running of my NAND, but the screen is non-responsive now, as it was yesterday.
I doubt it is hardware related, because I have never had an issue before yesterday when I wanted to change the android version, any ideas how I could get it working?

Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.

htccraze said:
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
Click to expand...
Click to collapse
I have tried two different android roms and the stock wm image from htc's site, all of which the screen doesn't work on. I will have a try with a cyanogen ROM and see if that makes a difference. Thanks

http://forum.xda-developers.com/showthread.php?t=769026
I just tried this rom and still no deal. This is very weird as I haven't had any issues with the screen at all, the phone is still in new physical condition.
Does anyone want to have a stab in the dark, as I really need to use it as a GPS tomorrow and any help would be appreciated.

Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.

htccraze said:
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
Click to expand...
Click to collapse
When installing a new rom, I have resized the magdlr partition, then copied the .zip to the sd card, then in ad recovery installed the zip through there. This has worked fine in the past. I followed the videos you have linked and I'm pretty sure I'm doing everything right and yes ive used task29 several times. In AD Recovery every time it states that installation has been successful. I have also formatted my SD card many times.
The ROM you linked, I can find download links on the page, not sure if I'm just missing them.
I just tried an SD card rom, its doing the same thing, no touch input is accepted.
Does NAND roms and SD roms not working imply that it could well be hardware? I just dont understand as it stopped working when I was reflashing yesterday and it was not dropped or roughly handled in anyway during this process.
I am now going to investigate MTTY (for bad blocks) and try reflashing back to original WM again. Please post more suggestions if anyone has them.

Another update: I just restored to default using the method listed below.
http://www.jayceooi.com/2011/08/15/how-to-restore-stock-rom-on-htc-hd2-video/
It took around 40-ish minutes and still no input from the screen, this is seriously frustrating.
WM boots fine and everything, but still no input is accepted.

I'm sorry to say but if your having the same problem with all that then it sounds like the digitizer stopped working. Maybe someone else knows something I don't so I would wait to see if they could help out.
Sent from my HTC HD2 using XDA

Thanks mate, I am not sure why it would have just stopped last night. Appreciate all the help! I'll see if anyone else has any suggestions.

It's not a problem. I do have to admit that it does seem pretty odd the timing of it. Hopefully it's a not the digitizer and someone would be able to point out what might be the cause of everything.
Sent from my HTC HD2 using XDA

This may seem a little crazy, but after having a search online about my issue, it seems that a ribbon going to the screen / digitizer is behind the power button on the HD2s, which apparently can get loose and after a sharp press of the button it started accepting screen input again!
The issue for me now is that when the power button it will stop accepting input again, untill I press it firmly again. I think I may need to open up the phone and check all the connections now.