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.
Related
Hi all,
This is my first post in this forum. Just got my HD2 yesterday & immediately set about installing a new ROM. I installed HSPL without any issues, but I'm having problems installing a new ROM. I've downloaded a couple in .exe format, synced up the phone to WMDC in Win 7, then when I start the exe file everythings fine until it starts to install, then the 4 colurs come on to the phone, and then the USB connection drops so WMDC isn't connected, then I get the error 266 (or 226). I used to have a touch diamond that did this, but I can't remember how you get the connection to remain whilst uploading the new ROM. I've had a look through the forum, but can't find the answer. Can anyone give me some ideas?? Does the phone need to have certain settings applied to it before flashing?? I'm not exactly a noob to flashing ROM's, but can't work this one out!! Thanks all.
just extract the exe, rename *.nbh to LEOIMG.nbh, put in ur microSD root, enter bootloader, press power button when u asked to do so. soft-reset when complete. feel free to pm me n i will guide u.
SD card method is the quickest way to brick your phone...
I use W7 64bit with WMDC and have never had an issue. Custom ROMs comes as an NBH file and tend to have CustomRRU.exe with them to run them. Run the EXE as an admin and you shouldn't have any issues.
Obviously check that when in the bootloader it does say SPL is 1.42.HSPL
When I flash a ROM, it turns the phone off (Windows knows that as it makes a sound) and then when the bootloader comes back up it says USB, Windows makes a sound for plug in and it starts.
EddyOS said:
SD card method is the quickest way to brick your phone...
I use W7 64bit with WMDC and have never had an issue. Custom ROMs comes as an NBH file and tend to have CustomRRU.exe with them to run them. Run the EXE as an admin and you shouldn't have any issues.
Obviously check that when in the bootloader it does say SPL is 1.42.HSPL
When I flash a ROM, it turns the phone off (Windows knows that as it makes a sound) and then when the bootloader comes back up it says USB, Windows makes a sound for plug in and it starts.
Click to expand...
Click to collapse
Hi, I'm using the same OS. I've tried running as admin but it still drops connection. The SPL is 1.42.HSPL. It just starts the update, then I see the phone disappear from the connected devices, then WMDC shuts down & a few seconds later the error message comes up??
you started flashing this fast only after one day of use
You don't need WMDC open - just close it once it says you're connected
The run the file and it should work.
As mentioned, why are you flashing it out the box? It's always best to get to know the device as it might just work as it is...perhaps try a stock ROM if you're not already using the newest one and go from there
EddyOS said:
SD card method is the quickest way to brick your phone...
Click to expand...
Click to collapse
I agree. not that there is anything technically unsafe about it, but unless you are fully aware what you are doing it's so easy to flash the wrong thing.
example,you flash a 1.66 stock rom from sd card but don't like it.you goo to change it but get a fail. why? because flashing stock from sd card also overwrites the spl.
no problem you say, I'll reinstall hspl.... only you can't because hspl needs spl 1.4 to instal and your 1.66 flash installed spl 1.6
worse still you instal one of the test roms from t mo us that are 2.0x which can't be downgraded even by gold card and you are stuck with spl2 until the geniuses that are the hspl team release hspl2.
just a thought...are you running as administrator? right click, run as administrator
samsamuel said:
I agree. not that there is anything technically unsafe about it, but unless you are fully aware what you are doing it's so easy to flash the wrong thing.
example,you flash a 1.66 stock rom from sd card but don't like it.you goo to change it but get a fail. why? because flashing stock from sd card also overwrites the spl.
no problem you say, I'll reinstall hspl.... only you can't because hspl needs spl 1.4 to instal and your 1.66 flash installed spl 1.6
worse still you instal one of the test roms from t mo us that are 2.0x which can't be downgraded even by gold card and you are stuck with spl2 until the geniuses that are the hspl team release hspl2.
just a thought...are you running as administrator? right click, run as administrator
Click to expand...
Click to collapse
Didn't know that, glad I have HSPL on my phone now!! lol
lots don't and that's what makes sd flashing dodgy. in the case of 1.6 it can be downgraded with a 1.4 spl stock rom.its just a pain. but 2.0 spl can't. check out the horror stories in my sig.
Yeah read about them, I nearly bricked my phone using the SD card method the first time I flashed but luckily the WMDC flash with my stock ROM got me back to normal!
I was trying to flash the stock 1.66 ROM, but it still disconnected. I have 1.43.206.4 WWE at the moment. The reason for flashing straight away, is usually the stock ROM updates are to improve / fix previous issues. This is why I wanted to start with a stock ROM & maybe move onto a cooked ROM at a later date. Does it make any difference when starting from an .exe file instead of RUU? Do you have to change something on the phone itself to allow it to stay connected?? cheers everyone for your comments.
run the exe as administrator, the phone should restart into boot loader (three colored stripes) and then flash.
samsamuel said:
run the exe as administrator, the phone should restart into boot loader (three colored stripes) and then flash.
Click to expand...
Click to collapse
Just tried it again & still no joy. It starts, the phones switches off, thats when it loses connection, then the bootloader appears, then about 10 secounds later it says error 266 connection lost. Still stumped???
Sounds like the device isn't reconnecting with the PC once in the bootloader - try another one...
with the phone in boot loader unplug the usb and plug back into a different port. preferably a port directly on the motherboard (round the back) not through a usb hub or slot in the case.
Sussed it now. I'm a mac user using Win7 using VMware fusion. I think it was this that was causing it to not detect the phone once it had started flashing the ROM. I tried it on my work laptop running XP & voila, it flashed immediately. Thanks everyone for your comments - no doubt I'll be posting a few more questions soon!!!
ah good stuff.
todays lesson ? put all the system info in the first post!
clemo71 said:
Sussed it now. I'm a mac user using Win7 using VMware fusion.
Click to expand...
Click to collapse
Ahhh... yes, that's the kind of non-standard setup that would make sense mentioning right away indeed. Everything that touches hardware level is rarely friendly to emulation, virtual machines, resource sharing and so on...
1st lesson - use a PC!!! POW!! lol
Ok.....next question. I've tried to flash a rom using the customruu file, but all it does is open up the contents of that file. I'm using XP Pro. Any ideas why anyone???
Since my HTC HD2 from Tmobile the SPL is 2.1
Is it possible to use a cooked rom without HSPL? Or is there another HSPL 2.1 hack.
Also, I searched the forum on downgrading it, which involves microsd. I'm not sure how to do it, anyone care to explain it to me? Thanks ^^
As long as you have one of these SPLs currently on the device - SPL 1.42.0000, SPL 1.62.0000, SPL 1.66.0000, SPL 2.07.0000, SPL 2.08.0000, SPL 2.10.000 you can flash HSPL3.
And you should always have hspl when flashing cooked ROMs
Dude I'm pretty sure there is no spl 2.1....
Sent from my HTC HD2 using XDA App
It's actually a 2.10.000
http://forum.xda-developers.com/showpost.php?p=6891358&postcount=1893
So I download HSPL3 and do it? Edit: For installing HSPL3, do I have to enter the tri color screen than do it or no? And also, is HSPL3 compatible with TMOBILE?
Also, how do I find out of it's a LEO512 or LEO1024? Like how does it know the HSPL is compatible with me HTC HD2 Tmoible? I know the SPL is 2.10.000
But I read that there is 3 different kind of Leo. So I dont know if it will be compatible
Edit: Let's say I bricked it, how would I enter boot loader?
Bump. need help ASAP ><
To confirm the instruction
1. Run HSPL3 (Do I have to be in the tri color screen in order to install it?)
2. Run the rom I want using CUSTOMRUU (It's a Miri HD2 WM6.5.X (23133) V18) (Do I have to be in the tri color screen? Or can I just plug in the phone and run the custom RUU?
3. After I flashed it, and I want to install Android on it, do I have to do anything about radio version or no? < I am asking this because on my current build, I hear robot voices... After I install the V18 everything should be fine and I don't have to worry about the radio right? Thanks again ^^
Bump! I really need help >< I really want Android on this phone and I keep hearing robot voice when calling..
I don't use the Miri ROM but I would search his thread for all instances of "Android" and see what other users are doing. Sorry I couldn't help more.
Dude... so there's a post in this section, actually one of the first ones in the area... stickyed close to the top (4th thread actually), that talks about EVERYTHING you just asked... and it's specificly for our 1024LEO (T-Mobile HD2)
give it a glance... it also provides the links to HSPL3 and instructions on how to install it.
I ran though this the 2nd day I had my T-Mobile HD2, first phone I've EVER customized, and it's all really straight forward & easy.... just be sure to RTFM
Also, as a bit of help....
when installing a ROM, the RUU will reboot the phone into the Tri-Color to perform the flash... however, if it's the first time the phone has been plugged into the computer while at the TRI-Color... the flash process will time out before the computer finishes installing the drivers required to see the device.... so I suggest going to the TRI-Color manually and pluging the phone into the computer... let the computer install the drivers (when finished, you will see the words change from SERIAL to USB in the white area of the Tri-Color screen) then run the ROM install. The RUU can be run both from the OS and from the Tri-Color
Oh, thanks!
Last question. Currently I have a official ROM from HTC, and when I boot up android, everything works fine except that when I make call I hear a robot voice.
Will flashing to custom rom fix this problem? Or do I have to update the radio? :|
nitrogen618 said:
Oh, thanks!
Last question. Currently I have a official ROM from HTC, and when I boot up android, everything works fine except that when I make call I hear a robot voice.
Will flashing to custom rom fix this problem? Or do I have to update the radio? :|
Click to expand...
Click to collapse
Official T-Mobile ROM? it's possible... both my Fiancee and I have the HD2, I flashed to the Energy ROM, and she used a kitchen and made a custom version of the T-Mobile ROM... when running Android mine works fine on voice, she however gets the robot...
we both flashed to the radio to Leo_Radio_2.12.50.02_2
I recall seeing something about formatting the SD card and trying again to fix the robot voice issue... but I would suggest doing some searches in the HD2 Android Development section first (found in the "other" HD2 section )... I know a lot of people were reporting that issue, so I'm sure someone has "The Fix" for it.
last bit... remember to ALWAYS check if a ROM is TMOUS supported before you flash... getting a ROM from this section is a safe bet (and i think a lot of the custom ROM cooks are starting to cook the Android loader in... I know the Energy ROMs have it) but when you start going to ROMs in the Android Development section made specifically for running Android you need to make sure.
Hi,
I've got some major problems with my HD2. First of all, it was running well. Last Saturday, I wanted to update my NAND TyphooN_CM7_v2.5 to TyphooN_CM7_v2.8.1. I opened CWM and made a backup. Afterwards, I installed the 2.8.1 version and after the reboot, I restored the backup(I think that's my mistake).
After that, I checked the build-version - it was still 2.5..
A little confused, I went to buy a BD. I recognized in the car, that the wake up bug happened again and I resetted the phone. Then, it worked fine.
Back at home, I took my phone in order to reinstall the 2.8.1 version. Suddenly, the HD2 only showed a clear white screen. I didn't boot and MAGLDR didn't appear either. So I tried to reinstall MAGLDR - didn't work(sometimes it's the 270 error, then it's the 262..)
What I've done till today:
-Tried to reflash HSPL
-Hardreset
-Tried to flash a tmo original WM Rom via USB(262&270 error)
-Tried to flash a tmo original WM Rom via SD =>No Flash Screen appeared
I'm kinda stuck cause the damn phone won't flash...
The usb connection is functionnable(the HSPL installer recognizes the HSPL version on the phone)
Hope you can help me
Greets
Erbse
Did you use s USB Micro SD card reader to copy tbd leoimg.nbh file to your SD card, and are you sure your SD card is formated Fat 32? Also go to your device manager in the control panel of hour computer while your BD2 is connected via USB and in bootloader. Make sure it says HTC USB Sync.
Yep - I'm sure about everything you mentioned
What to do next? The previous owner assured that the phone's got t-mobile de branding..
I guess then it is necessary to use a t-mobile Rom..
I'm quite confident, that it's not completely bricked - I can still enter the bootloader and the hard-reset mode
Give me some ideas
Erbsenkönig said:
What to do next? The previous owner assured that the phone's got t-mobile de branding..
I guess then it is necessary to use a t-mobile Rom..
I'm quite confident, that it's not completely bricked - I can still enter the bootloader and the hard-reset mode
Give me some ideas
Click to expand...
Click to collapse
Yes if you want to go back to stock and start over this is a very good idea. If you have the T-Mobile Leo with 1024MB RAM then yes only flash the T-Mobile official ROM to your HD2 as the any other official ROM will either brick your HD2 or the ROM will not function properly. Most of the time they brick a T-Mobile HD2 though as they have radios with x.xx.51.xx with them or a radio like these 2.04.50.xx or 2.05.50.xx. Any of those radio versions will brick a T-Mobile HD2
Also this may or may not help but I suggest it as it might help you out. Go to windowsmobile.com/getstarted and download the latest version of ActiveSync or Windows Mobile Device Center depending on what Windows your computer uses. The lateast releases have updated USB drivers and sometimes this is the problem when people are having issues flashing via USB.
You also had said you have tried the stock ROM already so you probably do not have HSPL anymore unless you got HSPL to reflash. So you will either have to flash a stock ROM or flash HSPL again so you can flash a custom ROM.
T-Macgnolia said:
Yes if you want to go back to stock and start over this is a very good idea. If you have the T-Mobile Leo with 1024MB RAM then yes only flash the T-Mobile official ROM to your HD2 as the any other official ROM will either brick your HD2 or the ROM will not function properly. Most of the time they brick a T-Mobile HD2 though as they have radios with x.xx.51.xx with them or a radio like these 2.04.50.xx or 2.05.50.xx. Any of those radio versions will brick a T-Mobile HD2
Click to expand...
Click to collapse
As far as I know, it's the 512 MB Version - a friend of mine made me check it the first day I got it
T-Macgnolia said:
Also this may or may not help but I suggest it as it might help you out. Go to windowsmobile.com/getstarted and download the latest version of ActiveSync or Windows Mobile Device Center depending on what Windows your computer uses. The lateast releases have updated USB drivers and sometimes this is the problem when people are having issues flashing via USB.
Click to expand...
Click to collapse
Already done
T-Macgnolia said:
You also had said you have tried the stock ROM already so you probably do not have HSPL anymore unless you got HSPL to reflash. So you will either have to flash a stock ROM or flash HSPL again so you can flash a custom ROM.
Click to expand...
Click to collapse
The bootloader still says
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
Ok you still have HSPL 2.08 wich is good as this means you can flash a custom ROM if you want to. Bit be advised that seeing as you have the 512MB version if you use any 3.14 official ROM or 3.14 based custom ROM then you will have to have SPL 3.03.0000 or HSPL 3.03 or you will incounter memory problems, also you will need a Radio version with a 50 in it. bit yhis is only if you are going to use Windows Mobile, if you are going Android don't worry about this.
Now what all have you tried sense your first post, and have hou tried a task 29?
I tried
-several USB ports
-AV and firewall off
-tried to install the other HSPL version(HSPL3 installer)=>Installer says "successfully done"..but there's no change in the bootloader
What's next?Task 29?
Btw: My battery LED doesn't turn green I charged the HD2 the whole night and in the morning, the LED's still orange..Looks like the first MAGLDR. With the first version, the charging didn't work when the phone was off. I had to take the battery and reinsert it. It's like that at the moment...
You want to make sure you have atleast a 50% charge or more on your battery cause you do not want your battery to die whild you are flashing anything as it will almost assuredly lead to your HD2 being bricked.You are right about MAGLDR too and that your HD2 has to be on to charge. Task 29 will delete what ever is in your NAND memory of your HD2 and reformat the NAND memory also. It is always a good idea to run a task 29 when you are going to flash a new ROM of any kind. Be advised though Task 29 will remove MAGLDR from your HD2. Here is a link to Task 29 so you can learn more about it anx download it if hou want to give it a try.
http://forum.xda-developers.com/showthread.php?t=644781
Thx buddy
But how can I be sure about my battery? The HD2 doesn't show me the battery status and I can't recognize it because the LED doesn't change
Erbsenkönig said:
Thx buddy
But how can I be sure about my battery? The HD2 doesn't show me the battery status and I can't recognize it because the LED doesn't change
Click to expand...
Click to collapse
That is a very good point as you have to have a ROM of some kind on your HD2 to get what percentage oc charge your battery has. I also do not know of any software you can get for you computer that can give you this information, but that is not to say it does not exist. You can try googling it to see what you can find. But the best bet is for you to boot up into MAGLDR and pmug your HD2 up to your wall charger and lrt it charge for 45 minutes to an hour and gou will have enough charge then.
MAGLDR doesn't start - the phone's stuck in that screen
The phone's been charging for about 90 minutes - I'll now try task 29
Task29 doesn't work either..
ERROR 262
Somewhere, there's a problem with the connection..but I can't see where
EDIT: I reinstalled the WMDC drivers - still the same error..
EDIT2: Same error with the original windows update drivers
Finally, I managed to use the SD card..
But then, the flashing failed
What now?
EDIT: After a couple of minutes, I pushed the reset button..The bootloader's still there The bootloader says still the same things as mentioned earlier and the usb connection is still working
I know this might be a redundant question, but are you absolutely sure you have the correct stock ROM for your HD2? Also are you 100% positive you have a T-Mobile Leo with the 1024MB ram and not a EU model with 512MB ram?
No problem buddy
I used this german website:"[Upd.19.02] Downloadübersicht HTC HD2 ROMs ( orig. & Betreiber ), Radio und Hotfixes and I took the first T-mobile rom(as it was an advice of an user)=>Auslieferungsrom(means like the rom the phone had when you bought it)
And I'm sure about the 512MB version - it's definetely a EU version!
Erbsenkönig said:
No problem buddy
I used this german website:"[Upd.19.02] Downloadübersicht HTC HD2 ROMs ( orig. & Betreiber ), Radio und Hotfixes and I took the first T-mobile rom(as it was an advice of an user)=>Auslieferungsrom(means like the rom the phone had when you bought it)
And I'm sure about the 512MB version - it's definetely a EU version!
Click to expand...
Click to collapse
OK so your phone looks like the picture of the one I attached below. Does the Duesch Telecom(sorry if I did not spell that right but I know they are the mother company of my carrier T-Mobile USA) not have a website you can download a official ROM from? Sorry I am still translating the stuff on the site you linked lol
Yeah, it looks like that. First, I downloaded the 3rd t-mobile Rom(directly from their website). But then a user told me to take the first version..
So you down;loaded this ROM and flashed it correct.?
Auslieferungsrom/Deutsch 1.43.111.2 2.04.50.22
And you had wanted to flash this one but was told not to correct?
01.02.11 / Deutsch 3.14.111.1 2.15.50.14
Who is your carrier by the way?
Edit: Could you not use one of the ROMs from here
I extracted the "Auslieferungs-Rom" and copied the *.nbh on the SD Card. I renamed it and tried to flash it - got to error message from the picture above.
My carrier is t-mobile de
I'm not sure if I can use a Rom from the HTC website When I use my SN, the website says "Sorry, this software download is not suitable for your device"
PS: Is it possible, that the flashing failed because of the different Radio versions? As far as I know, the version 2.15.50.14 is installed on my HD2. The "Auslieferungs-Rom" is mentioned with an other version..
EDIT: On the german HTC website, my SN only works for T-Mobile Roms.
Hi I have an HTC HD2 and decided to try it with Windows 7. I followed instructions and installed a stock Windows ROM (from HTC) - all fine. When I went to install the new ROM, all was well until I got to running the RUU (for MAGLDR 1.13). The process hung on 0%. I tried again, same thing. I tried MAGLDR 1.11 - same thing. After several attempts I got a bit suspicious and decided to re-run the HTC ROM update - it hung on 0%!
It seems like I can't update anything! Has anyone seen this or have any ideas what I can try?
you either don't have hspl installed. look in bootloader, wazzit say?
or
dont try flashing from running windows mobile, , enter bootloader manually, connect USB and THEN run your flash.
Hi, thanks for answering, but I am afraid none of that helps. I have HSPL 2.08 installed and I get the same result whether I use WMDC or USB connection. Do you know how I can remove HSPL? Apart from the WM 6.5 ROM, that is the only other thing I have installed on the phone.
"I have hspl 2.08 installed".... does it say "2.08.0000" or "2.08.hspl"?
I'm double checking because half the people that declare they absolutely, totally and definitely have "hspl 2.08 installed" actually have 2.08.0000 which isn't hspl.
That's fine, yes it is 2.08.0000... I installed it specifically as part of setting up for Windows 7.5 But is says SPL-2.08.000000 !
OK NOW I definitely have it installed and I shall try again before confidently posting anything ;-)
And now of course it all works - thanks!
hehe, you wont be the last to make that mistake,, you probably wont be the last THIS WEEK.
!!Take note, flashing newbs reading this!! always always double check visually in bootloader what your hspl status is. Don't just assume its what you think it is, half the time it isn't. If you get suck at 0% its nearly always this problem.
I bought a used HD2 running CM10(NexusHD2-JellyBean v1.3a). I want to run WP7.8 on it so I looked up the ways to do that. Tutorials like http://forum.xda-developers.com/show...postcount=1193 say to flash a stock winmo6.5 rom before moving to WP7. I tried to do that by trying to flash RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship. The normal RUU Updat Utility came up with lots or errors, but mostly connection or no response from device issues. So upon further reading i found out an alternate way to go about it by renaming the nbh and putting it in an sd card. I used 2GB microSD card and tried to flash it. But mid-way it stopped and upon reboot it said software update failed with a triangle. I went into the 3-color screen and there the message was present as well with two other messages microp led and microp touch. I tried the sd flash method again but it stopped by giving a not allow 00028002 error every time. I flashed HSPL 2.08.000 from the HSPL4 executable and Android booted up again.
i also tried RUU_Leo_S_TMO_UK_3.14.110.1_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship_2 but the same update error(266, i think) came up
Can i now go to a stock rom and then to WP7?
Thanks, in advance
Device details:
Boots with purple "stick together" logo(Weird, google search says this is tmobile america slogan yet this device is not US)
S/N:ht04anw01415
HTC HD2 T8585 P81100 (from the back)
Anyone?
follow the links below & your ready togo
mengfei said:
follow the links below & your ready togo
Click to expand...
Click to collapse
thanks for the reply but i want to go back to the stock rom which it seems i'm unable to do. i tried the usb flash and microsd flash methods with both RUUs. if i get to stock then i can proceed to wp7 with a clean slate. ATM i've flashed energy rom (Energy.Leo.29022.Sense2.5.Reference.Jul.05) with radio 2.15.50.14 in an attempt to see if doing this would help flash stock rom but no success.
IF you want WP7 no need to go back to stock ROM, I guess you haven't take a look at this link
http://forum.xda-developers.com/showthread.php?p=25781675#post25781675
once you have Magldr in your HD2, next steps would be easy as pushing a button
got windows phone 7.8 on it, thanks. But what if i want to later on return to stock rom? even when i was trying to wipe with task29 it was giving same error 266 and as of yet i haven't successfully flashed anything by the RUU method.
HD 2 Problems Win7
hi guys
Yesterday I tried to install HD2 WP7 ... and install a new Radio ROM my phone off, and since I did not start .... no reset button under the battery cover does not work .... it happened to anyone of you?? ... I had previously installed the official 6.5
Ralph79 said:
hi guys
Yesterday I tried to install HD2 WP7 ... and install a new Radio ROM my phone off, and since I did not start .... no reset button under the battery cover does not work .... it happened to anyone of you?? ... I had previously installed the official 6.5
Click to expand...
Click to collapse
Nope but then again, i never had to flash another radio. Try to follow the tutorial in mengfei's signature and if it doesn't work create a separate thread for others to weigh in.
geforceonline said:
Nope but then again, i never had to flash another radio. Try to follow the tutorial in mengfei's signature and if it doesn't work create a separate thread for others to weigh in.
Click to expand...
Click to collapse
If you want stock windows mobile (with HSPL) > Use HSPL to flash windows mobile using the RUU.
If you want stock winmo AND stock spl > Install winmo using HSPL, then use HSPL package to uninstall HSPL (i.e. install stock SPL).
That's the only way I can think of since you're getting lots of errors doing anything without HSPL.
Marvlesz said:
If you want stock windows mobile (with HSPL) > Use HSPL to flash windows mobile using the RUU.
If you want stock winmo AND stock spl > Install winmo using HSPL, then use HSPL package to uninstall HSPL (i.e. install stock SPL).
That's the only way I can think of since you're getting lots of errors doing anything without HSPL.
Click to expand...
Click to collapse
I presume you're talking about the regular USB>3-color screen>RUU(on pc) method. Well, i've been doing that for stock roms and other stuff(splashes, etc.) too but i almost always seem to get error 266 update error.
geforceonline said:
I presume you're talking about the regular USB>3-color screen>RUU(on pc) method. Well, i've been doing that for stock roms and other stuff(splashes, etc.) too but i almost always seem to get error 266 update error.
Click to expand...
Click to collapse
If you don't have HSPL, you will get an error when trying to flash almost anything.
You said you flashed HSPL, but in fact you didn't
geforceonline said:
.. I flashed HSPL 2.08.000 from the HSPL4 ..
Click to expand...
Click to collapse
From HSPL4 you can flash the stock SPL, which is what you did. HSPL 2.08.0000 is stock SPL. With that, you can't do much.
You need 2.08.HSPL.
Try again and report back.
Marvlesz said:
If you don't have HSPL, you will get an error when trying to flash almost anything.
You said you flashed HSPL, but in fact you didn't
From HSPL4 you can flash the stock SPL, which is what you did. HSPL 2.08.0000 is stock SPL. With that, you can't do much.
You need 2.08.HSPL.
Try again and report back.
Click to expand...
Click to collapse
I just tried the USB RUU(with WWE and TMOUK versions) method with 2.08.HSPL and it gave the same error 266
geforceonline said:
I just tried the USB RUU(with WWE and TMOUK versions) method with 2.08.HSPL and it gave the same error 266
Click to expand...
Click to collapse
Try this easy fix:
http://forum.xda-developers.com/showthread.php?t=993472
To sum it up:
*Try a different port.
*Install ActiveSync/WMDC.
*If already installed, uninstall then re-install, or simply try a different computer if you have.
Marvlesz said:
Try this easy fix:
http://forum.xda-developers.com/showthread.php?t=993472
To sum it up:
*Try a different port.
*Install ActiveSync/WMDC.
*If already installed, uninstall then re-install, or simply try a different computer if you have.
Click to expand...
Click to collapse
have WMDC/Zune and drivers(also had activesync but deleted it because even then it didnt work)
tried all three ports
reinstalled it as well but unfortunatly no other pc is available atm
geforceonline said:
have WMDC/Zune and drivers(also had activesync but deleted it because even then it didnt work)
tried all three ports
reinstalled it as well but unfortunatly no other pc is available atm
Click to expand...
Click to collapse
Well, I am sorry then. I am out of ideas; you have wait for other members with greater knowledge.
Edit:
Maybe the USB cable? Although I highly doubt it, there is no harm in trying. Try a different cable and see what happens.
Marvlesz said:
Well, I am sorry then. I am out of ideas; you have wait for other members with greater knowledge.
Edit:
Maybe the USB cable? Although I highly doubt it, there is no harm in trying. Try a different cable and see what happens.
Click to expand...
Click to collapse
well, thanks for trying!
edit: IT WORKED! I tried another cable and while recognizing the pc went to some qualcomm drivers that i used to have and reverted to htc ones and the RUU picked it up and the flashing commenced. Thanks a ton!