Related
Hi, how are you, guys ?
I'm new to this awesome forum (helped me many times), and I decided to post a new thread because I believe that my situation is pretty serious.
I'm from France, by the way, so I apologize in advance for potential grammatical errors or what. Let's cut it to the chase.
Like most of you, I love new technologies with mobiles, that's why I bought what I consider to be the greatest smartphone on the planet right now, the HTC Leo/HD2.
When I searched all over the internet for tests, reviews about several phones I planned on buying, the HD2 seemed to be the most versatile of them. I was most notably amazed by the fact that the Leo could be a home to Windows Mobile 6.5, Windows Phone 7, Android, among others. So my choice was made.
I wanted immediately to upgrade the OS, and to go into WP7. Several reasons to that, the first being Windows Mobile 6.5 Professional. As it's name indicates, this OS seemed to be made for professional purposes. Plus, and you may guess it, I was really excited to try Windows Phone 7.
I tried to search the easiest and most detailed tutorial on how to upgrade to WP7, and I found this site:
I'm not authorized to post the link to the site, so I'll just tell you that the article is "Download Windows Phone 7 [WP7] ROM For HTC HD2 [Install Guide]", in Aliwaqas[dot]com
Looks serious, right ?
I downloaded the files and followed the instructions.
Aparté: Before that, a week before, I downloaded the latest ROM from the HTC website, because I had a problem with text messages, a problem some of you (or even all of you) must've had: It took way too many time for the virtual keyboard to appear and process with the text message. So I download the ROM, it was the one from 2010-10-11, 3.14.406.2.
Back to the WP7 upgrade, now.
- It was asked to grab MAGLDR, extract and copy the files to my desktop: Done.
- Download HardSPL 2.08 and install it: Done.
After that, my phone completely froze at the white HTC Screen. Every time. I tried Soft & Hard Reset many times, still freezing. I continued, hoping that WP7 would stop the freezing.
- Download the 2.15.50.14 radio and install it. Done.
- Connect my phone to the computer and execute MAGLDR (v1.12): Done.
- Go to the fifth option, "USB Flasher": Done
And there stops my progression. As a matter of fact, it is aked to execute DWI.exe, which I did. However, every time, it finishes with this:
An error has occurred
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (1198)
Error Description: EnterBootloader missing
Info: .\RSPL\BootLoader.cpp (176)
Can anyone help me on this, please ? Because I can't even restart it all with the Hard Reset, because it doesn't work, obviously.
Thank you to all, peace !
Did you have the 3.14 ROM installed prior to running HSPL2, flashing the 2.15.50 RADIO?
fred_up said:
Did you have the 3.14 ROM installed prior to running HSPL2, flashing the 2.15.50 RADIO?
Click to expand...
Click to collapse
Yes I did, sir.
Hi there!
Try something like: http://forum.xda-developers.com/showthread.php?t=914026
Peace.
TheRockSays94 said:
Yes I did, sir.
Click to expand...
Click to collapse
The first thing you need to do is downgrade the WinMo6.5 ROM to either 1.66 (HTC) or 1.72 (branded: T-Mobile, Vodafone, etc). Go to HTC's website and download the ROM from there - you need to use your phone's serial number.
Put the phone into BootLoader Mode (with the phone off, press and hold the Volume Down button then tap the Power button). You will se a 3-colour screen with 'Serial' at the bottom. On the screen you should see SPL 3.03.0000 (this tells that you have the 3.14 ROM installed). Now connect to the PC and the 'Serial' will change to 'USB'.
Run the ROM (just tick the box about ActiveSync as bootloader bypasses the need for it). If you are running with Vista or Windows7 then you need to do this as an administrator. Once this is down you will have either a 1.66 or 1.72 ROM (either will have changed the SPL to 1.66.0000).
You can now run HSPL2 and select 2.08.HSPL.
You can now run the 2.08.50 RADIO.
Now you are prepaired to enter the world of WP7 or Android NAND flashing.
Hi,
Thank you for helping me.
In fact, fred_up, I'm already in SPL-2.08.HSPL. I went in the thread alarien suggested even before posting this one. When I told you that I tried everything I could, it was real. Went into several forums, several languages, but no solutions. I hope this'll be the one. Anyway.
When it is into BootLoader Mode, here is what's in there ("_" means "blank):
PB81100___HX-BC
SPL-2.08.HSPL__8G___XE
_______________0x05
CotullaHSPL______0x30
Even though I'm already at SPL 2.08.HSPL, do I still have to go through the process "3.03 -> 1.66 -> 2.08.HSPL -> 2.08.50" ?
TheRockSays94 said:
Hi,
Thank you for helping me.
In fact, fred_up, I'm already in SPL-2.08.HSPL. I went in the thread alarien suggested even before posting this one. When I told you that I tried everything I could, it was real. Went into several forums, several languages, but no solutions. I hope this'll be the one. Anyway.
When it is into BootLoader Mode, here is what's in there ("_" means "blank):
PB81100___HX-BC
SPL-2.08.HSPL__8G___XE
_______________0x05
CotullaHSPL______0x30
Even though I'm already at SPL 2.08.HSPL, do I still have to go through the process "3.03 -> 1.66 -> 2.08.HSPL -> 2.08.50" ?
Click to expand...
Click to collapse
Not really. But it's worth trying Bro
yeah, use a power mat or buy one of those external battery chargers, but be sure to make an extra battery so you can use it when charging the other one..
I'm afraid I don't see the relation between my problem and your post, coldest~~~...
have you tried running DWI.exe in administrator?
Yes, theroffness, I have, unsuccessfully.
Hi, everybody, thank you for your help
I re-downloaded the WPLEO7 folder, and I reinstalled it, it worked ! I'm now in Windows Phone 7, and it looks gorgeous.
On to the next problem, now
My phone is not recognized in my computer, no matter what way I try to go with. Installed Zune and the Windows Mobile Device Center, I can't do anything. Furthermore, the WMDC doesn't detect my WP7'ed HTC HD2. I want to install TouchXplorer and other .xap files, and I can't seem to find how I could possibly do that.
Anyone, s'il vous plaît ? (means "please" in french, for those of you who didn't know ! lol)
Again, Thank you to everybody who wanted to help me !
Follow this
http://forum.xda-developers.com/showthread.php?t=912218
I did it, thanks for the help. However, ever since I installed chevronwp7.cer, my computer can't seem to recognize my phone anymore. I have all the related software, but I can't go farther.
Also, when I put an SD Card on my phone, it can't switch on !
I honestly don't know how to deal with that, can someone do ? Thanks.
I just solved the problem by my own. But I still have this problem with SD Card. When I put it on my HD2 (at that time, the phone is off. When it is on, it isn't recognized by the phone), I can't switch it on. I obviously need space because I can't even send some damn text messages.
Hi!
The touchscreen of my phone almost doesn't work. I've read many topics about this in different forums and maybe a solution would be to reinstall all from 0 (resetting the phone with that yellow button when you revome the back doesn't work anymore).
So, I want to try to install android hoping this will solve the problem. If not, my phone will be a thin brick in a drawer.
Since the touchscreen is not working correctly, I can't go to see the details in the menu.
The phone was flashed once and currently has a rom called BSB beast 6 and when I turn it on, this red numbers appears:
2.10.50.26
15.39.50.07u
2.11.86834 8g
Current OS is Windows Mobile 6.5
I believe android will work with the current rom without the need of installing another one before, right?
Would recommend me one rom (android NAND) to put? because I saw a lot in thread here and I don't really understand what the differences would be. I just want the phone to work
I hope this is enough information
Thanks a lot!
If you want to flash Android what you need to do is...
Make sure you have 2.08.HSPL (I'm assuming you do as you have a custom ROM).
Then flash the newest radio (2.15.50.14)
Flash MAGLDR
Flash a NAND ROM of your choice.
Though I doubt that will fix the problem. Your digitizer is probably gradually dieing. You can easily get it fixed for about $80.
alc112 said:
Hi!
The touchscreen of my phone almost doesn't work. I've read many topics about this in different forums and maybe a solution would be to reinstall all from 0 (resetting the phone with that yellow button when you revome the back doesn't work anymore).
So, I want to try to install android hoping this will solve the problem. If not, my phone will be a thin brick in a drawer.
Since the touchscreen is not working correctly, I can't go to see the details in the menu.
The phone was flashed once and currently has a rom called BSB beast 6 and when I turn it on, this red numbers appears:
2.10.50.26
15.39.50.07u
2.11.86834 8g
Current OS is Windows Mobile 6.5
I believe android will work with the current rom without the need of installing another one before, right?
Would recommend me one rom (android NAND) to put? because I saw a lot in thread here and I don't really understand what the differences would be. I just want the phone to work
I hope this is enough information
Thanks a lot!
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showpost.php?p=12105680&postcount=1
I have been trying to help a friend install Android on his HD2. We actually had it working but didn't know anything about APN so we couldn't figure out how to get the 3g data working. Ultimately I wound up flashing it back to Windows, and then figured I would try flashing Android again after that. Unfortunately we are now stuck with Windows because it seems that we cannot flash MAGLDR. When we try, the progress bar sits there, stuck at 0%.
I had downloaded the image from T-mobile's website here:
http://www.t-mobile.com/wmupgrade/
But I found this post archived:
http://forum.xda-developers.com/archive/index.php/t-612580-p-78.html
It has some information stating that "If you cannot reflash and you stay at the 0 percent screen, then another solution is to flash first an original stock HTC ROM (1.66). Enter bootloader, connect to PC/Laptop and flash this ROM. When that has been succesfull, you can then reflash Artemis ROM."
Unfortunately the ROMs they are referring to (1.66, 1.72, etc.) appear to be non-US ROMs. I found the 1.72 website for the UK:
http://www.htc.com/uk/SupportViewNews.aspx?dl_id=936&news_id=638
But the site specifically says not to use that ROM to flash a T-Mobile(US) HTC HD2 as doing so can have unintended consequences. Is this true even when using HSPL? As part of the Android process we obviously had to install HSPL 2.08. I thought the point of HSPL was that you could always flash a ROM and even if the ROM didn't work, you will drop into the bootloader where another ROM can be flashed. So basically you can't brick the device any longer since you can always access the bootloader and flash a new ROM.
It seems people had success flashing one of those 1.66/1.72 ROMs and then installing some other ROM. I tried using the US ROM and it flashes just fine (doesn't get stuck at 0 percent) but when I try reflashing MAGLDR it just gets stuck. I don't intend on booting up and using the UK ROM...I'm just curious if I can flash that on this US based phone and then try to flash MAGLDR again to see if it works. Is this a good idea?
Oops...didn't mean to post this in the dev forum! Moderators please feel free to move this to Q&A.
flash any non tmous compatible cooked rom to a tmous and it wont boot past the RGD screen.
flash any STOCK non tmous rom to a tmous and it is bricked, full stop, dead. The radio contained in non tmous roms is permanently fatal to tmous phones.
This is true regardless of HSPL or any thing.
Simply put, you should never flash any rom where the chef doesnt explicitly state tmous compatible.
I havent used artemis, though glancing through the first post i see it is is based on the Leo S 3.14 rom, which is for the regular hd2 (LEO S means regular). What it doesnt make is any mention of tmous compatibility, so unless someone knows for certain i'd stay away from it.
Is this a good idea?
Click to expand...
Click to collapse
not at all.
If your aim is magldr, put phone into bootloader, connect usb, run hspl4, choose 2.08.hspl, your radio is already OK, because if it wasn't your phone would already be bricked (all tmous radios are ok for magldr by default), return to bootlaoder, flash magldr.
EDIT - Oh and once you are on android, you dont need to worry, all roms are tmous compatible.
Great thanks for the info...I definitely don't want to brick his phone with an incompatible radio. As for loading HSPL 2.08 that is precisely what I did. I flashed Windows back on there, then flashed HSPL 2.08, then tried to flash the same radio. It got stuck at 0% so I pulled the battery and tried again but it was a no go. So then I just tried MAGLDR and it also got stuck.
At this point I read the thread about flashing Windows back so I tried that again and am still unable to flash MAGLDR. You think I should flash HSPL again and then it will work? I think I used HSPL 3...so maybe I need to try HSPL 4.
Sent from my Evo via the xda app.
Also I don't plan on using Artemis...I just found that post while trying to fix the 0% issue while flashing. I had installed prj clean desire and he really liked that. He isn't too techie so I don't worry about him wanting to flash new ROMs to try them. As long as it is not Windows mobile he is happy. Unfortunately he is stuck on that for the moment.
Sent from my Evo via the xda app.
hanging at 0%, , two possibles, either you accidentaly chose 2.08.0000 instead of 2.08.hspl when you ran hspl, or your computer is timing out, in which case dont touch the phone, reconnect to a different usb port and run the flash again.
Also, if you flashed that http://www.t-mobile.com/wmupgrade/ 3.14 rom from there, then you already have the latest radio and dont need to change it.
Oh snap you might be right...I might have chosen 2.08.0000 and not the HSPL version. I seriously doubt the computer is timing out because it works fine with that same USB port to flash the Windows ROM. I bet you're right and I just flashed the wrong SPL! I'll get his phone and just bring it home with me soon. He can use his old phone for a day or two while I iron things out.
I'll try to remember to login from my computer and hit the thanks button. I don't see any way to do that in this app...
Sent from my Evo via the xda app.
gamblor01 said:
it works fine with that same USB port to flash the Windows ROM.
Click to expand...
Click to collapse
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settings (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probably also need the "google usb driver" if its your first time with android on that pc,, google them.)
Flashing from bootloader needs that box ticked, hence the slightly confusing instructions in flashing guides to 'get an activesync connection', it doesn't really mean a sync connection, but that those drivers have grabbed the usb.
samsamuel said:
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settinsg (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probly also need the "google usb driver" if its your first time with android on that pc,, google them.)
Click to expand...
Click to collapse
Yeah that causes a different error. Something about USB init failed and it complains about a source file called rspl.cpp or something like that. I had to fix that issue before I could ever install the prj ROM the first time. It's ActiveSync 4.5 though (I'm running XP on this partition -- I don't buy any Microsoft products any longer -- or Apple for that matter), but the steps are essentially the same. You just have to prevent it from establishing USB connections.
@samsamuel
Thank you so much for all of your help! I got his phone back today and it looks like the Windows ROM flashed 2.10.0000 on there. I launched HSPL3 again and this time made sure that I selected 2.08HSPL. It flashed right on, as did MAGLDR 1.13, and ultimately the prj clean Desire ROM. It's back to working again and we'll plug in the APN settings when I give it back to him tonight. Victory!
gamblor01 said:
Victory!
Click to expand...
Click to collapse
heh, a happy ending, nice.
Hello..a friend of mine gave me a HD2 to fix, said it can't load anything. As I own a HD2, I took it just to see what's wrong. I own an Asian HD2, and everything is fine, I tried various ROMs..both Android and WinPhone, settled at Hyperdroid. Anyway, I have no idea where the heck the other HD2 is from, neither my friend has.
So, the phone had nothing in it and was stuck at the HTC logo, so I loaded into bootloader and saw HSPL 3.03. Then I changed it to 2.08 in order to install MIUI android. Then I installed MAGLDR. The issue occured when I went to install CWM. I loaded the 150M partition at USB Flasher, it was doing all fine until it became stuck at "reset now...!". So I just took the battery off, and tried to load into AD recovery. While it loads to 1, then it shows "fatal hit" error. I tried a lot of times including task 29, but it persists. Was the phone bricked from earlier ? Something like heating issues I assume. Anyway, I tried to install my phones stock WinMo rom to it from SD but it also gives error like failed, not allow etc. The both phone looks the same, under the battery hood of my phone, it's written HTC HD2 T5858. On the other one, nothing. Rest visuals are same.
So is there any way I can bring this anonymous HD2 to life ? I think it's almost dead but still if there's any way you people can come up with. I'm using a 2GB Sandisk MicroSD and the phone's S/N is HT01CNW04979 ; if that helps to sort out the phone's identity. Your help is much appreciated. Thanks
http://forum.xda-developers.com/showthread.php?t=1520439
this is a thread I created 3 days ago....me, another user, and now you...
our hd2s are going to diee D: stop joking, I (and toher guys) think that is hardware related....like in my case....but I don't really know what's the problem, just guessing....take a look to my post
True that. Only the difference is, it's happening to me during clockwork recovery installation. And I don't know where the heck is the phone from so that I can load custom WinMo lol. My own HD2 is doing just fine by the way.
http://imageshack.us/photo/my-images/263/87604378.jpg/
http://imageshack.us/photo/my-images/412/59177201.jpg/
Hello;
It's been 5 days that i'm reading about this problem, and i didn't find any reliable solution, so i'm posting it here:
I've juste flashed my third HD2 with a new radio (2.15) an android NAND rom (the Nexus HD2 ICS), and since then i can't get into the bootloader mode, i've tried the vol -, the adb reboot bootloader, and nothing works.
i want to access the bootloader to downgrade the radio to the 2.12, and without the connection to usb via activesync, i can't do it. i just can access the MAGLDR menu when it says WPH not installed (i think it's the source of the problem) and then install roms.
So if anyone can help me changing my radio without the bootloader or how to get it back, i'd really appreciate it.
Vol down works perfet on WM6.5 and on android, and i've tested it with the key tester in Recovery mode
No answer?? no one raising the finger?? So basicly there's no solution for my problem!!!
Aaaaah did you change the boot source looks like Its trying to boot windows mobile and you have android installed btw we have no fast boot support in magldr. Change the boot source under services and technically it should work
Sent from my HTC Desire HD using XDA
I restored the boot source to Android from NAND, and it just simply avoids the "WPH not installed" message on Magldr, nothing to do with the bootloader who is still missing... anyway thanks for the tip.
Lol if your bootloader is gone your phone would be bricked!
Sent from my HTC HD2 using XDA
Big-amine said:
I restored the boot source to Android from NAND, and it just simply avoids the "WPH not installed" message on Magldr, nothing to do with the bootloader who is still missing... anyway thanks for the tip.
Click to expand...
Click to collapse
I don't think your alone because I've read a similar thread a while back but I can't seem to find it again. Basically it was reported to be an issue for many users who had used HSPL4 to flash HSPL or something like that. I did and can still access the bootloader but others have had problems. I don't think it should be something to be too concerned about unless you want to restore back to stock WinMo to send it in for repairs or something or if you want to change bootloader from MAGLDR to cLK. Flashing the radio as you wanted to do can be useful but I doubt there's a significant difference between these. And whenever anyone mentions 'do a Task29 to be safe' it's just BS. Task29ing is unnecessary in most situations but people have simply got into the habit of doing so every time they flash a ROM (which can actually be bad for the phone as it can eventually lead to bad blocks from what I've read) so whenever people ask for help their first response is Task29. Basically, I would say that you shouldn't worry about it too much