[Q] Bootloader: USB recognized, but unusable. Bricked, or still hope? - HD2 Android Q&A, Help & Troubleshooting and Genera

Alas, the old companion HD2 seems totally locked...
In my attempt to flash to an Android ROM, I spent two whole days digging through XDA. So I got me the HD2toolkit, a backup stock .exe, and the target ROM.
installing hSPL worked
magldr wouldn't install. So I updated the phone to get the right radio. This unfortunately upped hspl to 3.03. So i downgraded that by installing hspl4 and opting for 2.08.
Magldr then installed nicely, but the phone would not restart: the OS wouldn't start.
So I task29 succesfully, and install the windows update on the phone again. Works just fine.
Back to installing magldr, since hspl is still at 2.08 according to the tricolor screen. (that surprised me, since at the first time it went to 3.03).
And then it all went to bits. I get an HTC screen on white background, but no 'quietly brilliant' for 5 mins. Going to bootloader works, it recognizes the USBcable (can hear the telltale sound on the PC as well), but no data can be sent across that cable... No hd2toolkit orders (202 connection errors), and no official ROM executables will connect.
Tell me, is this now an official brick? Or might one of you have The Ultimate Revival Secret for me?

myrtthin said:
Alas, the old companion HD2 seems totally locked...
In my attempt to flash to an Android ROM, I spent two whole days digging through XDA. So I got me the HD2toolkit, a backup stock .exe, and the target ROM.
installing hSPL worked
magldr wouldn't install.
Click to expand...
Click to collapse
do you mean magldr wouldnt START? see note at the end**
So I updated the phone to get the right radio. This unfortunately upped hspl to 3.03.
Click to expand...
Click to collapse
no need, you could have just flashed teh radio, thus avoiding changing teh whole rom, removing magldr and hspl, and taking about ten minutes less.
So i downgraded that by installing hspl4 and opting for 2.08.
Magldr then installed nicely, but the phone would not restart: the OS wouldn't start.
Click to expand...
Click to collapse
ummm, what OS? you havent flashed one yet
So I task29 succesfully, and install the windows update on the phone again. Works just fine.
Back to installing magldr, since hspl is still at 2.08 according to the tricolor screen. (that surprised me, since at the first time it went to 3.03).
Click to expand...
Click to collapse
spl is prevented from being changed by usb flashing once hspl is installed
And then it all went to bits. I get an HTC screen on white background, but no 'quietly brilliant' for 5 mins.
Click to expand...
Click to collapse
again, there is nothing to boot, , flashing magldr removes winmo, and you havent yet flashed an android rom.
Going to bootloader works, it recognizes the USBcable (can hear the telltale sound on the PC as well), but no data can be sent across that cable... No hd2toolkit orders (202 connection errors), and no official ROM executables will connect.
Tell me, is this now an official brick?
Click to expand...
Click to collapse
not even close. So far everything sounds like a simple missmatch between magldr spl and radio, made more confusing because you arent really 100% sure of what exactly is being added / removed at each step. (Sorry, not having a go, just being blunt )
the connection errors might be an issue, but probably not, give your PC a reboot, use a different usb port.
in bootloader, what do the top line, and the spl line say? does it say USB at the bottom?
With your phone in bootloader and connected to PC, on the PC, click start - right click 'computer' (or 'my computer', depending on win version) choose properties, find device manager, and see what entry is listed for the phone.
**NOTE when you flash magldr, if the radio or spl is wrong, magldr will be there, it just wont show up, it will go straight to the boot screen and hang there. You dont have to re flash magldr, just change the spl/radio to the correct ones, and magldr is still there and should start, no need to re flash it. Magldr is only removed by flashing a stock winmo rom (or a cooked winmo rom that includes splash screens)

Be still, my beating heart...
Thanks for your answer, Sam. No harm done in the bluntness, you quite rightly marked me as a noob. Indeed not all is clear on the boards, but we all do our best.
As you said, I had no clue all the OS on my phone were gone. So i saved me another ten minutes (thank you, again) and flashed a new radio. And behold! Magldr is back!
You, sir, should be kissed!
Now to find out how to install a Zimage, that still seems to elude me (seeing there is no daf.exe or install.exe)... I'm aiming for this one to install: http://forum.xda-developers.com/showthread.php?t=1250703. hd2toolkit will only help out on nb or nbh, though.
If you could point me in the right direction?
And muchos thankyous are coming your way!

well first up you should add cwm on top of magldr, most roms are clockwork(cwm, cwr its called slightly different things, all mean the same, , 'clockwork mod recovery') roms.
You can do this with the toolkit, but instead of the hd2 being in bootloader, enter magldr and choose 5 usb flashing, then in the toolkit, choose a partition size, (160 by the looks of it, for an eu model) and when thats done,
restart,
enter magldr
option 8 ad recovery - will start cwm,
then choose 'install zip from sdcard' - 'choose zip from sdcard'
but remember BEFORE you do all the above, you should
1 - set up your ext partition (you can do that in cwm, , 'advanced' - 'Partition sd card', but be warned it will wipe the whole card)
and
2 - copy the romname.zip onto teh sd cards fat32 partition.
EDIT - oh and most roms have two versions, a magldr version and a cLK version, dont confuse cLK with CWM, theyre different things. For now stick to teh magldr versions, you can find out about cLK later.

Now we're getting places!
So if I understand correctly, the toolkit has not installed CWM. OK, I'll go and look for that rom.
However, the android I pointed out is, if I read you correctly, not NAND? It was posted in the NANDcategory, so that confuses me. Bummer, I need my SDcard for data.

yea its a nand rom. most nand roms use an EXT partition, and for most sense 2 roms, its advisable, and for sense 3 roms it simply wont work without it. Look at the partition size for the tmous version(which is the same but doesnt use an EXT),,,435meg, that's just for the system partition, it would leave you about 50meg for apps and data.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
myrtthin said:
So if I understand correctly, the toolkit has not installed CWM. OK, I'll go and look for that rom.
Click to expand...
Click to collapse
not a rom, as such. Go into the toolkit, with teh phone in magldr, option 5 'usb flashing',,at the top of toolkit 'magldr repartition', below that click the 'custom' size, below that cache size 5 (from the 5/160/5, personally i use 45 regardless of what teh rom says, but thats just me, its not absolutely critical), then below that 'repartition', , a popup will ask you teh custom size, 160, OK,and off it goes installing cwm.

Hm, interesting.
Thanks to your feedback, i get magldr 1.13 up and running, just fine.
Next to that, flashing ROMs seems to be working smoothly.
However, none of the android ROMs are taking! I downloaded (from several sources to exclude download errors) three ROMS:
1) rom Based RUU Desire HD 3.06.405.1 - With sense 3.0 - Android 2.3.5 http://forum.xda-developers.com/showthread.php?t=1264828
2) Desire_S_sense3.5_Android.2.3.4_v1.2_EU.zip http://forum.xda-developers.com/showthread.php?t=1250703
3) GBLeor3 http://forum.xda-developers.com/showthread.php?t=1256581
nrs. 1 and 3 are installing, but on startup hang on HTC's splashscreen. Nr 2 is not installing (aborting during install, status 0), tried both on 5/160 and 5/200.
Seems like android install through magldr is not working at all! Any thoughts?
To be complete, I installed:
hSPL 2.08
magldr 1.13
radio 2.15.50.14
repartitioning through hd2toolkit
It all started with stock winmo, wich i updated to 3.14.404.2. It's an EU phone.

Don't forget it takes a while on first boot, especially the large ones,I can well believe a sense 3 rom that is writing 300+ Meg to the ext partition would take well in excess of ten/fifteen minutes and more first boot.
Also, if you flash a rom and then go to flash another, you will be leaving parts of the old rom on the SD card. In cwm before the flash choose wipe data/factory reset. That's in cwm, not magldr. Also, did you set up the ext through cwm?
My advice would be go for a simpler rom, one of the cm7 roms, typhoon for example, purely to show its working.

The desire S (sense 3.5) did not even install after 6 hrs, so I'm guessing something's wrong there ;-)
I'll wipe data between flashes, and per your suggestion, try something light as an appetizer first. Not before next weekend though! I lost enough sleep )
Thanks again!

When I started flashing nand, very often(six times in ten maybe?) the first boot never completed, and I soon learned that if after a few minutes nothing happened,I'd pull the battery and it would Start the next boot. Also, keeping the hard keys lit (touch every min or so) seemed to help.
I know I'm straying into "lucky socks" and good luck charm territory,but can't help to try, and I DO know I've seen one rom in the past where the instructions mention keeping the screen on as being important, so who knows?? Not this stoned and overtired techaddict!
I've had a stable rom that I've been just flashing updates for some months now, so I've not had that situation for a while. The wipe data command in cwm is deff important tho.
The only other thing that consistently causes non starting is too small a partition size.

cyanogen is stable
Yub yub, commander, time for an update. Cyanogen has been installed and working for close to 3 months now. So it actually does all work!
On the boards, I can now see updates on the ROM I crave (sense 3.5 from htc desire), and those updates are suggesting 260 Mb partitions (no ext). So it would seem my first partition was indeed too small.
So tempted to try those again...
Too bad cyanogens rom backup is acting weird. Otherwise it'd be no problem just to try, eh?

Related

New to hd2 need to be clear on a few things

I came to this phone solely because there are so many roms to choose from and a lot of development. In the past I have worked flashed dif galaxy s phones, and mytouch 4g so I am not a complete noob.
When i power the phone on these are displayed:
R: 2.10.50 26
G: 15.39..50.07U
D: 2.13.90963 8G
In settings my flash size is 1024mb
I read the guide through and I just want to be 100 percent clear that my phone is capable of something before I flash it. So in short, do I just flash hardspl to phone, then magdlr, then the rom? I have a macbook pro and my windows desktop is old and sucks so I try to avoid using it whenever possible. Once i flash hardspl and magdlr can I use clockwork recovery to flash my rom? I am going for the cm7 nightlies. All help is greatly appreciated!
Yeah that's correct. I don't think there are any osx installers though, so you'd probably have to do all this through bootcamp. I don't have a mac so I don't know about the stability of bootcamp, but you really gotta make sure your computer doesn't crash during the flashing process, especially HSPL.
After having Magldr installed you can either use that to flash, or indeed use clockwork (which I recommend). MDJ's Gingerbread is a great CM7 nightly build.
Thanks for your quick reply! How long does it take to flash hardspl? And do I need to have that activesync thing going with windows mobile? This phone is 100% stock I dont want to back it up so can I just avoid windows mobile active sync and run that program in the noob tut
And one more thing, do I need to check to see if my stock spl is supported? What is everything I need to verify to ensure I will not brick the phone due to flashing the wrong thing? Thanks
Go to the guide, it tells you what you need in there. HSPL takes seconds to install. Once that is installed, it's pretty hard to brick your device. Just be wary when installing a stock rom. Best advice is to read lots.
Good luck.
:edit:
I'm not sure if you need active sync. I'm 99% sure you do, but I may be wrong.
Sent from my HD2 NANDroid using XDA App
Flashing HardSPL takes about 20s.
A rom takes about 10m. You can also check this link.
http://forum.xda-developers.com/showthread.php?t=925509
and
http://forum.xda-developers.com/showthread.php?t=893948
They explain how it works. Even with video.
good luck!
I'm guessing you have a T-Mobile so watch out! Don't flash an EU-radio.
If you want android your radio is good. No need to change it.
Flashing a rom takes only 3-4 minutes, but it will stop at 96% or 99% for a few secs, so don't freak out
also be sure to flash the newest version of HSPL. and check the youtube vidz, there many around. you don't even have to read, just google youtube+HD2+hspl
The support for this phone is much better than other devices, quick responses thanks! Just to be safe I am trying to find the windows sync thing for the phone. When I am finished flashing hardspl and magdlr do I need to format my sd card to a special way or can I just delete all the stuff on it and put the rom?
I strongly recommend that you first install the official 3.14 firmware, It has the newest radio so you don't have to worry about bricking your phone. After that flash hdspl and you are safe and ready to install magldr and Android.
Depends on the rom, zip, app2sd+, cwm, anything which mentions ext2/3/4, data.img data on sd, all require certain partitions. I would recommend starting with projections rom. It's quick and easy to get started with, and is a good base to get some confidence.
Sent from my HD2 NANDroid using XDA App
I just installed the hspl and now i am going to do the magdlr. Really I only want cyanogen mod 7 nightlies on here. I am pretty confident its just whenever it is my first time with any phone I like to be 100% clear because they all vary. I didnt get to looking at the installation of cm7 yet but I am sure I will be going to ext4 with it too. What format do sd cards come stock? I just wiped everything on it but im guessing thats not enough lol.
Um confused... I just got around to flashing magldr 1.12 and it said on screen and in guide post it will take ten min, it took no more than 30 sec. It did boot me into the black magldr screen though so i guess its good. Now can flash cm7 or is there other stuff. I am sure I will find out with more reading which i am about to do but I would like to use cwm to do it.
rrodxbox360repair said:
Um confused... I just got around to flashing magldr 1.12 and it said on screen and in guide post it will take ten min, it took no more than 30 sec. It did boot me into the black magldr screen though so i guess its good. Now can flash cm7 or is there other stuff. I am sure I will find out with more reading which i am about to do but I would like to use cwm to do it.
Click to expand...
Click to collapse
It's just a very wide margin to prevent people from flooding the forums if the flashing takes a little longer than expected, 30 seconds is normal.
Go to the clockwork thread and follow the 7 steps posted, you can then use CWM to flash CM7.
I have been trying to flash with usb flasher and I keep getting an error.
Error Description: USB init failed.
Can I flash cwm from magdlr? Every time I reboot it goes to that.
I see two possible problems here:
- In Magldr, have you picked menu item #4? (Something like USB Flasher). If you can still see all the options on the menu, you have not correctly selected it.
- Your USB drivers are not correctly installed. Reboot computer, power off and unplug phone, replug and restart Magldr. Wait for drivers to correctly install.
I just did what was suggested and same thing. Can I install it a different way? Option number 5 is usb flasher, 4 is mass storage.
My bad, I'm still using an older version of Magldr where it's #4.
What are you flashing by the way, CWM or CM7?
By the way, are you running the flasher as admin? Not sure which OS it is you're bootcamping, but right click on the installer and choose Install as administrator should be an option. Might be the problem!
I am on my desktop pc which is xp so I do not believe i need to run as admin. I was just checking out another post in this forum that has a fix for nand usb init failed, I am lost as to what daf.exe is. It sounds when I figure that out I should be good to go.
And I am trying to install cyanogen mod 7 mdj's version. If I can not get usb thing to work could I install clockwork mod without having to use computer and jsut put a .zip file on sd card?
I just hit run and typed DAF.exe and there isnt one. I am not completely lost lol
DAF.exe is the clockworkmod flasher.
I'm not sure what's going wrong, but just try everything again and make sure you follow the instructions very closely, you're probably just overlooking something somewhere.

[Q] Booting Problem

Problem:
Won't boot into any ROM.
Phone Details at Start:
Telstra HD2, HSPL 2.08, Radio 2.15.50.14, magldr 1.12, Windows Phone 7
Description:
I was running Windows Phone 7 when it decided to crash and restart. However it got stuck in a restarting loop; restart then crash during loading which caused it to restart then crash, etc. Then magldr came up with 1EFATAL HIT 1.
I figured WP7 had somehow corrupted part of the install but nothing I can do seems to fix it.
I have tried:
-Reflashing it with WP7.
-Reflashing it with another WP7 build.
-Reflashing to magldr 1.13 then WP7 again.
But none of these worked so I tried to go for a NAND Android build. However I couldn't get the ClockWork Mod to work. It too failed to boot with the same problem as WP7. Now I just wanted to get the phone in a working state again so I have tried:
-Formatting the SD card
-Reflashing to a custom winmob6.5 build
-Reflashing to a custom winmob6.5 build I had previously used and worked fine
-Changing the Radio to 2.14.50.02 then reflash to a custom wm6.5
-Changing the Radio to 2.12.50.02_02 then reflashing to a custom wm6.5
When I try the custom wm6.5 rom I see the boot screen but it just sits there and goes no further. I have tried installing an old copy of the chunky rom (as it changed the boot screen ) but still just sits at the boot screen.
I have tried redownloading all of the files I'm flashing with in case there was a problem downloading it. Also I have tried using files I already had which were working, but nothing seems to have fixed it.
Some things I have noticed are:
-that all flashings have and still load without error
-that it doesn't have any problems loading into the HSPL
-when ever I tried an install with magldr usb flash (CWM or WP7) it would work but at the end of the flash it said it would restart but never did. I had to remove the battery
-loading into magldr I could select the restart or powerdown option but it would just hang and again I had to remove battery to turn it off
Does anyone have any suggestions as to what I can try to get it fixed? The only things have haven't tried are flashing with a stock rom or reflashing another HSPL. Both of those I though could cause trouble for the currently working HSPL, which if I lost would cause more problems. Currrently I am under the impression it is a hardware failure as no rom (mb6.5, WP7 or CWM) will boot and magldr installed fine but wasn't able to restart the phone.
Check your battery pins to see if they're in anyway bent. If they are, just push them back a little bit with your finger.
Have you tried Task29? I think the only other way would be to flash stock again and start over.
Sent from my HTC Vision using XDA App
Skellyyy said:
Check your battery pins to see if they're in anyway bent. If they are, just push them back a little bit with your finger.
Have you tried Task29? I think the only other way would be to flash stock again and start over.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yes, I have tried Task29 and then tried installing both magldr then CWM and wm6.5. It however didn't make a different as I still got the same error. Sorry, I forgot to mention this in initial post.
I have also read about the battery pins being bent. I haven't tried it but from what I can see mine are all about the same height and seem pretty straight. When I put in the battery they also seem to be pushed back a bit so I am assuming they are all making contact. I was a bit worried about over extending them but I might give it go if no other option becomes available.
I've seen several times people with a phone that seems to flash, but nothing actually changes.
The only way you can visually test this in your current state is to change spl to something different, and look in bootloader see if it changed, but you said you don't wanna, so.
You can try flashing HSPL 4 and select HSPL 3.03 and see if gbiz is sucessful. If you have HSPL 3.03 in bootloader then you know it is flashing and you can go back to HSPL 2.08. Also you can try flashing your stock Telstra ROM via USB cable and computer as this method will not change your HSPL 2.08 but flashing it via SD card will revert you back to SPL. I think flashing the stock ROM will be your best bet for now.
Well I originally had the energy boot screen and when I flashed to a copy of the chunky rom it changed to its one. I would have thought it was at least partly flashing. Also I have removed with magldr with task29 then reflashed (with magldr) and was able to boot into magldr. So I think the flashing is happening successfully.
I you think reflashing the HSPL could work then I'll give that a try. As I haven't done that yet. If that doesn't work I'll take a look at flashing the Telstra ROM. I know flashing a stock rom is mentioned as a solution but I wasn't sure why I would make the phone work any better than a custom rom with concerns to booting.
Thank you for your suggestions.
Just to cover all bases here, your HD2 is not getting really warm or warmer than usual is it? If so this is a sign of thermal breakdown, but like I said this is just to cover all bases here.
From what I can tell it hasn't been getting any hotter than usual.
Re:"why to use stock instead of custom"
Its because a stock rom flashes everything, spl, splashscreen, radio and rom.
Also, some customs use a secondary splashscreen, which would replace magldr, so if things aren't right, starting over by flashing your correct rom is often advised just to draw a line under the current attempts and start over.
Don't forget that even if the stock flash fails, if you did it from bootloader then Hspl is likely gone, and magldr too, possibly.
Just an update. I flash a Telstra ROM which to my surprise it booted... after a couple of tries. Decided to reboot it to see if it starting up was just luck which it turns out it was. I couldn't get it to start again then it refused to even get into the bootloader. So I am sure enough now that it is a hardware failure and am taking it in for warranty.
Thanks again for the help.

[Q] Freezing issue for the clever folks

Hello folks, I appear to have gotten into bother during a rom flash. After successfully installing a MAGLDR nand rom via CWM, the first boot of said rom just gives me the frozen splash screen without animation and the boot does not complete. Happens the same with three different roms.
I suspected somewhere further back in the boot process was at fault so I reflashed a known working radio rom, but problem still persists.
Despite a LOT of reading I can't see much about freezes at this point in the boot process on MAGLDR roms.
Bits that work - HSPL rainbow boot screen happily comes up, Task 29 works, magldr reinstalls and works fine, CWM perfect. Installs roms from SD (freshly reformatted) and appears to be ready to go, until boot actually begins then... splash screen freeze.
I have redownloaded various versions of everything to ensure no issues with corrupt files. I have also used different SD cards and ensured freshly formatted FAT32.
If it helps anyone, I have previously used NDT CM7 12.1 for about a month with zero problems.
Any other less obvious stuff I'm missing?
I'm off to bed so will be approx 7 hours from post time when I start responding. In the meantime I've put MAGLDR 1.10 on the phone so at least it can charge!
Many thanks in advance for reading.
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
drachers said:
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
Click to expand...
Click to collapse
How long have you been leaving the ROM on the boot screen? A first install of an Android ROM can take anywhere up to and over 15 mins for first boot. I also remember one when installing a hyperdroid ROM I had to restart the phone once to get passed boot splash.
I'd recommend flashing a popular ROM, leaving it for 20 mins, restarting and leaving another 20 mins. What do you have to lose? Just remember magldr doesn't have charge while off capabilities!
Also check your partition sizes and layout (you have to edit flash.cfg for magldr builds, partition sizes depend on the rom you pick but will be specified in the ROM thread).
Thanks for the reply. Each time I left the rom on the boot screen for a good half hour, and in one case an hour. I have installed NDT 12.1 and the newer v16 successfully before, so I know what sort of timescales are involved. I also had a go at an earlier Typhoon build. Naturally I used only the recovery sizes specified in each rom's own thread, using versions of MAG/CWM specified there, and Task 29 beforehand.
I have an update to all this, however. Previously I said Winmo installed, but now it is bugging out to all hell. This might fit my "bad blocks in nand" hypothesis, perhaps the files covering the bad area are less critical than the ones in each android build, and Winmo just crosses its fingers and tries to boot anyway!
In any case, if I can get an SD android build running I'll cut my losses and stick with whatever works.
Cheers again, hopefully this random screed of info will help people. Seems to be if all else fails, try winmo.

[Q]windows mobile6.5 to android major problem

after tonnes and days of reading and digging out infos from this forum, i tried as much as i could to follow instructions here:
http://forum.xda-developers.com/showthread.php?t=893948
but then, something went wrong and now my HD2 is not booting up. it is now stucked at the HTC splash screen. i can reboot to get the MAGLDR however.
what i did was, i flashed MAGLDR, as in the first step in the link above.
then i flashed this android ROM:
MAGLDR_Android_2.3.5_Runny.rar
from
http://forum.xda-developers.com/showthread.php?t=1298188
and then the problem started. i'm now searching for a way to recover my phone to the original condition, which was windows mobile. or even better, someone help me solve this and my phone can continue in android. i really need the android because the WolfRam alpha app is not available for windows mobile.
help me please, i'm nearing exams and i need help in my calculus so i decided to take the risk but unfortunately i'm now phoneless and going out of my mind.
thanks in advance
correct spl?
correct radio?
correct partition size?
Radio 2.15.50.14
HARDSPL 2.08
i didn't check the partition, how do i check that?
when you flashed CWM you chose a partition size based on the stated size for the rom you want to flash. it will be in the first post of that roms thread. Use teh nand toolkit, is teh easy way.
EDIT - oh wait, forget that, that rom provides its own cwm, , you have a 265meg system partition, so probably not that, (unless you missed out steps
Download archive with the MAGLDR loader and Recovery from here than unpack its content.
and
Run DAF.exe from MAGLDR_Recovery folder)
still stucked at the black screen with the green HTC words. i tried several times already and it won't start up.
is it possible to wipe the whole thing installed in the phone, and install android to it?
If you flashed magldr then it's all already gone.
I'd try a different rom. Maybe its simply that that rom doesn't like your phone for whatever reason.
Pick a rom
Enter magldr - USB flasher
Flash required partition size using the nand toolkit
Enter magldr option 8 ad recivery
Choose flash zip from SD - choose zip
Probably a stupid suggestion - but have you checked the battery pins? Make sure they're not bent in anyway and that the'yre making contact with the battery.
@samsamuel;
you were right, the ROM hated me :'(
i changed to using the coredroid ROM and everything worked thank you very much!!
@MrFoxx;
i checked the battery pins, and they were indeed bent! but it didn't give me any problem

Need Alittle help

My buddy want's me to flash his T-Mobile HTC HD2 he want android to replace the pos winmobile, but I am getting a headache from the different ways of doing it and coming to dead download links for files needed to do something.
I was trying to find a good tutorial video but even the Videos that are in the **HD2 Android NAND Development - Sticky Roll-Up Thread* are dead. I need the needed links for the files I need and a good and clear cut tutorial. Also What radio version is suggested in "Radio Thread for T-Mobile USA" for his phone.
The T-Mobile HTC HD2 was the recalled one because of the issues with Windows Mobile lagging, frezzing.
Markitzero123 said:
Also What radio version is suggested in "Radio Thread for T-Mobile USA" for his phone.
Click to expand...
Click to collapse
you can ignore the radio for now. its a tmous phone, so the current radio will not give any trouble. one less thing to worry about..
(lets assume you are flashing the paranoidandroid rom - this would require a 150meg system partition - all roms will tell you what partition size to use, it may for example say 150/5 - this means 150 system and 5 cache, , , see below) - get the rom you want, it will be a zip file, dont unzip it. copy it to your sd card.
get hspl4 (my sig)
get the nand toolkit (google for 'hd2 nand toolkit', probably top result)
phone into bootloader with voldown + power
run hspl4 - choose 2.08.hspl - - - double check this, nothing will work with anything but 2.08.hspl
back into bootloader
**
run the nand toolkit
click install magldr
phone will reboot into magldr menu - choose usb flashing
in nand toolkit on teh left select 150 in teh list, and type 5 in eth cache box below
click repartition magldr
when it reboots into magldr menu, choose option 8 - ad recovery - this will start CWM (clockworkrecovery) which was installed when you clicked the repartition magldr button
in cwm choose 'install zip from sd - choose zip from sd' and find teh zip you coppied over
thats it. In theory the phone will reboot and boot into android.
ok
I downloaded
-HD2ToolKit
-HSPL4
-MAGLDR version 1.13
So basicly with your instructions is like this w w w. youtube .c o m//watch?v=Zd9luUWJ34o&feature=fvwrel after MAGLDR is installed
My buddy was thinking about icecream sandwhich is there by chance a list of android for this phone or do you have a suggestion of a either for Gringerbread or Icecreamsandwich
Also another thing is I have a question is Backing up the contacts
go to the nand development thread, and pick a rom. read all of posts 1-3 of any rom you want to try, and make sure you take note of its required partition size.
they are all 'the best rom', so don't ask that question, hehe.
for contacts, if you have it currently synced with outlook, myphoneexplorer works well for me.
ok one more is if the Radio have issues like dropping out etc. if that happens would you suggest of the radio firmware be updated.
you could try SD ROM first then if you like it you can go to NAND, SD ROM is much easier to install, try the link link below it might help.
No matter what his phone needs it because when someone texts him the phone will lock up for 5+ min depending on the message and if there is an attachment. I gave him the choice of flavor of Android and he picked out MIUI Android distro en. miui .com/
Ran into a Snag his phone has SPL-2.10 go to have to downgrade it.
hspl3 or 4 can both handle 2.10, run hspl3, choose 2.08.hspl, done. , dont get caught out following old guides which say you must flash an older rom to downgrade it.
I used this and went with out a issue [GUIDE] Downgrading SPL from 2.10.0000 (stock TMO) to 2.08
My buddy's phone is now android and does not lock up when getting a text message I put the latest MIUI Android on it and they had the install guide on there site.

Categories

Resources