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.
Related
I followed this guide:
w w w.jayceooi.com/2011/01/07/how-to-install-nand-android-on-htc-hd2-with-clockworkmod-recovery-video
and now i dont have any OS on my htc, it just sais
booting android from nand
and it keeps getting stuck at Go Go GO!!
help me!
hallamartin said:
I followed this guide:
w w w.jayceooi.com/2011/01/07/how-to-install-nand-android-on-htc-hd2-with-clockworkmod-recovery-video
and now i dont have any OS on my htc, it just sais
booting android from nand
and it keeps getting stuck at Go Go GO!!
help me!
Click to expand...
Click to collapse
I would get another ROM and reflash it, whether it's a ZIP ROM (CWM) or a NAND ROM via DFT.
it would be awsome if you could send me a link to a good rom? android or windows? realy need this to work
hallamartin said:
it would be awsome if you could send me a link to a good rom? android or windows? realy need this to work
Click to expand...
Click to collapse
Well there's lots of good roms out there... they are all very easy to flash back and forth from. I hate to say which one is "better" than another as that is purely subjective and everyone has a differing opinion. However, it seems a lot of people really like Sergios, MDJ's and CMYXLGO's ROMs. As a start you may want to check out one of those... Here is a link to the main Android NAND forum.
I have
•HSPL3 ~ SPL-2.08.HSPL
•Radio that support 576 RAM
•DFT MAGLDR Bootloader
•ClockworkMod Recovery
Installed.
Can you send a link to a rom that supports clockwork? i dont realy care witch one just one that works. am e newbie in this just got the phone yesterday, and now i kinda afraid i cant fix it :/ :/
hallamartin said:
I have
•HSPL3 ~ SPL-2.08.HSPL
•Radio that support 576 RAM
•DFT MAGLDR Bootloader
•ClockworkMod Recovery
Installed.
Can you send a link to a rom that supports clockwork? i dont realy care witch one just one that works. am e newbie in this just got the phone yesterday, and now i kinda afraid i cant fix it :/ :/
Click to expand...
Click to collapse
If it turns on and will boot to the bootloader, it's fixable So don't worry that much! Try out Sergio's ROM. It supports CWM. If you do use that one be sure to back up your SD card as you have to repartition it.
The steps to install it are:
Code:
HD2 COREDROID Desire HD V1
1. Extract downloaded zip to a folder of your choice
2. Copy contents of copy_to_sd_root (initrd.gz and zImage) to the root of your sd card
3. Boot into magldr and select USB Flasher option while phone is connected to PC
4. Run DAF.exe included in the zip and follow onscreen instructions.
5. After complete devise will reboot in magldr chose "Boot AD SD" option
6. Device will boot into Clockwork Recovery
7. Select advanced
8. Select Partition SD card (remember too backup all valuable data you have on SD Card)
9. Selet (minimum 512M)(maximum 1024M) Chose what fits best for you Recomended size 1024M
10.Select Swap 0M
11.Wait for the process too finish (do not restart device stay in ClockWork recovery)
12.Connect the Device into USB
13.select mounts and storage
14.select mount USB storage
15.Copy contents of copy_to_sd_root (initrd.gz, zImage) to the root of your sd card
16.Copy CoreDroid_HD_HD2_v*.zip to the root of your sd card
17.Press back key after finish
18.Press back key once more
19.Select install zip from sdcard
20.Select choose zip from sdcard
21.Select CoreDroid_HD_HD2_v* file and then confirm
22.Wait for it too finish
23.After flash options pop up again Press back Key
24.select reboot system now
25.Let it boot wait about +-10Min Enjoy
I haven't really examined the guide you followed that much, but make sure you have installed a recent version of Magldr (i.e. the one you can download in the official Magldr thread in the WinMo subforum, version 1.11 to be precise). The first version(s) have been notorious for the Gogogo! bug persistently affecting some users.
Just a fyi, ignore this if you already have this v1.11
I got the aMagldr V1.11
The rom you sendt me doesnt work, it stopps here:
Run DAF.exe included in the zip and follow onscreen instructions.
i allredy installed a Daf.exe can that be the problem?
hallamartin said:
i allredy installed a Daf.exe can that be the problem?
Click to expand...
Click to collapse
No, because it's not really an installer, but a flasher. I'm not really an expert on the CWM issues, but it seems to me like formatting your SD card(do a full format, not the quick one) might help you, since it's quite probably your SD card being the *****.
It may not help you, but if you've got a few minutes I'd say give it a shot. Don't forget to backup important SD (NAND isn't affected) first of course!
Oh, and there's also this small chance that your CWM download is corrupt. Not sure if that would give the gogogo error though.
Sorry for being a complete newb, but how do i do the hard format?
but do i need the DAF.exe to install the rom?
You'd have to format in Windows (which I assume is the OS you're running), which now that I think of it may be a bit of a problem. I don't think you can mount your SD card with Magldr, which means that you'd have to use an external card reader. If you don't have that, you'd have to reflash WinMo to format, but since that's quite some more work for something that I can't even guarantee to be a solution you might wanna hold on to other suggestions.
DAF.exe is the tool which flashes CWM to your phone. Some other tools and/or ROMS use the same name for their flasher though.
after this one :
8. Select Partition SD card (remember too backup all valuable data you have on SD Card)
9. Selet (minimum 512M)(maximum 1024M) Chose what fits best for you Recomended size 1024M
10.Select Swap 0M
i can't do **** i cant open the device in windows. is there no way i can just system recover the whole device? or do i have to rom it?..
realy need this to be working, prefer android but windows is okey
StephanV said:
You'd have to format in Windows (which I assume is the OS you're running), which now that I think of it may be a bit of a problem. I don't think you can mount your SD card with Magldr, which means that you'd have to use an external card reader. If you don't have that, you'd have to reflash WinMo to format, but since that's quite some more work for something that I can't even guarantee to be a solution you might wanna hold on to other suggestions.
Click to expand...
Click to collapse
dosn't seem like there is allot of things i can do? i just hope i didnt brick it...
i cant send it to repair like this?
hallamartin said:
dosn't seem like there is allot of things i can do? i just hope i didnt brick it...
i cant send it to repair like this?
Click to expand...
Click to collapse
It sure is no brick, as long as you can boot into bootloader (turn on phone while keeping volume down pressed) there's no problem at all. No need to return it either.
If you feel really desperate try the WinMo thing, you've got nothing to lose except for about 30 minutes of your time.
winmo thing? is there any guide?
if i download a format program i can format the sd card..
1. Flash WinMo, this should be no problem in bootloader
2. I think it's possible to format your SD card within WinMo. I've never used WinMo actually so I can't give instructions on that.
If you can't find it or if it isn't possible, mount your SD card so you can see it in Windows. Backup data if necessary. Then right click on it (in Windows), and choose format, then disable quick format which should be selected by default. After the format you should have a clean SD card.
4. Flash Magldr again, following instructions in the official Magldr thread. Download a new copy off xda, to eliminate the possibity of just having had a corrupt download.
6. Flash CWM, following instructions in the official CWM thread.
7. Flash ROM.
Edit: I used WinMo where I meant the mobile OS, and Windows where I meant the pc OS.
I did format the SD card, nothing new just that CWM disapeard.
Now its loading with aMagldr v1.11
And i Have Spl-2.08. Hspl 8g Xe
Can anyone send me a link to a good Win 6.5 rom and anykind of guide?
When I try to turn my phone on, it will not get passed the ROM loading screen (Energy blue logo). This is because the internal memory is full.
I really need to get into the file system to delete a file (and fix the problem) or copy certain stuff out - it has pictures of my fiance on to say the least, and I really want them.
But, as Windows won't boot I can't do this in the traditional way. Obviously I can still get into bootloader - so is there a way I can access the file system? A bit of software I can run on my laptop that can somehow access the file system through bootloader mode? All I need to do is identify a c.1mb file and delete it...
The background to all this is the phone was displaying messages about 'memory nearly full' - but it had done this before and just stopped, so I left it again. Except, at some point signal reception dropped and stayed at 0. So I rebooted, and got stuck at the loading screen - which is where we've been for the last few days now.
I really hope someone can help. If you can, I'll buy you a few beers.
Thanks,
David
Phone was running WM6.5 with HSPL (3 I'm fairly sure)
How in the hell did you manage to fill your internal memory up, why not just use a SD card for storage?
If you can get into bootloader, cant you simply connect it via activesync/wmdm and then just copy what you need and delete?
I think I took too many photos! Though I'm not exactly sure tbh... Some bug in the ROM kept changing the save dir from SD card to internal, but I did keep an eye on the space, perhaps just a few too many photos in one night...
Anyway ActiveSync isn't working (for me at least) in bootloader mode - don't I need to have Windows Mobile loaded?
Should activesync work in bootloader mode?
TheATHEiST said:
If you can get into bootloader, cant you simply connect it via activesync/wmdm and then just copy what you need and delete?
Click to expand...
Click to collapse
doesnt work. you cant access the live file system from anywhere except within running wm.
You can dump off the rom partition into .raw files, but when you rebuilt it (in a ktchen) you would still only end up with the original rom as it was out of the box, no user data.
@OP, you could possibly go into bootloader, confirm 2.08.hspl, flash magldr, and then boot from an sd android, though i suspect you still wouldn't see the winmo files. (I assume there are now android builds that can be booted to and run from sd without the need for haret/winmo? i'm a nand man meself so unsure. )
It's what i'd try if it really was that critical, otherwise I'd weep for a little while, kick myself and write 'backup' post-its all over my office, then hard reset and move on.
Thanks for the advice - I will definitely try your suggestion before 'moving on', losing a whole bunch of contacts will also be a real pain.
Do you know of any threads/links explaining magldr and how it will help?
Is there no other way to access any part of the internal memory and just delete 1 file?
I found out that magldr has 2 commands:
"Boot WPH" - boots WPH from nand. WPH must be flashed before. NOT AVAILABLE now.
"USB Flasher" - use this item to flash Android or WPH.
Problem is the first one isn't yet available - maybe he would give me a beta though.
I assume WPH is Windows Phone. So if I had a version with 'Boot WPH' command working,
a) Could I flash Windows Phone into the nand (whatever that is)?
b) Once in booted & loaded WP7, could I view the WM6.5 files on the internal RAM?
I think I agree it is unlikely the files would be viewable within Android - surely it must use a different file system. Does WM use FAT32 for the internal memory?
Thanks
Bear in mind WP7 and winmo are two very different OSes.
WP7 has been out btw.
Once you flash the device, with MAGLDR, android or WP7, the internal storage is wiped so it makes no sense to flash it if you still want what is in it.
davenash said:
I found out that magldr has 2 commands:
"Boot WPH" - boots WPH from nand. WPH must be flashed before. NOT AVAILABLE now.
"USB Flasher" - use this item to flash Android or WPH.
Problem is the first one isn't yet available - maybe he would give me a beta though.
I assume WPH is Windows Phone. So if I had a version with 'Boot WPH' command working,
a) Could I flash Windows Phone into the nand (whatever that is)?
b) Once in booted & loaded WP7, could I view the WM6.5 files on the internal RAM?
Click to expand...
Click to collapse
any type of flashing (nandroid, wp7 or wm) will destroy whats on there already, thus defeating the object.
There are more than two options in magldr, one of which is 'boot sd ad' for boot sd card android.
I think I agree it is unlikely the files would be viewable within Android - surely it must use a different file system. Does WM use FAT32 for the internal memory?
Click to expand...
Click to collapse
its probably not an issue of the file system type, android (linux) can access fat partitions no problem. Its probably more to do with whether the sd builds can mount the internal rom or not.
Im no linux head at all, still fumbling in the dark though, so i could be wrong.
Hi
I have tried to install android on my phone and after a few attempts I finally got to the step where to install Android which works fine.
But after first boot it is written that it may take upto 20 minutes.... I have tried with different kernels with same results.... it simply stops after GO GO GO then it comes to the android screen and nothing happens... I have tried to let it be for 5 hours... still no reaction!
What I do is to copy the .zip file to my SD card and go to to the boot menu and coose "Install from zip file on SD card".
Any good ideas how to solve it?
PeterSvendsen said:
Hi
I have tried to install android on my phone and after a few attempts I finally got to the step where to install Android which works fine.
But after first boot it is written that it may take upto 20 minutes.... I have tried with different kernels with same results.... it simply stops after GO GO GO then it comes to the android screen and nothing happens... I have tried to let it be for 5 hours... still no reaction!
What I do is to copy the .zip file to my SD card and go to to the boot menu and coose "Install from zip file on SD card".
Any good ideas how to solve it?
Click to expand...
Click to collapse
You need to provide more details for folks around here to reply. Ie:
1. Which model are you using - LEO512 or LEO1024
2. Which MAGLDR was flashed. Version 1.13? Because earlier version had the freeze at GOGOGO! problem.
3. Which android build did you use (DAF build type or CWR type?)
Only then we can even start to suggest what to do to help you
Wait....Are you using builds that requires SDCards to be partitioned? If yes, did you partition as required?
PeterSvendsen said:
Hi
I have tried to install android on my phone and after a few attempts I finally got to the step where to install Android which works fine.
But after first boot it is written that it may take upto 20 minutes.... I have tried with different kernels with same results.... it simply stops after GO GO GO then it comes to the android screen and nothing happens... I have tried to let it be for 5 hours... still no reaction!
What I do is to copy the .zip file to my SD card and go to to the boot menu and coose "Install from zip file on SD card".
Any good ideas how to solve it?
Click to expand...
Click to collapse
Mate,
I experience that too. I think not all ROM can be successfully boot.
My suggestions is either try reflashing or find another ROM that works for your HD2.
Cheers
silverwind said:
Mate,
I experience that too. I think not all ROM can be successfully boot.
My suggestions is either try reflashing or find another ROM that works for your HD2.
Cheers
Click to expand...
Click to collapse
Thats odd.... I only know that the experience may vary across different units (ie: wake-up lag, power drain, etc). Never have i heard that not all builds can be successfully booted. I still think the problems has to do with settings (i.e.: config.txt, NAND partition layout, SD Card partition size and formats etc).
If you have a prob with the builds, please specify clearly which version and your configurations. Only then folks here can advice accordingly....
can't hurt...
task 29, WM6.5 rom installation, magdlr installation then flash the rom again
make shure you created ext partition on SD if required for making work the ROM (check its trhead)....
Do a fresh installation(Format SD->Task 29->Flash Radio->Flash MAGLDR->Flash CWM->Flash ROM from zip using AD recovery option in MAGLDR.. Maybe you are using an incompatible radio?
if i have this problem, i flash windows back (LEOIMG.nbh is always on my sdcard).
this will help me.
after one "no-function"-flash dont try an other flash by the same config like the config before.
I think that problem is in kernel . you trying kernel for new desire, use for N1.
tidus18 said:
You need to provide more details for folks around here to reply. Ie:
1. Which model are you using - LEO512 or LEO1024
2. Which MAGLDR was flashed. Version 1.13? Because earlier version had the freeze at GOGOGO! problem.
3. Which android build did you use (DAF build type or CWR type?)
Only then we can even start to suggest what to do to help you
Wait....Are you using builds that requires SDCards to be partitioned? If yes, did you partition as required?
Click to expand...
Click to collapse
Hi
I have no idea if it is a 1024 or 512! How do I find out?
I use MAGLDR 1.13
I have tried to install
RAFDROID HD 4.0.2|Fastest Full DesHD|DATA2EXT|[Rafpigna 1.8 OC]
[LEO512][LEO1024]CMYLXGOs Stock Desire HD(2)[RUU1.84][RAFPIGNA 1.9OC]
and more
All with same result
I have tried to do the sd partition... .actually with 2 diffent cards but I have never been able to have 2 partitions.... I alway ends up with 1 partition on 2Gb
---
Do a fresh installation(Format SD->Task 29->Flash Radio->Flash MAGLDR->Flash CWM->Flash ROM from zip using AD recovery option in MAGLDR.. Maybe you are using an incompatible radio?
---
I tried that as well with same results
Do you recomment a specific android?
I'm totally new in this and only want a android on my phone )
tidus18 said:
Thats odd.... I only know that the experience may vary across different units (ie: wake-up lag, power drain, etc). Never have i heard that not all builds can be successfully booted. I still think the problems has to do with settings (i.e.: config.txt, NAND partition layout, SD Card partition size and formats etc).
If you have a prob with the builds, please specify clearly which version and your configurations. Only then folks here can advice accordingly....
Click to expand...
Click to collapse
I m trying to say that so many ROMs are available here.
Dont spend your time to long only to one ROM
Unless it is your favorite ROM (Chef)
Cheers...
i guess you did a ROM flash through clockworkmod? if so, did you flash the correct partition sizes (sense roms need often about 400mb /system partition). If not you need to find the 400mb clockwork recovery in this forum.
If you flashed a rom via DAF, please disregard this.
also please post in the correct forum (Q and A would be correct for this topic i believe)
joshman99 said:
i guess you did a ROM flash through clockworkmod? if so, did you flash the correct partition sizes (sense roms need often about 400mb /system partition). If not you need to find the 400mb clockwork recovery in this forum.
If you flashed a rom via DAF, please disregard this.
also please post in the correct forum (Q and A would be correct for this topic i believe)
Click to expand...
Click to collapse
Hi
I have tried to do it by DAF (reports size to big?!) and clockworkmod I have also tried with
Sorry about the trong forum, you're absolutly correct...
Update
I have now bought a new sd micro card to make a correct partition.. but I experience exactly the same... error I cant..
With program do you recomment?
PeterSvendsen said:
Hi
I have tried to do it by DAF (reports size to big?!) and clockworkmod I have also tried with
Sorry about the trong forum, you're absolutly correct...
Update
I have now bought a new sd micro card to make a correct partition.. but I experience exactly the same... error I cant..
With program do you recomment?
Click to expand...
Click to collapse
check this thread http://forum.xda-developers.com/showthread.php?t=981811 task 29 is reccommended do u have red and green call buttons on ur hd 2 or rather t mobile on top of ur screen
than we can help u accordingly
remember a wrong cwm partition might be responsible for bootloop
go for hyperdroidv10 rom it s amazing and use 135 or 150 cwm partition
shhbz said:
check this thread http://forum.xda-developers.com/showthread.php?t=981811 task 29 is reccommended do u have red and green call buttons on ur hd 2 or rather t mobile on top of ur screen
than we can help u accordingly
remember a wrong cwm partition might be responsible for bootloop
go for hyperdroidv10 rom it s amazing and use 135 or 150 cwm partition
Click to expand...
Click to collapse
use panasnic sd fromatter and frmat
http://forum.xda-developers.com/showthread.php?t=905089
or use mini partition tool
cwm is the best method to install android rom
sorry wrong quote
shhbz said:
check this thread http://forum.xda-developers.com/showthread.php?t=981811 task 29 is reccommended do u have red and green call buttons on ur hd 2 or rather t mobile on top of ur screen
than we can help u accordingly
remember a wrong cwm partition might be responsible for bootloop
go for hyperdroidv10 rom it s amazing and use 135 or 150 cwm partition
Click to expand...
Click to collapse
I have done a task29 several times already.
---
.... or rather t mobile on top of ur screen
---
I'm not sure what you ask me about. But no on my phone my call buttons is black and gray
By using panasonic formatter I only format... but the card is on 8Gb so guess I need to make a partition.
Mini partition tool doesnt work correct it report errors as soon as I ftry to format etx3
If your phone has T-mobile on top and buttons are colored red & grees - its LEO1024.
If all grey without any logo on its case/housing - then its LEO512/EURO model.
difference is the NAND size. LEO1024 has 1GB and LEO512 has 512MB.
Peter,
I'll quickly write the outline here, hopefully it helps. But detailed guide on each subject has been posted numerous times here. Please look for them.
Outline to get RAFDROID up and running (Based on your post, im assuming yours is LEO512)
1. Flash MAGLDR 1.13 (this involves entering tricolor screen and flashing like good'ol WM6.5)
2. From MAGLDR, choose USB Flasher mode (Option 4 i think...) and flash Clockwork Mod Recovery with 400MB layout. (this is important, wrong layout will cause bootloop and androd will not boot)
3. Assuming you have 2GB microSD card - Use a memcard reader and connect it to your PC. Dont use mass-storage option from MAGLDR. Launch Minitool Partition and create 1GB FAT32 Primary partiton followed by 1GB EXT3 with 4096 block size primary partition. This process is not as complicated as it may sound
4. Put the downloaded RAFDROID CWR zip file into the FAT32 partition. (When the partitioning is complete, windows will only see 1GB in your microSD. The 2nd 1GB EXT3 partition will only be available to android, so dont worry about it)
5.Once done, pop you microsd in your LEO, and choose Recovery option from menu. Once you enter the recovery menu, choose Install from ZIP file and choose the RAFDROID zip file that you have just put in.
6. Wait, and choose reboot. Whole process should be about 20 min.
7. Enjoy your android
Guys, please add anything if i missed out any steps
PeterSvendsen said:
I have done a task29 several times already.
---
.... or rather t mobile on top of ur screen
---
I'm not sure what you ask me about. But no on my phone my call buttons is black and gray
By using panasonic formatter I only format... but the card is on 8Gb so guess I need to make a partition.
Mini partition tool doesnt work correct it report errors as soon as I ftry to format etx3
Click to expand...
Click to collapse
ok if u have performed task 29
install stock rom having spl 2.08 or less
install hspl 2.08
install malgdr 1.13
install cwm depending on the rom u want to use (it must be mention in the thread which one to go for)
transfer the zip file from pc to mmc card by mounting the card orelse use card reader to transfer the files
go into malgdr option and install from zip
note:create 1024 ext3 or ext4 leaving the rest in fat format
http://forum.xda-developers.com/showthread.php?t=905089 (the best way to parttition)
or http://forum.xda-developers.com/showthread.php?t=910000
or http://forum.xda-developers.com/showthread.php?t=905145
or http://www.youtube.com/watch?v=9d7qhBpCJQc&feature=player_embedded
this is the best method to format your card in order of your requirement
do these steps of formating before instaling cwm or before doing any other steps
and 1 more thing u have a 512 leo euro hd 2 so read these guides here
http://forum.xda-developers.com/showthread.php?t=609477
u wil get all information for stock rom /correct radio and every stuff in the above thread
hope your probelem gets solved this time if u need any more help let me know
remeber if you have hspl 3.03 u cant install android so use stock rom with spl 2.08 and install hspl 2.08 later
i wouls suggest to use hyperdroid http://forum.xda-developers.com/showthread.php?t=918899 as its the best after MDJ built
great battery,speed,smooth,etc no errors but if you want to try froyo built than you are checking the right thread
I am a flash addict and I am sure most of you are. I can't stand a smooth running phone that works flawlessly. If it does, then I must do something to it to destroy it's stability. Well, it's not easy to brick HD2 unless you are a real dummy or like to live very dangerously lolll....even that can be fixed...but it was more difficult for me to find a way to unlock my SD card back to normal after WP7 installation. Some suggested in this forum that some of the cameras and nokia phones will do the trick...I was frustrated when I screwed up my 16GB sd card and could not find that camera or phone...as it won't make sense to buy them to restore a $15 card.....so I gave up on that card until today....I decided to play with WP mango again with the same sd card...resulted in locking it again...my challenge was to succeed unlocking it this time.....followed the same old procedures with no success...I tried and exhausted all options again!!! Then I decided to pop my sd card on my second hd2 which is running android with 4ext recovery installed and try to format it or something....and it worked!!!!! Just repartitioned the card and reformatted and it automatically unlocked it during the process....No step by step by step by step installation of software or reading pages or running codes.....nothing else was needed!
Life is meant to be simple after all
Anyone who is having the same issue with sd card after Windows Phone 7 or 7.5 installation just repartition and reformat your card via 4ext recovery and it will work...nothing else needed :} Good Luck!
All credits to 4ext recovery developer....and the developer must be proud to find this info.
Here is Step by Step process-
If you are running Android NAND and have 4ext recovery installed....then
1. Turn off your device
2. Take out the SD card(if there is any in it) and insert the one you want to unlock/fix
3. Turn on your device HOLD red power button until you get to aMAGLDR v1.13 menu
4. Go to option 8. AD Recovery hit green button for it load
5. Now you should have 4ext recovery(mine is version 2.2.7) menu
6. Scroll down to Advanced
7. Choose> Partition SD Card
8. Choose whatever size you want to first one, second one to be and the rest goes to fat. If you want all in one partition, just choose '0' for the first two and '0' as swap.
9. Follow on screen instruction you may see.....and it will delete all previous partition and create new one
8. NOW go back to main 4ext recovery menu....and format you SD card...AND there it it! Your SD card it back to normal...enjoy
NOTE: I use 4ext recovery that you flash via usb flasher thru magldr NOT the one from market. You can find the flashable one in here. I will try to find the link and post it. BUT it is not and will not be my work!
Here is a link I found....but this NOT what I used. I used this recovery that I found in one ROM link I have tried in the past which I can't think of but I have been using the same recovery since then because it is the BEST with the option of EXT4 file system....the one I have you can directly flash it like any other recovery you normally would to partition NAND to flash NAND Android roms. Nand partition size has nothing to do with sd recovery steps.
http://forum.xda-developers.com/showthread.php?t=1297587
Since I did not use the above option....I won't be much of help. But from my understanding you can use this option to update your current recovery to 4ext recovery and then follow my steps. The app from the market would require to update your current recovery as well to be able to use my method to restore your SD card after WP7 installation Good Luck! Although it is a very simple process to undertake, I am not responsible if you damage your phone or the sd card even more!!!
If someone who has the usb flashable version of 4ext recovery(for HD2) could attach it or provide link that would be great for everyone. Mine is installed in the phone and I don't seem to have that file....too many files I download everyday and must delete them all at some point
If you've found a solution to a problem...please go ahead and include a link or something so people can find the tool you used without having to spend time searching through threads and forums, instead of just writing that you found a solution.
please provide more detail. I downloaded free app from Android "Play Store" market but cannot see where to partition card.
Please provide more detail. i.e. is it free or paid version.
which menu to use etc
I will post detailed step by step soon
SEE Post#1
Sent from my HTC HD2 using xda premium
Whatdoyaknow said:
please provide more detail. I downloaded free app from Android "Play Store" market but cannot see where to partition card.
Please provide more detail. i.e. is it free or paid version.
which menu to use etc
Click to expand...
Click to collapse
I did not install that way(read post) but I think you have to update your recovery to 4ext after you install that app. And after that you can easily try my steps. It will work
NYSEAN1 said:
I did not install that way(read post) but I think you have to update your recovery to 4ext after you install that app. And after that you can easily try my steps. It will work
Click to expand...
Click to collapse
Ok thanks for all your efforts.
It seems to m that you can install 4ext from "android market", load it then choose the first menu option "Online install..." and download the additional 4ext recovery file from there.
But I'm still having problems getting it to load at boot up
Update: No joy. I have Clockworkmod recovery on mine. Installed 4ext but overwrote boot stuff and would not load 4ex. So I need help how to replace Clockworkmod with 4ext or whatever I need to do (I have more expertise in WP7 than Android)
For the HD2 the 4EXT Recovery was originally ported by Dansta34 and i have also seen a variant on Coredroid which looks like it's the same. The Sensation 4EXT from Madmaxx will not work on the HD2.
The HD2 4EXT Recovery can be taken from either Dan's thread (TBD ROM) or from Coredroid, whereas i recommend taking it from Dan as he also took the workload of porting it to the HD2 as far as i know. So he should deserve the Download stats and the credits
I've also got it mirrored in my Signature. Feel free to take it from there. I've got both the CoreDroid and the TBD variant, yet the only difference i can see is the background image. Not sure though.
Once you downloaded that Recovery you can put your HD2 into USB Flasher Mode in Magloader and then flash the Recovery via the included DAF.exe, then proceed with the Steps the OP recommends. Notice: if you flash it for the sole purpose of unlocking your SD-Card, setting the partition sizes in flash.cfg is irrelevant. Just leave them as they are since the Recovery and the partitions will be deleted and set up different from the WP7 flash afterwards.
Since the Threadstarter has contacted me for a link to the files (?? Why is that) i'd like to point out that this Recovery is not a hidden gem but a normal Download for at least two Android ROM's and can be taken in exchange for a THANKS.
I recommened NYSEAN1 to reproduce and verify his findings, as i find it rather strange that noone else has noticed this "function" of the Recovery before. There is quite a large number of people who mess with both android and wp7 and noone has ever noticed that the HD2 can, by means of the 4EXT Recovery, unlock DRM encrypted SD-Cards? Very odd.
Well, if it does actually work, the better it is for us. So, we have to say THANKS to NYSEAN1 for finding out this wonderful trick that saves us from finding an old Nokia phone.
I'd still recommend to post this Info on the SD-Card unlocking threads as this seems the most independent and hassle-free solution to me. But please only after this procedure has been verified by more than just one person to be working as expected.
Thanks
Thank you very much.
I have sloved it.
Sneakyghost said:
The HD2 4EXT Recovery can be taken from either Dan's thread (TBD ROM) or from Coredroid, whereas i recommend taking it from Dan as he also took the workload of porting it to the HD2 as far as i know. So he should deserve the Download stats and the credits.
Click to expand...
Click to collapse
Many thanks Sneakyghost, this will save others the problems that I have had.
Would you mind providing a link Dan's thread or advise as to which to download from your great site – it seems to have a few Xt4 files. Not being an expert, I’m not sure which to use.
Sneakyghost said:
For the HD2 the 4EXT Recovery was originally ported by Dansta34 and i have also seen a variant on Coredroid which looks like it's the same. The Sensation 4EXT from Madmaxx will not work on the HD2.
The HD2 4EXT Recovery can be taken from either Dan's thread (TBD ROM) or from Coredroid, whereas i recommend taking it from Dan as he also took the workload of porting it to the HD2 as far as i know. So he should deserve the Download stats and the credits
I've also got it mirrored in my Signature. Feel free to take it from there. I've got both the CoreDroid and the TBD variant, yet the only difference i can see is the background image. Not sure though.
Once you downloaded that Recovery you can put your HD2 into USB Flasher Mode in Magloader and then flash the Recovery via the included DAF.exe, then proceed with the Steps the OP recommends. Notice: if you flash it for the sole purpose of unlocking your SD-Card, setting the partition sizes in flash.cfg is irrelevant. Just leave them as they are since the Recovery and the partitions will be deleted and set up different from the WP7 flash afterwards.
Since the Threadstarter has contacted me for a link to the files (?? Why is that) i'd like to point out that this Recovery is not a hidden gem but a normal Download for at least two Android ROM's and can be taken in exchange for a THANKS.
I recommened NYSEAN1 to reproduce and verify his findings, as i find it rather strange that noone else has noticed this "function" of the Recovery before. There is quite a large number of people who mess with both android and wp7 and noone has ever noticed that the HD2 can, by means of the 4EXT Recovery, unlock DRM encrypted SD-Cards? Very odd.
Well, if it does actually work, the better it is for us. So, we have to say THANKS to NYSEAN1 for finding out this wonderful trick that saves us from finding an old Nokia phone.
I'd still recommend to post this Info on the SD-Card unlocking threads as this seems the most independent and hassle-free solution to me. But please only after this procedure has been verified by more than just one person to be working as expected.
Click to expand...
Click to collapse
Thanks Sneaky.....I was not sure where I found it and who created it. But I remember seeing your name around it....thanks again! I hope this really works for others.
Whatdoyaknow said:
Many thanks Sneakyghost, this will save others the problems that I have had.
Would you mind providing a link Dan's thread or advise as to which to download from your great site – it seems to have a few Xt4 files. Not being an expert, I’m not sure which to use.
Click to expand...
Click to collapse
I used TMobile version....but it doesn't matter anyway..nand partition or size does not really have anything to do with it...any size is fine...just pick any 4ext recovery and flash it through usb flasher...all we are looking for is the 4ext recovery menu to re-partition and format the card.
Please report back it worked for you...very eager to know
linxuehui said:
Thank you very much.
I have sloved it.
Click to expand...
Click to collapse
Did it work for you????? Please report back!
NYSEAN1 said:
I used TMobile version....but it doesn't matter anyway..nand partition or size does not really have anything to do with it...any size is fine...just pick any 4ext recovery and flash it through usb flasher...all we are looking for is the 4ext recovery menu to re-partition and format the card.
Please report back it worked for you...very eager to know
Click to expand...
Click to collapse
Sorry, but it's not that simple. I have had to start all over and rebuild the O/S as loading the wrong 4ext on messed it up - would no boot past "go go go". Hence we need to know precisely which 4ext to load.
Whilst your instructions are great and will be/are a big help, we must calrify this to ensure the project is a success for others.
So one last vital piece of information needed, if you can help clarify.
Many thanks for your help
BTW. Are we talking about a completely bricked SD-Card or one that just need some fixing. i.e. has a small fat partition?
Whatdoyaknow said:
Sorry, but it's not that simple. I have had to start all over and rebuild the O/S as loading the wrong 4ext on messed it up - would no boot past "go go go". Hence we need to know precisely which 4ext to load.
Whilst your instructions are great and will be/are a big help, we must calrify this to ensure the project is a success for others.
So one last vital piece of information needed, if you can help clarify.
Many thanks for your help
BTW. Are we talking about a completely bricked SD-Card or one that just need some fixing. i.e. has a small fat partition?
Click to expand...
Click to collapse
If you flash any recovery your WP7 will be gone. No matter what partition size you set. Sorry. That's exactly why it doesn't matter which 4EXT you take.
Regarding your second question: I was suspecting that Nysean1 only fixed a card with a small FAT partition. But he recons that he also fixed the DRM encrypted card from e.g. a Yuki or xboxmod ROM.
Sent from my multi talented HD2
Sneakyghost said:
If you flash any recovery your WP7 will be gone. No matter what partition size you set. Sorry. That's exactly why it doesn't matter which 4EXT you take.
Regarding your second question: I was suspecting that Nysean1 only fixed a card with a small FAT partition. But he recons that he also fixed the DRM encrypted card from e.g. a Yuki or xboxmod ROM.
Click to expand...
Click to collapse
Yes I realize that things will be wiped. But I grabbed 4EXT from the Market which jammed at GoGoGo. So best we warn folk about that.
I downloaded and installed EXT4_CoreDroid_10_180_10 from your site thanks very much - seems all OK. Have Android NAND back running again
I have now tried it on a fully bricked SD Card, but no luck at all for me. Tried about 10 times will different options. So it seems it is not an unlock for a fully bricked card (unless I've done something wrong - you say any of the Ext4 from your site should work the same)
Tried it on a card with a small FAT partition, and that's worked, but I can do that using partition program on my PC, so no added value from my perspective
(unless Nysean1 can throw some more light on this)
Whatdoyaknow said:
Yes I realize that things will be wiped. But I grabbed 4EXT from the Market which jammed at GoGoGo. So best we warn folk about that.
I downloaded and installed EXT4_CoreDroid_10_180_10 from your site thanks very much - seems all OK. Have Android NAND back running again
I have now tried it on a fully bricked SD Card, but no luck at all for me. Tried about 10 times will different options. So it seems it is not an unlock for a fully bricked card (unless I've done something wrong - you say any of the Ext4 from your site should work the same)
Tried it on a card with a small FAT partition, and that's worked, but I can do that using partition program on my PC, so no added value from my perspective
(unless Nysean1 can throw some more light on this)
Click to expand...
Click to collapse
Sorry it did not work for you. I am not hundred percent sure what kinda lock my card had. I wanted to run WP7 and android...so I installed WP7....did not quite partition the card for android as per the instructions.....this is the second time I failed to do that....WP7 without the option of android sd is lame....anyways therefore I wanted my card back...could not format it in anyways...via my camera...was not even recognized by my computer and mini tool....send usb unlock code....all failed for me....this happened to my last card also...i was never able to revive it...and did not work out any method I could find in xda and outside....but this time and with this diff. card 4ext was able to partition and format it back to normal. I can't even find that one anymore to try my new finding as I am aslo skeptic to try and take another chance with my current card as I use it everday....that I know for sure had Yuki rom installed when it first came out ...I am still searching for that card...and if I do find it I will certainly give feed back.
However....those who have installed ext4 will certainly appreciate it...since it is (I think) the best recovery you can have for you android...only thing is that some roms don't support ext4...so be aware of that.
Thanks for your explanation NYSEAN1
Thus your title/heading is fully correct - to unlock from Yuki rom.
I guess I got excited thinking that meant unlock a "bricked" SD card, which has been bricked through an error installing a WP7 rom such as Yuki rom. The two issues are different. However, you have not claimed the later case, but the first, and that is fair enough.
I have always hoped that an Android system might resurrect a fully bricked card- I still hope, but not their yet.
Thanks again
Edit 1: BTW thanks for putting me on to ext4. I do like it!!!
Edit 2:
Seems like the only way for a bricked card is for a Nokia device (or similar), which I don't have. See
http://forum.xda-developers.com/showthread.php?t=1242071
NYSEAN1 said:
Sorry it did not work for you. I am not hundred percent sure what kinda lock my card had. I wanted to run WP7 and android...so I installed WP7....did not quite partition the card for android as per the instructions.....this is the second time I failed to do that....WP7 without the option of android sd is lame....anyways therefore I wanted my card back...could not format it in anyways...via my camera...was not even recognized by my computer and mini tool....send usb unlock code....all failed for me....this happened to my last card also...i was never able to revive it...and did not work out any method I could find in xda and outside....but this time and with this diff. card 4ext was able to partition and format it back to normal. I can't even find that one anymore to try my new finding as I am aslo skeptic to try and take another chance with my current card as I use it everday....that I know for sure had Yuki rom installed when it first came out ...I am still searching for that card...and if I do find it I will certainly give feed back.
However....those who have installed ext4 will certainly appreciate it...since it is (I think) the best recovery you can have for you android...only thing is that some roms don't support ext4...so be aware of that.
Click to expand...
Click to collapse
If you couldn't reset the card by sending unlock cab, it simply means you did not suffer from the WP7 DRM encryption. That means your method is up until now nothing more than a faint hope. Someone has to really verify.
My theory:
It is from my perspective and experience much more likely that the file system, boot record or both had been damaged in a random way. since every partitioning tool pursues a different way of doing it's job, some might fail at your particular issue and some might get the job done. This time, it worked out for you with the 4EXT while all others failed.
Tools to try before giving up:
- windows format
- SD formatter from SD-association
- mini Tool
- EASEUS Partition Master
- Acronis
- 4EXT
To overcome the WP7 DRM encryption you would need a tool that forcefully ignores some SD-specific parameters and commands, which where originally invented to lock down these cards. As with all these systems, they only work if both content provider and content reader agree to stick you the specifications. If one doesn't, the encryption doesn't work. So far, only a certain edition of Nokias symbian does ignore the encryption command. BUT: I was hoping that also the 4EXT would maybe ignore it...
Sent from my multi talented HD2
Cotulla has indicated that the next version of MAGDLR for LEO will include the ability to unlock SD cards that have been locked by WP7.
Thanks a lot mt8 had a 8 gb card and when i installed android on nand the card was preety much dead 0 Kb space and formated using various formating tools but no luck and saw this thread and gave it a shot and i have my card with 8 gb in it. i am using cwm 3.0
Sent from my HTC HD2 using xda premium
First of all I would like to thank xda and the whole community for making all this possible. I have learned a lot and I am really grateful to all of you.
So I will start with the problem I have.
I have a 512 HD2 Europe version that I used since it came out. First as everyone knows, it came with a 6.5 version, which i got bored of quickly and replaced with a rom that i found on this web-site. 2 years ago i followed all the instructions and successfully installed a working gingerbread 2.3.7 on my device with everything working smoothly ( minimal lag). I was all happy and using it till a few weeks ago when I got a call and when i picked up my phone got stuck and i had to restart by removing the battery. And now come the problem that I am facing:
MAGLDR 1.13 Feb 2011 version doesnt boot my android anymore. Excuse me with the terminology but I got a bit rusty over the years and i might not be saying things right. Therefore I will try to be as simplistic as possible. Every time I try to turn on my HD2, it only loads up to the first screen after the HTC LOGO Screen, which says MAGLDR 1.13 Feb 2011. It vibrates a couple of times and afterwards nothing happens.
Of course the first thought that came to my mind was to re-install like the good old windows style. A re-install fixes everything, however when I connect my phone to the PC, it is not recognized by the PC (so that I can access the SD card).
I would be grateful to anyone who can give me guidelines or contribute to the whole problem-solving case.
Thank you in advace.
Can you get to magldr menu?, press and hold power button
Sent from my NexusHD2 using xda premium
No, it just turns on the first screen after the htc logo and the phone does not load anything. A strange remark is the fact that once it opens the boot screen, it vibrates 3 times and then nothing or it restarts itself.
Have you tried re-flashing MAGLDR?
Marvlesz said:
Have you tried re-flashing MAGLDR?
Click to expand...
Click to collapse
+1
Also what does it say on bootloader screen? Hold volume down while booting phone ...
Sent from my NexusHD2 using xda premium
Thank you for your replies.
While booting when I hold the volume key down, the red green blue white screen appears.
It says:
PB81100 HX-BC
SPL-2.08. HSPL 8G XE
0x05
CotullaHSPL 0x40
Afterwards, I am not able to do anything besides turning off by removing the battery.
himmelhammer said:
Thank you for your replies.
While booting when I hold the volume key down, the red green blue white screen appears.
It says:
PB81100 HX-BC
SPL-2.08. HSPL 8G XE
0x05
CotullaHSPL 0x40
Afterwards, I am not able to do anything besides turning off by removing the battery.
Click to expand...
Click to collapse
That looks fine, and that is the only way to exit.
Have you tried marvlesz's suggestion
Sent from my NexusHD2 using xda premium
Well, when i connect my phone to the pc, it is not recognized.. How could I reinstall ?
himmelhammer said:
Well, when i connect my phone to the pc, it is not recognized.. How could I reinstall ?
Click to expand...
Click to collapse
Boot to multicolour screen again and plug in usb cable to pc and see if the word serial at bottom of screen turns to USB, if so you can install magldr. Otherwise you need to install the correct drivers for your OS. Download and install WMDC if you are on win 7 or XP!
Edit: Here is a link to some good reading to help with the above...
Ok, "USB" appears after "Serial", then the next step is to reinstall MAGDLR but as I start the program it gives me the following error:
An error has occurred
Read below for more information
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: can't open config file
Info: .\RSPL\RSPL.cpp (304)
Any clues anyone ?
Are you using the hd2 toolkit?
Sent from my NexusHD2 using xda premium
no, i just use the MAGDLR rar, which you extract and then have to run an exe file.
should i try the toolkit? and is there a 32bit version for it?
Yes get the toolkit, its easier. Make sure to select correct partition size for the ROM.
Sent from my NexusHD2 using xda premium
shanman-2 said:
Yes get the toolkit, its easier. Make sure to select correct partition size for the ROM.
Sent from my NexusHD2 using xda premium
Click to expand...
Click to collapse
My advice to you is to start over from scratch and God knows I've done it a zillion times...from scratch here we go...
A1. Chase down and install the HD Toolkit and execute it!
A2. Remove your case, battery cover, and memory card. You will need a microUSB cord.
A3. I'm running Windows 8 Pro on my end and XP prior to it. Make sure your drivers are up to date.
A4. It won't matter if you're corded...plugged in to your computer or you insert the cord with each step.
B1. Press and hold you're volume down toggle, reinsert battery, and you will be quietly greeted with your bootloader's rainbow screen.
B2. Make sure you have "USB" at the bottom center.
B3. Click "Task 29" tab on HD2 ToolKit; this will wipe NAND on your device...it takes only seconds.
B4. The moment your device restarts again press and hold down your volume down toggle and again you will be greeted with your bootloader's rainbow screen. If you fail to get to this screen you will be greeted with "HTC" and that's it...just pull the battery and do it again.
C1. There are a gazillion ways to install the MAGLDR and Recovery but when I do it I click on MAGLDR and it too only takes a few seconds.
C2. The device will reboot automatically and let it. You will be greeted with the MAGLDR menu.
C3. Using your volume down toggle, scroll down to number 5 - USB Flasher
C4. You're looking for "Wait USB...USB"
C5. Open on your computer wherever you have your recovery files...again, there are a gazillion different ways to do this, but I use the cLK1.3_400mb partition for the EnergyROM.
C6. Open the folder and right click "DFT" Application
C7. Follow the prompts...you're looking for Waiting Connection to USB,,,be patient and pay attention to your device.
C8. Your device will respond by installing the file.
C9. From MAGLDR, scroll down to #8 Recovery...you will flash your Roms and other zip files from here.
D1. Using SD Formatter...format your card...it can be anything up to 64GB, really!
D2. Using Mini-Tool Partition Wizard you will perform the necessary steps to set your card up. I usually setup 75% of my card as Fat32 32K cluster, 25% EXT4 default cluster. The formatting of the Ext4 partition will take several minutes dependent upon the size of your card.
D3. Once done, while the card is still inserted to your computer, copy to your card all the zips you will need to flash your phone. You will not be able to see the Ext4 from Windows/File Explorer (Windows).
These steps are for NAND install; I've yet to successfully install EnergyROM by any other method than this way; newer ROMs, no problem regardless how you want to do it as long as your memory card is setup as above. There can be problems with your memory card, especially the slower ones. I recommend Class 6 or Class 10, though there are a few issues using the 64GB Class 10s. I've read the 16GB and 32GB Class 6's are pretty darn good. That said, I am using a 64GB SDXC I reformatted in my HD2. There is lag in the up to date Roms like NexusHD2 ICS and JB, but not enough to take away from a good experience....as long as you don't bog it any further down with resource hungry apps.
E1. At this stage the MAGLDR is the only thing on your device, reinsert the SD card to your device.
E2. Scroll down to #8 and follow the prompts
E3. I installed EnergyROM via NAND for T-Mobile
F1. Once all done and you have the three rings revolving around each other...enjoy.
F2. If you have T-Mobile Wi-Fi calling, use the appropriate file for the operating system; I'm not aware there is a JellyBean version; however, I've had no trouble with Gingerbread or ICS as long as you have the correct SIM card provisioned for it.
F3. I use App2Mgr to transfer what programs can be safely put on the SD card's Ext4. Music, Photos, Videos...you know the drill go on Fat32; you pray you don't have to reformat that part of the card given how much data you may have there.
Think positive! I can't tell you how many times I spent an evening enjoying Trial & Error on my couch! I usually read every known thread on the subject while experimenting.
berrywr said:
My advice to you is to start over from scratch and God knows I've done it a zillion times...from scratch here we go...
A1. Chase down and install the HD Toolkit and execute it!
A2. Remove your case, battery cover, and memory card. You will need a microUSB cord.
A3. I'm running Windows 8 Pro on my end and XP prior to it. Make sure your drivers are up to date.
A4. It won't matter if you're corded...plugged in to your computer or you insert the cord with each step.
B1. Press and hold you're volume down toggle, reinsert battery, and you will be quietly greeted with your bootloader's rainbow screen.
B2. Make sure you have "USB" at the bottom center.
B3. Click "Task 29" tab on HD2 ToolKit; this will wipe NAND on your device...it takes only seconds.
B4. The moment your device restarts again press and hold down your volume down toggle and again you will be greeted with your bootloader's rainbow screen. If you fail to get to this screen you will be greeted with "HTC" and that's it...just pull the battery and do it again.
C1. There are a gazillion ways to install the MAGLDR and Recovery but when I do it I click on MAGLDR and it too only takes a few seconds.
C2. The device will reboot automatically and let it. You will be greeted with the MAGLDR menu.
C3. Using your volume down toggle, scroll down to number 5 - USB Flasher
C4. You're looking for "Wait USB...USB"
C5. Open on your computer wherever you have your recovery files...again, there are a gazillion different ways to do this, but I use the cLK1.3_400mb partition for the EnergyROM.
C6. Open the folder and right click "DFT" Application
C7. Follow the prompts...you're looking for Waiting Connection to USB,,,be patient and pay attention to your device.
C8. Your device will respond by installing the file.
C9. From MAGLDR, scroll down to #8 Recovery...you will flash your Roms and other zip files from here.
D1. Using SD Formatter...format your card...it can be anything up to 64GB, really!
D2. Using Mini-Tool Partition Wizard you will perform the necessary steps to set your card up. I usually setup 75% of my card as Fat32 32K cluster, 25% EXT4 default cluster. The formatting of the Ext4 partition will take several minutes dependent upon the size of your card.
D3. Once done, while the card is still inserted to your computer, copy to your card all the zips you will need to flash your phone. You will not be able to see the Ext4 from Windows/File Explorer (Windows).
These steps are for NAND install; I've yet to successfully install EnergyROM by any other method than this way; newer ROMs, no problem regardless how you want to do it as long as your memory card is setup as above. There can be problems with your memory card, especially the slower ones. I recommend Class 6 or Class 10, though there are a few issues using the 64GB Class 10s. I've read the 16GB and 32GB Class 6's are pretty darn good. That said, I am using a 64GB SDXC I reformatted in my HD2. There is lag in the up to date Roms like NexusHD2 ICS and JB, but not enough to take away from a good experience....as long as you don't bog it any further down with resource hungry apps.
E1. At this stage the MAGLDR is the only thing on your device, reinsert the SD card to your device.
E2. Scroll down to #8 and follow the prompts
E3. I installed EnergyROM via NAND for T-Mobile
F1. Once all done and you have the three rings revolving around each other...enjoy.
F2. If you have T-Mobile Wi-Fi calling, use the appropriate file for the operating system; I'm not aware there is a JellyBean version; however, I've had no trouble with Gingerbread or ICS as long as you have the correct SIM card provisioned for it.
F3. I use App2Mgr to transfer what programs can be safely put on the SD card's Ext4. Music, Photos, Videos...you know the drill go on Fat32; you pray you don't have to reformat that part of the card given how much data you may have there.
Think positive! I can't tell you how many times I spent an evening enjoying Trial & Error on my couch! I usually read every known thread on the subject while experimenting.
Click to expand...
Click to collapse
?, Thanks for the info, but I had already linked OP to relevant tuts...
Thank you berrywr for the time you spent on my problem. I will try following your steps as soon as I have some free time left. Thank you so much shanman ! I will let you know asap if it worked out.
there is just one thing in the steps given by berrywr.. I have long lost my recovery files (original windows 6.5). Is that a big problem?
himmelhammer said:
Ok, "USB" appears after "Serial", then the next step is to reinstall MAGDLR but as I start the program it gives me the following error:
An error has occurred
Read below for more information
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: can't open config file
Info: .\RSPL\RSPL.cpp (304)
Any clues anyone ?
Click to expand...
Click to collapse
run the installer exe as administrator