Related
Hi,
I have been on this forum for the past 2-3 days trying to get android on my gf's HD2 and it just wont have it.
I have tried MCCM's HD v4 Desire one
I have tried Froyo 1.5
I have tried DL Desire Series, both SD and MAGLAR.
The ones where you click CLRCAD.exe then haret.exe either say it doesent have certificates to run or parts are missing. Or it goes to a black scree and gets stuck on "Jumping To Kernel" and it stays like that for ages (tested for 1 hour, never budged)
The DL desire series via MAGLAR wont work either, I need HSPL (sp?) to install MAGLAR but HSPL keeps reporting back that the file Rapi.dll is missing.
My SPL version is 1.42**** so technically thats right ( from what I have read )
I have tried formatting the SD card via PC and device, also tried a factory reset and an additional 2 other SD cards. Still nada.
What else can it be? Someone mentioned the radio but there is so many questions being asked in a specific thread that mine gets lost and since this is more of a global issue I thought a thread of its own is deserved
I really want this and will go to any length to get it ( not keen on ROM flashing thought, would like to avoid turning the handset into a hammer rather than a phone)
Hope I havent busted any rules
Cheers,
Gib
You need radio 2.14 or more for Android.
aka, upgrade your ROM.
You are not alone
You are not alone here.
I have been having this problem too, I get stuck on the HTC white screen. though I haven't tried much ROM but I have tried formating and reflahing of my WM ROM.
I once did a stock ROM official update with: (RUU_Leo_S_HTC_NLD_3.14.404.2_Radio_15.42.50.11U_2 .15.50.14_LEO_S_Ship)
ever since I have not been able to find how to flash using SPL, I have been flashing using SSPL_RU and my radio is 2.15.50.14.
Could this reason be the problem.
I need help please I want to have a feel of droid.
Know the feeling
I have been trying all the different android magldr sd roms and everytime its the same story. First boot fine. Second boot and on it just hangs at the green htc logo. I have tried so many things i don't know what to do next.
Have you tried one of the Energy ROM's? I found on my unlocked HD2 that these were the only roms (going back a while now) that I could get Android running off an SD card. I've since heard that there is a basically blank rom for people who want to run nothing but android. It's a small rom, only about 30mb.
It's in a few places around the board. I can't remember what the name of that one is off the top of my head, but any of the Energy series, or the Miri ROM's apparently work too.
Good luck!
Gibbo3771 said:
Hi,
I have been on this forum for the past 2-3 days trying to get android on my gf's HD2 and it just wont have it.
I have tried MCCM's HD v4 Desire one
I have tried Froyo 1.5
I have tried DL Desire Series, both SD and MAGLAR.
The ones where you click CLRCAD.exe then haret.exe either say it doesent have certificates to run or parts are missing. Or it goes to a black scree and gets stuck on "Jumping To Kernel" and it stays like that for ages (tested for 1 hour, never budged)
The DL desire series via MAGLAR wont work either, I need HSPL (sp?) to install MAGLAR but HSPL keeps reporting back that the file Rapi.dll is missing.
My SPL version is 1.42**** so technically thats right ( from what I have read )
I have tried formatting the SD card via PC and device, also tried a factory reset and an additional 2 other SD cards. Still nada.
What else can it be? Someone mentioned the radio but there is so many questions being asked in a specific thread that mine gets lost and since this is more of a global issue I thought a thread of its own is deserved
I really want this and will go to any length to get it ( not keen on ROM flashing thought, would like to avoid turning the handset into a hammer rather than a phone)
Hope I havent busted any rules
Cheers,
Gib
Click to expand...
Click to collapse
Solution!
Instructions :
- Download the Android SD version of your choice. Unzip, Extract the 'Android' folder to root of your SD Card. (Make sure to Format the SD card before doing this.)
- After you have done all steps go into Android folder and tap CLRCAD (for working sound), and after that just tap HaRET
-Booting ..
-Enjoy
kottaho said:
You are not alone here.
I have been having this problem too, I get stuck on the HTC white screen. though I haven't tried much ROM but I have tried formating and reflahing of my WM ROM.
I once did a stock ROM official update with: (RUU_Leo_S_HTC_NLD_3.14.404.2_Radio_15.42.50.11U_2 .15.50.14_LEO_S_Ship)
ever since I have not been able to find how to flash using SPL, I have been flashing using SSPL_RU and my radio is 2.15.50.14.
Could this reason be the problem.
I need help please I want to have a feel of droid.
Click to expand...
Click to collapse
Ater trying some nand roms i came back to the orignal firmware( the same as you).
And i also have this problem , it just load into a picture with htc on it.
Have you tried using a different SD card? My Sandisk 8gb didn't accept anything. I had an old 512mb laying around that came with my E90, loaded SuperRAM on it (aprox 450mb including data.img) and it booted straight away.
2.15.50.* is the right radio for most SD builds, make sure you have enough free space on SD. most builds have at least 512mb if not 1gb data.img which gets created when first boot. If runs out of space it will get stuck on boot screen. No hspl required with 3.14 HTC winmo rom
I also try to get Android in my HD2 (energy ROM). I am somewhat puzzled however: I want to flick back and forth between WM and Android and many programs I have reside onto my SD card. I have read in an earlier post that before attempting Android I should format my card - does this mean that I cannot have WM data (programs etc) in the same SD card I run android? or that I can transfer them back AFTER I manage (if) to load Android?. Thank you
The SD card has to be formatted in FAT32. Just to make sure the card is clean I copy all my data to my pc, format the card and transfer it all back.
Aesthetic said:
The SD card has to be formatted in FAT32. Just to make sure the card is clean I copy all my data to my pc, format the card and transfer it all back.
Click to expand...
Click to collapse
OK thank you - got it!
Unfortunately I cannot get passed the green HTC splash screen - my HD2 stays there for time no end and the only solution is to take battery out. Any suggestions?
Assuming you've got everything set up properly (right radio, hspl, ...) which you can find on the Android forum. I think you'll have to try using a different brand of sd card. Some cards simply don't play nice with Android.
Got uber annoyed with the SD method, just ended up doing a full scale flash to ROM. Was easier lol
MrAskani said:
Have you tried one of the Energy ROM's? I found on my unlocked HD2 that these were the only roms (going back a while now) that I could get Android running off an SD card. I've since heard that there is a basically blank rom for people who want to run nothing but android. It's a small rom, only about 30mb.
It's in a few places around the board. I can't remember what the name of that one is off the top of my head, but any of the Energy series, or the Miri ROM's apparently work too.
Good luck!
Click to expand...
Click to collapse
I am using Energy ROM (Energy Serie: Energy.Leo.28244.Sense2.5.Cookie.2.0.Feb.12)
My phone just hangs on the white HTC screen when I try to boot into Android from the SD card. I flashed my ROM with SSPL_RU after an update with the Stock ROM (RUU_Leo_S_HTC_NLD_3.14.404.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship)
ehh
Aesthetic said:
Assuming you've got everything set up properly (right radio, hspl, ...) which you can find on the Android forum. I think you'll have to try using a different brand of sd card. Some cards simply don't play nice with Android.
Click to expand...
Click to collapse
I would almost agree with that except, i have 2 exactly the same 16 gb cards, each with a 3 gb fat32 primary partition. 1 loads android but wont allow me to do things like take pictures[it says there isn't an sd card.] The second card just hangs at the green htc screen. Even if I copy the working partition to the other card, it still hangs.
evo1rs said:
2.15.50.* is the right radio for most SD builds, make sure you have enough free space on SD. most builds have at least 512mb if not 1gb data.img which gets created when first boot. If runs out of space it will get stuck on boot screen. No hspl required with 3.14 HTC winmo rom
Click to expand...
Click to collapse
Thanks for this Info. I didn't take into consideration that the file will be enlarged during booting. The copied Android folder was 508MB in size but this got enlarged to about 1.3GB during boot up. I thought if I just leave about 1.2GB in all the SD card I have been trying that it should be enough. But I was wrong.
Thanks a lot I have done multiple reboot without any problem.
I am enjoying my first Android feel.
Thanks once again.
Android on HD2 hates most SD Cards
From my own limited experience to also having read many posts I can say that most sd cards prevent Android from running properly on the hd2. Mine works fine with radio 2.14/2.15 and the stock Sandisk 16gb card that came with my tmous hd2, but I recently tried a wintec 16gb card that made Android run like a broke-wheel-cart and other sd cards I have laying around make it fail.
I think everyone needs to add what card they are using to their signature, or else we might all just end up howling in the wind.
Based on some feedback from another post I just ordered this Sandisk 16gb card from Newegg. It is Model # SDSDQ-016G-A11M . It is reported that that model# provides class10 speeds even though it is sold as a class2. It's use with Android is supposed to be good.
greetings.
have had nand up and running without issue. (between hyperdroid and typhoooN; hspl 2.08 and radio 2.15 etc.)
woke up ready to do some flashing (finally am skinning and making a theme) and go into CWMR and it says cannot mount sdcard. same thing when boot into android. (no amount of rebooting solved the issue.) overall, can't get into my sdcard.
flash back to WM and sd card is just fine - everything on it, etc.
now, the only thing i did last night was move some files around using "file explorer." didn't install anything, etc. didn't feel i could let android format the card...and didn't want to risk anything so thought starting over was best.
looked around and found no solutions. ideas what happened?
I've got a HD2 just to try wp7. After some careful reading manages to install, and it was booting and used the basic features for couple of hours without any issues, until i wanted to try out maps,,,, The HD2 got stuck and went to a boot loop.
After checking so much for the one and a half day (I'm so tired and sleepy) i'm sick of this phone. I ve seen many posts regarding this issue, but no one seem to post a clear answer that rectifies the issue. Yes i've tried task 29 and gone back to wm 6.5 as well. Anything else i'm missing here.
If i keep the battery off for about 10 mins or so then it boots up properly, but not all the time. I cannot use any most of the features, only texting and calling. If anything else is launched (IE, People, A/C config...) goes back to the boot loop. WTF
Pls guys help me. well i'm a complete nOOb for this and sorry for the long post.
I am by no means an expert here, but have you tried a different SD card? When I first flashed my HD2, when WP7 was first available for it, my SD card was incompatible and it was constantly rebooting. Some SD cards are incompatible with WP7, even the ones that originally shipped with the HD2.
I know how you feel... that's exactly what happened to me. OMCA1A's right, Try a new SD Card and you should be good to go.
Which method you use ? Zune or 1 shot install
Did you have wp7 on hd2 before trying to install This rom? Was the sd card working?
Did you unlock/ reformat sd card or install straight over?
as already mentioned it can be the SD card and is most likely the SD card in your case, how you install it, cabs or zune or whatever doesnt make the slightest difference, anyone using any card that is not certified to work with WP7 stands the risk of running in to the restart issue.
it might not happen today, it might not be next month or even year, but potentially the restart issue can rear its head when xx% of storage space free is hit
i say xx because it could be anything from 1 -100.
Peronally i find that dumping a few hundred meg of music on gets past these dodgy areas, like just now, if i remove 12MB of data from my device it will start restarting, i can replicate this, if i do a reflash i have to install at least 200MB of music before doing anything, 600MB on top of that i get more restarts so dumped another 200MB of music, installed navigon, restart issues, install 50MB of music all fine again, that its a pain in the arse but its workable, it just means i have a lot of music i will never listen too on my device
Sorry I seriously gave up on my HD2 and was using my sisters old LG phone (Sucked big time ) Yes OMAC1A I have tried 4 different SD cards, so I doubt it’s the SD card.
Moschino02 What do u mean by Zune or one shot install ? I installed the normal way here are the steps I did.
Did task29
Installed latest radio
Installed MAGLDR
Then the wp7 ROM bu running a DWI.exe
Well after I got tired I did install it over and over and over. Yes the cards were working fine on my x10i
dazza9075 The SD I used was empty.
Also guys like I mentioned I only cannot use any of the smart phone features, if I get in to maps or IE or any other task which consumes a lot of CPU, it happens.
I will try one more SD card cos u guys insist and if it doesn’t I’m seriously gonna sell it off for scrap if u want let me know it’s gonna be dirt cheap I can’t tolerate this anymore.
Also one more thing guys, i've tried android as well, a 2.2 desire ROM and a MIUI ROM. Some times it gets stuck on start up it self or on the initial setup. That to me doesn't sound like a SD card issue.
Also it overheats
You tried with Sandisk class 4\6 SD cards, right? Cuz those are the only ones that have a decent chance of working.
Overheating of the HD2 is a common problem, saw many of these phones being sold on ebay with that problem...
I have the same problem... Still trying to fix it... But I know the problem comes when the phone tries to access the SD card (sandisk).
zeus09 said:
Moschino02 What do u mean by Zune or one shot install ? I installed the normal way here are the steps I did.
Did task29
Installed latest radio
Installed MAGLDR
Then the wp7 ROM bu running a DWI.exe
Click to expand...
Click to collapse
So after you install wp7 rom by running dwi.exe ( you mean v2native rom, right?)
What did you do? Did zune find updates to mango? Or did you install mango by sending cabs? What version are you on?
Moschino02 - Yes it says,
Name: HTC HD7 T9292
OS Version: 7.0.7392.0
Also i have tried other ROM as well, did not have any luck. Even at this very moment it goes through a boot loop. Just tried accessing HTC hub and it went off.
After installing sometimes it reboots or i have to manually do it by removing the battery or a by a soft reset. Yes zune finds updates but i cant update. When the rebooting point comes it never reboots to the OS just goes to a boot loop. *@#^&%$
I have used the following,
Verbatim 2GB micro SD
Unbranded 8 GB Micro SDHC
Kingmax 2GB Micro SD
Sandisk 4GB Micro SD
and none of them worked.
jinge - I dont think so. Initially i thought the same. And i removed my SD card to see but the problems kept continuing.
IF its a SD card incompatibility issue the HD2 should work fine with android. It boots only up to the initial start up screen doesn't go beyond that. MIUI is the closest i got but that too gave problems.
I'm seriously sick of the hd2 guys and i hate it i wish i could show it to you'll.
This has to be a hardware fault. IS IT ????????
Hi,
I think I didn't post too often here but now I need your help.
I also did some searching first but in threads like http://forum.xda-developers.com/showthread.php?t=1143949 I did not finy a good solution, yet.
I am owning a HD2 and used CoreDroid 1.6 till yesterday. I connected my phone via USB to my computer to load it and left office. When I came back, I noticed my phone was still on. I touched it but nothing happened. The surface was frozen. Not even the off-button showed any effect. Thus, I removed the battery, waited a bit and inserted it again.
Unfortunately the phone did not boot any more. Just hangs at the first "Coredroid Screen". I tested around and when I removed the SD card and rebooted again, it worked. I checked the card and it had some file system problems. Thus, I saved all data and formatted it. However, my HD2 did not boot also with any of the other SD cards I tested (no difference how it is formatted). The system starts booting from NANE and shows the first CoreDroid screen and then just angs.
Then I noticed, that it said after booting "internal memory is full" (I checked it: 0 kb free). I searched for the reason and I found in the internal memory root a folder /bin. Observing it I saw, that nearly ALL executables have a size of 1.5 MB. I am talking about the executables that usually have some few kB.
In panic mode, I used Task29 to completely clear NAND. Then I installed MAGLDR and the appropriate CWM for CoreDroid. I downloaded the newer version 1.7 and flashed it. Same result. Did not boot with SD card but without it worked. However, I had that strange /bin folder with only 1.5MB files. Then I used MAGLDR to clean the system partition again and installed 1.6 again but same problem. I also used not the CWM provided by CoreDroid but also the "generic" downloadable and changed settings accordingly. Same effect. I even tried a CWM with 400 MB system partition instead the proposed 390 MB but same effect. 0 Bytes free. I also tried the latest Hyperdroid and Cyanogen ROMs with the same effect.
So I wonder if there is some tool for "checking" the internal memory for possible problems? Resetting it with Task29 did not bring any benefit.
Hope someone can give me a hint what I would do in this case.
I've not checked but I seem to remember coredroid uses the SD ext for data and parts of the system, so its hardly surprising that removing or using a different SD card will stop it booting.
If you were able to boot magldr and reflash roms and install cwms, I think your internal memory should be fine.
Try flashing some other rom, preferably with no sense. I'd say hyperdroid, i remember it as quick and light.
It might be problem with your phone SD card reader hardware...
samsamuel said:
I've not checked but I seem to remember coredroid uses the SD ext for data and parts of the system, so its hardly surprising that removing or using a different SD card will stop it booting.
Click to expand...
Click to collapse
Thanks for your answers.
The strange thing is: it does not boot if ANY SD-card is inside. If I remove the SD-card, it at least boots. In other words: it boots as long as there is NO SD-card at all.
I must admin I prefer Coredroid since I think it supports many nice features like all the options when connecting it via USB cable (going online over computer connection, usb tethering, etc). However, on the weekend I try flashing again some other roms to check. Still I would like to check what is going on :/
Yeah, I believe you.
Just hope it's not a hardware problem...
Hello all,
My friend wants me to put android on the old HD2. I've followed the guides to install via NAND and installed hspl, magldr, and the latest radio for T-Mobile US. I've gotten as far as flashing a Sense Leo ROM and getting to the step where the phone says "Reset now...!" at which point the phone won't reset. So then I try it all over with Task29, then I get stuck at 96% for flashing radios. I've also encountered bootloops with magldr, vibration patterns while booting, and a bunch of other problems. I think the original ROM is gone due to one of the steps wiping it. Can someone please help me either get any android rom to work or revert back to stock? I've been at this for hours and it's really frustrating me. Thanks in advance.
Edit: It just occurred to me that this might have been an unlocked phone from the factory. I've tried downloading an official ROM from T-Mobile but they don't recognize it. It's a T8585.
Edit #2: Just tried flashing Artemis Rom, went to 100% and rebooted but got stuck on HTC screen. Also tried a shipped WWE ROM, but that quit at 9%. Someone please help me...
I've had similar problems with my previous HD2. Hangs and bootloops on flashing ROMS, and an overheating phone. After 2 weeks of spending evenings trying to get things stable, I finally gave up and sold the phone, got a new one, and flashing succeeded on the first try. On first HD2, it was definately a hardware defect. The guy i sold it to couldn't get it to work either. There are so many defective HD2's around...
Whats your Radio version?
Do you use AD Recovery in MAGLDR for flashing the ROMS? Try playing around with different System Partition sizes on MAGLDR repartition. My current HD2 is very picky about this, a 'wrong' system partition size results in various hanging and bootloop problems.
Using HD2 Toolkit, follow the following steps:
1) Task29 (from bootmenu)
2) Install MAGLDR (from bootmenu)
3) MAGLDR repartition (from MAGLDR USB Flasher)
4) MAGLDR AD Recovery -> install ZIP from SD card
5) Reboot, if problems, go to step 3) with a different system partition size
I don't remember which radio version I tried last. I think it may be the latest tmous one, which I don't think is the correct one seeing as this particular HD2 is an 1100. I've been flashing via USB flash because the installation instructions on the ROM threads tell me to. I have to reflash MAGLDR every time a ROM flash fails because it either goes into a bootloop, or it goes to MAGLDR but without any menu. Nevertheless, I will try out your method and report back.
Edit: Can I still use a European radio even if I'm in the US?
wcstick said:
I don't remember which radio version I tried last. I think it may be the latest tmous one, which I don't think is the correct one seeing as this particular HD2 is an 1100. I've been flashing via USB flash because the installation instructions on the ROM threads tell me to. I have to reflash MAGLDR every time a ROM flash fails because it either goes into a bootloop, or it goes to MAGLDR but without any menu. Nevertheless, I will try out your method and report back.
Edit: Can I still use a European radio even if I'm in the US?
Click to expand...
Click to collapse
What I am not seeing here is details which may pinpoint the problem.
You need to pick one rom which works for a fair number of us and detail *exactly* what you are doing.
The radio, once flashed, remains. My signature should point you to a radio known to work in the US.
Beyond that, how are you partitioning you device; what kind of sd card and how is it formatted and setup; how are you flashing the rom; which recovery are you using; are you making any changes to the rom zip file... We could go on but hopefully you understand that, according to Murphy, the 1 piece of information you forget to mention out of the 100+ is the one that would have made one of us go "aha!"
---
Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
Okay. I will start completely over and document my actions. I'm switching to cLK since I seem to get more consistent results.
Device: HTC HD2 T8585 1100
SDcard: SanDisk 32GB MicroSDHC formatted to FAT32
Program: HD2 Toolkit 4.3.1
ROM: http://forum.xda-developers.com/showthread.php?t=2046327
Procedure:
1. Wipe with Task29 loaded from HD2 Toolkit 4.3.1
2. Make cLK Partition of 280 MB and 5 MB cache.
- Final message on phone screen: "fastboot: processing commands"
3. Install cLK Recovery in fastboot option
- Final message on phone screen: "rebooting the device"
4. Device never reboots.
wcstick said:
Okay. I will start completely over and document my actions. I'm switching to cLK since I seem to get more consistent results.
Device: HTC HD2 T8585 1100
SDcard: SanDisk 32GB MicroSDHC formatted to FAT32
Program: HD2 Toolkit 4.3.1
ROM: http://forum.xda-developers.com/showthread.php?t=2046327
Procedure:
1. Wipe with Task29 loaded from HD2 Toolkit 4.3.1
2. Make cLK Partition of 280 MB and 5 MB cache.
- Final message on phone screen: "fastboot: processing commands"
3. Install cLK Recovery in fastboot option
- Final message on phone screen: "rebooting the device"
4. Device never reboots.
Click to expand...
Click to collapse
I will be only a little help with CLK since I don't know it but..
If this is your first Android install perhaps you should try a stable rom, not an alpha one. Anyway, you don't seem to get to the rom install at all.
Is this a US or EU device? The latter has less space..
Are you SURE CLK requires 280 MB? If this us not a typo how much space is given to system and data?
---
Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
It seems to be an EU device since it doesn't have any of the indications that it's the tmous device. But it will be used in the US.
I don't think cLK itself requires 280 MB, I set it to a higher value than what was mentioned in the ROM thread. I'm probably wrong in assuming that, when the thread says "System partition size 275," it means the cLK partition. I apologize for selecting an unstable ROM, I just picked one that I'm vaguely familiar with (i.e. CM). Should I lower the cLK partition?
wcstick said:
It seems to be an EU device since it doesn't have any of the indications that it's the tmous device. But it will be used in the US.
I don't think cLK itself requires 280 MB, I set it to a higher value than what was mentioned in the ROM thread. I'm probably wrong in assuming that, when the thread says "System partition size 275," it means the cLK partition. I apologize for selecting an unstable ROM, I just picked one that I'm vaguely familiar with (i.e. CM). Should I lower the cLK partition?
Click to expand...
Click to collapse
Look at it this way: once you get one rom to boot the rest will be much easier to try.
Okay, let's backup a little and get on common ground. It may not seem so but we're making progress.
Please keep in mind I have never installed cLK so am not sure about it. However, cLK, like Magldr, is a bootloader. As such I suspect it. Does not use a traditional partition.
I am guessing that the 280 is intended for system. The EU Leo has 512 MB if NAND space. The US (tmobile) version has 1 gb. They have, essentially the same RAM.
Your NAND memory needs to be devided into partitions: boot, system, data and, possibly cache and misc. How these are created is likely specific to your bootloader (cLK or Magldr). The file systems often are dictated by those as well - Magldr uses different formatting for the boot partition than cLK.
Anyway, you will need someone cLK knowledgeable to help if you cannot spot the problem. BTW, which version of cLK are you using? I *think* v1.5.x black is one of the preferred versions.
Once you are able to load the bootloader you can start dealing with the rom. If your device is a 512 MB EU model start with a smaller rom or one that offers DataOnEXT installation.
I will check back to see what progress you will make but first a few hours of sleep (it is 3 am here).
---
Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.
Thanks for the help. I'll look into it tomorrow as I need to sleep as well. I've been thinking of trying Magdlr again since you're familiar with it. I know how to flash ROMs on Android devices (CWM) so yes, once I get any rom flashed, the rest should be fairly straightforward. It's just not going to that critical step...
I can really recommend you to try flashing the ROM through MAGLDR instead. I have CLK issues myself, repartitioning CLK on my HD2 also leads to hanging phone. Try repartition MAGLDR instead and then flash the ROM by using AD Recovery from MAGLDR menu.
Also, repartitioning with too large system size gives hanging problems on my phone. I think due to bad memory blocks and lack of space for the rest of the programs. Try different partitioning sizes.
Try THIS rom, it is in my opinion the most stable: http://forum.xda-developers.com/showthread.php?t=1434860
Go for DataOnExt. The rom then needs 175MB, so go for 180MB system partition size when repartitioning MAGLDR.
Please create a FAT32 primary partition with 32KB cluster size, then an EXT4 primary partition with default cluster size on your SD card.
The EXT4 should be about 1GB - 2GB.
So:
1) Task29 (from phone bootmenu)
2) Install Magldr (from phone bootmenu)
3) Repartition Magldr 180 MB (from MAGLDR USB Flasher)
4) Format SD card with 2 partitions (MiniTool Partition Wizard Home Edition)
5) Place the ROM ZIP on the FAT32 partition
6) Insert SD card in phone
7) install ZIP from SD card (from MAGLDR AD Recovery)
8) Choose ROM ZIP
9) choose DataOnExt (in Aroma installer)
10) Choose Davik Cache Wipe (in Aroma installer)
11) Reboot when done
12) Have fun with Android
make sure the HD2 is not fake, there was one here before & he showed a photo of it & it really looked like the real thing, also use the HD2 Toolkit to make it easier for you.
& since it's a T-mobile there are certain Radios that can brick that model if it is such (1g version) so better do a little more reading & there are lot of reference here in XDA.
Thanks for the help. I will try it when I get home later and report back.
I think I've bricked the phone...I tried flashing Magdlr again but got only the header when it booted. So I task29'd it again and attempted reflashing. It got stuck at 96% for a super long time so I did a battery pull. Then I tried booting it into recovery and it does nothing but vibrate...recovery, hard reset, nothing works...looks like the end of the road for this phone.
wcstick said:
I think I've bricked the phone...I tried flashing Magdlr again but got only the header when it booted. So I task29'd it again and attempted reflashing. It got stuck at 96% for a super long time so I did a battery pull. Then I tried booting it into recovery and it does nothing but vibrate...recovery, hard reset, nothing works...looks like the end of the road for this phone.
Click to expand...
Click to collapse
If you truly bricked it the phone would not do anything - would not go to 96% or anything.
If Magldr did not finish you certainly would not have a recovery installed yet.
Task29 is over-rated and, in most cases, simply unnecessary. You are wearing out your NAND memory if you keep doing it.
OK, so having said all that.. Did you try a different USB cable, a different USB port, re-installing the Windows side of the software (ActiveSync?)
Look for MSKIP's guide to flashing the HD2 - it should get you past the MAGLDR install.
Er, I meant to say I think I've bricked it after I tried reflashing Magdlr. It does nothing but vibrate when I attempt to turn it on now.
wcstick said:
Er, I meant to say I think I've bricked it after I tried reflashing Magdlr. It does nothing but vibrate when I attempt to turn it on now.
Click to expand...
Click to collapse
You cannot even get to the tri-color bootloader??
You didn't overwrite HSPL somehow, did you?
Before you try anything else make sure your battery has a decent charge (at least 50%).
The last thing you want is to die in the middle of these steps.
If HSPL is (or should be) OK, disconnect the device from any external power source. Remove the battery and place it back after a short while. Remove the HD2's back cover and press (and hold) the volume_down key. Press in the red reset button under the back cover to the bottom left of the SIM (you will need a sharp object for this) and release the soft reset button but continue to hold the volume down key in until you are presented with the tri colour bootloader screen.
If you get to the boot loader, make sure you have HSPL in tact. You can use this mode, with the tri-color screen, to flash Magldr later.
If you made it this far try the following steps.
Make sure you are using the correct radio - this can create serious problems! YOU NEED A RADIO WHICH SUPPORTS 576 RAM (2.08.50 or later should be fine but the Radio NEEDS to be 2.**.50.**). I recommend the 2.15.50.14 radio
The Original MAGLDR thread by Cotulla is here if you need it. MAGLDR doesn't replace OSPL/HSPL. It runs in the chain after. So it's safe to install and remove it Once you are in the tri-color bootloader mode:
Synch Phone with PC in Windows Mobile!!! It has to be connected to activesync or WMDC via USB cable. As an alternative method to activesync you can restart your phone in Bootloader Mode, then connect the usb cable and wait until 'usb' appears in the bottom half of your phones screen
Browse to the folder you extracted your Magldr Package files to on your pc, right click on ROMUpdateUtility.exe and select Run as Administrator (Win7 or later)
Tick the box to confirm you are aware of the risks and select 'Next'
Tick the box to confirm you have followed the preperation steps and select 'Next'. The program will check the usb connection.
Select 'Update'
Verify the image you will flash (it should say 2.00.000.0) and Select 'Next'
Read the process list and Select 'Next'
Your phone will enter BootLoader Mode and the progress will (hopefully) goto 100%
Your phone will Reboot. You should now have MGLDR installed.
To Enter MAGLDR Menu Screen after installation, Long Hold the Power Button when resetting the phone and the menu will appear
If you make it this far I suggest you now run DAF.EX to repartition and update your recovery software. We can talk about this step next - let's ee if you can make it this far!
Frustrated with the whole process...What process?
I have spent WAY too many hours this weekend reading through threads here and elsewhere, with the goal of converting my T-Mobile WMo HD2 to Ice Cream Sandwich.
I have seen three for four different message thread that seem to contradict each other on what the process is.
Here is what I have done.
Changed to 2.08.HSPL. It was 2.10.000 .
Flased MAGLDR and it is working.
So I currently have a useless phone, although not bricked.
I had to use an old WinXP Laptop, since my Win8-64 Laptop would not see the phone.
Downloaded a ROM, NexusHD2-ICS-CM9-HWA_v2.9a .
Apparently there should be an Installer or a Daf included, but there is not.
I tried running Daf from the directory on the PC where the MAGLDR installer and other utilities are, like others have. Now I know that that will not work.
The current NAND Toolkit will not work on 32 bit windows. This is according to bzdemes here http://forum.xda-developers.com/showpost.php?p=19931919&postcount=501 . It certainly does not work on my Windows XP, "hd2toolkit.exe is not a valid win32 application" .
If my Windows 8 Laptop would see the phone, then I suppose that I could try it there, but once again, that does not work. I do not have access to any more Windows 7 PCs.
I have since seen messages indicating that I should have done Task29 before flashing MAGLDR. I have seen other messages indicating that it is not necessary. Of course, no usable toolkit, so here we go back into the loop of failure again...
I have wasted an entire weekend on this and have nothing to show for it, other than a non-usable phone.
I know that you guys put a lot of effort into playing with this stuff, but I really hope that someone here can provide a clear concise process for those of us who do not have play time.
FWIW, I am a noob at converting phones to Android, but I am very technical otherwise, with nearly thirty years in IT and Telcom / Data. Clearly this is not rocket science, but for those of us who do not have this specific experience, and generally have all of our time consumed by our non-Android jobs, this is a challenge.
Thanks
Dean
warpedspeed said:
Here is what I have done.
Changed to 2.08.HSPL. It was 2.10.000 .
Flased MAGLDR and it is working.
Click to expand...
Click to collapse
Excellent start! Before long you shall be looking back at this, smiling.
The next question you have to answer is if you wish to install all to NAND or place your apps and data on an SD Card. If you have an EU HD2 the SD card method is strongly recommended. I have the larger (1 GB) US version but prefer to use the SD Card method for a number of reasons (we can cover those another time if you wish).
warpedspeed said:
I had to use an old WinXP Laptop, since my Win8-64 Laptop would not see the phone. Downloaded a ROM, NexusHD2-ICS-CM9-HWA_v2.9a .
The current NAND Toolkit will not work on 32 bit windows. This is according to bzdemes here http://forum.xda-developers.com/showpost.php?p=19931919&postcount=501 . It certainly does not work on my Windows XP, "hd2toolkit.exe is not a valid win32 application" .
Click to expand...
Click to collapse
I have not used the Toolkit myself but one would think it would run OK on XP..
Having said that, try this - should be relatively quick and painless (I hope):
Download dafexe_399.zip - 5.17 MB to your PC and unzip it into an empty folder of your choice.
If you wish to use install option #2 (DataOnExt, placing only your boot, recovery and system partition on the device itself (NAND) use the setup as is. See notes on partitioning your SD Card before attempting to install the ROM! If you wish to install everything to NAND you must modify the file called FLASH.CFG which you shall find in the folder you extracted the zip file to - reduce the size of the system partition (the fourth line in the cfg file) to something like:
Code:
system ya 200M
I suggest setting it to 200M (200 MB) to start but you may have to redo this and make it larger if your device has bad blocks. A large system partition will, in turn, make for a smaller data partition - as a result you may be limited on the number of apps and data you can have on the device. This is why I personally prefer install option 2, placing the data partition on an SD card.
Once ready, boot your device to MAGLDR
Select USB Flasher from the MAGLDR menu (you can replace steps 3 & 4 with entering the tri color boot loader, if you wish)
Connect your device to the PC via USB
Make sure you are in the folder you created in step 1 and run DAF.EXE on your PC. This will partition your device according to the specifications in FLASH.CFG and also install ClockworkMod Recovery v5.x into the recovery partition.
If you decided on install option 2 - DataOnEXT - make sure your SD card is correctly partitioned before going on from here! You must have a FAT32 partition and an EXT4 partition (in that order), both set as PRIMARY. The EXT4 partition should be at least 1 GB, you can make it bigger if you have a larger card. If you need more info on partitioning and setting up the card please read post # 3 in this thread.
Copy the ROM of your choice to the FAT32 partition of your SD card.
Reboot your device while holding the END key to enter the MAGLDR menu.
Select menu option # 8 - AD Recovery. This will load Clockworkmod Recovery you flashed in step 6.
Select install from ZIP menu option and locate the ROM zip file you placed on the SD card earlier.
After the device reboots you should be running the new ROM. Now, you may still experience some problems - such as bootloops or getting stuck at the logo screen if you made the system partition too small for your device or if you have too many bad blocks on your device and you selected install option # 1. In this case you will have to return to step 2 and increase the system partition size and do it all again.
Does any of this help thus far?
Yesterday I had a chance at work to try another Windows XP PC that is pretty much just used for testing. It has a fairly fresh image on it. I had the same Win32 error on it with the NAND toolkit.
I also was able to get my hands on a Win7 32 bit PC, with the same result.
Then I was able to “commandeer” a PC that was going to be re-imaged anyway. I put a Win 7 64 image on it, and sure enough the toolkit worked.
So it appears that the NAND Toolkit works on Win 7 64, and possibly Win 8 64, but support for 32 bit Windows appears is over, unless the program gets fixed.
The problems that I was having with synching the phone on my Win 8 64 PC may have been due to using a USB3 port. Last night I was able to see the phone on that PC with a USB2 port. I should have tried that this last weekend.
So I ended up using the Toolkit yesterday, before I saw your reply. I did look through the partitioning guide that you referenced. I opted not to go with the Data on EXT option. It is a 1Gb T-Mobile HD2, so I am in good shape there. I did not want the operation of the phone to be dependent on a relatively slow SD card. I will just keep optional data there, such as music, pictures, and documents. I will keep anything important, such as programs and notes that I use for reference in the main memory. I do not have all that many extra programs or data.
So I am up with the ICS-CM9-HWA_v2.9a build and it is pretty good. So far I like it. Previously I was doing a dual boot, using Haret and a Gingerbread build, basically as a test, and while I was waiting for some Android apps to mature, that initially were not a good replacement for some specialized WinMo apps that I had. I finally have all of the functionality that I need on the Android platform.
For me, the biggest challenge in this was the variety of documented procedures that are out of synch, and mostly out of date. For instance Mr Skip’s guide is well written, but out of date to the point that it sent me down the wrong road. I am not picking on Mr Skip, in fact his guide was the best written of the bunch, so that is why I mention it.
If I am the last guy on this particular planet to make the switch on an HD2, then it is probably is not worth updating the docs out there. However there might still be a few holdouts in the wings yet.
If I can get my wife to stop using my T-mobile upgrade credits, then maybe I can get a newer hardware platform someday! Although I am very impressed with the longevity and durability of the HD2. That is a rare thing anymore.
Thanks for the help.
Glad you got it to work. I only have a couple of brief comments to add.
warpedspeed said:
I opted not to go with the Data on EXT option. It is a 1Gb T-Mobile HD2, so I am in good shape there. I did not want the operation of the phone to be dependent on a relatively slow SD card.
Click to expand...
Click to collapse
Going with option 1 is fine. You may or may not encounter limitations and you can always change later if need be. However, it should be noted that the HD2 NAND operates at roughly the same speed as a Class 4 card, hence you could not slow it much by using a card.
warpedspeed said:
For me, the biggest challenge in this was the variety of documented procedures that are out of synch, and mostly out of date. For instance Mr Skip’s guide is well written, but out of date to the point that it sent me down the wrong road. I am not picking on Mr Skip, in fact his guide was the best written of the bunch, so that is why I mention it.
Click to expand...
Click to collapse
Mark's guides are indeed excellent and as you noted, somewhat dated since they were written early in the HD2 / Android days. A number of things have changed and I think Mark has moved on to Samsung or Nexus devices since that time. For good or evil his guides survived the test of time.
---
Appreciation is a wonderful thing. It makes what is excellent in others belong to us as well.