Database Users

Wallaby radio stack upgrade problem solve successfully!!

Hi everybody
Yesterday i had a problem trying to upgrade my wallaby to radiostack 6.18 tu RSU 6.24.
When i was doing the upgrade with the rsu files and the upgrade was in 88% in the screen appears:
" Upgrade problem, please reset" (something like that :? )
When i did the reset i got the boot screen and in the corner only i get the ROM version. The radio stack dissapears and then im not able to have my wallaby works.
Then i get into the wallaby bootloader version 5.15 and i got the following message:
GSM-ERROR
I reset the device a lot of times and nothing. i think " god i lost mi phone"
and then reading posts and posts i solve the problem in this way:
1:- I cook a rom image in an sd card using Xtools and a card reader instaled in your pc.
2.- when you finish insert the sd card with the image, enter again bootloader by holding On/Off and doing a soft reset
3.- Bootloader should tell you something that OS is detected on your SD-Card
4.- Press Action Key to install the ROM
5.-After finishing do a hard reset
Now your ROM should be installed on your device.
6.- turn off your device, maybe you will have to press the power button several times.
7.- Remove your SIM card
8.- Turn on your device, wait about 15 minutes and you can see that the device goes out off that frezze screen and gets into the align screen setup.
9. When you get the TODAY screen connect your device in the cradle and make a new asociation for your device
10. get into the windows file with the explorer of activesync on your pc and copy the 4 radio stack files in the windows file of your deviceq and the .exe file in the \Windows\StartUp folder of your device.
11. Restart the device and the upgrade will begins automaticaly in the back ground
12. when it sucsesfully done, do a soft reset and you must have your radio stack upgrade done and your wallaby completly recovered.
13.- Insert your SIM card again and enjoy
I hope this guide will help you
Rememeber to copy the correct radio stack in your device, i used the RSU 6.24 because i have a PW10B1 wallaby. check your version in the label in the rear part off your device
[/b]
if this tip results succesfully to someone please let me know. thanks

Well done, not many people manage to repair corrupt/missing radio stack, thanks for the details also, it may help resurrect other dead Wallabys.

which RSU to use
hi,
mine is PW10A1 so which RSU to use

Re: which RSU to use
maddawood said:
hi,
mine is PW10A1 so which RSU to use
Click to expand...
Click to collapse
ftp://[email protected]/Wallaby/Radio_Stack/RSU_V4.16_PPC.zip
HTH
Stefan

which rom you used?

Re: which RSU to use
LumpiStefan said:
maddawood said:
hi,
mine is PW10A1 so which RSU to use
Click to expand...
Click to collapse
ftp://[email protected]/Wallaby/Radio_Stack/RSU_V4.16_PPC.zip
HTH
Stefan
Click to expand...
Click to collapse
That link isn't working at the moment - I could sure use it

Link should be:
ftp://xda:[email protected]/Wallaby/Radio_Stack/RSU_V4.16_PPC.zip
Stefan

Thanks Stefan - I saw elsewhere what the password was, and noticed it was missing from the URL. I got the RSU file and have finally managed to get it on to the XDA, but still fails every time it restarts... the old 1% problem... Do you know if it is easier to update the radio stack from an SD card? The XDA is running the special edition ROM, which has at least given me back some control of the device.
Thanks in anticipation
Phil

PhilHirons said:
Thanks Stefan - I saw elsewhere what the password was, and noticed it was missing from the URL. I got the RSU file and have finally managed to get it on to the XDA, but still fails every time it restarts... the old 1% problem... Do you know if it is easier to update the radio stack from an SD card? The XDA is running the special edition ROM, which has at least given me back some control of the device.
Thanks in anticipation
Phil
Click to expand...
Click to collapse
I have the same problem, every time my device restarts, and stop at 1%. So I am wondering if Stefan can help us to give us solution in this case.

Worth the risk?
After reading this ordeal, is it worth the risk to upgrade a working radio stack? Does the telephone work substantially better after the upgrade?

Try other RSU's
kinowong said:
PhilHirons said:
Thanks Stefan - I saw elsewhere what the password was, and noticed it was missing from the URL. I got the RSU file and have finally managed to get it on to the XDA, but still fails every time it restarts... the old 1% problem... Do you know if it is easier to update the radio stack from an SD card? The XDA is running the special edition ROM, which has at least given me back some control of the device.
Thanks in anticipation
Phil
Click to expand...
Click to collapse
I have the same problem, every time my device restarts, and stop at 1%. So I am wondering if Stefan can help us to give us solution in this case.
Click to expand...
Click to collapse
Hi, have you tried using other RSU versions? I had the same problem too (1% fail) using 4.16. After giving up on the 4.16, I tried RSU 4.21 (exe). One shot and I was able to re-flash my RSU. What I did differently was to remove the AC power while doing the RSU upgrade (the exe file prompted me). Hope you get your wallaby up and running again.

I try alot of times but it stop at 1% - full batery got the same result.
help.

Re: Try other RSU's
Thank you for your help. I have tried many vensions of RSU, such as 4.16, 4.21, 6.24, 6.25, etc. But all of them showed 1% mistake.
morph751 said:
kinowong said:
PhilHirons said:
Thanks Stefan - I saw elsewhere what the password was, and noticed it was missing from the URL. I got the RSU file and have finally managed to get it on to the XDA, but still fails every time it restarts... the old 1% problem... Do you know if it is easier to update the radio stack from an SD card? The XDA is running the special edition ROM, which has at least given me back some control of the device.
Thanks in anticipation
Phil
Click to expand...
Click to collapse
I have the same problem, every time my device restarts, and stop at 1%. So I am wondering if Stefan can help us to give us solution in this case.
Click to expand...
Click to collapse
Hi, have you tried using other RSU versions? I had the same problem too (1% fail) using 4.16. After giving up on the 4.16, I tried RSU 4.21 (exe). One shot and I was able to re-flash my RSU. What I did differently was to remove the AC power while doing the RSU upgrade (the exe file prompted me). Hope you get your wallaby up and running again.
Click to expand...
Click to collapse

Re: which RSU to use
LumpiStefan said:
maddawood said:
hi,
mine is PW10A1 so which RSU to use
Click to expand...
Click to collapse
ftp://[email protected]/Wallaby/Radio_Stack/RSU_V4.16_PPC.zip
HTH
Stefan
Click to expand...
Click to collapse
Hi guys i have a pw10a1 too, and my radio version is 4.21, i really think it sucks. so is it a good idea to downgrade to 4.16??? or will it only be made worse. or can i use the 6.25.02 version? or is that for another phone type.. PWIEW srry for all the questions .. if 1 is awnsered. i'm happy

Radio Problem !!!

--------------------------------------------------------------------------------
Hello,
i am having a frustrating problrems with my p3600
- the phone is not working ! it show that there is no singal and i can't get to the phone seetings
- i tried hard reset / soft reset / upgraded to wm6 , no difference
- tried to flash the radio , but it stops at 0% , and after one hour , it is still 0%?
please help!

Try updating to WM6 with this package:
Apoc said:
jesus, use this: http://rapidshare.com/files/2987211...y_WM6_v2.0.0.4_incl_HSPL___Radio1.41.0.11.exe
created a self-extracting archive so that you only need windows to do the upgrade(no 7zip or winrar), it should extract to a temporary folder and execute the updater, it will flash the hardspl, radio 1.41.0.11, and lsvw's 2.0.0.4.
Click to expand...
Click to collapse
Like it says, it's a total upgrade package which will also upgrade the radio, using harspl, so CID shouldn't be a problem...
Just connect to ActiveSync (preferably as a guest) and start the .exe you've just downloaded. It'll push SSPL by Des (modified bootloader) to the phone, execute it and start updating.
Let me know if this worked...

Did the upgrade and still not working ......
?

Time for a warranty repair!
Your symptoms stongly suggest a hardware fault with the Qualcomm radio chip.
Updating to the WM6 ROM's doesn't update the Radio, so you could try flashing just a Radio ROM (though by your 1st post you've already tried that?)
The instructions for LSVW and Mun-rus both state that the radio should be updated prior to applying the WM6 ROM itself.

osamanet said:
Did the upgrade and still not working ......
?
Click to expand...
Click to collapse
But did the whole upgrade process finish all well...? Is radio 1.41 installed now?
It's a bummer you still have problems, but just exclaming it's not working doesn't really help... Can you be a bit more specific please???
What went well, and what didn't, and what is the exact problem that has risen or didn't get solved? Did you get any specific error-messages? Are you in a good-coverage area? Etc,etc...
NeilM said:
Updating to the WM6 ROM's doesn't update the Radio....
Click to expand...
Click to collapse
Yes it does....the package i linked before does flash radio 1.41.

Moaske said:
Yes it does....the package i linked before does flash radio 1.41.
Click to expand...
Click to collapse
Ah- missed the significance of that one! Thanks
Problem is that this topic is split in 2 forums, so some info not consistent- his answers in the other thread stongly suggest hardware failure.

Hello,
thank you for answering
i did try all the updates in this forum , SAME PROBLEM !
when i press the green button nothing happins , when i go to Phone nothing happiens , when i go to phone settings , also nothing happiens
it used to work before , but it used to disconnect every hour or two , then it stopped working
is the device coverd by warranty in the U.S ? i bought it from eBay less than three months ago

I've no idea if it is likely to be covered- was it a new device, fully boxed?
If so, there should be an international warranty card inside, but I don't know HTC's policy on coverage in USA.
HTC's USA Home Page doesn't mention this model at all.

Please help - bricked XDA Orbit II

Hi, first post on the forum so please be gentle with me....
I have an XDA Orbit 2 which was until last Thursday working fine with the last official upgrade from O2 (Win 6.1, no idea about all the other stuff).
Whilst using the phone last week it suddenly died in the middle of a conversation. It wouldn't power on at all. I took out the battery, waited a couple of minutes, put the battery back in and switched it on. All that happened was the phone displayed the 4 colour screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white. I repeated the battery removal exercise a few times, waiting for increasing lengths of time but nothing changed.
I had a fairly long search through the forum and have tried for a few hours now going through the various fixes suggested but I am getting nowhere.
It won't hard reset, all that happens is the message "No Image Found" appears for a very short time and I then get stuck on the 4 coloured screen with the message above.
The same thing happens if I try just putting the thing in bootloader mode.
I can't use any of the official O2 rom upgrades as the phone because all the PCs I've tried connecting to it won't recognise it over a USB link.
I've tried connecting to it using mtty, again on several PCs, but I just get a message "USB port can not open". Just in case I've uninstalled Activesync on one PC and got the same answer.
The "how to flash you polaris using the microSD card" originally looked useful but I have some problems with it.
The first is that I need HardSPL installing on the device, which I can't do because I can't get to it.
The second will be down to me not knowing where to look, but I can't find a ROM to download and copy to the microSD card as POLAIMG.nbh. I did manage to find a Win6.5 one (the HTC Polaris - PDaviet rom wm6.5 manilla 2d (core 23004) by tranminhman one) which I thought I'd try. I guess the idea was that if I could just get something working I could always reflash it again with a different ROM or maybe apply the o2 upgrade. Unfortunately the image was password protected and I couldn't find the password in the thread.
I'm kind of at a loss now so any help would be appreciated.
Cheers

Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan

Did you do soft reset

alanazar said:
Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan
Click to expand...
Click to collapse
Bit in bold er... cant quite understand why in iolite section as the xda orbit 2 is the rebrand htc touch cruise => htc touch find. Its in the right place.
On the side of what to do i the ony thing i can think of would be mtty and if that didnt work then try to reflash the official o2 6.1 release and see what happens when you try to do it.
You cant try to install any 3rd party roms they jsut wont flash as you dont have hard spl installed and cant do that until you have it running again.
Try the above and see what happens...

Hi Nik
I have tried just about every kind of reset, nothing has worked.

Hi Alan
If I can't get it sorted any other way I'll probably send it off somewhere but I'd like to have a go at fixing it myself. It will at least be a bit of fun!
I take then that I've posted this in the wrong forum. Oops, apologies.
Jon

You have not posted in the wrong forum look at my signature!

Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
1a) Extract shipped ROM by WinRAR , take RUU Signed.nbh
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]

Nik Ahmad said:
Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]
Click to expand...
Click to collapse
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon

jonfsharp said:
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon
Click to expand...
Click to collapse
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend

have u tried this?...
turn off, pull out the battery, then put it back, charge ur phone till the battery indicators shows green (which mean it's already fully charged) then... power on ur device.
it looks like a dumb suggestion , but... i have had a same situation
(HTC KAISER, not Polaris).
if it doesn't work, then try to upgrade with a POLAIMG.nbh (take it from official HTC ROM)
in a 2G FAT32 microSD root directory.

Nik Ahmad said:
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend
Click to expand...
Click to collapse
Thanks Nik
Much appreciated.
Downloaded the ROM as suggested, unzipped to the SD card, renamed the image to POLAIMG.nbh, stuck it in the phone and things got slightly more interesting.
In bootloader mode I now get a bit further. I get a grey screen which says "Loading ..." then "Checking...." then "00028002 Not allow". It then goes back to the four coloured screen as before.
However, does the fact that it is trying to read something mean that I have just got the wrong file?
I'll try a few more and see what happens.
Thanks once again, your help is greatly appreciated.
Jon

Hi oza
Yep tried all the battery pulling out stuff but got nowhere.
The ROM thing on the SD card gets further. I extracted the ROM from the official O2 upgrade, stuck it on the card and renamed it POLAIMG.nbh.
If I put the phone in Bootloader mode I now get even further than before. I get a grey screen with:-
POLAIMG.nbh -
RADIO_V2 -
BOOTLOADER -
SPLASH1 -
OS -
Press power button to start update image
Press action button to cancel update image
If I press the power button
I get an "Update In Progress" message and a progress bar.
After about 4 minutes I get a full progress bar and :-
POLAIMG.nbh - OK
RADIO_V2 - OK
BOOTLOADER - OK
SPLASH1 - OK
OS - OK
Update complete
UPDATE SUCCESS
And that's as far as I've got so far.
If I take the SD card out and try a hard reset I just get stuck on the 4 coloured screen I got before, but with no No Image Found message.
I get the same thing with bootloader mode and when I just remove the battery.
If I put the SD card back in I can go through the update process but I can't do anything
else.
So, have I actually made any progress? I'm not actually sure what I have updated and what state the phone is in at the moment. Is the fact that this didn't work an indication of a hardware failure and I should send it off somewhere.
Any advice on next steps would be good.
Jon

what is ur bootloader screen says now?
IPL...
SPL...

Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?

Try this one M-AMINES if the radio you had was a 1.59.xx radio as it has the radio included.
if it was a 1.65.xx radio then try the VLIT naked rom.

oza_crazy said:
what is ur bootloader screen says now?
IPL...
SPL...
Click to expand...
Click to collapse
Hi Oza
Exactly the same as it did when it first broke. I get the 4 coloured screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white.
No idea what the IPL is or was I'm afraid.
Jon

bally3 said:
Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?
Click to expand...
Click to collapse
I've not been a big modifier in the past so it was just using the bog standard O2 software from the O2 website. The name of the file is "RUU_Polaris_O2_UK_3.13.206.0_radio_sign_25.85.30.07_1.59.42.15_Ship.exe" so I presume that there can be information gleaned about things like the SPL, ROM and radio versions?
Not a complete nunce, no, but so very far away from being comfortable with all this. This post was a result of a good few hours trawling through the forums looking for help. Anything I have done has been the result of a post on this site and I am very grateful that there are people willing to share their knowledge.
Anyway, as for hard spl, nope it isn't installed. I'd never needed anything like it before the phone died and now that it has died I can't get onto it to install anything.
Yes, this happened right in the middle of a conversation after a good year or so of normal day to day use. As I said, I haven't needed to make any changes to the phone so the only thing I've ever done is upgraded it with software from the O2 site.
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon

jonfsharp said:
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon
Click to expand...
Click to collapse
Well whatever you do dont bin it, we can always use it on the Android project if you decide to go that way.
Ok.. so lets see.. the phone is not picked up at all in windows?
If that is the case, if even a serial connection cant be made then theres issues. At this point, I would disregard all the other advice as it only applies to a hard spl device unfortunately. SD card flashing and all other radio rom flashing will only work with hard spl as far as I know - definitely safer for certain and you dont want to wreck a repairable device.
I take it, its not under warranty, for your mention of costly repair.
The important thing at this stage is a serial or usb connection from a Windows PC. I think I have heard of forcing this connection by opening the device but this would really be in the realms of profficient repairer or enthusiast.
I'll have a look but also do some searching yourself for making a connection to a Windows PC and forcing an SPL onto a phone.
I dont know whether anyone's ever managed to HardSPL a phone using a memory card? Just a thought...

Who would have known.. have a read of this and see if you can follow it up regarding the spl through sd card ..
http://forum.xda-developers.com/showpost.php?p=3273438&postcount=7

official at&t callerID update bricked my phone.. :(

after my phone rebooted once the update was complete, it wont get passed the "at&T World Phone" white screen... SOMEONE PLEASE HELP ME!!!! i was using a stock at&t pure with the stock rom. i can not upgrade hardspl or ANYTHING any suggestions on how to get my phone to boot? hard-reset went through with no signs of failure but it still will not boot up after that finishes... sorry if its something im overlQQKing, but i just cant figure it out. n yes i have researched although obviously not enough at this point. Thanks to anyone who can help in advance. forgive my stupidity!!!

......
noone?????

The HTC Pure updates hosed my phone too, I had already applied hard-spl to my Pure and i've flashed it with dozens of roms. Since I was currently using one of the "Stock" AT&T roms posted on XDA I figured I could apply the updates. Unfortunately after applying the update my phone froze at the boot loader. I was forced to flash my rom using the memory card method and then restore a backup.
you could try putting the phone in SSPL mode manually, (reset button+volume down), the run hard-spl hard-spl in manual mode.
you can then flash your rom using the memory card method. (FAT32 formated memory card, rom file renamed to topaz.nbh copied to root of flash card, reset button+volume down to enter SSPL, power button to confirm flash).
All this assumes you've already tried to hard reset your Pure (reset button+vol up+vol down)

Thanks for the reply! Unfortunatly, i tried the manual method and after it hanging at 0% for about 5 minutes, i keep getting error [262] update error.. (communications error) is this becuase i can not sync with mobile device center (win7)? I really dont want to just have to toss the phone! I have had an at&t tilt, at&t fuze, and now the at&t pure, and this is the only phone i have had this problem with for some reason...

Try Unplugging Your Pure From the computer Take Out the Battery Put the Battery Back in Mean While Restart your computer and Press Power And Volume Down At the Same time on your Pure If its on the colored screen your good,..Make sure your system is online and your not downloading anything and plug in your Pure to the computer it give it about 2 minutes to download the HTC USB driver then once its done your phone will say USB on the bottom of the Red Green Blue And White four color screen Then open up one of your ROM's and Flash it,....Do You Have Windows Mobile Device Center Installed?
If Not here is the Link
http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
If you do already you need to uninstall the Driver update for windows mobile media center then install it again .

i can get the bootloader screen just fine! i just can not get hardspl to flash onto it. it sits at 0% every time. the phone will not boot so i can NOT get into mobile device center. The tri-colored screen comes up with no problem and it says USB on the bottom, so the drivers are already installed. I even tried hard-reset and still no luck

There was an additional cab file I needed to install to HSPL the Pure
"enablerapinew.cab"
basically the machine just would fail to load the HSPL without it
but it still functioned afterwards, does yours?
Do a search on XDA find and DL the cab (or I could attach a zipped copy)
If you can still access the device,
just copy enablerapinew.cab to any temp dir on the device
the execute it through fileexplorer
then go back to installing the HSPL (mine then worked fine)
If you haven't already, You should go to
http://forum.xda-developers.com/showthread.php?t=520312
you'll find troubleshooting info and a link to the extra cab there
If you really are bricked at this point , it sounds like nothing has actually
been changed on your device yet? its just frozen should be still under warrentee? Unless anyone else has a better suggestion you should be
able to return it for exchange to ATT
Good Luck
KJL

It sounds like Windows is not properly recognizing your device when it is plugged into the USB port while in SSPL mode.
Have you tried different ports?
Is there another computer you can use?

another thought about returning under warranty
on the boot page of the stock Pure it indicates HSPL 1.83.000
After you update the HSPL it will say HSPL "1.83.Olinex"
this normally an indication of a successful update,
but it will probably void your warranty if they just look at the boot screen
This is true for all Pure (and Tmobile Compact V) Rom upgrades
The Stock Pure came with 6.5 and therefore the 1.83.00 HSPL
The Diamond2s did not, so their solution which reverts to 1.63 <?>
will not correctly revert to 1.83.00 on the Pure.
No way to correct this yet as far as I know,?
All the "reverts" are geared toward the Diamond2s, not the Pure.
But If your boot screen indicates 1.83.00 before it freezes
I'm fairly sure its still entitled to a warranty repair/replace
How could they tell the cause of the failure
was a reburn as opposed to natural causes?
Good Luck
KJL

When you put the phone into a manual bootloader mode... Mobile Device Center becomes obsolete.
HardSPL is only needed for unofficial roms. Forget HardSPL for the time being. The goal here is to get your phone operational. Just download the official HTC WM6.5 WWE rom and flash that. Put phone in manual bootloader mode and run the Rom installer.
As long as your phone is in bootloader mode and says "USB"... then your set to go.
Another solution is to try another PC. You'd be surprised how often that will resolve your issues. Perhaps find an XP machine and install Activesync (so it loads the bootloader USB drivers). I had to do that on several occasions when my main PC refused to flash my mobile device.

I did both of the updates htc has for the pure. Both worked fine. I am on the origianal rom. It does reboot your phone and stays on the white screen for a min then it loads the update and the phone starts.

The offical ROM comes back with a wrong vender ID error I guess cause its a "pure" and not the HTC branded "topaz"... NOW what should i do??? Seems like i NEED hardspl so i can flash any ROM, as from what i researched, there IS NO AT&T Pure rom that has been released. I still cant figure out why a hard-reset will not work though.... This is REALLY starting to get me angry!!!

Just for reference, the Pure's ID is TOPA210 32M
SPL-1.83.0000
The official hotfixes worked fine for me as well. Did you apply the hotfixes on the original ROM that came with your Pure?
Also, does the official HTC Touch Diamond 2 ROM work for you? If so, the hotfixes for the Pure are irrelevant, as are any future updates released for the Pure. You should look for updates for the Touch Diamond 2 on the Worldwide HTC site.
If you needed to do a warranty claim, the closest you can get to returning your phone to stock/shipped form is to use the ROM dump using HardSPL and hope they don't notice that the SPL is different. Currently, there's no way to return the Pure back to completely official software.
A hard reset simply wipes everything off and restores everything back to what is contained in just the ROM you currently have on it. If you've flashed your phone at all, you've already wiped out the original ROM that came with it.

It is still the STOCK ROM. I have never flashed it yet.. The topaz rom will not flash due to a vender ID error. The spl is still stock also... i think thats is why i am having this problem. I bought the phone off craigslist so returning it to AT&T is NOT an option either way. My only solution is to find a fix. (or trash it) I really appreciate all of your suggestions and input so far. You guys are by far the best board around! I am a LONG time follower, but a few-time poster. Obviously i have little to contribute to the board.

Can I trouble you to dig up a few version numbers? It'd help evaluate your situation so we can see which options are best for your case.
ROM version? You can find this in Device Information. Start --> Settings --> System --> Device Information
Bootloader version? Do a soft reset while holding down the volume down button on the side until a screen with red, green, blue, and white, ordered top to bottom, shows up. It should be the second line starting with "SPL-..."

The ROM is the STOCK AT&T ROM (again...) I CAN NOT go to start;.... because if you noticed in the first post, the phone will not boot past the white "AT&T WorldPhone" screen... the spl is stock also incase you missed that part. (1.33.0000) I have never flashed the divice. EVERYTHING IS HOW AT&T SELLS THE PURE OUT OF THE BOX! NO MODS. NO FLASHED ROMS. NO HardSPL... NOTHING! STOCK!!! (for those overlooking the details in my previous posts) I have no doubt you guys (n hopefully a few girls ) will help me fix my issue. I'm just REALLY anxious for it to happen sooner than later!

Have you tried downloading the official rom here on xda and renaming it to TOPAIMG.nbh and update using the sd card method?
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=600339
The download is in post #1

I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!

jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
You can flash hard SPL the same way by renaming the .nbh file to
TOPAIMG.nbh

jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
Actually that is supposed to be an officially signed rom. If that is true it will work with the stock spl. It will either work or it won't. Also, as stated in the response after yours, you can apply the hardspl via SD as well.

[ROM]RUU_Mozart_TMO_DE_1.20.111.03_Radio_5.50.09.18_22. 24.50.09U, by ansar

Hi,
A new ROM for the TMO_DE operator:
RUU_Mozart_TMO_DE_1.20.111.03_Radio_5.50.09.18_22.24.50.09U_by_ansar
just in case you need to comeback to this branded ROM for any reason
see also thread: Windows Phone 7 Branded ROMs for Mozart
Till next version enjoy!!!
Regards, ansar

i have problems with my phone not booting past the white screen
i tried a hard reset with no luck
i want to flash my phone with default firmware
Its a mozart from tMo-de, unlocked from the store
my questions are : i want to make sure that it will not ask the unlock code once im done
or can i flash a unbranded rom on this phone?
i found this rom
i need it NOT to be Nodo, which version is this one?

mariu$ said:
i have problems with my phone not booting past the white screen
i tried a hard reset with no luck
i want to flash my phone with default firmware
Its a mozart from tMo-de, unlocked from the store
my questions are : i want to make sure that it will not ask the unlock code once im done
or can i flash a unbranded rom on this phone?
i found this rom
i need it NOT to be Nodo, which version is this one?
Click to expand...
Click to collapse
Hi,
This ROM is NoN NoDo and will not ask unlock code after flashing
How did you manage to boot only at splash?
I hope it is not a bad Storage Card issue
Regards, ansar

i forgot to say that this problem came up when using zune update
i came to this rom to see if i can correct the problem
looks like many tmobile de phones have this problem, took my second one and also got stuck at the white boot up screen after update, proably the only way to upgrade is using romupdateutility, impossible with zune
recovered using restore point
im trying romupdateutiliy now but it says that rapitool closed
tried restart and different usb port and the same problem comes up
it says to check the usb connection but im sure its ok, and its on bootloader
dont know what to do
anyways im trying to flash 1.28
installed wm device center and its working
victory

mariu$ said:
i forgot to say that this problem came up when using zune update
i came to this rom to see if i can correct the problem
looks like many tmobile de phones have this problem, took my second one and also got stuck at the white boot up screen after update, proably the only way to upgrade is using romupdateutility, impossible with zune
recovered using restore point
im trying romupdateutiliy now but it says that rapitool closed
tried restart and different usb port and the same problem comes up
it says to check the usb connection but im sure its ok, and its on bootloader
dont know what to do
anyways im trying to flash 1.28
installed wm device center and its working
victory
Click to expand...
Click to collapse
Hi,
Glad you fix it!!
Regards, ansar