Hi there,
Got a HD2 Leo, basically unused.
However, I got no clue what happened to it before it found me, however this is what I get when booting it up:
postimg.org/image/3pqzwfnz7/
when plugged on PC, it installed some drivers and suggested Windows Mobile Center and the serial changes to USB.
When I hard reset it, it asks me to go back to factory settings, when I press VOLUP, it just goes into a endless reboot screen (not constantly rebooting)
Is this device bricked or is there still hope?
Thanks in advance!
poen17 said:
Hi there,
Got a HD2 Leo, basically unused.
However, I got no clue what happened to it before it found me, however this is what I get when booting it up:
postimg.org/image/3pqzwfnz7/
when plugged on PC, it installed some drivers and suggested Windows Mobile Center and the serial changes to USB.
When I hard reset it, it asks me to go back to factory settings, when I press VOLUP, it just goes into a endless reboot screen (not constantly rebooting)
Is this device bricked or is there still hope?
Thanks in advance!
Click to expand...
Click to collapse
there is hope. it looks to me as though everything has been wiped from the phone. But you have hspl installed. you now should decide what you want on your phone, wm6.5, wp7, android? This will determine what bootloader you will have to install.
Robbie P said:
there is hope. it looks to me as though everything has been wiped from the phone. But you have hspl installed. you now should decide what you want on your phone, wm6.5, wp7, android? This will determine what bootloader you will have to install.
Click to expand...
Click to collapse
Hey Robbie, thank man.
Well it seems I can get some stuff on there, right now I can nagivate though aMAGLDR V1.13, this after I updated the radio (before I couldn't do anything) However when opening it shortly says: SD KERNEL FAILED
However I have two issues, when opening Windows Mobility Center 6.1, it shows I do not have a connection (When selecting USB flasher in MAGLDR) and therefore when opening the DWI.exe from the computer (Can't access SD card, should I be able to?) I get:
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)
What am I doing wrong here?
I assume you are trying to install wp7.
it might be something simple like the micro-usb lead being a charging one (2 wired) instead of a data one (4 wires). See if you can borrow one.
Open dwi.exe using right click and run as administrator.
sd kernel opened failed- means magldr is looking for Android zImage using ad sd booting, you have to first set the folder name (eg NativeSD) using ad sd dir for magldr to find it (of course a (Native)SD rom must first be installed for those files to be on your sdcard). But you don't need any of this unless you want to dual boot android wp7. The only command you need is boot wph.
See dxdy's signature for an excellent tutorial on flashing wp7
Related
How To Install A NAND Android ROM On Your T-Mobile HD2
(I am linking to several Original Threads in this tutorial. The "Nice Thing To Do" is hit the "Thanks" button at the bottom of those threads to let the author know we appreciate their help)
mskip wrote an excellent tut over on the Leo forums. I used his instructions to create my own method, which has never given me issues.
My method has been used by others and has a 100% success rate as of this writing.
You MUST be HSPL'd. This is not a joke. If you attempt this method without HSPL, your phone won't boot. I can not help you if you do this. If you have the 3.14 radio, try flashing: this stock ROM before HSPL. Thanks to xmoo for the link! Original thread is here.
Read the following steps. If you're confused, read the explanations below.
(Preparing)
Folder: Create a new folder on your Desktop. I named mine Flash. Put all downloads here.
HSPL: Cotulla's HSPL 3 is located here. (Original thread is here)
Task29: Download the Task29.exe program located here. Unzip it to a new folder. Replace the RUU_Signed.nbh file with your favorite radio. I use 2.15.50.14 (Original thread is here)
MAGLDR: Get MAGLDR 1.11 (or the latest version!) located here. Unzip this to a new folder.
ROM: Visit HD2 NAND Android Development thread here on XDA and download your new ROM. I am currently using this one, but will probably have a different one tomorrow Unzip this to a new folder.
SD Card: Back up everything you want to keep from your SD card, and then format it. Hint: dcim is where your pictures are stored (File System: Fat32, Allocation unit size: 16 kilobytes) Personally, I like to uncheck the "Quick format"; it takes up to an hour but ensures my card is in the best shape possible. Once your format is complete, you may replace your backed up files.
(Flashing)
(*Optional: Remove your SD and SIM cards, if you are paranoid, like me )
Connect your phone via USB to the PC and wait for any drivers to install.
Task29: Navigate to the Task29 folder and right-click on task29.exe and "Run as administrator". Your phone will reboot to the initial flash screen. You will have to reset to Bootloader.
Wait for your PC to update the drivers again.
MAGLDR: Navigate to the MAGDLR folder and right-click on ROMUpdateUtility.exe and "Run as administrator". Your phone will reboot to a new boot screen.
Wait for your PC to update the drivers again.
You should be booted to the new MAGLDR screen and see a series of options. Use your volume rocker to highlight "USB Flash" and press the green call button to select it.
Wait for your PC to update the drivers again.
ROM: Navigate to your new ROM folder and right-click DAF.exe and "Run as administrator".
Congratulations! When your phone reboots, it should start MAGLDR which will immediately boot your new Android NAND ROM!
Now, here are the details about the above instructions. You should only need them if you are confused.
(Preparing)
I use this to keep myself organized. I own several HTC phones and flash them all, so keeping things separate is a must for me.
Having a Hard Secondary Program Loader is a must for any NAND flash, whether it be Windows Mobile or Android. This will void your T-Mobile warranty, but can be fixed by flashing a Stock T-Mobile ROM via your microSD card. Check my sig for the tutorial link on how to do that.
This is the easiest method to do a task 29. The other is using mtty, which is beyond the scope of this tutorial. Task29 completely erases the existing files and partitions, preventing any loose data bits from causing issues with a new flash. You should always Task29 between NAND ROMs.
MAGLDR: A group of devs have been working on a NAND loader for some time and Cotulla and the Dark Forces Team (DAF) were the first to release a working loader. There may be more to come in the future, but this is the first (and has Tetris built in )
You should never ask the "best ROM for my phone" question. Every chef works hard on their build and considers it the best. Every user has their favorite chef and considers them the best. You should shop around to find the one that fits you best.
I consider formatting the SD card a must if I have any data written to it by a ROM. If you have installed Android to your card, you definitely want to do this!
(Flashing)
Your phone will boot into several different modes throughout the process. Each mode may require separate drives for WMDC to talk to it.
To reset to your bootloader, pull the battery and replace it. Hold down the "Volume Down" rocker and press the power (End Call) button. The phone should boot up to the tri-color screen. If it did not, keep trying!
Your PC may not need to search for drivers at this point, but wait and see anyway, just in case
MAGDLR will work as your new bootloader, but you can always access the original tri-color bootloader if you need to.
Don't worry if you get the missing "ADB" driver warning here. Only PCs with the Android SDK properly installed will have this driver.
You must flash your new ROM from the #4 screen via USB. It is the only way and the tri-color Bootloader method won't work here.
Again, you can ignore the missing "ADB" driver if it occurs. See above x2 for explanation.
Some chefs are renaming "DAF.exe" to "Install.exe" or "ANDR_INSTALL.exe". No matter what it's named, it should be the blue icon. See your ROM thread for detailed installation instructions if you get confused here.
Hope this helps!
262 Update Error
I have tried many different options, but none seem to go past the error. It showed white htc, on black background, and 0% update complete; and freeze about 7-10 minutes, then a popup with an update error message display.
[262] Update Error
I am running Energy ROM, with HSPL 2.8
The rest of my software info:
ROM version
27.Dec.2010WWE
ROM Date
08/30/10
Radio Version
2.07.50.27_2
Hardware info:
RAM size
576MB
Flash memory size
1024MB
If you have any suggestion for me, I am greatly appreciated.
Thanks in advanced.
DaraM said:
I have tried many different options, but none seem to go past the error. It showed white htc, on black background, and 0% update complete; and freeze about 7-10 minutes, then a popup with an update error message display.
[262] Update Error
Click to expand...
Click to collapse
Thanks for the plethora of information. In this case, it wasn't needed but most of the time it is
Error 262 means there is a link error between your phone and the PC. Some have solved this by re-installing ActiveSync or Windows Mobile Device Center. Some people said it was solved by simply unplugging the phone and trying a different USB port or cable.
After installing android rom in nand, device continously reboots
I followed all your steps and installed everything (there war an error encountered while installing the rom in the last step) but when my phone boots into android, after about a minute it will just restart itself and continue the same over and over without ever fully going into android.
can you please tell me how to get over this?
parthakolkata1 said:
I followed all your steps and installed everything (there war an error encountered while installing the rom in the last step) but when my phone boots into android, after about a minute it will just restart itself and continue the same over and over without ever fully going into android.
can you please tell me how to get over this?
Click to expand...
Click to collapse
It looks like the Android build you chose is either incompatible or was somehow corrupted when you downloaded it.
I suggest you delete the copy you have on your PC and download a different ROM, and then start over again.
Since there was an error, you don't want to try a fresh install without a task 29 and reinstalling hspl.
If you are using the Euro version of the HD2, don't try to install a TMOUS ROM, and vice versa. If you aren't sure, ask the chef who posted the ROM you want.
Hope this helps!
Radio Version
2.07.50.27_2
I think that the RADIO has to be 2.08.50.xx or a .50 greater.
Hello, I have some problems with my mob.phone HTC HD2: after get all the steps done my mobile stop working, then I tried install windows and tried turn on first time and my phone shows white screan with name HTC and don`t work at all,then i tried reset and Hard reset all setings and turn on again and than screan appears again with name HTC.
When i conect my phone to pc by usb, so my pc can`t find that phone.
Can you help me with this problem.
Thank you.
paulagrace said:
Hello, I have some problems with my mob.phone HTC HD2: after get all the steps done my mobile stop working, then I tried install windows and tried turn on first time and my phone shows white screan with name HTC and don`t work at all,then i tried reset and Hard reset all setings and turn on again and than screan appears again with name HTC.
When i conect my phone to pc by usb, so my pc can`t find that phone.
Can you help me with this problem.
Thank you.
Click to expand...
Click to collapse
One thing that was specified but not in the steps was HSPL. If you don't have that, you can't flash.
After having a bit of problem using the original tut you reference in your first post(basically it got locked on gogogo and a variety of problems thereafter), I am very happy to report that your variation on the method not only worked for me, but worked on the first attempt. And it has thus far done so each time I have tried it since. You cannot imagine my relief after all the frustration I had previously. So just wanted to let you know how helpful I found your post. Thanks!
The only edit I would suggest is that I believe USB Flashing is option 5 now instead of 4.
FWIW I was originally on ROM 2.13.531.1 (90963) WWE with Radio 2.10.50.26(now on 2.14.50.04).
gokun said:
The only edit I would suggest is that I believe USB Flashing is option 5 now instead of 4.
Click to expand...
Click to collapse
I just tried a fresh download of MAGLDR 1.11 and the option is still #4. Did you perchance grab version 1.12?
It would still work, but 1.12 gives you the additional option of installing and Windows 7 Phone ROM.
Yes on MAGLDR the option is 5 instead of 4.
Other than that, and the part about removing your sim and SD card, looks like an excellent guide.
apallohadas said:
Yes on MAGLDR the option is 5 instead of 4.
Other than that, and the part about removing your sim and SD card, looks like an excellent guide.
Click to expand...
Click to collapse
I am updating the tutorial to reflect on the changing menu numbers, thank you!
As far as the SIM and SD card removal, I did mention that this is optional but recommended. Yes, I realize that this is from the early days of flashing and is more than likely not needed, but in my defense this is my own method and I have never, ever had a bad flash. I've owned several HTC phones going back for a few years now and have not bricked a single one. I would consider that a pretty good track record, considering the number of posters who did brick their phone and have no idea what went wrong.
In light of your input, I will re-word the OT to ensure that the "optional" part is clarified.
Oh I totally hear ya.
I've never had a bad flash either. I think that some of the "Brickensteins" just do something wrong and don't mention it (like unplugging the phone mid-flash).
In your favor, I did read in one of the WP7 tutorials that the sd card should be removed, but since I don't plan on flashing that any time soon, I'll leave that wisdom with wiser hands
Thank you very much
HELP
Someone- anyone, I desperately need help. I went to a tmobile store because I was miserable with my HD2 and the man there gave me this website to turn my phone into an android, but i am NOT a tech person and now my phone is totally gone and I have no idea what I did wrong. I am so pissed I even did this. I need someone to help me.
my email is [email protected]
lalablu13 said:
Someone- anyone, I desperately need help. I went to a tmobile store because I was miserable with my HD2 and the man there gave me this website to turn my phone into an android, but i am NOT a tech person and now my phone is totally gone and I have no idea what I did wrong. I am so pissed I even did this. I need someone to help me.
my email is [email protected]
Click to expand...
Click to collapse
Ok do this hold the volume button down while powering on your HD2 and see if the multicolor bootloader screen comes up. If so you are not fubared. If you get bootloader you can save your HD2. Click on my Guide linked in my sig and read it then click the links at the top of my guide if you want to install Android or the link for WP7 if you want to install it. The links I have at the top of my guide are links to very good and extensive guide. If you want come post back here and I or others will help you and if you want to just PM me.
Please Help me...
I followed all your steps.. more then once. But every time I tried, I failed :[
I believe im doing everything right up until i have to connect my phone to run the DAF.exe file. When it says looking for usb, i have my phone connected but it then gives me this error;
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
I would love to use Android on my HD2.. so can someone help me? ._."
ol3randon said:
I followed all your steps.. more then once. But every time I tried, I failed :[
I believe im doing everything right up until i have to connect my phone to run the DAF.exe file. When it says looking for usb, i have my phone connected but it then gives me this error;
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
I would love to use Android on my HD2.. so can someone help me? ._."
Click to expand...
Click to collapse
You are using MAGLDR 1.13, not 1.11. On 1.13 (not covered by this tutorial), you have to choose "ROMUpdateUtility.exe", not "DAF.exe".
Hi...
I have a TMOUS HD2 and I had a MDJ Rom on it but i travelled to India and i had occasional hangups and restarts with the phone. So i tried flashing to a different ROM and i tried MIUI but the condition persisted (HAD MAGLDR 1.11 and CWM 1.2)
However that didnt work and i couldnt update the radio too (assuming that the EDGE connection is messing up the phone)
So i flashed back to the TMOUS Stock Rom RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship
and installed Radio 2.15.50.14 and HSPL 2.08.
After that i tried installing MAGLDR (1.13) in my Windows 7 system but it wouldnt. So i used a windows vista system and installed it using Romupdate utility.
Now i am trying to install CWM 1.3 but i keep getting this error
An error has occurred
Read below for more information
Error Description: send partition data failed
Info: .\RSPL\RSPL.cpp (815)
Error Description:
Info: .\RSPL\RSPL.cpp (558)
On phone:
Partition layout same
Erase
...
...
Save EMBR...
Default OS is AD NAND
Empty 0 partition .. OK
Flashing 1 partition... 1 [221-23E] MO
Can someone help pls? i couldnt post in the development forum cos i have to make atleast 10 posts else i would have posted this in the CWM 1.3 thread or this one even http://forum.xda-developers.com/showthread.php?t=981811.
Also in option USB Flasher from MAGLDR
the prompt says WAIT USB... even after connecting the USB to the phone. HOwever on running the DAF, it comes as WAIT USB...USB but many threads say that it has to be WAIT USB..USB even before running the DAF for CWM.
Thanks in advance
Andrew
Shamelessly bumping the thread so that someone could help me!!!
AJ
What's wrong is that you have allowed USB connections in ActiveSync. Open ActiveSync and untick the "allow USB connections" box and reflash and it'll flash correctly.
Ok... since its windows 7 / Vista there is only Mobile Device Center and i have unchecked the option "Allow USB Connections" And I still get the error...
Is there any workaround for this ?
Does anyone know why there was frequent system hangups ? Could someone help me find the root cause of this one ?
I am trying to install any new rom and see if the problem disappears in anything. But unfortunately I am stuck with CWM install.
AJ
which size cwm are you trying? there have been a few reports lately (myself included) that teh 150 ver failed in various ways, , download the 250meg ver and edit flash.cfg to 150 (or just leave as 250 for a quick test flash) and see if it works.
samsamuel said:
which size cwm are you trying? there have been a few reports lately (myself included) that teh 150 ver failed in various ways, , download the 250meg ver and edit flash.cfg to 150 (or just leave as 250 for a quick test flash) and see if it works.
Click to expand...
Click to collapse
Hi,
I tried the 250 one and the 450 one but it still fails. I dont know what is going wrong.
AJ
Try doing it like this.
Turn on your phone with vol down key held to enter bootloader (tri colour screen)
Run Task29.
When the phone reboots hold vol down again to get back into bootloader.
Flash MAGLDR 1.13 from bootloader by running "ROMUpdateUtility" instead of the DAF.exe.
Should work without a problem, I always flash MAGLDR like this.
I don't think it relies on mobile device centre like this so should eliminate any problems in that area.
This time when it reboots hold the power button to get into MAGLDR. Select USB flasher and flash the 150MB CWM partition. I sometimes have problems with the larger partitions but 150MB one always works.
Then install which ever rom you use using recovery option from MAGLDR.
Also make sure you have the latest versions of everything:
MAGLDR 1.13 - http://forum.xda-developers.com/showthread.php?t=893618
CWM partition should be version 1.3 - http://forum.xda-developers.com/showthread.php?t=898913
zX TheRipper Xz said:
Try doing it like this.
Turn on your phone with vol down key held to enter bootloader (tri colour screen)
Run Task29.
When the phone reboots hold vol down again to get back into bootloader.
Flash MAGLDR 1.13 from bootloader by running "ROMUpdateUtility" instead of the DAF.exe.
Should work without a problem, I always flash MAGLDR like this.
I don't think it relies on mobile device centre like this so should eliminate any problems in that area.
This time when it reboots hold the power button to get into MAGLDR. Select USB flasher and flash the 150MB CWM partition. I sometimes have problems with the larger partitions but 150MB one always works.
Then install which ever rom you use using recovery option from MAGLDR.
Also make sure you have the latest versions of everything:
MAGLDR 1.13 - http://forum.xda-developers.com/showthread.php?t=893618
CWM partition should be version 1.3 - http://forum.xda-developers.com/showthread.php?t=898913
Click to expand...
Click to collapse
Hi,
I tried doing like you said.
I downloaded TASK29...
Got into bootloader (4 color screen).
Connected the USB cable... waited for drivers to install and then waited till the prompt changed from SERIAL to USB.
Started TASK29. (as adminstrator - windows vista 32 bit)
Showed Image version as blank and Updated ROM as 2.00.000.00.
Clicked on NEXT and then the Screen changed the HTC with 0%.
It is stuck there.
Now i am unsure what to do.
AJ
HunterAJ said:
Hi,
I tried doing like you said.
I downloaded TASK29...
Got into bootloader (4 color screen).
Connected the USB cable... waited for drivers to install and then waited till the prompt changed from SERIAL to USB.
Started TASK29. (as adminstrator - windows vista 32 bit)
Showed Image version as blank and Updated ROM as 2.00.000.00.
Clicked on NEXT and then the Screen changed the HTC with 0%.
It is stuck there.
Now i am unsure what to do.
AJ
Click to expand...
Click to collapse
Don't know if you should unplug the phone. After it's started, it's possible to brick your device by unplugging in the process of wiping. I don't have any advice after that, but just a note if you're wondering whether it's safe to unplug. Wait 'til someone other than I with experience says otherwise. Sorry and good luck.
That has happened to me once before, not sure if it was during Task29, flashing a stock rom / radio or MAGLDR. I left it for a long time and in the end decided there was nothing I could do but pull the battery and pray my phone wasn't bricked. Luckily it was ok and I tried again and everything was fine. Don't think anyone will tell you to do that though because none of us want to be responsible for bricking your phone!
If it hasn't got anywhere after 10 minutes or so then I guess you won't have much choice.
In theory if it's stuck at 0% then it hasn't started yet so it might be ok to unplug and pop the battery but don't take my word for it.
Would probably be more of a risk if it was half way through and you unplugged it.
Good Luck!
Well i did post earlier that i didnt brick my phone yet... but i have tried everything else that has been said in the community and now i am losing all hope of getting the android to work on my HD2...
Can someone pls help ??
Cotulla / bebe - Anyone ? I know you possibly might not check these forums but just wanted to ask your help.
AJ
Give this a try...
Use the task29 from my thread .. do what it says ..
DL one of the setup programs.. 150 - 430 depending on what ROM you want.
And follow the on screen helps ..
http://forum.xda-developers.com/showthread.php?t=981811
I've already look through the other threads of users with the same issue, but none seem to have exactly the answer I'm looking for.
I was running windows phone 7 on my htc hd2, which was easy enough to do.
but yesterday I decided I wanted to put android back onto it, so I downloaded
Energy_2.8.2012.SensationXL from here. Followed all the steps in the thread, but now everytime I turn on the phone I get the error "NAND yaffs2 boot mount failed" and then just clicks straight over to the boot menu
so, as stated in http://forum.xda-developers.com/showthread.php?t=971268 I tried to "task29" the phone through the HD2 Toolkit app, and start again.
But all I get when trying to: task 29, update to/ install magldr 1.13 or clockwork, it just gives me an error [264] connection.
I'm unable to get onto the tri-coloured usb flashing screen that I used when I put WP7 on it, i've tried putting it in 'usb flasher' mode from the menu to no avail..
is there somehow a way to put the new ROM I downloaded ^^^^ onto the phone by switching it over to mass storage mode,
and then selectiong option 3: boot AD NAND?
how about return to WM,then try task29 and MAG or CLK
uyong said:
how about return to WM,then try task29 and MAG or CLK
Click to expand...
Click to collapse
I've always done the task29 and wiped it via HD2 Toolkit, but it's still stuck on the magldr boot menu
does the USB flasher option be the same at the bootloader (three-coloured screen) for flashing the new android rom?
If I simply loaded the android rom onto the SD card via an adapter, would that work if I went through the MAGLDR boot menu?
EG: 9: services, 1: boot settings, 1: boot source, 1: android from sd
..yes?
I'm at my wits end here guys!
I'm well aware of how to get into the three coloured bootloader screen, but the HD2 just wont do it!
I've done it numerous times before with this very handset from WM 6.5, then android (can't remember what version) , then WP7, and now it's decided to stop doing it when I want to go back to android, and the task29 has wiped it all, so I can't even simply revert back to WM6.5..
if someone could give me some step-by-step instructions on either a nand or SD android rom and the steps I need to take to get it working with that, bearing in mind the 'stuck on magldr' issue I have.
I can't remember if I stated it in my previous post but ever since I did the task 29, anything I try to do ie: update magldr to v1.13, update clockwork, or anything like that, it just give me an error saying it isn't connected via usb.
and now (started a few min ago) it isn't being recognised by the computer when I plug it in, even if i try and use 'mass storage' from the menu, whereas yesterday it was
julz1111 said:
If I simply loaded the android rom onto the SD card via an adapter, would that work if I went through the MAGLDR boot menu?
EG: 9: services, 1: boot settings, 1: boot source, 1: android from sd
..yes?
I'm at my wits end here guys!
I'm well aware of how to get into the three coloured bootloader screen, but the HD2 just wont do it!
I've done it numerous times before with this very handset from WM 6.5, then android (can't remember what version) , then WP7, and now it's decided to stop doing it when I want to go back to android, and the task29 has wiped it all, so I can't even simply revert back to WM6.5..
if someone could give me some step-by-step instructions on either a nand or SD android rom and the steps I need to take to get it working with that, bearing in mind the 'stuck on magldr' issue I have.
I can't remember if I stated it in my previous post but ever since I did the task 29, anything I try to do ie: update magldr to v1.13, update clockwork, or anything like that, it just give me an error saying it isn't connected via usb.
and now (started a few min ago) it isn't being recognised by the computer when I plug it in, even if i try and use 'mass storage' from the menu, whereas yesterday it was
Click to expand...
Click to collapse
Try flashing it back to window 6.5.... nbh.img?
Sent from my LG-P999 using xda premium
Yes, I agree with the others.
When I try a new ROM and it fails for some reason or another, I always just go back to win6.5 (http://forum.xda-developers.com/showthread.php?t=623283) and start over.
A bit of a hassle, but have found this to be the most reliable way so far.
how can I flash it back to 6.5 if I cant get to the bootloader/ when it doesn't recognise the phone when it's plugged in
julz1111 said:
how can I flash it back to 6.5 if I cant get to the bootloader/ when it doesn't recognise the phone when it's plugged in
Click to expand...
Click to collapse
When flash back to 6.5... you don't need a computer. All you need is an SD card. Download the correct file that matches to your country... extract the file... pull out the nbh file and rename it leo... then place it on the root of your SD... then boot.
This is a short run down of how to get it back to stock. Search a little... cause I know there is a thread that tells you how to do it in detail... plus it have all the files that you'll need.
http://theunlockr.com/2010/04/22/how-to-get-the-htc-hd2-back-to-stock/
Sent from my LG-P999 using xda premium
Ok. I have a HTC HD2 t-mobile. Someone gave it to me to see if I can fix it. So I have NO clue how it got to the point it is at now. All I know is that you power on and its a white screen. No HTC logo. Just white.
Enter boot loader: Red/Green/Blue/Black/White.... Its says:
PB81120 SS-B3
SPL-2.10.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x50
SERIAL
Thats it. It doesnt connect to the computer.
What can I do? I tried:
CLEAN INSTALL
It’s a pretty long process, however, it takes a shorter time than the Installation of NAND Android. It takes me about 15minutes. It should take you about half an hour but no more than half an hour.
HSPL3, -2.08.HSPL.
[Head to my guide on How to install HSPL3, if you haven't install HSPL3 yet.]
Radio Version that supports 576 RAM(Radio2.15.50.14).
[Head to my guide on How to install radio , if you haven't install a suitable radio version yet.]
Wipe phone memory completely.
Install DFT MAGLDR.
Install ClockworkMod Recovery.
Create EXT3 Partition with ClockworkMod Recovery. (This step will wipe everything on our SD Card.)
Transfer ROM(zip file) to SD Card with ClockworkMod Recovery.
Install ROM from SD Card with ClockworkMod Recovery.
Details will be provided for each of the 6 steps.
But the phone and computer cant communicate. I have tried a hard reset. So thats where I am at now.
temp removed.
Ok. So I tried to flash the stock ROM from the SD card. It didnt complete. It says that it failed. It says at the top
00018003
LEOIMG.nbh - FAIL
Error happen
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
Error Description: wait marker fails
Info: .\RSPL\BootLoader.cpp (225)
When I try to install HSPL3 I get this error
CRITICAL ERROR
FLOW: 00000006
Error code: 00000014
Description Unknown
I can not get HSLP on my phone. I have tried versions 2,3 and 4... Is the phone done???
So I know I am a pain. But I have searched and read just about everything I can. I have tried to flash the stock ROM, I get an error of Radio Fail. I can not flash any other ROMS because I can not install HSLP.... I can connect via USB. But Windows Mobile Device center does not acknowledge the phone. I have ran the Task29... well tried... it says image is corrupted. I have even stuck the dang thing in the freezer like I have seen in random posts. Nothing but a really cold phone.
When I try and install HSPL3 I get an option to choose 2.08.HSPL or 2.08.0000 I have tried both. I get the critical error... Error code 16 description unknown.
I have tried following every set of directions I can locate in xda... Nothing has worked at all.
McSpammer5 said:
temp removed.
Click to expand...
Click to collapse
???What does that mean???
Have you tried reflashing window mobile???
Sent from my LG-P999 using xda premium
Yes I tried to reflash several times. I went and bought a new SD card. Solved it. Got windows working properly... Now to move on to installing Android
yesiamanoob said:
Yes I tried to reflash several times. I went and bought a new SD card. Solved it. Got windows working properly... Now to move on to installing Android
Click to expand...
Click to collapse
Great...
Sent from my LG-P999 using xda premium
Hi to the experts!
I have a very similar problem, maybe "almost" identical...
My HD2 (Australian Telstra, stock in almost every way), and it has been reliable for 2 years from new.
Then last Saturday night it started "failing to load HTC Sense", but all the WinMo 6.5 stuff was still fine. This lasted for 2 days and I thought it was stable like this so I would have time to look for a new phone, but last night I turned it off and on again, and all I have is the white screen. Mine has the green htc on it, but the only way to make it go away is to take out the battery.
I tried the volume down / power ON and I get the RGB+W screen, and when I plugged it in via USB to my new laptop it loaded drivers and initiated Windows mobile device center - but it won't recognise that there is a device there.
Now my very strong desire is to somehow boot it to allow recovery of my contacts directory - I have just started a new job and have probably 40 or so new people in there since my last backup.
What are my options? Is there anyway to boot from SD card without erasing the whole of system memory??
Failing that, how do I flash back to stock?
thanks (in hope)
..Neil
Stock WM
Try installing stock WM 6.5. There are many links available for the same, google it.
Do this without the memory card.
Enter Bootloader by pressing volume down and power on button together.
Then run the WM ROM file on your computer. You must see the progress bar on your phone. Let it settle down.
Hope that helps..!!
Hi, Tried installing my first Nexus ICS Android on HTC HD2
following instruction here http://forum.xda-developers.com/showthread.php?t=1434860
Got to the point where I got MAGLDR v1.13 installed and running.
Then found that I needed HD2 Android NAND Tool and Repartitioned System size to 200 Mb
using USB flasher mode on the MAGLDR.
Then NAND Tool suggested that running Wipe(taks 29) to be a good idea before attempting to install Android so I tried running this as well.
I got the phone into tri-colour USB mode and started wipe. USB mode disappeared replaced by HTC progress bar but it got stuck at 0% and timedout.
I tried recovering to HTC original WWE ROM but it also gets stuck at 0% progress.
Currently Bootloader starts and loads a options, I can also go into USB mode but nothing will start updating the phone it gets stuck at 0%.
I think what repartitioning created a problem but I am unsure how to recover it and need your help!
sofaford said:
Hi, Tried installing my first Nexus ICS Android on HTC HD2
following instruction here http://forum.xda-developers.com/showthread.php?t=1434860
Got to the point where I got MAGLDR v1.13 installed and running.
Then found that I needed HD2 Android NAND Tool and Repartitioned System size to 200 Mb
using USB flasher mode on the MAGLDR.
Then NAND Tool suggested that running Wipe(taks 29) to be a good idea before attempting to install Android so I tried running this as well.
I got the phone into tri-colour USB mode and started wipe. USB mode disappeared replaced by HTC progress bar but it got stuck at 0% and timedout.
I tried recovering to HTC original WWE ROM but it also gets stuck at 0% progress.
Currently Bootloader starts and loads a options, I can also go into USB mode but nothing will start updating the phone it gets stuck at 0%.
I think what repartitioning created a problem but I am unsure how to recover it and need your help!
Click to expand...
Click to collapse
Wrong forum, should be in the Q&A. You'd have thought it would be obvious, seeing as you're asking a QUESTION, but somehow people don't pick that up
Also, you really need to read more. There isn't any point in installing MAGLDR then Task29ing, in fact there is very little point in Task29ing at all unless you experience major problems with your phone. A simple data wipe (in CWM) and repartition has never failed me.
If you did a task 29 after doing the other steps first then you wiped everything back off. Install magldr again then CWM and then install your rom of choice.
Also for being a member since 2005 you should know not to EVER post a question in development.
Mods please move to Q&A
Sent from my Galaxy Nexus, T989, HD2, G2x or Touchpad.
moved
Sorry for posting it in the wrong forum.
Many thanks for the comments...I cannot install anything at present because once update process starts it times out at 0%. Task29 did not work either - it also gets stuck at 0%.
Only thing that works is Boot loader and USB mode.
As Boot loader is working I tried to install NAND Android following this instruction:
2. FLASH YOUR ANDROID ROM
The Original NAND Android Thread by Cotulla is *HERE*
NOTE1: This section is only applicable AFTER you have flashed MAGLDR to your Device
NOTE2: Make sure your phone is still connected via usb cable before starting
* When your phone Reboots it will Enter the MAGLDR Boot Menu Screen *
1. Press the 'Volume Down' button to goto Option 5: USB Flasher and press the 'Call' button (far left of the 5 hardware buttons at the bottom)
2. The menu will enter Android Flasher mode and install usb drivers if not present
3. Browse to the folder you extracted your NAND Android Package files to on your pc, right click on Run DAF.exe (or Install.exe if DAF.exe isnt present) and select Run as Administrator
But DAF is giving this error back:
Error happen
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
thats all old instructuions.
go get the nand toolkit, and also get hspl3
...
phone into bootloader (tri colour screen, not magldr)
connect usb
run hspl3
choose 2.08.hspl (don't assume its already 2.08.hspl, check it, hanging at 0% is often a sign of no hspl)
when reboots immediately go back into bootloader
*(* from here on you can do all this in the nand toolkit*)*
flash magldr
when it reboots enter magldr
(if phone hangs on a htc screen and doesn't show magldr, you need to flash radio 2.15.50)
phone into magldr
connect usb
choose 'usb flasher'
in toolkit select desired system partition size and cache size
when its finished
phone back into magldr
choose 'ad nand'
this starts cwm
(if you havent yet partitioned your sd card with an ext partitio, look ity up and do it now)
select 'install zip from sd'
select zip from sd
browse to where you dropped the rom.zip file onto your sd card.
when it reboots you're done, , alternatively it failed somewhere, , which step?
if you get apparent driver errors, theres a nice big button called drivers in the toolkit (i think?)
Many thanks that worked like clockwork